[dapper] linux-image-2.6.15-12-386 has no SATA support

Though I can't boot with 2.6.15-12, if I drop back to 2.6.15-7-386 I can boot with no trouble as long as I switch X from the nvidia driver to the nv driver.

Please don't change the severity just yet. For starters, I know that SATA is working for others with the 386 kernel.

First, you need to attach dmesg and lsmod output from a working boot. I really suspect this is a udev bug.

I had the same thing when trying to install an MSI 1u server.. I had to add scsi_mod to the initramfs image, and then it worked. It was a gdth raid device, but just loading the gdth driver without a scsi_mod present caused the error above

Original user never replied. I suspect this was a passing problem, perhaps fixed in initramfs-tools.

I suffer from this and have yet to fix it - if this could be reopened and investigated, that'd be nice. I'm in the process of downloading a live-cd to try adding sata_nv to the initramfs. In my case, the root partition is on /dev/sda2.

(sorry if changing the bug to unconfirmed isn't the correct thing to do, I'm not familiar with launchpad)

Try adding sd_mod. I know that sata_nv works. I just setup an Athlon system with nforce4 motherboard and an sata 300GB drive. Installed it on, and booting from it just fine.

I didn't need to do anything to get it working.

im having something similar to this problem as well. ive managed to intsall dapper flight 4 without any hickups. However, during my first boot, it just wont boot.

it says something like /dev/sda2 does not exist. dropping a shell.

my specs are:
Abit IC7-MAX3 Mobo
Pentium 4 e 3.0 ghz
Raptor 40 gb <--- set my bios to boot from this hdisk, therefore hd0
Seagate Sata 120gb
Seagate Sata 200gb

I posted a similar bug (#um...)

On installing Dapper from a Beta 2 install disc, then performing the forced reboot, this message appears:
-----
Okay booting the kernel yadda yadda

mount: Mounting /root/dev on /dev/.static/dev failed: No such device
mount: Mounting /sys on /root/sys failed: No such file or directory
mount: Mounting /proc on /root/proc failed: No such file or directory
Target filesystem doesn't have /sbin/init

BusyBox v1.00-pre10 (Debain 20040623-1ubuntu22) Built-in shell (ash)
Enter 'help' for a list of built-in commands
-----

The relevant specs of the machine are one ATA (sda and sdb) hard disks and one SATA hard disk (sdc). Dapper installed on sda [1,5], Breezy installed on sdb [1,5], and two storage partitions on sdc [1,2].

The hack to correct the problem was to edit menu.lst on sda1 from sdb1 (Breezy), changing the line:

/boot/vmlinuz-2.6.15-22-386 root=/dev/sda1 ro quiet splash

to

 /boot/vmlinuz-2.6.15-22-386 root=/dev/sdb1 ro quiet splash

This loads Dapper. Now the issue is Dapper doesn't appear to know where it is (sometimes it thinks it's sda1, other times sdb1), and it never knows where it is in relation to the other hard disks (sdb mounts as sda, sdc mounts as sdb, and so on).

Bug number 44261 ^

I am marking this as a duplicat of #44261 though this bug report is older. #44261 in spite of this is Confirmed and Medium and is correctly assigned to the installer. Feel free to add comments there.

Thanks for making Ubuntu better and feel free to file new bug reports at any time.

[Expired for linux-source-2.6.15 (Ubuntu) because there has been no activity for 60 days.]