have you tried emergeing* x11-drivers/xf86-input-evdev and x11-drivers/xf86-input-mouse on their own without xorg?

Cheers

Kad

On Mon, May 10, 2010 at 9:59 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:

About a week ago, my Gentoo box was in a bad state where there were some packages that would not install, so I was carefully emerging what I could and filed a bug about one in particular that I could not emerge.


Then I got a new kernel, 2.6.32-gentoo-r7, and I booted from it.* Eeeek. No X11 at all.

The logs informed me about some things to do, and I did them, re-emerging a number of things.* I paid particular attention to emerging anything with x11 or xorg in its name.
Long wait.
I got to a point somewhere in there where X11 started, but would recognize neither keyboard nor mouse.


I kept going.* The keyboard started to work.* I could actually log in, but that's not all that useful without a mouse.
Then I started getting complaints about USE flags needed to make some particular packages support some other packages.* I did those too.

Now I'm at the state where "emerge -aDNvu" denies there's any work to do, and revdep-rebuild reports health.
Still no mouse.
Fortunately, I have a laptop that can ssh into the box and I can work with it, but it's still essentially headless.


Anybody run into this state recently?*
If there's a quick fix, I'd rather not make another bug.
--
Kevin O'Gorman, PhD

On Mon, May 10, 2010 at 10:12 PM, Kaddeh <kaddeh@gmail.com> wrote:

have you tried emergeing* x11-drivers/xf86-input-evdev and x11-drivers/xf86-input-mouse on their own without xorg?

Cheers

Kad
I'm not quite sure what that means. * If you mean emerging them while X is down, I had to do that when X would not come up at all,

but I'll try again.* It will be a while before I have everything backed up the way I want it to be before I try switching to Ubuntu.

If you mean something else, please clue me in.

++ kevin

On Tue, May 11, 2010 at 9:28 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:

On Mon, May 10, 2010 at 10:12 PM, Kaddeh <kaddeh@gmail.com> wrote:


have you tried emergeing* x11-drivers/xf86-input-evdev and x11-drivers/xf86-input-mouse on their own without xorg?

Cheers

Kad
I'm not quite sure what that means. * If you mean emerging them while X is down, I had to do that when X would not come up at all,


but I'll try again.* It will be a while before I have everything backed up the way I want it to be before I try switching to Ubuntu.

If you mean something else, please clue me in.

++ kevin




In any event, no joy.* It's still mouseless.

--
Kevin O'Gorman, PhD

Kevin O'Gorman wrote:
About a week ago, my Gentoo box was in a bad state where there were
some packages that would not install, so I was carefully emerging what
I could and filed a bug about one in particular that I could not emerge.


Then I got a new kernel, 2.6.32-gentoo-r7, and I booted from it.
Eeeek. No X11 at all.
The logs informed me about some things to do, and I did them,
re-emerging a number of things. I paid particular attention to
emerging anything with x11 or xorg in its name.

Long wait.
I got to a point somewhere in there where X11 started, but would
recognize neither keyboard nor mouse.
I kept going. The keyboard started to work. I could actually log in,
but that's not all that useful without a mouse.
Then I started getting complaints about USE flags needed to make some
particular packages support some other packages. I did those too.
Now I'm at the state where "emerge -aDNvu" denies there's any work to
do, and revdep-rebuild reports health.

Still no mouse.
Fortunately, I have a laptop that can ssh into the box and I can work
with it, but it's still essentially headless.

Anybody run into this state recently?
If there's a quick fix, I'd rather not make another bug.
--
Kevin O'Gorman, PhD



Have you tried this:

emerge -1a $(qlist -I -C x11-drivers/)

I have upgraded my kernel before without rebuilding these but they are
small and only take a few minutes. Your mileage may vary.


The mouse drivers should be in that list. If not, then something is
missing in your set up.


Dale

:-) :-)

On Wed, May 12, 2010 at 7:56 AM, Dale <rdalek1967@gmail.com> wrote:

Kevin O'Gorman wrote:


About a week ago, my Gentoo box was in a bad state where there were some packages that would not install, so I was carefully emerging what I could and filed a bug about one in particular that I could not emerge.



Then I got a new kernel, 2.6.32-gentoo-r7, and I booted from it. *Eeeek. No X11 at all.

The logs informed me about some things to do, and I did them, re-emerging a number of things. *I paid particular attention to emerging anything with x11 or xorg in its name.

Long wait.

I got to a point somewhere in there where X11 started, but would recognize neither keyboard nor mouse.

I kept going. *The keyboard started to work. *I could actually log in, but that's not all that useful without a mouse.

Then I started getting complaints about USE flags needed to make some particular packages support some other packages. *I did those too.

Now I'm at the state where "emerge -aDNvu" denies there's any work to do, and revdep-rebuild reports health.

Still no mouse.

Fortunately, I have a laptop that can ssh into the box and I can work with it, but it's still essentially headless.

Anybody run into this state recently?

If there's a quick fix, I'd rather not make another bug.

--

Kevin O'Gorman, PhD






Have you tried this:



emerge -1a $(qlist -I -C x11-drivers/)



I have upgraded my kernel before without rebuilding these but they are small and only take a few minutes. *Your mileage may vary.



The mouse drivers should be in that list. *If not, then something is missing in your set up.



Dale



As I think I explained, I have re-emerged *everything* installed that had "x11" or "xorg" in its name.* And the mouse driver was definitely there.
--

Kevin O'Gorman, PhD

Kevin O'Gorman wrote:
On Wed, May 12, 2010 at 7:56 AM, Dale <rdalek1967@gmail.com
<mailto:rdalek1967@gmail.com>> wrote:


Kevin O'Gorman wrote:

About a week ago, my Gentoo box was in a bad state where there
were some packages that would not install, so I was carefully
emerging what I could and filed a bug about one in particular
that I could not emerge.

Then I got a new kernel, 2.6.32-gentoo-r7, and I booted from
it. Eeeek. No X11 at all.
The logs informed me about some things to do, and I did them,
re-emerging a number of things. I paid particular attention
to emerging anything with x11 or xorg in its name.
Long wait.
I got to a point somewhere in there where X11 started, but
would recognize neither keyboard nor mouse.
I kept going. The keyboard started to work. I could actually
log in, but that's not all that useful without a mouse.
Then I started getting complaints about USE flags needed to
make some particular packages support some other packages. I
did those too.
Now I'm at the state where "emerge -aDNvu" denies there's any
work to do, and revdep-rebuild reports health.
Still no mouse.
Fortunately, I have a laptop that can ssh into the box and I
can work with it, but it's still essentially headless.
Anybody run into this state recently?
If there's a quick fix, I'd rather not make another bug.
--
Kevin O'Gorman, PhD



Have you tried this:

emerge -1a $(qlist -I -C x11-drivers/)

I have upgraded my kernel before without rebuilding these but they
are small and only take a few minutes. Your mileage may vary.

The mouse drivers should be in that list. If not, then something
is missing in your set up.

Dale


As I think I explained, I have re-emerged *everything* installed that
had "x11" or "xorg" in its name. And the mouse driver was definitely
there.

--
Kevin O'Gorman, PhD



That usually works so I'm clueless. I assume the mouse works somewhere
else? I think you mentioned it working somewhere so I'm out of ideas.


Sorry.

Dale

:-) :-)

On Wednesday 12 May 2010 21:21:25 Dale wrote:
> Kevin O'Gorman wrote:
> > On Wed, May 12, 2010 at 7:56 AM, Dale <rdalek1967@gmail.com
> > <mailto:rdalek1967@gmail.com>> wrote:

> >
> > Have you tried this:
> >
> > emerge -1a $(qlist -I -C x11-drivers/)
> >
> > I have upgraded my kernel before without rebuilding these but they
> > are small and only take a few minutes. Your mileage may vary.
> >
> > The mouse drivers should be in that list. If not, then something
> > is missing in your set up.

> > As I think I explained, I have re-emerged *everything* installed that
> > had "x11" or "xorg" in its name. And the mouse driver was definitely
> > there.
>
> That usually works so I'm clueless. I assume the mouse works somewhere
> else? I think you mentioned it working somewhere so I'm out of ideas.


Sorry to persist, but the drivers usually have "xf86-*" in their name not
"x11" or "xorg", e.g. xf86-input-evdev.

(The category of those packages is of course x11-drivers/ ; i.e. x11-
drivers/xf86-input-evdev)

Other than that could it be a udev issue and some permanent rule for a USB
type of mouse, which you should remove and restart udev? Don't know, just an
idea.
--
Regards,
Mick

Mick wrote:

On Wednesday 12 May 2010 21:21:25 Dale wrote:


Kevin O'Gorman wrote:


On Wed, May 12, 2010 at 7:56 AM, Dale<rdalek1967@gmail.com
<mailto:rdalek1967@gmail.com>> wrote:



Have you tried this:

emerge -1a $(qlist -I -C x11-drivers/)

I have upgraded my kernel before without rebuilding these but they
are small and only take a few minutes. Your mileage may vary.

The mouse drivers should be in that list. If not, then something
is missing in your set up.



As I think I explained, I have re-emerged *everything* installed that
had "x11" or "xorg" in its name. And the mouse driver was definitely
there.


That usually works so I'm clueless. I assume the mouse works somewhere
else? I think you mentioned it working somewhere so I'm out of ideas.



Sorry to persist, but the drivers usually have "xf86-*" in their name not
"x11" or "xorg", e.g. xf86-input-evdev.

(The category of those packages is of course x11-drivers/ ; i.e. x11-
drivers/xf86-input-evdev)

Other than that could it be a udev issue and some permanent rule for a USB
type of mouse, which you should remove and restart udev? Don't know, just an
idea.



That's what I was thinking. I get this list using part of the command I
posted earlier:


[IP-] [ ] x11-drivers/nvidia-drivers-173.14.22:0
[IP-] [ ] x11-drivers/xf86-input-evdev-2.3.2:0
[IP-] [ ] x11-drivers/xf86-input-keyboard-1.4.0:0
[IP-] [ ] x11-drivers/xf86-input-mouse-1.5.0:0
[IP-] [ ] x11-drivers/xf86-video-nv-2.1.17:0

Mine has xf86-* drivers as well. OP, do you have your setting in
make.conf correctly? Mine looks like this:


INPUT_DEVICES="keyboard mouse evdev"

I do NOT use hal so your settings may need to be different but you do
need the line tho.


Other than this, back to clueless.

Dale

:-) :-)

On Wednesday 12 May 2010 21:21:25 Dale wrote:

> That usually works so I'm clueless.

No, Dale, you aren't. Really.

:-)

--
Rgds
Peter.

Peter Humphrey wrote:

On Wednesday 12 May 2010 21:21:25 Dale wrote:



That usually works so I'm clueless.


No, Dale, you aren't. Really.

:-)




Sometimes I am. If rebuilding the drivers don't work and the kernel is
set up properly, I don't know what else to try. May think of something
later but right now, no ideas come to mind.


Dale

:-) :-)