Slackware :: USB Keyboard Won't Respond On Luks Login?
May 9, 2011
I just installed slackware 13.37 64 using luks and lvm by following this. However, when its time to enter the password, my usb keyboard won't work. I included the uhci-hcd, and usbhid modules when running mkinitrd,
I was looking into installing Gnome for Slackware 13.1 due to the instability of KDE and I was able to find GSB [URL]. I ran the simple installation: Code: lynx --source [URL] Everything downloaded and installed so I logged off, ran xwmconfig and set it to gnome and then tried starting my xserver and my screen turns black with a single white dash in the corner. My keyboard doesn't respond (the lock lights won't turn on) and I'm stuck on this black page. I tried changing xwmconfig back to KDE and the same thing happens
My computer was working this morning and both hard drives were working fine, then all of a sudden for about two hours I was stuck with this "problem", then after fumbling and moving and stablizing things, then Windows works? See below for details. I've finally reinstalled both hard drives, but the one with the Linux partition doesn't work: it says nothing is discovered on the disk. I can't login at the LUKS login after grub starts, therefore I can't get into Linux, but Windows works?! I used to be able to go directly into Grub when the computer starts, I forgot how to do that but it doesn't matter. If you need details I'd be glad to provide them. I just wondered why Linux doesn't work, but Windows does. I have Linux & Windows on two different separate hard drives
Starting with Slackware 13.1, I am having trouble with keyboard application shortcuts in Xfce. Most of the time, they are not set up at login, for example Alt+F2 for Run prompt, and some custom ones. The fix each time is to kill the xfce4-settings-helper process, which somehow automatically restarts, and the keyboard shortcuts all work after that. But this is annoying.
Has anyone else seen this? I found this bug report which seems to match this problem. But there is no fix, and the bug report goes back to Aug 2009. [url]
I'm pretty sure Slackware 13.0 has the exact same version Xfce-4.6.1 but I never saw this problem under 13.0.
I'm having some weird problems with my mouse and keyboard. I'll be moving the mouse and keyboard about and all of a sudden the keyboard won't respond and the mouse moves and is fully working, but it seems to be a problem with the desktop, more then the mouse, because it'll highlight stuff and certain stuff will open when I click them, but when I go down to the toolbar, and try to click applications, places, and system, it'll highlight it but not respond when I click it. This happens about every 45 Minutes, to 1 hour of time with ubuntu running [10.04] [Additional details]
- I'm using an HP Pavilion Dv6000 Laptop, 64 Bit Ubuntu 10.04 - My drivers are all up to date - Could it be because my Laptop gets really hot? But it dosen't happen ever when I'm running Windows, so I'm not so sure about that.
My Thinkpad R32 keyboard & trackpad will not work when booted off the HD with 9.04, I can plug in an external USB keyboard & that works fine. If I start the laptop from a Ubuntu LiveCd the keyboard & trackpad work fine. There must be some system file disabling the onboard keyboard, I have used Keyboard Preferences to try different keyboard models.
I am running Ubuntu 10.04, randomly while working in gnome with no particular application I get a freeze periodically. Neither the mouse or the keyboard will respond. I am running it on a lenovo Z61m laptop. I have had previous experience with Posix systems but I am a recent migrant from XP as my primary operating system. I never had such an issue with this computer which leads me to believe that it is not a hardware issue.
My desktop sometimes freezes and does not respond to keyboard or mouse. I initially thought the CPU was overheating but it froze tonight when my CPU temperature was 32C and it has been up to 50C without freezing. I am beginning to think it is a software issue rather than a hardware issue but do not know. I looked at the pm-powersave.log and user.log but did not see anything suspicious.
I'm having trouble installing F11 x86_64, and I'm sure it is something to do with the video card.X will not even start if I have both nvidia quadro FX1700's installed. If I take one out, I can install F11, but it always 'hangs' when it starts X (which is to say, both the keyboard and mouse are locked - until I press the power button, but then it shuts down anyway).I've fiddled inittab so it starts in runlevel 3 so I can at least get in and tinker. There is no xorg.conf in /etc/X11, so I assume the system is building it's own and not quite getting it right (guess work based on other threads with similar symptoms).
I can connect to the system from another Linux machine via ssh, and I can ftp to it. I tried copying the xorg.conf from the other machine, but while it changed the screen resolution (ergo, it had some effect), it still went nuts. Starting X remotely via ssh allowed me to trap the messages, which indicate the lack of HAL has something to do with the problem.service --status-all reports hald stopped; I'm assuming this should not be the case. I've used yum to reinstall hal, but that made no difference. Nor did an update - it was already at the most recent level.F11 was installed from a DVD downloaded vai a bittorrent; the disk checked out ok.
My knowledge is limited, and I don't know what should be in xorg.conf for my machine, although I could type it in from scratch or ftp it across from here. It was 'okay' under F10, happily tolerating both video cards. But it seems to be sulking under F11. In case it matters, I'm doing everything as root; since firstboot starts X, I can't use that to create another userid.
- nomodeset, xdriver=vesa, selinux=0, remove rhgb as boot parameters - all to no avail (although these changes seem to be ignored for the most part anyway);
- start the HAL daemon manually (mine failed to start, as others have reported). It didn't like that! (the output is available, but is enormous)
- startx -configure - simply failed;
- dirconf didn't work;
- I've tried swearing at it during start-up, which turned out to be no more or less successful than anything else, but it was fun.
Intel Q6600 64 bit. Twin nvidia Quadro FX1700 cards (one removed for the time being) driving two 1920x1200 monitors each. Please let me know if there is any other relevant information I can supply.
Have just upgraded (14-->15) using the dvd option; installed the nvidia driver (I think) and am able to startx and get to the Gnome 3 desktop (Wallpaper and top "task" bar look correct)..But, the mouse and keyboard have absolutely no affect. No matter what I click on, or what keyboard combination I use, nothing happens..(Have spent the last 3 hours researching it; and just seem to be getting nowhere.. I can do anything I need to from the CLI; but am not sure what to do..
Yesterday something has happened with power supply, so 2 of 3 PCs has shut down. And now my debian pc doesn't respond to multimedia (volume to be precise) keys, leds also doesn't work. Other keys are fine. Tried xev, but it doesn't respond to multimedia keys either. I have dual boot with Win7 on this machine, and it works fine with multimedia keys.
I believe this is a clue:
Code: Select all[ 22.324109] generic-usb: probe of 0003:04D9:1702.0004 failed with error -110
I recently installed OpenSUSE 11.4 64 bit with GNOME yesterday and everything is going fantastic. I like it much better than Ubuntu 10.10 64 bit Maverick Meerkat because it is much more stable, reliable, and dependable. I own a heavily modified ASUS N61JV-X2 notebook PC. I installed OpenSUSE using the LVM based method and LUKS encryption. When I turn on the power to my notebook PC, it asks me for my password to decrypt my Intel 2nd Generation 160.00 GB Solid State Drive. I expected this behavior. However, I never get to see the OpenSUSE login screen. After I type in my password to decrypt my SSD, it loads up the desktop immediately. How do I configure my OpenSUSE so that I can see the login screen so that I can select my standard user profile and enter the user password to login?
I have been following Alien Bob's README_CRYPT.TXT on the install disk and playing around with LUKS and LVM as highlighted in the section Combining LUKS and LVM. I got this working following the examples in the readme however I now wish to add another volume to the volume group. I have got this working and extended the group with an encrypted volume so it's now bigger. I want the two included physical volumes in the volume group (which are both encrypted) to be opened on bootup.
As it is now I am prompted for a password for the first physical volume (the passwords are set to be the same) and that opens and boots the volume. It has a problem with the second PV I have added and doesn't open this. There are errors on boot up about this and pvdisplay give this:
Code: Couldn't find device with uuid 'JVirxL-lmqH-SUym-3lXG-MnXx-Qjk8-JZRha8'. Couldn't find device with uuid 'JVirxL-lmqH-SUym-3lXG-MnXx-Qjk8-JZRha8'. Couldn't find device with uuid 'JVirxL-lmqH-SUym-3lXG-MnXx-Qjk8-JZRha8'. --- Physical volume --- PV Name /dev/block/253:0
I've just did a fresh Slackware 13.1 install on a 32-bit box for friends of mine. It's an older machine with an AMD Athlon XP 2500. Generally everything works just fine, with one exception, however.Connecting a LUKS encrypted USB harddisk is notified by KDE. Clicking on the device icon in Dolphin opens the dialog asking for the LUKS passphrase. No error message appears, but the file system is not opened and mounted, anyway.However, before another attempt I have to "remove" the device in Dolphin.Output of dmesg:
Code: # Nov 25 23:58:24 mycomputer kernel: device-mapper: ioctl: unable to remove open device temporary-cryptsetup-3023
Basic Problem: I have been trying to install 13.1 (64-bit) and have not been able to get lilo to install.
Procedure:
1) partitioned drive /dev/sdc 1GB (Linux RAID) and 499GB (Linux Raid) 2) copied partitioning scheme to /dev/sdd 3) set up RAID-1 arrays md0 (sdc1-sdd1) and md1 (sdc2-sdd2) 4) write random data to partitions 5) set up LUKS on md1 (swluks) 6) set up LVM on swluks (80GB /, 375GB /home, 20GB swap) 7) ran setup, chose partitions, installed software 8) setup lilo (mbr, selected /) 9) TRIED to install lilo
I am trying to get Slackware 12.2 running on a system with two identical harddiscs using RAID-1, LVM and LUKS.
Here is what I get:
Code:
The system is still the same, however, the results of upgrading or installing 12.2 are different. The system refuses to boot. The screen messages during boot seem to suggest, that the RAID system is "seen" by the system, but the encrypted filesystem is not.
I can boot with the installation DVD, however, and
Slackware 13 Kernel 2.6.29.6 have three hard drives. Root is on own drive sda1. sdb and sdc are raid via mdadm with two partitions. one for /home raid0 md0 one for swap raid1 md1. md0 is encrypted vi cryptsetup. md1 is encrypted vi fstab. everything boots fine and is accessible. However, /dev/mapper/* shows sda1 as block device connected to the raid md0. swap crypted device is correct in /dev/mapper/*. fstab is set correctly. problem seems to be with initrd. I would like the correct device in /dev/mapper so that I can access drive info; size, available space, etc. now info shows only sda1 info
So I was wondering about the dilemma of how to encrypt the password file on a key card to unlock your harddrive without having to enter any password. I came to the conclusion that that the scripts could do this without storing any passwords in plane text them self. Have a few extra steps to the scripts that would:
1. Read the UUID of any disks coming in.
2. Attempt to use that ID to decrypt a password file stored in the initrd.
3. Use the decrypted password file to unlock the the keycard partition.
4. THEN use the password files on the keycard to decrypt the main partition and boot the system.
However, if somebody stole your key card and didn't know what the unencrypted information was, then it's harmless for them to have it anyway. And if they did know, you wouldn't be any better off with it being encrypted because they probably can gain access to your computer anyway; leaving them to just pop the key card in and automatically decrypt the drive.
I suppose encrypting the keycard would give you extra assurance that the information would be much harder to recover if you destroyed the key card in a hurry. So would this extra security step even be worth it?
I guess the most secure thing would be to only have a password and type it in every time... unless you are concerned about the aliens/government stealing that from your brain which would probably mean they wouldn't need your password anyway.
I have a luks-encrypted external drive with lvm on top. When I plug it in xfce prompts me (twice as usual) for the encryption phrase. Then, unlike when I have a regular file system on top and it automounts, I need to activate the volumes and manually mount. Is there a way to make these steps happen automatically?
Anyone else experiencing the random LUKS fails? Anyone know of a solution?I filed a bugBasically I have a USB hard drive with two LUKS partitions on it (sdb2, sdb3). When plugged in, it asks for the password in Xfce (like it did in Slackware 13.0), but instead of the previous "asks twice for password" bug, now it asks once, but nothing pops up on the desktop. It's rare to see either of them put an icon on the desktop (usually nothing results).
I see /dev/mapper/luks_crypto_{UUID} get populated, so they are successfully being unlocked (LUKS), but no icon appears, and no mount point for the volume label (i.e. /media/BACKUP /media/ASUS) is populated.Does anyone know how I could produce a more useful bug report? I'm wondering if "strace startxfce" would produce anything useful or if I should alias Thunar to "strace -o /tmp/thunar-`date`.txt" would be in order.
How can I get a LUKS encrypted partition on an external USB device automounted with r/w access for non-privileged users?
Background: I just reformatted an external USB device with ext4. The only partition is LUKS encrypted. Now, when I plug the device to my computer, KDE notifies me and asks me to enter the LUKS passphrase. Then it mounts the device. Little snag here: Non-privileged users have read-only access.
My user is a member of group plugdev, but not of group disk, as this was discouraged several times, e. g. by Robby Workman. With non-encrypted disks regular users have read/write access, or can change the filemodes accordingly, as far as I recall (currently I have no more non-encrypted disks left to verify it...)
Quote: The precompiled Slackware kernels are available in the /kernels directory on the Slackware CD-ROM or on the FTP site in the main Slackware directory. I am unable to reach it, what's the proper login?
This just started happening last night and it's annoying as hell. I log in fine, and bam, no keyboard. I have to go to System> preferences> input method switched, switch it to sysadmin default> lock screen> switch user> log back in> Then it works. How can I have my keyboard back? I read on a similar old thread to copy .config and copy it to a different user then delete it from home directory. Will all of my preferences go away if I delete it?
I recently upgraded to Ubuntu 11.04. Login worked fine at first. After a recent update, I can no longer login. The Keyboard is inactive on the home screen. Mouse is active and I can enter through other non-admin accounts with no password required for their login.Keyboard works fine once I can get past the login. Doesn't work on normal, classic or safe mode. Keyboard driver (system-wide)set to Dell Inspiron 6xxx/8xxx.
I have an AMD 64 Dual Core 4200 w/2 Gigs RAM. On Jaunty, after adding some software through Synaptic (don't remember which software), I lost the use of both my mouse and keyboard at the Login screen. I can't even click on what I want to use (Gnome, KDE, etc.) I had to install the i386 version of Jaunty in Windows just to get into my Linux files. I tried going into the Initialize commands file (advice from Ubuntu forums) and add them, but still no keyboard or mouse.
i have a brand new CentOS 5.2 installation and cannot login because it does not react to any keyboard inputs.By the way ... the cursor is still blinking - so the machine is running.
As the title says i have this error on both my main computer and my laptop. For my main computer see this post, that is when it happened. viewtopic.php?f=30&t=65743
I run the updates on my laptop a while ago and decided to restart it to check if everything went okay. It seems not.
The only way i can get on the desktop, is to choose the recovery mode, su to user and startx.
This is a common error during booting on both computers. Starting the hotplug events dispatcher: udevderror binding control socket, seems udevd is already running
It seems a little strange, same error on both computers.