[Solved]Network on A toshiba protégé M800-104

[Detonate]

Re: Network on A toshiba protégé M800-104

What does ifconfig -a show?

[Fintan]

Re: Network on A toshiba protégé M800-104

Hey Dible, yeah I saw that one.

I will try as a last resort but redoing that after every kernel update isn't the idea I would think.

especially since this kernel should have that driver.

any way

$ dmesg | grep sky2

gives:

$ dmesg | grep sky2
[ 3.849038] sky2 driver version 1.22
[ 3.849161] sky2 0000:07:00.0: enabling device (0000 -> 0003)
[ 3.849170] sky2 0000:07:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 3.849256] sky2 0000:07:00.0: setting latency timer to 64
[ 3.849312] sky2 0000:07:00.0: Yukon-2 FE+ chip revision 0
[ 3.850153] sky2 0000:07:00.0: irq 2299 for MSI/MSI-X
[ 3.850631] sky2 eth0: addr 00:23:8b:6b:df:a6

EDIT:
@Detonate:

~$ ifconfig -a
eth0 Link encap:Ethernet Hardware Adresse 00:23:8b:6b:df:a6
BROADCAST MULTICAST MTU:1500 Metrik:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:16

lo Link encap:Lokale Schleife
inet Adresse:127.0.0.1 Maske:255.0.0.0
inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
UP LOOPBACK RUNNING MTU:16436 Metrik:1
RX packets:72 errors:0 dropped:0 overruns:0 frame:0
TX packets:72 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:5096 (5.0 KB) TX bytes:5096 (5.0 KB)

pan0 Link encap:Ethernet Hardware Adresse 22:92:ad:46:42:2f
BROADCAST MULTICAST MTU:1500 Metrik:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

vmnet1 Link encap:Ethernet Hardware Adresse 00:50:56:c0:00:01
inet Adresse:172.16.251.1 Bcast:172.16.251.255 Maske:255.255.255.0
inet6-Adresse: fe80::250:56ff:fec0:1/64 Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

vmnet8 Link encap:Ethernet Hardware Adresse 00:50:56:c0:00:08
inet Adresse:192.168.239.1 Bcast:192.168.239.255 Maske:255.255.255.0
inet6-Adresse: fe80::250:56ff:fec0:8/64 Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wlan0 Link encap:Ethernet Hardware Adresse 00:22:fa:1d:06:6e
BROADCAST MULTICAST MTU:1500 Metrik:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wmaster0 Link encap:UNSPEC Hardware Adresse 00-22-FA-1D-06-6E-00-00-00-00-00-00-00-00-00-00
BROADCAST MULTICAST MTU:1500 Metrik:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

[Fintan]

Re: Network on A toshiba protégé M800-104

Okay guys I got fed up with all the configuring.

I reinstalled and changed the interface to:

auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp

Network manager is back and I would like to keep it if at all possible.

ifconfig -a

ifconfig -a
eth0 Link encap:Ethernet Hardware Adresse 00:23:8b:6b:df:a6
inet6-Adresse: fe80::223:8bff:fe6b:dfa6/64 Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
RX packets:672 errors:0 dropped:0 overruns:0 frame:0
TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:60251 (60.2 KB) TX bytes:5511 (5.5 KB)
Interrupt:16

eth0:avahi Link encap:Ethernet Hardware Adresse 00:23:8b:6b:df:a6
inet Adresse:169.254.9.53 Bcast:169.254.255.255 Maske:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
Interrupt:16

lo Link encap:Lokale Schleife
inet Adresse:127.0.0.1 Maske:255.0.0.0
inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
UP LOOPBACK RUNNING MTU:16436 Metrik:1
RX packets:56 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:3600 (3.6 KB) TX bytes:3600 (3.6 KB)

pan0 Link encap:Ethernet Hardware Adresse 2a:54:bc:6a:b5:40
BROADCAST MULTICAST MTU:1500 Metrik:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wlan0 Link encap:Ethernet Hardware Adresse 00:22:fa:1d:06:6e
UP BROADCAST MULTICAST MTU:1500 Metrik:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wmaster0 Link encap:UNSPEC Hardware Adresse 00-22-FA-1D-06-6E-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Network manager now tells me (again )
LAN unmanaged.

For now I just want LAN to work.
I'll worry about wlan later.

sudo ifup eth0

gives:

interface eth0 already configured

How do I disable network manager?


anything else I can check?

[muzicman0]

Re: Network on A toshiba protégé M800-104

OK, so I glanced through most of this thread...my question would be:

If you don't have a router, where do you get your IP address from? is it pulled via DHCP from your ISP? You said it is a modem connected through a switch, I think...what type of modem? Cable, DSL, etc?

mm0

[Fintan]

Re: Network on A toshiba protégé M800-104

Hi musicman, thankx for the visit

Cable modem with dhcp.

There is no problem with the modem, the cable connection or otherwise.

EDIT:
I decided to install wicd, so removed network manager again and did:

~$ sudo dpkg -i wicd_1.5.9-2_all.deb

(Lese Datenbank ... 90009 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereiten zum Ersetzen von wicd 1.5.9-2 (durch wicd_1.5.9-2_all.deb) ...
Entpacke Ersatz für wicd ...
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von wicd:
wicd hängt ab von python-gtk2; aber:
Paket python-gtk2 ist nicht installiert.
wicd hängt ab von python-glade2; aber:
Paket python-glade2 ist nicht installiert.
dpkg: Fehler beim Bearbeiten von wicd (--install):
Abhängigkeitsprobleme - lasse es unkonfiguriert
Verarbeite Trigger für man-db ...
Fehler traten auf beim Bearbeiten von:
wicd

EDIT2:
Okay now it is getting strange.
I did a reboot to load windows (the cards are disabled there for some reason)

While the machine is booting down I get this message:
Killing all remaining.....
Deconfiguring network interfaces [fail]

and the process hangs for ever.
I have to hard shutdown.

[muzicman0]

Re: Network on A toshiba protégé M800-104

have you tried bypassing the switch, and plugging the cable modem directly into the laptop? Easiest way is to power down, connect laptop to ethernet port of modem, and boot...probably worth a try.

mm0

[Fintan]

Re: Network on A toshiba protégé M800-104

Yes I have tried that. I'll do it again. Just a sec

Nope that didn't help >

[muzicman0]

Re: Network on A toshiba protégé M800-104

I also found this:

http://omingo.zorngrid.com/

Older version of Ubuntu, but might be useful. It looks like the avahi (shows on eth0.avahi in your ifconfig) is a zeroconf program. I assume it has something to do with the DHCP request in this case. but a 169.x.x.x address is not a valid address, this is what I see on windows machines when they don't pull a DHCP address.

mm0

[Fintan]

Re: Network on A toshiba protégé M800-104

Okay did that and get this:

sudo dhclient

sudo dhclient
There is already a pid file /var/run/dhclient.pid with pid 3607
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wmaster0/
Sending on LPF/wmaster0/
Listening on LPF/pan0/ee:4a:52:34:79:01
Sending on LPF/pan0/ee:4a:52:34:79:01
Listening on LPF/wlan0/00:22:fa:1d:06:6e
Sending on LPF/wlan0/00:22:fa:1d:06:6e
Listening on LPF/eth0/00:23:8b:6b:df:a6
Sending on LPF/eth0/00:23:8b:6b:df:a6
Sending on Socket/fallback
DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Still no go. at least it is not asking for resolve.conf

[Detonate]

Re: Network on A toshiba protégé M800-104

Look in /var/run and delete any dhclient.pid files you find. Have to do this as sudo. Then restart networking.

[Fintan]

Re: Network on A toshiba protégé M800-104

Look in /var/run and delete any dhclient.pid files you find. Have to do this as sudo. Then restart networking.

Hmm....there are none.

What now?

Edit:
Okay I am getting mad.

I did:

sudo /etc/init.d/networking stop

then I did:

sudo ifup eth0

ignoring unknown interface eth0=eth0

Edit 2:
I am about to get really ..........

I have reinstalled again and try this from the beginning.

I'll get back later

[Fintan]

Re: Network on A toshiba protégé M800-104

Okay I put this in interface:

auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp

then;

sudo /etc/init.d/networking stop

then

sudo ifup eht0

which gave me the usual blah, blah and
the:

No DHPOFFERS recieved
grep: /etc/resolv.conf: no such file.

I thought this was supposed to generate on??

A question:
Can I copy over some files from my desktop JJ?
Like:
resolv.conf to /etc/, and nm-dhclient-eth0.conf to /var/run (they don't exist)

This exists:
/var/run/dhclient-eth0.pid
and says:

5125

[flarson]

Re: Network on A toshiba protégé M800-104

I was gone for awhile. Looks like a lot went on. As far as ifconfig is concerned, if an interface has been configured but is not up it will not show up in ifconfig, you need ifconfig -a. If you run ifup eth0 and it tells you that the interface is already configured the appropriate response should be ifdown eth0. However, when network-manager says that it is not managing interfaces, but actually is, that command has no effect. You can run

sudo ifconfig eth0 down

which will down the interface but network-manager will immediately try to restore it.

I think that you are almost certainly seeing network-manager messing with the interface when it should not be. To solve this you need to have network-manager off the system, and you probably should not have wicd installed either. At the moment you really want eth0 to work and ifupdown will do that just fine, but you need to have a clear system so you know what is really happening.

It looks like your hardware is found and supported correctly. The udev rules and lspci, as well as the drivers, (modules) and even the behavior of ifconfig indicate that. At the moment what is failing is your DHCP. When you bring up an interface using dhcp it broadcasts to the entire network and any DHCP server there should offer a lease. When you had the system configured properly it was trying to do this but getting no response. Your error messages tell you that.

The first real question is, do you know that you have a DHCP server? Is it configured to serve addresses? Do you have another computer that gets an IP address from that DHCP server. Many modem/router/dhcp servers will let, or make you use MAC address filtering where you have to tell it the hardware address of your network card before it will assign an address. Is that in play here?

You can configure a static IP address, but you will need to know something about your network. Probably the modem has an IP address of 192.168.0.1 unless you changed it but if you know what it is you can configure a static IP address in that subnet, using the modem IP address as a gateway. To do this, assuming that the modem is 192.168.0.1 use something like this in /etc/network/interfaces.

iface eth0 inet static
address 192.168.0.200
netmask 255.255.255.0
broadcast 192.168.0.255
network 192.168.0.0
gateway 192.168.0.1

Then try

ifup eth0

. If it says eth0 already configured run

ifdown eth0
ifup eth0

If you still get that message run

ifconfig eth0 down
ifup eth0

You need to run the second one before network-manager has a chance to mess with it.

At that point ifconfig should show an IP address for eth0 and

route

should show a default route to 192.168.0.1 and you should be able to ping your modem.

The other route to take would be to try a different dhcp client. Some DHCP servers will fail to work with some DHCP clients. You can find out which dhcp client you are using by running

dpkg -l | grep dhcp

. Probably you will see

ii dhcp3-client 3.1.2-1ubuntu1 DHCP client
ii dhcp3-common 3.1.2-1ubuntu1 common files used by a

If that is the case and you want to try a different dhcp client use dhcpcd.

sudo aptitude install dhcpcd

[muzicman0]

Re: Network on A toshiba protégé M800-104

Ok...this may be a stupid question, but you said no router...I just want to make sure that the laptop is the only pc connected to the modem or switch...

Mm0

[Fintan]

Re: Network on A toshiba protégé M800-104

@mondo:
Thankx for the lengthly reply.

Many modem/router/dhcp servers will let, or make you use MAC address filtering where you have to tell it the hardware address of your network card before it will assign an address. Is that in play here?

I doubt it. My desktop didn't need any configuration and any other computer I hook up to the switch just connects.
I have tried connecting directly to the modem but th result is still nada.

To solve this you need to have network-manager off the system, and you probably should not have wicd installed either.

Do I remove network manager (again )? Wicd is not installed as explained above.

Before I go the static route I tried:

dpkg -l | grep dhcp

and got:

ii dhcp3-client 3.1.2-1ubuntu1 DHCP client
ii dhcp3-common 3.1.2-1ubuntu1 common files used by all the dhcp3* packages

Do I do:

sudo aptitude install dhcpcd

??

How? I have no connection.

If so what then?

I want to get this right this time around.

@mondo:
No I have my desktop on the switch as well. But it makes no difference since it doesn't connect when connected directly to the cable modem either.

Edit:
Just for fun I did:

ping 192.168.0.1

and get this from the desktop:

PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
From 213.202.32.241 icmp_seq=11 Destination Host Unreachable
etc.

From the lappy:

PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
From 169.254.9.53 icmp_seq=11 Destination Host Unreachable
etc.

Bthw. On windows the cards are not active either and you need the server administrator........
Could this be an issue. I doubt it very much but you know clutch the straw, etc.

Edit2:

route

on the desktop gives:

Kernel-IP-Routentabelle
Ziel Router Genmask Flags Metric Ref Use Iface
192.168.68.0 * 255.255.255.0 U 0 0 0 vmnet8
172.16.145.0 * 255.255.255.0 U 0 0 0 vmnet1
213.202.38.0 * 255.255.254.0 U 1 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth0
default dyn-cust.1.38.2 0.0.0.0 UG 0 0 0 eth0

and on the lappy:

Kernel-IP-Routentabelle
Ziel Router Genmask Flags Metric Ref Use Iface
link-local * 255.255.0.0 U 1000 0 0 eth0
default * 0.0.0.0 U 1000 0 0 eth0

Edit3:
One more thing.
When I shut down / reboot I get this:
mm-system settings: SCPLugin-ifupdown: devices removed (udi: /org/freedesktop/Hal/devices/net_00_22_fa_1d_06_6e)
mm-system settings: SCPLugin-ifupdown: devices removed (udi: /org/freedesktop/Hal/devices/net_00_23_8b_6b_df_a6)
Ifupdown: get unmanaged devices count 0
Asking all remaining prcesses to terminate OK
Kille all remaining processes fail
Deconfinguring network interfaces _

Hangs until I hard kill (turn off)