Bug#253683: Re: Bug#253683: TC1
Hi Joey and Martin,
I found the problem! During the install, the [!] Detect network
hardware screen comes up. The wording on it includes:
An example string looks something like "IRQ=7 IO=0x220"
It appears the routine parsing this entry does not recognize
uppercase IRQ and IO as shown in the example. I finally tried
lowercase "irq=3 io=0x340" (in my case) and it worked! Tried it 3
times, alternating between upper and lower case tries. So the
routine should either be changed *or* the example changed to match
reality (along with a note to use lowercase).
I'm somewhat of a newbie with Debian releases ... and Linux in
general, although I've dabbled with it for a couple years half
heartedly and years ago had a few years experience with Unix SysV.
Please see my comments below interspersed between your questions:
On 10 Jun 2004 at 14:23, Joey Hess wrote:
> Don Jackson (AE5K) wrote:
> > Output of lspci: n/a
>
> Why did you not provide this information? Unless your NIC is not a PCI
> device, it's very important information we need to solve your problem.
Moot point now, but my NIC is ISA. In addition, how do I run
"lspci"? Changing to a 2nd virtual console and using "BusyBox", it
comes back with "not found".
In fact when I was going thru the installation and stalling at the
NIC driver screen, I didn't realize I could open a 2nd console ;-)
Therefore, most of stuff in the "template" for reporting the problem
is "n/a" since I didn't know I could access the stuff.
> Do you have any messages from dmesg that might be useful in determining
> why the kernel isn't finding your NIC even when you load the right
> module with the right settings?
Once I found I could open the 2nd console to get this, yes dmesg gave
me the hint at the end of the file:
ne.c: You must supply "io=0xNNN" value for ISA cards.
Note the lowercase "io". That gave me the idea to try lowercase.
On 10 Jun 2004 at 19:25, Martin Michlmayr wrote:
> Can you open a shell on the 2nd virtual console and check if the
> module has successfully been loaded?
Thanks for the hint! Yes, I then tried it and using "lsmod" did not
see "ne" listed. I assume I was using the correct command. (?)
Anyway, thanks for your prompt responses -- I proceeded without
further hitches and just about ready to boot the new install for the
first time.
Further comments: the script instructions are a little confusing in
the wording in the partitioning area for inexperienced users. I have
some suggestions, but don't think this bug report is proper channel
to make them.
Regards,
Don
Reply to: