Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!daffy!uwvax!uwm.edu!math.ohio-state.edu!howland.reston.ans.net!news.sprintlink.net!news.onramp.net!lerami!rwsys!nemesis!uhclem From: uhclem@nemesis.lonestar.org (Frank Durda IV) Subject: Re: 2.0.5 screen problems after upgrade (no interactive response) X-Newsreader: Tin 1.1 PL5 Organization: The Big Blue Box Message-ID: <DC3II1.Drp@nemesis.lonestar.org> References: <3u7cuq$bb0@agate.berkeley.edu> Date: Sat, 22 Jul 1995 02:20:24 GMT Lines: 23 [0]John Vorstermans <john@atlantis.actrix.gen.nz> wrote: [0]I created a boot floppy and managed to boot up fine except when it [0]got to the point where the colourful initial configuration screen [0]was susp[osed to pop up I was simply faced with a blank screen. I [1]Jordan K. Hubbard (jkh@violet.berkeley.edu) wrote: [1]Hmmm. That's weird! Have you tried disabling all the devices in the kernel [1]that you don't need (boot with -c and use the `disable' command)? It's [1]entirely possible that the first "probe all devices" scan that sysinstall [1]does is wedging up your particular system. Try disabling COM3 and COM4 detection. I have discovered several video systems (mostly on Intel MLBs) that use the I/O ports that other people use for COM3 and/or COM4. The COM3/COM4 probe could be scrambling the video chips brains. If you can't disable COM3/COM4 by themselves, try disabling all serial I/O and see if things improve. Frank Durda IV <uhclem@nemesis.lonestar.org>|"The Knights who say "LETNi" or uhclem%nemesis@fw.ast.com (Fastest Route)| demand... A SEGMENT REGISTER!!!" ...letni!rwsys!nemesis!uhclem |"A what?" ...decvax!fw.ast.com!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983