J?rgen Keil wrote: >Nov 23 21:47:35 max cardbus: [ID 451854 kern.notice] pciclass,0607000: >........................................ >Nov 23 21:47:35 max cardbus: [ID 451854 kern.notice] pciclass,0607000: Pri >Bus = [0x2] >Nov 23 21:47:35 max cardbus: [ID 451854 kern.notice] pciclass,0607000: Sec >Bus = [0x3] >Nov 23 21:47:35 max cardbus: [ID 451854 kern.notice] pciclass,0607000: Sub >Bus = [0x3] > > >
>Nov 23 21:47:35 max cardbus: [ID 451854 kern.notice] pciclass,0607001: >........................................ >Nov 23 21:47:35 max cardbus: [ID 451854 kern.notice] pciclass,0607001: Pri >Bus = [0x2] >Nov 23 21:47:35 max cardbus: [ID 451854 kern.notice] pciclass,0607001: Sec >Bus = [0x4] >Nov 23 21:47:35 max cardbus: [ID 451854 kern.notice] pciclass,0607001: Sub >Bus = [0x4] > > This is very likely to be a bus overlapping error. Obviously BIOS assigned bus #3 to the first socket, and 4 to the second socket. These register values are left untouched on the bridge before the card is inseted. After inserting the card into the second socket, the cardbus driver allocates number 3 and programs it on the second socket. So now two socket are programmed with the same bus number. This causes a bus error so the card can never be detected. If the guess is correct, then there can be two solutions: 1. Use the BIOS assigned values. 2. Clear the BIOS assigned values at cardbus attach time. We can use lspci to verify the bug (with a card inserted in the lower socket): # lspci -M It shows the bus topology, and reports bus overlapping errors Hi Jurgen, would u please verify that? Thanks Vincent
