nusable, as the firewall effectively shuts down all
networking. Thus the severity of this bug report should be raised to "grave"
Regards,
C. Dominik Bódi
signature.asc
Description: This is a digitally signed message part.
Unfortunately, I did not think of making a foto of the messages.
I've tried that new kernel on my "real" machines at home, there it
booted without problems. Both machines are using luks and lvm. One is
unlocked manually, the other via mandos in my LAN. Both machines booted
the 3.16-1 kernel withou
I've tried the new 3.16-2 kernel today. That one works without problems.
Feel free to close this bug report.
Regards,
Dominik
signature.asc
Description: OpenPGP digital signature
Hi,
I have a similar symptom with that kernel version on my laptop which might be
caused by the same problem. I don't have any lvm/md/raid stuff on the
laptop's disk, it boots from a normal partition. Booting without the initial
ramdisk, the kernel prints the following error:
VFS: cannot open
Since the same symptoms started to appear with the older 2.6.20 kernel as
well, I have done some more investigation.
Booting the kernel without initramfs: Mounting the root filesystem fails,
although the hard disk with the root filesytem was recognised correctly. That
is probably ok since the e
Package: linux-2.6
Version: 2.6.16-6
Severity: critical
Justification: breaks the whole system
*** Please type your report below this line ***
The kernel seems to boot up normally, but then fails to mount the root device
with a message
"failed to mount root on /dev/hda8 - no such device"
according
Yes, booting that kernel gets me into the rescue shell. All /dev/hda?
partitions that should exist do so, as well.
Here's a list of modules that are loaded:
usbhid
8139too
ide_cd
cdrom
ide_disk
generic
ohci1394
ieee1394
8139cp
mii
ehci_hcd
ohci_hcd
atiixp
ide_core
usbcore
thermal
processor
fan
I
7 matches
Mail list logo
