Re:*** RECOVERED EMAIL ***: Re: more Have Netgear FA310TX eth0 card/trying to set apt source
I did receive this email. Not sure what "recovered email" indicates. My card
is not recognized at all by the system. lsmod shows tulip loaded but 0
devices using it. Remember, this box worked fine as a SQL server under Win2K
server, so it's not a basic hardware/router issue. It's a tulip/Debian
issue.
I tried a reinstall to attempt to force the newer tulip driver from the
floppy that came with the NIC to load. No luck. Apparently the directories
on the floppy weren't structured properly to use during an install. I am
leaving town for a couple of weeks so I have to put this on hold but I am
going to try to replace the tulip driver currently installed with the tulip
driver on the floppy. That ought to be an "educational" experience!
I don't know how to build a kernel without using the installer so that's not
an option yet. I thought I'd master a few more basics first like how to get
the @$%$#^ thing to print. Being able to find my ethernet "local" HP 4MV
from one of my working installs would be a good start.
Sorry for the frustration. I just hate spending so much time to acheive
basic functionality. I have so many other demands on those hours! Maybe
that's why more women don't use Debian.
Sivea
----- Original Message -----
From: "Steve Juranich" <sjuranic@ssli-mail.ee.washington.edu>
To: "Sivea Key" <siveakey@attbi.com>
Cc: "Kevin C. Smith" <smithkevinc@mchsi.com>; "Debian List"
<debian-user@lists.debian.org>
Sent: Thursday, July 11, 2002 11:31 AM
Subject: *** RECOVERED EMAIL ***: Re: more Have Netgear FA310TX eth0
card/trying to set apt source
> When I installed potato on my new computer, I had a terrible time with the
> tulip driver (2.2r6, or was it r5?). I had to bring my computer in to
work,
> me and one of the sysadmins figured out that the driver was buggy. After
I
> rebuilt the kernel, everything worked just fine.
>
> The problem I was experience was that I wasn't getting any DHCPOFFERs from
my
> ISP. Actually, I probably was getting them, but tcpdump didn't show any.
The
> same computer worked fine under M$, though (well, as fine as any computer
> using M$ can work).
>
> Have you used tcpdump on the interface yet? Is your NIC hearing anything
at
> all? My problem was that it was broadcasting fine, but it wouldn't
receive.
> If that's the case, a kernel rebuild might be worth the effort.
>
> Good luck.
>
> --------------------------------------------------------------------------
> Stephen W. Juranich sjuranic@ee.washington.edu
> Electrical Engineering http://students.washington.edu/sjuranic
> University of Washington http://ssli.ee.washington.edu/ssli
>
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
>
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: