Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#1276 - kernel26 2.6.8.1-2 upgrade doesn't recognize my SATA drive
Attached to Project:
Arch Linux
Opened by Don Melton (gramps) - Friday, 20 August 2004, 09:39 GMT
Last edited by Judd Vinet (judd) - Friday, 20 August 2004, 16:34 GMT
Opened by Don Melton (gramps) - Friday, 20 August 2004, 09:39 GMT
Last edited by Judd Vinet (judd) - Friday, 20 August 2004, 16:34 GMT
|
DetailsI just upgrade from kernel-scsi 2.6.8.1-1 to kernel26 2.6.8.1-2 in order to take advantage of the new SATA support in the regular kernel. Unfortunately the new kernel doesn't recognize my SATA drive saying it can't find the root partition. Since I'm the same knucklehead who posted the other bit SATA problem on Tuesday:
http://bbs.archlinux.org/viewtopic.php?t=6259 ... I knew to try a few different drive designation this time. Unfortunately none of them worked on my VIA controller. |
This task depends upon
egrep -i '(sata|serial)' /proc/pci
Thanks
RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 128).
Judd, I'll try building a few custom kernels later tonight and/or this weekend to try and figure out what's going on.
strongbad:home/brett> egrep -i '(sata|serial)' /proc/pci
RAID bus controller: Silicon Image, Inc. (formerly CMD Technology Inc) Silicon Image Serial ATARaid Controlle (rev 2).
Since you're having the same problem I guess we can assume that it's not a driver-specific issue because I'm using the VIA driver and I believe you're using the SIS driver.
(Also, I'd like to say I'm disturbed at how bad my grammar was in the original text description of this bug report. This will remind me of the perils of writing after 2 a.m. ;)
I figured out the problem and it only took one kernel compile and install to prove it. :)
I decided to compare the config files for kernel-scsi 2.6.8.1-1 to kernel26 2.6.8.1-2 and it stood out when I thought about it. Here's the patch:
--- kconfig26-2.6.8.1-2 2004-08-19 12:36:28.000000000 -0700
+++ /boot/config-2.6.8.1-test 2004-08-21 00:24:10.000000000 -0700
@@ -397,7 +397,7 @@
#
# SCSI support type (disk, tape, CD-ROM)
#
-CONFIG_BLK_DEV_SD=m
+CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_ST=m
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=m
Yep. Basic SCSI support for hard disks (the "CONFIG_BLK_DEV_SD" flag) must be compiled into the kernel rather than as a module or the kernel can't call the compiled-in support for VIA, SIS and other SATA chipsets at boot time.
Of course, compiling this in adds another 5291 bytes to the size of the kernel but that's still much smaller than the entire SCSI binary.
I look forward to seeing kernel26 2.6.8.1-3 soon. :)