[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Device detection?



That's not what im talking about. There are some modules which work just
fine when you modprobe them, psaux comes to mind. And i'm sure there are
others. Im not suggestting scanning for *everything* just stuff that is
fairly simple to detect.

On Tue, Mar 09, 1999 at 09:14:42PM -0500, Brandon Mitchell wrote:
> On Tue, 9 Mar 1999, Stephen Crowley wrote:
> 
> > On Tue, Mar 09, 1999 at 07:37:49PM +0100, Wichert Akkerman wrote:
> > > Previously Stephen Crowley wrote:
> > > > Yes, I was wondering if it would be possible to do a brute force scan for
> > > > some older legacy hardware. Just cycle through the i/o and irq ports for
> > > > some commonly used hardware. Some devices might lock up on this though, so
> > > > they would have to be installed manually.
> > > 
> > > No way, this will certainly crash lots of systems..
> > 
> > Of course, that's why I said it should only be used on devices which wont
> > lock up systems.
> 
> But how do you auto detect a device that locks up your system when you
> probe for it?  This is the reason for windows throwing you into safe mode,
> no auto detection because you probably crashed from a misguided auto
> detect.  I prefer linux's way of telling the kernel what you have.  But, I
> guess someone could make a package that just mod-probes the heck out of
> your system with every option until you crash or the modprobe succeeds.
> 



-- 
/-----------------------------------------------------------\
|Stephen Crowley      stephenc@wf.net, crow@debian.org      |
|Debian GNU/Linux     http://www.debian.org                 |
|GPG Key              http://va.debian.org/~crow/public.key |
\--- 8A8B 3B82 6EA7 CF4E 01A5  5B21 B378 981D D2E1 0D85 ----/
     


Reply to: