1 |
Kevin O'Gorman wrote: |
2 |
> On Wed, May 12, 2010 at 2:26 PM, Mick <michaelkintzios@×××××.com |
3 |
> <mailto:michaelkintzios@×××××.com>> wrote: |
4 |
> |
5 |
> On Wednesday 12 May 2010 21:21:25 Dale wrote: |
6 |
> > Kevin O'Gorman wrote: |
7 |
> > > On Wed, May 12, 2010 at 7:56 AM, Dale <rdalek1967@×××××.com |
8 |
> <mailto:rdalek1967@×××××.com> |
9 |
> > > <mailto:rdalek1967@×××××.com <mailto:rdalek1967@×××××.com>>> |
10 |
> wrote: |
11 |
> |
12 |
> > > |
13 |
> > > Have you tried this: |
14 |
> > > |
15 |
> > > emerge -1a $(qlist -I -C x11-drivers/) |
16 |
> > > |
17 |
> > > I have upgraded my kernel before without rebuilding these |
18 |
> but they |
19 |
> > > are small and only take a few minutes. Your mileage may vary. |
20 |
> > > |
21 |
> > > The mouse drivers should be in that list. If not, then |
22 |
> something |
23 |
> > > is missing in your set up. |
24 |
> |
25 |
> > > As I think I explained, I have re-emerged *everything* |
26 |
> installed that |
27 |
> > > had "x11" or "xorg" in its name. And the mouse driver was |
28 |
> definitely |
29 |
> > > there. |
30 |
> > |
31 |
> > That usually works so I'm clueless. I assume the mouse works |
32 |
> somewhere |
33 |
> > else? I think you mentioned it working somewhere so I'm out of |
34 |
> ideas. |
35 |
> |
36 |
> |
37 |
> Sorry to persist, but the drivers usually have "xf86-*" in their |
38 |
> name not |
39 |
> "x11" or "xorg", e.g. xf86-input-evdev. |
40 |
> |
41 |
> (The category of those packages is of course x11-drivers/ ; i.e. x11- |
42 |
> drivers/xf86-input-evdev) |
43 |
> |
44 |
> Other than that could it be a udev issue and some permanent rule |
45 |
> for a USB |
46 |
> type of mouse, which you should remove and restart udev? Don't |
47 |
> know, just an |
48 |
> idea. |
49 |
> |
50 |
> I'll try any idea. Where would such a permanent rule reside? |
51 |
> |
52 |
> |
53 |
> -- |
54 |
> Kevin O'Gorman, PhD |
55 |
> |
56 |
|
57 |
They should be in: |
58 |
|
59 |
/etc/udev/rules.d |
60 |
|
61 |
I have been known to back that directory up, delete all the rules and |
62 |
then re-emerge udev. Sometimes that works, sometimes it doesn't. If |
63 |
you have rules you made yourself, do back them up first. |
64 |
|
65 |
Of course you may be able to check in the rule files and see if there is |
66 |
something obviously wrong too. |
67 |
|
68 |
Dale |
69 |
|
70 |
:-) :-) |