Matt > When you see the "boot:" prompt, hit <space> and then type 'boot -v' and > watch your system boot. Then send the list the detailed information about > the sis0 driver (use the dmesg command once you've booted.)
... pci0: <unknown card> (vendor=0x1039, dev=0x7012) at 2.7 irq 10 sis0: <SiS 900 10/100BaseTX> port 0xd400-0xd4ff mem 0xdfffb000-0xdfffbfff irq 5 at device 3.0 on pci0 sis0: Ethernet address: (...mac address...) sis0: MII without any PHY! device_probe_and_attach: sis0 attach returned 6 pci0: <unknown card> (vendor=0x14f1, dev=0x2f00) at 5.0 irq 10 pci0: <unknown card> (vendor=0x1106, dev=0x3044) at 7.0 irq 11 ... pci0: <unknown card> (vendor=0x1039, dev=0x7012) at 2.7 irq 10 sis0: <SiS 900 10/100BaseTX> port 0xd400-0xd4ff mem 0xdfffb000-0xdfffbfff irq 5 at device 3.0 on pci0 sis0: Ethernet address: (...mac address...) sis0: MII without any PHY! device_probe_and_attach: sis0 attach returned 6 pci0: <unknown card> (vendor=0x14f1, dev=0x2f00) at 5.0 irq 10 pci0: <unknown card> (vendor=0x1106, dev=0x3044) at 7.0 irq 11 ... I do not know whether it is relevant to note that win2k uses 'interrupt request 11' rather than irq5 for the sis900. In fact it uses irq11 for all pci devices. The 3 unknown devices are: pci0 2.7 is a sis7012 audio driver pci0 5.0 is a conexant 56k modem pci0 7.0 ia a VIA OHCI Compliant IEEE1394 host controller > > What's probably happening is that we're not recognizing the PHY device that > the sis900 uses, or the card itself is doing something wierd. There is no other output about sis0. -- Guido Van Hoecke <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
