SCIENTIFIC-LINUX-USERS Archives

January 2009

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Keith Lofstrom <[log in to unmask]>
Reply To:
Date:
Mon, 26 Jan 2009 01:03:58 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (58 lines)
Keith wrote ...
> driver works fine in 5.2 .  The EEE also needed a patched 
> ethernet driver with 5.0, while the driver in 5.2 worked fine.

I spoke too soon.  After a reboot, the network went away - or else
I was not paying attention previously.  The EEE PC Box uses a
Realtek 8168B, but for some reason the (updated) SL5.2 kernel calls
for the 8169 driver, which does not work.  So I added rpmforge to
my yum repositories, then installed the dkms-8168 driver.  I'm not
sure I did everything right - during boot it talks about the driver
already being loaded - but it works now.  The steps:

1) With the network not working, I temporarily connected through a
USB-to-ethernet adapter, which automounted as eth2 when I plugged
it in.  I've used three different adapters in the past, all worked
out of the box. This time I used an ancient Farallon Netline PN976
( 07a6:0986 ADMtek, Inc. AN986 Pegasus Ethernet).  In the past I've
used a cheapo AirLink and a 3Com, model numbers not at hand.

2) I used firefox to go to   https://rpmrepo.org/RPMforge, clicked
"Using RPMforge" to go to https://rpmrepo.org/RPMforge/Using , then
clicked the "RHEL5 / CentOS-5 i386" rpm link.  That downloaded some
stuff that added RPMforge to the yum repositories.

3) I then did a "yum install dkms-r8168" and got a working driver.
eth1 came up, and I could unplug the USB-to-ethernet adapter.

I may have remembered something incorrectly.  Please correct me
if so.  I plan to add my notes to my wiki in a few days:

   http://wiki.keithl.com/index.cgi?SL5eee

So you can add stuff there in a week or so, too.

BTW, I plan to build the EEE Box to come up with a very simple
SL5.2 host OS, and two VMware guests, one full-featured SL5.2
(for surfing the web, vpn, ssh, and the usual applications) and
a Windows 2000 guest with Dragon Naturally Speaking Medical. 
The win2K guest will have networking, file sharing, browsers
etc. turned off).   Dragon will be used by my doctor wife for
dictating patient records, and I will do my damndest to keep
the Windows guest isolated from the internet to protect patient
privacy. 

Since there will be 3 OSes running, I needed more memory.  I
voided the warranty of the EEE by opening it up (no easy task,
look for instructions on YouTube) and installed 2GB of 667MHz
SoDIMM RAM to replace the 1GB that it came with.  I also replaced
the original 160GB XP drive with a 250GB Seagate SATA notebook
drive (not one of the drives with the bricking problem).

Keith

-- 
Keith Lofstrom          [log in to unmask]         Voice (503)-520-1993
KLIC --- Keith Lofstrom Integrated Circuits --- "Your Ideas in Silicon"
Design Contracting in Bipolar and CMOS - Analog, Digital, and Scan ICs

ATOM RSS1 RSS2