On 25/11/2020 07:59, Richard Kimberly Heck wrote:
On 11/24/20 5:53 PM, Ed Greshko wrote:
On 25/11/2020 05:43, Richard Kimberly Heck wrote:
On 11/24/20 2:12 PM, Jonathan Billings wrote:
On Tue, Nov 24, 2020 at 02:06:46PM -0500, Richard Kimberly Heck wrote:
This looks like the issue:
Nov 22 23
On 11/24/20 5:53 PM, Ed Greshko wrote:
On 25/11/2020 05:43, Richard Kimberly Heck wrote:
On 11/24/20 2:12 PM, Jonathan Billings wrote:
On Tue, Nov 24, 2020 at 02:06:46PM -0500, Richard Kimberly Heck wrote:
This looks like the issue:
Nov 22 23:10:03 rkhstudy kernel: lockd: server 192.168.1.2 n
On 25/11/2020 05:43, Richard Kimberly Heck wrote:
On 11/24/20 2:12 PM, Jonathan Billings wrote:
On Tue, Nov 24, 2020 at 02:06:46PM -0500, Richard Kimberly Heck wrote:
This looks like the issue:
Nov 22 23:10:03 rkhstudy kernel: lockd: server 192.168.1.2 not responding,
still trying
This was wo
On 11/24/20 2:12 PM, Jonathan Billings wrote:
On Tue, Nov 24, 2020 at 02:06:46PM -0500, Richard Kimberly Heck wrote:
This looks like the issue:
Nov 22 23:10:03 rkhstudy kernel: lockd: server 192.168.1.2 not responding,
still trying
This was working fine in Fedora 32, though, so I'm puzzled wha
does your hdpi have an ARC ?? this was my problem and a PITA as you dont
get any fedora tips about this issue.
On Tue, Nov 24, 2020 at 10:59 AM Jorge Fábregas
wrote:
>
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an ema
On Tue, Nov 24, 2020 at 02:06:46PM -0500, Richard Kimberly Heck wrote:
> This looks like the issue:
>
> Nov 22 23:10:03 rkhstudy kernel: lockd: server 192.168.1.2 not responding,
> still trying
>
> This was working fine in Fedora 32, though, so I'm puzzled what's wrong now.
> There's no firewall
On 11/24/20 7:55 AM, Jonathan Billings wrote:
On Nov 23, 2020, at 22:08, Richard Kimberly Heck wrote:
I believe it is v3 on the server.
If so, you need to make sure that the rpc.lockd can communicate on both sides.
That is probably why locking fails, and any program that is hanging is because
On 11/24/20 2:47 PM, Bob Goodwin wrote:
> It shows Built-Audio selected
>
> and
>
> Profile: Analog Stereo Duplex (unavailable)
>
> Those items look questionaable to me?
That should be the profile: "Analog Stereo Duplex". I honestly don't
know why it appears as unavailable. Check this [1]
Al
On 11/24/20 2:18 AM, Stephen Morris wrote:
On 24/11/20 1:55 pm, Richard Kimberly Heck wrote:
On 11/23/20 9:17 PM, Jonathan Billings wrote:
On Nov 23, 2020, at 19:05, Richard Kimberly Heck
wrote:
LyX refuses to start, blocking at a call to
lockf(fd, F_LOCK, 0) at support/filetools.cpp, during
On 2020-11-24 13:26, Jorge Fábregas wrote:
I see the built-in audio controller from Intel. In pavucontrol, under
"Configuration"...do you see your card there? If so, what profile do you
have selected?
°
It shows "Profile: Digital Stereo (HDMI 3) Ouput
However I have wondered about this, the
Every time I install a new fedora, I think I lost sound
because the new feddora always picks the motherboard
audio output as the default, and I always listen via
the TV speakers over HDMI.
I always run:
gnome-control-center sound
to change the default output to HDMI. It apparently does
something
On 11/24/20 2:22 PM, Bob Goodwin wrote:
> Yes I always use the PAVolumecontrol to see what I can. as I said, there
> appears to be an input at Playback but nothing at the Output. Alsamixer
> shows levels set to 100% but no sound out ...
I see the built-in audio controller from Intel. In pavucon
On 2020-11-24 13:04, Jorge Fábregas wrote:
Try these commands as root to see if you see your soundcard there:
aplay --list-devices
cat /proc/asound/cards
And to see the driver (kernel module) being used (usually called snd*):
lsmod | grep snd
°
[bobg@Workstation-2 ~]$ lsmod | grep snd
snd_h
On 11/24/20 1:57 PM, Bob Goodwin wrote:
> In a new install of Fedora-33 desktop I have no sound. I have fiddled
> with the problem for several days to no avail so I guess I need to ask
> for help.
Try these commands as root to see if you see your soundcard there:
aplay --list-devices
cat /proc/
In a new install of Fedora-33 desktop I have no sound. I have fiddled
with the problem for several days to no avail so I guess I need to ask
for help.
PA Volume appears to get an input but i see no output ...
The system had sound with the previous install which was removed when
anaconda did t
If you have a "rescue" option in grub then boot it, the rescue install
should be built with hostonly=no and is expected to include all
drivers including that one. I verified on one of my machines that one
is included in my rescue. The normal initrd is hostonly=yes and only
includes the critical
On Nov 23, 2020, at 22:08, Richard Kimberly Heck wrote:
>
> I believe it is v3 on the server.
If so, you need to make sure that the rpc.lockd can communicate on both sides.
That is probably why locking fails, and any program that is hanging is because
locks are hanging.
--
Jonathan Billings
On 24/11/2020 20:19, Sreyan Chakravarty wrote:
I think I have found the problem:
Nov 24 10:44:00 localhost.HPNotebook dracut-initqueue[861]: Scanning devices
dm-0 for LVM logical volumes vgfedora/fedora
Nov 24 10:44:00 localhost.HPNotebook dracut-initqueue[886]: inactive
'/dev/vgfedora/pool00
Ok,
I think I have found the problem:
Nov 24 10:44:00 localhost.HPNotebook dracut-initqueue[861]: Scanning
devices dm-0 for LVM logical volumes vgfedora/fedora
Nov 24 10:44:00 localhost.HPNotebook dracut-initqueue[886]: inactive
'/dev/vgfedora/pool00' [929.75 GiB] inherit
Nov 24 10:44:00 localho
On Mon, Nov 23, 2020 at 4:02 AM Michael D. Setzer II via users <
users@lists.fedoraproject.org> wrote:
> dd bs=1M if=$localback |lzop -c - > /mnt/local$localpath$localimagename
>
> I use lzop for compression of image, since it gives good compress and is
> considerable faster than gzip.
>
> Note: S
On Mon, Nov 23, 2020 at 9:27 AM Jonathan Billings
wrote:
>
> 'dump' is probably the most appropriate tool to capture an ext4 volume
> to be converted to a thin-provisioned volume. Tar could also work as
> long as you capture all the extended (selinux) attributes, which I
> don't believe were des
On Mon, Nov 23, 2020 at 5:12 PM Samuel Sieb wrote:
> For general imaging, dd is fine. But you need to read the context here.
> He wants to make an image of the current filesystem in order to write
> it back to a thin LV. For that purpose, you only want to be writing the
> used blocks. Otherw
Hi,
I have cloned my original root LVM, and then migrated to the newer thin
LVMs using partclone.
Both backup and restore went off without causing any problems.
But when I am now trying to boot into my system, it asks for the encryption
LUKS passphrase but after that I am getting:
23 matches
Mail list logo
