Puppy Linux Discussion Forum

[claude]

To Tempestuous,

I am using the pet: rtl8185-proprietary-k2.6.21.7.pet

Modules are loaded correctly (with my own script) but network interface wlan0 is absent.

Any hint please ?

Thank you very much.

Claude

[claude]

To Tempestuous,

Here is the pci list:

00:00.0 Class 0600: 8086:7100 (rev 01)
00:01.0 Class 0601: 8086:7110 (rev 01)
00:01.1 Class 0101: 8086:7111 (rev 01)
00:01.2 Class 0c03: 8086:7112 (rev 01)
00:01.3 Class 0680: 8086:7113 (rev 01)
00:0a.0 Class 0300: 1002:4755 (rev 9a)
00:0b.0 Class 0c03: 1045:c861 (rev 10)

no wlan0 interface available.

rtl8185 chipset, network card TL-WN353GD (TP-Link)

[tempestuous]

With older kernels, the Realtek wifi driver failed to reliably support the newer RTL8185 wifi chipsets, and not even the improved versions I contributed were completely successful.

If you're serious about good wifi support of your Realtek RTL8185 device, you should move up to the 2.6.25.6 kernel in Puppy 4.1.x/4.2.x, or better still, the 2.6.30.5 kernel in Puppy 4.3.x.

[claude]

To Tempestuous,

I tried with puppy 4.3.1 (kernel 2.6.30.5): if I load rtl8180, the wlan0 interface is not shown.

Any hint please ?

Claude

[tempestuous]

claude,
there is no wifi device in your PCI list.

Assuming you have provided the full list, your wifi device is not recognised by your system.
So there's no driver that will solve your problem. Your problem is low-level.
You should attend to all the low-level checklist stuff:

Check your bios. If you see an option for "PnP OS = YES/NO" set it for "NO".

Check the output of "dmesg". If you see any errors relating to ACPI, add boot options to fix this ...
such as "acpi=force".

If you see any errors relating to IRQ allocation, add the boot option "pci=biosirq".

Also I see what appears to be a PCI card with extra USB ports (1045:c861).
This might be creating a conflict with the wifi card. You should remove this card and see.

[claude]

To Tempestuous,

Here is an updated pci list:

00:00.0 Class 0600: 8086:7100 (rev 01)
Flags: bus master, medium devsel, latency 32

00:01.0 Class 0601: 8086:7110 (rev 01)
Flags: bus master, medium devsel, latency 0

00:01.1 Class 0101: 8086:7111 (rev 01) (prog-if 80 [Master])
Flags: bus master, medium devsel, latency 32
[virtual] Memory at 000001f0 (32-bit, non-prefetchable) [disabled] [size=8]
[virtual] Memory at 000003f0 (type 3, non-prefetchable) [disabled]
[virtual] Memory at 00000170 (32-bit, non-prefetchable) [disabled] [size=8]
[virtual] Memory at 00000370 (type 3, non-prefetchable) [disabled]
I/O ports at e000 [size=16]

00:01.2 Class 0c03: 8086:7112 (rev 01)
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at d800 [size=32]

00:01.3 Class 0680: 8086:7113 (rev 01)
Flags: medium devsel, IRQ 9

00:0a.0 Class 0300: 1002:4755 (rev 9a)
Subsystem: 1002:4755
Flags: bus master, stepping, medium devsel, latency 32
Memory at e6000000 (32-bit, non-prefetchable) [size=16M]
I/O ports at d400 [size=256]
Memory at e5800000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at 10000000 [disabled] [size=128K]

00:0c.0 Class 0200: 10b7:9055
Subsystem: 10b7:9055
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at d000 [size=128]
Memory at e4800000 (32-bit, non-prefetchable) [size=128]
Expansion ROM at 10020000 [disabled] [size=128K]
Capabilities: [dc] Power Management version 1

I tried all your suggestions: I removed a pci usb board (used by the mouse); the ps2 mouse is not detected.

Thank you very much for your support.

Claude

[tempestuous]

I think you have serious hardware problems.
There's now an extra PCI ID which wasn't listed in your first post: 10b7:9055
That's a 3COM ethernet card.

And this -