From: rob p. <pf...@ri...> - 2006-09-25 16:25:24
|
On Sep 24, 2006, at 12:15 PM, mactel-linux-users- re...@li... wrote: > Mac Pro and Linux AHCI SATA driver help Here's something of a dumb question: apparently the high-end Dell and HP server systems use this same chipset and motherboard, and they can be bought from dell/hp pre- configured with linux (RHEL4, i believe). do dell and HP do their own patches to the kernel for this stuff, or is it simply that these machines have BIOS and so linux can use the 'built in' drivers for these problematic devices? so far these kind of issues have stopped me, and a friend at another company, from buying mac pros to run linux-based chip cad tools. thanks, rob |
From: J. H. <af...@bf...> - 2006-11-05 05:00:15
|
>Once you do get Linux installed either via DVD or HD image, then there's >another issue. The ESB2 is detected as the 4 port SATA device in the ICH6, >not the 6 port SATA controller it really is. ESB2 is an offshoot of one of >the ICHes. > >For this, two things must be done. First is to edit and re-build the AHCI >driver. Edit the file ahci.c and add the following line in the Dev ID list: > >{ PCI_VENDOR_ID_INTEL, 0x2680, PCI_ANY_ID, PCI_ANY_ID, 0, 0, >board_ahci }, /* ESB2 */ > >This will tell the driver to claim Dev ID 0x2680, which is the AHCI controller >ID in the Mac Pros. According to the ESB2 datasheet, the ID could be 0x2680, >0x2681, 0x2682, or 0x2683 depending on the fusing options. In this case, >0x2680 was not claimed by default in the AHCI driver. > >Also, when you rebuild the AHCI driver, it's a good idea to either not build >the ata_piix driver in your kernel, or delete the module altogether. It >won't work, and it's really the wrong driver for the ESB2 chips. We only >need the AHCI driver here, the ata_piix is for older chipsets like ICH5, >ICH5, etc. The ata_piix tries to claim the 0x2680 Dev ID, which is the ID >presented in these older chipsets for their 2 or 4 port SATA controllers. > > I did the following in linux-2.6.19-rc4: added to ./drivers/ata/ahci.c { PCI_VDEVICE(INTEL, 0x2680), board_ahci }, /* ESB2 */ removed from ./drivers/ata/ata_piix.c { 0x8086, 0x2680, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich6_sata_ahci }, I used the following settings (among many others...:-) : CONFIG_BLK_DEV_SR=m CONFIG_SATA_AHCI=y CONFIG_ATA_PIIX=m CONFIG_PATA_MPIIX=m The ahci.c driver does not appear to detect the ESB2 hardware, and the kernel panics. Using the stock kernel from a Ubuntu 6.06 installation, that hardware appears to be claimed up by the ata_piix driver. Any ideas here ? J. Hart |
From: J. H. <af...@bf...> - 2006-11-05 11:51:58
|
> I did the following in linux-2.6.19-rc4: > > added to ./drivers/ata/ahci.c > { PCI_VDEVICE(INTEL, 0x2680), board_ahci }, /* ESB2 */ > > removed from ./drivers/ata/ata_piix.c > { 0x8086, 0x2680, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich6_sata_ahci }, > > The ahci.c driver does not appear to detect the ESB2 hardware, and the > kernel panics. Some additional information : I rebuilt the kernel for 2.6.19-rc4, and insured that the modifications to the ahci and ata_piix drivers were correct. I then built into the kernel the drivers that I had earlier configured as modules, and booted the new kernel. I was able to get the following additional messages : scsi0: ahci ata1: SATA link up 3.0 Gbps (SStatus 123 Scontrol 300) ....a long pause here... ata1.00: qc timeout (cmd 0xec) ata1.00: failed to IDENTIFY (I/O error, er_mask+0x104) ata1: port is slow to respond, please be patient (Status 0x890) ata1: port failed to respond (30 secs, Status 0x80) ata1: COMRESET failed (device not ready) ata1: hard reset failed, retrying in 5 secs There are several retries of this sort before it finally gives up. It would appear that the ahci driver cannot see my drive for some reason, though the ata_piix driver will if I allow it to (ex. use it unmodified). This drive is the one that came with my machine originally, and is a Western Digital WD2500JS-41S Rev: 20.0 J. Hart |
From: Dave M. <dcm...@co...> - 2006-09-26 01:45:48
|
On Monday 25 September 2006 09:24, rob pfile wrote: > On Sep 24, 2006, at 12:15 PM, mactel-linux-users- > > re...@li... wrote: > > Mac Pro and Linux AHCI SATA driver help > > Here's something of a dumb question: > > apparently the high-end Dell and HP server systems use this same > chipset and motherboard, and they can be bought from dell/hp pre- > configured with linux (RHEL4, i believe). > > do dell and HP do their own patches to the kernel for this stuff, or > is it simply that these machines have BIOS and so linux can use the > 'built in' drivers for these problematic devices? > > so far these kind of issues have stopped me, and a friend at another > company, from buying mac pros to run linux-based chip cad tools. > > thanks, > > rob I have yet to fully determine if the driver issues discovered on the Mac Pro will be the same as on the HP and Dell systems, but the legacy IDE controller issue is the only one I've uncovered that is isolated to the Mac Pros. Also, I'm not sure if all 6 SATA controllers are available on the HP and Dell systems, will have to research that. HP does offer a driver CD for their 5000X based workstations, but only for RHEL3 and 4. I took a look at the updates, and it appears that they only support the 2.4.x kernels right now, and the driver CD only inlcudes ALSA updates and support for installing the NVIDIA drivers. On the otherhand, a price comparison will show that the HP and Dell workstations run about $700-$800 more than the Mac Pro for close to the same configurations. In my opinion, the Mac Pro case sold me on it vs. the Dell or HP. The driver issues are minor, and you can always fall back on Mac OS X or XP if you wanted. Dave |