Carl Hartung wrote:

I don't know what you mean by "safe mode" ... AFAIK that's a Windows only term. If you're saying you've already tried booting the system to run level 3 (no X) then this suggestion probably won't work.

I believe he means "Failsafe" which is the term used in openSUSE. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 1/10/2012 6:52 PM, Carl Hartung wrote:

On Tue, 10 Jan 2012 21:44:20 -0500 James Knott wrote:

...

Carl Hartung wrote:

...

I don't know what you mean by "safe mode" ... AFAIK that's a Windows only term. If you're saying you've already tried booting the system to run level 3 (no X) then this suggestion probably won't work. I believe he means "Failsafe" which is the term used in openSUSE.

Ah, of course! See what happens when you end up running a (knock on wood) rock solid system for a few years? You forget about trying 'failsafe' and other boot options ;-) Thanks for the refresher! Yep, meant failsafe... I wrote this from my laptop, running WIndoz, so my brain switched dimensions as well.. LOL.. Thanks, I forgot about the 3 trick, will give that a try...

Marc.. -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 1/10/2012 7:20 PM, Rajko M. wrote:

On Tuesday, January 10, 2012 08:01:16 PM Marc Chamberlin wrote:

...

When I move the mouse, I do get a popup from something called BlueDevil which is asking if I should authorize my Logictech wireless mouse, but since I cannot move the mouse cursor, or do anything with my Logictech wireless keyboard, I am stuck in a Catch22 no-mans land... It is interesting catch. To have bluetooth device working one has to pair that device, which is interesting problem with keyboard and mouse :) In other words you hit nice bug that should be reported.

Try to remove BlueDevil if keyboard works in a text mode. Carl explained how to get there.

zypper search bluedevil will list all related.

zypper remove bluedevil

After that I would reboot, to make sure that something related is not active tough early-xdm.

Hmmm, well attempting to go to runlevel 3 took me down a different rabbit hole.... I reach the login prompt, but the keyboard remains unresponsive. So am unable to log in or do anything... A new "feature" also surfaced, right after getting the login prompt, I am getting a repetition of some sort of instrumented error (about every 10 second) - [ nnn.nnnnnnnn] [drm] nouveau 0000:01:00.0: No native mode, forcing panel scaling The nnn.nnnnnnn is a number which keeps increasing on each line as it is printed out to the screen. This number increments by about 10 to 12 in value, climbs up to 600.9150863 then everything freezes up.... Only option is to reset the computer at this point..... So no joy with the keyboard in the runlevel 3 state... Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 1/10/2012 8:38 PM, Felix Miata wrote:

On 2012/01/10 19:48 (GMT-0800) Marc Chamberlin composed:

...

Rajko M. wrote:

...

...

Try to remove BlueDevil if keyboard works in a text mode. Carl explained how to get there.

...

...

zypper search bluedevil will list all related.

...

...

zypper remove bluedevil

...

...

After that I would reboot, to make sure that something related is not active tough early-xdm.

...

Hmmm, well attempting to go to runlevel 3 took me down a different rabbit hole.... I reach the login prompt, but the keyboard remains unresponsive. So am unable to log in or do anything... A new "feature"

Even when you choose the "failsafe" Grub menuitem, with or without "3" on the Grub line?

...

also surfaced, right after getting the login prompt, I am getting a repetition of some sort of instrumented error (about every 10 second) -

...

[ nnn.nnnnnnnn] [drm] nouveau 0000:01:00.0: No native mode, forcing panel scaling

...

The nnn.nnnnnnn is a number which keeps increasing on each line as it is printed out to the screen. This number increments by about 10 to 12 in value, climbs up to 600.9150863 then everything freezes up.... Only option is to reset the computer at this point..... So no joy with the keyboard in the runlevel 3 state...

I suspect the nomodeset component of failsafe should avoid this (not use nouveau/drm) and let you do your updates and get rid of bluedevil, after which try again the default grub entry. Oh, I am sorry Felix, I didn't make myself very clear... No, I am unable to use the keyboard, regardless of whether I boot to runlevel 3 (text mode) or runlevel 5 (graphics mode), when booting to either the desktop or the failsafe version of 12.1. I have tried all 4 variations, no joy, and was reporting the one unusual anomaly I saw.

But, while I didn't feel this was out of the ordinary, I will report that when I tried to boot the failsafe version, to runlevel 3, I get the login prompt, but further output messages are reported to the screen until it starts phase 2 of the SuSE firewall. That is the last thing reported, quite awhile after the login prompt occurred. I don't have the network configured yet either, so there are some failures being reported in conjunction with network startup, but I figure that as soon as I can get to YaST, I can fix those issues as well. However, that remains a moot point because at this point when output messages stop, I cannot input anything via the keyboard. This discussion has given me an idea however, and I think I have an old PS2 keyboard out in my garage, that I will try and use tomorrow. Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2012/01/10 23:07 (GMT-0800) Thomas Taylor composed:

Since your mouse and keyboard work fine in 11.3 the problem is obviously in 12.1. BlueDevil is the bluetooth interface for an external device and if it hasn't been initialized by the time you reach login it can't see those devices.

If failure to first initialize is indeed the problem, changing PARALLEL_BOOT from yes to no in /etc/sysconfig/boot will likely be a successful workaround that won't necessitate using the PS/2 keyboard.

Were you using this same mouse/keyboard when you installed 11.3? I suspect that it was changed after that install?

You might try attaching a PS2 mouse/keyboard and make sure BlueDevil service is started (Start> Configure Desktop> Startup& Shutdown> Service Manager - make sure BlueDevil is checked). Let us know if that solves the problem.

Another thing to try is using chroot to 12.1 from a 11.3 boot to install sysvinit-init. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2012/01/11 17:16 (GMT-0800) Marc Chamberlin composed:

I tried to uninstall the BlueDevil packages, but that seemed to make matters worse... SO I reinstalled them back in...

As an FYI, the keyboard is a Logitech MX5000 and the mouse is a Logitech MX1000 Both of these connect to the computer via a Bluetooth USB dongle.

I don't understand your last suggestion, using chroot to 12.1 from a 11.3 boot to install sysvinit-init... I sorta understand the idea of "chroot" (in the context that it restricts a user to a certain part of the file system) but the rest of your suggestion flew right over the top of my head... Can you tell me what to do in simpler terms?

A lot of 12.1 problems go away by replacing systemd init with sysvinit-init. To check if it will help, use F5 in the Grub menu. Chroot was about making the switch permanent without any keyboard or mouse while booting/booted to 12.1. Read the release notes about sysvinit-init, which might be key to solving your BlueDevil trouble before systemd init is actually ready for use by ordinary openSUSE users and appropriate updates are available to that effect. http://www.suse.de/relnotes/i386/openSUSE/12.1/RELEASE-NOTES.en.html#12 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 1/11/2012 6:03 PM, Basil Chupin wrote:

On 12/01/12 12:16, Marc Chamberlin wrote:

...

...

On 2012/01/10 23:07 (GMT-0800) Thomas Taylor composed:

...

Since your mouse and keyboard work fine in 11.3 the problem is obviously in 12.1. BlueDevil is the bluetooth interface for an external device and if it hasn't been initialized by the time you reach login it can't see those devices.

If failure to first initialize is indeed the problem, changing PARALLEL_BOOT from yes to no in /etc/sysconfig/boot will likely be a successful workaround that won't necessitate using the PS/2 keyboard.

...

Were you using this same mouse/keyboard when you installed 11.3? I suspect that it was changed after that install?

...

You might try attaching a PS2 mouse/keyboard and make sure BlueDevil service is started (Start> Configure Desktop> Startup& Shutdown> Service Manager - make sure BlueDevil is checked). Let us know if that solves the problem.

Another thing to try is using chroot to 12.1 from a 11.3 boot to install sysvinit-init. Thanks Felix (and everyone) for your thoughts.. I have managed to find a PS2 keyboard, and a USB mouse and can use them to input text and manipulate the cursor. However, still no joy in getting the wireless keyboard and mouse working. It appears as if the BlueDevil manager recognizes both the keyboard and mouse, but only in acknowledging that they are Bluetooth devices. It seems as if, after a few seconds that the manager forgets about them, and the recognition only occurs when the keyboard or mouse is "activated" by either a key press or a mouse movement. Though not entirely, for the mouse I keep getting a popup asking is I want to authorize the mouse or not, every few seconds. I click on the button to authorize it, but

On 1/11/2012 12:37 AM, Felix Miata wrote: that does not do much, except to change the associated icon in the BlueDevil manager from red to green until it "forgets" about the device. But as I said, no joy when it comes trying to use either.

I tried to uninstall the BlueDevil packages, but that seemed to make matters worse... SO I reinstalled them back in...

As an FYI, the keyboard is a Logitech MX5000 and the mouse is a Logitech MX1000 Both of these connect to the computer via a Bluetooth USB dongle.

You are certain that it is Bluetooth and not simply a wireless keyboard and mouse? I am wondering about the MX5000 (or should this be MX5500?) and the different number of MX1000 for the mouse.

If it is Bluetooth, my wife uses Bluetooth headphones for the digital TV and she has to reconnect to the Bluetooth in the TV everytime she wants to use the headphones.

There is some FAQs etc on the 'net so why not do a search or go directly to http://www.logitech.com/bluetooth .

[pruned]

BC

Thanks Basil for your thoughts/reply. I have been doing a LOT of digging on the internet for a solution to this problem, no joy, so went ahead and reported the bug to KDE. I then did some more subsequent Googling around and finally got a hit (helps to use the right terms!) showing that this bug has already been reported to Novell. https://bugzilla.novell.com/show_bug.cgi?id=722763 Hopefully this will get resolved quickly, as I cannot upgrade my media center until it is.... Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org