Talk:Tiny Core Linux: Difference between revisions

From OLPC
Jump to navigation Jump to search
m (fixed sig)
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=== Configure wireless ===
=== Configure wireless ===


A 1.5 here with firmware q3c16. No eth0 is evident.
An XO-1.5 here with firmware Q3C16. No eth0 is evident.


* scan for networks:
* scan for networks:
Line 18: Line 18:
:Yes, eth0 is no longer present in recent versions, you must identify the interface name using {{code|iw dev}}, and I've edited the page to show that. For all other network connection problems, refer to the Tiny Core Linux web sites, as we don't provide support for Tiny Core Linux here beyond that required for hardware compatibility. --[[User:Quozl|Quozl]] 23:09, 16 February 2014 (UTC)
:Yes, eth0 is no longer present in recent versions, you must identify the interface name using {{code|iw dev}}, and I've edited the page to show that. For all other network connection problems, refer to the Tiny Core Linux web sites, as we don't provide support for Tiny Core Linux here beyond that required for hardware compatibility. --[[User:Quozl|Quozl]] 23:09, 16 February 2014 (UTC)


== Configure DHCP ==
I have an old XO-1 and the instructions aren't working. I have a wlan0 interface, I set it to the SSID of my open wireless network, but when I run /etc/init.d/dhcp.sh it never seems to assign an IP.


I have an old XO-1 and the instructions aren't working. I have a wlan0 interface, I set it to the SSID of my open wireless network, but when I run /etc/init.d/dhcp.sh it never seems to assign an IP. Any ideas? --[[User:Lmsurpre|Lmsurpre]] 21:11, 29 March 2014 (UTC)
<blockquote>

> iwlist wlan0 scan | less
:Figured it out! dhcp.sh was only looking for devices like "eth." I modified this script to look for "wlan." instead and it worked like a charm. --[[User:Lmsurpre|Lmsurpre]] 21:27, 29 March 2014 (UTC)
...

Cell 05 - Address 00.23.69.8B:19:D6
::Even easier is to invoke udhcpc directly. Thanks, I didn't notice this problem because I build with the ''mktinycorexo --essid'' option, and this calls udhcpc. --[[User:Quozl|Quozl]] 23:17, 30 March 2014 (UTC)
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=70/70 Signal level=-40dBm
Encryption key:off
ESSID:"maximus"
Bit Rates:...
Bit Rates:...
Mode:Master
Extra:...
...
</blockquote>
<blockquote>
> iwconfig
lo no wireless extensions
wlan0 IEEE 802.11bg ESSID:"maximus"
Mode:Managed Frequency:2.462 GHz Access Point: 00:23:69:8B:19:D6
Bit Rate=5.5 Mb/s
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
Link Quality=59/70 Signal level=-51 dBm
Rx invalid nwide:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
...
</blockquote>
Any ideas?
--[[User:Lmsurpre|Lmsurpre]] 21:11, 29 March 2014 (UTC)

Latest revision as of 23:17, 30 March 2014

Configure wireless

An XO-1.5 here with firmware Q3C16. No eth0 is evident.

  • scan for networks:
iwlist scan | more
... lo ...
... wlan0 ...
  • associate with an open network:
#iwconfig eth0 essid network
iwconfig wlan0 essid linksys
... 
  • configure the interface using DHCP
/etc/init.d/dhcp.sh
  • Try to retrieve something.
lynx http://wiki.laptop.org/go/Tiny_Core_Linux
Unable to locate remote host wiki.laptop.org.
Yes, eth0 is no longer present in recent versions, you must identify the interface name using iw dev, and I've edited the page to show that. For all other network connection problems, refer to the Tiny Core Linux web sites, as we don't provide support for Tiny Core Linux here beyond that required for hardware compatibility. --Quozl 23:09, 16 February 2014 (UTC)

Configure DHCP

I have an old XO-1 and the instructions aren't working. I have a wlan0 interface, I set it to the SSID of my open wireless network, but when I run /etc/init.d/dhcp.sh it never seems to assign an IP. Any ideas? --Lmsurpre 21:11, 29 March 2014 (UTC)

Figured it out! dhcp.sh was only looking for devices like "eth." I modified this script to look for "wlan." instead and it worked like a charm. --Lmsurpre 21:27, 29 March 2014 (UTC)
Even easier is to invoke udhcpc directly. Thanks, I didn't notice this problem because I build with the mktinycorexo --essid option, and this calls udhcpc. --Quozl 23:17, 30 March 2014 (UTC)