Re: CardBus problems. $PIR: ROUTE_INTERRUPT Failed.

2005-12-18 Thread Björn König
Andrew Walker schrieb: [...] cbb0: mem 0x20822000-0x20822fff at device 2.0 on pci0 cardbus0: on cbb0 cbb0: mem 0x20821000-0x20821fff at device 2.1 on pci0 cardbus0: on cbb1 $PIR: ROUTE_INTERRUPT failed. cbb: Unable to map IRQ... device_attach: cbb1 attach returned 12 [...] I had similar

CardBus problems. $PIR: ROUTE_INTERRUPT Failed.

2005-12-17 Thread Andrew Walker
.1 on pci0 cardbus0: on cbb1 $PIR: ROUTE_INTERRUPT failed. cbb: Unable to map IRQ... device_attach: cbb1 attach returned 12 ...and then later... unknown: can't assign resource (port) unknown: can't assign resource (irq) unknown: can't assign resource (port) unknown: can&

Thinkpad 380XD with CardBus problems. $PIR: ROUTE_INTERRUPT Failed.

2005-12-13 Thread Andrew Walker
/messages: cbb0: mem 0x20822000-0x20822fff at device 2.0 on pci0 cardbus0: on cbb0 cbb0: mem 0x20821000-0x20821fff at device 2.1 on pci0 cardbus0: on cbb1 $PIR: ROUTE_INTERRUPT failed. cbb: Unable to map IRQ... device_attach: cbb1 attach returned 12 AND LATER (may not be relavent, but

$PIR: ROUTE_INTERRUPT failed.

2004-03-29 Thread Wayne Sierke
Do I need to be concerned about these boot entries in /var/log/messages (running -CURRENT i386): kernel: pci1: on pcib1 -> kernel: $PIR: ROUTE_INTERRUPT failed. kernel: pci1: at device 0.0 (no driver attached) and I presume to be related: kernel: vga0: at port 0x3c0-0x3df io