Vojtech Pavlik wrote:
> On Fri, Mar 12, 1999 at 05:32:31PM +0100, Ulf Jaenicke-Roessler wrote:
>
> Basically, the Realtek people are right. The W9x simply removes the value
> for the interrupt number of the ethernet card from the PCI config space
> register of that card.
Who knows why Windows does this :( I don't see any sense in it.
> The number was written there by the BIOS, while initializing the PCI
> subsystem to tell the operating system which IRQ was assigned to the
> card.
Well, as I wrote in my original message, if I use BIOS access for the PCI
card, it can be seen, that the I/O information is destroyed too.
There was one way, I could keep the IRQ information. I needed to disable
'interrupt steering' in Windows. However, it didn't restore the I/O
information and there were certain problems in Windows itself (although I
can't remember exactly - it's related to the PnP support of Windows, but
not only), so I decided to stick with the default behaviour.
I hoped, that there might be a way to trigger the BIOS to rewrite the
information about I/O and IRQ.
> This is a problem of W9x and, as far as I know could only be fixed by
> re-assigning all the interrupts to PCI cards upon Linux boot, which doesn't
> happen now (though is possible to happen in the future).
This would be great.
> So, the only solution for you now is to mark the linux batchfile as needing
> a different configuration in W98, so that W98 reboots prior to running it.
Yes, but actually I tried to circumvent rebooting, because it's faster.
> Or, alternately, throw away W98 ;)
Unfortunately this is not possible.
Greetings,
Ulf
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/