The order of which the disk-device handling modules are loaded is _very_ important. Len Sorensen helped me sometime ago with the same problem. The order solved my problem. On Tue, 2004-11-23 at 21:34 +0100, email@example.com wrote: > Quoting Norval Watson <firstname.lastname@example.org>: > > > Hi Gasper, > > Which kernel did you use for initial install? > > I have very similar system: amd64 athlon 3000+, nforce3 chipset, > > Seagate sata hd, the motherboard is gigabyte ga-k8ns Pro. > > 2.6.8-1 kernel does not find Seagate SATA HD. > > Are your sound, network and usb drivers working? > > Regards, > > Norv > >> > > Yes, everything else works perfectly. network module is forcedeth, > sound driver > is i810, usb mouse works fine. But -- if it's 2.6.8 -k7 it works, if it's -k8 > it doesn't. I'm using this .deb > http://packages.debian.org/unstable/base/kernel-image-2.6.8-9-amd64-k8 > > Hm... I'm thinking ... i first installed i386 and then wanted to install a 64 > bit kernel with IA32 support to debootstrap the pure64. Am I going wrong way? > > I just checked debian bug tracker for above kernel image and supposedly it has > System.map with 0 byte length - > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=281424 > Could this be it? > > Also Len Sorensen noted there's a missing initrd line in my grub/menu.lst that > might be causing this and could be related to kernel unable to mount > root. I've > also compiled my own kernel with built in drivers and same happens. > > But then could this be due to RAID in bios? (I don't know if it's enabled or > not) > > I'm sorry I'm not near the box now, but I'll check this all tomorrow. > > Regards, > Gasper Zejn > > > -- .O. Scream, Scream like the silence of the bits. ..O Dead lies the flag by the feet of the cold one. OOO Freedom WILL break the walls of mammon.
Description: This is a digitally signed message part