Fedora :: F14 Bluetooth Mouse Won't Auto Connect After Suspend / Resume?
Dec 11, 2010
I'm running Gnome with the bluetooth applet and I have to explicitly use the applet, select the mouse and tell it to connect. It automatically connects just fine when I boot into windows.
I have the same problem with both a Microsoft bluetooth mouse 5000 and a "BLUETOOTH HID v1.02 Mouse [Interlink Bluetooth Mouse]".
Im using a Samsung R420/R470 laptop with Broadcom bluetooth and a Prolink PMO624B mouse.My mouse works when I add it as a new device, but if I off the mouse and on it again, the mouse does not auto connect. I have to press and hold the connection button under the mouse and reconnect to the mouse.The mouse says that it is linux compatible, so I guess its a problem with my bluetooth drivers.
I've just started using OpenSuse 11.2 KDE. I have KDE4.4 installed. I had this issue with KDE 3.4 as well. My HP Multimedia DV3065 laptop is encountering an issue with suspend/restore. After restoring, the mouse is frozen. I have already tried a few things.
1. Dropping to init 1 and then back up to init 5 did not provide a temporary fix. So this is probably hardware related in some sense (kernel?) 2. I tried a grub option (cant remember what it is now). i8500-reset something like that. It made no difference. 3. I tried modifying my 99ZGrub file per another posts suggested solution. That actually locked up my laptop and I could not reboot (even after a cold boot). I pulled the battery and let it sit for a bit and it booted again
So I have several issues.. 1. I would like suspend to restore my mouse. 2. I have not figured out how to program my Sleep button to Sleep. My menu bar icon has Log Out / Restart / Turn Off. The ALT+F1 menu tab Leave has those plus Sleep and Hibernate.
i just installed ubuntu 9.10 netbook remix on my acer aspireone ao532h netbook, and so far, it's been working beautifully. much better than the windows 7 starter edition that came with the machine. the only problem i've experienced so far had to do with the wireless connection. initially, the connection would drop during certain types of activities (e.g. downloading updates or programs, or even streaming videos videos) and the network manager would freeze so completely that i'd have to hard reboot. that seems to have been fixed by installing wicd (following a suggestion here: http://ubuntuforums.org/showthread.php?t=1135723&page=2), meaning that it hasn't disconnected in the several hours since i've been using it. however, wicd has a different problem: it disconnects after a suspend / resume cycle. this requires a reboot to fix also, as not only does it disconnect, but it looses awareness of the network altogether. obviously, this could be a real headache on a netbook that gets closed and opened frequently.
If I suspend my notebook it starts the usual slow orange blinking indicating the suspend mode got reached. There is also evidence in the various log files that this works. If I try to resume it hangs a for 3 seconds and then I get the hdd-password screen from my bios and the notebook boots from zero. I couldn't find anything in /var/log/messages nor dmesg. If I first boot to windows (grub 2nd partition) and then restart and boot to linux, all the suspend works fine
how do i disable the screen lock after i wake my computer from suspend? i would prefer to be able to just wake the computer up and have it go right to the desktop, without having to enter a password. i used to use ubuntu until today, and i remember having to run "gconf-editor" and then switching off on "lock_on_suspend" under apps/gnome-power-management from the menu that popped up. i tried to run "gconf-editor" in fedora 15, but that doesn't appear to exist. i've searched around and haven't been able to find an answer, so i'm wondering if anybody knows what to do?
Starting with kernels 2.6.29.x and above (which includes 2.6.30.x and 2.6.31.x),whether obtained from "kernel.org" of from the "FC11 repository", none of theseresume properly after putting the computer to sleep (suspend)... in my case, via"pm-suspend".When I press the "On" button, I hear the fan, but get no video. And the fan neverreturns to the normal resumed, slower speed -- which it normally does after aroper resume.Eventually I have to issue "Ctrl + Alt + Delete" to reboot. So the computeris resumed to some degree (to have been able to accept that sequence), butnot all the way - no video (and who knows what else)Any ideas -- I've searched high and low. Are there new kernel parametersI have to be aware of when I do a "make oldconfig", and go from there?
I am having a problem with suspend in F15. While the computer enters and resumes from suspend extremely fast (basically instantaneous), the whole system seems sluggish and unresponsive afterwards. The mouse cursor is lagging and some key strokes are omitted when typing. The animations in Gnome 3 are also very non-fluid compared to how they were before suspend. The only way I have found to return to normal operation is to reboot the computer. I have tried 32 and 64-bit versions of Fedora 15 with the problem existing in both. I also tried the latest version of openSuse (Gnome 2.32) just to see if this problem persisted and I can confirm that it did. Perhaps this indicates a kernel-related problem that should be reported as a bug somewhere else?
lspci: Code: 00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11) 00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 (rev 11) 00:08.0 System peripheral: Intel Corporation Core Processor System Management Registers (rev 11) 00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and Scratchpad Registers (rev 11) 00:08.2 System peripheral: Intel Corporation Core Processor System Control and Status Registers (rev 11) 00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous Registers (rev 11) .....
I have a nifty new headset (a JawBone icon�the noise cancellation is incredible) and I've successfully connected it to my Karmic laptop (64 bit, for the off chance it makes a difference). The trouble is, I only occasionally want to connect it to my laptop; I mostly use it with my mobile 'phone.
The two devices fight over my new toy a lot, and invariably the laptop wins, contrary to what I want. It seems a pain to have to rediscover the headset every time I want to use VIOP or whatever, so is there a way to add a device to Karmic's Bluetooth list, but not have it connect whenever it sees it?
I have a new, fully updated installation of F12 which won't resume from suspend (to RAM) on my hardware. I also have the Ubuntu Karmic Live CD which does suspend/resume perfectly on the same box. So, I'd like to try and find out what Ubuntu is doing to make it work and configure my F12 to do the same.
I have an ati 2600 mobile. I am running fedora 10 64 bit. If I have compiz enabled when I resume from suspend I just get a black screen with some garbed colors and I have to hold the power button to shut it off. I have tried turing sync to vblank off. It works fine with no compiz. Is there anyway I can get resume working with compiz enabled?
I recently fixed an annoying problem and I thought it would be nice to share my solution here. The problem was that after a cycle of suspend/resume, Network Manager would only auto-connect to the same network as it was previously connected to. So, for example, if I suspended my laptop at home, and then I went to school and resumed it, it would try to connect to the home network, and then just give up. It would not connect to the school network unless I explicitly told it to.irst, I'll describe the fix. If you're having this problem, you can this. Copy the following:
First of all I have to say I love Fedora, just switched from openSuSE after the system was kinda sluggish the last 2 or 3 versions. But one thing I always liked was the fact that when the system went into suspend my external harddrive spun down and after resuming it spun up again as soon as I tried to access a file. Now in Fedora the harddrive continues spinning and is unavailable after resuming. There is nothing about the harddrive in dmesg, not during suspending and not even when i unplug it after resuming.
I used a live CD burned onto a DVD-RW and it booted up and worked great. So I installed it using the entire hard drive, Ran Update manager, enabled the driver for the wifi card. Before I was using 10.5 with all recent updates done. A few things don't work. It fails whenever I try to connect my Bluetooth mouse and keyboard, CD drive doesn't mount anything, I thought it would bring up the restricted nvidia driver but it doesn't so the video is slow and sketchy.
Running FC13 on Dell E6410. Everything was great until I ran the latest update about a week back. I started to see (or actually not see) that after resume from sleep the mouse cursor will disappear. It is there, just not work showing. If i click on left click on the desktop I get the menu, I can also "see" going over windows from time to time as I move it. I'm currently running 2.6.33.6-147.fc13.i686.PAE I think previously it was /vmlinuz-2.6.33.5-124.fc13.i686.PAE Nvidia driver is 195.36.31
My laptop won't resume after it suspends. It works fine under win 7 so it's not the hardware. The light says it's on and it's pretty much a blank screen. I'm not sure whether it's operational but the screen is off. It has exactly the same resault a waiting for the blank screen except it won't go back on.
I've just upgraded from 9.10 to 10.04 via the upgrade manager. Prior to the upgrade I was able to suspend and hibernate without any problems. Now that I have upgraded to 10.04, I can suspend however when I resume I am back at the gdm login prompt, logging in again with a new session.Having just done another test whilst writing this, it actually appears that if I select suspend from the top right I am suspended and can resume my session. If I close the lid on my laptop (which is supposed to suspend) I am logged out and suspended.Also, Hibernate doesn't work as well - sometimes it never actually hibernates (just sits on a black screen) and sometimes it doesn't resume (it's never hibernated and resumed correctly since the upgrade)
I have an issue with my Sony vaio fw31e not resuming from suspend. Reported this as a bug: [URL] The usual ways of suspending, from the kde 4 menu, from the power/battery widget or by lid closing always result in no resume. However, running pm-suspend from a root terminal suspends and resumes just fine. My question is, how does one delve into the way that the usual methods initiate suspend? Maybe if I could find out what each of these methods actually does, I may be able to see what is going wrong? I had been running squeeze on this lappy since July 2009 with no suspend issues until an update broke it sometime in January. The install is being fully upgraded every day at the moment.
I've upgraded 4 boxes (32- and 64-bit) from Suse 11.1 to 11.2 with no unresolvable issues. Now I'm stuck with my 5th box, a Dell Dimension 8400 desktop box (yes, an old brick, 32-bit). I can suspend to RAM ("suspend") and to disk ("hibernate") fine, but resume seems to fail. In Suse 11.1 I used kpowersave (GUI in the sys tray) to suspend to RAM. For some reason, it couldn't suspend to disk but that didn't bother me. kpowersave relies on the powersaved running.
Note I had upgraded my 11.1 installation to all shiny and new KDE 4.3 stuff, and while KDE 4.3 seems not to use powersaved (and thus kpowersave) all worked fine. Upgrading to 11.2 has removed kpowersave and powersaved. I don't mind switching to another way if only I could find documentation what's being used on KDE 4.3 (and/or Suse 11.2). All I find by googling is that the daemon used is powerdevil, and that I should use a GUI for suspending (this battery monitoring plasma app).
Well, if I do that on this box it simply does -- nothing. So I tried s2ram and a2disk directly:Running s2ram with the --force option works, but the box doesn't resume. Goes on, screen stays blank, mouse and keyboard don't work. s2disk complains about not being able to "stat the resume device file". I gave it the --resume_device /dev/sda6 option, and it hibernated fine. But it doesn't resume. Pressing the power on button just starts Suse anew (and recovers the file system journals, so I assume it thinks it has crashed before).
So I think I have 2 questions: What the heck does Suse 11.2 use for suspend/hibernate and resume? Is there any how-to available to learn what I need to configure? Why can't I resume from successful s2ram or s2disk operations? /var/log/pm-suspend-log or pm-powersave-log don't provide any clues.
Whatever way I suspend my laptop (menu, keyboard shortcut, close lid), it seems to suspend just find (no panic lights, suspend LED indicator flashing as expected). However, when i try to resume, the laptop seems to begin the proper wakeup process (for example, the DVD-drive is tested), there's a lot of HDD activity for about 5 seconds, screen does not power on, and then the laptop just shuts off.
System setup: lucid beta 2, fully updated (just check now) LG E-500 laptop /w nvidia gforce mobile 8400G bios version 1.17 from June 2007 (not sure this is important)
Things I tried: * Completely remove anything to do with gpu drivers and installed nvidia-current driver. * Suspend stress test described here. this didn't work at all. The first test failed (with ac adapter attached) and the second test suspended but didn't automatically resume (see "the behavior" above). Also, when I booted up again, no apport bug report is created. I tried both with rtc set to utc=yes and utc=no. with utc=yes, the second test did automatically resume, but the same problem happened (laptop shutdown while resuming). * The debugging steps described here, but I couldn't get the "no_console_suspend" option to work. I tried adding both "no_console_suspend" and "no_console_suspend=1" (without quotes) to the boot script in the grub menu, but when I did pm-suspend in tty1, the laptop really did suspend. I would like to try to do this again if someone could explain how to add this option.
Notes: * Not sure this is relevant, but when I boot up after a failed resume attempt, wireless network is disabled (this only happens after a failed resume!!!). * I found a package called nvram-wakeup in synaptic that seems to be related to this. This package is not installed. Should I install it? In case this is relevant, forgot to mention I'm running ubuntu in dual-boot along side windows7.
I don't have any problems with 9.04 at all with suspend & resume just shutdown (wont power off usb saitek keyboard & razer mouse) but i don't care for that I prefer suspend & resume. However trying 9.10 suspend works while resume gets a black screen & locks up. Now on 10.04 it will suspend very fast but will not power up from resume keyboard & usb power is turned off thats what I can't figure out I have checked bios & changes settings after settings & nothing happens. I know in windows everything works but i do not want windows at all I prefer linux (ubuntu). In my asus eee pc 1001p suspend & resume works with both 9.10 & 10.04.
When I close my laptop lid (it goes into suspend mode). When I open it again, I can't see anything but a black screen. I have to reset the computer manually to accessUbuntu again.On a related note probably.. for 'some' screensavers, when I click to re-access my desktop, the screensaver freezes, but I can't see the unlock dialogue. I can however still type my password and it will unlock, I just can't see what I'm doing
in kubuntu how can i resume from suspend without password? it annoys the crap out of me i have been looking all over and cant find anything in settings to do this
Karmic 2.6.31-22-generic, Asus M3N78-EM, MCE remote with USB/IR dongle, latest Bios, Bios PM enable and set for suspend S3. IT will suspend but I need to depress case power button for it to resume. I want to use my remote control, I also can not get it to resume from Keyboard/mouse (See Note Below). Only suspend and power button work.
$ lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Laptop 1 is an acer aspire 5570. closing and opening the lid works a few times, after editing acpi_handler.sh, and battery life reporting is ok during this time. then, for no apparent reason, the laptop no longer responds to the lid closing, and no longer seems to be able to read the battery charge state. once this has occurred, the computer will also no longer restart, it tries a few times, with lights flashing and the hd making ugly noises. the only way to extricate the computer from this state is to pull and reinsert the battery.
Laptop 2 is a gateway nv18. suspend/resume with the lid are ok, mostly. the issure here is no display at all in x. but the computer does respond to ctrl-alt-backspace to kill x, with the command prompt returning. still not good. I'm trying a fresh install on the gateway, to see if this was just an installation glitch. Both laptops performed flawlessly in 13 otherwise.
I've been trying to find an answer to the following problem : whenever my PC is put in Suspend/Hibernate mode, it fails to recover when pushing the power button. This happens both with automatic suspend or manual suspend. I've been reading this problem, and mine is quite similar, but no solution is given.
uname -rmi 2.6.18-194.11.4.el5 x86_64 x86_64 PS: this computer is not connected to Internet, no update possible.
I have a quite simple installation of Debian 8 Jessie XFCE and the resume from suspend is not working 9 out of 10 times. The system is single booted if that matters. I have found a few solutions to this problem but they were not suitable to my case as I don't have an Nvidia GPU but only Intel Onboard:
Code: Select all# lspci -v 00:00.0 Host bridge: Intel Corporation 82Q35 Express DRAM Controller (rev 02) Subsystem: Hewlett-Packard Company Device 2818 Flags: bus master, fast devsel, latency 0 Capabilities: [e0] Vendor Specific Information: Len=0b <?> Kernel driver in use: agpgart-intel
When I try to resume, I can hear the system booting but I can't see anything on the screen and the keyboard is not working either (no light on Num Lock and Caps Lock). The only option is to press the power button for a few seconds to stop the machine and then push again to start booting again.
Up until a couple days ago, my computer had no problems suspending to ram. However, now when I suspend, and later hit a key on the keyboard (usually space) to resume, all I see is an illuminated black screen. I can't even open a tty via Ctrl+Alt+F1. I can however ssh into the machine.he only possibility I can think of is that I am no longer running kdm. I just use "startx" to star an openbox-session.
I have installed squeeze on a HP notebook. I have one small problem though.It does not resume from suspend. If I shutdown -> suspend, or close the the lid, or shut downs (suspends) as expected, but whenower it backup up, the screen just stays black.Hibernate is working fine.
output of lspci (if needed) 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)