S-ATA trouble. Can't boot installed system
Today I spent several hours installing 9.0 for AMD 64 through FTP using the Suse 9.0 patch-boot cd. Not an easy task compared to previous Suse FTP installations I did. Anyway now for the question I have. My fresh installed systeem hangs at boot. Kernel panic because the root partition SDA5 cannot be mounted. I have a serial ata drive with ext3 hooked on a Via controller on a MSI KT8 NEO board. I think the problem relates to to the possible absence of the sata_via module/driver during boot. Can somebody confirm that initrd needs to contain the sata_via module? How does a 'working' INITRD_MODULES variable in /etc/sysconfig/kernel look? Using the Suse 9.0 patch-boot cd I managed to boot the system. I tried to make a new initrd with the mkinitrd script. The response was that the dependencies of sata_via couldn't be determined, "maybe modules.dep is out of date". Running depmod -a didn't help me: "/lib/modules/2.4.20-4GB-athlon/modules.dep could'nt be opened for writing". I don't know why. Filesystem is mounted rw. Please help. I am stuck. Regards, Jeroen Amsterdam
On Thu, 26 Feb 2004 depot@xs4all.nl wrote:
Today I spent several hours installing 9.0 for AMD 64 through FTP using the Suse 9.0 patch-boot cd. Not an easy task compared to previous Suse FTP installations I did. Anyway now for the question I have.
My fresh installed systeem hangs at boot. Kernel panic because the root partition SDA5 cannot be mounted. I have a serial ata drive with ext3 hooked on a Via controller on a MSI KT8 NEO board.
I think the problem relates to to the possible absence of the sata_via module/driver during boot.
Can somebody confirm that initrd needs to contain the sata_via module? How does a 'working' INITRD_MODULES variable in /etc/sysconfig/kernel look?
Using the Suse 9.0 patch-boot cd I managed to boot the system.
I tried to make a new initrd with the mkinitrd script. The response was that the dependencies of sata_via couldn't be determined, "maybe modules.dep is out of date". Running depmod -a didn't help me: "/lib/modules/2.4.20-4GB-athlon/modules.dep could'nt be opened for writing". I don't know why. Filesystem is mounted rw.
Please help. I am stuck.
You are not the only one! I gave up and loaded the 2.6 kernel because the drivers for sata work under the ide system rather than the scsi system on my motherboard. Note that SuSE does _not_ support sata on amd64 9.0, only ide. If you've got the 8237 chip set, then upgrading to the 2.6 kernel will work. I'm not sure if loading it from ftp will work because I loaded to an ide disk first and then turned on sata drives from there. I should be able to boot directly to the sata drives now, but I'm gutless and tired of dinking with it! I'll just use them for main storage and working from. I did get Mandrake to boot to the sata drives using 2.4, but when I added the ide it too crashed and never really recovered. I've since formatted over it and just use the Suse distro with the 2.6 kernel. It's taken me 3 weeks to get things to work (but at only 1 or 2 hours a day, so it's not really that bad, just really frustrating!!) Not that it helps you, but I feel better now :-) Patience, persistence, truth, Dr. mike
* depot@xs4all.nl <depot@xs4all.nl> [040226 18:35]:
Today I spent several hours installing 9.0 for AMD 64 through FTP using the Suse 9.0 patch-boot cd. Not an easy task compared to previous Suse FTP installations I did. Anyway now for the question I have.
My fresh installed systeem hangs at boot. Kernel panic because the root partition SDA5 cannot be mounted. I have a serial ata drive with ext3 hooked on a Via controller on a MSI KT8 NEO board.
I think the problem relates to to the possible absence of the sata_via module/driver during boot.
Besides sata_via you need libata, sd_mod and scsi_mod in your initrd.
Can somebody confirm that initrd needs to contain the sata_via module? How does a 'working' INITRD_MODULES variable in /etc/sysconfig/kernel look?
here is mine: INITRD_MODULES="ext3 sata_via scsi_mod sd_mod libata" (But this should have been done during installation of the package) All of them are required to access the root filesystem which contains the (other) modules
Using the Suse 9.0 patch-boot cd I managed to boot the system.
I tried to make a new initrd with the mkinitrd script. The response was that the dependencies of sata_via couldn't be determined, "maybe modules.dep is out of date". Running depmod -a didn't help me: "/lib/modules/2.4.20-4GB-athlon/modules.dep could'nt be opened for ^^^^^^^^^^^^^^^^^ writing". I don't know why. Filesystem is mounted rw.
This is certainly from a 32bit kernel, and rather old as well. What exactly are you doing?
Please help. I am stuck.
Regards, Jeroen Amsterdam
-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com
-- Stefan Fent SuSE Linux AG, Maxfeldstr. 5, D-90409 Nuernberg
participants (3)
-
depot＠xs4all.nl -
Mike Rosing -
Stefan Fent