(
Jump to the original submission)
Sun 14 Jul 2013 01:23:59 PM UTC, comment #11:
Parkes' kernel no longer needs 'console=tty' or 'no_aut_cmd'.
|
Sun 14 Mar 2010 11:30:31 AM UTC, comment #10:
quick update: the grub building issue is in another bug report (about using grub from sid/testing).
there has been some progress on that bug.
|
Wed 10 Feb 2010 01:31:00 AM UTC, comment #9:
I can't get our grub to rebuild either. it sits running mawk indefinitely. :(
Can someone else have a look at this?
|
Tue 09 Feb 2010 10:59:22 PM UTC, comment #8:
FTR, I've been unable to make grub from sid build on metad, so we won't be able to switch to it yet.
|
Tue 02 Feb 2010 12:48:22 PM UTC, comment #7:
good to know. I'll try it tomorrow evening (or the day after). would it be worth me filing a bug in debian asking for the build dep to be gcc (>= 4.3) rather then 4.4?
|
Tue 02 Feb 2010 12:18:36 PM UTC, comment #6:
gcc-4.3 should work, it's what I used for the previous builds.
|
Sat 30 Jan 2010 05:31:05 AM UTC, comment #5:
Robert:
grub2 in sid requires gcc-4.4 to build, which is unavailable in gns and lenny-backports.
whats the likelihood we could backport gcc, or should we try to rebuild grub2 with gcc-4.3?
http://packages.debian.org/sid/grub2
I dropped the severity of this bug until we've worked out what happens here.
If we stick with our current grub2 snapshot, I'll bump the version on my patch (previously attached) and upload that as -3. it does mean we lose the cherrypick from your -2 upload, since it isn't mentioned in bzr (at least not in debian/changelog).
|
Fri 29 Jan 2010 04:21:29 AM UTC, comment #4:
In progress, until we've had a chance to work out whats happening to our grub-yeeloong packages.
|
Fri 29 Jan 2010 03:57:40 AM UTC, comment #3:
I'm working on a package, it'll be ready tonight.
|
Thu 28 Jan 2010 10:27:23 PM UTC, comment #2:
Nope, needs to be fixed in the grub-yeeloong package.
|
Thu 28 Jan 2010 12:04:56 AM UTC, comment #1:
There have been two new uploads to yeeloong-base package (not sure about grub) - has this bug been fixed by either of them?
kk
|
Tue 05 Jan 2010 06:16:38 PM UTC, original submission:
Linux on the Yeeloong needs the parameters "no_auto_cmd console=tty" to be able to boot. Grub-yeeloong should set those parameters when it's installed, but doesn't.
GRUB gets the default boot parameters from the file /etc/default/grub. When grub-yeeloong is installed this file is constructed from a default template and user input. The package's configuration (debian/config) prompts the user for input and suggests the values it finds in /etc/default/grub. The first time the package is installed that file doesn't exist yet, so the configuration gets its suggested values from a debhelper template file (debian/templates). The template only suggests "quiet" as a boot parameter. The unknowing user just accepts the suggested values and will be unable to boot his machine with GRUB.
It looks to me like the solution would be to add a
Default: no_auto_cmd console=tty
line to the grub2/linux_cmdline block in the templates file.
|
Depends on the following items: None found
Items that depend on this one: None found
Follow 11 latest changes.