On Wed, Aug 11, 2004 at 12:31:04AM -0500, Evilpig wrote: > Output of lspci from my YellowDog install: > 00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40) > 00:0d.0 PCI bridge: Digital Equipment Corporation DECchip 21154 (rev 02) > 00:10.0 VGA compatible controller: ATI Technologies Inc Rage 128 RE/SG > 01:00.0 FireWire (IEEE 1394): Texas Instruments PCILynx/PCILynx2 IEEE > 1394 Link Layer Controller (rev 02) > 01:01.0 IDE interface: CMD Technology Inc PCI0646 (rev 05) > 01:02.0 PCI bridge: PicoPower Technology PT86C525 [Nile-II] PCI-to-PCI > Bridge (rev 01) > 01:03.0 SCSI storage controller: Adaptec AHA-7850 (rev 03) > 01:04.0 SCSI storage controller: Adaptec AHA-2940U2/U2W (rev 01) > 01:05.0 Class ff00: Apple Computer Inc. Paddington Mac I/O > 01:06.0 USB Controller: OPTi Inc. 82C861 (rev 10) > 02:08.0 SCSI storage controller: Advanced System Products, Inc > ABP940-U / ABP960-U (rev 03) > 02:09.0 Multimedia video controller: Zoran Corporation ZR36057PQC > Video cutting chipset (rev 02) > > Output of lspci -n from my YellowDog install: > 00:00.0 Class 0600: 1057:0002 (rev 40) > 00:0d.0 Class 0604: 1011:0026 (rev 02) > 00:10.0 Class 0300: 1002:5245 > 01:00.0 Class 0c00: 104c:8000 (rev 02) > 01:01.0 Class 0101: 1095:0646 (rev 05) > 01:02.0 Class 0604: 1066:0004 (rev 01) > 01:03.0 Class 0100: 9004:5078 (rev 03) > 01:04.0 Class 0100: 9005:0010 (rev 01) > 01:05.0 Class ff00: 106b:0017 > 01:06.0 Class 0c03: 1045:c861 (rev 10) > 02:08.0 Class 0100: 10cd:1300 (rev 03) > 02:09.0 Class 0400: 11de:6057 (rev 02) > > Comments/Problems: > > There were two problems here; the first is pretty minor but the second > is more significant. The first issue was that the onboard network > card was not detected and I had to choose the BMAC driver from the > list myself. Although I realize that not all cards will be > autodetected, it seems like this one should be since it was the > standard onboard card for the G3 series (at least the blue & whites).
I can't find your network card in the lspci output at all. Does anyone have any idea why this could be? > The installer completed succesfully, but unfortunately wouldn't reboot > into Debian. Since this machine doesn't have a serial port I could > not capture the output of the boot process in a serial console, so I > had to take a picture and type it all out (and I could only get the > last screen). From the combination of this output and the lspci, it > seems that the problem is related to the firewire module. It's > possible that there are minor typos in this since I had to type it by > hand, so if you need something verified just ask - it's infinitely > reproducable: > > tsdev: loaded successfully > evbug: blacklisted > evdev: already loaded > input [success] > isapnp > isapnp [success] > net > net [success] > pci > ignoring pci display device on 00:10.0 > PCI: Enabling device 0000:01:00.0 (0014 -> 0016) > pcilynx0: allocated PCL memory 4096 Bytes @ 0xd7f01000 > pcilynx0: allocated interrupt 21 > pcilynx0: remapped memory spaces reg 0xda1e6000, rom 0xda268000, ram > 0xda246000, aux 0xda257000 > Machine check in kernel mode. > Caused by (from SRR1=41030): Transfer error ack signal > Oops: machine check, sig: 7 [#1] > NIP: DA1E816C LR: DA1E9CB4 SP: D73FDAE0 REGS: d73fda30 TRAP: 0200 Not tainted > MSR: 00041030 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11 > TASK = d7356cf0[826] 'modprobe' THREAD: d73fc000Last syscall: 128 > GPR00: 82000000 D73FDAE0 D7356CF0 FFFFFFFF 00000200 FFFFFFFF 00000002 C02B5CDC > GPR08: 000591F5 DA1E6F0C 00000000 DA1E6000 82088424 1001DD78 00000000 00000000 > GPR16: 00000000 00000000 00000000 00000000 10001378 10018850 00000000 00000000 > GPR24: 00000020 D73FA000 C1C7CC48 C1C7CC00 D73FBD98 D73FBD9C D73FBD90 00009032 > NIP [da1e816c] get_phy_reg+0x58/0xf4 [pcilynx] > LR [da1e9cb4] add_card+0x4a8/0xbd8 [pcilynx] > Call trace: > [da1e9cb4] add_card+0x4a8/0xbd8 [pcilynx] > [c00b1b80] pci_device_probe_static+0x6c/0x88 > [c00b1bec] __pci_device_probe+0x50/0x70 > [c00b1c3c] pci_device_probe+0x30/0x60 > [c00da81c] bus_match+0x50/0x8c > [c00da99c] driver_attach+0x88/0xc8 > [c00dacf4] bus_add_driver+0x98/0xec > [c00db1a8] driver_register+0x30/0x40 > [c00b1f44] pci_register_driver+0x68/0xa4 > [da10101c] pcilynx_init+0x1c/0xa8 [pcilynx] > [c00365ec] sys_init_module+0x198/0x31c > [c0007c40] ret_from_syscall+0x0/0x44 > ./pci.agent: line 156: 826 Bus error $MODPROBE $MODULE >/dev/null 2>&1 > pcilynx: can't be loaded > missing kernel or user mode driver pcilynx Looks like a bug in the pcilynx module. - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
