Bugzilla – Bug 570557
openSUSE 11.2 freeze upon logging into wireless access point
Last modified: 2010-01-14 13:39:31 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.6) Gecko/20091201 SUSE/3.5.6-1.1.1 Firefox/3.5.6 Asus 1000H installed with openSUSE 11.2 since release. Recently openSUSE 11.2 freeze upon logging into wireless access point (both wpa or clear) Thought that it was a KDE problem, plugged into ethernet (it works) and installed fluxbox and wicd. Similarly, openSUSE freeze when wicd is in the midst of connecting to my wireless router. System is fully up to date while using ethernet connection (above) zypper refresh - okay zypper update - okay Booted the unit with Debian (Squeeze) through and external drive, everything works perfectly, showing that it is not a hardware related problem. Seems like it is openSUSE related. Posted onto forum and someone confirmed that same problem existed with her/him (http://forums.opensuse.org/install-boot-login/430745-opensuse-11-2-kde-freeze-asus-eee-1000h.html) Please advise is you require any further info, cause I need the unit to be functional and may have to install debian over it (across the weekend). Will try to provide as much info as you require. Hope this info is useful. Reproducible: Always Steps to Reproduce: 1. Boot up 2. Login and connect to wireless access point 3. System freeze, touchpad, mousepad, external mouse all wil not work Actual Results: openSUSE 11.2 freeze upon logging into wireless access point Expected Results: Work and make my happy :D
Why is this assigned to kde-maintainers when it is also reproducble with fluxbox as described in the initial comment and in GNOME according to the linked thread in the forum. Please reassign. For me it sounds like a duplicate of bug 548265
Hi Christian Trippe, do not quite understand what you mean by "Why is this assigned to kde-maintainers". I didn't even know what is wrong with my openSUSE setup that caused this freeze, did i accidentally assigned it to someone? please help to reassign to the appropriate person if i've made that mistake. thanks.
Michal, this bug is probably a duplicate of bug #540589. A fix will be available soon in the KOTD repository [1]. You can either wait for it or downgrade to the original 11.2 kernel [2] which doesn't seem to have the problem. [1] ftp://ftp.suse.com/pub/projects/kernel/kotd/openSUSE-11.2/i586/ [2] kernel-desktop-2.6.31.5-0.1.1.i586.rpm available in: http://download.opensuse.org/distribution/11.2/repo/oss/suse/i586/ *** This bug has been marked as a duplicate of bug 540589 ***
(In reply to comment #3) > Michal, this bug is probably a duplicate of bug #540589. A fix will be > available soon in the KOTD repository [1]. You can either wait for it or > downgrade to the original 11.2 kernel [2] which doesn't seem to have the > problem. > > [1] ftp://ftp.suse.com/pub/projects/kernel/kotd/openSUSE-11.2/i586/ > [2] kernel-desktop-2.6.31.5-0.1.1.i586.rpm available in: > http://download.opensuse.org/distribution/11.2/repo/oss/suse/i586/ > > *** This bug has been marked as a duplicate of bug 540589 *** Hi Leonardo Chiquitto, thanks for the info, have just come across a post http://old.nabble.com/System-freeze-with-kernel-2.6.31.8-and-ralink-rt2860-rt2870-on-11.2-td27109679.html and understand that kernel 2.6.31.8's rt2860 causes the problem. Have downgrade to kernel 2.6.31.5 and things is normal again. do not quite understand what KOTD is and how to use it, appreciate a little detail, thanks.
> and understand that kernel 2.6.31.8's rt2860 causes the problem. Have > downgrade to kernel 2.6.31.5 and things is normal again. Good news. I believe the next kernel update will have a proper fix for the problem. > do not quite understand what KOTD is and how to use it, appreciate a little > detail, thanks. KOTD is the "Kernel of the Day" project. You can understand it as a daily build of the current state of the kernel repository, for each maintained branch. Developers commit new patches to the kernel repository every day and eventually one of these kernels will be released as official updates. Thus, KOTD is always newer than the latest maintenance update and is very useful for testing and verification that some fix will be included in the next update. Hope this helps!