How do I get all LVs to activate before activation of disk encryption?
I am mounting an encrypted filesystem in fstab that resides on a VG
different from my un-encrypted root filesystem.
The root LV is initialized in the initrd, but the remaining are not
initialized until after udev starts. This apparently leads to an
initial failure, based on the msgs I am seeing, for "Starting disk
encryption" preceeds "Setting up Logical Volume Management". After LVM
is setup, "Starting Disk Encryption" is run again and I can enter the
pass phrase and all is well.
Tho the problem is currently self healing, it seems that something is
out of sync.
I have Compaq Presario C772TU Laptop. I has Atheros AR5006X Wireless Network
Adapter. Yesterday I installed Fedora 8 but I was not able to enable WiFi.
1. I tried configuring WiFi using KNetworkManager, but no luck.
2. I installed Windows driver (.inf and .sys) file in fedora using
NDISwrapper. When I tried to scan wlan0 I got the error that "Network
doesn't support Scanning: Network is Down". I then tried *ifconfig
wlan0 up*but I got following error
*How can I enable WiFi on Fedora 8. Is this problem solved in Fedora 9.
I really love Fedora and don't want to switch to any other OS.
I'm experiencing the same issue on an F9 x86_64 updated system. I booted with the rescue disk and everything GRUB-related looks fine. I ran a memory test which also checked out. I don't know what component to file a bug against, although my suspicion is that it's anaconda. Any help would be appreciated. The system stops at the word "GRUB" and allows no further input.
After logging out of KDE or Gnome, the login panel (I use kdm) won't
respond to the keyboard. I have to restart the X server via the onscreen
menu before being able to log in again.
Anyone know if this is an X issue or should I report it to bugs.kde.org?
Has anybody noticed that F9-pre installer creates an /etc/fstab file
based on UUIDs instead of LABELs? I seem to remember everybody all
worked up about LABELs instead of the traditional /dev/sda2 type
identifiers, in order to simplify changes to hard drive configuration.
But now, all of a sudden I've got this 32-character long UUID that makes
everything complicated again.
Granted, I understand that a UUID is just as good as a LABEL, as far as
functionality goes, but LABELs are so much easier to read, compare, and
type. Why would the F9 installer choose to create UUIDs instead of
readable LABELs? I have no idea.
After the updates that have come out, Friday though yesterday, I finally did a reboot. Whe4n it boots, the word "grub" pops up on the screen and that's as far as it goes. I assume its toast but what caused it? I can't say what the updates are since the laptop is now dead as my grandmother.