Linspire/FreespireThis Forum is for the discussion of Linspire and Freespire.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Debian Sid, SourceMage 0.9.5, & To be Continued on a TP
Posts: 800
Rep:
Mouse Locks up Box
I just recently installed Lindows DE at work on an old Compaq P300 box, I think it's a 300mhz. Everything seems to be doing fine until after awhile when I move the mouse, it locks up Xwindow. I can't even use Cnt-Alt-Backspace to get to the console, I have to press the power button to restart.
I even switched the mouse to make sure the first one was not a problem and both seem to do the same thing.
Any idea why this is happening? The mouse is a regular ps/2 mouse, two button.
Got the same thing on a laptop with a mousepad. Have no idea what's causing it, but it appears to be related to being connected to a network, 'cause when I'm not connected the mouse has no problem. And it often occurs after/while downloading a file from the net.
It sounds like this is coming from a hardware conflict of some sort. Can you open a console (L > Programs > Utilities > Console) and type this:
cat /proc/interrupts [hit ENTER]
You can highlight the text that is displayed in the console and leave it selected. Then, go to another window where you want to paste (like this forum reply box!) and click the left and right mouse buttons simultaneously. This should copy and paste your results from the console to the forum so we can see what IRQ's you are using. There might be a conflict of somesort going on with your other hardware?
Which version of LindowsOS are you using?
You can go open CNR (click and run) and go to HELP > ABOUT to find your version.
It appears that you have quite a few things all trying to share IRQ 10. This might be causing a problem?
Under your BIOS settings have you made sure that "Plug-N-Play OS" is set to NO or DISABLED?
Yenta is a driver for PCMCIA / CardBus device. What kind of network card do you have?
ohci_hcd = USB devices.
It appears that your USB is conflicting with your PCMCIA card by sharing resources. That is why everytime you access the network it locks up. What USB devices are you using?
Last edited by linspirekendall; 03-04-2004 at 02:33 AM.
I don't have a PnP option in my BIOS.
I use a D-Link DE-660+ network card (NE2000-compatible).
I don't use any USB device, but have USB support enabled because I occasionally use an externel USB hard disk. If that's causing the problem I could recompile the kernel and leave USB support out of it.
Since you mentioned PCMCIA conflicts, maybe it's worth mentioning that quite often during boot (not always though), the card service fails to map appropriate memory:
[Edit: these errors occur after I have to force my way out of the mouse-lock by holding the power button]
cs: warning: no high memory space available!
cs: unable to map card memory!
cs: unable to map card memory!
cs: unable to map card memory!
cs: unable to map card memory!
cs: unable to map card memory!
cs: unable to map card memory!
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x3c0-0x3df 0x480-0x48f
cs: IO port probe 0x1000-0x17ff: excluding 0x1000-0x110f
eth1: NE2000 Compatible: io 0x300, irq 3, hw_addr 00:50:BA:38:02:41
Some additional info:
Last night I disabled USB support and recompiled the kernel, but USB ports are anyway detected and /proc/interrupts still shows those 3 competing for IRQ10. And the mouse still locks up...
Regarding PnP:
I have the kernel compiled with:
PNP yes
ISAPNP yes
PNPBIOS yes
Are you using a ps/2 mouse? Try a USB mouse. This may solve your problem. Not a fix but a solution none the less. May want to consider an equipment upgrade?
Distribution: Debian Sid, SourceMage 0.9.5, & To be Continued on a TP
Posts: 800
Original Poster
Rep:
Well the computer with Lindows 4.5 DE is not connected to internet at this time, but using the cat /proc/interrupts command only show usb-uhci & eth0 sharing the same irq(11) and mouse is on 12, nothing else is sharing.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.