Linux Newbie help
 help / color / mirror / Atom feed
From: Bryan Whitehead <driver@jpl.nasa.gov>
To: James Miller <jamtat@mailsnare.net>
Cc: linux-newbie@vger.kernel.org
Subject: Re: longstanding Linux irritants: suggested solutions?
Date: Mon, 12 Apr 2004 16:08:08 -0700	[thread overview]
Message-ID: <407B2158.6070702@jpl.nasa.gov> (raw)
In-Reply-To: <Pine.LNX.4.58.0404121355350.673@debian-emach>


> I've generated a working XF86Config-4 file and the display quality is to
> my liking.  The problem is that it is shifted slightly too far right on
> the monitor (LCD flat screen 17").  I can, of course shift the image
> manually with control buttons on the monitor itself.  But when I do this,
> running text that gives boot messages on startup gets cut off a bit on the
> opposite side.  What I've done to deal with it thus far is to run Xvidtune
> and reposition the display that way - which does work.  Problem is, it
> doesn't hold between reboots: I have to rerun Xvidtune every time I reboot
> to properly center the display.  I kind of expect Xvidtune to write the
> values I tune the display to to XF86Config-4, but it doesn't do that.
> I've tried it both as user and as root.  Judging from the man page for
> Xvidtune, which says:
> 
> Show      Print the currently selected settings to stdout in XF86Config
>           "Modeline" format.  The primary selection is similarly set.
> 

First, run xvidtune from a terminal and DO NOT close the terminal.

After you get xvidtune to the exact psoition you want press the "show" 
button.

In the terminal a "Modeline" will be printed. On mine I get this:
"1600x1200"   229.50   1600 1664 1856 2160   1200 1201 1204 1250 +hsync 
+vsync

In your XF86Config-4 file goto your Monitor section and add
ModeLine <the crap xvidtune spit out>

So for me I'd add this to Section "Monitor":
ModeLine "1600x1200"   229.50   1600 1664 1856 2160   1200 1201 1204 
1250 +hsync +vsync

Now restart X... Simple eh?

> The next irritant I've encountered has to do with mice and the 2.6.4
> kernel.  I have a pretty much standard ps2 mouse (a trackballish type
> thing but definitely with a ps2 plug).  This mouse works fine with the 2.4
> kernels I've tried it with thus far: I've loaded 3 or 4 different 2.4.x
> kernels over the last few months and never had any problems.  However,
> when I tried to use a 2.6.x kernel - up to and including the latest 2.6.4
> kernel - the mouse does not work.  In other words, I try to move the
> cursor and it won't move: it simply stays stuck in the middle of the
> screen regardless of what I move on the physical mouse.  These kernels are
> the stock Debian Sid ones, btw - I did *not* compile them myself (ok, go
> ahead and subtract geek points . . . see if I care).  In other words, when
> I want to try a new kernel I do apt-get install
> kernel-image-whatever.ver-686.  Then I do the necessary tweaking of lilo
> and symlinks in /boot and so forth.  The machine boots fine by this means,
> btw.  I just can't use the mouse with the 2.6.x kernels when it gets to
> the gui stage, for some strange reason.  I looked over
> /var/log/XFree86.0.log and, to my untrained eye, the following message
> toward the end of that file seems like it could apply:
> 
> (**) Option "Protocol" "PS/2"
> (**) Configured Mouse: Protocol: "PS/2"
> (**) Configured Mouse: Core Pointer
> (**) Option "Device" "/dev/gpmdata"
> (==) Configured Mouse: Buttons: 3
> (**) Option "Protocol" "PS/2"
> (**) Generic Mouse: Protocol: "PS/2"
> (**) Generic Mouse: always reports core events
> (**) Option "Device" "/dev/input/mice"
> (EE) xf86OpenSerial: Cannot open device /dev/input/mice
>         No such device.
> (EE) Generic Mouse: cannot open input device
> (EE) PreInit failed for input device "Generic Mouse"
> (II) UnloadModule: "mouse"
> (II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE)
> 
> Could anyone offer suggestions for how to resolve this mouse problem so I
> can finally begin using the 2.6.4 kernel?  Thanks for input on this.

You are not loading in the USB input modules. Read the kernel docs on 
what ones you need. I don't use debian so I can't help anymore...

-- 
Bryan Whitehead
SysAdmin - JPL - Interferometry and Large Optical Systems
Phone: 818 354 2903
driver@jpl.nasa.gov

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2004-04-12 23:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-12 19:39 longstanding Linux irritants: suggested solutions? James Miller
2004-04-12 23:08 ` Bryan Whitehead [this message]
2004-04-13  3:28   ` James Miller
2004-04-13  4:14     ` Ray Olszewski
2004-04-13  5:47     ` Beolach
2004-04-13 15:03       ` James Miller
2004-04-13 17:42         ` James Miller
2004-04-13 21:42           ` caszonyi
2004-04-13 23:51           ` kernel 2.6.4 report, further assistance requests James Miller
2004-04-14  2:39             ` joy
2004-04-14  2:57               ` James Miller
2004-04-14 14:26                 ` James Miller
2004-04-12 23:23 ` longstanding Linux irritants: suggested solutions? Ray Olszewski
2004-04-12 23:28 ` caszonyi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=407B2158.6070702@jpl.nasa.gov \
    --to=driver@jpl.nasa.gov \
    --cc=jamtat@mailsnare.net \
    --cc=linux-newbie@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox