Tiny Core Linux
Tiny Core Base => Raspberry Pi => Topic started by: Rensie on February 20, 2014, 04:54:03 PM
-
My wireless adapter is no longer working in version 5.x. I had no trouble with 4.7.5.
Adapter is RTL8187 (rosewill rnx-g1)
When I try to do anything with the wireless I get: SIOCGIFFLAGS: no such device
dmesg:
[ 3.283403] usb 1-1.3: New USB device found, idVendor=0bda, idProduct=8187
[ 3.283436] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.283458] usb 1-1.3: Product: RTL8187_Wireless_LAN_Adapter
[ 3.283504] usb 1-1.3: Manufacturer: Manufacturer_Realtek_RTL8187_
[ 3.283522] usb 1-1.3: SerialNumber: 001AEF1B286B
.......
[ 29.979510] rtl8187: Unknown symbol eeprom_93cx6_multiread (err 0)
[ 29.979691] rtl8187: Unknown symbol eeprom_93cx6_read (err 0)
I am primarily using Steen's piCorePlayer, but the problem is also present in regular Tiny Core.
-
Hi
This driver used to be provided in 3.0.21 kernel modules, then was in staging with 3.2.10, but has now been included with 3.8.13. Loading " wireless-3.8.13-tinycore " extension should provide the needed rtl8187 driver. You might also need firmware-rtlwifi extension to provide the firmware.
To summarize, load both
wireless-3.8.13-tinycore.tcz
firmware-rtlwifi.tcz
good luck
Note: I found some confusion in the location of this device driver, however in tc-5.x is found in wireless-3.8.13-tinycore.tcz
-
Also try unplug the device and reinstall to a new USB port
Also recheck the device name for example wlan0
Failing that we need more info. Start with last 50 lines of dmesg
-
It is about Raspberry Pi, therefore reference to x86 release is irrelevant.
RTL8187 driver is in the wireless-3.13.3-piCore+.tcz but depends on a modul eeprom_93cx6.ko which is missing in base. I will add it in rc2.
-
That's great, the op did also mention the problem exists in regular core
Glad you were able to resolve the problem
-
That's great, the op did also mention the problem exists in regular core
He is referring to Steen's piCorePlayer, so regular TC means probably piCore and not x86:
I am primarily using Steen's piCorePlayer, but the problem is also present in regular Tiny Core.
Kindly ask do not mix Raspberry Pi's piCore issues with x86 where the processor architecture, kernel version and possible packaging is different, it is misleading and most likely false.
-
5.2rc2 posted, please try.
-
It works! Thanks for taking care of it so quickly. Apologies for any confusion, I will try to be more specific in the future.
-
It works! Thanks for taking care of it so quickly. Apologies for any confusion, I will try to be more specific in the future.
Glad to hear it works. No need to apologies, you posted it in the regight topic and for me it was clear. Confusion was not caused by you :)