headers
Matthias Scheler | 1 Nov 2002 13:12
Picon
Favicon

Re: black on black terminal after quitting X

In article <Pine.NEB.4.44.0210311944540.10212-100000 <at> sdf.lonestar.org>,
	poff <at> SDF.LONESTAR.ORG writes:
> I searched the list, and found a similar problem from someone having a
> black on black terminal...

There are multiple VGA drivers which don't save the state properly.

> Any ideas?

Try to build XFree86 4.2.1 from NetBSD's latest sources. Matthias Drochner
fixed this problem in several drivers.

	Kind regards

--

-- 
Matthias Scheler                                  http://scheler.de/~matthias/
Permalink | Reply | 3 comments |
headers
poff | 1 Nov 2002 14:05
Picon
Favicon

Re: black on black terminal after quitting X

> Try to build XFree86 4.2.1 from NetBSD's latest sources. Matthias
Drochner
> fixed this problem in several drivers.

Ok, I had a quick look and there are ports for FreeBSD and OpenBSD but not
yet NetBSD (binary packages).

There is a patch for the source tree, but I've only ever used binaries and
wouldn't know where to start with the patch.

Maybe I should wait until it appears? There are lots of release notes for
4.2.1 on netbsd, pointing to non-existent directories...

I see you've "imported XFree86 4.2.1 into NetBSD's X11 sources " - I'm
rather a n00b and the only thing I can manage is pkg_add and pkg_delete.
Any tips on how to update my version?

Thanks very much for your help,

poff <at> sixbit.org
SDF Public Access UNIX System - http://sdf.lonestar.org
Permalink | Reply | 2 comments |
headers
Matthias Scheler | 1 Nov 2002 14:15
Picon
Favicon

Re: black on black terminal after quitting X

On Fri, Nov 01, 2002 at 01:05:17PM +0000, poff <at> sdf.lonestar.org wrote:
> Ok, I had a quick look and there are ports for FreeBSD and OpenBSD but not
> yet NetBSD (binary packages).

I can make some if there's a big demand.

> There is a patch for the source tree, ...

You are talking about the XFree86 site? You shouldn't use their source
distribution, NetBSD has its own one.

> I see you've "imported XFree86 4.2.1 into NetBSD's X11 sources " - I'm
> rather a n00b and the only thing I can manage is pkg_add and pkg_delete.
> Any tips on how to update my version?

Download the files "local.tar.gz", "top-level.tar.gz" and "xfree.tar.gz"
from "ftp://ftp.netbsd.org/pub/NetBSD-current/tar_files/xsrc/" and
untar them in a single directory. Afterwards build and install them
with these commands:

cd xsrc
env USE_XF86_4=yes make build

	Kind regards

--

-- 
Matthias Scheler                                  http://scheler.de/~matthias/
Permalink | Reply | 0 comments |
headers
Richard Rauch | 3 Nov 2002 02:08
Favicon

wsmouse/wsmux, trackballs, X11

(My system is an i386 laptop, but there's nothing i386-specific about my
problem, I assume.  So, within the domain of NetBSD, I think that this is
most closely an X11 technical problem.)

The laptop of course has a builtin keyboard and mouse (a touch-pad).  I
don't care for the cramped keyboard and have an external keyboard that I
bought a week or so ago to make life easier.  (I mostly use the computer
in an office, so I can keep the keyboard there and the fact that the
keyboard isn't portable isn't an issue.  (^&)

Tonight, I bought a MicroSoft USB trackball (have I mentioned the irony
that they seem to make decent hardware?).

I've got some minor problems with it, but it's working "well enough" that
I can live with it for now.  Still, I thought that I'd ponder some of
these aloud, and maybe get some feedback on them:

 * For the mouse device, I chose "/dev/wsmouse" after some twiddling.
   This seems to be what I want to use.  But the default XFree86
   configuration was to use wsmouse0 or so, I believe.  (I.e., only
   support the touch-pad or the trackball, but not both.)

   I tried various combinations, including wsmux0, and also using
   wsconsctl/wsmuxctl (cfg? whichever).  I'm pretty sure that in some
   variation, I had my trackball plugged in "early" (during boot?), and
   "wsmouse" wasn't giving both mouse & trackball.

   Some wsconsctl/wsmuxctl (cfg?) commands caused weird things to happen,
   such as causing the xconsole to apparently take over the 0 wsconsole,
   giving a "login" prompt (unfortunately, at the stage where I saw that,
(Continue reading)

Permalink | Reply | 2 comments |
headers
Urban Boquist | 3 Nov 2002 11:06

Re: wsmouse/wsmux, trackballs, X11

Richard> Wheel events, and the outermost 2 buttons generate
Richard> nothing.  Any ideas on how I might get X to use this?

For the wheel you can use something like this:

        Option      "Buttons" "5"
        Option      "ZAxisMapping" "4 5"

which will make it generate button4/5 events. It used to also be the
case that you needed to "teach" all applications what to do for those
events. See example below for xterm. At least this was the case a
couple of years ago when wheel mice started to show up. But maybe the
mapping to button4/5 events have become so "standard" nowadays that
applications do the right thing by themselves, I haven't checked.

Google around a bit and you'll easily find what to do for other
applications if you need it.

Kind regards,

        -- Urban

XTerm*VT100*Translations: #override \n\
        <Btn4Down>,<Btn4Up>:            scroll-back(1,halfpage)\n\
        <Btn5Down>,<Btn5Up>:            scroll-forw(1,halfpage)\n\
Permalink | Reply | 1 comment |
headers
Richard Rauch | 3 Nov 2002 18:25
Favicon

Re: wsmouse/wsmux, trackballs, X11

> Richard> Wheel events, and the outermost 2 buttons generate
> Richard> nothing.  Any ideas on how I might get X to use this?
>
> For the wheel you can use something like this:
>
>         Option      "Buttons" "5"
>         Option      "ZAxisMapping" "4 5"

Thanks.  I set up XFree86 with this about 5 years ago and forgot all about
it since then.  (^&  Would it be an overall win if the XFree86
configuration tools would add in ZAxisMapping options by default?  I don't
know how commonly they are needed, but it would certainly be easier to
find and remove/change a bogus option than to figure out what to add to
get it to work.

An obvious adaptation for the situation I described makes this actually
work:

  Option "Buttons" "7"
  Option "ZAxisMapping" "6 7"

I still wish that I could adjust the sensitivity of the trackball
independantly from the touch-pad built into the laptop.  This is more of a
NetBSD kernel/mouse/mux issue, but still (within NetBSD) seems mostly
x11-related.  (^&

It seems odd that there's no way for XFree86 to understand "this is a
wheel" and to report it as such to applications.  Ah well...

> which will make it generate button4/5 events. It used to also be the
(Continue reading)

Permalink | Reply | 0 comments |
headers
poff | 3 Nov 2002 22:22
Picon
Favicon

Re: black on black terminal after quitting X

> > Try to build XFree86 4.2.1 from NetBSD's latest sources. Matthias
> Drochner
> > fixed this problem in several drivers.

Well I *finally* managed to do this (I didn't realise /usr has all the
space for me!):

XFree86 Version 4.2.1 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 3 September 2002
        If the server is older than 6-12 months, or if your card is
        newer than the above date, look for a newer version before
        reporting problems.  (See http://www.XFree86.Org/)
Build Operating System: NetBSD/i386 1.6 [ELF] The NetBSD Foundation, Inc.
Module Loader present

HOWEVER; this doesn't solve the problem for me :( I still have a black
(dark grey) on black terminal after quitting X.

Any other ideas? It's using a Trident driver.

Thanks for your help,

poff <at> sixbit.org
SDF Public Access UNIX System - http://sdf.lonestar.org
Permalink | Reply | 0 comments |
headers
Brian A. Seklecki | 7 Nov 2002 22:00

Re: black on black terminal after quitting X

On Thu, 31 Oct 2002  <at>  7:49pm (-0000), poff <at> SDF.LONESTAR.ORG wrote:

> Hi,
>
> I searched the list, and found a similar problem from someone having a
> black on black terminal...
>
> XFree86 Version 4.2.0
>
> http://poff.sixbit.org/netbsd has a load of my logs and configurations for
> X...

...this problem is old as sin, and no one seems to be able to fix it, and
none of the wscons fixes ever make it back to the xfree86.org tree; normally
it happens with the 'nv' driver.  Happens to to my geforce all the time.

-lava

>
> I didn't see any solutions to this from the other posts, something about
> changing from 80x50 to 80x25 => how would I do this and would it help?
> (I'm a n00b)
>
> I tryed "reset" and posting a weird string of stuff someone else
> suggested, but to no avail :(
>
> Any ideas? It's the same if I use Ctrl-Alt-F1 or similar during my x
> session.
>
> Thanks,
(Continue reading)

Permalink | Reply | 1 comment |
headers
Al Urbaitis | 7 Nov 2002 22:36

Visual Modes

Hello
Could someone direct me to a discussion
on Visual Modes. I am interested in the
difference between "TrueColor" and "DirectColor".

Al
Permalink | Reply | 2 comments |
headers
Hubert Feyrer | 8 Nov 2002 01:45
Picon

Re: Visual Modes

On 7 Nov 2002, Al Urbaitis wrote:
> Could someone direct me to a discussion
> on Visual Modes. I am interested in the
> difference between "TrueColor" and "DirectColor".

I can only guess that the O'Reilly X books discuss that.

 - Hubert

--

-- 
Want to get a clue on IPv6 but don't know where to start? Try this:
* Basics -> http://www.onlamp.com/pub/a/onlamp/2001/05/24/ipv6_tutorial.html
* Setup  -> http://www.onlamp.com/pub/a/onlamp/2001/06/01/ipv6_tutorial.html
Of course with your #1 IPv6 ready operating system -> http://www.NetBSD.org/
Permalink | Reply | 0 comments |

Gmane