| View previous topic :: View next topic |
| Author |
Message |
FoxHunter
n00b
Joined: 12 May 2004
Posts: 9
|
 Posted: Tue Jun 08, 2004 5:03 pm Post subject: Where's my S-ATA drive? |
 |
|
Hi
I'm running my S-ATA drive in Enhanced Mode, because I need both 2 IDE-Channels. My Gentoo-Install is using the gentoo-dev-sources-2.6.5-r1.
However, it seems like I can't access my S-ATA drive. Here's some dmesg output:
| Quote: | ICH5: IDE controller at PCI slot 0000:00:1f.1
PCI: Enabling device 0000:00:1f.1 (0005 -> 0007)
ICH5: chipset revision 2
ICH5: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:DMA, hdd:DMA
hda: SAMSUNG SP4002H, ATA DISK drive
hdb: QUANTUM FIREBALLlct08 17, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: CREATIVE DVD-ROM DVD1243E, ATAPI CD/DVD-ROM drive
hdd: RICOH CD-R/RW MP7080A, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 78242976 sectors (40060 MB) w/1824KiB Cache, CHS=65535/16/63, UDMA(100)
/dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 >
hdb: max request size: 128KiB
hdb: 33906432 sectors (17360 MB) w/418KiB Cache, CHS=33637/16/63, UDMA(33)
/dev/ide/host0/bus0/target1/lun0: p1 p2 p3
hdc: ATAPI 40X DVD-ROM drive, 512kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
hdd: ATAPI 32X CD-ROM CD-R/RW drive, 4096kB Cache, DMA
libata version 1.02 loaded.
ata_piix version 1.01
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ata1: SATA max UDMA/133 cmd 0xEFE0 ctl 0xEFAE bmdma 0xEF60 irq 18
ata2: SATA max UDMA/133 cmd 0xEFA0 ctl 0xEFAA bmdma 0xEF68 irq 18
ata1: SATA port has no device. disabling.
scsi0 : ata_piix
ata1: thread exiting
ata2: dev 0 cfg 49:2f00 82:346b 83:7f01 84:4003 85:3c69 86:3c01 87:4003 88:20ff
ata2: dev 0 ATA, max UDMA7, 312581808 sectors (lba48)
ata2: dev 0 configured for UDMA/133
scsi1 : ata_piix
Vendor: ATA Model: SAMSUNG SP1614C Rev: 1.02
Type: Direct-Access &n bsp; ANSI SCSI revision: 05
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 32Kbytes |
Here's the most interesting line:
| Quote: | scsi1 : ata_piix
Vendor: ATA Model: SAMSUNG SP1614C Rev: 1.02
Type: Direct-Access &n bsp; ANSI SCSI revision: 05 |
It seems like my S-ATA drive is being found, but there's no /dev for it.
It's neither listed under /dev/hd*, nor /dev/sd*.
What am I doing wrong?
My Gentoo install is running fine, except that I can't access my S-ATA drive.
regards |
|
| Back to top |
|
 |
arch_dude
n00b
Joined: 06 Apr 2004
Posts: 38
|
| Posted: Tue Jun 08, 2004 7:23 pm Post subject: I think you need to sonfigure the kernel with SCSI |
|
|
I'm also using SATA on gentoo-dev-sources-2.6.5-r1.
Here is the snippet from my dmesg:
| Code: | Uniform CD-ROM driver Revision: 3.20
libata version 1.02 loaded.
ata_piix version 1.01
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ata1: SATA max UDMA/133 cmd 0xC400 ctl 0xC802 bmdma 0xD400 irq 18
ata2: SATA max UDMA/133 cmd 0xCC00 ctl 0xD002 bmdma 0xD408 irq 18
ata1: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c69 86:3e01 87:4003 88:207f
ata1: dev 0 ATA, max UDMA/133, 320173056 sectors (lba48)
ata1: dev 0 configured for UDMA/133
scsi0 : ata_piix
ata2: SATA port has no device. disabling.
ata2: thread exiting
scsi1 : ata_piix
Vendor: ATA Model: Maxtor 6Y160M0 Rev: 1.02
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 320173056 512-byte hdwr sectors (163929 MB)
SCSI device sda: drive cache: write through
/dev/scsi/host0/bus0/target0/lun0: p1 p2 p3
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
ieee1394: raw1394: /dev/raw1394 device initialized
|
If I recall correctly, "SCSI" devices are assignes starting at /dev/sda regardless
of which controller they are on, so I'm guessing your drive will eventually be /dev/sda even though it's plugged into ata2 instead ofata1.
I'm clearly a true expert on this. after all, my very first experience with SATA was yestterday  |
|
| Back to top |
|
|
arch_dude
n00b
Joined: 06 Apr 2004
Posts: 38
|
| Posted: Tue Jun 08, 2004 7:40 pm Post subject: |
|
|
OOPS!
Somehow the important part of my reply was dropped (perhaps by me?)
I think you need to configure SCSI into your kernel to use SATA. |
|
| Back to top |
|
|
FoxHunter
n00b
Joined: 12 May 2004
Posts: 9
|
| Posted: Wed Jun 09, 2004 8:55 am Post subject: |
|
|
Thanks for your reply.
I have SCSI support in my kernel, however the drive isn't being mapped to dev/sdx
Here's a part of my kernel config:
| Quote: | #
# SCSI device support
#
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
CONFIG_CHR_DEV_SG=y
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_REPORT_LUNS is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
#
# SCSI Transport Attributes
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_MEGARAID is not set
CONFIG_SCSI_SATA=y
# CONFIG_SCSI_SATA_SVW is not set
CONFIG_SCSI_ATA_PIIX=y
# CONFIG_SCSI_SATA_PROMISE is not set
# CONFIG_SCSI_SATA_SIL is not set
# CONFIG_SCSI_SATA_VIA is not set
# CONFIG_SCSI_SATA_VITESSE is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_QLA6322 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
#
# PCMCIA SCSI adapter support
#
# CONFIG_PCMCIA_AHA152X is not set
# CONFIG_PCMCIA_FDOMAIN is not set
# CONFIG_PCMCIA_NINJA_SCSI is not set
# CONFIG_PCMCIA_QLOGIC is not set
|
regards |
|
| Back to top |
|
|
arch_dude
n00b
Joined: 06 Apr 2004
Posts: 38
|
| Posted: Wed Jun 09, 2004 2:25 pm Post subject: |
|
|
Oh, well, so much for that theory. Here is a snippet from my config:
| Quote: | #
# SCSI device support
#
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
CONFIG_CHR_DEV_SG=y
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
CONFIG_SCSI_REPORT_LUNS=y
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
|
and the remainder matches yours.
As you can see, I have
CONFIG_SCSI_REPORT_LUNS=y
but you do not.
This might be why I have more stuff in my dmesg than you do, but I speculate that it only explains the last two "extra" lines.
You might try movins the SATA cable to connector 1 instead of connector on your controller. Thsi clearly should not matter, but it is a difference between our setups. |
|
| Back to top |
|
|
r3pek
Retired Dev
Joined: 17 Sep 2003
Posts: 568
Location: Lisbon - Portugal
|
| Posted: Wed Jun 09, 2004 7:36 pm Post subject: |
|
|
| FoxHunter wrote: |
| Quote: |
CONFIG_SCSI_SATA=y
# CONFIG_SCSI_SATA_SVW is not set
CONFIG_SCSI_ATA_PIIX=y
# CONFIG_SCSI_SATA_PROMISE is not set
# CONFIG_SCSI_SATA_SIL is not set
# CONFIG_SCSI_SATA_VIA is not set
# CONFIG_SCSI_SATA_VITESSE is not set
|
|
well i noticed something in here.... don't know if i'm right 'cause i don't have any sata drive... yet. 
you did configure SATA support into the kernel but you didn't configure any sata chipset. is this normal???? |
|
| Back to top |
|
|
srs5694
Guru
Joined: 08 Mar 2004
Posts: 434
Location: Woonsocket, RI
|
| Posted: Thu Jun 10, 2004 2:25 pm Post subject: |
|
|
FoxHunter has defined an SATA chipset. That's what the CONFIG_SCSI_ATA_PIIX=y line does; it enables the PIIX chipset (used on many Intel-based motherboards, IIRC). The kernel boot messages indicate that the kernel's found the chipset and identified a hard disk it's handling.
FoxHunter, you could try forcing the matter by using mknod to create appropriate SCSI device files:
| Code: |
mknod sda b 8 0
mknod sda1 b 8 1
mknod sda2 b 8 2
|
...and so on. These numbers are what I see on my system for my first SCSI disk, so I expect they'd be right for your configuration. I'd probably do this is a directory other than /dev, at least initially.
If this works and gives you access to the disk, then that means there's a problem in your devfs configuration, or possibly a bug in the devfs driver. You can either live with it using your new device files as a workaround or try to track it down. If it doesn't work, then perhaps the attempt will give you some extra clues, like dmesg entries after you attempt to access the device files you create.
One more comment: It appears that your kernel, FoxHunter, has both the ATA PIIX driver and the libata (SCSI) PIIX driver compiled into it. I don't know offhand if the ATA PIIX driver supports SATA devices, but if it does, it's probably interfering with the libata driver. It's conceivable that the libata driver is also interfering with the ATA driver, as well. You might try simply dumping the libata driver altogether and accessing the hard disk using the ATA driver (probably as /dev/hde or /dev/hdg). Alternatively, you might try building the libata driver into the kernel and building the ATA driver as a module. That way, the libata driver should be able to detect and access the SATA drive without interference before the ATA driver even loads. This will require either placing your root (/) filesystem on the SATA drive or using an initrd, though.[/code] |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
