Mirko Scurk wrote: > > Bob McGowan wrote: >> Mirko Scurk wrote: >> >> I have installed a recent Debian (it's been a while, not sure if I used >> etch or not, maybe sarge, but definitely not woody), on an ALR 486 VEISA >> system and it ran fine. The biggest HW difference besides manufacturer >> and EISA bus is the memory. Mine has 48MB. >> >> I'd suggest you see if you can increase the memory on your system. >> >> Meanwhile, I'd also suggest doing a reinstall, if possible, wiping the >> disk by not preserving current partitioning. >> >> I'm suggesting that you select the manual partitioning method (hoping >> that you have enough knowledge to deal with it ;-) because you may need >> to increase the size of the swap partition. I'm not sure if memory is >> the issue here (init respawning errors could be due to too little >> memory, but also could be due to the read-only filesystem, to problems >> with the tty interface to the VGA card, files not being found because of >> an install error, etc.) but increasing the swap may at least get you up >> and running. I have no idea what would work in this case. Your hard >> disk is small enough that too large a swap would make installation a >> problem. Perhaps something in the range from 64MB to 100MB would be a >> good choice? >> >> The second thing I'd suggest is to install the minimal system. It's >> been long enough since I touched woody that I'm not sure if things >> looked the same then or not, but in sarge/etch, there's a 'task select' >> section during install that lets you choose some basic setups. By >> default, this selects the base system *and* desktop environment >> (Gnome/KDE/...). *Uncheck* the GUI desktop install (you can always add >> it back later). Just try to get a basic system installed and working. >> >> Good luck ;) >> >> Bob >> > > Increasing memory is not an option right now. > I've tried all from above with no luck. > I'm almost sure that problem is with ISA network card. I installed slack > again and everything was OK until I tried to load ewrk3 (module with right > options io=0x320 and irq=5). After that proc wasn't mounting any more and > root was mounted RO. > When I pass parameters to lilo via boot prompt everything is working OK > again. I tried to pass parameters via lilo.conf append but never got it to > work. Somewhere I found that append isn't working for modules?? > > > -- > Mirko Scurk >
-- Mirko Scurk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]