I can confirm that the JMC250 driver "jme version 1.0.8" which is part
of Ubuntu 14.04 LTS does NOT support EEE (802.3az) at 1000 Mbit/s. It
seems to support EEE ports at 100M, though.
Evidence:
When using a managed switch Zyxel GS1900-8, enabling the EEE at the
switch port will prevent
Using Asus EeeBox PC EB1007 with 14.04 reinstalled and updated
yesterday.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310798
Title:
JMicron JMC250 ethernet: networking always disconnected
To
I faced with the same problem on Ubuntu 14.04/Laptop ASUS X52JU/Router ASUS
RT-AC68U.
Laptop has the same ethernet controller.
Workaround with setting up of the speed to 100 is working for me too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Driuchatyi Nikolay, it will help immensely if you filed a new report via a
terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310798
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310798
This could have something to do with Energy Efficient Ethernet (802.3az).
http://permalink.gmane.org/gmane.linux.network/197197
I also experience a situation on the mainline kernel where no link is
detected upon plugging in the cable.
--
You received this bug notification because you are a
Peter Wu, it would help greatly if you filed a new report as outlined in
#13.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310798
Title:
JMicron JMC250 ethernet: networking always disconnected
I ran
sudo ethtool -s eth0 speed 100 duplex full
and the link came up. I did this well after signing on and was using wifi.
This is the first time I have used this ethernet controller with a
gigabit network, normally I use the laptop with wifi.
--
You received this bug notification because
Caysho, thank you for your comment. So your problem and hardware may be
tracked, could you please file a new report with Ubuntu by executing the
following in a terminal while booted into the default Ubuntu kernel (not a
mainline one) via:
ubuntu-bug linux
For more on this, please read the
Alex Cabal, thank you for reporting this and helping make Ubuntu better.
Could you please test the latest upstream kernel available from the very
top line at the top of the page (the release names are irrelevant for
testing, and please do not test the daily folder) following
Yes, sudo ethtool -s eth0 speed 100 duplex full solved the problem.
This might be a driver's problem. When the box is turned on, the light on the
switch is on. But when Ubuntu starts booting, the light goes off.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Jim, I solved the issue by disabling gigabit ethernet on the network
card with:
$ sudo ethtool -s eth0 speed 100 duplex full
This command has to be run on startup.
Here's the relevant lshw -c if you're still interested, run after the
above fix:
description: Ethernet interface
product:
I'm more interested in what it looked like before the fix, I guess -
in my case, the card was just never aliased to eth0 at all, and was
marked DISABLED on boot. All I had to do to mine was ifconfig up p1p1
(it was being detected as p1p1, and not aliased to eth0 or
ethanythingelse) and it was
Have you made any progress on this since then? I tried your workaround
from post 37 of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880316
(using ethtool) but it didn't fix anything. I'm at a loss here.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Alex, please sudo lshw -c network and post output.
On my Trusty system, the card showed up as there but disabled - finding
it with lshw -c network allowed me to ifconfig up the device and truck
right on from there with no issues (though with a funny devicename -
p1p1 instead of eth0, but who
Workaround over here. I don't know why, but the device just doesn't get
named eth(x), it gets named p1p1 or similar, and doesn't get
automatically entered into /etc/network/interfaces.
I did lshw -c network on a new Trusty x64 Server install on my Gazelle
Pro p9 laptop, and it showed the JMC250
correction: my laptop's a gazprop6, sorry 'bout the typo/braino.
Very definitely a JMC250 chipset wired ethernet controller in it,
though. Didn't autodetect during the installer process (though the
wireless did), didn't come up on first boot (and wouldn't, until I'd
manually run ifconfig p1p1 up
*** This bug is a duplicate of bug 880316 ***
https://bugs.launchpad.net/bugs/880316
** This bug has been marked a duplicate of bug 880316
Ubuntu installer can't setup network on Shuttle XS35GTV2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 880316 ***
https://bugs.launchpad.net/bugs/880316
This is not a duplicate, bug #880316 was solved in the comments (see
comment #4 and #5) because the drivers weren't included in the
distribution at all.
The fact that the drivers are totally broken deserves
19 matches
Mail list logo
