Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: bigpcman on December 01, 2008, 09:23:36 AM
-
Great job guys on building the tinycore system. I have booted it up on my dell 640 laptop. Boots fast just as you described. After the boot completes there is no network connection. I'm connected to a typical router with dhcp turned on. What do I need to do to get the network connected? I've tried turning on the dhcp client in the control panel and a few other simple things.
bigpcman
-
Hi Bigpcman,
What kind of NIC do you have? On some of my PC's the drivers are not modprobed and I have to do it manually before I setup the network.
-
According to dmesg I have a "e100: Intel pro/ 100 driver 3.5.23 -k4 -NAPI" driver loaded but I think the dell 640 laptop actually uses a integrated 3com network device. I'll have to boot up another os to see for sure.
--------------------------
Ok, I have a 3com 3C920 integrated ethernet controller. Can Someone remind me how to load a driver for this device?
-
The name of your driver should be "3c59x", try loading it:
sudo modprobe 3c59x
-
That did it. Thanks.
-----------------------------------
How do I get this to happen on boot? Is there a boot code for this or do I have to remaster the iso?
-
You would add that (without sudo) to /opt/bootlocal.sh, which is by default included in your backup.
-
Great. I'm assuming if I only have ntfs hard drive file systems I would need to use a usb stick for backup. Is this correct?
-
Yes, or a floppy if you must :)
-
Similar problem of net card not detected. Dsl-N DMESG SHOWS
Linux Tulip driver version 1.1.13 (May 11, 2002)
tulip0: MII transceiver #1 config 3000 status 7829 advertising 01e1.
eth0: Lite-On 82c168 PNIC rev 32 at 0001d800, 00:A0:CC:D1:3D:1C, IRQ 9.
I tryed
sudo modprobe -v tulip
and it loads without error but cat /proc/interrupts doesn't show it. modinfo tulip just adds to my confusion. DSL DSL-N and Debian detect it. The computer is a Tiger GT200 200mhz, 186megs according to torsmo and 1 gig swap. I also have Debian on this box, maybe I should see what it says.
-
True. Not all hardware is auto detected. But again Tiny Core is not a turnkey system.
By using control panel and viewing tabs, typically dmesg, then modprobe, add to /opt/bootlocal.sh and away go you at full speed.
-
Re question on r4 :
Anyone who had their netcard module not autoload, does it do that now?
My dell 640 laptop now boots up with the 3c59x network driver loaded so I don't have to do a modprobe anymore. However, the network does not come up. Using netcardconf post boot and enabling (yes) for use dhcp broadcast then apply brings up the network interface. Netstat now reports active connection. If I go back to networkconf no ip address is shown and the dhcp broadcast is still set to no. The name servers are now filled in. Seems strange to me. Would it be better to default the system after boot to use dhcp?
---------
edit: Clicking on dhcp client in the control panel post boot also brings up the network interface. But netcardconf still does not display dhcp (yes) and the ip address is use. I suppose the default is always no dhcp and the ip field can only be used to enter a static ip address.
edit2: Does the dhcp client have to be on all the time or just until an ip address is obtained? Is the client required for automatic recovery of an ip address in the event the dhcp server is restarted?
-
It does, but we boot too fast for some cards :)
For now, add some wait with waitusb=5 and see if that is enough for your card.
-
OK, the delay fixed the problem, the network now comes up after boot.
-
to qwery how to work a atheros l2 fast ethernet of a asus eepc 4 gb ? its not recognised in boot ...
thanks
ps the asus have another wireless card atheros ar 5007eg
-
edit2: Does the dhcp client have to be on all the time or just until an ip address is obtained? Is the client required for automatic recovery of an ip address in the event the dhcp server is restarted?
sure, but it's not only that - it's usually for renewing when the ip lease expires. You can look up how dhcp works if you want more info.
kuky: are you using rc7? If so, please output the related parts of lspci -v, ifconfig, lsmod, dmesg, etc.
-
rc7 ok
- lspci
bla bla
atheros ar242 x 802.11 abg (the wireless card)
bla bla
attansic L2 100 Mb (the ethernet card)
asustek unknow device 8233
bla bla
- ifconfig
local loopback (only)
- lsmod
sg grmod
hdc
scsi
battery ac
- dmesg
bla bla
net protocol family 15
net protocol family 17
bla bla
thanks
-
The -v switch is important for verbose information. You can also use -k if you want just the modules
If you want to get wireless, see the extension as it is not included in the base.
-
I have a Intel 82567LM in my lenovo X200 and it looks like tc doesn't know this... too bad as I have no clue how to get this working. Could someone tell me how I can get this to work?
Oh yes and it also has a Intel WiFi Link 5100 which would use the iwlwifi driver but that isn't included in the tc kernel right? How can I get that to work too?
Thank you
-
tinycore is built with some of the 2.6.26 netcard drivers present and none of the 2.6.26 wifi drivers present. Some of the netcard drivers are compiled into the kernel and some of them are compiled as modules.
You can get the missing drivers from the net-2.6.26.tcem or wireless-2.6.26.tcem extensions