Re: [WBEL-users] Adding Gui on command-line install

At 08:11 PM 10/26/2006, Robert Heller wrote:
>At Thu, 26 Oct 2006 16:28:37 -0700 david <[email protected]> wrote:
>
> > > > When I ran the Xorg -configure, it claimed it could not detect the
> > > > mouse, and suggested that I edit
> > > >    /root/xorg.conf.new
> > > > I saw that the device pointer therein was
> > > >    /dev/mouse
> > > > but my dev listing shows
> > > >   /dev/mouse0
> > > >
> > > > So, I did the edit, saved it, reran the configure, and it complained
> > > > again.  When I reexamined the edited file, my changes were erased !!
> > > >
> > >
> > >Is it a serial, PS/2, or USB mouse?
> > >
> > >You might have to fuss with udev to get the /dev/mouse symlink to stay
> > >around.
> > >
> > >I have a serial mouse on COM2, so I have this line in
> > >/etc/udev/rules.d/10-local.rules:
> > >
> > >KERNEL="ttyS1", SYMLINK="modem"
> > >
> > >You might need to add something else for your mouse.
> > >
> > >Also:  *Always* Cc to the list! -- select 'Reply To All' when you reply.
> > >I'm not the only one with answers -- there are others who might have
> > >answers too.
> >
> >
> > It is a PS2 mouse that was not visible during original WBEL
> > install.  I can only find the file /etc/udev/rulses.d/50-udev.rules,
> > but have no idea what to do with it.  The only line that has MOU 
> on it says:
> >
> > KERNEL="mouse*", NAME="input/%k"
> >
> > Is a reinstall of WBEL4 the cleanest "no brainer" way to do this?
>
>No.  The "reinstall when in doubt" is a *windows* thing.  Also, you
>don't touch /etc/udev/rulses.d/50-udev.rules, but you might need to
>create/add a line to /etc/udev/rulses.d/10-local.rules.  You probably
>don't need to though, since I think a PS/2 should be handled properly.


OK..... I did system-config-mouse, which put me into text mode.
I chose a two-button PS/2 mouse (which is where I plugged it in)
Xorg -configure still didn't work. -- said it could not detect the 
mouse, although the mouse does move the square cursor in command mode.




>You might try setting up the console mouse services.  Strange as that
>sounds, it is what has worked for me.
>
>Run '/usr/bin/system-config-mouse' and follow the steps.
>
> >
> > David
> >
> > 
>
>
>--
>Robert Heller             -- 978-544-6933
>Deepwoods Software        -- Linux Installation and Administration
>http://www.deepsoft.com/  -- Web Hosting, with CGI and Database
>[email protected]       -- Contract Programming: C/C++, Tcl/Tk
> 
>