UbuntuThis forum is for the discussion of Ubuntu Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
A few months back, I decided to might play with using LUKS for whole disk encryption. Everything was working fine until tonight when I turned on my computer to do some work, and after entering my password, I got an error saying that it had failed. Nonplussed, I tried again... it failed again. Fat-fingered it twice in a row? How odd.
Three failures?! Maybe I am not typing it right? Maybe I'm not remembering it right? Holy smokes, did something go hokey with the disk or some software update to hose the encryption somehow?
Well, after freaking out a little bit, I remembered that I had been playing with writing some software to interface with a credit card reader. The credit card reader is a usb thing that by default shows up as a HID... and it was still plugged in... Could that be interfering somehow?
Well to end a long story, the answer is yes... once I disconnected the card reader, I could enter my password and boot up the computer...
Thought I'd throw out a message about it since my panic-laden google searches didn't come up with that being a possibility (not that _that_ many people will have the problem, but...)
I had the same situation a while ago with a new keyboard. Some odd reason, booting up after plugging in a new keyboard resulted in a password failure.
So in the end i booted up with the old keyboard plugged in, and all worked fine. Only until plugging in the new keyboard and rebooting with it still plugged in... seemed to allow me to unlock the disk at boot time.
Strange either way...
Maybe a new piece of hardware is being detected as a key device for pam authentication, but not being able to read the keyfile? I have no idea tbh.