Re: Debian Installation ideas
David Bristel <targon@targonia.com> writes:
> After a rather annoying fight while installing slink, it struck me as odd that
> we can't choose which modules to load or to exclude during the initial install
> from floppy or from CD-ROM. I got bitten by the WD-7000 detection on an Intel
> Venus motherboard. I'm sure that a number of you have experienced the problem
> where the WD-7000 auto-probe will lock up a system. I personally don't know
> anyone that has such a controller. Since this is a built-in, and not a module,
> there's no easy way to work around the problem. The second CD works, but
> doesn't have Adaptec support which I need on this SCSI based system. So, why
> can't we make the WD7000 a module which can be installed the way other devices
> can be? Do we REALLY need to install a root partition before installing a
> module which is already there on the CD waiting for us to say we want to use it?
> The Adaptec driver being in the base kernel makes sense because there are so
> many people with Adaptec SCSI controllers, but the WD7000?
No, it doesn`t. :)
Every time I bootet the adaptec without speed limitations my system
had scsi errors. Well, I found out that the last drive didn`t
terminate the scsi properly and switched it with another. Now the scsi
works, but before I had to boot with special flags for the scsi
controler to make it run asynchron and slow.
Having the scsi as a module allows a easier way to set parameters,
since you will be asked for them. Also, if such an aproach is taken,
ALL things that can be module, must be modules.
Also, to prevent that one has to select millions of modules just for
installation, a autodetection (e.g. loading each module in turn)
should be provided, but the probed modules should be recorded onto the
bootdisk, so that on the next boot only modules that worked are loaded
and the module that hung the system is skipped.
EasyLinux, for example, does that, its great.
May the Source be with you.
Goswin
Reply to: