internet connection, but the bios beat me.
The new kit they supplied is fine so at least there's a happy ending.
- Original Message -
From: "David Wright" <[EMAIL PROTECTED]>
To: "Patrick Kirk" <[EMAIL PROTECTED]>
Cc: "debian-user"
Sent: Fri
Quoting Patrick Kirk ([EMAIL PROTECTED]):
> [snip]
>
> > patric >Imagine how I felt as the CD drive that the Debian CD choked on
> worked
>
> choked on - that is - it died on contact with loadlin.
Loadlin? That's DOS software isn't it? And Real DOS, not DOSbox.
You were running it from a Real DO
[snip]
> patric >Imagine how I felt as the CD drive that the Debian CD choked on
worked
choked on - that is - it died on contact with loadlin.
> patric >flawlessly - creaking 2-speed brute! The cards installed
flawlessly on the
> patric >same IRQs that failed under Linux. Its a real choker tha
On Fri, 18 Feb 2000, Patrick Kirk wrote:
patric >Imagine how I felt as the CD drive that the Debian CD choked on worked
patric >flawlessly - creaking 2-speed brute! The cards installed flawlessly on
the
patric >same IRQs that failed under Linux. Its a real choker that these old
boxes
patric >w
In the end, I installed 4 different NICs all of which worked but all of
which prevented a second card being loaded. After over 10 hours, I decided
that this had made the small move from being a challenge to being an
obsession. I gave up and put the Win98 CD in to restore it.
Imagine how I felt a
On Thu, 17 Feb 2000, Jonathan Heaney wrote:
> Phil Brutsche wrote:
>
> :
> :
> :
> :
>
> > If the ethernet card gets a 255 IRQ, then it's possible that you need to
> > change the setting that looks something like "PnP OS" (that's how it
> > appears on my computer) to "None" or "No". Setting "
Phil Brutsche wrote:
:
:
:
:
> If the ethernet card gets a 255 IRQ, then it's possible that you need to
> change the setting that looks something like "PnP OS" (that's how it
> appears on my computer) to "None" or "No". Setting "PnP OS" to "On" or
> "Yes" only makes sense with Win95 and it's der
I had a similar problem with a pci scsi card in an old 486. It
would not let me leave a blank pci slot. The card had to be installed
next to the video card which was in the first pci slot.
hth
jim
> Would modprobe ne2k-pci io=0x300 irq=11 work when:
>
> cat /proc/io...
> -001f : dma1
> 00
A long time ago, in a galaxy far, far way, someone said...
> Would modprobe ne2k-pci io=0x300 irq=11 work when:
For PCI cards (indicated by the fact that you're using the driver
ne2k=pci) you don't need to bother with io= and irq= statements on the
command line. All that information is read from
The problem is the hardware. The PCI bios cannot assign a free
interrupt to the card in the PCI slot. Therefore it assigned a
value of 255 to it.
Try to assign a interrupt to the pci device by changing the
bios
settings.
Frank Dost
rarp
>
>
> - Original Message -
> From: "Ron Rademaker" <[EMAIL PROTECTED]>
> To: "Patrick Kirk" <[EMAIL PROTECTED]>
> Cc:
> Sent: Thursday, February 17, 2000 3:16 PM
> Subject: Re: PCI BIOS problems
>
>
> > If the card can
Message -
From: "Ron Rademaker" <[EMAIL PROTECTED]>
To: "Patrick Kirk" <[EMAIL PROTECTED]>
Cc:
Sent: Thursday, February 17, 2000 3:16 PM
Subject: Re: PCI BIOS problems
> If the card can work on irq 11 and io 0x300 it should work because both
> the irq as
If the card can work on irq 11 and io 0x300 it should work because both
the irq as the io adress aren't taken. You should try it...
Ron
On Thu, 17 Feb 2000, Patrick Kirk wrote:
> Would modprobe ne2k-pci io=0x300 irq=11 work when:
>
> cat /proc/io...
> -001f : dma1
> 0020-003f : pic1
> 0040-
Would modprobe ne2k-pci io=0x300 irq=11 work when:
cat /proc/io...
-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : npu
0170-0177 : ide1
01f0-01f7 : ide0
02c0-02df : NE2000
02f8-02ff : se
So you have 2 ne compatible cards in that computer?
Have you tried loading in ne2k-pci with irq=XX io=0xXXX arguments that
make sense? (irq=255 is something I think is IMPOSSIBLE because as far as
I know irq go between 0 and 16 (16 not included), in other words 4 bit not
8).
Ron
On Thu, 17 Feb 2
There is a reason why that could fail: irq 11 or io 0x300 could be taken
already, you can check that by: cat /proc/interrupts and cat /proc/ioports
There you see what interrupts and io adresses are taken by your devices,
if irq 11 and io 0x300 are not taken... there would be no reason that that
wou
Hi Ron,
The ne.o module loads cleanly. Its the false reading on ne2k-pci that kills
me. I have to leave ne.o installed as its the card I've telnetted in from
at work.
Patrick
If I take out the PCI card and put in a second NE2000 with jumpers set to
io=0x300 and irq=11, is there any reason why that would fail? Getting
desperate here.
Patrick
>
> >From /etc/modules
> #auto
> ne
> ne2k-pci
> ip_alias
> ip_masq_quake
> ip_masq_raudio
> rarp
>
>
>
>
> - Original Message -
> From: "Ron Rademaker" <[EMAIL PROTECTED]>
> To: "Patrick Kirk" <[EMAIL PROTECTED]>
> Cc:
>
-pci
options ne io=0x2c0 irq=10
path[boot]=/lib/modules
>From /etc/modules
#auto
ne
ne2k-pci
ip_alias
ip_masq_quake
ip_masq_raudio
rarp
- Original Message -
From: "Ron Rademaker" <[EMAIL PROTECTED]>
To: "Patrick Kirk" <[EMAIL PROTECTED]>
Cc:
Sent: Thurs
An irq of 255 ? Can't be!!
io of 0x4000 ?
You are using the ne driver... that one is for ISA ne compatible network
cards and should ALWAYS be used in combination with the option io=0x
and optional with irq=XX
I guess you should try using the ne2k-pci driver, or insert the module
with
21 matches
Mail list logo
