[Solved] Need help getting internet going so I can install extra packages

[MTCAT]

Hello,

I'm completely new to TinyCore Linux but really like it so far.

I'm running an old version (TinyCore 3, kernel 2.6.33.3) in an attempt to maintain compatibility with ADC driver and data acquisition software.

However, I need to install some more software (gcc - to build the ADC driver, and pciutils.tcz - PCI interface to ADC), but I haven't been able to get my internet working.

I'm using a wired connection, ifconfig -a reveals that eth0 is there, but it's not active I guess.

I'm very sorry, but I can't even edit a text file, I've tried "joe", "nano", "vi", "emacs" and "editor" and nothing works for me.

I assume I need to add some commands to a start up file to bring up eth0 interface ?

I'm hoping to do that in order to execute "tce-load -wi compiletc"  to get gcc, and I'm not sure how to add pciutils.tgz

I apologize as well, I created an account but I still haven't been able to access the Wiki page.

Thanks in advance for the help. Sorry for posting incorrectly to TCB Talk as well, I'm new to forums in general.

[Rich]

Hi MTCAT
Welcome to the forum.

If you enter this:

Code: [Select]

sudo ifconfig eth0 up
Is eth0 active then?

[MTCAT]

Hi Rich, thanks for your reply, and welcoming me to the Forum, I will try this shortly...

David

[MTCAT]

Hi Rich,

I tried out "sudo ifconfig eth0 up" and it seemed to work, didn't get any errors, but I still can't ping "google.com" (I also tried ping 8.8.8., if I try to execute "tce-load -wi compiletc" I get a bunch of errors still.

I took some screen shots but couldn't make them small enough for loading here, and still be legible.

So I'm not sure, for some reason we can see eth0 as being "there", but it's not talking to the outside world yet.

Any ideas as to what else I can try ?

[MTCAT]

Sorry, just had to save as jpeg's, here's the screen-shots, with output of "ifconfig -a" before and after executing "sudo ifconfig eth0 up"

Thanks,

[Rich]

Hi MTCAT
Click on the  Control Panel  icon at the bottom of the screen. It's the icon with the screwdriver on it. When it comes
up, click on the  Network  button. Fill in the fields and click  Apply  and if necessary,  Exit.  Then try  ping  again.

[MTCAT]

Hi Rich,

Thanks so much for the help, this did make some progress, seems I can transmit now, but still am not receiving, attached screenshot.

I tried both DHCP (which never seems to work for me) and static, I just made up an IP address for static of 192.168.1.20 ?

Attached a screenshot of behavior with my attempt with static IP address.

Maybe you can see a mistake ?

Thanks

[attachment deleted by admin]

[Rich]

Hi MTCAT
The  Gateway  address is probably wrong. The  Gateway  is your router. The address is likely  192.168.1.1.
You also want a  Name Server  listed. The  Name Server  is what resolves  google.com  to an IP address.
You can try using  192.168.1.1  for the  Name Server  field for now.

[MTCAT]

Hi Rich,

I tried 192.168.1.1 for the Gateway address and the nameserver and unfortunately that still didn't work.

I apologize for my ignorance, how can I find out the IP address of my router ? Is it listed on it (Xfinity modem).

Thanks

[corezoo]

Can you ping 192.168.1.1, enter in a web browser and the modem page will come up. Are you locked out of the modem?
I think 8.8.8.8 is the address of google's DNS.

[Rich]

Hi MTCAT
If you run:

Code: [Select]

ifconfig -aDoes it show that  eth0  has  192.168.1.20  assigned to it?

Also, we are talking about a wired connection here, right? There is a cable between your machine and router, yes?

See if this produces a response:

Code: [Select]

sudo ping 192.168.1.1

[MTCAT]

Hi Rich,

No, I can't ping 192.168.1.1 either, I don't think I'm locked out of the modem, I was able to get a newer version of Lubuntu (16.04, kernel 4.4.6) going on the same hardware this afternoon....could we get some hints from that somethow ?

I'm hoping for TinyCore though !, I really like the minimalist approach.

I don't think I have a web browser installed yet though (in Tiny Core 3) ?

Just saw your new post as well, yes, "ifconfig -a" shows 192.168.1.20 assigned to eth0, so that's good.

Yup, direct wired connection, the "sudo ping 192.168.1.20" unfortunately wasn't successful either.

Thanks,

David

[Rich]

Hi MTCAT

... I was able to get a newer version of Lubuntu (16.04, kernel 4.4.6) going on the same hardware this afternoon....could we get some hints from that somethow ? ...

Absolutely. Open a terminal under Lubuntu and do this:

Code: [Select]

ifconfig -a 2>&1 > network.txt

Code: [Select]

route 2>&1 >> network.txt
And post the contents of  network.txt.

[MTCAT]

Hi Rich,

Thanks again for all this help, here's the screenshot of network.txt (from Lubuntu) after doing the commands you instructed !

I guess Lubuntu uses a new style of naming convention for the interface, I like the older style better !

[Rich]

Hi MTCAT
If Lubuntu is using a wireless connection, which it might be, then the following won't work:
Set IP address to 10.0.0.40
Set Network Mask to 255.255.255.0
Set Broadcast to 10.0.0.255
Set Gateway to 10.0.0.1
Set Name Server to 10.0.0.1