On Thu, 2015-05-14 at 16:03 +0100, G.W. Haywood wrote: > Hi there, > > When I upgraded my laptop from Wheezy to Jessie the JME driver failed. > > When I was running Wheezy the Debian-supplied version did not work at > all, leaving me with no Ethernet connection. So I would routinely > replace the JME driver supplied by Debian with one from JMicron which > I compiled myself. > > A week or so ago, when I upgraded to Jessie, the Debian-supplied driver > again failed, but the driver which I have been using with Wheezy does not > compile under Jessie's updated build system. It would be much easier to > switch to a different distribution than to find out why it won't compile > and fix it, so I trawled the 'net with the search engines and found this > Ubuntu list post which describes a workaround: > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880316 > > This workaround is to reduce the speed at which the interface operates > from 1Gbit/s to 100Mbit/s. Obviously to find this post I had to use a > different a computer, since mine wasn't able to connect to the network. I had a look at what JMicron's driver does differently from the version included with Linux. It appears that it periodically checks for link failure and then automatically applies this workaround. I could try cleaning up the automatic workaround a bit and submitting upstream, but I doubt that it would be accepted. In short, this is faulty hardware and you know how to work around it. I think there nothing left to be done. > 'Upgrading' my laptop to Jessie felt like a definite downgrade as it > prevented me from using my computer. So I'd call this bug SERIOUS. Sorry but I do not agree. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part