A couple of issues.

Unr3a164 · 10-17-2007, 01:12 PM

I am running Slackware 12 on a Gateway Notebook AMD64. The first issue I have is with my USB drive. When I plug it in, Slackware 12 recognizes it and pops up asking me if I want to open it to view the files, but when I do that, I get an error about not being able to mount the device. I have to mount it manually every time I plug it in.

The second issue I have is with my mouse. The scroll wheel does not work on it. It is a Microsoft Wireless Notebook mouse.

Any ideas? Thanks.

rworkman · 10-17-2007, 01:22 PM

See the sticky thread titled "12.0 and HAL" for the first problem.
For the second problem, generate a new xorg.conf with "X -configure" and copy it to /etc/X11/xorg.conf - if that doesn't make the scroll wheel work, we'll go from there.

Alien Bob · 10-17-2007, 01:26 PM

Quote:

Originally Posted by Unr3a164

The second issue I have is with my mouse. The scroll wheel does not work on it. It is a Microsoft Wireless Notebook mouse.

As an alternative to Robby's suggestion, you could try and change the parameter to the psmouse module probe in /etc/rc.d/rc.modules - I have a ThinkPad where the mouse in X does not work if I do not change the line

Code:

/sbin/modprobe psmouse proto=imps

to

Code:

/sbin/modprobe psmouse proto=any

Eric

onebuck · 10-17-2007, 01:29 PM

Quote:

Originally Posted by Unr3a164

I am running Slackware 12 on a Gateway Notebook AMD64. The first issue I have is with my USB drive. When I plug it in, Slackware 12 recognizes it and pops up asking me if I want to open it to view the files, but when I do that, I get an error about not being able to mount the device. I have to mount it manually every time I plug it in.

The second issue I have is with my mouse. The scroll wheel does not work on it. It is a Microsoft Wireless Notebook mouse.

Any ideas? Thanks.

Hi,

You should use a better description for the subject line. Plus post any error messages related to the problem.

As a user, does the user belong to the proper groups? If you are in kde and using kdm then the user must be added to the proper group in the '/etc/group' file. You should add the groups when you create the user for the system. The login.defs are just default.

Code:

 excerpt from /etc/login.defs;

 cat /etc/login.defs |less
# Use with caution - it is possible for users to gain permanent
# access to these groups, even when not logged in on the console.
# How to do it is left as an exercise for the reader...
#
# Most of these groups are self-explanatory, with the possible
# exception of "plugdev", which allows the use of plugable devices
# such as USB storage (flash memory sticks, most digital cameras,
# some media players, and other devices), many IEEE1394 (sometimes
# called "FireWire") devices, and more.  For plugdev devices, the
# use of HAL is required.  HAL also helps users interact with
# hardware in the other groups below (and other hardware) more
# easily as well, so it's a good idea to turn HAL on for any
# machine that will be used from the console.
#
# Note that users are added to these default groups only when
# logging into a shell with /bin/login, not when using a login
# manager such as kdm.  In that case, users who should have
# hardware access must be added to the appropriate groups
# when the user is added with adduser or useradd, or by editing
# /etc/group directly.
#
CONSOLE_GROUPS          floppy:audio:cdrom:video:plugdev

As for the mouse 'issue' could have done a search on LQ Slackware forum as this has been covered a lot.

Code:

 excerpt from 

~# cat /etc/X11/xorg.conf |less

# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

    Identifier  "Mouse1"
    Driver      "mouse"
    Option "Protocol"    "IMPS/2"
    Option "Device"      "/dev/mouse"
#
#01-24-06 17:00 gws
#
    Option "Buttons"       "7"
    Option "ZAxisMapping"  "4 5"
#end 01-24-06 gws

Google & LQ searches are good places to search for answers to problems of this type. The problems are answered all the time!

edit: change the Option "Protocol" to your mouse protocol for the Microsoft mouse. If it is the intelli then the one shown will work.

rworkman · 10-17-2007, 01:31 PM

Quote:

Originally Posted by Alien Bob

As an alternative to Robby's suggestion, you could try and change the parameter to the psmouse module probe in /etc/rc.d/rc.modules - I have a ThinkPad where the mouse in X does not work if I do not change the line

Code:

/sbin/modprobe psmouse proto=imps

to

Code:

/sbin/modprobe psmouse proto=any

Interestingly enough, the one on my ThinkPad (T41) won't work with any of the protocols except "imps" (unless I'm using the synaptics driver, in which case, I use the kernel default - which is "any," I think).

Unr3a164 · 10-17-2007, 03:42 PM

Quote:

Originally Posted by onebuck

You should use a better description for the subject line. Plus post any error messages related to the problem.

I do apologize. I am at work, and do not have access to the error code right now. I will post it when I get it.

I appreciate all the help. I will try some things tonight and see how I fare. Thanks.

DF