[Bug 300090] [NEW] Added RAM - lost connection to 2 SATA-drives. Removed RAM and drives work again
Public bug reported: Ubuntu 8.04 LTS 64-bit desktop being used mostly as server. The server was running fine for considerable time before I took it down to install 2GB ram (1 module) in addition to the 2 x 1GB-modules already installed. After doing so it would not recognise drives connected to the PCIe-SATA- card, despite checking wiring, testing with different wiring and 4 distinct drives (3 x Samsung 500GB, 1 x Seagate 80GB). Rebooting did nothing to aid, only when I removed the RAM-module did it work properly. NOTE! Everything else appeared to work fine; Gnome, Partition manager, FreeNX-server, internet, etc. Hence the specific RAM-module is not of itself faulty. With the help of erUSUL on IRC: #Ubuntu i got the following verified: Driver loaded and running. $ lspci 03:00.0 RAID bus controller: Silicon Image, Inc. SiI 3132 Serial ATA Raid II Controller (rev 01) rmn: driver is sata_sil24 run « lsmod | grep sata_sil » does it output something ? sata_sil24 20484 2 libata176432 5 ata_generic,pata_acpi,pata_atiixp,sata_sil24,ahci $ dmesg [ 850.947249] ata1: reset failed (errno=-5), retrying in 8 secs [ 858.725083] ata1: hard resetting link http://paste.ubuntu.com/74488/ A number of these lines appear fo ata1 and ata2, until it gives up. In dmesg.1.gz the following lines appear (also in kern.log): [ 345.748858] end_request: I/O error, dev sr0, sector 1278024 [ 345.748865] Buffer I/O error on device sr0, logical block 159753 [ 345.752028] end_request: I/O error, dev sr0, sector 1278024 [ 345.752031] Buffer I/O error on device sr0, logical block 159753 Hardware: MB: ASRock AliveXFire ESATA 2 CPU: AMD Athlon 64 X2 4000+ RAM: 2x 1GB Kingston ValueRAM DDRII PC667 CL5 RAM: 1x 2GB Kingston ValueRAM DDRII PC667 CL5 VGA: Galaxy GF 7200GS PCIe 128MB PCI: Delock PCIe 2xSATAII Raid (drives not run in RAID) Summary: The only symptom I noticed was that I lost contact to the drives, and got an error-led on the drive-bay. hddtemp failed, etc. The symptom only occured after adding RAM, all other things equal. The symptom did not go away by checking/replacing cables and drives. The symptom did indeed go away by removing the extra RAM-block, all else equal. ** Affects: ubuntu Importance: Undecided Status: New -- Added RAM - lost connection to 2 SATA-drives. Removed RAM and drives work again https://bugs.launchpad.net/bugs/300090 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 289918] Re: Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
The problem with the evdev-solution is that it causes problems for those users that may be on the physical machine. E.g. when I log into my home server over FreeNX the keyboard now works. However if I log in locally the keyboard is broken (same problem - except now in reverse). Hence one must either change the keyboard layout every time one changes login method, or one must choose which keyboard is more important; remote or local. There have been a number of updates, but the problem seems to persist. -- Regression: Connecting to FreeNX breaks keyboard layout in Intrepid https://bugs.launchpad.net/bugs/289918 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 355516] Re: Grub Error 18, when install Kubuntu (9.04 beta) with encryptet LVM
(gnome) Ubuntu 9.04 alternate disc (final), (gnome) Ubuntu 9.04 standard disc (final) IBM R40. Both the regular install from the standard disc *and* the "Guided - encrypted LVM" from the alternate disc failed with Grub Error 18. Workaround: Did a "Guided - use entire disk", but with a custom /boot-partition of 150 MB in the start of the disk. This turned out to work. -- Grub Error 18, when install Kubuntu (9.04 beta) with encryptet LVM https://bugs.launchpad.net/bugs/355516 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 281499] Re: Changing from kernel 2.6.27-5 to ...-6 and ...-7 breaks boot. LUKS, USB
I found the cause for the problem on the Desktop Dell with the -4 kernel, which might shed some light on what the problem might be for the -6 and -7. The latest update on October 15th did not help. On the desktop I had forgotten to load the modules in initrd. When doing this error the behaviour was exactly the same as on the laptop. As such I presume that some of the modules have either been renamed or are no longer available. The script depends on the following modueles in /etc/initramfs-tools/modules: vfat fat nls_cp437 nls_iso8859_1 Is there a way to see whether those modules have been loaded into an initrd - to rule out that the problem is caused by not rebuilding initrd correctly? -- Changing from kernel 2.6.27-5 to ...-6 and ...-7 breaks boot. LUKS, USB https://bugs.launchpad.net/bugs/281499 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 281499] Re: Changing from kernel 2.6.27-5 to ...-6 and ...-7 breaks boot. LUKS, USB
When I boot with the intention of authenticating from the USB-stick I usually plug it in at BIOS, at which time BIOS recognises it. Since there is no OS on it it continues to GRUB. I just tried booting with ...-7 again, and got the same result. However I tried to pay attention to the USB stick LED, which lit up at more or less the same point as with ...-5 (which boots successfully), but my impression was that it was lit for a longer duration. I still cannot enter the password normally with -7. -- Changing from kernel 2.6.27-5 to ...-6 and ...-7 breaks boot. LUKS, USB https://bugs.launchpad.net/bugs/281499 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 281499] Re: Changing from kernel 2.6.27-5 to ...-6 and ...-7 breaks boot. LUKS, USB
I just did a stock install of the pre-beta on a Dell desktop (Intel P -III-generation). The machine does not have a connection to the net at the moment, and as such I have not upgraded the kernel. Pre-boot authentication was working fine, but even at the first attempt at using the keyscript I got the same problem with it not finding the keyscript, and not allowing the password to be entered. There is a large difference between when the script works, but no keyfile is found - and this state and no keyfile is found. In the former it patiently waits for the password to be entered, in the latter it simply goes on to a blank screen. Note that this is the same script that works on my other machine with the ...-5 kernel. The script, as well as guide to set it up: http://wejn.org/how-to-make-passwordless-cryptsetup.html At the bottom there is a link to an improved version. I am using that version. http://wejn.org/stuff/hendrik-crypto-usb-key.sh.html -- Changing from kernel 2.6.27-5 to ...-6 and ...-7 breaks boot. LUKS, USB https://bugs.launchpad.net/bugs/281499 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 289918] [NEW] Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
Public bug reported: Details: http://ubuntuforums.org/showthread.php?p=6043289&posted=1#post6043289 Story: I have a Ubuntu 8.04.1 64bit server with FreeNX (used to be Debian Etch 4 with NomachineNX). Then I have two 32bit clients, one with XP and one with Intrepid (used to be Hardy). The Intrepid-client also has FreeNX (server) installed. When it breaks the keymap is messed up to the point of not being usable in the NX-session. Locally run programs are not affected. Regular letters and numbers are not affected, but arrow keys and special keys such as pgup, pgdn, and delete are either not functioning or doing weird things (e.g. arrow up is remapped to screenshot). The following works: WinXP to Debian Nomachine Hardy to Debian Nomachine WinXP to Intrepid FreeNX WinXP to Hardy FreeNX The following is broken: Intrepid to Hardy FreeNX Intrepid to Intrepid FreeNX Changing character-map on the FreeNX host does not help. Keyboard works fine locally, and simultaneously with the NX-session (ie if I have a text editor on top the home key will work in the editor run locally, but nothing run remotely). ** Affects: ubuntu Importance: Undecided Status: New -- Regression: Connecting to FreeNX breaks keyboard layout in Intrepid https://bugs.launchpad.net/bugs/289918 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 255008] Re: Up arrow key mapped to Print [screen]
Judging by the remapping this appears to be the same issue that affects NX-sessions. https://bugs.launchpad.net/ubuntu/+bug/289918 The difference here is that the keyboard works as expected with no ill effects *locally*, but broken when in an NX-session. I cannot find any .Xmodmap-files anywhere in my home directory or lower. -- Up arrow key mapped to Print [screen] https://bugs.launchpad.net/bugs/255008 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 289918] Re: Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
PeteJ said on the forum: After reading tons, having no clue, flailing around, on both client and server I did System, Preferences, Keyboard, Layouts, "Evdev-managed keyboard" or similar, and then in the nx session, on the server, I did System, Preference, Keyboard shortcuts, Desktop, Take a screenshot. It was "Print", I pressed "Ctrl+PrtSc", it changed to "Ctrl+Print", and now ALL the nav keys work fine. This works for me too. -- Regression: Connecting to FreeNX breaks keyboard layout in Intrepid https://bugs.launchpad.net/bugs/289918 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 289918] Re: Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
The important part was setting the keyboard to Evdev-managed keyboard. Whether it is the remote or local or both that does the trick I'm not sure of. Changing the print-screen combination is convenient to allow a print screen to be executed remotely, instead of locally only. -- Regression: Connecting to FreeNX breaks keyboard layout in Intrepid https://bugs.launchpad.net/bugs/289918 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 281499] [NEW] Changing from kernel 2.6.27-5 to ...-6 and ...-7 breaks boot. LUKS, USB
Public bug reported: I used the alternate install CD on a Dell XPS laptop to set up Ubuntu with default settings for a fully encrypted setup. I have since expanded crypttab to read a USB-stick to get a keyfile, or if that fails ask for a password. This worked without a hitch, and continue to do so when I explicitly boot 2.6.27-5 from GRUB. With ...-6 and ...-7 it starts by failing to find the keyfile, and asks for passphrase. There are no indications that it receives any characters (no asterix). Second at random times it comes up with something to the effect of "Bad passphrase or options". I rebuilt initrd in case that was the cause to no avail. I do not believe this is luks-related. The problem is authenticating. Ie. getting input to the system - either USB pendrive, or input from my keyboard which I suspect is USB (laptop, don't know for sure). Original install was Intrepid pre-beta, and I have successfully upgraded kernels since install. ** Affects: ubuntu Importance: Undecided Status: New -- Changing from kernel 2.6.27-5 to ...-6 and ...-7 breaks boot. LUKS, USB https://bugs.launchpad.net/bugs/281499 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 310231] [NEW] Bluetooth: HTC Windows phone - cannot parse
Public bug reported: 8.10, Bluetooth in general appears to work. Pairing and file transfer with a different device works. Pairing with the HTC Windows-phone works one way; When initiating from Ubuntu, Ubuntu considers it a success, but the HTC-phone keeps waiting for some extra piece of information, and fails shortly after. Initiated from HTC there are no issues. Pairing with K750 works flawlessly, initiated from Ubuntu. However every file transfer fails (push from phone), and browsing files on the phone fails with either of the following error messages: Push: (on phone: Failed) Browse: Internal server error OBEX: Unable to parse incoming data The weird pairing behaviour, together with the browsing issues leads me to believe that this is a standards-issue, and that a work-around is required on "our" account. Please inform me on which additional information to post, and I will add it as I can get it (not my phone). ** Affects: ubuntu Importance: Undecided Status: New -- Bluetooth: HTC Windows phone - cannot parse https://bugs.launchpad.net/bugs/310231 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 453337] Re: Karmic: Boot up problem, after usplash logo is a blank screen for about 14 seconds before xsplash appears briefly.
I am starting to suspect that this is the bug I too have been experiencing on a laptop I set up for a friend. Unfortunately I don't think I ever let the computer sit for long enough (10s according to #2 here) before trying something else. I changed from GDM to XDM, and while I still didn't get xsplash (sweeping progression bar), I got to a working login screen at the expected time. Boot from the live-CD worked as intended, with the proper splash screens etc, but of course with no login-screen (since it went directly to a working desktop). I posted my experience here: http://ubuntuforums.org/showthread.php?t=1293255&highlight=thefineprint&page=3 -- Karmic: Boot up problem, after usplash logo is a blank screen for about 14 seconds before xsplash appears briefly. https://bugs.launchpad.net/bugs/453337 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 269851] Re: Bluetooth Logitech Dinovo Edge Keyboard/Mouse does not work anymore
Summary refers to Lucid beta. The problem is also present on Lucid final, as installed from the alternate CD. I only have diNovo-keyboards in my disposal, so even the workarounds are a bit of a hassle since I can't log on without some older live CD. -- Bluetooth Logitech Dinovo Edge Keyboard/Mouse does not work anymore https://bugs.launchpad.net/bugs/269851 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 269851] Re: Bluetooth Logitech Dinovo Edge Keyboard/Mouse does not work anymore
Both a google search and a local search in the bug database reveals that this is a recurring problem, and at least every other Ubuntu release breaks the keyboard support. This is particularly problematic because it's nearly impossible to fix without a second keyboard, and since most live CDs don't support cryptsetup and LVM. I ended up using System Rescue CD to perform the fix mentioned on the blog below. Note that it refers back to a different Launchpad bug. Please include diNovo edge and other affected Logitech peripherals in the compatibility testing, so that we don't need all these unnecessary bug reports. http://awesomelinux.blogspot.com/2010/05/ubuntu-1004-lucid-logitech-dinovo-edge.html http://www.sysresccd.org/Main_Page https://launchpad.net/+search?field.text=dinovo -- Bluetooth Logitech Dinovo Edge Keyboard/Mouse does not work anymore https://bugs.launchpad.net/bugs/269851 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
