I have installed a 2.6.32-5-bigmem kernel on my Dell 790 computer since than the non of the USB devices are not recognized (keyboard , mouse , pendrive , etc ..). When running lspci the usb is listed as unknown device. When loading 2.6.26-2-bigmem kernel in the same computer the usb devices work fine.
View 1 RepliesSometimes when I reboot, I go to log on only to find that the mouse won't move and the keyboard does nothing. Well, the mouse moves, it's not glued to the desk or anything. But it doesn't move the cursor. The first few times this happened, I found that it was a music player or other USB device plugged in that somehow created confusion or something. So if I unplugged them and booted up again, everything was fine. And by booting up again, I mean I have to hold down the power button and forcibly shut the thing off, since I obviously can't do it the nice way with no mouse or keyboard.
Anyway, it's been doing it now more often, even with nothing plugged into the front USB ports. But I have found that if I disconnect my external hard drive, it boots up fine again. But that's obnoxious, because that hard drive is online as much as the computer itself, because it's my main repository for files. So I have to unplug the USB from the back of it, hold the cable so it doesn't fall behind the desk, turn on the computer, and then log in one-handed while I hold the cable (because if I just plug it back in before the desktop shows, it doesn't mount properly).
And I know it's an Ubuntu thing rather than a general computer thing because the bios options work just fine. In fact, the little NumLock light is on until the moment that Ubuntu starts up and shows the login dialog.
I'm installing slack 13.0 in a Dell 2350 for a friend. once installed, it works ok for a while then within some somewhat random period of time, just plain locks up. the keyboard stops working, the mouse cursor still moves, but there is no response from mouse clicks. i was ssh'ed into the machine one of these times to see if i could read the logs during a lockup. the machine stopped responding to the ssh session as well (actually i had an instance of mc running at the time, and the machine still responded to it. when i exited mc, i was stuck in console never-never land). the logs show absolutely nothing. /etc/messages keeps showing MARK long after the lockup. all other logs are not updated since boot. this machine has an i810 chipset, is there a driver issue here?
View 6 Replies View RelatedDebian seems to recognize me touchpad as PS/2 Generic Mouse so tapping works but I don't have touchpad in system preferences and two fingers scrolling doesn't work as well as two fingers zoom. Notebook is Samsung 530u3c. I give you some info about my system down below.
uname -a
Code: Select allLinux debian 3.2.0-4-amd64 #1 SMP Debian 3.2.54-2 x86_64 GNU/Linux
lspciCode: Select all00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
[Code] .....
my mouse wouldn't work in any fashion after going through most of the install process from Debian Lenny to Squeeze (couldn't click, move the mouse, etc. under both Compiz and Metacity). My system is a Lenovo ThinkPad T61 laptop; I keep the touchpad disabled, but the button mouse (TrackPoint) wouldn't work either. I was following the instructions here:
[URL]
So, the first thing I did was run the following commands, as it says to do:
# apt-get upgrade
# apt-get install linux-image-2.6-686
# apt-get install udev
Then, I rebooted my machine into the new kernel (2.6.32-5-686). I got a ton of udev warning messages at startup (all along the lines of "SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in something-or-other" - details can be provided if needed), but got a functioning prompt. I logged in, ran startx, and everything worked except the mouse, which couldn't do anything - as if it wasn't recognized at all. Switching window managers from Compiz to Metacity, as mentioned before, didn't help. "modprobe psmouse" revealed that that module was correctly loaded.
Rebooting into my old backported kernel (2.6.32-bpo.3-686) restored mouse function, although I still had the udev warning messages (so maybe those aren't relevant, I don't know). Apparently, something about the different kernels is causing the problem, but I'm not sure what - any thoughts? I haven't wanted to complete the upgrade with "apt-get dist-upgrade" without knowing that I'll have a working mouse, since I need a functional GUI at the moment and don't have a good way of fixing it if I trash it.
I'm having a weird problem with my keyboard. I have to hold on to the key that I want typed for about 1 whole second for it to be entered... the mouse click is okay, it's just the keyboard.Here's a rough outline of what happened, and the significants events that took place on the desktop that this is happening on.The computer originally had Debian Lenny on it. At some point of time, I just started getting everything from backports... and after some things and hops later, the computer does in fact report having Debian 6.0.Anyway - I again did an upgrade... and now the problem occurs.
View 1 Replies View RelatedFor some reason I am unable to use either my keyboard or my mouse. No problem in etch up until now, even after rebooting.
View 1 Replies View RelatedAs the title says i have this error on both my main computer and my laptop. For my main computer see this post, that is when it happened. viewtopic.php?f=30&t=65743
I run the updates on my laptop a while ago and decided to restart it to check if everything went okay. It seems not.
The only way i can get on the desktop, is to choose the recovery mode, su to user and startx.
This is a common error during booting on both computers. Starting the hotplug events dispatcher: udevderror binding control socket, seems udevd is already running
It seems a little strange, same error on both computers.
So here is my situation..i was using win 7 and ubuntu 10.10 in my dell studio 1555. and i wanted to try out debian so i installed debian in my pendrive. so the grub was modified. when the computer starts it shows debian,ubuntu and win7 no problem.. but if i remove the pendrive, nothing comes up. it shows grub rescue>..
so now i cant start up unless i plug in the pendrive. what to do now to solve this problem?? i want to restore my grub to the previos state.
I use a set of keyboard + mouse Logitech MK330. So, they are wireless in five minutes of inactivity have to sleep. But sleep only the keyboard. The mouse does not fall asleep. On distro Ubuntu and Windows goes into standby mode, both devices. How can I fix it to Debian?
During installation Debian distro, mouse goes to sleep, but on the installed system will not go into standby mode.
So it's a beautiful day and I'll be happily using my computer when I realise that the screen is no longer showing that I'm typing or moving my mouse (or finger across a touch-pad). I can leave my computer in this frozen/crashed state for hours. My only recourse is to drain the battery or hold down the power button until the computer shuts down. The computer is a Dell Inspiron 6400 laptop/notebook. As my memory serves, it has an ATI graphics thingy. Radeon 1400, maybe. But I've had the computer for years and this behaviour has emerged only the past couple of months, with seemingly increasing frequency.
The OS is
# uname -a
Linux polaris 2.6.32-trunk-amd64 #1 SMP Sun Jan 10 22:40:40 UTC 2010 x86_64 GNU/Linux
(aka Squeeze?)
Sometimes this happens within minutes of turning the computer on and logging into Gnome. Sometimes this happens only hours after I've started using the computer (mainly just surfing the web). Sometimes it is preceded by a loud boop sound and the following if I have console open, sometimes not. So maybe that's unrelated. But that happened just now so I thought I'd throw it in.
One weird thing: Usually this happens within an hour of starting to use the computer, but one occasion I noticed I had not had the problem for several hours. On that occasion, the only thing I noticed I was doing that was also unusual: I had turned on and forgotten about a kvm virtual machine. After I shut down the vm, I had about only a minute before the freeze. I'm surprised now that it hasn't frozen since I started typing thing. Maybe I should always keep this forum open in a browser window.
A couple of weeks ago I installed a new 4-core Lenovo PC and installed Squeeze on it - keeping it updated every day. When kdm or gnome display the login screen, my USB-connected keyboard and mouse don't react. When I then unplug and re-attach them into the same socket everything ist fine. Surely this can't be working as intended? I can however get into BIOS-Setup as usual during the initial boot-phase by pressing Crtl-S and F1. Things also are fine when selecting the debian version to run from the multi-boot screen.
I am enclosing the kern.log of the last boot below (don't know how to attach files!). In that I can see that on line 530 ist says New USB device found, idVendor=046d, idProduct=c03e (address: 5; optical Logitech mouse) and then on line 542 New USB device found, idVendor=046d, idProduct=c31c (address: 6; keyboard).
It seems to get "interesting again on line 632 etc. with the message usb 2-1.8: USB disconnect, address 6.
-------------------------------------
2.754607] usb 2-1.5: new full speed USB device using ehci_hcd and address 4
2.855589] usb 2-1.5: New USB device found, idVendor=046d, idProduct=0a0c
2.855594] usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
2.855598] usb 2-1.5: Product: Logitech USB Headset
[Code]....
I've just installed Debian Testing XFCE, and mouse & keyboard don't respond to any inputs. The keyboard works just fine in the Recovery Shell, that's why I suspect a problem with the XServer.
View 9 Replies View RelatedI have debian with kde on a laptop with a built in ps/2 keyboard and touch pad mouse which have been working without problem since i bought the computer. However, recently i booted the computer up and all of a sudden the mouse and keyboard are not functioning. I know it is not a hardware problem because i can type in the BIOS password, make the selection between normal and recovery mode in grub, and can type in all of my passwords to unencrypt my hard drive.
Also, it recognizes the keyboard all the way up until the point where kde starts, at which point it loads a login screen with the mouse and cursor on the screen, but no ability to type, not even caps lock or ctrl+alt+f1 to switch to console mode. does anyone know why this is? I have performed not updates and have not changed the configuration of my computer so i am not sure why this would happen.
P.S.1 out 15 times when i load the part where i need to type in the passwords to unencrypt the hard drive the keyboard will stop working then instaed of with kde.
I am using Debian with a gnome desktop.
Code: Select alluname -a
returns
Code: Select allLinux app-server 3.2.0-4-amd64 #1 SMP Debian 3.2.65-1+deb7u1 x86_64 GNU/Linux
My desktop sometimes freezes and does not respond to keyboard or mouse. I initially thought the CPU was overheating but it froze tonight when my CPU temperature was 32C and it has been up to 50C without freezing. I am beginning to think it is a software issue rather than a hardware issue but do not know. I looked at the pm-powersave.log and user.log but did not see anything suspicious.
I was trying to tweak my video card's performance by configuring the xorg.conf file. There were many lines unrelated to the card there; so, to make the file cleaner, I decided to delete all the sections except the one I was dealing with. Obviously I shouldn't have done that. After rebooting the system, all the hardware that provided human interface stopped working. Now I have to find a way to delete that xorg.conf file. The computer is still connecting to the internet, and I have another computer running Debian available. Is there a way to access the broken computer with the other one?
View 4 Replies View RelatedAfter installing KDE USB keyboard and mouse won't work. They are added to /proc/bus/input/devices though.
I also tried to install Gnome; same thing.
I took #usb-devices and they were there also..
But #usbhid-dump did not generate anything to screen.
I have Asus Z87-PRO motherboard with i5-4670k and I'm trying to install Debian Testing with 64-bit architecture. My problem is mouse and keyboard (I guess USB in general) stop working after installer get loaded (the last thing I do is choose between text and graphical install). I found a few topics on different forums indicating that I should enable IOMMU (Intel VT-d) option in my bios.
The problem is that Intel k-series processors didn't use to have IOMMU support, so there's nothing I can do about it. I tried changing different bios options like disabling UEFI, enabling xHCI and EHCI with no luck. Passing "iommu=off" or "iommu=soft" to the boot command also doesn't work. However, I have LMDE 2 64-bit live cd (based on Debian Jessie) and it works fine, so I guess my problem may be related to some changes in 4.2 kernel.
I'm trying to net install Wheezy on an Abit IC7-G PIV system. I tried this months ago but the problem still exists. This is not so much an installation problem but after installation when it boots, I lose PS/2 mouse, PS/2 keyboard and network. I get:
startpar. service(s) returned failure udev ... failed I can plug USB mouse and keyboard in after this failure which then works. There is nothing wrong with the hardware. It works fine on other systems. Squeeze works perfectly.
I installed a copy of Debian Jessie server and then tried to install a light GUI, specifically XFCE4. I am accessing my installation directly via a mouse/ keyboard and monitor, not remotely. After installing the Debian server software, I ran the following commands: apt-get install xfce4
It all appeared to go well, with no error messages. I then tried to launch the XFCE4 interface by running the following command: xfdesktop.However, all I get is the following error message:Failed to parse arguments: Cannot open display.what I need to do here to succesfully launch XFCE4?
i immigrate to Debian Squeeze. So, for each time i want to start debian i have a kernel panic and ( mouse + keyboard blocked ), I can't use anything.Here is my kern.log pastebin
View 6 Replies View RelatedI use the debootstrap to make a base Debian System of the ARM architecture for BananaPro [URL]... , and install the LXDE desktop. But the keyboard and mouse didn't response after the LXDE boot.
If I use the Debian system without the LXDE desktop, and it is normal. Meanwhile, I only installed the framebuffer driver, and can't find the right GPU driver to install.
Is caused by the lack of the GPU driver ? and what should i do ?
I get some error logs from /var/log/Xorg.0.log file,as follows:
Code: Select all[Â Â 17.206] (II) Module shadow: vendor="X.Org Foundation"
[Â Â 17.206]Â Â compiled for 1.12.4, module version = 1.1.0
[Â Â 17.206]Â Â ABI class: X.Org ANSI C Emulation, version 0.4
[Â Â 17.206] (==) Depth 24 pixmap format is 32 bpp
[Â Â 17.207] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[Â Â 17.211] (==) FBDEV(0): Backing store disabled
[Â Â 17.212] (==) FBDEV(0): DPMS enabled
[Code] ....
I have a problem with mouse and keyboard. Both freeze within 30sec to half an hour after logging into squeeze 64bit (using gnome). My hardware is Asus P7P55D EVO (tested with linux according to ASUS) with Intel i5 760 CPU. I use IBM keyboard and Trust PS2 mouse. I also have MSI HD4350 graphics card, that was at least listed on Ubuntu to be supported, worked fine also with Lenny.
When using same combination with Lenny (64-bit) I never found any problem with either keyboard nor mouse, even running long nights. However there was need to upgrade to Squeeze since it has newer kernel supporting the sensors on board my MB. I used same mouse and keyboard also on Ubuntu 9.10 and had never problems. However when I upgraded to new MB I started with Ubuntu 10.04 64 bit version and experienced same keyboard and mouse freeze as I have now in squeeze. Only way out from this status is hard reset using PC reset button.
I connected with putty to my linux box and found following (while the linux box was on frozen state) from dmesg on keyboard: :/var/log$ dmesg | grep -i keyboard [ 1.064628] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
I rebooted my system about a few days ago to find that whenever X was started, my mouse and keyboard would not function. I am unable to even switch to another tty when this occurs, however alt+sysrq+r will allow me to switch ttys again.
Xorg.0.log
[ 70.287]
X.Org X Server 1.10.1
Release Date: 2011-04-15
[code]....
anyway the reason for my posti downloaded a network install of wheezypartitioned and loaded wheezy on to a dell latitude d600now after installation the keyboard and mouse ( touchpad or nipple ) do not functionsince this inconvenience i have been plugging in a usb keyboard and mouse at the graphical login then using them to work the laptopAfter a reboot the usb peripherals do need to be uplugged and reconnected otherwise they also do not functioni am obviously missing something vital here but i am not sure where to start, kernel 2.6.38.2-686
i have loaded the non-free repos added the various firmware files etc. to get wireless and bluetooth to functionbut the keyboard and mouse has me stumped i have searched the forum and google but haven't come across anyone with the same issue.Some forum suggestions have been to reconfigure xorg.conf but this does not exist on this installevdev - the event driver is thereudev - the kernel device manager is also there
I'm running Lubuntu 10.04 on a Thinkpad T41. I had been running for a week before realizing that my USB devices (card reader and thumb drive) were not being recognized. I thought that the issue might be related to my aging Thinkpad but I installed the hard driveat is running Slackware and I had no issues with USB devices. I reinserted the hard drive with Lubuntu and was unable to recognize any USB devices.Has anyone else noticed this issue? If so, is there a fix for this issue?
View 9 Replies View RelatedAfter the usual mild annoyances inseparable from a Fedora release (installation from the LiveCD worked OK, but generated a requirement for 162MB of day-one updates, followed by something like 150MB of downloads to install OpenOffice - which comes as standard with Ubuntu/Mint/Mandriva and, no doubt, many other distros) I have been able to get the system working reasonably well. If there are major performance gains from the use of ext4, I have been unable to detect them. However, the only really frustrating issue from my perspective has been the difficulty in getting my two printers (both of which worked straight out of the box in the other distros mentioned above) to actually print. The devices in question are a Brother 2140 laser printer and an HP 2280 multi-function inkjet.
Both of these devices were properly recognised by the system, but neither would actually print (there were some initial signs that action was imminent, but no result - the printing processes were finally shown as having been stopped). I removed both printers, and started from scratch. The laser printer could not be persuaded to work, either with the recommended 2170 driver or the old faithful 2060-gutenprint driver. However, when I tried to add the HP, the printer utility advised that I needed to install "hpijs" before proceeding. This I duly did, and the HP 2280 then worked fine. On the basis that my only aim was to get the printers working, I decided to ignore the recommended drivers for the Brother 2140, and select the "2060-hpijs" version. This worked fine, and others may like to try this workaround.
Jaunty is fully updated but SUDDENLY is not recognizing external devices (card reader, camera, DVD inserted in drawer, etc.) In other words, I cannot see my media and, therefore, cannot open it.
Anybody else having problems here? What's up? Did something go wrong in the updates?
(AMD64 running stable Jaunty 9.10 fully updated)
After setting the "nomodeset" kernel parameter, to install the nVidia proprietary driver in OpenSuSE 11.3 (I need to do CUDA development), my Sansa Clip+ is no longer recognized. When I turn the "nomodeset" option off, I can see it with $(fdisk -l).
View 1 Replies View RelatedIm considering installing Open Suse linux on my laptop - Lenovo Thinkpad T510i. Will all the devices be recognized?
View 2 Replies View Related