Tiny Core Linux
General TC => General TC Talk => Topic started by: coreplayer2 on March 29, 2012, 12:38:41 AM
-
Ok, am not sure if this is the best location for this thread but have started a list of supported wifi devices in the wiki. it should be a place of reference for those in search of a Core supported wifi device and to learn which extension will be required to support it.
Wiki list of supported wifi devices (http://wiki.tinycorelinux.net/wiki:list_of_supported_wifi_devices)
This project is still under construction, so please your input is welcome. At this early stage am open to suggestions as to which device information to include to best help those who need it and of course for ease of maintenance.
To add your tested device to the list I suggest copying this template/list to your post below. Please include as much information as possible and I'll do my best to include and maintain the wiki list with this info, thanks.
Template/Example
Wireless NIC Chip =
USB ID =
PCI ID =
OEM & Model as tested =
HW rev =
Interface =
WLAN standard [802.11] =
Frequency Band =
Security (1) =
Tested with kernel =
Tested with Wifi.tcz =
Required Extensions (2) =
Notes =
Example
Wireless NIC Chip = RTL8712U
USB ID =
PCI ID =
OEM & Model as tested = Amped-UA150C
HW rev =
Interface = USB 2.0
WLAN standard [802.11] = 802.11 b/g/n
Frequency Band = 2.4GHz
Security (1) = WPA/WPA2
Tested with kernel = 3.0.21-tinycore
Tested with Wifi.tcz = Y
Required Extensions (2) = wl-rtl8712u-3.0.21-tinycore.tcz (r8712u) - firmware.tcz (rtlwifi/rtl8712u.bin)
Notes = WPS (not tested)
Notes
1. Security WPA2 assumes WPA/WPA2 & WEP. if other please specify in the Features/notes section ( WPS )
2. As in specific extensions (TCZ's) required for device functionality and connection manager tested with but not to include deps of a connection manager, unless that dep includes a required module or firmware for the specific adaptor.
-
I would like to participate but I can not find this information, maybe you could write how to find this info in top of the wiki page
-
What is missing is the chipset information adapter is based on.
-
Hi coreplayer2
That looks like a very good starting point. I will offer a few thoughts however.
FCC ID: While this can be used to track down some information about the device/manufacturer, I think changing it
to USB ID and PCI ID for external and internal respectively would be a more useful choice.
Features: Maybe the information from Interface, WLAN standard [802.11], Frequency Band, and Security columns
could be consolidated under a features column. This will help conserve some horizontal space in the table
yet still convey that information.
Links: Add a column that can contain links to threads in the forum that have helped people. A narrow column that can
contain the word Link on one or more lines would suffice. That would aid someone in finding threads relevant
to their device.
Supported via Wifi.tcz: Remove that column and make Wifi.tcz or whatever the primary tool required is the first entry
under Required Extensions.
-
Nice idea and good job so far :) I would also opt for Vendor ID and Product ID as of lsusb and lspci. It's the simplest method to get a proper (and often complete) identification of the hardware.
-
What is missing is the chipset information adapter is based on.
Yes I agree this can be misleading but comes under the heading of "Wireless NIC" in the first column. While debating how to label this most important item I researched the chip manufacturers web site and was surprised to find they refer to their chips as Wireless NIC's so that is what I called them, thinking it was self-explanatory..
Perhaps we should Change the heading from Wireless NIC to " Based on Wireless NIC Chip " ??
-
FCC ID: While this can be used to track down some information about the device/manufacturer, I think changing it
to USB ID and PCI ID for external and internal respectively would be a more useful choice.
Cool am all over that!!
Features: Maybe the information from Interface, WLAN standard [802.11], Frequency Band, and Security columns
could be consolidated under a features column. This will help conserve some horizontal space in the table
yet still convey that information.
Like this :)
Supported via Wifi.tcz: Remove that column and make Wifi.tcz or whatever the primary tool required is the first entry under Required Extensions.
See, here's the thing.. I didn't want to alienate or offend those who like there own network manager, though Wifi.tcz is my preferred and recommended manager it isn't mandatory. Whereas the driver module and firmware extensions are.. This really refers to which tcz's are absolutely required for this device to function as advertised and which connection manager has it been tested with. Perhaps I can find a workaround...
-
Nice idea and good job so far :) I would also opt for Vendor ID and Product ID as of lsusb and lspci. It's the simplest method to get a proper (and often complete) identification of the hardware.
I use an internal module, so I think that's enough lspci:
tc@box:~$ lspci
...
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
tc@box:~$
Bingo?
ok I tried to edit the wiki in my ability
-
Vinnie, just place the details here in this thread and I'll update the wiki thank you. But looks like you got it, thanks for the contribution ;D
Good job Vinnie
-
Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
-
Hi coreplayer2
In order to retrieve the PCI ID, people should use the command
lspci -nnThe code is shown in the form nnnn:nnnn and is enclosed in square brackets.
For the USB ID, the command is
lsusbThe code is just to the right of the word ID in the same form.
These codes not only identify the Vendor:Product of the device in question, they do so in a very concise and
consistent manner. Getting individuals to include these IDs when posting about any hardware problems could
could also be beneficial when it comes to searching the forum for answers.
-
Thank's I'd forgot about the -nn. ok added it to the link to the footnotes and extended the notes to each relevant column header
thanks
-
Also maybe I need to give another example..
copy the Template from op and edit it with your adapters specific details, like this one please :)
Second USB-Wifi adapter from Patriot
Wireless NIC Chip = Realtek Semiconductor RTL8191SU
USB ID = 0dba:8172
PCI ID =
OEM & Model as tested = Patriot - PCBOWAU2-N
HW rev =
Interface = USB 2.0
WLAN standard [802.11] = 802.11 b/g/n
Frequency Band = 2.4GHz
Security (1) = WPA/WPA2
Tested with kernel = 3.0.21-tinycore
Tested with Wifi.tcz = Y
Required Extensions (2) = wl-rtl8712u-3.0.21-tinycore.tcz (r8712u), firmware.tcz (rtlwifi/rtl8712u.bin)
Notes = WPS (not tested)
-
Vinnie, just place the details here in this thread and I'll update the wiki thank you. But looks like you got it, thanks for the contribution ;D
Good job Vinnie
oops, I'd misunderstood
PCI ID = 168c:002b
that's right? :P
-
No problem thanks :)
-
Hi coreplayer2
To check for firmware requests, one could use something like:
dmesg | grep -B 2 -A 5 -i firmwareThis will print out every line containing the word firmware plus the two lines leading up to and the five lines
right after it.
On the footnotes in the Wiki, might I suggest the following:
1. Change LSUSB and LSPCI to lowercase because Linux is case sensitive, and to be newbie friendly.
2. Change note 1 to Use "lsusb" from command line (no quotes)
3. Change references for note 2 to 1
4. Change note 2 to Use "lspci -nn" from command line (no quotes)
5. Change references for notes 5 and 6 to 2 (removing notes 5 and 6)
6. Change references for note 7 to 3
7. Change references for note 8 to 4
Notes 1 and 2 basically provide the same information and are redundant.
Same goes for 5 and 6. lspci -nn provides all the information that lspci does plus a little more.
-
Thanks, well I've found that a driver calls for firmware by name which has never included the word firmware. usually the line will read something like driver_name is opening generic_related_file_name etc etc so is not consistent.
So far in my search have had to look for lines in dmesg with the expected file name and hope it leads to cfg8011 or a firmware file which normally ends in .bin, but not all drivers have firmware as such these days?
Thanks for the case sensitive suggestion, I hear you about the redundancy but without it the column header will not give any clue how to get that info so I included it anyhow..
8)
-
Hi coreplayer2
I'm afraid the only sample of a dmesg firmware request I had was for a sound card, and the message included the
phrase "firmware: requesting". This was under TC3.4 and the filename rquested ended in ".fw". Maybe the following
would be better:
dmesg | grep -B 2 -A 5 -i '.bin'
dmesg | grep -B 2 -A 5 -i '.fw'
-
Wireless NIC Chip = Broadcom Corporation BCM4312
USB ID =
PCI ID = 14e4:4315
OEM & Model as tested = Dell Latitude D430, Dell wireless mini-PCI 1395
HW rev = rev 01
Interface = PCI
WLAN standard [802.11] = 802.11b/g
Frequency Band = 2.4GHz
Security (1) = WPA2
Tested with kernel = 3.0.21-tinycore
Tested with Wifi.tcz = N
Required Extensions (2) = wpa_supplicant, user supplied firmware
Notes
Requires Broadcom firmware, see http://linuxwireless.org/en/users/Drivers/b43#Device_firmware_installation
b43-phy0: Broadcom 4312 WLAN found (core revision 15)
Broadcom 43xx driver loaded [ Features: PMNL, Firmware-ID: FW13 ]
b43-phy0: Loading firmware version 508.1084 (2009-01-14 01:32:01)
Will also work with wl-modules-3.0.21-tinycore or ndiswrapper-modules-3.0.21-tinycore (with bcmwl5.{inf,sys}) using boot codes blacklist=bcma blacklist=b43 blacklist=ssb
Edit: I confirm this will work with wifi.tcz as long as the user supplied firmware is loaded first
-
Thanks you Juanito, am all over this.. :)
-
Juanito am curious, will these extensions work (albeit perhaps not as efficiently) with your BCM4312 device??
wl-modules-3.0.21-tinycore &
firmware-broadcom.tcz
or
Am I correct in saying there is a supported driver in 3.0.21-tinycore? If so will it function with firmware-broadcom.tcz ?
or
is the only method available for this specific device to download the firmware from the link provided..?
Just curious..?
Thanks again for the info, have added the data
-
what firmware I'm using? ???
tc@box:~$ dmesg | grep -B 2 -A 5 -i firmware
PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
PCI: Using MMCONFIG for extended config space
[Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
ACPI: EC: GPE = 0x1c, I/O: command/status = 0x66, data = 0x62
ACPI: No dock devices found.
HEST: Table not found.
PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
tc@box:~$ dmesg | grep -B 2 -A 5 -i '.bin'
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
UDP hash table entries: 512 (order: 2, 16384 bytes)
UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
tc@box:~$ dmesg | grep -B 2 -A 5 -i '.fw'
asus_wmi: Unknown symbol pci_hp_deregister (err 0)
asus_wmi: Unknown symbol __pci_hp_register (err 0)
Synaptics Touchpad, model: 1, fw: 7.2, id: 0x1c0b1, caps: 0xd04733/0xa40000/0xa0000
usb 2-2: new low speed USB device number 2 using uhci_hcd
input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input6
input: Microsoft Microsoft�� Comfort Mouse 4500 as /devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.0/input/input7
generic-usb 0003:045E:076C.0001: input: USB HID v1.11 Mouse [Microsoft Microsoft�� Comfort Mouse 4500] on usb-0000:00:1d.0-2/input0
usb 3-1: new low speed USB device number 2 using uhci_hcd
tc@box:~$
-
..will these extensions work (albeit perhaps not as efficiently) with your BCM4312 device??
wl-modules-3.0.21-tinycore &
firmware-broadcom.tcz
wl-modules-3.0.21-tinycore will work without any additional firmware as long as the boot codes blacklist=bcma blacklist=b43 blacklist=ssb are used. Note that you will need "sudo modprobe wl" as it will not be automatically loaded.
firmware-broadcom will not work with this hardware
is the only method available for this specific device to download the firmware from the link provided..?
To work with the b43 module from wireless-3.0.21-tinycore, yes. It is not required for wl-modules-3.0.21-tinycore (the wl module provides the firmware) or ndiswrapper-modules-3.0.21-tinycore (the windows driver provides the firmware).
-
Wireless NIC Chip = Broadcom Corporation BCM4331
USB ID =
PCI ID = 14e4:4331
OEM & Model as tested = Apple Inc. Macmini5,3
HW rev = rev 02
Interface = PCI
WLAN standard [802.11] = 802.11a/b/g/n
Frequency Band = 2.4 & 5GHz
Security (1) = WPA2
Tested with kernel = 3.0.21-tinycore64
Tested with Wifi.tcz = N
Required Extensions (2) = wpa_supplicant, user supplied firmware, compat-wireless-3.2.5-1
Notes
Requires Broadcom firmware, see http://linuxwireless.org/en/users/Drivers/b43#Device_firmware_installation
b43-phy0: Broadcom 4331 WLAN found (core revision 29)
Broadcom 43xx driver loaded [ Features: PMNLS ]
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
Requires compat-wireless-3.2.5-1, see http://linuxwireless.org/en/users/Download/stable/#compat-wireless_3.2_stable_releases
Will not work with wl-modules-3.0.21-tinycore, broadcom's driver <cough> does not support this hardware
Will not work with ndiswrapper-modules-3.0.21-tinycore, the windows driver requires a more recent version of ndis than that supplied by ndiswrapper
I am not sure if 802.11a or n or dual simultaneous n is supported by this version of compat-wireless - in any case, my wireless ap does not support 802.11a or dual simultaneous n
-
Hi coreplayer2
Looks like I provided some inadequate commands (again) , the grep syntax I provided ignores punctuation.
One more time
dmesg | grep -B 2 -A 5 -Fi '.bin'
dmesg | grep -B 2 -A 5 -Fi '.fw' This of course presumes that the system knows to request FILENAME.bin before a firmware extension has been
installed. A sample dmesg line when firmware is missing might be helpful, without that I'm just grepping at straws.
The Wiki page is coming together nicely by the way.
@vinnie: Not all cards require or use firmware.
-
Rich, how about using an extended RE (http://linux.die.net/abs-guide/x15066.html#EXTREGEX) to merge your two fixed string matches into a single command:
dmesg | grep -B 2 -A 5 -iE '\.(bin|fw)'
Please note that it uses '\.' to match the dot character, which is not an extended RE but rather part of the (standard) RE specifications.
-
...
@vinnie: Not all cards require or use firmware.
then the package wireless-3.0.21-tinycore is useless in my case?
p.s. I added the new kernel version for my card in the table
-
Vinnie, why don't you post the last 50 or so lines from the dmesg log then maybe we can tell. Which extensions did you install to get wireless up and running?
-
Hi maro
Thanks. I don't spend enough time on the command line to be proficient with the fancy stuff, so I usually take a
simplistic approach. Lucky for me, you saw what I wrote, shook your head, and suggested a better way. ;D
-
Thank you Juanito is posted :)
-
Vinnie, why don't you post the last 50 or so lines from the dmesg log then maybe we can tell. Which extensions did you install to get wireless up and running?
I can do better and even paste the entire dmesg! :P
-
just attaching it would be fine..
-
ah yes, true, I also had to link it!
sorry, I am a bit sleepy
http://sprunge.us/NJhI
-
Looking at:
ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
Registered led device: ath9k-phy0
ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xf8480000, irq=17
..and:wlan0: authenticate with 5c:da:d4:4f:8b:76 (try 1)
wlan0: authenticated
wlan0: associate with 5c:da:d4:4f:8b:76 (try 1)
wlan0: RX AssocResp from 5c:da:d4:4f:8b:76 (capab=0x411 status=0 aid=1)
wlan0: associated
..I'd say you didn't need any additional firmware for things to work
-
I'm lucky 8), but the package wireless-3.0.21-tinycore contains firmware of other card? is useless for me?
-
You'll still need wireless-3.0.21-tinycore for the modules to support your wireless driver. As far as I recall, it does not contain any firmware files.
If you enter "modinfo your_wifi_module_name", it's almost certain it will depend on one or more modules from wireless-3.0.21-tinycore
-
Vinnie according to your dmesg your wifi card "Atheros AR9285 Rev:2" needs at least "cfg80211" module which is in "wireless-3.0.xx-tinycore"
Thanks
-
Thanks to you!
-
Your welcome.
Also I like the command line paste bin "sprunge" how do you use it??
-
Your welcome.
Also I like the command line paste bin "sprunge" how do you use it??
Suggestion you take this to a thread in the "Off Topic" subforum ;)
-
Your welcome.
Also I like the command line paste bin "sprunge" how do you use it??
microOT, I promise :D
search on appbrowser sprunge_script and read with attention the info ^_^
-
See that's exactly what was asked thanks Vinnie for the heads up on the command line paste bin.. could come in handy here too ;)
Really was there any need for an off topic comment.. ???
-
Not having been aware of a respective extension, I was ready to post my own script for sprunge - but I would not do so in a thread and subforum where such would be totally off-topic.
NB: My own script which does the job for me is 54 bytes, I would find using an extension a bit disproportional.
-
That would be cool too, so please make a thread and link too it so we can find it thanks
-
Meanwhile anyone with wifi devices please post your spec as per the template here ;)
-
new USB Wifi device
Wireless NIC Chip = Atheros AR9271 Rev:1
USB ID = 0846:9030
PCI ID =
OEM & Model as tested = NetGear N 150 Wireless USB Adapter - WNA1100
HW rev =
Interface = USB
WLAN standard [802.11] = B/G/N
Frequency Band = 2.4GHz
Security = wpa
Tested with kernel = 3.0.21
Tested with Wifi.tcz = y
Required Extensions = wireless-3.0.21-tinycore.tcz + firmware.tcz
Notes =
driver - ath9k_htc
firmware - htc_9271.fw
Reliable, good performance
-
and another..
Wireless NIC Chip = Realtek Semiconductor Corp. RTL8188CUS
USB ID = 0bda:8176
PCI ID =
OEM & Model as tested = Sabrent Mini USB-A11N
HW rev =
Interface = USB 2.0
WLAN standard [802.11] = b/g/n
Frequency Band =
Security = WPA2
Tested with kernel = 3.0.21
Tested with Wifi.tcz = Y
Required Extensions = wireless-3.0.21-tinycore.tcz (rtl8192cu) + firmware.tcz (rtlwifi/rtl8192cufw.bin)
Notes =
-
One more..
Wireless NIC Chip = WNA3100M
USB ID = 0846:9021
PCI ID =
OEM & Model as tested = NetGear N300 Wireless Mini USB
HW rev =
Interface = USB 2.0
WLAN standard [802.11] = 802.11 b/g/n
Frequency Band = 2.4GHz
Security (1) = WPA/WPA2
Tested with kernel = 3.0.21-tinycore
Tested with Wifi.tcz = Y
Required Extensions = ndiswrapper
Notes = WPS (not tested)
While the wireless chip point towards RTL8192C there is no direct reference and rtl8192* + rtlwifi/rtl8192cufw.bin doesn't work with the device, additionally the USB listing for 0846:9021 is NetGear, Inc. (0846) : Device name unknown (9021)
driver in use with ndiswrapper is listed as netwna3100m
-
A Netgear G54/N150 Wireless USB Micro Adapter [Of all those tested this one is my favorite, really small and extremely reliable]
Wireless NIC Chip = RTL8188CUS
USB ID = 0846:9041
PCI ID =
OEM & Model as tested = NetGear WNA 1000M - (100ENS)
HW rev =
Interface = USB 2.0
WLAN standard [802.11] = 802.11 b/g/n
Frequency Band = 2.4GHz
Security = WPA/WPA2
Tested with kernel = 3.0.21-tinycore
Tested with Wifi.tcz = Y
Required Extensions = wireless-3.0.21-tinycore.tcz, firmware.tcz
Notes = WPS (not tested)
-
A Belkin product this time.. Basic, cheap, a little bulky, is reliable
A Belkin N150 Wireless USB Adapter
Wireless NIC Chip = RTL8188SU
USB ID = 050d:945a
PCI ID =
OEM & Model as tested = Belkin Components F7D1101 Basic Wireless USB Adapter v1000
HW rev =
Interface = USB 2.0
WLAN standard [802.11] = 802.11 b/g/n
Frequency Band = 2.4GHz
Security = WPA/WPA2
Tested with kernel = 3.0.21-tinycore
Tested with Wifi.tcz = Y
Required Extensions = wl-rtl8712u-3.0.21-tinycore.tcz (r8712u), firmware.tcz (rtlwifi/rtl8712u.bin)
Notes = WPS (not tested)
-
A Belkin N600 Wireless Dual Band USB Adapter
Wireless NIC Chip = Broadcom BCM4323
USB ID = 050d:615a
PCI ID =
OEM & Model as tested = Belkin Components F9L1101 Wireless Dual Band USB Adapter
HW rev =A02
Interface = USB 2.0
WLAN standard [802.11] = 802.11 a/b/g/n
Frequency Band = 2.4GHz
Security = WPA/WPA2
Tested with kernel = 3.0.21-tinycore
Tested with Wifi.tcz = Y
Required Extensions = ndiswrapper.tcz
Notes = WPS (not tested)
- Best Signal strength of all tested
- Up to 300mbps and 1400 feet range
- Used Blacklist boot codes for ssb, b43 and bcma during testing (eg: blacklist=bmca blacklist=b43 etc etc)
- A little bulky
-
[edit] Here's one that only works with the wl driver and only when wpa_supplicant is run in the foreground
Wireless NIC Chip = Broadcom Corporation BCM43228
USB ID =
PCI ID = 14e4:4359
OEM & Model as tested = Dell Wireless 1530 Wireless-N WLAN Mini-Card
HW rev = ??
Interface = PCI
WLAN standard [802.11] = 802.11a/b/g/n
Frequency Band = 2.4 & 5GHz
Security (1) = WPA2
Tested with kernel = 3.0.21-tinycore
Tested with Wifi.tcz = N
Required Extensions (2) =
Notes
As per http://linuxwireless.org/en/users/Drivers/b43: this hardware is not tested, but should work with the broadcom wl driver.
As per http://www.broadcom.com/support/802.11/linux_sta.php: These packages contain Broadcom's IEEE 802.11a/b/g/n hybrid Linux® device driver for use with Broadcom's BCM4311-, BCM4312-, BCM4313-, BCM4321-, BCM4322-, BCM43224-, and BCM43225-, BCM43227- and BCM43228-based hardware.
.and it looks like it should work: lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
wl 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
wl 0000:02:00.0: setting latency timer to 64
lib80211_crypt: registered algorithm 'TKIP'
eth1: Broadcom BCM4359 802.11 Hybrid Wireless Controller 5.100.82.112
lib80211_crypt: registered algorithm 'WEP'
lib80211_crypt: registered algorithm 'CCMP'..but it only seems to work with wpa_supplicant run in the foreground
..and with the latest ndiswrapper release candidate (which adds additional ndis commands required for this device) and the driver from here http://ftp1.us.dell.com/FOLDER00436179M/1/Network_Driver_PP4MX_WN_A02.EXE: ndiswrapper version 1.58rc1 loaded (smp=yes, preempt=no)
ndiswrapper: driver bcmwl5 (Broadcom,10/26/2011, 5.100.82.112) loaded
ndiswrapper 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
ndiswrapper 0000:02:00.0: setting latency timer to 64
ndiswrapper: using IRQ 17
wlan0: ethernet device 64:27:37:22:ab:51 using NDIS driver: bcmwl5, version: 0x5645270, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 14E4:4359.5.conf
wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2-PSK; AES/CCMP with WPA, WPA2, WPA2-PSK
usbcore: registered new interface driver ndiswrapper..it still doesn't work :(
-
While the Wiki was set up for known working devices, it might be worthwhile to list devices that
are known not to work.
-
I think it's equally important to indicate both those which are function and those not compatible. thanks for the info, am thinking we need another category in the wiki to show non compatible devices.
If Juanito can't get the device to function then there's not likely much chance of anyone getting it to perform, clearly valuable info.
Thanks
-
I looked at the Broadcom Corporation BCM43228 again.
This doesn't work: sudo wpa_supplicant -B -i eth1 -c/etc/wpa_configure.conf
sleep x
sudo udhcpc -b -i eth1 -h boxdell -p /var/run/udhcpc.eth1.pid..for any value of x I tried.
.and this clearly doesn't work: $ sudo wpa_supplicant -B -Dbroadcom -i eth1 -c/etc/wpa_configure.conf
Unsupported driver 'broadcom'.
$ sudo wpa_supplicant -B -Dndiswrapper -i wlan0 -c/etc/wpa_configure.conf
Unsupported driver 'ndiswrapper'
..but this does work: $ sudo wpa_supplicant -dd -i eth1 -c/etc/wpa_configure.conf
[from a different terminal window]
$ sudo udhcpc -b -i eth1 -h boxdell -p /var/run/udhcpc.eth1.pid..but only for the wl driver and not ndiswrapper
It doesn't seem logical that running wpa_supplicant in the foreground should change anything, but yet it does ???
I'll modify the original post.
-
So, after a great help from Rich, my contribution :
Wireless NIC Chip = RTL8192SU
USB ID = 07d1:3303
PCI ID =
OEM & Model as tested = D-Link DWA 131 802.11n Wireless N Nano Adapter
HW rev = A1
Interface = USB 2.0
WLAN standard [802.11] = 802.11 b/g/n
Frequency Band = 2.4GHz
Security = WPA/WPA2
Tested with kernel = 3.0.21-tinycore
Tested with Wifi.tcz = Y
Required Extensions = wl-rt8712u-3.0.21-tinycore, wireless-3.0.21-tinycore.tcz, firmware.tcz
Notes = WPS (not tested)
-
Wireless NIC Chip = Prism II
Hardware identity 801b:0000:0001:0000
Station identity 001f:0004:0001:0007
manfid = 0x02ac, 0x3021
OEM & Model as tested = "Siemens", "SpeedStream Wireless PCMCIA"
HW rev =
Interface = PCMCIA
WLAN standard [802.11] = 802.11 b
Frequency Band = 2.4GHz
Security (1) = WEP supported, 104-bit key
Tested with kernel = 2.6.29.1-tinycore & 3.0.21-tinycore
Tested with Wifi.tcz = untested
Required Extensions (2) = wireless-3.0.21-tinycore.tcz
Notes = Firmware determined as Intersil 1.7.4 (flashing firmware to recommended version may be of benefit)
-
I think it's equally important to indicate both those which are function and those not compatible. thanks for the info, am thinking we need another category in the wiki to show non compatible devices.
...and a category of only conditionally compatible, see e.g.
http://forum.tinycorelinux.net/index.php/topic,14081.msg79134.html#msg79134
-
Wireless NIC Chip = Ralink RT2500USB
USB ID = 13b1:000d
PCI ID =
OEM & Model as tested = Linksys WUSB54G v4 802.11g Adapter
HW rev =
Interface = USB 2.0
WLAN standard [802.11] = 802.11 b/g
Frequency Band = 2.4GHz
Security (1) = WPA/WPA2
Tested with kernel = 2.6.29.1-tinycore & 3.0.21-tinycore
Tested with Wifi.tcz = untested
Required Extensions (2) = wireless-3.0.21-tinycore.tcz
Notes =
-
IMHO, this list could be significantly improved by including:
- drivers and stacks tested
- modes tested and/or reported to be available
-
Thanks will update the list ASAP
Noted, yes I think we were going to provide a list of incompatible devices also. Will get right on that too
-
Wireless NIC Chip = Broadcom Corporation BCM43228
USB ID =
PCI ID = 14e4:4359
OEM & Model as tested = Dell Latitude E6220/Dell Wireless 1530 Half-size Mini PCIe Card
HW rev = n/a
Interface = PCI
WLAN standard [802.11] = 802.11a/b/g/n
Frequency Band = 2.4 & 5GHz
Security (1) = WPA2
Tested with kernel = 3.0.21-core/3.0.21-corepure64
Tested with Wifi.tcz = N
Required Extensions (2) = wpa_supplicant, wl-modules-KERNEL blacklist=ssb blacklist=bcma blacklist=b43
Notes
Will not work with b43, latest news is "not tested"
dmesg:
wl: Unknown symbol lib80211_get_crypto_ops (err 0)
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
wl 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
wl 0000:02:00.0: setting latency timer to 64
lib80211_crypt: registered algorithm 'TKIP'
lib80211_crypt: registered algorithm 'WEP'
lib80211_crypt: registered algorithm 'CCMP'
eth1: Broadcom BCM4359 802.11 Hybrid Wireless Controller 5.100.82.11
Will not work with ndiswrapper-modules-3.0.21-tinycore, the windows driver requires a more recent version of ndis than that supplied by ndiswrapper
I am not sure if 802.11a or n or dual simultaneous n is supported - in any case, my wireless ap does not support 802.11a or dual simultaneous n
The connection will not start at the first attempt, I'm obliged to do this: udhcpc (v1.20.2) started
Sending discover...
Sending discover...
Sending discover...
No lease, forking to background
$ ps aux | grep udhc
3268 root udhcpc -b -i eth1 -x hostname boxdell -p /var/run/udhcpc.eth1.pid
$ sudo kill 3268
$ sudo udhcpc -b -i eth1 -x hostname boxdell -p /var/run/udhcpc.eth1.pid
udhcpc (v1.20.2) started
Sending discover...
Sending select for 192.168.1.113...
Lease of 192.168.1.113 obtained, lease time 86400
deleting routers
route: SIOCDELRT: No such process
adding dns 213.42.20.20
adding dns 195.229.241.222 ..this is apparently a bug in the wl driver when used in "wext" mode
-
Hi,
I am a wireless novice being spoilt with ethernet so first had to stop wired
sudo modprobe -r 8139too
as I appear to have the same chipset as wiki entry 2, I first tried to connect without all of packages dmesg link
http://ompldr.org/vaTFxMQ/dmesg.txt
Feel free to let me know if I have done anything wrong, in future I plan to do this
tce-load -i wl-rtl8712u-3.0.21-tinycore firmware wifi
sudo modprobe -r 8139too
sudo ifconfig eth0 down
sudo wifi.sh
I may change that on reboot, anyhow
Wireless NIC Chip = Realtek Semiconductor Corp. RTL8191SU
USB ID = 0bda:8172
PCI ID =
OEM & Model as tested = no name, "Wireless USB Adaptor"
HW rev =
Interface = USB 2.0
WLAN standard [802.11] = 802.11 b/g/n
Frequency Band = 2.4GHz
Security (1) = 64or 128 WEP/ WPA/ WPA-PSK/ WPA2 / WPA2-PSK, TKIP/AE5
Tested with kernel = 3.0.21-tinycore
Tested with Wifi.tcz = Y
Required Extensions (2) = wl-rtl8712u-3.0.21-tinycore firmware wifi
Notes = No WPS button and not yet able to connect to wireless printer
will edit when I can figure out how to connect to wireless printer.
It cost about $12 with free postage and the other reason was the image said Linux --- from a well known auction site
(http://ompldr.org/vaTFxYg/006-2.JPG)
-
Wireless NIC Chip = Broadcom Corporation BCM43228
Update:
Tested with Wifi.tcz = Y
Required Extensions (2) = wpa_supplicant, wl-modules-KERNEL blacklist=ssb blacklist=bcma blacklist=b43
Notes
Will not work with b43, latest news is "not tested", does work (32bit and 64bit) with the latest ndiswrapper (1.58) and the windows xp drivers from the dell support site
-
Hi,
I am a wireless novice being spoilt with ethernet so first had to stop wired
sudo modprobe -r 8139too
as I appear to have the same chipset as wiki entry 2, I first tried to connect without all of packages dmesg link
http://ompldr.org/vaTFxMQ/dmesg.txt
Feel free to let me know if I have done anything wrong, in future I plan to do this
tce-load -i wl-rtl8712u-3.0.21-tinycore firmware wifi
sudo modprobe -r 8139too
sudo ifconfig eth0 down
sudo wifi.sh
I may change that on reboot, anyhow
Wireless NIC Chip = Realtek Semiconductor Corp. RTL8191SU
USB ID = 0bda:8172
PCI ID =
OEM & Model as tested = no name, "Wireless USB Adaptor"
HW rev =
Interface = USB 2.0
WLAN standard [802.11] = 802.11 b/g/n
Frequency Band = 2.4GHz
Security (1) = 64or 128 WEP/ WPA/ WPA-PSK/ WPA2 / WPA2-PSK, TKIP/AE5
Tested with kernel = 3.0.21-tinycore
Tested with Wifi.tcz = Y
Required Extensions (2) = wl-rtl8712u-3.0.21-tinycore firmware wifi
Notes = No WPS button and not yet able to connect to wireless printer
will edit when I can figure out how to connect to wireless printer.
Have you tried the driver for this device r8192u_usb ? wl-rtl8712u driver is for a different adapter
-
coreplayer2
so I don't detract from the theme of this post I have started a new thread in response to your request
http://forum.tinycorelinux.net/index.php/topic,15217.0.html
cheers
-
Wireless NIC Chip = RTL8187SE
PCI ID = 10ec:8199
OEM & Model as tested = Realtek Semiconductor Co., Ltd. RTL8187SE Wireless LAN Controller
Interface = PCI
WLAN standard [802.11] = 802.11 b/g
Frequency Band = 2.4GHz
Security (1) = WPA/WPA2
Tested with kernel = 2.6.29.1-tinycore
Tested with Wifi.tcz = Untested
Required Extensions (2) = rtl8187se_coffee.tcz (2.x)
-
Thanks tinypoodle
-
Wireless NIC Chip = Broadcom BCM4313
USB ID = n/a
PCI ID : 14e4:4727 I think (I am not sure what PCI ID is, here is the full line from lspci -nn just in case I messed up: 02:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
OEM & Model as tested = The one in a lenovo g580
HW rev = 01
Interface = mini pcie
WLAN standard [802.11] = n (didn't test anything else)
Frequency Band = 2.4GHz
Security (1) = only tested wpa2 personal
Tested with kernel = 3.0.21-tinycore
Tested with Wifi.tcz =y
Required Extensions (2) = I did it with coreplus and blacklisted ssb, bcm43legacy, and bcm. I didn't have to do anything other than blacklist those, after that it ran out of the box!
Is this thread still in use to update the wiki?
If I messed something up let me know, I'll give you more info.
-
Am going to have to add devices for tc-5 now :)
-
TC5 runs on my HP-G62 OK.
(Using ath9k module it would seem)
-
Thanks, but without the information requested at the beginning of this thread, that's not much use :)
-
Wireless NIC Chip = Intel Corporation Dual Band Wireless-AC 7260
USB ID =
PCI ID = 8086:08b1
OEM & Model as tested = Intel AC 7260
HW rev = 73
Interface = pcie
WLAN standard [802.11] = 802.11 a/b/g/n
Frequency Band = 2.4GHz & 5.0GHz
Security (1) = WPA2
Tested with kernel = 3.16.6-tinycore{,64}
Tested with Wifi.tcz = N
Required Extensions = firmware_iwlwifi-7260
Notes =
-
Wireless NIC Chip = Realtek Semiconductor RTL8191SEvA
USB ID =
PCI ID = 10ec:8171
OEM & Model as tested = Asus EeePC 1201N
HW rev = 10
Interface = PCI-Express
WLAN standard [802.11] = 802.11b/g/n
Frequency Band = 2.4GHz
Security = WPA/WPA2
Tested with kernel = 3.16.6-tinycore
Tested with Wifi.tcz = Y
Required Extensions = firmware-rtl8192ce_se_de.tcz, wireless-3.16.6-tinycore.tcz
Notes = http://forum.tinycorelinux.net/index.php/topic,19533.0.html
-
Hi
if you are still the maintainer of the wiki
Wireless NIC Chip = 8188eu (rtl8188eu)
USB ID =2357:010c
PCI ID =
OEM & Model as tested = TP-Link TL-WN722N v2
HW rev = 3
Interface = USB 2.0
WLAN standard [802.11] = 802.11 b/g/n
Frequency Band = 2.4GHz
Security (3) = WEP, WPA-PSK/WPA2-PSK
Tested with kernel = 4.14.10-tinycore64
Tested with Wifi.tcz = N....wicd used
Required Extensions (1) = 8188.tcz (included FW)
Notes = WPS (not tested)
-
I've finally managed to get working WiFi on the old laptop I mentioned on here some years back! I found an old Linksys PCMCIA card and tried that and it worked! I'd post the spec of it, but pccardctl claims it doesn't exist, despite it quite clearly working and lspcmcia only specifies the sockets. Tinycore version is 6.something, kernel is 3.16.6-tinycore.
If someone can give me some alternative commands to get info I'll post whatever I can find out.
-
Edimax Techonology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUs] (WPA-PSK / WPA1/WPA2)
tested with 4.19.81-piCore
By the way:
The link (list) of supported Wifi devices does not work for me.
-
Is anyone currently using a Netgear WNDA3100 v2 (USB wifi dongle with Broadcom BCM4323) with Core 14.x 32 bit?
I just acquired two of these in bunch of tech junk. They seem to be in working condition but I can't seem to actually get them working.
I found a relevant thread here:
https://forum.tinycorelinux.net/index.php/topic,12910.msg73169.html#msg73169 (https://forum.tinycorelinux.net/index.php/topic,12910.msg73169.html#msg73169)
but it's over ten years old and mentions ndiswrapper.tcz (which does not seem to be in the 14.x/x86/tcz repo).
lsusb shows the device as
Bus 003 Device 002: ID 0846:9011 NetGear, Inc. WNDA3100v2 802.11abgn [Broadcom BCM4323]
wireless-6.1.2-tinycore.tcz provides both
./usr/local/lib/modules/6.1.2-tinycore/kernel/drivers/net/wireless/broadcom/b43/b43.ko.gz
and
./usr/local/lib/modules/6.1.2-tinycore/kernel/drivers/net/wireless/broadcom/b43legacy/b43legacy.ko.gz
although neither of them gets loaded when the extension is loaded. Manually loading them with modprobe doesn't seem to help.
firmware-broadcom_bcm43xx.tcz seems like it should be relevant as well
wifi.sh (from wifi.tcz) reports "no wifi devices found".
I feel like the pieces are all there but maybe I'm doing something wrong or out of order.
-
Hi Leee
A search of the Internet suggests there is no kernel support
for that device and that ndiswrapper is required.
Even with ndiswrapper some people reported they could
not get the device to work. The suggestion to switch to
a supported device came up on several occasions.
-
Thanks Rich. I'll probably just relegate these to the "maybe Windows" heap. :)
-
Hello everyone!
I'm running 14.x x64 on an HP laptop (17-by0036nr (https://support.hp.com/in-en/document/c06177262)) and I randomly grabbed a few short USB dongles (under 1" long outside the USB port) from the office for wireless since the onboard wireless didn't seem to have TCL support. Wouldn't you know... they're all RTL8811 chips, even though three different brand names. (TP-Link and two generic/unbranded AC devices - what are the odds :) )
2357:011e TP-Link AC600 wirless Realtek RTL8811AU [Archer T2U Nano]
After a little research...
I have the kernel compiling for 6.1.2 and will be rolling up a RTL88xxAU driver here in a little while as the internal wifi chip (RTL8327) was deleted last year from the Realtek firmware for 14.x for some reason, so I have to rebuild the module anyway if I want to use this laptop for the project in question...
So, what's our take on non-kernel drivers such as this (https://github.com/morrownr/8821au-20210708)? Do we build extensions "as is" or simply not support them?
REF: HP:17-BY0036NR WIFI:TCL:RTL8723DE WIFI:TCL:RTL8811AU
-
I’d say build extensions as needed.
-
Yeah, external modules are fine as extensions (including binary drivers like Nvidia as long as their license allows).
-
I caution you on being a maintainer supporting Realtek product. I used to manage them for a different system, and it became unmanageable due to the constant state of flux with 3rd party repos (updating for newer kernels, or they stopped working). There is some kernel work trying to build a intree realtek kernel driver, but its support is very limited right now.
I think the simpler approach is to wiki how to build your own driver.
I found this to be the most complete information on what works for USB wifi.
https://github.com/morrownr/USB-WiFi/tree/main
PS. I build the 8812au driver for my own personal use.
-
@Paul_123: Maintaining anything third party tends to come with inherent hazards (ie: No good deed goes unpunished)
I was thinking more in the direction of an extension based on necessity here... and with 15.x being on the anvil as we speak, likely compiled for that era as well... build instructions and the likes included with a note in the .info "...if it doesn't work for you, here's how to build your own... G'luck!" by which time, for all we know, that vintage of RTLs could make it into the main-stream.
github:morrownr is actually where I was reading up on the RTL8821/11 and 8822/12 before reaching out
@curaga / @Juanito: Thanks!
Any time we create something on this end that originates in part or in whole elsewhere, I tend to copy the (C) and distribution terms verbatim; or at least provide a link of where to find the red-tape. Granted, sometimes "free to distribute" (CDDL) does not always mean "freely distribute" (GPL) so... either scrub the mission, or "...better to ask forgiveness..." when the grey area is too gray!
EDIT: Disregard everything... if I'm understanding correctly, 8821CE (PCIe) and AU (USB) are kernel supported in >= 6.3.x and our 14.x is running 6.1.2
Will know for certain here in a while -- will be downloading 6.6 and digging in.
PCIe... yes. USB... no. :-\
Well, at least my own build seems to be working nicely.
-
I caution you on being a maintainer supporting Realtek product. I used to manage them for a different system, and it became unmanageable due to the constant state of flux with 3rd party repos (updating for newer kernels, or they stopped working).
For the r8168 PCIe Ethernet driver I've found the patches that Debian publish for their corresponding r8168 driver package very handy to fix build problems with newer kernel versions.
-
@CNK: Yes, working up-stream occasionally has its advantages :)
Thankfully, the 8821/8822 chipset drivers compile without too much effort (mostly path related issues since placing the ko in /lib is where it wants to go, but most extension files are expected to live in /usr(/local/lib/modules/) plus the extension itself still needs a little TLC; I went to strip the resulting binary and it gained quite a bit of weight instead of losing it, so we'll be digging a little deeper there before submitting, but otherwise submitqc says it's happy.
-
Hi CentralWare
... (mostly path related issues since placing the ko in /lib is where it wants to go, but most extension files are expected to live in /usr(/local/lib/modules/) ...
You know those extension files can also be reached through:
/lib/modules/$KERNEL/kernel.tclocal/
-
@Rich: I was under the impression that all extension related content was expected to call /usr/local home and to avoid blending in with /var ?
-
Hi CentralWare
Sorry, my response was poorly worded.
Extension files go in /usr/local/lib/modules/$KERNEL/kernel/
However, the rootfs.gz includes a link to that location:
tc@E310:~$ readlink /lib/modules/4.19.10-tinycore/kernel.tclocal
/usr/local/lib/modules/4.19.10-tinycore/kernel/
tc@E310:~$
-
Hello Rich! Hope your day finds you well!
If you know the answer already, this would be useful to know...
/usr/local/lib/modules/4.19.10-tinycore/kernel/
(and the associated /lib/modules/KERNEL/kernel.tclocal if course)
If I were to call modprobe mydriver after placing mydriver.ko(.gz) in the above directory, does the kernel already know to look here or does the entire path need to be given?
(I'm assuming so, but it's better to ask ridiculous questions and hear someone in the background scoff "...duh!" as opposed to asking after the fact and being the one saying "(apply entire vulgar dictionary here)" for not asking in the first place.)
Thanks!
-
Hi CentralWare
Both modprobe and modinfo will find drivers without providing a path:
tc@E310:~$ sudo modprobe keyspan
tc@E310:~$ lsmod | grep keyspan
keyspan 20480 0
usbserial 20480 1 keyspan
ezusb 12288 1 keyspan
tc@E310:~$ sudo modprobe -r keyspan
tc@E310:~$ modinfo keyspan | grep filename:
filename: /lib/modules/4.19.10-tinycore/kernel.tclocal/drivers/usb/serial/keyspan.ko.gz
tc@E310:~$
-
Hi CentralWare
... If I were to call modprobe mydriver after placing mydriver.ko(.gz) in the above directory, ...
and then running:
sudo /sbin/depmod -a 2>/dev/null
If you use tce-load it will detect there are kernel modules
and run depmod automatically for you.
-
If you use tce-load it will detect there are kernel modules
and run depmod automatically for you.
Good to know; thanks!