[Bug 294702] Re: Kernel Panic 2.6.27-7
I upgraded to Jaunty four days ago and I am now using kernel version 2.6.28-13-generic. Kernel panics did not recur. -- Kernel Panic 2.6.27-7 https://bugs.launchpad.net/bugs/294702 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 294702] Re: Kernel Panic 2.6.27-7
Sorry, of course I am using Intrepid, not hardy... -- Kernel Panic 2.6.27-7 https://bugs.launchpad.net/bugs/294702 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 294702] Re: Kernel Panic 2.6.27-7
By now, I am still using Hardy, with kernel 2.6.27-14-generic. I did not have any kernel panics since a couple of months now. Unfortunately, I do not remember the kernel update that made my system stable... I plan to upgrade to Jaunty in a few days. If the problem recurs, I will post the details here. -- Kernel Panic 2.6.27-7 https://bugs.launchpad.net/bugs/294702 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 294702] Re: Kernel Panic 2.6.27-7
I can confirm this: I also get random kernel panics every few days (so the machine freezes, ignores the sysrq keys, and blinks caps and numlock lights). I am using exactly the same kernel version (i.e. the outputs of lsb_release and apt-cache are the same). My lspci output is attached. ** Attachment added: "lspci.log" http://launchpadlibrarian.net/19546059/lspci.log -- Kernel Panic 2.6.27-7 https://bugs.launchpad.net/bugs/294702 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 287159] Re: package libamdxvba1 None [modified: /var/lib/dpkg/info/libamdxvba1.list] failed to install/upgrade: trying to overwrite `/usr/lib32/libAMDXvBA.so.1.0', which is also in package xorg-d
+1 intrepid amd64bit -- package libamdxvba1 None [modified: /var/lib/dpkg/info/libamdxvba1.list] failed to install/upgrade: trying to overwrite `/usr/lib32/libAMDXvBA.so.1.0', which is also in package xorg-driver-fglrx https://bugs.launchpad.net/bugs/287159 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146710] Re: backlight brighness control does not work (Samsung Q45 with Nvidia GForce 8400M)
It seems that as of now, the only option is to deactivate the nvidia driver (temporarily via switching to console mode). This bug is known to NVIDIA for one year now at the very least, as can be seen in http://www.nvnews.net/vbulletin/showthread.php?t=100494 Yesterday there was a post of someone who succeded in changing the brightness under X via a hardware hack: http://www.nvnews.net/vbulletin/showpost.php?p=1815030&postcount=133 -- backlight brighness control does not work (Samsung Q45 with Nvidia GForce 8400M) https://bugs.launchpad.net/bugs/146710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146710] Re: backlight brighness control does not work (Samsung Q45 with Nvidia GForce 8400M)
The backlight keys (fn+up/dwn), the wlan switch (fn+f9) and the brightness function keys (fn+f5/f6) as well generate "unknown key" events and have not the intended effect. Writing to /proc/acpi/video/NVID/LCD/brightness under X has no effect (see SonniesEdge). However, this works outside of X (e.g. ctrl+alt+f1 terminal). This is obviously a bug in the NVIDIA driver, as with the default unaccelerated driver, this problem does not occur. The NVIDIA driver somehow blocks changes to the proc location from having any effect. -- backlight brighness control does not work (Samsung Q45 with Nvidia GForce 8400M) https://bugs.launchpad.net/bugs/146710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146710] Re: backlight brighness control does not work (Samsung Q45 with Nvidia GForce 8400M)
PS: Writing to /proc/acpi/video/NVID/LCD outside of X works, but the brightness keys do not work here as well. Seems like the NVIDIA driver is blocking the brightness update via acpi somehow. I am using driver version 177.80. -- backlight brighness control does not work (Samsung Q45 with Nvidia GForce 8400M) https://bugs.launchpad.net/bugs/146710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146710] Re: backlight brighness control does not work (Samsung Q45 with Nvidia GForce 8400M)
Same here on my Samsung R560 Aura Studentbook (NVIDIA GeForce 9600M GT) on Ubuntu 8.10 Beta. Neither writing to /proc/acpi/video/NVID/LCD (which is the correct file on my machine) nor using the brightness function keys works. Not even under outside of X. Could anyone please investigate in this? This seems to be not taken care of for quite some time now. -- backlight brighness control does not work (Samsung Q45 with Nvidia GForce 8400M) https://bugs.launchpad.net/bugs/146710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 268345] Re: [Intrepid] Start up blocked on "Loading hardware drivers"
PS: I am using the Beta 32bit LiveCD release of Intrepid Ibex. -- [Intrepid] Start up blocked on "Loading hardware drivers" https://bugs.launchpad.net/bugs/268345 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 268345] Re: [Intrepid] Start up blocked on "Loading hardware drivers"
I can confirm this bug on my Samsung R560 Aura Studentbook. As my Ethernet and WLAN were not working with Hardy (similar to Rastaxe and Zugol) I intended to switch to Intrepid. It fails on the line "Loading hardware drivers..." as well, very exactly similar to the screenshot from the bug attachments. Starting without "quiet" and "splash" does not help either. However, the system starts up normally in recovery mode. -- [Intrepid] Start up blocked on "Loading hardware drivers" https://bugs.launchpad.net/bugs/268345 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 255590] Re: System beep goes nuts on start up
I can confirm this bug for Intrepid Ibex Live CD Beta 32Bit on my brand new Samsung R560 Aura Studentbook. -- System beep goes nuts on start up https://bugs.launchpad.net/bugs/255590 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 244591] Re: Cannot connect to ICQ ("The client version you are using is too old.")
I can confirm this bug on Ubuntu 8.04 using pidgin-2.4.2.
Patching with
http://launchpadlibrarian.net/15741199/pidgin-2.4.2-icq.patch as
proposed by noof worked for me.
--
Cannot connect to ICQ ("The client version you are using is too old.")
https://bugs.launchpad.net/bugs/244591
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
