Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
09-05-2004, 10:01 PM
|
#1
|
LQ Newbie
Registered: Aug 2004
Distribution: JAMD
Posts: 10
Rep:
|
Linux SuSE 9.0 Cannot connect to the Internet
I am runnig a Compaq Presario AMD 750 MHZ with a Linksys Cable Modem and a Airlink router. This is my forst time using Suse and I cannot connect to the internet. I do not know how to configure the system. Can anyone help? 
|
|
|
09-05-2004, 10:12 PM
|
#2
|
Senior Member
Registered: Sep 2003
Location: Rio
Distribution: Debian
Posts: 1,513
Rep:
|
hi!
Can you explain how does it connect to the cable modem? Ethernet? Usb?
If you had win before, can you remember some of the configs?
Please, post here the output of the "ifconfig" command, so we can see how are things doing so far, with your comp?
|
|
|
09-05-2004, 10:32 PM
|
#3
|
LQ Newbie
Registered: Aug 2004
Distribution: JAMD
Posts: 10
Original Poster
Rep:
|
IPCONFIG display
Connection-specific DNS Suffix.:
IP Address 192.168.1.5
Subnet mask 255.255.255.0
Default Gateway 192.168.1.1
|
|
|
09-05-2004, 10:33 PM
|
#4
|
LQ Newbie
Registered: Aug 2004
Distribution: JAMD
Posts: 10
Original Poster
Rep:
|
IPCONFIG
Im running ethernet
|
|
|
09-05-2004, 11:30 PM
|
#5
|
Senior Member
Registered: Sep 2003
Location: Rio
Distribution: Debian
Posts: 1,513
Rep:
|
Try to do this at the console:
ping 192.168.1.1
ping www.google.com
and
ping 64.233.161.99
these commands will check whether you can accesss something inside and outside your network. Please post here the result.
|
|
|
09-12-2004, 12:20 PM
|
#6
|
LQ Newbie
Registered: Sep 2004
Distribution: SuSE 9.1
Posts: 9
Rep:
|
I bumped into this topic whilst searching for possible solutions for my problem (which is the same one as yours ranger)..
I just got the computer for free, basically to mess around with linux.. I've already once before installed linux on my laptop and the internet did work then, on the desktop it doesn't seem to work however
My conncetion is also through ethernet, the network card is configured, I've tried connecting using proxy settings instead of going for the "connect directly to the internet" option but no succes so far... any help is appreciated!
btw, I typed the ping stuff from above and for the ip addresses I got: "connect: Network is unreachable", for the other url it said: "ping: unknown host www.google.com"
|
|
|
09-12-2004, 03:14 PM
|
#7
|
Senior Member
Registered: Sep 2003
Location: Rio
Distribution: Debian
Posts: 1,513
Rep:
|
This means you have no network, or you don't have a valid ip on your eth cards. Type "ifconfig" without arguments as root, to see the entire eth info. After that, try to do
ifup eth0
this will run the dhcp client on this interface, assuming you use eth0 for internet. Replace it with your actual ethX number.
Post again if it doesn't work.
|
|
|
09-12-2004, 04:17 PM
|
#8
|
LQ Newbie
Registered: Sep 2004
Distribution: SuSE 9.1
Posts: 9
Rep:
|
okay, I typed the ifconfig and I got the following:
Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:42 errors:0 dropped:0 overruns:0 frame:0
TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2708 (2.6 Kb) TX bytes:2708 (2.6 Kb)
but I wouldn't have any idea of the number of the ethernet adapter  I've asked my dad but he doesn't know either.. I've tried from 0 to 10 and I got "ERROR: No configuration found for ethX"
I've installed winXP on the comp as well by the way and my internet does work on XP.. Still a newbie at linux here so be patient, I appreciate the time and effort you're putting into answering here!
oh by the way.. I wrote down the error msg I got during the setup of SuSE when it was testing the internet connection:
digital equipment Corporation DECchip 21041 [TulipPass3] (rev11) device
eth-bus-pci-0000:00:0b.0 configuration:
ERROR: Interface is not available
Don't know whether this helps..?
|
|
|
09-12-2004, 05:32 PM
|
#9
|
Senior Member
Registered: Sep 2003
Location: Rio
Distribution: Debian
Posts: 1,513
Rep:
|
It does help, indeed. I don't know why, but suse 9.1 decided to name eth devices by the pci addresses, for some reason... Its akward for dealing with.
So, the name "eth-bus-blablabla..." is the name of your interface. Instead of typing
ifup eth0
you have to ifup this damn interface name, like this:
ifup eth-bus-etc...
If it works ok, you'll see cablemodem/dslmodem activity, and it will output some ip configs. By looking at your current ifconfig, you only have loopback interface running. When correctly set, you'll also have this eth-thing listing there. So, after ifuping, do infconfig again.
Post again, if it fails.
Last edited by bruno buys; 09-12-2004 at 05:34 PM.
|
|
|
09-13-2004, 03:54 AM
|
#10
|
LQ Newbie
Registered: Sep 2004
Distribution: SuSE 9.1
Posts: 9
Rep:
|
writing ifup eth-bus-... gives me the exact same output as I wrote down previously (ERROR: interface is not available and the rest of it)
does this mean it doesn't recognize the ethernet cable?
|
|
|
09-13-2004, 10:57 AM
|
#11
|
Senior Member
Registered: Sep 2003
Location: Rio
Distribution: Debian
Posts: 1,513
Rep:
|
Do you have the proper drivers loaded for this card? I can't believe suse didn't install it, but, anyway:
Try to do
ifconfig eth-bus... up
ifup eth-bus...
and see if it helps.
If it doesn't, we'll have to check your drivers:
- You have to figure out what is your ethernet card brand and chip. Once you know this, you can check if the driver is loaded and/or load it yourself.
- To find this info, you can get your computer documentation and take a look. Or you can use the lspci command in a console, as root.
Do
lspci |grep Eth
Mine looks like this, for your reference:
frank:/home/bruno# lspci |grep Eth
0000:00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
0000:00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
frank:/home/bruno#
(two lines, cause the computer has two cards. Yours should list only one)
The important part says RTL-8139c, which is the name of the chip. The module (driver) for this very common chip is 8139too.
If you use this same chip, you can do, as root:
modprobe 8139too
this will load the drivers for the network card, and then you should be able to bring up the connection, doing the ifup thing.
Last edited by bruno buys; 09-13-2004 at 11:00 AM.
|
|
|
09-16-2004, 07:28 AM
|
#12
|
LQ Newbie
Registered: Sep 2004
Distribution: SuSE 9.1
Posts: 9
Rep:
|
the chips name: Digital Equipment Coroporation DECchip 21041 [Tulip Pass 3] (rev 11)
So now I have to figure out the drivers' name I guess..?
|
|
|
09-16-2004, 08:27 AM
|
#13
|
LQ Newbie
Registered: Sep 2004
Posts: 26
Rep:
|
It might be worth checking in the Yast control centre to see if it is recognised.
On SuSE 9.1 you can still do ifup eth1 /eth0 etc, even though its called weird things in Yast.
Dont try and change the name in yast to eth0 or anything, it will muck up!
Is the light on, on your network card?
|
|
|
09-16-2004, 08:58 AM
|
#14
|
LQ Newbie
Registered: Sep 2004
Distribution: SuSE 9.1
Posts: 9
Rep:
|
Yast does indeed recognize the network card, that's why I thought it'd be configured properly but apperently not 
|
|
|
09-19-2004, 02:52 PM
|
#15
|
Member
Registered: Jun 2004
Distribution: Mac OS X 10.6.6, Gentoo Linux, FreeBSD 6.0
Posts: 127
Rep:
|
Quote:
Originally posted by krerar
the chips name: Digital Equipment Coroporation DECchip 21041 [Tulip Pass 3] (rev 11)
So now I have to figure out the drivers' name I guess..?
|
I've been having issues getting my modem to work. It's a DECchip 21041 [Tulip Pass 3] (rev 33). It still does not work, but I do know that it uses the 'tulip' driver. For your rev 11 you might need to use the 'tulip_old' driver.
I've been reading that the tulip driver is broken, but I don't know the details.
|
|
|
All times are GMT -5. The time now is 10:19 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|