Sven Joachim <svenj...@gmx.de> writes:

[...]

Harry wrote:
>> It fixes my goofy screen problem but it does cause bootup to go into
>> maintenance mode.  Telling me to enter root passwd or press C-d.
>>
>> I press C-d and it finishes booting up normally.

Sven Replied:
> This is rather odd and indicates that you are booting in single user
> mode, perhaps by passing "init 1" or "single" as boot parameters.  The
> answer should be found in /proc/cmdline.

cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.0.0-1-686-pae 
root=UUID=83a94f1d-e6e6-432e-86ad-b24754755fff ro single

Haaa you nailed that, but how does it get there... where is single
being set?

It happened the moment I added this to the kernel line in
/boot/grub/grub.cfg, `nouveau.noaccel=1', like so:

linux /vmlinuz-3.0.0-1-686-pae root=UUID=83a94f1d-e6e6-432e-86ad-b24754755fff 
ro  quiet splash nouveau.noaccel=1

Harry wrote:
>> So it means I cannot have an unattended bootup, but that is usually
>> what I do anyway so not a huge problem, but wondered if there might be
>> some other way to disable acceleration that on the kernel line?

Sven replied:
> I'm not aware of any, but disabling graphics acceleration is orthogonal
> to booting in single user mode.

It appeared, at this end, to start the moment I added the nouveau
snippet to linux line in /boot/grub/grub.cfg

For a moment, I thought perhaps the `=1' is somehow being interpreted
as an instruction to boot single mode.

But, just now, removing that nouveau part from linux line in
/boot/grub/grub.cfg, reboot, and still the bootup goes to single or
maintenance mode. ... although clicking C-d to skip it appears to boot
with no problems.

That last would seem to indicate there is no actual problem bringing
on single mode.

How does /proc/cmdline get set? It is apparently something one is not
supposed to edit.

But that `single' bit has remained, since I removed nouveau.noaccel=1
from /boot/grub/grub.cfg

cat /proc/cmdline

BOOT_IMAGE=/vmlinuz-3.0.0-1-686-pae 
root=UUID=83a94f1d-e6e6-432e-86ad-b24754755fff ro single

Where is it coming from?

I'm not purposely passing anything at bootup and have removed my edits
to /boot/grub/grub.cfg.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87sivhfj9o....@newsguy.com

Reply via email to