| PLEX86 | ||
|
Kernel Panic with ACPI DSDT Correction PatchHi, I've patched the 2.6.10 kernel that I'm using on my laptop with the the DSDT table that I'm using before in a previous installation, (before a hard disk failure and replacement on warranty) but that was with 2.6.9. On boot, the kernel panics and says: Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) I tried booting the kernel with an initrd without the added DSDT, and it worked perfectly - with the exception of acpi. After slight modification of printk so that the debug output scrolled past much slower (my laptop has no serial port, so I couldn't transfer any of the debug output to disk), I found the following message in the midst of stuff that I believe could be related: checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd I believe that this is wrong, as `file initrd-2.6.10.img-dsdt` gives: "gzip compressed data, from Unix, max compression". I have checked that the first two bytes of my initrd correspond to the magic numbers of a gzip file, and they do. SuseNvidia Saga Paul A. Bennett It is a very bad idea to have the system enabled to perform any sort of automatic updating. The likelyhood is that it will break itself. Why we want... I began to investigate the properties of the file that was gzipped. file informed me that the gzip contained a "ASCII cpio archive". I've looked through the kernel documentation, but can't find anything that tells me what the filesystem of the initrd is. ISO vs .tar No. You don't have to. Linux's utilities will happily burn any binary image (be it ISO, e2fs, FAT or even a .tar.bz2 file... Does anyone have any idea how to fix this, whats happening here or what I should do next? thanks, SuseNvidia Saga Hello! I would appreciate it if someone could help me out with a problem I'm having with my SuSE Professional 9.1 machine. It's an AMD64 machine with... Rob
|
||||
Linux groups from Newsgroups The #1 Usenet Provider on the Internet
|
||||