Ok. I'm boned. (xdm autostarting and X issue)

liquigel · 02-18-2004, 12:14 AM

I just installed debian Woody from some slightly older 3.0 CD's. (During the
install, there was a dpkg problem with the gv package, but I don't think that is
an issue here.)

I was booting into the console just fine for a couple times there, but then xdm
started trying to start after I booted up (how can I stop this? I'd like to type startx
if I want to run X, rather than it starting up on its own).

I'm not sure what I might've done to make xdm start coming up. It could've been
a 'dpkg-reconfigure { xfree86-common | xserver-xfree86 | xserver-common }'
but I don't know... (?) Maybe because I did 'apt-get install icewm' ?

Anyhow, the xdm X display comes up, and the usb mouse doesn't respond.
The (ps/2) keyboard won't respond either. It makes some of its clicky noises the first
few times I hit some keys (it's one of those sweet programmable jobbies), but
then after hitting 5 or 6 keys it seems to just go dead.

The only way out at this point is to hit the hard reset button on my x86 case
and reboot the machine -- but little good it does, because I just get xdm starting
up automatically again and everything locking up again. To be clear: I can't
even get to a console now.

Some help would really hit the spot. :)

liquigel · 02-18-2004, 01:20 AM

Well, I was able to boot up with install CD #1, asked for the bf24 kernel (just like the
one I installed originally on the system), hit alt-ctrl-F2 to get a root ash prompt, mounted
my hd's root partition

Code:

 mount -t reiserfs /dev/hda1 /mnt

and modified /etc/inittab to read

Code:

 id:1:initdefault

instead of

Code:

 id:2:initdefault

Rebooted, and now I've got my root prompt in single-user mode.

{EDIT} Used modconf to add usbmouse, but that didn't seem to help (though it was probably
necessary anyway).

{EDIT} I read this thread:
http://www.linuxquestions.org/questi...hreadid=129513
then this one:
http://www.linuxquestions.org/questi...hreadid=118534
but still no luck. Tried adding "hid" with modconf. Tried 'cat /dev/input/mice' but cat just keeps
telling me that there's no such device (even though ls -l shows it as being there).

One thing that looks strange, is that my /etc/X11/XF86Config-4 has *two* "InputDevice"
sections in it -- one with identifier "Configured Mouse", and the other with "Generic Mouse":

Code:

Section  "InputDevice"
  Identifier  "Configured Mouse"
  Driver  "mouse"
  Option  "CorePointer"
  Option  "Device"  "/dev/psaux"
  Option  "Protocol"  "ImPS/2"
  Option  "ZAxisMapping"  "4 5"
EndSection

Section  "InputDevice"
  Identifier  "Generic Mouse"
  Driver  "mouse"
  Option  "SendCoreEvents"  "true"
  Option  "Device"  "/dev/input/mice"
  Option  "Protocol"  "ImPS/2"
  Option  "ZAxisMapping"  "4 5"
EndSection

snacky · 02-18-2004, 04:05 AM

I think you want your default runlevel to be 4.

codeape · 02-18-2004, 04:12 AM

Quote:

Originally posted by liquigel

I was booting into the console just fine for a couple times there, but then xdm
started trying to start after I booted up (how can I stop this? I'd like to type startx
if I want to run X, rather than it starting up on its own).

You should be able to achieve this by using 'rcconf' (available through dselect).
Unchecking your display manager should stop it from loading automatically.

liquigel · 02-18-2004, 10:42 AM

Thanks for the replies.

Snack, do runlevels 2 through 5 have any practical differences from eachother?
http://www.debian.org/doc/manuals/re...ml#s-runlevels

Codeape -- Ahhhh yes. :) My good friend rcconf, how did I ever forget about you?
Thanks. I shut off xdm, set my inittab back to it's default, and now I'm no longer
boned as my original message subject indicated.

Now I just need to figure out why I can't get my usb mouse recognized. It worked
for me with Slackware. What was interesting about that was when I ran startx,
after the WM came up, it would take a few seconds of me moving the mouse
around before the cursor started moving. I suppose that some subsystem was
recognizing that a usb mouse needed to be loaded, and that process took a couple
of seconds. I think that may have had something to do with this "hotplug" package
I've seen mentioned.

I installed gpm to help me diagnose the mouse problem, and am reading the docs
on gpm, devfs, mousedev, hotplug, and anything else I can find on usb support in
debian. Any other tips would be welcomed.

{EDIT}
Ok, when I unplug the mouse, I get:

usb.c: USB disconnect on device 2

And when I reconnect the mouse, I get:

hub.c: USB new device connect on bus1/1, assigned device number 3
input0: Logitech USB Mouse on usb1:3.0

'cat /dev/input/mice' still yields "No such device".

lsmod tells me (non-usb material snipped):

hid 0 (unused)
usbmouse 0 (unused)
input 0 [hid usbmouse keybdev usbkbd]
usb-uhci 0 (unused)
usbcore 0 [hid usbmouse usb-storage usbkbd usb-uhci]

dmesg tells me the following about usb:

Code:

usb.c: registering new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 10:29:43 Apr 14 2002
usb-uhci.c: High bandwidth mode enabled
PCI: Found IRQ 12 for device 00:07.2
PCI: Sharing IRQ 12 with 00:07.3
usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 12
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Found IRQ 12 for device 00:07.3
PCI: Sharing IRQ 12 with 00:07.2
usb-uhci.c: USB UHCI at I/O 0xd800, IRQ 12
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
usb.c: registered new driver keyboard
usbkbd.c: :USB HID Boot Protocol keyboard driver
spurious 8259A interrupt: IRQ7
hub.c: USB new device connect on bus1/1, assigned device number 2
usb.c: USB device 2 (vend/prod 0x46d/0xc001) is not claimed by any active driver.

...

usb.c: registered new driver usb_mouse
input0: Logitech USB Mouse on usb1:2.0
usbmouse.c: v1.6:USB HID Boot Protocol mouse driver

...

usb.c: registered new driver hiddev
usb.c: registered new driver hid
hid-core.c: v1.8 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
hid-core.c: USB HID support drivers

...

usb.c: USB disconnect on device 2
hub.c: USB nev device connect on bus1/1, assigned device number 3
input0: Logitech USB Mouse on usb1:3.0

startx brings up icewm for me, but I still get that "frozen mouse and keyboard" effect.

liquigel · 02-18-2004, 12:07 PM

Installed usbutils, but it's lsusb gives me no output -- even as "lsusb -vv"

Also, lspci yields:

00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16)
00:07.3 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16)

Tried removing the usbkbd module with modconf, but that didn't help so I'm putting
it back in.

This is weird,... why would bf24 have such a problem with a standard setup like a usb
mouse and a ps/2 keyboard? I still haven't built my own kernel yet, because things look
like they should work with this one.

Any tips anybody?

codeape · 02-18-2004, 12:27 PM

It seems to me like it's assigning IRQ's twice, which it probably shouldn't be doing. Did you modconf a driver or was it installed in the kernel at installation?

liquigel · 02-18-2004, 12:41 PM

Thanks for the reply codeape.

Well, there's 2 usb ports on the back of this x86 box (as usual), so maybe that's why
lspci lists two devices, and why they end up sharing an IRQ.

During installation, modconf gets run for me, and IIRC, I chose a couple of usb items
at the time, then later added in others, like usbmouse and hid.

I think I may have brought this thread off-topic. My original problem of just getting my
prompt back is solved, so I'm going to start a new, more relevant "usb mouse" thread
and just provide a link to this one.
(see http://www.linuxquestions.org/questi...hreadid=147651 )