Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
03-27-2006, 03:32 PM
|
#1
|
Member
Registered: Nov 2003
Location: U.K.
Distribution: Slackware-12
Posts: 137
Rep:
|
sil 3132 sata chip driver
the 2.6.16 kernel only supports SIL CMD680 and 3112 (Serial ATA) chips, on the silicon image site there are drivers for the sil 3132, but no generic linux drivers, only distro specific.....
http://www.siliconimage.com/support/...ctid=2&osid=1&
what would be the best one to use?
thank you
|
|
|
03-27-2006, 04:13 PM
|
#2
|
LQ Guru
Registered: Jan 2003
Location: Seymour, Indiana
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
|
The sil24.c is the source for the sata sil 3124/3132 and is already in the 2.6.16 kernel source. If you go under Scsi device support > Serial ATA (Sata) support. It is listed there as Silicon Image Sata Support.
The images you see on the website are only compiled and works with those kernels specified. They are used during the install to add the sata support to install to.
Brian1
|
|
|
03-28-2006, 04:28 PM
|
#3
|
Member
Registered: Nov 2003
Location: U.K.
Distribution: Slackware-12
Posts: 137
Original Poster
Rep:
|
hi,
thanks, the reason i couldnt see it was that i didnt have development testing on, under 'code maturity'.
i built 'Silicon Image SATA support' under 'ATA etc support'
then under SCSI>low level drivers>SATA Support> 'Silicon 3124/3132 SATA Support' as built in.
there is also a 'Silicon Image SATA support' above the 3124/3132 driver which i left unbuilt.
Code:
NFORCE-CK804: IDE controller at PCI slot 0000:00:06.0
NFORCE-CK804: chipset revision 162
NFORCE-CK804: not 100% native mode: will probe irqs later
NFORCE-CK804: BIOS didn't set cable bits correctly. Enabling workaround.
NFORCE-CK804: 0000:00:06.0 (rev a2) UDMA133 controller
ide0: BM-DMA at 0xfb00-0xfb07, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xfb08-0xfb0f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
hda: Maxtor 6L160P0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: LITE-ON CD-RW SOHR-5239V, ATAPI CD/DVD-ROM drive
hdd: PIONEER DVD-RW DVR-110D, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 512KiB
hda: 320173056 sectors (163928 MB) w/8192KiB Cache, CHS=19929/255/63, UDMA(133)
hda: cache flushes supported
hda: hda1 hda2
hdc: ATAPI 52X CD-ROM CD-R/RW drive, 1536kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
hdd: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 2000kB Cache, UDMA(66)
ide-floppy driver 0.99.newide
libata version 1.20 loaded.
so libata loads but my two sata drives dont appear anywhere 
Last edited by edM; 03-28-2006 at 04:30 PM.
|
|
|
03-28-2006, 04:37 PM
|
#4
|
LQ Guru
Registered: Jan 2003
Location: Seymour, Indiana
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
|
Not sure how that driver works. Did you compile it as a module or into the kernel. If module make sure all modules are loaded. If they are and still no luck you might try compiling them into the kernel. I have seen as module not work but if in the kernel it works and vice a versa as well.
Brian1
|
|
|
03-28-2006, 04:40 PM
|
#5
|
Member
Registered: Nov 2003
Location: U.K.
Distribution: Slackware-12
Posts: 137
Original Poster
Rep:
|
Quote:
Originally Posted by Brian1
Not sure how that driver works. Did you compile it as a module or into the kernel. If module make sure all modules are loaded. If they are and still no luck you might try compiling them into the kernel. I have seen as module not work but if in the kernel it works and vice a versa as well.
Brian1
|
compiled into the kernel.
EDIT: ill try and compile them as a modules then see if that helps.
EDIT 2:
no seetting them as modules doesnt even load libata

Last edited by edM; 03-28-2006 at 05:58 PM.
|
|
|
03-28-2006, 09:45 PM
|
#6
|
LQ Guru
Registered: Jan 2003
Location: Seymour, Indiana
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
|
As modules you may have to load manual. use the command ' modprobe name_of_module '
modprobe libata
Other than that I am at a lost to what to do next. If something comes to me I will post.
Brian1
|
|
|
03-30-2006, 11:44 PM
|
#7
|
Senior Member
Registered: Dec 2003
Location: Paris
Distribution: Slackware forever.
Posts: 2,534
Rep: 
|
This kind of thing is very "sensible" so you should compile it directly into the kernel. I don't have one so i sadly can't help you more.
|
|
|
04-05-2006, 05:11 PM
|
#8
|
Member
Registered: Nov 2003
Location: U.K.
Distribution: Slackware-12
Posts: 137
Original Poster
Rep:
|
 the correct way to update a problem is to use the orginal thread!
i didnt know!
hi,
i got a bit further on but now am a bit stumped, i know its very close to working!
Code:
libata version 1.20 loaded. sata_sil24 0000:03:00.0: version 0.23 PCI: Setting latency timer of device 0000:03:00.0 to 64 ata1: SATA max UDMA/100 cmd 0xF8810000 ctl 0x0 bmdma 0x0 irq 11 ata2: SATA max UDMA/100 cmd 0xF8812000 ctl 0x0 bmdma 0x0 irq 11 ata1: SATA link down (SStatus 0) scsi0 : sata_sil24 ata2: SATA link down (SStatus 0) scsi1 : sata_sil24
what is that telling me?
thanks
|
|
|
All times are GMT -5. The time now is 07:27 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|