Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: devinbj on October 05, 2010, 02:47:27 AM
-
I have a dell studio 14 laptop and I am booting TCL 3.1 (I also tried current) from a usb drive. I am trying to download applications but it says that I cannot connect to a network when I hit network in the app manager. When I type in ifconfig -a I just receive a result under lo. There seems to be no Internet connection. The wired Internet works when I boot Windows however.
Brian
-
Try with installing the firmware extension.
-
What firmware?
-
firmware.tcz
-
So before tcl wasn't installed on my flash drive. I installed it using the USB installer which created the tce folder. I installed firmware but nothing has changed.
-
So as "poking around in the mist" by installing the 'firmware.tcz' extension has not worked. I'd therefore suggest you provide us with the output of the dmesg command.
Please save it to your USB stick, and then attach the file as a response here (no inline quote please), or use pastebin (http://pastebin.com/)
-
Here it is:
-
I believe the "interesting" lines are:
tg3.c:v3.106 (January 12, 2010)
tg3 0000:03:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
tg3 0000:03:00.0: setting latency timer to 64
tg3 mdio bus: probed
eth%d: No PHY devices
tg3: Problem fetching invariants of chip, aborting.
tg3 0000:03:00.0: PCI INT A disabled
I just googled the 'tg3.c:v3.106' part together with the kernel version for TC 3.x (i.e. '2.6.33'): On this page (https://lists.linux-foundation.org/pipermail/bugme-new/2010-February/024284.html) I found the recommendation to use:
modprobe -r tg3
modprobe broadcom
modprobe tg3
You will have to execute those commands as 'root', which would be achieved by preceeding each of them with sudo)
Now check for errors in dmesg | tail and if unsure you might want to follow the step-by-step trobleshooting I just suggested in this post (http://forum.tinycorelinux.net/index.php?topic=7001.msg39540#msg39540). If that all works you probably want to make this tweak "stick": I'd suggest to put those commands (this time without the sudo) into '/opt/bootlocal.sh' and make sure that they are included in the backup (e.g. via filetool.sh -b).
-
Thank you so much. That worked. I just have to enable DHCP using the gui afterwords. Do you know how i can include that in bootlocal.sh?
-
Good the know you are making progress.
Now, the DHCP service get's started from '/etc/init.d/tc-config' before it hands over to '/opt/bootsync.sh' (which itself runs '/opt/bootlocal.sh' in the background). So I can imagine that things are not working out.
I'd say if you use boot code 'nodhcp' (to prevent the premature running of it) and add /etc/init.d/dhcp.sh after the 'modprobe' commands in '/opt/bootlocal.sh' you should achieve your goal. I'm not sure whether you'll have to put a delay (e.g. sleep 2) between the last 'modprobe' and the 'dhcp.sh', but that should not be too difficult to find out.
-
Thanks, that worked.
-
devinbj: Would you please in the interest of other users that might run into the same issue state whether you needed a delay or not (i.e. just list all your changes to '/opt/bootlocal.sh').
-
My bootlocal.sh file is as follows (note: I did not need to use sleep - maybe because my os already has a waitusb=5 on boot):
modprobe -r tg3
modprobe broadcom
modprobe tg3
/etc/init.d/dhcp.sh
ifconfig eht0 up