Bug 137691

Please attach the output of:

cat /proc/bus/input/devices

and attach uncompressed xorg.conf and Xorg log file from /var/log/

Created attachment 105995 [details]
/proc/bus/input/devices

Created attachment 105998 [details]
xorg.conf

Note: the following parts were added by myself and should not interfere with
this bug:

1. Prevent Ctrl+Alt+Backspace from bombing out of X (this should be default
IMHO, but it is another problem)

Section "ServerFlags"
	Option "DontZap" "On"
	Option "DontZoom" "On"
EndSection

2. Set display size (in Monitor section)
	Displaysize  304 228

Created attachment 105999 [details]
Xorg.0.log

Replicated here.

Can you try system-config-display --reconfig with the PS/2 mouse
plugged in attach the conf and test (feel free to add your options
back to the generated conf).

`system-config-display --reconfig` ends up with the same exact 
xorg.conf (minus my modifications of course). 
As a result, next restart also fails to use the mouse. 
 
Side note: as usual, Fedora fails to detect any Dell Laptop display 
panel, in this case a 'Dell 1024x768 Laptop Display panel' that I 
have to select manually. 

OK, that means we may not detect the PS/2 mouse.  I tested here with a synaptics
config only, then reconfigured with an external mouse.

The panel is probably not probable with DDC so there isn't much we can do in
that case.

Can you run as root with the PS/2 mouse attached:

kudzu -p -b psaux 

 > OK, that means we may not detect the PS/2 mouse.  I tested here 
with a synaptics config only, then reconfigured with an external 
mouse. 
 
Did you manage to get the mouse working ? 
 
> The panel is probably not probable with DDC 
 
What is DDC ? 
 
> Can you run as root with the PS/2 mouse attached: 
 
# kudzu -p -b psaux  
- 
class: MOUSE 
bus: PSAUX 
detached: 0 
device: input/mice 
driver: synaptics 
desc: "SynPS/2 Synaptics TouchPad" 
- 
class: KEYBOARD 
bus: PSAUX 
detached: 0 
driver: ignore 
desc: "AT Translated Set 2 keyboard" 
 

Yes I got an external PS/2 working here after reconfiguring.

DDC is Display Data Channel, a standard by VESA
http://www.vesa.org/standards_summaries.html which can be used to
probe video cards and monitors.  This is what is used to detect your
monitor, if a monitor or panel doesn't support DDC probing then we
can't auto detect.

You should have another psaux mouse device listed with PS/2 external
connected - as it's not there seems to be something wrong.  

Are there any BIOS options related to the external PS/2 port and
Legacy USB support that you can adjust and see if that makes a difference?

Bug confirmed on FC3 final. 
It is indeed a regression from FC1 (can confirm behaviour of FC2 
later if needed).  
 
Thanks for the info about DDC. 
 
> You should have another psaux mouse device listed with PS/2 
external 
> connected - as it's not there seems to be something wrong. 
 
Well, it is not the hardware. I checked one more time with FC1 
install disk -> graphic install autodetects mouse, which works 
perfectly aside the synaptics touchpad. 
 
> Are there any BIOS options related to the external PS/2 port and 
> Legacy USB support that you can adjust and see if that makes a 
difference? 
 
Bingo! 
 
The option is: 
 Touchpad [Enabled / Auto Disabled] 
 
FWIW: 
 - BIOS rev is A15 for Dell Inspiron 7000 
 - mouse is PS/2 wheel mouse (IntelliMouse). 
 
1.  'Enabled' 
  - FC1: mouse + touchpad work together. 
  - FC3: no mouse, touchpad OK. 
 
2. 'Auto Disabled': 
  - FC1: detects 'Generic - Wheel Mouse (PS/2)' (correct), disables 
touchpad. Wheel mouse works OK. 
  - FC3: detects 'Generic - 3 Button Mouse (PS/2)' (*incorrect*), 
disables touchpad. Wheel mouse works (as 3-button mouse). 
 
Enabled is the preferred option of course. 
So FC1 worked perfectly in all respects, and FC3 does not work 
correctly for any option (regression). 
 
I now remember struggling with this option a long time ago --RH6--, 
and was probably very happy to erase the bad memories from my brain's 
filesystem (trying to explain the "why didn't I think of this 
earlier?" factor). 
 
 

Adjusted product version to FC3, so that it does not get lost. 
Let me know if adjusting version like this is the thing to do. 

Hi,

I had a similar problem with an Amilo A 7600 laptop  i.e. no touchpad
detected during install and duringing post install on FC2 and FC3 -
after hunting around passing the kernel parameter i8042.nomux seemed
to fix it - I read that on the unofficial fedora faq - they said it
helped with keyboard, mouse issues - not sure what it does or why it
works but it did for me.

Best Regards

Comment #10 - 2.6 uses a completely different input layer to 2.4 which
is what FC1 uses.

Comment #12 - Phillipe does passing the i8042.nomux make any
difference to your experience?

> Phillipe does passing the i8042.nomux make any 
> difference to your experience? 
 
No difference in any of the four combinations (install CD/regular 
boot, Enabled / Auto Disabled). 
 

Looks like an issue in the input layer and your laptop with the
external ps/2 connected as I've been able to get things working with
external PS/2 and synaptics on a system here.

Replicated here with a Compaq Armada 110.
Solved with: psmouse.proto=imps as boot parameter to the kernel.

References:
https://www.redhat.com/archives/fedora-list/2004-December/msg05787.html

Also replicated with kernel 2.6.10-1.770_FC3 on a Dell Inspiron 7500.

Problem resolvable with psmouse.proto=imps boot param.

An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem.   Please update to this new kernel, and
report whether or not it fixes your problem.

If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.

Thank you.

> Problem resolvable with psmouse.proto=imps boot param.     
     
I confirm that booting with 'psmouse.proto=imps' boot param does work around  
the problem:  
 - during install of FC3 (type 'linux psmouse.proto=imps' at prompt)  
 - at start of the system (option added to grub.conf)  
  
The update does not fix it, this option is still necessary with 
kernel-2.6.12-1.1372_FC3. 
  
    
    
    

This is a mass-update to all currently open Fedora Core 3 kernel bugs.

Fedora Core 3 support has transitioned to the Fedora Legacy project.
Due to the limited resources of this project, typically only
updates for new security issues are released.

As this bug isn't security related, it has been migrated to a
Fedora Core 4 bug.  Please upgrade to this newer release, and
test if this bug is still present there.

This bug has been placed in NEEDINFO_REPORTER state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

Thank you.

I will wait for FC5 and test again then. 
 
Cheers. 

Does this occur in FC5?

A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed.  See bug 207474 for further details.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.

Thank you.

(this is a mass-close to kernel bugs in NEEDINFO state)

As indicated previously there has been no update on the progress of this bug
therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue
still occurs for you and I will try to assist in its resolution. Thank you for
taking the time to report the initial bug.

If you believe that this bug was closed in error, please feel free to reopen
this bug.