Bug 145920

Summary:	Can not start X in the installation
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Pang Dawei <pangdae>
Component:	Installation	Assignee:	Marcus Schaefer <ms>
Status:	RESOLVED FIXED	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None
Version:	Beta 1
Target Milestone:	---
Hardware:	i686
OS:	SUSE Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	xorg.conf of error installation this file is /proc/bus/usb/devices in the installation

Description Pang Dawei 2006-01-26 17:38:22 UTC

There are two device like mouse in my computer , one is PS/2 mouse and the other is hand writing pad (USB).
When I install SuSE10.1beta1 in my computer , both the two device have been pluged in my computer.The SuSE10.1beta1 installation can not start X, When changed screen using CTRL+ATL+F8, I could see some error information like that:
Parse error on line 57 of section InputDevice in file /etc/X11/xorg.conf "Section " is not a valid keyword in this section. and so on.
I checked the xorg.conf, found the two same line like:
Section "InputDevice"
  Driver "mouse"
  Identifier "Mouse[1]"

When I remove the hand writing pad , the installation will start X normally.

I think that maybe a bug.

Comment 1 Pang Dawei 2006-01-26 17:41:45 UTC

Created attachment 65283 [details]
xorg.conf of error installation

Comment 2 Pang Dawei 2006-01-26 17:44:38 UTC

Created attachment 65286 [details]
this file is /proc/bus/usb/devices in the installation

Comment 3 Marcus Schaefer 2006-01-27 10:25:12 UTC

I tried to reproduce with two mice connected one is a PS/2 the other
a USB mouse both are working and the installation starts (Beta1)
Hmm, could you provide the output of the command

   xmset -c

You can call this if you switch to a text console

   Ctrl-Alt-F2

straight after YaST has been started

Thanks

Comment 4 Pang Dawei 2006-01-27 16:18:09 UTC

I can reproduce that.
I use the "xmset -c" command in the CTRL-ALT-F2 , got the followed information:

Section "InputDevice"
  Driver     "mouse"
  Identifier "Mouse[1]"
Section "InputDevice"
  Driver     "mouse"
  Identifier "Mouse[1]"
  Option     "Protocol" "explorerps/2"
  Option     "Device"   "/dev/input/mice"
EndSection

Comment 5 Marcus Schaefer 2006-01-30 13:52:44 UTC

ok, something is wrong here. Could you send the information
from 


  hwinfo --mouse

as well. Thanks

Comment 6 Pang Dawei 2006-01-30 18:31:45 UTC

I got some messages followed by hwinfo --mouse

15: USB 00.0: 10503 USB Mouse
  [Created at usb.122]
  UDI: /org/freedesktop/Hal/devices/usb_device_b57_8001_noserial_if0_logicaldev_input
  Unique ID: cLrx.jCmtwnc19XF
  Parent ID: k4bc.3PraMNnpCG1
  SysFS ID: /devices/pci0000:00/0000:00:1f.2/usb1/1-2/1-2:1.0
  SysFS BusID: 1-2:1.0
  Hardware Class: mouse
  Model: "Han Wang Technoloy Center JB8 USB Tablet"
  Hotplug: USB
  Vendor: usb 0x0b57 "Han Wang Technoloy Center"
  Device: usb 0x8001 "JB8 USB Tablet"
  Revision: "0.11"
  Compatible to: int 0x0200 0x0001 "Generic USB Mouse"
  Driver: "usbhid"
  Device File: /dev/input/event3
  Device Number: char 13:67
  Speed: 1.5 Mbps
  Module Alias: "usb:v0B57p8001d0011dc00dsc00dp00ic03isc01ip02"
  Driver Info #0:
    XFree86 Protocol: explorerps/2
    GPM Protocol: exps2
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #14 (Hub)

18: PS/2 00.0: 10500 PS/2 Mouse
  [Created at input.157]
  UDI: /org/freedesktop/Hal/devices/platform_i8042_i8042_Aux_Port_logicaldev_input
  Unique ID: AH6Q.hI1e_vHaTSC
  Hardware Class: mouse
  Model: "ImPS/2 Generic Wheel Mouse"
  Vendor: int 0x0210 
  Device: int 0x0013 "ImPS/2 Generic Wheel Mouse"
  Device File: /dev/input/mice (/dev/input/mouse0)
  Device Files: /dev/input/mice, /dev/input/mouse0, /dev/input/event1
  Device Number: char 13:63 (char 13:32)
  Driver Info #0:
    Buttons: 3
    Wheels: 1
    XFree86 Protocol: explorerps/2
    GPM Protocol: exps2
  Config Status: cfg=new, avail=yes, need=no, active=unknown

Comment 7 Marcus Schaefer 2006-01-31 08:38:19 UTC

Thanks now I know what is going wrong. for Tablet devices there is
code to skip the device from being enabled while installing. Within
that code there was a bug creating an incomplete InputDevice section
I fixed that.