I don't mean to thread hijack, but I believe that I have a similar (if not the same) issue.
I have a syba pci card that uses the si3114 chipset. There are two versions of bios for this card, one with raid support (software) and one with controller information only (no raid). if I use the raid bios, the card boots to solaris, but no driver attaches, and no amount of toying with settings will get it to work. now, if I use the controller card and boot in the safe mode grub option with -svk, I get a decent amount of lines, and then it hangs. I turned off all non-essential onboard devices on the motherboard, and removed ALL pci cards (I need to put the networking one back in). With the minimal settings, and grub booting with -svk on the kernel, I wind up with the following: (last screen of text that I can see) pseudo-device: pseudo1 pseudo is /pseudo/[EMAIL PROTECTED] ide device at targ 0, lun 0 lastlun 0x0 model ST340016A ATA/ATAPI-5 supported, majver 0x3e minver 0x0 ata_set_feature (0x66,0x0) failed PCI-device: [EMAIL PROTECTED], ata0 ata0 is /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED] IDE device at targ 0, lun 0 lastlun 0x0 model ST340016A ATA/ATAPI-5 supported, majver 0x3e minver 0x0 ata_set_feature: (0x66,0x0) failed ATAPI device at targ 1, lun 0 lastlun 0x0 model SAMSUNG DVD-ROM SD-816B PCI-device: [EMAIL PROTECTED], ata1 ata1 is /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED] IDE device at targ 0, lun 0 lastlun 0x0 model WDC WD3200JD-22KLB0 ATA/ATAPI-6 supported, majver 0x7e minver 0x0 ata_set_feature: (0x66,0x0) failed IDE device at targ 1, lun 0 lastlun 0x0 model WDC WD3200JD-00KLB0 ATA/ATAPI-6 supported, majver 0x7e minver 0x0 ata_set_feature: (0x66,0x0) failed <hangs here> my set up is as follows onboard pata ide: primary master: st340016a (40gb seagate drive) secondary master: st340016a (40gb seagate drive) secondary slave: samsung dvd-rom controller card (si3114): 4 western digital drives. 2 of which show up as wd3200jd-22klb0 the remaining 2 show up as wd3200jd-00klb0 I believe that I have triggered the ata irq bug mentioned earlier in this thread, partly because it just hangs my system, and partly because the si3114 chipset even had a problem booting in windows (where the card is supposed to be supported) because it could not get enough resources (interrupts) and it was conflicting with other components (I wound up removing my sound card). I think that right now I am not triggering the irq bug, but another bug.. possibly having to do with sata/pata emulation on the si3114 chipset. This message posted from opensolaris.org _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
