This is a discussion on Why can't Linux see my NIC? within the Linux Operating System forums, part of the Unix Operating Systems category; --> I'm dual booting Windows XP and SUSE Linux 9. When I'm in Windows, my PC connects on bootup to ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I'm dual booting Windows XP and SUSE Linux 9. When I'm in Windows, my PC connects on bootup to my broadband router through its NIC card with no problems. But in Linux, it doesn.'t. I get the red "failed" flag during boot for my eth0 when it attempts a DHCP connection. If it matters, I'm on Verizon DSL using a Siemens/Efficient Networks SpeedStream 2624 router. Any ideas? Thanks. |
| |||
| Hiawatha Bray <watha@monitortan.com> wrote: > problems. But in Linux, it doesn.'t. It would be a little easier if you know which NIC is that. Davide -- | Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western | Civilization? Gandhi: I think it would be a good idea. | | |
| |||
| It's a generic NIC based on the 3Com 3C905TX. "Hiawatha Bray" <watha@monitortan.com> wrote in message news:QZgZb.62972$KV5.54611@nwrdny01.gnilink.net... > I'm dual booting Windows XP and SUSE Linux 9. When I'm in Windows, my PC > connects on bootup to my broadband router through its NIC card with no > problems. But in Linux, it doesn.'t. I get the red "failed" flag during > boot for my eth0 when it attempts a DHCP connection. If it matters, I'm on > Verizon DSL using a Siemens/Efficient Networks SpeedStream 2624 router. > > Any ideas? Thanks. > > |
| |||
| "Hiawatha Bray" <watha@monitortan.com> wrote in message news:<QZgZb.62972$KV5.54611@nwrdny01.gnilink.net>. .. > I'm dual booting Windows XP and SUSE Linux 9. When I'm in Windows, my PC > connects on bootup to my broadband router through its NIC card with no > problems. But in Linux, it doesn.'t. I get the red "failed" flag during > boot for my eth0 when it attempts a DHCP connection. If it matters, I'm on > Verizon DSL using a Siemens/Efficient Networks SpeedStream 2624 router. > > Any ideas? Thanks. Not sure about SUSE specifics and "red failed flags", but there are a few things you can check. "lspci" will show you if linux can see the NIC at all (assuming it is pci) "ifconfig -a" will show you all configured network interfaces "lsmod" will show you which modules you have loaded I'd take a guess that you don't have the module (In "Windows" I guess you'd call this a "driver") loaded. Either way, running those commands will show you wether your NIC is correctly set up or not. If there is no problem with the nic, then you can move on to how you're doing DHCP. |
| |||
| Okay...I tried assigning a static IP address, and now the NIC starts up. But I still can't reach the Internet. Apparently it doesn't see the router at all. That figures, since if it could, I presume DHCP would have worked and it would have been assigned an IP address. So my guess is that for some reason the Speedstream router won't talk to SUSE correctly. Anybody ever see anything like this? Thanks. "Mattias Honrendgard" <comeand@kissmyfatarse.com> wrote in message news:dd394218.0402200314.798e4e6b@posting.google.c om... > "Hiawatha Bray" <watha@monitortan.com> wrote in message news:<QZgZb.62972$KV5.54611@nwrdny01.gnilink.net>. .. > > I'm dual booting Windows XP and SUSE Linux 9. When I'm in Windows, my PC > > connects on bootup to my broadband router through its NIC card with no > > problems. But in Linux, it doesn.'t. I get the red "failed" flag during > > boot for my eth0 when it attempts a DHCP connection. If it matters, I'm on > > Verizon DSL using a Siemens/Efficient Networks SpeedStream 2624 router. > > > > Any ideas? Thanks. > > Not sure about SUSE specifics and "red failed flags", but there are a > few things you can check. > > "lspci" will show you if linux can see the NIC at all (assuming it is > pci) > "ifconfig -a" will show you all configured network interfaces > "lsmod" will show you which modules you have loaded > > I'd take a guess that you don't have the module (In "Windows" I guess > you'd call this a "driver") loaded. Either way, running those commands > will show you wether your NIC is correctly set up or not. If there is > no problem with the nic, then you can move on to how you're doing > DHCP. |
| |||
| Hiawatha Bray wrote: > Okay...I tried assigning a static IP address, and now the NIC starts up. > But > I still can't reach the Internet. Apparently it doesn't see the router at > all. That figures, since if it could, I presume DHCP would have worked > and it would have been assigned an IP address. > > So my guess is that for some reason the Speedstream router won't talk to > SUSE correctly. Anybody ever see anything like this? Don't know if I can help, but: (a) Is your dsl pppoe (seems not to be, but have to ask)? (b) Are you using your router as a router (do you have a local network?) or as a bridge (direct connection between your machine and your isp)? In case of a "bridge", is your modem in "bridge"? I worked with an Adsll provider which was not pppoe; Using Knnopix (not SuSE), booting from the cd, it would be automatically detected; I'd be on the web in seconds. Really, had to do nothing. In that machine, the would be a 3c905b (not the 3c509), using the 3c59x module (and some ppp modules). So: (c) Is the 3c59x module being loaded? If not, you may try to load it mannually: modprobe 3c59x ^^^^^<-If I'm not mistaken!) If it is pppoe, than it is different. You may have to download some files (www.roaringpenguin.com) and do some configuring. Keep us informed about the outcome, ok? Good luck! |
| |||
| I think Verizon is pppoe. But I'm plugging into the router. So I shouldn't have to use ppp at all, right? It should just talk to the router, the way it does in WinXP, Win 2000 or on my Mac for that matter. "Paulo R. Dallan" <prdolc@yahoo.com.br> wrote in message news:c16gvr$1d882q$1@ID-225087.news.uni-berlin.de... > Hiawatha Bray wrote: > > > Okay...I tried assigning a static IP address, and now the NIC starts up. > > But > > I still can't reach the Internet. Apparently it doesn't see the router at > > all. That figures, since if it could, I presume DHCP would have worked > > and it would have been assigned an IP address. > > > > So my guess is that for some reason the Speedstream router won't talk to > > SUSE correctly. Anybody ever see anything like this? > > Don't know if I can help, but: > > (a) Is your dsl pppoe (seems not to be, but have to ask)? > > (b) Are you using your router as a router (do you have a local network?) or > as a bridge (direct connection between your machine and your isp)? In case > of a "bridge", is your modem in "bridge"? > > I worked with an Adsll provider which was not pppoe; Using Knnopix (not > SuSE), booting from the cd, it would be automatically detected; I'd be on > the web in seconds. Really, had to do nothing. > > In that machine, the would be a 3c905b (not the 3c509), using the 3c59x > module (and some ppp modules). So: > > (c) Is the 3c59x module being loaded? If not, you may try to load it > mannually: > > modprobe 3c59x > ^^^^^<-If I'm not mistaken!) > > If it is pppoe, than it is different. You may have to download some files > (www.roaringpenguin.com) and do some configuring. > > Keep us informed about the outcome, ok? > > Good luck! > > |
| |||
| Hiawatha Bray wrote: > I think Verizon is pppoe. > > But I'm plugging into the router. So I shouldn't have to use ppp at all, > right? Nop, you use ppp; you may not have to login through a script/program over the os, if your "router" is doing so, but it may not be. Check comments below. > It should just talk to the router, the way it does in WinXP, Win > 2000 or on my Mac for that matter. Not necessarily. The router can be programmed to access the pppoe directly, making the "login" therein (i.e., the router makes the login) OR NOT. Check with your ISP. Ex.: I've worked with an ISP which used pppoe, there was a router connected to the nic, but in fact it was assigned as bridge; The connection login was made by an script through software. And, in fact, it had a win CD installation, Windows was scripted to connect directly; OTOH, there was no Linux support! (i.e., one had to connect using a Linux pppoe program; in www.roaringpenguin.com they have a free one which is quite good). So, again: (a) Really check with your ISP if your dsl is pppoe? (b) Are you using your router as (i) a router only for login purposes; (ii) as a real router (i.e., do you have a local network?); or (iii) as a bridge (direct connection between your machine and your isp) (ps.: by the latest info, seems to be router, but again, if necessary, check with your ISP)? In case of a "bridge", is your adsl (I'm supposing it is adsl; correct me if necessary) modem in "bridge mode"? (c) As your nic is an generic 3c905, is the 3c59x module being loaded? Check with the "lsmod" command and copy the results here. Good luck! |
| ||||
| In comp.os.linux.help Hiawatha Bray <watha@monitortan.com> wrote: > Okay...I tried assigning a static IP address, and now the NIC starts up. But > I still can't reach the Internet. Apparently it doesn't see the router at > all. That figures, since if it could, I presume DHCP would have worked and > it would have been assigned an IP address. > > So my guess is that for some reason the Speedstream router won't talk to > SUSE correctly. Anybody ever see anything like this? Likely you are not setting something right on either the router or the linux machines. Try "ifconfig" and "route -n" and see if the tables are properly set up. -- Best regards, Stephen Jenuth (jenuths@homacjen.ab.ca) Quidquid latine dictum sit, altum viditur. pgp/gpg public key available at http://www.keyserver.net |