Date: Sun, 20 Apr 1997 21:20:03 -0700 (PDT) From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: freebsd-bugs Subject: Re: conf/3354: 2.2.1 Installation problems with Diamond SpeedStar64 Message-ID: <199704210420.VAA14032@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR conf/3354; it has been noted by GNATS. From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: pscott@netcom.com Cc: freebsd-gnats-submit@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: conf/3354: 2.2.1 Installation problems with Diamond SpeedStar64 Date: Sun, 20 Apr 1997 11:24:08 +0900 >>Number: 3354 >>Category: conf >>Synopsis: 2.2.1 Installation problems with Diamond SpeedStar64 >>Confidential: no >>Severity: serious >>Priority: high >>Responsible: freebsd-bugs >>State: open >>Class: sw-bug >>Submitter-Id: current-users >>Arrival-Date: Sat Apr 19 16:30:01 PDT 1997 >>Last-Modified: >>Originator: Paul A. Scott >>Organization: >>Release: 2.2.1 >>Environment: >N/A >>Description: >Attempting to install FreeBSD 2.2.1 (from Walnut Creek CD-ROM or floppy) I hav >e the exact same TWO problems as reported in conf/2775: > >1) On system 1, after kernel uncompresses, the screen goes completely >garbled. Look like running in graphics mode with completely messed up >character maps. Almost looks like static it's so garbled. This occurs with >Diamond Speedstar64 video card. Impossible to continue installation. This is because the video mode parameter table in BIOS is not organized in the standard way and the console driver syscons gets confused. I discussed this matter with Soeren. I don't know when the fix is coming, just yet. >2) On system 2, using a Trident 9000 video card, the screen looks fine, but af >ter kernel probes all devices, the screen goes blank, beeps once, the cursor g >oes to the lower left hand corner of the screen, and the system sits idle. Swi >tching to the alternate console, Alt-F2, I see a single line that says "DEBUG: > ioctl(3, TIOCCONS, NULL) = 0 (success)". Key strokes on the first console ar >e ignored. Key strokes on the alternate console are processed, but no shell is > available. As you can switch between the two vtys, keyboard I/O seems OK... What if you specify the flag 0x01 to the npx0 device in the device configuration menu (in CLI mode)? The symptom you described does not quite match the ones which are solved this way, but, it may just work. Kazu >>How-To-Repeat: >Install 2.2.1 with Diamond SpeedStar64 video card. >>Fix: >Use a different video card, install, compile kernel to use PCVT console driver >, replace original video card. This reportedly worked for someone else who use >d a Trident video card, but did not work for me because even with a Trident vi >deo card the installation stopped as reported above.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704210420.VAA14032>