Hello,
Just installed f12 beta on my infamous HP dv9237eu laptop. I read that suspend will now work even when you have nvidia graphics adapter. I try suspend to disk on kde, screen goes black but the cpu fan keeps rolling. System seems frozen so I have to use power button to shutdown.
Now when I boot I see:
*** An error occured during the file system check. *** ... *** ... *** ... Give root password for maintenance (or type Control-D to continue):
Indent looks weird but who cares. Now if I press ANY key I get: Login incorrect. Give root password for maintenance (or type Control-D to continue):
Control-D does not work and I can't type root password. How can I boot normally?
Riku
On Wed, Oct 21, 2009 at 5:47 PM, Riku Seppälä riku.seppala@kymp.net wrote:
Hello,
Just installed f12 beta on my infamous HP dv9237eu laptop. I read that suspend will now work even when you have nvidia graphics adapter. I try suspend to disk on kde, screen goes black but the cpu fan keeps rolling. System seems frozen so I have to use power button to shutdown.
Now when I boot I see:
*** An error occured during the file system check. *** ... *** ... *** ... Give root password for maintenance (or type Control-D to continue):
Indent looks weird but who cares. Now if I press ANY key I get: Login incorrect. Give root password for maintenance (or type Control-D to continue):
Control-D does not work and I can't type root password. How can I boot normally?
Riku
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
https://bugzilla.redhat.com/show_bug.cgi?id=529285
This should be fixed after updating (but I'm not sure how will you update if you can't even boot...).
2009/10/21 Vedran Miletić rivanvx@gmail.com
On Wed, Oct 21, 2009 at 5:47 PM, Riku Seppälä riku.seppala@kymp.net wrote:
Hello,
Just installed f12 beta on my infamous HP dv9237eu laptop. I read that suspend will now work even when you have nvidia graphics adapter. I try suspend to disk on kde, screen goes black but the cpu fan keeps rolling. System seems frozen so I have to use power button to shutdown.
Now when I boot I see:
*** An error occured during the file system check. *** ... *** ... *** ... Give root password for maintenance (or type Control-D to continue):
Indent looks weird but who cares. Now if I press ANY key I get: Login incorrect. Give root password for maintenance (or type Control-D to continue):
Control-D does not work and I can't type root password. How can I boot normally?
one option would be to boot live cd and fsck from there.
On 10/21/2009 06:49 PM, Vedran Miletić wrote:
On Wed, Oct 21, 2009 at 5:47 PM, Riku Seppäläriku.seppala@kymp.net wrote:
Hello,
Just installed f12 beta on my infamous HP dv9237eu laptop. I read that suspend will now work even when you have nvidia graphics adapter. I try suspend to disk on kde, screen goes black but the cpu fan keeps rolling. System seems frozen so I have to use power button to shutdown.
Now when I boot I see:
*** An error occured during the file system check. *** ... *** ... *** ... Give root password for maintenance (or type Control-D to continue):
Indent looks weird but who cares. Now if I press ANY key I get: Login incorrect. Give root password for maintenance (or type Control-D to continue):
Control-D does not work and I can't type root password. How can I boot normally?
Riku
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
https://bugzilla.redhat.com/show_bug.cgi?id=529285
This should be fixed after updating (but I'm not sure how will you update if you can't even boot...).
Thanks. My first install was just hour ago so I guess I just do new install.
*** An error occured during the file system check. *** ... *** ... *** ... Give root password for maintenance (or type Control-D to continue):
Indent looks weird but who cares. Now if I press ANY key I get: Login incorrect. Give root password for maintenance (or type Control-D to continue):
Control-D does not work and I can't type root password. How can I boot normally?
This happened to me.
From digging down, it looks like on shutdown something in f12 beta sets
the last mounted time +6 hrs into the future on the root or boot partition. When you re-boot, you get the weird behavior because the root partition cannot be mounted because the last modified time is in the future.
You can work around this by
1) waiting 6 hrs and then booting 2) setting the clock ahead in the BIOS and re-booting
-benjamin
2009/10/21 Benjamin Kosnik
From digging down, it looks like on shutdown something in f12 beta sets the last mounted time +6 hrs into the future on the root or boot partition. When you re-boot, you get the weird behavior because the root partition cannot be mounted because the last modified time is in the future.
You can work around this by
- waiting 6 hrs and then booting
- setting the clock ahead in the BIOS and re-booting
-benjamin
On Wed, 2009-10-21 at 18:47 +0300, Riku Seppälä wrote:
Hello,
Just installed f12 beta on my infamous HP dv9237eu laptop. I read that suspend will now work even when you have nvidia graphics adapter.
well, it's more that the nouveau driver in general now implements suspend/resume support, whereas it didn't before. suspend/resume being how it is, there'll still be some systems where it doesn't work because of specific bugs, whether these are in the nouveau driver or not. :/
try reinstalling (as you thought), doing rawhide updates, then try the suspend again. if it still doesn't work, it's bug filin' time :)
� wrote:
Hello,
Just installed f12 beta on my infamous HP dv9237eu laptop. I read that suspend will now work even when you have nvidia graphics adapter. I try suspend to disk on kde, screen goes black but the cpu fan keeps rolling. System seems frozen so I have to use power button to shutdown.
Now when I boot I see:
*** An error occured during the file system check. *** ... *** ... *** ... Give root password for maintenance (or type Control-D to continue):
Indent looks weird but who cares. Now if I press ANY key I get: Login incorrect. Give root password for maintenance (or type Control-D to continue):
Control-D does not work and I can't type root password. How can I boot normally?
Oh, over-zealous security nazis.[1] Easily defeated. Boot with the option init=/bin/bash
It gets you a shell (bash) and, with any luck, initrd has found your disks so you can run fsck on everything.
1 So described because, alone, the effort is so futile. Give me physical access, I own the system. Unless you use encryption.
On 10/22/2009 07:19 AM, John Summerfield wrote:
Oh, over-zealous security nazis.[1] Easily defeated. Boot with the option init=/bin/bash
It gets you a shell (bash) and, with any luck, initrd has found your disks so you can run fsck on everything.
1 So described because, alone, the effort is so futile. Give me physical access, I own the system. Unless you use encryption.
Encryption is not as full proof as you imagine.
http://www.bress.net/blog/archives/162-Security-is-a-multilayered-problem.ht...
Rahul
2009/10/22 Rahul Sundaram
Encryption is not as full proof as you imagine.
http://www.bress.net/blog/archives/162-Security-is-a-multilayered-problem.ht...
Rahul
foolproof?
Rahul Sundaram wrote:
On 10/22/2009 07:19 AM, John Summerfield wrote:
Oh, over-zealous security nazis.[1] Easily defeated. Boot with the option init=/bin/bash
It gets you a shell (bash) and, with any luck, initrd has found your disks so you can run fsck on everything.
1 So described because, alone, the effort is so futile. Give me physical access, I own the system. Unless you use encryption.
Encryption is not as full proof as you imagine.
http://www.bress.net/blog/archives/162-Security-is-a-multilayered-problem.ht...
Sounds like stoned...
Even so, it's quite a bit more difficult.
Use BIOS passwords, grub passwords and all anyone needs to do is pop the disk into another computer,that's why I said "physical access."
I suppose that if I created a live Fedora disk with some attractive features, there's a good chance some here would be foolish enough to download it and run it, but I had in mind any computer, not just those with gullible owners.
On Thu, 2009-10-22 at 16:14 +0530, Rahul Sundaram wrote:
On 10/22/2009 07:19 AM, John Summerfield wrote:
Oh, over-zealous security nazis.[1] Easily defeated. Boot with the option init=/bin/bash
It gets you a shell (bash) and, with any luck, initrd has found your disks so you can run fsck on everything.
1 So described because, alone, the effort is so futile. Give me physical access, I own the system. Unless you use encryption.
Encryption is not as full proof as you imagine.
http://www.bress.net/blog/archives/162-Security-is-a-multilayered-problem.ht...
The title of that post also handily illustrates why it makes sense for Fedora to implement the layers of security it can, even when they don't make anything any more secure *on their own*. For sysadmins who take the time to lock everything else down properly themselves, the recovery console could indeed be a vulnerable path if we didn't lock it down in Fedora.