Unable to boot Trisquel 6.0 from GRUB
- Anmelden oder Registrieren um Kommentare zu schreiben
Hello guys, just installes the last Trisquel 6.0 in my computer. and, when I was at the grub, where I had to select what OS to enter to, I found that it was impossible to run it, because the boot commands were not on "nomodeset". So, I go to edit boot commands when, surprise! it tells me to put an username and a password.
After trying my Trisquel account for a hunderd times, searching some changes shortcuts on my keyboard an so on, I found that it does not work. I enter my account, and it goes back to the select OS screen, nothing more happens, and of course it does not let me edit the commands.
What should I do?
The lead developer thinks setting a GRUB password (randomly generated during the install) improves the security even if the bad guy has a physical access to the computer. Well, it does not: boot any live system (such as the one you used to install Trsquel), mount the root partition of your Trisquel install and read /etc/grub.d/01_PASSWORD ('sudo cat /etc/grub.d/01_PASSWORD') to know the password. If you want to remove it, you can too ('gksu gedit /etc/grub.d/01_PASSWORD' and comment/remove the two lines in it).
For more information about this choice of a GRUB password you can read this thread.
I am a member!
So, when I start a new system, installed from the final release of
Trisquel 6, I'll have to enter a randomly-generated password? I realize
that I can us the live cd, mount my root file system, and comment out
the lines in '/etc/grub.d/0_password', but, how would one get this
password if she didn't know about this trick? A post above, in this
thread, suggests that getting this password isn't an easy thing.
Incidentally, I had a look at /etc/grub.d/0_password and found that it
contains a couple of comments and a couple of 'echo' lines, one having a
5-digit password on it. My grub isn't password-locked at present.
Thanks for making us aware of this coming issue.
Cheers,
Dave H.
I believe that the developer, BY PROGRAMMING this feature. is a TOTAL CONTROL FREAK! He is using the excuse of "Security" to excuse himself.
For me, someone telling me, that I will need a password to boot from grub, I should have the option to decide, not the developer!
As a user, I should be the one able to decide the level of security.
The developer might as well start selling Trisquel and make it proprietary from know on.
This is Bull Cr@p, Less kudos and less hope towards Trisquel.
I would hardly call a single bad design decision a deal-breaker or the death of Trisquel (or something similar).
There's always Ubuntu with 12.04.2 released today: http://www.ubuntu.com/download
We don't suggest proprietary software here.
Big deal.
Every feature and every default setting in any software was decided by someone else, not you. Most programs allow you to configure them, and all free software allow you to change it. Then you can share you versions, if you think you can and are willing to do better.
Calm down. The password is required to *edit* GRUB's configuration from GRUB itself. Not to boot a kernel. Notice that editing GRUB's configuration is the easiest way to get root's privileges: just add the keyword "single" to the boot line. However, and as I wrote, GRUB's password is not much of a security. You only need a live system to read or remove this password. GNU GRUB's documentation agrees:
By default, the boot loader interface is accessible to anyone with physical access to the console: anyone can select and edit any menu entry, and anyone can get direct access to a GRUB shell prompt. For most systems, this is reasonable since anyone with direct physical access has a variety of other ways to gain full access, and requiring authentication at the boot loader level would only serve to make it difficult to recover broken systems.
Again, I invite anybody who wants to get both side of the discussions to read this thread.
I already solved it! Thanks!
If anyone want to know what I did, I puted back the live-cd of Trisquel, downloaded "grub customizer" and customizate the boot commands from there.
I am a member!
Thank you for sharing; that's great! However, this should never be
necessary!
On 02/14/2013 03:28 PM, name at domain wrote:
> I already solved it! Thanks!
>
> If anyone want to know what I did, I puted back the live-cd of Trisquel,
> downloaded "grub customizer" and customizate the boot commands from there.
Heh; all of this about some "password" you don't know being needed to add nomodeset. I added nomodeset to mine with Trisquel 6 and never needed a password other than my own.
For the recod it's easy to add nomodeset and no mystery password is needed.
Step 1: Edit /etc/default/grub and add nomodeset to the line containing GRUB_CMDLINE_LINUX_DEFAULT
You will probably need sudo for this and will be asked for a password but it's your own password.
Once that's done run sudo update-grub and TA DA!
Anyway, just to set the record straight that there's no mystery password required to add nomodeset to your GRUB configuration.
- Anmelden oder Registrieren um Kommentare zu schreiben