JMicron JMC250 ethernet: networking always disconnected

[Alex Cabal]

What is expected in 14.04 is ethernet networking works when cable connected. What happens instead is it always shows "disconnected", even when cable connected.

In Ubuntu 12.04, this same ethernet controller also exhibited the same problem. However it was fixable by downloading and manually compiling a new version of the jme drivers from here: ftp://driver.jmicron.com.tw/Ethernet/Linux/jmebp-1.0.8.5.tar.bz . In 14.04, the above 1.0.8.5 driver no longer compiles and is thus not installable. I tried downloading and compiling the latest source for the driver from https://github.com/torvalds/linux/blob/master/drivers/net/ethernet/jme.c. This driver does compile, but after installation still doesn't work, with the wired network status always showing "disconnected".

Output of dmesg | grep jme
[ 2.044151] jme: JMicron JMC2XX ethernet driver version 1.0.8
[ 2.044209] jme 0000:02:00.5: can't disable ASPM; OS doesn't have ASPM control
[ 2.045351] jme 0000:02:00.5 eth0: JMC250 Gigabit Ethernet chiprev:23 pcirev:3 macaddr:80:ee:73:13:68:7d
[ 22.302804] jme 0000:02:00.5: irq 45 for MSI/MSI-X
[ 22.302930] jme 0000:02:00.5 eth0: Link is down
[ 22.328814] jme 0000:02:00.5 eth0: Link is down

WORKAROUND: The following terminal command provides 100 Mbps ethernet speed:
sudo ethtool -s eth0 speed 100 duplex full

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic]
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: alex 1540 F.... pulseaudio
CurrentDesktop: Unity
Date: Mon Apr 21 16:06:41 2014
HibernationDevice: RESUME=UUID=9a76734d-f4e5-48af-9ba2-c86f712f39d9
InstallationDate: Installed on 2014-04-18 (2 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Standard XS35
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=347d51ff-61a3-4f81-bcc4-125707703d1e ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-generic N/A
 linux-backports-modules-3.13.0-24-generic N/A
 linux-firmware 1.127
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/21/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: B10IE01
dmi.board.vendor: Shuttle
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Shuttle
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd03/21/2011:svnStandard:pnXS35:pvrToBeFilledByO.E.M.:rvnShuttle:rnB10IE01:rvrTobefilledbyO.E.M.:cvnShuttle:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: XS35
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: Standard

[Brad Figg (brad-figg)]

This change was made by a bot.

[Alex Cabal (acabal)]

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 a different bug--they were working for a brief while until 12.04, and they've been included in the distro since 12.04, they just don't work at all and they haven't worked for years.

[Jim Salter (jrssnet)]

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 as disabled, but with logical name "p1p1". Did ifconfig p1p1 up ; dhclient p1p1 and connected to my network and got an address immediately.

Added p1p1 to my /etc/network/interfaces, and I'm off to the races - just with a funny network adapter device name.

[Jim Salter (jrssnet)]

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 / added p1p1 to the /etc/network/interfaces file appropriately.)

[Alex Kibler (akibler16)]

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.

[Jim Salter (jrssnet)]

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 cares, really).

[Alex Cabal (acabal)]

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: JMC250 PCI Express Gigabit Ethernet Controller
       vendor: JMicron Technology Corp.
       physical id: 0.5
       bus info: pci@0000:02:00.5
       logical name: eth0
       version: 03
       size: 100Mbit/s
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm pciexpress msix msi bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=jme driverversion=1.0.8 duplex=full ip=192.168.1.2 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s
       resources: irq:45 memory:feaf8000-feafbfff ioport:dc00(size=128) ioport:d800(size=256)

[Jim Salter (jrssnet)]

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 fine, gigabit included.

[Wenjay Chang (wenjay-chang)]

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.

[penalvch (penalvch)]

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 https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested exactly shown as:
kernel-fixed-upstream-3.18-rc4

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Caysho (caysho)]

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.

[penalvch (penalvch)]

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 official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Peter Wu (lekensteyn)]

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.

[penalvch (penalvch)]

Peter Wu, it would help greatly if you filed a new report as outlined in #13.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Driuchatyi Mykola (druchaty)]

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.

[penalvch (penalvch)]

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.

[P.O.L. (pekka-linna)]

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 connection and the PC indicates that the ethernet cable is disconnected. When disabling EEE at that port, the PC connects immediately at 1000M.

When using "unmanaged" switches (I tried TrendNet TEG-S50g), the only solution I have found is the same as above: force the connection to 100 Mbit/s. There is no way to disable EEE (which the vendor calls "Greennet").

           sudo ethtool -s eth0 speed 100 duplex full.

The Trendnet unmanaged switch works fine at 1000M with Windows 7.

[P.O.L. (pekka-linna)]

Using Asus EeeBox PC EB1007 with 14.04 reinstalled and updated yesterday.