[Bug 264196] Re: [intrepid] keyboard Repeat Keys is failing to adjust, when AutoAddDevices is on
I am also affected by this bug. I have installed Ubuntu 8.10 through the alternate CD, and afterwards installed Xubuntu-desktop. The keyboard repeat delay was too short, and I could not change it with the Xfce GUI, the Gnome GUI or with the xset command. Interestingly, typing xset q does reflect the changes made with either the GUI or with the xset r rate command, but the actual keyboard behavior is *not* affected. I have yesterday installed Kubuntu 8.10 (through the final release alternate CD) in a friend's computer, and updated it shortly after install. Same problem there. However, I the command kbdrate *does* work in my computer. After I type sudo kbdrate -r 25 -d 500 in an rxvt, the keyboard starts to behave (have not tested yet if the fix lasts after a reboot) -- [intrepid] keyboard Repeat Keys is failing to adjust, when AutoAddDevices is on https://bugs.launchpad.net/bugs/264196 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 190492] Re: Kernel hangs on boot (SATA, AMD64/i386)
I have installed Kubuntu 8.10 yesterday (2008-11-20) in a friend's computer through the final release alternate CD, and updated it shortly afterwards. The problem persists. I am using the workaround pci=nomsi and it appears to work. I am very disappointed. Still no mention in the release notes (which in my opinion is absurd), still no official explanation of what exactly the pci=nomsi workaround does or at least a general statement regarding its safety. Please, at least mention this bug in the release notes. It would save people many hours of debugging. The first time the bug appeared and I didn't know of the workaround, I spent days trying to change SATA configuration in the BIOS setup, examine the hard disk for defects, exchange hard disk, try other Linux versions, and of course a lot of Google searching (and looking in the release notes). Then I finally remembered that months ago I had read in a Wikipedia article that certain motherboards have problems with SATA under Linux; I went to the article and found the treasured workaround. My colleague told me "How do you claim Linux is easy to use, you spent days trying to install it in Wanderson's computer!". This bug is serious. Please mention it in the release notes. -- Kernel hangs on boot (SATA, AMD64/i386) https://bugs.launchpad.net/bugs/190492 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 264196] Re: [intrepid] keyboard Repeat Keys is failing to adjust, when AutoAddDevices is on
>I thought I would give a xset a try but I don't understand the syntax. I think it is clear enough in the man page. The xset manpage has two paragraphs for the "r" option. The second paragraph says If the server supports the XFree86-Misc extension, or the XKB extension, then a parameter of ’rate’ is accepted and should be followed by zero, one or two numeric values. The first specifies the delay before autorepeat starts and the second specifies the repeat rate. In the case that the server supports the XKB extension, the delay is the number of milliseconds before autorepeat starts, and the rate is the number of repeats per second. If the rate or delay is not given, it will be set to the default value. So if you want a reasonable delay of 500ms a a repeat rate of 25 characters per second, you would type xset r rate 500 25 Typing xset q (which shows the parameters in effect) then reflects the change. I does *not*, however, make an actual difference in keyboard behavior (which is probably due to this very bug). My workaround for this problem is adding the line kbdrate -r 25 -d 500 to the file /etc/rc.local This fixed the problem for me, with no visible side effects so far. -- [intrepid] keyboard Repeat Keys is failing to adjust, when AutoAddDevices is on https://bugs.launchpad.net/bugs/264196 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 264196] Re: [intrepid] keyboard Repeat Keys is failing to adjust, when AutoAddDevices is on
(In reply to the immediately previous comment, https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/264196/comments/27) You are welcome. I welcome everyone else to test this workaround, and, if you all like it better than the one involving editing xorg.conf, someone could add it to the topmost (first) post of this bug report, to help people with the same problem who browse this page (assuming it is possible to edit an already-submitted post). And the importance of this bug should be changed from "undecided" to at least "medium" or the like (I don't know what are the selectable values), as it makes the computer use quite annoying, and I imagine would be a show-stopper for disabled people with poor hand dexterity. -- [intrepid] keyboard Repeat Keys is failing to adjust, when AutoAddDevices is on https://bugs.launchpad.net/bugs/264196 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 190492] Re: Kernel hangs on boot (SATA, AMD64/i386)
(In response to immediately previous post, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/190492/comments/33) >Using the pci=nomsi switch is completely safe and harmless. Where did you get that information? And more importantly >However, this bug seems to be fixed in the 2.6.27 kernel. No. I tried to install from the final release alternate Kubuntu 8.10 CD and got hit by the problem. To install, I had to manually used pci=nomsi (using F6 to edit the kernel parameters). Also, I recently (on 2008-11-21) updated the system and tried removing the pci=nomsi workaround from menu.lst. Didn't work, so the workaround is still needed. I don't know why your Sata DVD drive now works, but for me the problem has remained the same until now. I have no idea whether this but affects Sata DVD drivers differently from Sata HD drives, or if your bug was a different one. -- Kernel hangs on boot (SATA, AMD64/i386) https://bugs.launchpad.net/bugs/190492 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 190492] Re: Kernel hangs on boot (SATA, AMD64/i386)
Well, let me make two corrections to my post: 1) "tried removing the pci=nomsi workaround from menu.lst. Didn't work". To be precise, I didn't actually edited menu.lst, I used the handy Grub editing capacity to remove pci=nomsi from the kernel command line. 2) "I have no idea whether this but affects (...)" I obviously meant "this bug", not "this but". And more importantly I have not only tested the 8.10 alternate Kubuntu CD, but also 8.10 final CD (don't remember if it was liveCD or alternate), and this bug also appears there (as expected - Kubuntu and Ubuntu share the same kernel and much else) -- Kernel hangs on boot (SATA, AMD64/i386) https://bugs.launchpad.net/bugs/190492 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 37138] Re: Location ignored
This bug is still present in 8.04.1 and 8.10, which is depressing. In both cases I installed through the alternate installer. Right in the boot prompt I chose English language and Brazilian keymap. Later, when asked, I told I live in Brazil. But the locale was all set to en_US.UTF-8. I had to manually edit /etc/environment and /etc/default/locale. They now contain: [EMAIL PROTECTED]:~$ cat /etc/environment PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games" LANG=pt_BR.UTF-8 LC_MESSAGES="en_US.UTF-8" LANGUAGE="en_US:en" [EMAIL PROTECTED]:~$ cat /etc/default/locale LANG="pt_BR.UTF-8" LC_MESSAGES="en_US.UTF-8" LANGUAGE="en_US:en" Why doesn't do installer do something like this automatically? -- Location ignored https://bugs.launchpad.net/bugs/37138 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 190492] Re: Kernel hangs on boot (SATA, AMD64/i386)
I also confirm that the problem persists with 8.10 beta - I don't know if there has been more than one beta, so be informed that I used the iso CD image named ubuntu-8.10-beta-alternate-i386.iso, with md5sum 108696aafe01d4e90ee145c31ad05b82. I burned it to a new blank CD-R at low speed (8x), checked the CD for defects, and none was found. With a normal boot, the HD is not detected. With the pci=nomsi kernel parameter, the HD is detected (I didn't proceed to install the system though). The motherboard is an ASUS a8v-x. The hard disk is SATA. In the BIOS setup, the item 'Serial ATA IDE controller' is configured as 'SATA'; the options are 'Disabled', 'SATA', 'RAID' and 'AHCI'. Changing to 'AHCI' didn't seem to help. I have not tried 'RAID', nor (obviously) 'Disabled'. I have attached, in .tar.gz format, the output of dmesg, lsmod, lspci -vv, /proc/cmdline and /proc/cpuinfo for two situations: with a normal boot (except that I removed the 'quiet' kernel parameter) and a boot with the 'pci=nomsi' kernel parameter (and 'quiet' removed too). In both cases, I booted with the alternate CD, chose English language, Brazilian keymap, edited the boot parameters, then allowed the installer to reach its first prompt. Then I switched into a virtual console and gathered the previously mentioned information, saving it into a pen drive. My attempt to install Linux in that computer involved Ubuntu 8.04 (failed to install), then Ubuntu 7.10 (failed to install), then Debian Etch. Debian Etch installed successfully, but was unstable. KDE would sometimes abruptly disappear and the system would go back to KDM. Then, since NTFS-3g complained that Debian Etch's 2.6.18 kernel was too old, I tried 2.6.24. Didn't work, with error messages similar to Ubuntu. I tried 2.6.26 from Lenny, with the same problem. I then read http://en.wikipedia.org/wiki/Ahci#Common_problems_switching_to_AHCI_under_Linux, saw that VT8251 is faulty, confirmed that this chip is present on the computer, and tried the pci=nomsi workaround. Now the Debian system seems to work stably (and NTFS-3g works without complaints). I beg you to mention this bug in the Intrepid Release Notes, along with the pci=nomsi workaround. And it should be explained wether or not this workaround has bad side effects (I don't know. I have read the MSI- HOWTO.txt from the kernel documentation, but I still don't know if pci=nomsi is safe). Of course, making the installer automatically detect the faulty chip and work around the problem would be excellent, if viable. Even better would be to change the kernel itself. Of course, if you make any additional information request, I will respond as quickly as possible. Thank you for working in this excellent OS, Jorge Peixoto from Brasil ** Attachment added: "dmesg, lsmod, lspci -vv, /proc/cmdline and /proc/cpuinfo on two cases: normal boot and boot with pci=nomsi kernel parameter" http://launchpadlibrarian.net/18648074/information_of_system_with_and_without_pci-nomsi_kernel_parameter.tar.gz -- Kernel hangs on boot (SATA, AMD64/i386) https://bugs.launchpad.net/bugs/190492 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 190492] Re: Kernel hangs on boot (SATA, AMD64/i386)
This problem has reached Intrepid final. Why wasn't it at least mentioned in the release notes? Anyway, I have tested the problematic computer with Mandriva one 2009 (gnome CD), and the problem does *not* seem to appear. I have attached some information about the computer when booted trough the Mandriva CD. ** Attachment added: "dmesg, lsmod, lspci -, /proc/cmdline and /proc/cpuinfo on problematic computer booted with mandriva CD" http://launchpadlibrarian.net/19145628/mandriva_one_2009_gnome_debug_data.tar.gz -- Kernel hangs on boot (SATA, AMD64/i386) https://bugs.launchpad.net/bugs/190492 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 190492] Re: Kernel hangs on boot (SATA, AMD64/i386)
Note: the description of the attachment above says lspci -, but the actual command I used was lspci -vvnn. Sorry. -- Kernel hangs on boot (SATA, AMD64/i386) https://bugs.launchpad.net/bugs/190492 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 190492] Re: Kernel hangs on boot (SATA, AMD64/i386)
I have retested Ubuntu 7.10 and it seems to be able to detect the disk. I don't remember what went wrong the last time I tried 7.10 and prompted me to install Debian Etch, but It seems that Ubuntu 7.10 is able to at least detect the disk. Also, my previous attachment had the output from lspci -vv. This new one has output from lspci -vvnn (again from Intrepid Beta, with and without the pci=nomsi kernel parameter). ** Attachment added: "lspci -vv, lspci -vvnn and /proc/cmdline on two cases: normal boot and boot with pci=nomsi kernel parameter" http://launchpadlibrarian.net/18795092/new_information_of_system_with_and_without_pci-nomsi_kernel_parameter.tar.gz -- Kernel hangs on boot (SATA, AMD64/i386) https://bugs.launchpad.net/bugs/190492 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
