Re: Kernel panic 2.6.8-9, unable to boot at all
Hello , try to remove root (hd0,0) I dont know how but for my own system this works greetings central
Re: Kernel panic 2.6.8-9, unable to boot at all
Hi, I am afraid it didn't work over here. Cheers, Ray, central wrote on 2004-10-30 16:19: Hello , try to remove root (hd0,0) I dont know how but for my own system this works greetings central
Re: Kernel panic 2.6.8-9, unable to boot at all
John C. Martin wrote on 2004-10-30 16:42: Is the driver for the root filesystem device modularized in your kernel? Yes, it is modularized. This being the 3ware card, it is part of the kernel for a very long time. I just found something somewhat odd while checking if they were actually both modularized in the config-xxx files in /boot Yes, they are both modularized. But, since my card is 3ware, I am not sure if my culprit isn't in these two lines config for kernel 2.6.7-5 CONFIG_BLK_DEV_3W__RAID=m config for kernels 2.6.8-1..2.6.8-9 CONFIG_BLK_DEV_3W__RAID=m CONFIG_SCSI_3W_9XXX=m Now... A couple of days ago I asked the 3ware people about their raid manager stuff for debian, and here is a part of their reply: We are planning to phase these in to the 8000/7000 series in the next release. Make sure the controller has the latest firmware and driver. I wonder if having the 2 modules in is what screws up things. I had the same thing here last week on my systems (Shuttle SN95G5). The driver module supporting the device the root filesystem was on was not being loaded. The problem was solved by explicitly adding the module to /etc/mkinitrd/modules and rebuilding the initrd image (using a full kernel rebuild, I could not get mkinitrd to work for me standalone). I had to fall back to previous kernel I was using (2.6.6) to boot, make these changes, and rebuild the kernel. I added '3w-' (the module I need) to /etc/mkinitrd/modules With that, I tried to login, but ended up with the same kernel panic stuff. Now... Do I need a kernel compilation? If so, how on earth can I do that --I can't even login... BTW, since I am using stock Debian kernels, is there anywhere I can download those images from. I might as well try that --easier than setting up a fresh install, I guess. Cheers, Ray
Re: Kernel panic 2.6.8-9, unable to boot at all
On Sat, Oct 30, 2004 at 02:18:09PM +0300, Basri Kanca wrote: I am in very deep and hot waters... You can try my DFS CD from http://people.debian.org/~jgoerzen/dfs. It contains a kernel that does not* require initrd to boot, and as an added bonus, has most of the critical drivers for your initial boot compiled statically. Make sure to use one of the amd64 kernels if you have an amd64 userland. You should be able to mount your existing filesystems, then chroot into your system to repair it. There are also instructions on the CD for installing one of the kernels included on it to your live system. As a general rule, I never use the initrd kernels for just some of these reasons. It's too error-prone. Once you have your machine installed, you can build your own kernel, and then the whole need for the initrd kernels goes away. (Yes, they're useful if you have to have a generic kernel, but as far as I'm concerned, that's where the usefulness ends.) [*] In the usual sense. The DFS CD does use an initrd to mount the CD and do a little housekeeping, but it doesn't use it for drivers, and when installed on your system, doesn't need an initrd at all. -- John
Re: Kernel panic 2.6.8-9, unable to boot at all
On Sat, Oct 30, 2004 at 06:36:07PM +0300, [EMAIL PROTECTED] wrote: John Goerzen wrote on 2004-10-30 18:10: Hi John, You can try my DFS CD from http://people.debian.org/~jgoerzen/dfs. Thank you. I am not being much a Linux person, yet --I am just a tad above newby level :-) I checked your site and DFS files are all non-amd64, yet there is an amd64 image in there Grab the i386 version. It has both i386 and amd64 kernels on it. Just pick the amd64 kernel from the Grub menu and you're set. It's i386 because the programs on the CD itself are compiled for i386. But they run just fine on a 64-bit machine, too, and the CD can be used to restore a 64-bit installation. http://people.debian.org/~jgoerzen/vmlinuz-2.6.6-amd64 If I placed it in the /boot of the machine (under knoppix), would it work with these in grub It should. Just make sure you delete the initrd line. It'll probably give you enough to get to a root prompt, but then you'll need to compile or install your own kernel, since this one doesn't support things like sound or DRI. As a general rule, I never use the initrd kernels for just some of these reasons. It's too error-prone. Once you have your machine installed, you can build your own kernel, and then the whole need for the initrd kernels goes away. (Yes, they're useful if you have to have a generic kernel, but as far as I'm concerned, that's where the usefulness ends.) I suppose I will have to do just that one day. ATM, I am just not brave enough to compile my own kernels :- It's actually not all that painful under Debian. There's a Linux kernel building HOWTO out there. You can use its instructions to configure that kernel, and then: make-kpkg --rootcmd=fakeroot kernel_image to roll your own .deb of the new kernel. If you can figure out partitioning, OS installation, bootloaders, etc., you can figure out kernel building :-) -- John Goerzen Author, Foundations of Python Network Programming http://www.amazon.com/exec/obidos/tg/detail/-/1590593715
Re: Kernel panic 2.6.8-9, unable to boot at all
John Goerzen wrote on 2004-10-30 19:19: I checked your site and DFS files are all non-amd64, yet there is an amd64 image in there Grab the i386 version. It has both i386 and amd64 kernels on it. Just pick the amd64 kernel from the Grub menu and you're set. d/l'ing as I write. http://people.debian.org/~jgoerzen/vmlinuz-2.6.6-amd64 If I placed it in the /boot of the machine (under knoppix), would it work with these in grub It should. Just make sure you delete the initrd line. It'll probably give you enough to get to a root prompt, but then you'll need to compile or install your own kernel, since this one doesn't support things like sound or DRI. Tries it; but I ended up with a different kernel panic: It keeps asking for an 'initrd' value. Apparently, 'initrd' just has to be given. Just out of curiosity --and ignorance :-) --, why do we need anything other than vmlinuz. Why can't the whole thing be a large singular blob :-) It's actually not all that painful under Debian. There's a Linux kernel building HOWTO out there. You can use its instructions to configure that kernel, and then: make-kpkg --rootcmd=fakeroot kernel_image to roll your own .deb of the new kernel. If you can figure out partitioning, OS installation, bootloaders, etc., you can figure out kernel building :-) Kernel building? Ha! The moment I get myself out of this mess, I shall set off to climb Mt Everest --no less :-) Cheers, Ray
Re: Kernel panic 2.6.8-9, unable to boot at all
Hi, [EMAIL PROTECTED] writes: why do we need anything other than vmlinuz. Why can't the whole thing be a large singular blob :-) Because nowadays, that blob would be so large that most bootloaders and many systems would choke on it. Regards, Jens. -- J'qbpbe, le m'en fquz pe j'qbpbe! Le veux aimeb et mqubib panz je pézqbpbe je djuz tqtaj!
