Re: SUSE 9.2 Realtek RTL 8139 Network Card Please help!

From: Cousin Stanley (CousinStanley_at_HotMail.Com)
Date: 03/28/05


Date: Mon, 28 Mar 2005 13:20:34 -0700


| Strange, using rtl8139 based cards for some purposes since ages,
| they aren't the fastest but halfway reliable and cheap.
|
| Can't remember any problem with them. Not with the rtl8139 module
| or the 8139too driver in later kernels, other then one or another
| card breaking after some years and needing to be replaced.
| ....
|

Michael ....

   Thanks for the info regarding the 8139 NIC ....

   Aside from 2.6 kernel connection problems,
   and initial problems installing a driver
   for Win98, the 8139 NIC has worked very well
   here for about a year now ....

   Attempting to install a Realtek 8139 NIC
   into a 5 year old Compaq running Win98_SE
   is what eventually led me to pursuing Linux
   as an alternatative for an operating system,
   eventually ending up with a dual-boot machine ....

     o Had 2 new 8139 NICs available ....

     o Stuck 1 in the Compaq/Win98 box ....

     o Machine wouldn't boot, no-way ....

     o Removed the NIC ....

     o Machine still would not boot into DOS/Windows,
       even from Win98 boot floppy ....

     o Stuck in a Knoppix 3.2 CD,
       and machine booted with no problem ....

     o Stuck other new 8139 NIC in machine ....

     o Booted with Knoppix 3.2 ....

     o 8139 NIC recognized, no problem ....

     o Configured aDSL modem/router via net interface ....

     o All internet connections were flawless
       with the 8139 NIC under Knoppix 3.2 ....

     o Install Knoppix 3.2 to hard-disk
       to dual-boot with Win98_SE ....

     o Boot into Win98_SE ....

     o Repeated attempts to install 8139 NIC driver
       into Win98 from manufactuer's CD all fail ....

     o After 2 days of failures to install drivers
       from the install CD's Win98 directory,
       tried the install CD's Win95 directory ....

     o Win95 flavor of 8139 NIC drivers install
       under Win98 on the first attempt and function
       perfectly ....

The hassle with trying to install a driver
for a fairly common NIC under Win98
when it was automatic and no hassle at all with Knoppix,
along with other common Win98 problems, at that point
made the decision to pursue Linux a no-brainer for me ....

Tried Mandrake, a few different Knoppix HDD installs,
and eventually ended up with dual-boot Win98/Debian
at the end of July 2004 ....

I've wondered if compiling the 8139 driver locally
here under kernel 2.6, perhaps with some alternate
compile options might help ....

-- 
Stanley C. Kitching
Human Being
Phoenix, Arizona


Relevant Pages

  • Re: [SLE] Has anyone tried the new ATi Linux driver, version 8.14.13?
    ... ATI cards but will not give any 3d performance whatsoever. ... The radeon driver is installed by default, ... >>(stupid easy SINGLE driver install for most of their models (by ...
    (SuSE)
  • Poweredge 700
    ... I have installed fedora core 1 on a poweredge 700 and the network card is ... install needs a driver disc ... I currently have 6 linux desktops with ATI cards in them (Radeon ...
    (Fedora)
  • Re: Any SDIO or CF wifi card for CE5 - that has been proved to wor
    ... driver CAB for the right processor type placed in the ActiveSync directory. ... I had tried the WM5 cab, but it immediately poped up a dlg box say it was ... not a valid CE file image - it happened with the other cards to so I ... So a WM5 cab file should install then -any ideas what it giving this ...
    (microsoft.public.windowsce.platbuilder)
  • RE: System Cloning and Driver
    ... There are two Intel PRO 1000 Ethernet cards on board. ... Intel driver and the other is our own driver. ... But if I install both of the ... It seems it has something to do with System Cloning. ...
    (microsoft.public.windowsxp.embedded)
  • Virtual Webcam followup, win98 install issues
    ... based on the TESTCAP DDK sample. ... Its working perfectly on both Win2k/xp and Win98. ... However, while on 2K/XP, i can install the driver automatically using ...
    (microsoft.public.development.device.drivers)