Announcement

**Fintan** · Jun 20, 2009, 01:38 PM

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

Okay I went here:
https://bugs.launchpad.net/ubuntu/+bug/239852

and did:

Code:

ubuntu@ubuntu:~$ lspci -vvnn

these are the relevant lines:

07:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8040T PCI-E Fast Ethernet Controller [11ab:4355] (rev 12)
Subsystem: Toshiba America Info Systems Device [1179:ff50]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 2299
Region 0: Memory at b8000000 (64-bit, non-prefetchable) [size=16K]
Region 2: I/O ports at 2000 [size=256]
Capabilities: <access denied>
Kernel driver in use: sky2
Kernel modules: sky2

08:00.0 Network controller [0280]: Intel Corporation Wireless WiFi Link 5100 [8086:4232]
Subsystem: Intel Corporation Device [8086:1201]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 2298
Region 0: Memory at b8100000 (64-bit, non-prefetchable) [size=8K]
Capabilities: <access denied>
Kernel driver in use: iwlagn
Kernel modules: iwlagn

It seems to be finding the driver, etc.

But what does:
<access denied>
mean?

I am still on the live cd.

Anyone?

**Fintan** · Jun 20, 2009, 04:29 PM

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

OKay with the help of dible i did this to /etc/network/interfaces:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback
iface eth0 inet dhcp
allow-hotplug wlan0
iface wlan0 inet manual
wpa-driver wext
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp

and made a file for /etc/wpa-supplicant/wpa_supplicant.conf:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=netdev
ap_scan=1
fast_reauth=1
eapol_version=1
#network={
# ssid="TRENDnet"
# psk={lotta stuff}
# priority=5
#}

network={
key_mgmt=NONE
}

I was told to comment out the middle part because I don't have a wlan router but a lot of neighbors do

NOw Network manager says:
etho: not managed
wlan: not managed

lspci -vvnn gives the same as before.

lshw tells ne the network is disabled

iwconfig gives:

lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11abgn ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=0 dBm
Retry min limit:7 RTS thr

ff Fragment thr=2352 B
Power Management

ff
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

pan0 no wireless extensions.

I am lost !!!!

**flarson** · Jun 20, 2009, 06:12 PM

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

A few things that might clear up some mysteries. To get full info from lspci run it as root.

Code:

sudo lspci -vv

/etc/network/interfaces is part of ifupdown, not network-manager. Since you have the interfaces in /etc/network/interfaces network-manager is saying

etho: not managed
wlan: not managed

You could change that by editing /etc/Network-Manager/nm-something but since you are configuring /etc/network/interfaces I guess you want to use ifupdown, which is very good for wired connections.

Debian has a package of firmware for your wireless ,firmware-iwlwifi, and Ubuntu has one also. I expect your wireless should work, and maybe is but it seems you do not have an access point to connect to?

If you have an ethernet connection with the setup you have described I think that

Code:

sudo ifup eth0

will probably give you a working ethernet.

With a manual wlan0 you would also need to run

Code:

sudo ifup wlan0

to get it to start. I think both of those NIC's should work just fine.

**Fintan** · Jun 21, 2009, 12:20 AM

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

Hi Mando,
Thank you for the answer.

In the mean time I had a look at detonates how-to:
http://kubuntuforums.net/forums/inde...opic=3100052.0

I didn't follow it because one of the posters said he had exactly the same interface setup as my default.but I did:

$ ifconfig
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:52 errors:0 dropped:0 overruns:0 frame:0
TX packets:52 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:3288 (3.2 KB) TX bytes:3288 (3.2 KB)

07:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040T PCI-E Fast Ethernet Controller (rev 12)
Subsystem: Toshiba America Info Systems Device ff50
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 2299
Region 0: Memory at b8000000 (64-bit, non-prefetchable) [size=16K]
Region 2: I/O ports at 2000 [size=256]
Capabilities: [48] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [5c] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
Address: 00000000fee0300c Data: 4199
Capabilities: [c0] Express (v2) Legacy Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <256ns, L1 unlimited
ClockPM+ Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [130] Device Serial Number 00-23-8b-ff-ff-6b-df-a6
Kernel driver in use: sky2
Kernel modules: sky2

08:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100
Subsystem: Intel Corporation Device 1201
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 2298
Region 0: Memory at b8100000 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
Address: 00000000fee0300c Data: 41a1
Capabilities: [e0] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ FLReset-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <128ns, L1 <32us
ClockPM+ Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [140] Device Serial Number 6e-06-1d-ff-ff-fa-22-00
Kernel driver in use: iwlagn
Kernel modules: iwlagn

Then with dible interface setup:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback
iface eth0 inet dhcp
allow-hotplug wlan0
iface wlan0 inet manual
wpa-driver wext
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp

and did:

sudo ifup eth0
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/eth0/00:23:8b:6b:df:a6
Sending on LPF/eth0/00:23:8b:6b:df:a6
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
grep: /etc/resolv.conf: No such file or directory

Now I went back to the original interface setup:
# The loopback network interface
auto lo
iface lo inet loopback

and sudo ifup eth0
gives:

Ignoring unknown interface eth0=eth0

I am slowly loosing it.

I read on a ubuntu post that this lappy worked out of the box on Ubuntu Intrepid:
http://ubuntuforums.org/showthread.p...t=Toshiba+M800

EDIT:
I tried to be smart and install wicd with getdebi. It told me it was conficting with network manager so I got rid of that.
Couldn't find: network-manager-kde

Next gedebi told me there was some python stuff missing.

So I went back to detonates site and I did the changes:
From:

auto lo
iface lo inet loopback

to

auto eth0
iface eth0 inet dhcp

did

Code:

ifconfig

That gives:
command not found

ifup eth0= now gives me the same as above with this difference:
No working leases in persistent database - sleeping.

grep: /etc/resolv.conf: No such file or directory
*if-up.d/mountfs[etho]: waiting for interface before doing NFS mounts

:P

EDIT2:
I made a empty etc/resolve.conf file (Ididn't know what to put in it for dhcp

)

No ifconfig seems to work.

But:
ifup eth0= now gives me the same as before:
No working leases in persistent database - sleeping.

grep: /etc/resolv.conf: No such file or directory
*if-up.d/mountfs[etho]: waiting for interface before doing NFS mounts

**Detonate** · Jun 21, 2009, 05:52 AM

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

This is the strangest thing. When you run ifconfig, your ethernet controller is shown as 07:00.0, not eth0. I've never seen that before. Same with lspci. There is no eth0. Try using that instead of eth0 in your interfaces file and see what happens.

**Fintan** · Jun 21, 2009, 05:59 AM

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

Hi detonate,
yeah it is weird

Do you mean changing this:
auto eth0
iface eth0 inet dhcp

for this
auto 07:00.0
iface 07:00.0 inet dhcp

??

**Detonate** · Jun 21, 2009, 06:07 AM

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

Yes, try it. I don't know what will happen, but there does not appear to be a "eth0" on your machine.

**Fintan** · Jun 21, 2009, 06:51 AM

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

Okay I took dibles interface and changed it to:

auto 07:00.0
iface 07:00.0 inet dhcp
allow-hotplug wlan0
iface wlan0 inet manual
wpa-driver wext
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp

sudo /etc/init.d/networking restart gives:

* Reconfiguring network interfaces...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
SIOCSIFADDR: No such device
07:00.0: ERROR while getting interface flags: No such device
07:00.0: ERROR while getting interface flags: No such device
wmaster0: unknown hardware address type 801
Bind socket to interface: No such device
Failed to bring up 07:00.0.

That cannot be it

**flarson** · Jun 21, 2009, 06:52 AM

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

The output that shows

07:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040T PCI-E Fast Ethernet Controller (rev 12)

is from lspci -vv, not from ifconfig.

It would be good to see what is in /etc/udev/rules.d/70-persistent-net.rules as that will name your interfaces.

The ifup command, and it's partner ifdown, operate on interfaces that are described in /etc/network/interfaces. This is an entirely seperate software suite from network-manager and wicd. edit /etc/network/interfaces to contain this

Code:

auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp

Make sure that network-manager is not running and wicd is not running, then run

Code:

sudo ifup eth0

That should get eth0 working if you are connected to a modem/router that acts as a DHCP server.

The ifconfig command is in /sbin. If that is not in your PATH you will need to use /sbin/ifconfig to run it. As root /sbin will be in your PATH.

Ifconfig requires options to correctly configure an interface. ifup uses the options specified in /etc/network/interfaces to use ifconfig to configure the network. Running ifconfig with no options will list the interfaces for you, but will not bring one up.

Your system will create a /etc/resolv.conf if dhcp works.

When gdebi complained about python it is a gdebi problem that Kubuntu should have set package dependencies to avoid, not a problem with wicd. The thing to do would be to skip the unreliable python GUI and run

Code:

sudo dpkg -i wicd-....deb

You are very close to having things working. Stick with using ifup and /etc/network/interfaces until you get it figured out. You are confusing yourself by jumping around and trying disjointed advice.

**Fintan** · Jun 21, 2009, 06:58 AM

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

HI Mando,
Okay I changed ny interfaces back to:

auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp

Sorry I pressed post to soon

Here is /etc/udev/rules.d/70-persistent-net.rules :

# This file maintains persistent names for network interfaces.
# See udev(7) for syntax.
#
# Entries are automatically added by the 75-persistent-net-generator.rules
# file; however you are also free to add your own entries.

# PCI device 0x11ab:0x4355 (sky2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:23:8b:6b:df:a6", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x8086:0x4232 (iwlagn)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:22:fa:1d:06:6e", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"

Code:

ifup eth0

gives:

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/eth0/00:23:8b:6b:df:a6
Sending on LPF/eth0/00:23:8b:6b:df:a6
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
grep: /etc/resolv.conf: No such file or directory

and

Code:

sudo ifup eth0

gives:

interface eth0 already configured

**Detonate** · Jun 21, 2009, 07:06 AM

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

In reply #4 he ran ifconfig and it did not show a "eth0" interface.

I also would be interested to see how the interface is named in /etc/udev/rules.d/70-persistent-net.rules.

**dibl** · Jun 21, 2009, 07:10 AM

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

@fintan, I assumed your router is a DHCP server -- is it? If not, then you don't want the "iface eth0 ..." line that is in my interfaces file. Sorry if I messed up with that.

**Fintan** · Jun 21, 2009, 07:17 AM

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

"Mondo:

Make sure that network-manager is not running and wicd is not running, then run

Code:

sudo ifup eth0

That should get eth0 working if you are connected to a modem/router that acts as a DHCP server.

I don't have network manager any more.

Hi Dible.

I don't have a router, just a modem on a switch.

This is my desktop jaunty interface just for the hell of it:

auto lo
iface lo inet loopback

" all:
ifconfig gives now:

$ ifconfig
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:24 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:1488 (1.4 KB) TX bytes:1488 (1.4 KB)

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)

**dibl** · Jun 21, 2009, 08:02 AM

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

Maybe this:

http://ubuntuforums.org/showpost.php...7&postcount=12

Announcement

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

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

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment