Raspbian ethernet fail in X

[fromagique]

Is anyone else still having the built-in USB ethernet fail while in X? The command line is fine, but when I start up an X session, the Ethernet drops out every time. It comes right back when the X session shuts down on logout.

This is getting rather frustrating... why can't the Pi seem to work with bog-standard devices that every other system uses with no problems?

I have a self-powered hub attached to one of the Pi's USB ports, and the keyboard and mouse are plugged into that. No other devices are attached (other than the ethernet cable, HDMI, and power). I'm using the new Raspbian image, fully updated with rpi-update and apt-get update/upgrade. The Pi is powered with a 10W iPad charger. Again, all of these USB devices work fine on any other system I try them with--why can't the Pi seem to cope?

[redhawk]

Something is wrong Raspbian wheezy has never failed me on the LAN port yet.
Open a console window and try the following:
ifdown eth0
ifup eth0

Richard S.

[fromagique]

Something is wrong Raspbian wheezy has never failed me on the LAN port yet.
Open a console window and try the following:
ifdown eth0
ifup eth0

Richard S.

While this dropout is occurring, log messages are being written indicating that the smsc95xx (USB ethernet) can't read some of its registers (the actual register seems to vary, 0x114 and 0x118 being most common.) So if the ethernet interface can't read its registers, telling eth0 to go up and down isn't going to do much of anything, since it can't even talk to itself, let alone release its DHCP address, etc. I also get messages in the log saying 'MII is busy in smsc95xx_mdio_read', by the way.

When I disconnect the mouse (it doesn't matter which mouse I use--they all do the same thing), the ethernet pops back on again, and if I plug it back in (during the same session), the ethernet drops again. So, it's either the network connection or the mouse, but not both. This makes web browsing a rather sisyphean proposition. (The keyboard is not affected.)

[redhawk]

Do you have a voltmeter?? if so check the voltage between TP1 and TP2 while running your X session.

Richard S.

[drgeoff]

Is anyone else still having the built-in USB ethernet fail while in X? The command line is fine, but when I start up an X session, the Ethernet drops out every time. It comes right back when the X session shuts down on logout.

This is getting rather frustrating... why can't the Pi seem to work with bog-standard devices that every other system uses with no problems?

I have a self-powered hub attached to one of the Pi's USB ports, and the keyboard and mouse are plugged into that. No other devices are attached (other than the ethernet cable, HDMI, and power). I'm using the new Raspbian image, fully updated with rpi-update and apt-get update/upgrade. The Pi is powered with a 10W iPad charger. Again, all of these USB devices work fine on any other system I try them with--why can't the Pi seem to cope?

There are many users on this forum reporting such problems. Please add your findings to https://github.com/raspberrypi/linux/issues/29.

[El_Presidente]

There are two schools of thought on this kind of issue, we don't know for sure exactly what is going on...yet.

First you could just have a low quality hub and/or hub power adapter. The Pi may be very sensitive to USB operating parameters and specs of items.
Second, you could be seeing the apparent flakiness of the Pi USB/Kernel driver code, something that (we hope) several people are looking into.

I'd be interested to know what make & spec of hub you are using and what the details of the hub power supply are. Also are you aware if the hub is 'back-powering' the Pi?

You'll be able to tell if you take out the Pi's own power supply and it keeps running, which would mean that it is getting an amount of power from the hub. That isn't really recommended due to there being a couple of polyfuses inside the Pi, so don't do it for more than a few seconds as a test (shouldn't do any harm).

I'm trying to find a pattern in this as I've had horrendous problems with all kinds of hubs, power supplies and devices.

You might need to swap out component parts one by one and note any change in behaviour. Note that all items in the chain from the cables, hub, power supplies and USB connected devices should be included in diagnostics.

[johnbeetem]

As redhawk suggested, check the TP1-TP2 voltage. On my RasPi, starting up X definitely drops the voltage a bit so it could expose a marginal power supply. In my case, I first see problems on my DVI-D monitor (green dots, then a blank screen). It's peculiar that you're seeing Ethernet problems, since the LAN9512 uses 3.3V and it's unlikely that your TP1-TP2 is going low enough to affect 3.3V. Still, it's easy to check with a voltmeter.

[exartemarte]

Is anyone else still having the built-in USB ethernet fail while in X? The command line is fine, but when I start up an X session, the Ethernet drops out every time. It comes right back when the X session shuts down on logout.

I had exactly this problem. It was fixed, for me, when I dispensed with the RPi's separate power supply and took its power from a spare port on the powered hub instead.

The supply I had been using for the Pi was a decent quality, UK-sourced one rated at 5V/2A. I have a suspicion that some of these problems arise when the Pi and hub are working on slightly different voltages.

[williamhbell]

Hi,

Do the errors in /var/log/messages look like,
http://www.raspberrypi.org/phpBB3/viewt ... 66&t=11971

?

Thanks and best regards, Will

[g1uup]

Hi Guys,
I just thought it might be useful for me to confirm that for me also changing the pi to be powered from my (cheap no name) USB hub solved this issue.

As mentioned I was certainly seeing the pi still receiving power when its independent power supply was turned off and I guess the interplay between the two power sources is the cause of the problem.

This also has the benefit of reducing the number of mains sockets required to just one, plus the monitor.

Regards

Andy R

[lostintime]

Is anyone else still having the built-in USB ethernet fail while in X? The command line is fine, but when I start up an X session, the Ethernet drops out every time. It comes right back when the X session shuts down on logout.

I'm having the same problem. When I start X via SSH over Ethernet I lose my connection. Checking with sudo tail -f /var/log/syslog as X starts up reveals errors relating to Ethernet. Quitting X via the keyboard and mouse attached to the Pi via the USB hub built into my monitor sometimes/always (not sure, need to test more) restores Ethernet. Removing the mouse and restarting X with just the keyboard attached to the hub appears to work, i.e. Ethernet does not die.

This is getting rather frustrating... why can't the Pi seem to work with bog-standard devices that every other system uses with no problems?

Good question. My guess is that it's down to poor/cheap design. The Raspberry Pi Foundation have known about this issue since mid-May at least: http://www.raspberrypi.org/phpBB3/viewt ... =24&t=5830 and http://www.raspberrypi.org/phpBB3/viewt ... f=6&t=6037

I have a self-powered hub attached to one of the Pi's USB ports, and the keyboard and mouse are plugged into that. No other devices are attached (other than the ethernet cable, HDMI, and power). I'm using the new Raspbian image, fully updated with rpi-update and apt-get update/upgrade.

Same here. I'm assuming my monitor's hub is not a passive hub. It's a Dell U2410.

The Pi is powered with a 10W iPad charger.

I'm using a 5 watt/1 amp USB charger I bought here: http://www.happymobile.co.nz/usb-wall-c ... iversal-77.

Also, I submitted a story to Slashdot about this but it was declined: http://slashdot.org/~rephlex/submissions

[El_Presidente]

Also, I submitted a story to Slashdot about this but it was declined

I'm hoping you weren't doing this in a fit of pique regarding your issues?

If you were then please think again. There are many people who have some frustrations with the Pi, it's operation, glitches and such, but I think everyone is working to help provide good quality information to the foundation and it's mass of superb supporters, all working to improve the experience.

If you tried the early Squeeze, or even Fedora remix OS releases for Pi from around May, you would realise that this thing has come on leaps and bounds. We have a hard float OS in Raspbian that is now 50%+ quicker than those first operating systems.

Give it a few weeks and I think USB/Ethernet issues will also improve significantly, by better understanding of successful hardware combinations, workarounds or by actual coding improvements in drivers and kernel.

The only way is up!

[redhawk]

I think most of the PI problems are caused by unsuitable power supplies it doesn't matter if you have a 5v @ 700ma or 5v @ 10A power supply the PI doesn't play nice if the voltage drops under load or had noise (from rectifying the 50Hz ac to dc).
As an example I have a Motorola FMP5202A power adapter rated at 5v 850ma it charges my iRiver mp3 player, Garmin sat nav, Bluetooth headset just fine but it just won't work with the PI I get hardware errors while booting.
I also have another mobile phone charger rated at a lower 700ma and this works fine with the PI it even holds the supply voltage perfectly under load which is more than I can say for my RS power adapter.
So the bottom line is if your PI boots with errors, works but craps itself when USB devices are attached or goes funny at random times for whatever reason then change your power supply.

Richard S.

[lostintime]

Also, I submitted a story to Slashdot about this but it was declined

I'm hoping you weren't doing this in a fit of pique regarding your issues?

Actually, I didn't have any issues at that stage since I hadn't even opened my Raspberry Pi at the time I submitted it! I merely thought it was important to mention the issues many others were and still are having.

If you tried the early Squeeze, or even Fedora remix OS releases for Pi from around May, you would realise that this thing has come on leaps and bounds. We have a hard float OS in Raspbian that is now 50%+ quicker than those first operating systems.

I've been reading these forums for months. I'm well aware of how much things have progressed.

Give it a few weeks and I think USB/Ethernet issues will also improve significantly, by better understanding of successful hardware combinations, workarounds or by actual coding improvements in drivers and kernel.

You have more hope than I do. I have an uneasy feeling that hardware modifications are the only thing that will help.

[El_Presidente]

Actually, I didn't have any issues at that stage since I hadn't even opened my Raspberry Pi

Odd then, to feel the need to write a Slashdot item, when you might have found that your own setup was fine?

I've been reading these forums for months. I'm well aware of how much things have progressed.

...adds to my confusion...

You have more hope than I do. I have an uneasy feeling that hardware modifications are the only thing that will help.

...I AM a glass is half-full kind of guy...
But I'd be willing to make a significant bet that things will improve with USB one way or another, without too much solder flying around.