Wifi Setup on a HP Laptop running TinyCore 11.1 (64 bit)

[RYTCL]

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.

[RYTCL]

It stopped after creating some of the directories.  No files were copied...

Code: [Select]

~> 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


[Rich]

Hi RYTCL
It's possible you need to compile the kernel in order for  /modules.builtin.modinfo  to be created. Run this:

Code: [Select]

make bzImageThen:

Code: [Select]

rm -rf /home/tc/tmpThen continue at reply #56.

[RYTCL]

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...

[RYTCL]

Driver build completed...

Code: [Select]

~/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

Code: [Select]

/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...

[Rich]

Hi RYTCL
You could remove  firmware-ralinkwifi.tcz  from your onboot.lst  if you don't want to load it.

[RYTCL]

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

[Rich]

Hi RYTCL
OK, what happens if you run this:

Code: [Select]

sudo wifi.sh

[RYTCL]

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 ?

[RYTCL]

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 ?

[Juanito]

Yes - see the wifi info file

[RYTCL]

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.