Fedora core, 2.6.0, psmouse lockup

I installed the 2. 6. 0 kernel in a new Fedora core installation. Everything works but when I load the mouse driver (psmouse), and then move the mouse just a few times, the whole machine locks up. I've tried disabling acpi (both in the kernel configuration and on the boot command line) and building a non-preemptibl ...

Linux Hardware 765 This topic was started by ,


data/avatar/default/avatar12.webp

30 Posts
Location -
Joined 2003-12-30
I installed the 2.6.0 kernel in a new Fedora core installation. Everything works but when I load the mouse driver (psmouse), and then move the mouse just a few times, the whole machine locks up.
 
I've tried disabling acpi (both in the kernel configuration and on the boot command line) and building a non-preemptible configuration.
 
The m/b is a Gigabyte GA-7N400 (Nvidia chipset), and I suspect that has something to do with it, because I have the software on another machine that has a Via chipset, and I have no problems whatsoever.
 
A usb mouse works ok, but I can't use it on this machine because I need to use a KVM switch (which doesn't support a usb mouse.).
Back to top

Participate on our website and join the conversation

You have already an account on our website? Use the link below to login.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This topic is archived. New comments cannot be posted and votes cannot be cast.

Responses to this topic


data/avatar/default/avatar32.webp

2 Posts
Location -
Joined 2004-01-15
hello,
 
i also have the ga-7n400 pro 2 and am seeing hard locks. i have had it lock with mandrake 9.0, 9.2, win2k and during the gentoo 1.0 install. i am suspecting the gigabit on-board lan because it seems to happen when transferring lots of data from another computer and talking to that computer via ssh, etc. i hung gentoo right at the start with their script "net-setup eth0" => dead. i installed a PCI 10/100 network card and disabled the on-board lan, but the OSes still appear to be talking to the on-board lan or something to see what it is.
 
i'm interested to hear what you found. i'm going to try the <CTRL>-F1 trick to get into the "secret" BIOS settings and see what i find.
 
thanks,
-sean

data/avatar/default/avatar32.webp

2 Posts
Location -
Joined 2004-01-15
it appears to have been the network card after all (for me). booted into linux with m/b network card enabled and 10/100 plugged into pci, and told mdk not to activate the m/b card at boot and removed the driver from /etc/modules.conf. then rebooted and set BIOS to disable the card m/b network card. i think that was all i did, there were several reboots in there... but no more locks with heavy network traffic!
 
-sean