Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!news.moneng.mei.com!uwm.edu!caen!usenet.coe.montana.edu!bsd.coe.montana.edu!nate From: nate@bsd.coe.montana.edu (Nate Williams) Newsgroups: comp.os.386bsd.questions Subject: Re: cursor?? Date: 7 Jan 1994 19:39:11 GMT Organization: Montana State University - Bozeman MT Lines: 48 Message-ID: <2gkdov$kfu@pdq.coe.montana.edu> References: <gate.ee9qFc1w165w@subway.hacktic.nl> <1994Jan7.061120.3230@news.csuohio.edu> NNTP-Posting-Host: bsd.coe.montana.edu In article <1994Jan7.061120.3230@news.csuohio.edu>, Steve Ratliff <stever@csuohio.edu> wrote: >Koen Martens (gmc@subway.hacktic.nl) wrote: >: Where is my cursor??? >: I lost it somewhere in the FreeBSD boot process.. After the first couple >: of lines when booting, the cursor dissapears and only pops up on the first >: display line.. >: >: Anybody knows where it might have gone?? >:[sig delted] > This sounds like a known bug with trident 8900 chipsets. Ahh, thanks for jogging my memory Steve. >This was discussed several months ago in c.o.386.bugs (I think). >Unfortunately I do not remember the exact solution to the problem. The solution has been applied to the newest versions of the FreeBSD console drivers. I believe we had to move a couple lines out of a conditional define in order to get it to work correctly, but my memory is pretty fuzzy. > I foggily remember something about the chipset not liking the >cursor to be initialized on line zero or something. The brute force >solution is to exchange your vga card for a better one (different >chipset). Another possible solution (????) is to modify the console >driver, (either syscons.c or pccons.c ) that you are using and either >undef FAT_CURSOR or #define it. I.E. change it opposite to what it is >in your existing kernel. Exactly. > The third and probably best choice is to logon to minnie and >grep through the old news articles and find the correct solution posted >some time ago. If you have kernel sources, I'm sure someone could get you a console driver that would work correctly if you sent email with all the pertinent (sp?) information to freebsd-questions@freefall.cdrom.com. Nate -- nate@bsd.coe.montana.edu | Freely available *nix clones benefit everyone, nate@cs.montana.edu | so let's not compete with each other, let's work #: (406) 994-4836 | compete with folks who try to tie us down to home #: (406) 586-0579 | proprietary O.S.'s (Microsloth) - Me