Re: HELP! Install problem. How to free I/O locked by "reserve=..." in boot params?
On Wed, Mar 08, 2000 at 03:04:03AM +0100, Bjoern Brill wrote:
>
> Have you tried to insert the wd module with parameters (io=0x280 etc.)?
> I think it doesn't care if resources are reserved or not in this case.
Hmmm, I used the "insmod wd io=0x280", and it resulted in the mentioned
error.
However I've checked it in my home system. I've append the "reserve=0x300,1"
line to the lilo.conf (I have ne2000 at 0x300).
In this case system starts correctly, then I switched off the eth0
interface and removed the ne module.
After I tried: "insmod ne", I got:
#insmod ne
ne.c: No PCI cards found. Use "io=0xNNN" value(s) for ISA cards.
/lib/modules/2.0.36/net/ne.o: init_module: Device or resource busy
However, when I typed "insmod ne=0x300", I got:
#insmod ne io=0x300
ne.c:v1.10 9/23/94 Donald Becker (becker@cesdis.gsfc.nasa.gov)
NE*000 ethercard probe at 0x300: 00 c0 df 48 fa ef
eth0: NE2000 found at 0x300, using IRQ 11.
The 0x300 area is still reported in /proc/ioports as:
0300-0300 : reserved
(even when the module is loaded!)
So I can see a few possibilities:
1) The modules ne and wd differently handles the reserved I/O space
2) There is a difference in this subject between 2.0 and 2.2 kernels
(I use 2.0.36 at home, and 2.2.14 in the failing machine)
3) This is not I/O space, what causes the "resource unavailable" error.
Unfortunately the insmod gives very poor information about the
reasons of failure (even the -v switch does not help).
Thanks for suggestions. Tomorrow I'll try to investigate the problem
more thoroughly.
--
Wojciech Zabolotny
http://www.ise.pw.edu.pl/~wzab
http://www.freedos.org Free DOS for free people!
Reply to: