lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 13 Jan 2012 13:43:58 -0500
From:	Paul Gortmaker <paul.gortmaker@...driver.com>
To:	Michael Mueller <malware@...nline.de>
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH] Making de2104x working with BNC connection on 21040 chipset

On Thu, Jan 12, 2012 at 5:52 PM, Michael Mueller <malware@...nline.de> wrote:
> Hi,
>
> while I recently updated an older machine to the latest Debian
> distribution which included updating the kernel from 2.4.x to 3.0 the
> tulip driver did stop working for my network card. The replacement
> driver de2104x did initialize the network interfaces but no transmission
> was possible.

Did you try the original de4x5.c driver?   I believe it was all that existed
back in the 2.4 vintage, and I think it was kept around just to keep old
cards that didn't like the "new" tulip driver working.

Paul.

>
> Digging into it I found the de2104x driver just assumes there is no BNC
> transceiver on a card using the 21040 chipset. So I extracted the
> correct configuration values from the old tulip driver and removed some
> sanity checking which denied setting the transceiver to BNC. Now I can
> use the driver by just setting the correct transceiver using ethtool.
>
> A patch against 3.0 is appended. It should apply against more recent
> versions too since there was not the lot happening for this old driver,
> but for the relocation of the files from drivers/net/tulip to
> drivers/net/ethernet/dec/tulip.
>
>
> Michael
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ