Networking in BT5 fails

[brenny]

Hi everybody,

I was very happy to install BT5 but I'm having a network problem which reminds me of my Lucid install.

/etc/init.d/networking start throws up a complaint about using 'start' which is fair enough because I remember problems with Lucid last year and the fix was relatively simple.

I did the following:

service network-manager stop

I removed /var/lib/NetworkManager/NetworkManager.state

and then

service network-manager start

The above procedure does not work with BT5 of course because /var/lib/NetworkManager/ does not exist.

ifconfig will put eth0 up but a connection will not be established.

WICD will 'see' the network but will be unable to make a connection.

It's the first time since the mid 1990's that a simple ethernet connection has failed.

I'm sure there is something obvious I'm missing and I apologise in advance but without networking the operating system is useless.

I'm on a Vaio P by the way, which is a pain as regards poulsbo, but networking has never been a problem.

If anybody has any ideas it would be appreciated.

Take care,

Bren.

[sostentado]

try to refresh:

ifconfig eth0 down
wicd stop
/etc/init.d/networking stop

then:

/etc/init.d/networking start
wicd start
ifconfig eth0 up

[brenny]

Hi sostentado and thanks for your reply.

Unfortunately when I get to the /etc/init.d/networking start as per your suggestion I get the following:

"Rather than invoking init scripts through /etc/init.d, use the service(8) utility, e.g. service networking start
Since the script you are attempting to invoke has been converted to an Upstart job, you may also use
the start(8) utility, e.g. start networking"

This is exactly what used to happen with my Lucid install.

Using "service networking start" fails, as does "start networking"

If you or anyone else has a suggestion I would be grateful.

Am I the only one with this problem?

cheers,

Bren.

[khianhui]

Hi Brenny,

Can you explain "WICD will 'see' the network but will be unable to make a connection"? Are you using DHCP or static ip configuration? The /etc/init.d/networking which is working in BT4 is deprecated now.

[r083rt]

are you using vmware or virtualbox ??????
is it installed??
is it booting from usb ??

try dhcp and check if you have an ip

when you ping a network do you get any packets

ping www.google.ie

theres something quite not right here

do you have network when you boot from usb ???

more info PLEASE

[sostentado]

try this:

wicd stop

then:
wicd start
dhclient eth0 (eth0 an example of your connection)

[brenny]

Hi everyone, and thanks for the responses.

I'm quite adept at pretending to be busy and I've spent all afternoon at work investigating the problem and I think I may have

found the cause.

Sony, not content with foisting upon Vaio P users the crappy poulsbo chipset, decided to go one further and furnish the Vaio P

with the not so marvellous Marvell Yukon 88E8057 PCI-E Gigabit Ethernet Controller.

The driver for this chipset is borked in Lucid.

The fix appears to be to install an old driver from the marvell website. Unfortunately the Linux kernel source must be available

in directory /usr/src/linux.

Thankfully Muts has told us how to do this in the How-To section. But of course the Vaio has no internet access.

A friend is coming round with a copy of the source files and then I can try the new drivers.

What I mean when I say WICD 'sees' the network is that the wired and wireless networks show up as available but a connection cannot be established.

It's a hard disk install, dual boot with windows 7 and there is no network when booting from the live USB also.

The connection is DHCP.

lspci shows the Marvell Controller but lsmod does not, modprobe doesn't help either.

Many thanks for your help people, I'll report back if my proposed solution works in case someone else is in the same predicament.

Cheers,

Bren.

[brenny]

Hi people,

Just to let you know that the installation of the new drivers proved effective.

The package I installed is 'install_v10.87.3.3.tar.bz2' from the Marvell website.

Make sure you unload the sky2 module first so you won't have problems with the installation.

Kernel sources need to be installed at /usr/src/linux

I've set up a static IP as I still seem to have a problem with DHCP.

Now that I have a solid ethernet connection I can move on to the joys of configuring the poulsbo chipset!

Thanks again everyone,

Take care,

Bren.

[jayeshdude]

sorry if this sounds funny but m not able to install that driver as i am new ti lunux so can u plz provide me some guidance on it



Thank u in adv

[zachattack303]

i also need help too i am new to Linux and I need help because i tried everything that the forum said and i am still having trouble with /etc/init.d/networking start