General TC > Tiny Core Netbooks
Dell Mini 9
Juanito:
Ah- so much for my memory, I see the problem now. The init.d script creates the missing directory, but the start-up script does not, which means if you load the extension and run the daemon manually it will fail.
It would have been smarter to do things differently - I'm traveling at the moment, but I'll have a look at this when I get back.
Thanks for the feedback.
Juanito:
updated acpid posted
h-munster:
--- Quote ---updated acpid posted
--- End quote ---
Thanks!
nick65go:
Hi,
Thank you very much for Tiny Core! I love it, I think this will be the future for linux distributions...
It boots up in 12 seconds, from grub menu until I can move the mouse pointer. My grub menu.lst
title Tiny Core Linux tce home opt
root (hd0,1)
kernel /tiny/bzImage ht=on hpet=disabled embed tce=hda2 home=hda2 opt=hda2 norestore noswap nodhcp max_loops=255 quiet
initrd /tiny/tinycore.gz
I use TC 2.7 on dell mini 910. In /tce I have only 915resolution.tcz, wl.tcz +depenencies.
All tcz updated are into /tce/optional. I use the new ondemand script for menu/mount them.
I can see wifi as eth1 in iwconfig and ifconfig, but I can not connect to essid with WEP/WPA.
cat /opt/wlan0.sh
#!/bin/sh
modprobe lib80211_crypt_tkip
modprobe lib80211_crypt_wep
modprobe lib80211_crypt_ccmp
modprobe wl
route add default gw 192.168.1.1
echo nameserver 213.154.124.1 > /etc/resolv.conf
echo nameserver 193.231.252.1 >> /etc/resolv.conf
pkill udhcpc
iwconfig eth1 essid qubs key restricted 1122334455
ifconfig eth1 192.168.1.105 netmask 255.255.255.0 broadcast 192.168.1.255 up
sudo iwlist txpower
eth1 2 available transmit-powers :
0 dBm (1 mW)
25 dBm (255 mW)
Current Tx-Power:32 dBm (1496 mW) ; hmm bugy
Also there are 11 chanels, not 13 when sudo iwlist channel.
I did not use yet wap_client or wpa_passphare...I would like to go with out it.
EDIT: solved buggy WL wireless driver. (In bootlocal.sh is nothing to run)
in the end of setup, eth0=wire and eth1=wireless
Initial lsmod shows that not all lib_cript_* are loaded, only tkip.
1. Initial sudo ifconfig do not show eth0 neither eth1. (Buggy, should show eth1, as WL is loaded)
2. Then sudo iwconfig trigger eth0 to show up, but not eth1. buggy aslo.
3. Now sudo ifconfig show up eth1 only.
4. Now sudo iwconfig show both eth0 and eth1 (not linked to ESSID).
We need something to arrive here quickly...
5. sudo /opt/wlan0.sh will associate with AP now.
I wait the new TC kernel, to eliminate broadcom proprietary wifi...
Thank you.
roberts:
Not sure of the point of having both wired eth0 and wireless eth1 both up at the same time on the same network.
I always boot my mini with nodhcp and wireless works as I posted in the first message (no scripts needed) in this topic. I am behind a firewall router.
Perhaps you need static IPs. Unless wireless is rarely used, I would have my wireless extensions in the tce directory not in tce/optional
Anyway, for kicks, I plugged in wired booted with the default dhcp request and had my wireless disabled. After boot with eth0 up. I see the same result as you for eth1. All trafic is on eth0 and my wireless access point is "Not-Associated".
But using one or the other works as expected.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version