rtl8139 not recognized

[andreasf]

The integrated 100MbE NIC of my Gericom 1st Supersonic Performance notebook is not recognized by Haiku hrev36100 Live-CD.

listdev output:

device Network controller (Ethernet controller) [2|0|0]
  vendor 10ec: Realtek Semiconductor Co., Ltd.
  device 8139: RTL-8139/8139C/8139C+

Stippi indicated at BeGeistert that this one should in theory work.

[andreasf]

syslog excerpts from hrev36339:

KERN: PCI: [dom 0, bus  0] bus   0, device  8, function  0: vendor 10ec, device 8139, revision 10
KERN: PCI:   class_base 02, class_function 00, class_api 00
KERN: PCI:   vendor 10ec: Realtek Semiconductor Co., Ltd.
KERN: PCI:   device 8139: RTL-8139/8139C/8139C+
KERN: PCI:   info: Network controller (Ethernet controller)
KERN: PCI:   line_size 00, latency 40, header_type 00, BIST 00
KERN: PCI:   ROM base host 00000000, pci 00000000, size 00000000
KERN: PCI:   cardbus_CIS 00000102, subsystem_id 8139, subsystem_vendor_id 10ec
KERN: PCI:   interrupt_line ff, interrupt_pin 01, min_grant 20, max_latency 40
KERN: PCI:   base reg 0: host 00001c00, pci 00001c00, size 00000100, flags 01
KERN: PCI:   base reg 1: host e0002400, pci e0002400, size 00000200, flags 00
KERN: PCI:   base reg 2: host 00000000, pci 00000000, size 00000000, flags 00
KERN: PCI:   base reg 3: host 00000000, pci 00000000, size 00000000, flags 00
KERN: PCI:   base reg 4: host 00000000, pci 00000000, size 00000000, flags 00
KERN: PCI:   base reg 5: host 00000000, pci 00000000, size 00000000, flags 00
KERN: PCI:   Capabilities: VPD

KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/net/pegasus
KERN: [rtl8139] (rl) bus_alloc_resource(4, [16], 0x0, 0xffffffff, 0x1,0x2)
KERN: rtl8139: init_driver(0x82e55b24)
KERN: [rtl8139] (rl) bus_alloc_resource(4, [16], 0x0, 0xffffffff, 0x1,0x2)
Last message repeated 1 time
KERN: [rtl8139] (rl) bus_alloc_resource(1, [0], 0x0, 0xffffffff, 0x1,0x6)
KERN: [rtl8139] (rl) couldn't map interrupt

[anevilyak]

At a glance this looks related to ticket #5, the PCI dump indicates the controller doesn't have an interrupt assigned to it by the BIOS (which would explain the "unable to map interrupt" error message in your log)

[anevilyak]

You could possibly work around it if the BIOS has the option to disable PnP OS though. Alternatively, if the BIOS supports PXE boot, you could try enabling that, that might force it to fully configure the ethernet controller.

[andreasf]

Replying to anevilyak:

You could possibly work around it if the BIOS has the option to disable PnP OS though.

Unfortunately no. But thanks for the follow-up!

Firewire also has some IRQ issue in the syslog, and no PC cards are shown in listdev so probably the CardBus controller affected, too - it indeed sounds like #5. Feel free to close as duplicate.

[scottmc]

(In #5) All but one of the blocking tickets have been closed out, and that one just needs confirmation as to whether it's been fixed or not. So I say let's close this one out as being fixed, seeing as the reported symptoms have gone away.