Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!inferno.mpx.com.au!nsw1.news.telstra.net!news.telstra.net!news-out.internetmci.com!newsfeed.internetmci.com!feed1.news.erols.com!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!rill.news.pipex.net!pipex!tank.news.pipex.net!pipex!news.utell.co.uk!usenet
From: brian@shift.lan.awfulhak.org (Brian Somers)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Kernel config problem
Date: 25 Mar 1997 11:38:02 GMT
Organization: Awfulhak Ltd.
Lines: 62
Message-ID: <5h8deq$lj1@ui-gate.utell.co.uk>
References: <5h4i5b$djg@chronicle.concentric.net>
Reply-To: brian@awfulhak.demon.co.uk, brian@utell.co.uk
NNTP-Posting-Host: shift.utell.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Newsreader: knews 0.9.8
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:37806
In article <5h4i5b$djg@chronicle.concentric.net>,
Slater@cris.com (Rick Slater) writes:
> I recently purchased a Dell Dimension XPS M200s. It is
> a 200 MHz pentium with EIDE drive and an IDE cdrom drive.
>
>
> I was able to boot directly from the FreeBSD 2.1.0 cdrom
> and install FreeBSD without any difficulties. However,
> the generic kernel which is installed doesn't support
> IDE cdrom drives, and so I rebuilt the kernel to include
> that support. I used a configuration file from another
> machine (based on a 486 chip and with only ISA slots),
> but something very strange happened: The screensaver
> not only blanked the screen; it also "blanked" the
> keyboard!
>
> Once the screen blanked, none of the keys which should
> have lit an l.e.d. did anything (Num lock, Caps lock,
> ...) and I couldn't get control back without hitting the
> reset switch (ctl-alt-del failed too).
>
> I switched back to the generic specification file and
> added the IDE cdrom support to it. The new kernel
> handles a blanked screen correctly.
>
> I have no scsi devices on the machine, but when I start
> removing them from the kernel, I get right back into the
> keyboard problem.
>
> This is driving me nuts. Has anyone run into this kind
> of behavior before? If you can point me in the right
> direction, you'd save me an awful lot of time.
>
> Right now, it appears that I may have no choice but to
> remove one scsi device at a time, rebuild the kernel,
> and test the screen blanker after each build.
>
> That's about as much fun as watching grass grow.
>
> Thanks for any assistance.
>
> Regards,
> Rick Slater
>
> Correct email address: Rslater@concentric.net
>
> ==
> Banner email address changed to avoid spam. All
> mail to it will bounce.
Sounds like the ps/2 problem again - your machine has a ps/2
mouse I'll bet. You may be able to fix your problems by
removing ps/2 mouse support (I'm not sure), otherwise you
can get http://www.freebsd.org/~brian/setcon.tgz which allows
you to switch consoles remotely (unfreezing the keyboard).
It looks like these problems have been fixed in 2.2.
--
Brian <brian@awfulhak.demon.co.uk> <brian@freebsd.org>
<http://www.awfulhak.demon.co.uk>
Don't _EVER_ lose your sense of humour !