Tiny Core Linux
Tiny Core Extensions => TCE Bugs => Topic started by: andfree on April 15, 2016, 01:14:36 PM
-
I want to connect to internet via a wifi adapter. I installed wicd and its icon has been created. But when I click on it, nothing happens. Nothing also happens when I run:
tc@box:~$ sudo wicd
-
Not enough information here to help you.
You may need to install the driver and firmware.
Show the output of 'lspci -nn'.
-
tc@box:~$ lspci -nn
/bin/sh: lspci: not found
tc@box:~$
-
Install it.
-
tc@box:~$ tce-load -iw lspci.tcz
Downloading: lspci.tcz
Connecting to distro.ibiblio.org (152.19.134.43:80)
wget: server returned error: HTTP/1.1 404 Not Found
md5sum: lspci.tcz.md5.txt: No such file or directory
Error on lspci.tcz
tc@box:~$
-
Use App's provides button to find the package that contains lspci.
-
These three are listed:
grub2-efi.tcz
grub2.tcz
pci-utils.tcz
-
I installed pci-utils.tcz. Afterwards:
tc@box:~$ lspci -nn
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD/ATI] RS200 Host Bridge [1002:cab2] (rev 02)
00:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RS200/RS250 AGP Bridge [1002:7010]
00:02.0 USB controller [0c03]: ULi Electronics Inc. USB 1.1 Controller [10b9:5237] (rev 03)
00:06.0 Multimedia audio controller [0401]: ULi Electronics Inc. M5451 PCI AC-Link Controller Audio Device [10b9:5451] (rev 02)
00:07.0 ISA bridge [0601]: ULi Electronics Inc. M1533/M1535/M1543 PCI to ISA Bridge [Aladdin IV/V/V+] [10b9:1533]
00:08.0 Modem [0703]: ULi Electronics Inc. M5457 AC'97 Modem Controller [10b9:5457]
00:0a.0 CardBus bridge [0607]: O2 Micro, Inc. OZ601/6912/711E0 CardBus/SmartCardBus Controller [1217:6972]
00:10.0 IDE interface [0101]: ULi Electronics Inc. M5229 IDE [10b9:5229] (rev c4)
00:11.0 Bridge [0680]: ULi Electronics Inc. M7101 Power Management Controller [PMU] [10b9:7101]
00:12.0 Ethernet controller [0200]: National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller [100b:0020]
01:05.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RS200M [Radeon IGP 330M/340M/345M/350M] [1002:4337]
tc@box:~$
-
I see no wifi controller there. Is it a USB controller?
If so you need to post the output of 'lsusb';
-
tc@box:~$ lsusb
Bus 001 Device 003: ID 0cf3:1002 Atheros Communications, Inc. TP-Link TL-WN821N v2 / TL-WN822N v1 802.11n [Atheros AR9170]
Bus 001 Device 002: ID 045e:007d Microsoft Corp. Notebook Optical Mouse
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
tc@box:~$
-
What does "ifconfig -a" show?
-
Probably missing firmware. Check dmesg.
-
tc@box:~$ ifconfig -a
dummy0 Link encap:Ethernet HWaddr 0e:01:e7:2d:47:98
BROADCAST NOARP 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:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
eth0 Link encap:Ethernet HWaddr 00:0b:cd:55:f5:f2
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2804 errors:0 dropped:11 overruns:0 frame:0
TX packets:2551 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3162832 (3.0 MiB) TX bytes:479111 (467.8 KiB)
ip_vti0 Link encap:IPIP Tunnel HWaddr
NOARP MTU:1364 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:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:200 (200.0 B) TX bytes:200 (200.0 B)
tunl0 Link encap:IPIP Tunnel HWaddr
NOARP MTU:1480 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:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
tc@box:~$
-
See the attachment.
-
I installed firmware.tcz. Now what? Wicd still doesn't start.
-
I don't see any drivers for the BCM5974.
-
As per https://wikidevi.com/wiki/List_of_Wi-Fi_Device_IDs_in_Linux
..you need the carl9170 driver, but as per the kernel config:
# CONFIG_CARL9170 is not set
-
I followed the link, downloaded the driver for TL-WN821N for linux, unzip it, opened it, and I see it's a blank file. Nothing written in it.
-
I believe you need to enable the carl9170 driver in the kernel config and compile it.
-
This means to edit /mnt/sda1/tce/boot/extlinux/extlinux.conf? It's like this:
DEFAULT core
LABEL core
KERNEL /tce/boot/vmlinuz
APPEND initrd=/tce/boot/core.gz quiet waitusb=5:UUID="b7c9ae56-0223-4d78-9cfb-9ece1ebe91e2" tce=UUID="b7c9ae56-0223-4d78-9cfb-9ece1ebe91e2" kmap=qwerty/gr lang=el_GR.UTF-8
How should it become?
-
No, it means that you will need to download the kernel source and kernel config from here:
http://repo.tinycorelinux.net/7.x/x86/release/src/kernel/
..enable the carl9170 driver as a module, recompile the kernel and make an extension containing the module.
-
carl9170-modules-4.2.9-tinycore extension posted - let me know if it works
BTW, it looks iffy: https://wireless.wiki.kernel.org/en/users/Drivers/carl9170
-
tc@box:~$ tce-load -iw carl9170-modules-4.2.9-tinycore.tcz
Downloading: carl9170-modules-4.2.9-tinycore.tcz
Connecting to distro.ibiblio.org (152.19.134.43:80)
wget: server returned error: HTTP/1.1 404 Not Found
md5sum: carl9170-modules-4.2.9-tinycore.tcz.md5.txt: No such file or directory
Error on carl9170-modules-4.2.9-tinycore.tcz
tc@box:~$
-
I don't know if this is more for support, but tplink have some drivers on there own site.
http://www.tp-link.com/res/down/soft/TL-WN821N_V4_150909.zip
It has a good doc inside the zip file(Installation for linux driver_RTL.pdf)
Some thing says to me there are some changes to the hardware between the hardware versions.
What i can see on there site, there are v5 v4 v3.
http://www.tp-link.se/download/TL-WN821N_V5.html
-
It probably didn't make it to the mirrors yet, download it from http://repo.tinycorelinux.net
-
I see it there at http://repo.tinycorelinux.net/7.x/x86/tcz/ (http://repo.tinycorelinux.net/7.x/x86/tcz/), but I don't see how to download it.
-
Either use the apps gui and the mirrors extension to change the download site or:
$ wget -c http://repo.tinycorelinux.net/7.x/x86/tcz/carl9170-modules-4.2.9-tinycore.tcz{,.dep,.md5.txt}
-
tc@box:~$ wget -c http://repo.tinycorelinux.net/7.x/x86/tcz/carl9170-modules-4.2
.9-tinycore.tcz{,.dep,.md5.txt}
Connecting to repo.tinycorelinux.net (89.22.99.37:80)
wget: server returned error: HTTP/1.1 404 Not Found
tc@box:~$
-
$ wget -c http://repo.tinycorelinux.net/7.x/x86/tcz/carl9170-modules-4.2.9-tinycore.tcz
$ wget -c http://repo.tinycorelinux.net/7.x/x86/tcz/carl9170-modules-4.2.9-tinycore.tcz.dep
$ wget -c http://repo.tinycorelinux.net/7.x/x86/tcz/carl9170-modules-4.2.9-tinycore.tcz.md5.txt
-
I don't know if this is more for support, but tplink have some drivers on there own site.
http://www.tp-link.com/res/down/soft/TL-WN821N_V4_150909.zip
It has a good doc inside the zip file(Installation for linux driver_RTL.pdf)
Some thing says to me there are some changes to the hardware between the hardware versions.
What i can see on there site, there are v5 v4 v3.
http://www.tp-link.se/download/TL-WN821N_V5.html
See what I wrote at Reply #17. That time I had downloaded v4 and now v5. But again, after unzip the file, I open it (with editor or leafpad) and it's blank. And there was not any doc inside the zip file.
-
tc@box:~$ wget -c http://repo.tinycorelinux.net/7.x/x86/tcz/carl9170-modules-4.2
.9-tinycore.tcz
Connecting to repo.tinycorelinux.net (89.22.99.37:80)
carl9170-modules-4.2 100% |*******************************| 36864 0:00:00 ETA
tc@box:~$ wget -c http://repo.tinycorelinux.net/7.x/x86/tcz/carl9170-modules-4.2
.9-tinycore.tcz.dep
Connecting to repo.tinycorelinux.net (89.22.99.37:80)
carl9170-modules-4.2 100% |*******************************| 33 0:00:00 ETA
tc@box:~$ wget -c http://repo.tinycorelinux.net/7.x/x86/tcz/carl9170-modules-4.2
.9-tinycore.tcz.md5.txt
Connecting to repo.tinycorelinux.net (89.22.99.37:80)
carl9170-modules-4.2 100% |*******************************| 70 0:00:00 ETA
tc@box:~$
Does this mean it has been installed? But:
tc@box:~$ carl9170-modules-4.2
/bin/sh: carl9170-modules-4.2: not found
tc@box:~$
-
No, it means it has been downloaded - now you need to copy the three files to your tce/optional folder and then load the extension with "tce-load -i carl9170-modules-KERNEL"
-
TL-WN821N_V4_150909.zip indeed fails to extract using unzip .
This works:
7z x TL-WN821N_V4_150909.zip
requires p7zip.tcz .
-
tc@box:~$ tce-load -i carl9170-modules-KERNEL
carl9170-modules-4.2.9-tinycore.tcz: OK
tc@box:~$
-
TL-WN821N_V4_150909.zip indeed fails to extract using unzip .
This works:
7z x TL-WN821N_V4_150909.zip
requires p7zip.tcz .
Indeed. Thanks.
I read at PDF:
System version: Ubuntu 14.04.1
Kernel version: 3.16.0-30-generic
Gcc version:4.8.2
This is not a problem?
-
Good - the extension is loaded.
You can check with "lsmod" if the carl9170 module loaded and, if not, load it with "sudo modprobe carl9170".
Once you've verified that the module is loaded, it would also be good to check with something like "dmesg | tail -20" that the carl9170 firmware also loaded.
Then you should be ready to try wicd again...
-
c@box:~$ lsmod
Module Size Used by Not tainted
speedstep_lib 12288 0
cpufreq_conservative 12288 0
cpufreq_stats 12288 0
cpufreq_powersave 12288 0
cpufreq_userspace 12288 0
ppdev 12288 0
squashfs 24576 149
lz4_decompress 12288 1 squashfs
parport_pc 24576 0
floppy 45056 0
pcspkr 12288 0
8250_fintek 12288 0
parport 28672 2 ppdev,parport_pc
video 20480 0
backlight 12288 1 video
natsemi 20480 0
loop 16384 298
battery 16384 0
ac 12288 0
acpi_cpufreq 12288 0
tc@box:~$ tce-load -i carl9170-modules-KERNEL
carl9170-modules-4.2.9-tinycore.tcz: OK
tc@box:~$ lsmod
Module Size Used by Not tainted
carl9170 57344 0
mac80211 221184 1 carl9170
ath 16384 1 carl9170
cfg80211 135168 3 carl9170,mac80211,ath
speedstep_lib 12288 0
cpufreq_conservative 12288 0
cpufreq_stats 12288 0
cpufreq_powersave 12288 0
cpufreq_userspace 12288 0
ppdev 12288 0
squashfs 24576 150
lz4_decompress 12288 1 squashfs
parport_pc 24576 0
floppy 45056 0
pcspkr 12288 0
8250_fintek 12288 0
parport 28672 2 ppdev,parport_pc
video 20480 0
backlight 12288 1 video
natsemi 20480 0
loop 16384 300
battery 16384 0
ac 12288 0
acpi_cpufreq 12288 0
tc@box:~$ dmesg | tail -20
random: nonblocking pool is initialized
eth0: DSPCFG accepted after 0 usec.
eth0: link up.
eth0: Setting full-duplex based on negotiated link capability.
mtrr: no MTRR for d8000000,3ff0000 found
usb 1-2: reset full-speed USB device number 3 using ohci-pci
usb 1-2: Direct firmware load for carl9170-1.fw failed with error -2
usb 1-2: Falling back to user helper
usbcore: registered new interface driver carl9170
usb 1-2: driver API: 1.9.7 2012-12-15 [1-1]
usb 1-2: firmware API: 1.9.6 2012-07-07
ath: EEPROM regdomain: 0x809c
ath: EEPROM indicates we should expect a country code
ath: doing EEPROM country->regdmn map search
ath: country maps to regdmn code: 0x52
ath: Country alpha2 being used: CN
ath: Regpair used: 0x52
ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
input: phy0 WPS Button as /devices/pci0000:00/0000:00:02.0/usb1/1-2/1-2:1.0/ieee80211/phy0/input9
usb 1-2: Atheros AR9170 is registered as 'phy0'
tc@box:~$
wicd still doesn't work. This line is the cause?
usb 1-2: Direct firmware load for carl9170-1.fw failed with error -2
-
Did you copy the dep file, carl9170-modules-4.2.9-tinycore.tcz.dep, to your tce/optional folder?
This should have loaded the firmware extension that contains carl9170-1.fw.
Also, it's worth checking in dmesg to see if carl9170-1.fw is mentioned twice - the second mention would be to confirm that it has been successfully loaded.
Edit: an example of what I mean, but with intel wifi hardware: $ dmesg
...
iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7260-15.ucode failed with error -2
iwlwifi 0000:02:00.0: Falling back to user helper
iwlwifi 0000:02:00.0: loaded firmware version 15.227938.0 op_mode iwlmvm
iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144
-
Did you copy the dep file, carl9170-modules-4.2.9-tinycore.tcz.dep, to your tce/optional folder?
Yes, and it's still there.
Also, it's worth checking in dmesg to see if carl9170-1.fw is mentioned twice - the second mention would be to confirm that it has been successfully loaded.
It's mentioned once and this to say that the load failed:
usb 1-2: Direct firmware load for carl9170-1.fw failed with error -2
I see that the carl9170-modules-4.2.9-tinycore extension is now there at "Apps -> Cloud -> Browse" list, but I can't add it to the onboot list.
-
Hmm - /usr/local/lib/firmware/carl9170-1.fw is present in the firmware extension - could you double-check that it is loaded using "tce-status -i | grep firmware"?
'Strange that you cannot add carl9170-modules-4.2.9-tinycore onboot using the apps gui - you could always edit tce/onboot.lst manually, but that's not the point.
-
tc@box:~$ tce-status -i | grep firmware
firmware
firmware-iwlwifi
tc@box:~$
-
You don't need firmware-iwlwifi, but I don't think that's the cause of the problem.
Maybe you could reboot with nothing loaded onboot and then try "tce-load -i carl9170-modules-4.2.9-tinycore" and check dmesg to see if the firmware loaded.
If that doesn't work, about the only thing I can think of is to try the firmware from https://github.com/chunkeey/carl9170fw
Apparently, you should see something like this: [14402.310944] usb 1-1.2: new high-speed USB device number 9 using dwc_otg
[14402.459068] usb 1-1.2: New USB device found, idVendor=0cf3, idProduct=1002
[14402.459096] usb 1-1.2: New USB device strings: Mfr=16, Product=32, SerialNumber=48
[14402.459114] usb 1-1.2: Product: USB2.0 WLAN
[14402.459129] usb 1-1.2: Manufacturer: ATHER
[14402.459145] usb 1-1.2: SerialNumber: 12345
[14402.560962] usb 1-1.2: reset high-speed USB device number 9 using dwc_otg
[14402.698503] usb 1-1.2: driver API: 1.9.7 2012-12-15 [1-1]
[14402.698543] usb 1-1.2: firmware API: 1.9.6 2012-07-07
[14403.050326] ath: EEPROM regdomain: 0x809c
[14403.050351] ath: EEPROM indicates we should expect a country code
[14403.050365] ath: doing EEPROM country->regdmn map search
[14403.050377] ath: country maps to regdmn code: 0x52
[14403.050390] ath: Country alpha2 being used: CN
[14403.050401] ath: Regpair used: 0x52
[14403.080221] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
[14403.084478] cfg80211: Calling CRDA to update world regulatory domain
[14403.099237] input: phy1 WPS Button as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.0/ieee80211/phy1/input2
[14403.099912] usb 1-1.2: Atheros AR9170 is registered as 'phy1'
[14403.559455] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
-
Maybe you could reboot with nothing loaded onboot and then try "tce-load -i carl9170-modules-4.2.9-tinycore" and check dmesg to see if the firmware loaded.
$ tce-load -i carl9170-modules-4.2.9-tinycore
firmware.tcz not found!
The bad news is that I deleted all extensions from onboot list and now I can't run x:
$ startx
-sh: startx: not found
I tried:
tce-load -iw Xvesa Xprogs flwm aterm wbartce-load -iw Xorg-7.7
Everything seems to be already downloaded.
-
If everything is already downloaded, you just need "tce-load -i Xvesa Xprogs flwm aterm wbar" to get a gui with "startx".
It looks like you need to download the firmware extension with "tce-load -w firmware" and then try to load the carl9170-modules-4.2.9-tinycore extension again.
-
If everything is already downloaded, you just need "tce-load -i Xvesa Xprogs flwm aterm wbar" to get a gui with "startx".
After "startx", I get this in green letters:
Tiny Core Linux - Xvesa Resolution Setup
1. 320x200x15
2. 320x200x16
3. 320x200x24
4. 320x200x24
5. 320x240x15
6. 320x240x16
7. 320x240x24
8. 320x240x24
9. 320x240x8
10. 400x300x15
11. 400x300x16
12. 400x300x24
13. 400x300x24
14. 512x384x15
15. 512x384x16
Enter selection ( 1 - 37 ) or (q)uit, (n)ext, (p)revious: :
-
Were you at the console prompt or in a terminal window in a gui?
Usually you need to enter "xsetup.sh" to get that message.
-
At the console prompt. I can't get in a gui.
-
You can choose your displays native resolution and your mouse type and then see if the gui starts.
-
I didn't know my displays native resolution and thought to try them one by one. I chose the first one, and now the gui is a small rectangular at the center of the screen (all the other is black). I tried to reboot, but after "startx" I got to the same gui, without being asked again about resolution. Then I opened a terminal and tried "xsetup.sh", but there is not much space for the display and I can't see the cursor. I typed in blind "15" and pressed enter and it went to the next question (about mouse setup). But this time I try to type "1" (for usb mouse) and press enter, but nothing happens. In conclusion, I don't know how to correct the resolution setup.
-
Maybe the best would be to reboot, load Xorg-7.7 flwm aterm and wbar and then startx.
Otherwise, you could google for your display native resolution and use Xvesa.
BTW, if you change xsetup.sh from inside a gui, you need to exit to the console and startx again for the changes to take effect.
-
Maybe the best would be to reboot, load Xorg-7.7 flwm aterm and wbar and then startx.
It worked. Thanks.
It looks like you need to download the firmware extension with "tce-load -w firmware" and then try to load the carl9170-modules-4.2.9-tinycore extension again.
$ tce-load -w firmware
firmware is already downloaded.
Then, "Download + Load" carl9170-modules-4.2.9-tinycore.tcz and wicd.tcz from Apps -> Cloud -> Browse.
After all:
$ sudo wicd
sudo: wicd: command not found
-
OK, but did you check dmesg to see if the carl9170 driver loaded and that it loaded the carl9170-1.fw firmware?
Take a look at the wicd info file, you need: $ sudo /usr/local/etc/init.d/dbus start
$ sudo /usr/local/etc/init.d/wicd start
$ wicd-gtk --no-tray
-
OK, but did you check dmesg to see if the carl9170 driver loaded and that it loaded the carl9170-1.fw firmware?
I see none of them at dmesg.
$ sudo /usr/local/etc/init.d/dbus start
sudo: /usr/local/etc/init.d/dbus: command not found
$ sudo /usr/local/etc/init.d/wicd start
sudo: /usr/local/etc/init.d/wicd: command not found
$ wicd-gtk --no-tray
sh: wicd-gtk: not found
-
Did you load the wicd extension?
-
$ tce-load -w wicd.tcz
wicd is already downloaded.
-
tce-load -w ...
Downloads extensions
tce-load -i ...
Installs already downloaded extensons
tce-load -wi ...
Downloads and installs extensions; Only works if not already downloaded.
-
tce-load -w ...
Downloads extensions
tce-load -i ...
Installs already downloaded extensons
tce-load -wi ...
Downloads and installs extensions; Only works if not already downloaded.
Thanks a lot.
tc@box:~$ tce-load -i firmware
firmware.tcz: OK
tc@box:~$ tce-load -i carl9170-modules-4.2.9-tinycore.tcz
wireless-4.2.9-tinycore.tcz not found!
tc@box:~$ tce-load -wi carl9170-modules-4.2.9-tinycore.tcz
carl9170-modules-4.2.9-tinycore is already downloaded.
tc@box:~$ tce-load -i carl9170-modules-4.2.9-tinycore.tcz
wireless-4.2.9-tinycore.tcz not found!
-
carl9170-modules-4.2.9-tinycore.tcz depends on wireless-4.2.9-tinycore.tcz which you don't have because you downloaded carl9170...tcz manually, thus dependencies didn't get resolved.
If you see mesages like "wireless-4.2.9-tinycore.tcz not found!", just download it via
tce-load -w wireless-4.2.9-tinycore
and then try your previous command again.
tce-load -i carl9170-modules-4.2.9-tinycore
-
Thanks again.
tc@box:~$ tce-load -w wireless-4.2.9-tinycore
wireless-4.2.9-tinycore is already downloaded.
tc@box:~$ tce-load -i wireless-4.2.9-tinycore
wireless-4.2.9-tinycore.tcz: OK
tc@box:~$ tce-load -i carl9170-modules-4.2.9-tinycore
carl9170-modules-4.2.9-tinycore.tcz: OK
tc@box:~$ tce-load -i wicd
libffi5.tcz: OK
ncurses.tcz: OK
ncurses-utils.tcz: OK
net-tools.tcz: OK
dhcpcd.tcz: OK
libiw.tcz: OK
wireless_tools.tcz: OK
readline.tcz: OK
libnl.tcz: OK
wpa_supplicant-dbus.tcz: OK
gdbm.tcz: OK
bzip2-lib.tcz: OK
sqlite3.tcz: OK
python.tcz: OK
urwid.tcz: OK
dbus-python.tcz: OK
pycairo.tcz: OK
gobject-introspection.tcz: OK
pygobject.tcz: OK
pygtk.tcz: OK
wicd.tcz: OK
tc@box:~$ sudo wicd
tc@box:~$
Nothing again.
-
sudo wicd
just starts the daemon.
See extension info in Apps GUI or
http://tinycorelinux.net/7.x/x86/tcz/wicd.tcz.info
on how to use wicd properly on Core.
-
sudo wicd
just starts the daemon.
It should do so, but it does not. This is the problem.
-
Please read the info file.
-
Just to be clear:
For the carl9170 driver to work properly, the firmware and wireless-KERNEL extensions need to be loaded before the carl9170-modules-KERNEL extension is loaded.
This would normally be taken care of by the carl9170-modules-KERNEL dep file, but I am not sure that you have this file in your tce/optional folder.
For the wicd extension to work, both the dbus and wicd daemons need to be started and the carl9170-modules-KERNEL extension loaded before double-clicking on the wicd icon/running "wicd-gtk --no-tray".
-
I reboot and startx. Then:
tc@box:~$ tce-load -i firmware
firmware.tcz: OK
tc@box:~$ tce-load -i wireless-4.2.9-tinycore
wireless-4.2.9-tinycore.tcz: OK
tc@box:~$ tce-load -i carl9170-modules-4.2.9-tinycore
carl9170-modules-4.2.9-tinycore.tcz: OK
tc@box:~$ tce-load -i wicd
libffi5.tcz: OK
ncurses-utils.tcz: OK
net-tools.tcz: OK
dhcpcd.tcz: OK
libiw.tcz: OK
wireless_tools.tcz: OK
readline.tcz: OK
libnl.tcz: OK
wpa_supplicant-dbus.tcz: OK
gdbm.tcz: OK
bzip2-lib.tcz: OK
sqlite3.tcz: OK
python.tcz: OK
urwid.tcz: OK
dbus-python.tcz: OK
pycairo.tcz: OK
gobject-introspection.tcz: OK
pygobject.tcz: OK
pygtk.tcz: OK
wicd.tcz: OK
tc@box:~$ sudo /usr/local/etc/init.d/dbus start
tc@box:~$ sudo /usr/local/etc/init.d/wicd start
Starting wicd daemon
tc@box:~$ wicd-gtk --no-tray
The gui started, I connected to the wireless network, but the browser doesn't load pages. The light on the adapter has also been turned off.
-
I added to /opt/bootlocal.sh:
/usr/local/etc/init.d/dbus restart
/usr/local/etc/init.d/wicd start
I added to /opt/.filetool.lst:
usr/local/etc/wicd
var/lib/wicd/configurations
I added firmware, wireless-4.2.9-tinycore, carl9170-modules-4.2.9-tinycore & wicd extensions to onboot list.
I rebooted.
I started wicd daemon and conected to the wireless network. Again, firefox doesn't load pages and the light on the adapter has been turned off.
/mnt/sda1/tce/optional/carl9170-modules-4.2.9-tinycore.tcz.dep exists and its content is:
wireless-KERNEL.tcz
firmware.tcz
Note that wireless-KERNEL.tcz is written this way and not wireless-4.2.9-tinycore.tcz.
-
Note that wireless-KERNEL.tcz is written this way and not wireless-4.2.9-tinycore.tcz.
That is correct - try entering the command "echo $KERNEL"
I presume wicd shows you a list of available wifi networks, that you chose one of them, entered the password and it appeared to connect?
Do you see any error messages in dmesg (you can see the last 20 lines, for example, by using "dmesg | tail -20")?
-
Note that wireless-KERNEL.tcz is written this way and not wireless-4.2.9-tinycore.tcz.
That is correct - try entering the command "echo $KERNEL"
Where? I tried it to the terminal, but nothing happened.
I presume wicd shows you a list of available wifi networks, that you chose one of them, entered the password and it appeared to connect?
Exactly. But it doesn't load pages, although it appears to be connected. On the other hand, wired network appears disconnected, but it loads pages.
Do you see any error messages in dmesg (you can see the last 20 lines, for example, by using "dmesg | tail -20")?
tc@box:~$ dmesg | tail -20
input: phy0 WPS Button as /devices/pci0000:00/0000:00:02.0/usb1/1-2/1-2:1.0/ieee80211/phy0/input9
usb 1-2: Atheros AR9170 is registered as 'phy0'
eth0: DSPCFG accepted after 0 usec.
eth0: link up.
eth0: Setting full-duplex based on negotiated link capability.
mtrr: no MTRR for d8000000,3ff0000 found
wlan0: authenticate with dc:02:8e:7f:4e:df
wlan0: send auth to dc:02:8e:7f:4e:df (try 1/3)
wlan0: authenticated
wlan0: associate with dc:02:8e:7f:4e:df (try 1/3)
wlan0: RX AssocResp from dc:02:8e:7f:4e:df (capab=0x431 status=0 aid=1)
wlan0: associated
eth0: Autonegotiation advertising 0x5e1 partner 0x00.
eth0: link down.
eth0: Autonegotiation advertising 0x5e1 partner 0x45e1.
eth0: link up.
eth0: Autonegotiation advertising 0x5e1 partner 0x00.
eth0: link down.
eth0: Autonegotiation advertising 0x5e1 partner 0x45e1.
eth0: link up.
tc@box:~$
-
dmesg looks OK in terms of your wifi connection - it might be better to test your wifi connection without the wired cable connection plugged in just to sure it is working.
You could also try: $ sudo ifconfig eth0 down
$ sudo ifconfig wlan0 up..just to be sure you have only the wifi connection.
-
I plugged out ethernet cable every time I tested wifi connection, but these commands got the job done:
$ sudo ifconfig eth0 down
$ sudo ifconfig wlan0 up
This is my first post with wifi connection. Thanks a lot.
-
Great :)
BTW, I mislead you with "echo $KERNEL" - this will not work from a terminal window/console, but wireless-KERNEL.tcz is correct in the dep file.
You might want to check out the home grown wifi extension - it has a lot less deps than wicd.
-
You might want to check out the home grown wifi extension - it has a lot less deps than wicd.
This also works, although the first time I lost connection suddenly. After rebooting seems to work fine. Thanks again.
-
Take care not to load both the wifi and wicd extensions - wifi uses wpa_supplicant and wicd uses wpa_supplicant-dbus, which cannot both be loaded at the same time.
-
It seems that this was the problem.
I deleted from /opt/bootlocal.sh these lines:
/usr/local/etc/init.d/dbus restart
/usr/local/etc/init.d/wicd start
I deleted from /opt/.filetool.lst these lines:
usr/local/etc/wicd
var/lib/wicd/configurations
I deleted wicd extension from onboot list.
I rebooted.
Wifi extension seems to work without problem now.