Ray Olszewski wrote:
>
> At 12:03 PM 8/6/00 -0400, Dances with Turtles wrote:
> >I can not get my new linksys 10/100LNETX card to be recognized by
> >Linux. It works fine under windows. Let me also
> >state that my prior Linksys ether16 ISA card was working perfectly prior
> >to my 'upgrade.'
> [details deleted]
>
> Well ... your more detailed post makes it clear why you're finding this
> process frustrating. You've pretty much tried almost everything I'd say to
> check. I'm left with 3 thoughts ...
>
> 1. You say the card works under Windows but not under Linux. Does this mean
> you have a dual-boot host? If so, the BIOS may be set wrong for Linux -- it
> should say NO for the Plug-and-Play OS question.
>
Well, I thought that you nailed it on the head as I wasn't aware that
the bios would be causing a problem, and I never
gave it a thought since my last ethernet card was PNP. But, after
turning PNP OS aware off, there was no difference.
> 2. Have you tried the card in more than 1 slot? In my experience (not just
> with Linksys), some card/slot combinations work, others don't.
>
Yes, multiple slots. I also tried setting the priorities on the slots
(knowing that this was slim to no help). I even added a winmodem so as
to change the interrupt and IO address. It changed them, but didn't
resolve the problem.
With that in mind, I'm thinking that this isn't a 'random' chance that a
resource is in use, but something that I've selected incorrectly within
the building of the kernel, or the modules.
> 3. You probably did this right, but just in case ... you are using a a tulip
> module from the same compile as the kernel, right? Not just the same kernel
> humber -- the same actual compile.
>
I think I understand this. To answer, I always rebuild the kernel and
the modules together. Pain in the arse, but it has to be done or I
would definately have a problem. :)
> These suggestions are ... to use your own word ... "pathetic". Afraid it's
> all I can think of, though.
>
But your responses are most welcomed and very good, even if they don't
resolve my issue, they definately would help many others, especially the
PNP OS and having another ethernet card built into the kernel, and
mixing kernels with network devices with modules. :)
> Getting the wrong manufacturer name in the lspci output is a commonplace
> problem and indicates nothing of consequence. My Lynksys shows up as a
> "Lite-On", for example.
>
I'm glad to hear that. I was a bit worried but not too much. I had
tried a linux diag utility, I think that it was
called etherdiag or something, and it reported something totally
different, AND it told me my MAC address was all high-values
(FF-FF-FF-FF-FF-FF-FF-FF). The "IPCONFIG -a "command under Windows
showed that this wasn't true.
I guess that I'm done to rebuilding the init_modules routines and see
what it is reporting. I hate debugging at
that level, but ....
I'll let you know what I find out.
> --
> ------------------------------------"Never tell me the odds!"---
> Ray Olszewski -- Han Solo
> Palo Alto, CA [EMAIL PROTECTED]
> ----------------------------------------------------------------
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to [EMAIL PROTECTED]
> Please read the FAQ at http://www.linux-learn.org/faqs
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
