Tiny Core Linux
General TC => Tiny Core Netbooks => Topic started by: RYTCL on November 24, 2020, 07:41:19 PM
-
I need help in setup / configuration of WiFi on my HP Laptop
Here is the list of Extensions that are loaded at BOOT time
SDA9:/tce/onboot.lst
jwm-full.tcz
Xorg-7.7.tcz
rxvt.tcz
wbar.tcz
xf86-input-synaptics.tcz
firefox-ESR.tcz
wifi.tcz
WiFi ICON shows up. Clicking, brings up a blank window & dies after a min or so.
Any WiFi SETUP Guide, I could follow
-
I have tried adding the following WiFi firmware extensions 1 at a time, rebooting every time.
WiFi FirmWare
- firmware-iwlwifi.tcz
- firmware-ralinkwifi.tcz
- firmware-rtlwifi.tcz
Ran Command : "sudo wifi.sh" for each firmware after bootup.
System Response : "No WiFi devices detected"
-
Note that firmware-*.tcz needs to be loaded before wifi.tcz can be loaded.
Edit your onboot.lst
jwm-full.tcz
Xorg-7.7.tcz
rxvt.tcz
wbar.tcz
xf86-input-synaptics.tcz
firefox-ESR.tcz
...
firmware-iwlwifi.tcz
firmware-ralinkwifi.tcz
firmware-rtlwifi.tcz
wifi.tcz
...
Reboot your machine and try again later.
If wifi still doesn't work, try the following:
Execute the following code on your terminal
tce-load -wil firmware-iwlwifi
tce-load -wil firmware-ralinkwifi
tce-load -wil firmware-rtlwifi
tce-load -wil wifi
tce-load -wil wpa_supplicant-dbus
tce-load -wil libnl
tce-load -wil dbus
tce-load -wil expat2
tce-load -wil elogind
tce-load -wil acl
tce-load -wil attr
tce-load -wil libcap
tce-load -wil openssl-1.1.1
tce-load -wil readline
tce-load -wil ncursesw
tce-load -wil wireless_tools
tce-load -wil wireless-5.4.3-tinycore64
tce-load -wil libiw
First remove wifi and firmware-* from your onboot.lst, then reboot your machine and execute the following code
tce-load -i firmware-iwlwifi wifi
tce-load -i firmware-ralinkwifi
tce-load -i firmware-rtlwifi
sudo wifi.sh
-
You don't mention what wifi hardware you have.
Most, if not all, wifi hardware will try to load firmware under linux - if the hardware does not find the correct firmware, it will not work.
You can find which firmware your hardware is trying to load by looking at dmesg - you should see something analogous to this: $ dmesg | tail -10
...
cfg80211: failed to load regulatory.db
Intel(R) Wireless WiFi driver for Linux
Copyright(c) 2003- 2015 Intel Corporation
iwlwifi 0000:02:00.0: enabling device (0000 -> 0002)
iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7260-17.ucode failed with error -2
iwlwifi 0000:02:00.0: Falling back to sysfs fallback for: iwlwifi-7260-17.ucode
iwlwifi 0000:02:00.0: loaded firmware version 17.459231.0 op_mode iwlmvm
iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144
iwlwifi 0000:02:00.0: base HW address: a0:a8:cd:2c:3e:13..where, in this example, the firmware is iwlwifi-7260-17.ucode.
Once you know which firmware extension you need, it must be loaded before the wifi extension.
-
..where, in this example, the firmware is iwlwifi-7260-17.ucode.
I wonder if firmware and driver are the same concept on Linux? Is all the files under firmware-*.tcz necessary for every computer, or is it just a file that suits firmware?
-
Usually just one or two files from the firmware extension
-
Usually just one or two files from the firmware extension
Is the same for other firmware? Like a graphic card, a sound card? Do I just need a few files to get my graphics and sound card to work?
-
Hi ONE
... Execute the following code on your terminal
tce-load -wil firmware-iwlwifi
tce-load -wil firmware-ralinkwifi
tce-load -wil firmware-rtlwifi
tce-load -wil wifi
tce-load -wil wpa_supplicant-dbus
tce-load -wil libnl
tce-load -wil dbus
tce-load -wil expat2
tce-load -wil elogind
tce-load -wil acl
tce-load -wil attr
tce-load -wil libcap
tce-load -wil openssl-1.1.1
tce-load -wil readline
tce-load -wil ncursesw
tce-load -wil wireless_tools
tce-load -wil wireless-5.4.3-tinycore64
tce-load -wil libiw
...
No. Everything listed after wifi will be included automatically. All you need is:
tce-load -wil firmware-iwlwifi
tce-load -wil firmware-ralinkwifi
tce-load -wil firmware-rtlwifi
tce-load -wil wifi
-
Hi ONE
Yes, the same applies to graphics and sound cards.
-
A few graphics cards need firmware - I haven’t heard of any sound cards that need it.
-
I updated onboot.lst and did a reboot. Cannot identify any information related to wifi in dmesg.log
ONBOOT.LST
SDA9: /tce/onboot.lst
jwm-full.tcz
Xorg-7.7.tcz
rxvt.tcz
wbar.tcz
xf86-input-synaptics.tcz
firefox-ESR.tcz
firmware-iwlwifi.tcz
firmware-ralinkwifi.tcz
firmware-rtlwifi.tcz
wifi.tcz
I do run Ubuntu 20.04 and also Windows.10 on different partitions on the same laptop
O/S : Ubuntu 20.04 :
$> lspci
00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e)
00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e)
00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 0e)
00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e)
00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e)
00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e)
00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e)
00:1c.1 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 2 (rev 0e)
00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 (rev 0e)
00:1c.3 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 4 (rev 0e)
00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e)
00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0e)
02:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
02:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI Express Fast Ethernet controller (rev 07)
Windows 10 - System Information
Name [00000001] Ralink RT3290 802.11bgn Wi-Fi Adapter
Adapter Type Ethernet 802.3
Product Type Ralink RT3290 802.11bgn Wi-Fi Adapter
Installed Yes
I have also included the complete DMESG log.
It looks like WiFi module is " Ralink corp. RT3290 Wireless 802.11n ".
How do I check if module RT3290 is loaded on TinyCore.
-
I haven’t heard of any sound cards that need it.
？？？Doesn't ALSA include sound card firmware?
Don't need to install sound card drivers or firmware on Linux?
-
Hi RYTCL
It appears your wired connection requires firmware:
r8169 0000:04:00.0: Direct firmware load for rtl_nic/rtl8106e-1.fw failed with error -2
r8169 0000:04:00.0: Falling back to sysfs fallback for: rtl_nic/rtl8106e-1.fw
r8169 0000:04:00.0: Unable to load firmware rtl_nic/rtl8106e-1.fw (-11)That would be in firmware-rtl_nic.tcz.
I don't see the RT3290 being detected in your dmesg listing.
-
Hi RYTCL
Maybe run this on your Ubuntu setup and attach it to your next post:
dmesg > dmesg-ubuntu.txt
-
I am including the DMESG log attachment from Ubuntu.
-
Ubuntu - nmcli - command-line tool for controlling NetworkManager
$> nmcli
wlp2s0f0: connected to A.RY.NETGEAR.2.4G
"Ralink RT3290 1T/1R"
wifi (rt2800pci), 74:29:AF:24:3B:87, hw, mtu 1500
ip4 default
inet4 192.168.1.44/24
route4 0.0.0.0/0
route4 192.168.1.0/24
route4 169.254.0.0/16
inet6 fe80::a3ae:9f16:ce63:de6/64
route6 fe80::/64
route6 ff00::/8
enp4s0: unavailable
"Realtek RTL810xE"
ethernet (r8169), 38:63:BB:E6:A7:E0, hw, mtu 1500
lo: unmanaged
"lo"
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
DNS configuration:
servers: 192.168.1.1
domains: RRR
interface: wlp2s0f0
-
The firmware-ralinkwifi extension provides rt3290.bin, which I would guess is the firmware for your device.
Try this after reboot: $ tce-load -i firmware-ralinkwifi wifi
$ dmesg | tail -20..and check if you see a message about loading firmware.
If not, try this: $ sudo rfkill list all
-
1) Removed all WiFI Firmware.TCZ & WiFi.tcz from the onboot and rebooted the machine.
2) Installed rfkill.tcz through $> tce-ab
3) captured dmesg into a log file
$> dmesg > dmesg.1
4) Load extensions
$> tce-load -i firmware-ralinkwifi.tcz wifi.tcz
5) captured dmesg into a log file
$> dmesg > dmesg.2
6) DMESG analysis - no new lines added after installing extensions
7) Run RFKILL
$> sudo rfill list all
No output
I have the showapps pause bootcodes in my Grub Menu.
I see the following error message immediately after listing all the extensions:
udevd[183] : unknown key 'RUN{program}' in /etc/udev/rules.d/73-seat-late.rules:17
Is it possible to see the boot messages in some log file once the GUI window manager shows up ?
-
Hi RYTCL
... I see the following error message immediately after listing all the extensions:
udevd[183] : unknown key 'RUN{program}' in /etc/udev/rules.d/73-seat-late.rules:17 ...
I just fixed that. Update your system and it will go away:
tce-audit builddb
tce-audit updatedeps
tce-audit fetchmissing
tce-update
Then click the Exit icon and select reboot.
-
Hi RYTCL
... I see the following error message immediately after listing all the extensions:
udevd[183] : unknown key 'RUN{program}' in /etc/udev/rules.d/73-seat-late.rules:17 ...
I just fixed that. Update your system and it will go away:
tce-audit builddb
tce-audit updatedeps
tce-audit fetchmissing
tce-update
Then click the Exit icon and select reboot.
Error message disappeared. Thanks.... 8)
-
Does "lsmod" show if the driver for your wifi hardware (rt2800pci?) was loaded?
-
Here is the lsmod output
/$> lsmod
Module Size Used by Not tainted
cpufreq_conservative 12288 0
cpufreq_powersave 12288 0
cpufreq_userspace 12288 0
squashfs 32768 0
zstd_decompress 65536 1 squashfs
hp_wmi 12288 0
pcspkr 12288 0
wmi_bmof 12288 0
video 32768 0
backlight 12288 1 video
rtsx_pci_sdmmc 16384 0
wmi 16384 2 hp_wmi,wmi_bmof
mmc_core 73728 1 rtsx_pci_sdmmc
rtsx_pci_ms 12288 0
memstick 12288 1 rtsx_pci_ms
mei_hdcp 12288 0
battery 16384 0
realtek 16384 0
rtsx_pci 36864 2 rtsx_pci_sdmmc,rtsx_pci_ms
intel_vbtn 12288 0
sparse_keymap 12288 2 hp_wmi,intel_vbtn
ac 12288 0
loop 20480 0
r8169 57344 0
xhci_pci 12288 0
xhci_hcd 94208 1 xhci_pci
hp_wireless 12288 0
lpc_ich 20480 0
mei_txe 16384 1
mei 40960 3 mei_hdcp,mei_txe
-
There do not appear to be any wifi drivers loaded.
You can verify that the wireless-KERNEL extension is loaded with: $ tce-status -i | grep wireless
If wireless-KERNEL is loaded, you can try this: $ sudo modprobe rt2800pci..and then check lsmod and dmesg
-
Hi Juanito
I found this in his Ubuntu dmesg:
tc@box:~$ grep -E "wlp2s0f0|rt2|80211|02:00.0" .opera-11/temporary_downloads/dmesg.ubuntu
[ 1.135971] pci 0000:02:00.0: [1814:3290] type 00 class 0x028000
[ 1.136005] pci 0000:02:00.0: reg 0x10: [mem 0x90710000-0x9071ffff]
[ 1.136140] pci 0000:02:00.0: PME# supported from D0 D3hot
[ 4.956207] systemd[1]: unit_file_build_name_map: normal unit file: /lib/systemd/system/wpa_supplicant-nl80211@.service
[ 7.049144] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 7.052037] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 7.236988] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3290, rev 0015 detected
[ 7.245501] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 3290 detected
[ 7.245561] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 7.720001] rt2800pci 0000:02:00.0 wlp2s0f0: renamed from wlan0
[ 11.789939] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin'
[ 11.792261] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37
[ 13.310515] wlp2s0f0: authenticate with 50:6a:03:ba:48:fb
[ 13.312530] wlp2s0f0: send auth to 50:6a:03:ba:48:fb (try 1/3)
[ 13.314619] wlp2s0f0: authenticated
[ 13.315821] wlp2s0f0: associate with 50:6a:03:ba:48:fb (try 1/3)
[ 13.319281] wlp2s0f0: RX AssocResp from 50:6a:03:ba:48:fb (capab=0x1411 status=0 aid=7)
[ 13.319371] wlp2s0f0: associated
[ 13.375871] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0f0: link becomes ready
tc@box:~$
The Tinycore dmesg stops after the first 3 lines.
-
There do not appear to be any wifi drivers loaded.
You can verify that the wireless-KERNEL extension is loaded with: $ tce-status -i | grep wireless
If wireless-KERNEL is loaded, you can try this: $ sudo modprobe rt2800pci..and then check lsmod and dmesg
It looks like WIRELESS-KERNEL is not loaded.
]~> tce-status -i | grep wire
wireless-5.4.3-tinycore64
wireless_tools
~>
~> tce-status -i | grep ral
firmware-ralinkwifi
-
wireless-KERNEL=wireless-5.4.3-tinycore64
Did you try "sudo modprobe rt2800pci"?
-
$> sudo modprobe rtl2800pci
no output
Is there a wireless-kernel.tcz module - I could not find one in 11.1 64 bit TCZ folder
-
After "sudo modprobe rtl2800pci" you need to look at "lsmod" and "dmesg"
-
I do see some rt2800 lines in LSMOD, but no new messages in DMESG. dmesg.3 attachment included...
Is RT2800, the equivalent driver for RaLink RT3290 card for my laptop ?
~> lsmod
Module Size Used by Not tainted
rt2800pci 12288 0
rt2800mmio 12288 1 rt2800pci
rt2800lib 86016 2 rt2800pci,rt2800mmio
rt2x00mmio 12288 2 rt2800pci,rt2800mmio
rt2x00pci 12288 1 rt2800pci
rt2x00lib 28672 5 rt2800pci,rt2800mmio,rt2800lib,rt2x00mmio,rt2x00pci
mac80211 274432 3 rt2800lib,rt2x00pci,rt2x00lib
cfg80211 208896 2 rt2x00lib,mac80211
eeprom_93cx6 12288 1 rt2800pci
cpufreq_userspace 12288 0
cpufreq_conservative 12288 0
cpufreq_powersave 12288 0
squashfs 32768 0
zstd_decompress 65536 1 squashfs
wmi_bmof 12288 0
rtsx_pci_ms 12288 0
mei_hdcp 12288 0
hp_wmi 12288 0
memstick 12288 1 rtsx_pci_ms
rtsx_pci_sdmmc 16384 0
mmc_core 73728 1 rtsx_pci_sdmmc
realtek 16384 0
r8169 57344 0
video 32768 0
backlight 12288 1 video
battery 16384 0
lpc_ich 20480 0
pcspkr 12288 0
xhci_pci 12288 0
xhci_hcd 94208 1 xhci_pci
ac 12288 0
wmi 16384 2 wmi_bmof,hp_wmi
mei_txe 16384 1
mei 40960 3 mei_hdcp,mei_txe
rtsx_pci 36864 2 rtsx_pci_ms,rtsx_pci_sdmmc
intel_vbtn 12288 0
sparse_keymap 12288 2 hp_wmi,intel_vbtn
loop 20480 0
hp_wireless 12288 0
-
Hi RYTCL
When extensions have the text KERNEL as part of their name, KERNEL is a symbol representing the kernel version you are
currently running. When tce-load encounters the KERNEL symbol, it replaces it with the output of this command:
uname -rwhich in your case would return 5.4.3-tinycore64. So wireless-KERNEL.tcz becomes wireless-5.4.3-tinycore64.tcz
-
Hi RYTCL
When extensions have the text KERNEL as part of their name, KERNEL is a symbol representing the kernel version you are
currently running. When tce-load encounters the KERNEL symbol, it replaces it with the output of this command:
uname -rwhich in your case would return 5.4.3-tinycore64. So wireless-KERNEL.tcz becomes wireless-5.4.3-tinycore64.tcz
Thanks for that useful information.
-
Is RT2800, the equivalent driver for RaLink RT3290 card for my laptop ?
I believe so - do the following give any output?
$ dmesg | grep 2800
$ sudo rfkill list all
$ sudo wifi.sh
-
Issue persists...
~>
~> dmesg | grep 2800
last_pfn = 0x280000 max_arch_pfn = 0x400000000
pci 0000:02:00.0: [1814:3290] type 00 class 0x028000
~>
~>
~> sudo rfkill list all
~>
~> sudo wifi.sh
No wifi devices found!
~>
~>
-
A different question :
Terminal Window when launched does not source .profile. I normally have to source the profile every time a new window is launched.
$> . ./.profiile
How to force Term Win to source .profile ?
-
It seems as though something is blocking your wifi, but I don’t know what..
-
LSMOD shows hp_wireless in both Ubuntu and TinyCore . Does this mean anything ?
/mnt/sda9/log> grep wire lsmod*
lsmod.tinycore:hp_wireless 12288 0
lsmod.ubuntu:hp_wireless 16384 0
-
As per google that might be blocking your wifi - you could try rebooting, then “sudo modprobe -r hp_wireless” (you might need to use hp-wireless) and then load the firmware and wifi extensions.
-
The 3290 seems to be one of the experimental-marked drivers, and is disabled in our kernel.
-
looks like we have reached an impasse.
I don't mind trying hp_wireless experimental driver. Is it possible to extract just the driver from Ubuntu or Puppy Linux and try it out here.
-
No, it’ll need to be compiled.
-
Hi RYTCL
looks like we have reached an impasse. ...
For wireless, yes. If you want to get the wired connection up, it wants firmware-rtl_nic.tcz. The r8169 driver is include
in the base install.
-
Wired Ethernet is working currently without additional firmware.
It will be nice to get rid of this ERROR message in the DMESG log
r8169 0000:04:00.0: Direct firmware load for rtl_nic/rtl8106e-1.fw failed with error -2
r8169 0000:04:00.0: Falling back to sysfs fallback for: rtl_nic/rtl8106e-1.fw
r8169 0000:04:00.0: Unable to load firmware rtl_nic/rtl8106e-1.fw (-11)
-
Hi RYTCL
Did you install firmware-rtl_nic.tcz? It provides rtl8106e-1.fw.
-
Installed firmware-rtl_nic.tcz & rebooted...
onboot.lst
/mnt/sda9/tce> cat onboot.lst
firmware-rtl_nic.tcz
firmware-ralinkwifi.tcz
wifi.tcz
rfkill.tcz
jwm-full.tcz
Xorg-7.7.tcz
rxvt.tcz
wbar.tcz
xf86-input-synaptics.tcz
firefox-ESR.tcz
dmesg :
r8169 0000:04:00.0: Direct firmware load for rtl_nic/rtl8106e-1.fw failed with error -2
r8169 0000:04:00.0: Falling back to sysfs fallback for: rtl_nic/rtl8106e-1.fw
Generic PHY r8169-400:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-400:00, irq=IGNORE)
r8169 0000:04:00.0 eth0: Link is Down
r8169 0000:04:00.0 eth0: Link is Up - 100Mbps/Full - flow control rx/tx
2 ERROR lines related to rtl_nic persists. 'unable to load firmware' error has disappeared.
Wired Ethernet did work even without including the firmware - RTL_NIC
dmesg.tinycore - attachment included.
-
Here is an interesting article on how to enable WiFi support on HP Laptop for Ubuntu.
Fix ‘No WiFi Adapter Found’ for HP Laptops with Ubuntu 18.04
http://ubuntuhandbook.org/index.php/2018/08/no-wifi-adapter-found-hp-laptops-ubuntu-18-04/
(http://ubuntuhandbook.org/index.php/2018/08/no-wifi-adapter-found-hp-laptops-ubuntu-18-04/)
Blacklist BROADCOM drivers
6. If that does not work, you may remove and blacklist the broadcom drivers and restart:
sudo apt purge bcmwl-kernel-source
sudo sed -i '/blacklist bcma/ d' /etc/modprobe.d/blacklist.conf
sudo sed -i '/blacklist brcmsmac/ d' /etc/modprobe.d/blacklist.conf
In addition, (thanks to jeremy31) if you notice weak signal try command:
sudo modprobe -r rtl8723de && sleep 5 && sudo modprobe rtl8723de ant_sel=1
May be some other driver(s) are conflicting with my WiFi card "Ralink RT3290 - rt2800pci "
My limited skills does not permit me to make that judgement call... :)
-
I booted into UBUNTU and here is the network related information
lshw -C network
/root # lshw -C network
*-network
description: Wireless interface
product: RT3290 Wireless 802.11n 1T/1R PCIe
vendor: Ralink corp.
physical id: 0
bus info: pci@0000:02:00.0
logical name: wlp2s0f0
version: 00
serial: 74:29:af:24:3b:87
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=rt2800pci driverversion=5.4.0-53-generic firmware=0.37 ip=192.168.1.44 latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: irq:17 memory:90710000-9071ffff
*-network
description: Ethernet interface
product: RTL810xE PCI Express Fast Ethernet controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:04:00.0
logical name: enp4s0
version: 07
serial: 38:63:bb:e6:a7:e0
size: 100Mbit/s
capacity: 100Mbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8106e-1_0.0.1 06/29/12 ip=192.168.1.43 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s
resources: irq:19 ioport:1000(size=256) memory:90500000-90500fff memory:90400000-90403fff
It clearly shows rt2800pci is the correct driver and not hp_wireless.
-
Hi RYTCL
... 2 ERROR lines related to rtl_nic persists. ...
You can ignore them. It just means it didn't find the firmware in the first place it looked.
... 'unable to load firmware' error has disappeared. ...
That means it found the firmware.
... May be some other driver(s) are conflicting with my WiFi card "Ralink RT3290 - rt2800pci " ...
No.
... It clearly shows rt2800pci is the correct driver ...
That only tells half of the story. Here's part of the config file for our kernel:
CONFIG_RT2800PCI=m
CONFIG_RT2800PCI_RT33XX=y
# CONFIG_RT2800PCI_RT35XX is not set
# CONFIG_RT2800PCI_RT53XX is not set
# CONFIG_RT2800PCI_RT3290 is not setIt shows:
1. The rt2800pci was compiled as a loadable module.
2. The rt2800pci has rt33xx chipset support compiled in.
3. The rt2800pci does not have rt35xx chipset support compiled in.
4. The rt2800pci does not have rt53xx chipset support compiled in.
5. The rt2800pci does not have rt3290 chipset support compiled in.
The only way to fix that is to reconfigure and recompile the kernel and recompile the driver.
-
That's unfortunate - it means that you would need to replace the rt2800pci driver in the wireless-KERNEL extension rather than creating an additional extension.
-
Thank you Rich, Juanito, Curaga and everyone trying to help.
Does this mean, WiFi support for my laptop hardware may be in a future release.
I do have development experience in my past life (10+ years ago). I will be available, if I could be of any help.
-
You would need to do something like this:
$ tce-load -i compiletc ncursesw-dev elfutils-dev bc perl5
$ wget http://tinycorelinux.net/11.x/x86_64/release/src/kernel/linux-5.4.3-patched.txz
$ wget http://tinycorelinux.net/11.x/x86_64/release/src/kernel/config-5.4.3-tinycore64
$ tar xf linux-5.4.3-patched.txz
$ cd linux-5.4.3
$ make mrproper
$ cp ../config-5.4.3-tinycore64 ./.config
$ make oldconfig
$ make menuconfig
Device Drivers -->
Network device support -->
Wireless LAN -->
Ralink driver support -->
[*] rt2800pci - Include support for rt3290 devices (EXPERIMENTAL)
$ make modules
..and then over-write the rt2800pci.ko driver in wireless-5.4.3-tinycore64.tcz with the one compiled above.
-
btw - the rt3290 support is still experimental in the 5.10.x kernel, which is likely to be our next one.
-
I will work on compiling the driver. Should I start a new thread for this driver build.
-
Hi RYTCL
No, just continue it here so the problem and solution are in one place.
-
Driver build - I am at the last step. " $ make modules "
Questions
1. Is there a Command to rebuild / update wireless-5.4.3-tinycore64.tcz. Will the current build process result in .tcz file ?
..and then over-write the rt2800pci.ko driver in wireless-5.4.3-tinycore64.tcz with the one compiled
2. Is there a command to list all the files in the new TCZ package to confirm RT3290 files are present ?
-
APPS Gui has the ability to display all the files contained in a package.
Apps -> Cloud (Remote) -> Browse :: Choose Package : Files TAB on the right lists all the files
In my case, kernel.tcz will be a local file. I am not sure, how to get APPS Gui to browse local folders. Is there a Command line equivalent for TCZ Package File listing.
-
Hi RYTCL
... 1. Is there a Command to rebuild / update wireless-5.4.3-tinycore64.tcz. Will the current build process result in .tcz file ?
..and then over-write the rt2800pci.ko driver in wireless-5.4.3-tinycore64.tcz with the one compiled ...
There's a script that is used to sort and package all of the kernel modules. I'll get you a list of instructions.
... 2. Is there a command to list all the files in the new TCZ package to confirm RT3290 files are present ?
unsquashfs -ll ExtensionName.tcz
-
Hi RYTCL
OK, here you go:
# Place the modules somewhere for packaging.
mkdir -p ~/tmp/package/modules/usr/local
make INSTALL_MOD_PATH=/home/tc/tmp/package/modules/usr/local modules_install
cd ~/tmp/package/
# I like to keep the mod.alias, mod.builtin, mod.dep, mod.order, and mod.symbols files.
mv modules/usr/local/lib/modules/4.19.10-tinycore64/modules.* .
# Remove the 2 links in modules/usr/local/lib/modules/4.19.10-tinycore64/
rm modules/usr/local/lib/modules/4.19.10-tinycore64/build
rm modules/usr/local/lib/modules/4.19.10-tinycore64/source
# Set up sorter.sh to package all the modules.
cd ..
mkdir sorter
cd sorter
tce-load -i bash squashfs-tools zsync
wget https://github.com/tinycorelinux/sorter/archive/master.zip
unzip master.zip
cd sorter-master/
# This creates all of the Tinycore module packages and leaves them in the current directory.
./sorter.sh 4.19.10-tinycore64 /home/tc/tmp/package/modules
Copy the wireless-KERNEL.tcz file to your tce/optional directory. Delete the wireless-KERNEL.tcz.md5.txt file in your
tce/optional directory so that any future extension updates don't overwrite it with the version in the repo.
-
My DRIVER build directory : /home/tc/work/linux-5.4.3
ZERO errors uptil 'make modules'.
Did a reboot and ran the above command again to ensure all files were still there.
/work/linux-5.4.3> make INSTALL_MOD_PATH=/home/tc/tmp/package/modules/usr/local modules_install
cp: can't stat './modules.builtin.modinfo': No such file or directory
make: *** [Makefile:1319: _modinst_] Error 1
I ran a search 'find /home/tc -print | grep modules.builtin.modinfo' & could not locate one.
-
Hi RYTCL
If you go to /home/tc/tmp/package/modules/usr/local is it populated with subdirectories and .ko files?
-
~/tmp> find . -print | grep ko
no output.
> find /home/tc/tmp -print > /tmp/home.tc.tmp.dir
Attachment: home.tc.tmp.dir
-
I tried to upload Directory listing for /home/tc/work where driver module was built. GZipped file size was 526449 and is hitting the Forum post size limits.
I could take directory listing of one or more sub-directories, if that will help.
-
It stopped after creating some of the directories. No files were copied...
~> find /home/tc/tmp -print
/home/tc/tmp
/home/tc/tmp/package
/home/tc/tmp/package/modules
/home/tc/tmp/package/modules/usr
/home/tc/tmp/package/modules/usr/local
/home/tc/tmp/package/modules/usr/local/lib
/home/tc/tmp/package/modules/usr/local/lib/modules
/home/tc/tmp/package/modules/usr/local/lib/modules/5.4.3-tinycore64
/home/tc/tmp/package/modules/usr/local/lib/modules/5.4.3-tinycore64/source
/home/tc/tmp/package/modules/usr/local/lib/modules/5.4.3-tinycore64/kernel
/home/tc/tmp/package/modules/usr/local/lib/modules/5.4.3-tinycore64/modules.builtin
/home/tc/tmp/package/modules/usr/local/lib/modules/5.4.3-tinycore64/modules.order
/home/tc/tmp/package/modules/usr/local/lib/modules/5.4.3-tinycore64/build
-
Hi RYTCL
It's possible you need to compile the kernel in order for /modules.builtin.modinfo to be created. Run this:
make bzImageThen:
rm -rf /home/tc/tmpThen continue at reply #56.
-
After the 'make modules' step, I did force a manual BACKUP and did a reboot.
It looks like BACKUP skipped some of the files and/or folders.
Running 'make bzImage' now...
-
Driver build completed...
~/tmp/sorter/sorter-master> ll wireless-5.4.3-tinycore64.*
-rw-r--r-- 1 tc staff 62 Nov 26 22:09 wireless-5.4.3-tinycore64.moddeps
-rw-r--r-- 1 tc staff 4419584 Nov 26 22:09 wireless-5.4.3-tinycore64.tcz
-rw-r--r-- 1 tc staff 12833 Nov 26 22:09 wireless-5.4.3-tinycore64.tcz.list
-rw-r--r-- 1 tc staff 64 Nov 26 22:09 wireless-5.4.3-tinycore64.tcz.md5.txt
-rw-r--r-- 1 tc staff 13176 Nov 26 22:09 wireless-5.4.3-tinycore64.tcz.zsync
~/tmp/sorter/sorter-master> grep 28 wireless-5.4.3-tinycore64.tcz.list
./usr/local/lib/modules/5.4.3-tinycore64/kernel/drivers/net/wireless/ralink/rt2x00/rt2800lib.ko
./usr/local/lib/modules/5.4.3-tinycore64/kernel/drivers/net/wireless/ralink/rt2x00/rt2800mmio.ko
./usr/local/lib/modules/5.4.3-tinycore64/kernel/drivers/net/wireless/ralink/rt2x00/rt2800pci.ko
./usr/local/lib/modules/5.4.3-tinycore64/kernel/drivers/net/wireless/ralink/rt2x00/rt2800usb.ko
onboot.lst
/mnt/sda9/tce> cat onboot.lst
xf86-input-synaptics.tcz
Xorg-7.7.tcz
rxvt.tcz
wbar.tcz
firefox-ESR.tcz
icewm.tcz
icewm-themes.tcz
compiletc.tcz
ncursesw-dev.tcz
elfutils-dev.tcz
bc.tcz
perl5.tcz
squashfs-tools.tcz
icewm-list.tcz
icewm-help.tcz
icewm-locale.tcz
bash.tcz
zsync.tcz
wireless-5.4.3-tinycore64.tcz
firmware-rtl_nic.tcz
firmware-ralinkwifi.tcz
wifi.tcz
rfkill.tcz
Do I still need to include firmware-ralinkwifi.tcz in addition to wireless-5.4.3-tinycore64.tcz ?
Waiting for the BACKUP to be completed. I will reboot and test out WireLess...
-
Hi RYTCL
You could remove firmware-ralinkwifi.tcz from your onboot.lst if you don't want to load it.
-
WiFi card is detected. WiFi networking is not working...
Config info with Ethernet unplugged
~> ifconfig
eth0 Link encap:Ethernet HWaddr 38:63:BB:E6:A7:E0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wlan0 Link encap:Ethernet HWaddr 74:29:AF:24:3B:87
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
~> sudo rfkill list all
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
~>
~> iwconfig
wlan0 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry short long limit:2 RTS thr:off Fragment thr:off
Power Management:off
lo no wireless extensions.
tunl0 no wireless extensions.
dummy0 no wireless extensions.
ip_vti0 no wireless extensions.
eth0 no wireless extensions.
dmesg
random: crng init done
random: 6 urandom warning(s) missed due to ratelimiting
r8169 0000:04:00.0: Direct firmware load for rtl_nic/rtl8106e-1.fw failed with error -2
r8169 0000:04:00.0: Falling back to sysfs fallback for: rtl_nic/rtl8106e-1.fw
Generic PHY r8169-400:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-400:00, irq=IGNORE)
r8169 0000:04:00.0 eth0: Link is Down
ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin'
rt2800pci 0000:02:00.0: Direct firmware load for rt3290.bin failed with error -2
rt2800pci 0000:02:00.0: Falling back to sysfs fallback for: rt3290.bin
ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37
no MTRR for 80000000,3df0000 found
-
Hi RYTCL
OK, what happens if you run this:
sudo wifi.sh
-
Yaaaaay... Wireless is up & running.... :)
ifconfig
wlan0 Link encap:Ethernet HWaddr 74:29:AF:24:3B:87
inet addr:192.168.1.44 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1838 (1.7 KiB) TX bytes:2660 (2.5 KiB)
~> ping yahoo.com
PING yahoo.com (74.6.231.21): 56 data bytes
64 bytes from 74.6.231.21: seq=0 ttl=51 time=62.282 ms
64 bytes from 74.6.231.21: seq=1 ttl=51 time=62.151 ms
I had run 'wifi.sh' with Ethernet Cable plugged in. When I disconnected Ethernet to test out WiFi, it failed. Rebooting did not fix at that time.
Do I need to run wifi.sh after reboot every time ?
-
I did a reboot and WIFI was out again.
sudo wifi.sh and WIFI was up and running.
Is it possible to automate & add this to Boot Time Startup Scripts ?
-
Yes - see the wifi info file
-
Juanito - Thanks for pointing in the right direction.
Made changes to /opt/bootlocal.sh
#--- Added to automate WiFI Connection
/usr/local/bin/wifi.sh -a 2>&1 > /tmp/wifi.log
Now it connects to AP defined in /home/wifi.db file after reboot.
TinyCoreLinux is a nice distro. What makes it even more appealing is the people behind it. I am greatly thankful to everyone who made it possible to get TCL up & running on my laptop.