Re: [Gnewsense-dev] grub-yeeloong
On Fri, 18 Dec 2009, Karl Goetz wrote: On Tue, 15 Dec 2009 Lars Nooden wrote: ... Both al and boot.cfg seem to ignore whatever grub set during its installation process. If you fix al it'll boot fine. it'll still complain about no boot.cfg, but such is life. Perhaps when grub is set by default we should ask lemote to remove that warning? Can you describe or point to a description of what that fix entails so that grub is used instead of /boot/boot.cfg? /Lars ___ gNewSense-dev mailing list gNewSense-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/gnewsense-dev
Re: [Gnewsense-dev] grub-yeeloong
Sam Geeraerts schreef: Robert Millan schreef: On Sun, Dec 13, 2009 at 07:12:51PM +0100, Sam Geeraerts wrote: A was a bit quick to send this email. My grub configuration is also broken now it seems. When I try to boot I get Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Are you passing the right params to Linux? Check GRUB_CMDLINE_LINUX in /etc/default/grub. I did a fresh install today. The grub.cfg the installer generates works fine: the background now fills the whole screen and the system boots. If I then generate it with `grub-mkconfig /boot/grub/grub.cfg' and reboot, the system no longer boots: it stops with the kernel panic I mentioned before. So I compared both grub.cfg files and found a difference in the linux boot parameters: original: linux /boot/... root=/dev/hda3 ro quiet grub-mkconfig: linux /boot/... root=UUID=7f94 ro quiet I checked the uuid with blkid and it matches /dev/hda3. Kernel = 2.6.31.6-libre1. I tested again, with 2 kernel versions: 2.6.32.1-libre-lemote panics with both root=/dev/... and root=UUID=... 2.6.31.6-libre1 panics with root=UUID=..., but boots with root=/dev/... I currently have grub 1.98~20091212-2. My grub.cfg is at http://gnewsense.pastebin.com/m3dee1614 ___ gNewSense-dev mailing list gNewSense-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/gnewsense-dev
Re: [Gnewsense-dev] grub-yeeloong
Robert Millan schreef: On Sun, Dec 13, 2009 at 07:12:51PM +0100, Sam Geeraerts wrote: A was a bit quick to send this email. My grub configuration is also broken now it seems. When I try to boot I get Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Are you passing the right params to Linux? Check GRUB_CMDLINE_LINUX in /etc/default/grub. I did a fresh install today. The grub.cfg the installer generates works fine: the background now fills the whole screen and the system boots. If I then generate it with `grub-mkconfig /boot/grub/grub.cfg' and reboot, the system no longer boots: it stops with the kernel panic I mentioned before. So I compared both grub.cfg files and found a difference in the linux boot parameters: original: linux /boot/... root=/dev/hda3 ro quiet grub-mkconfig: linux /boot/... root=UUID=7f94 ro quiet I checked the uuid with blkid and it matches /dev/hda3. Kernel = 2.6.31.6-libre1. ___ gNewSense-dev mailing list gNewSense-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/gnewsense-dev
Re: [Gnewsense-dev] grub-yeeloong
Robert Millan schreef:
On Sun, Dec 13, 2009 at 07:12:51PM +0100, Sam Geeraerts wrote:
A was a bit quick to send this email. My grub configuration is also
broken now it seems. When I try to boot I get Kernel panic - not
syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Are you passing the right params to Linux? Check
GRUB_CMDLINE_LINUX in /etc/default/grub.
menu ... {
insmod ext2
set root=(ata0,3)
search --no-floppy --fs-uuid --set uuid
linux /boot/vmlinux... root=uuid ro quiet
initrd /boot/initrd.img...
}
This menu entry looks OK to me. It's similar to the one I see on metad
i386, except that one has set root=(hd0,3) and linux ...
root=/dev/hda3. The uuid matches with what I find in the output of
blkid. /etc/default/grub has 'GRUB_CMDLINE_LINUX='.
___
gNewSense-dev mailing list
gNewSense-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/gnewsense-dev
Re: [Gnewsense-dev] grub-yeeloong
Karl Goetz wrote: Can you give more details on what you mean here? They do boot perfectly without boot.cfg, if the correct settings are made in pmon. (Mine still boots this way). The exact PMON error message: booting: The boot.cfg not existed!System will try default entry from al. I've avoided changing al settings by using boot.cfg to specify boot options. Both al and boot.cfg seem to ignore whatever grub set during its installation process. /Lars ___ gNewSense-dev mailing list gNewSense-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/gnewsense-dev
Re: [Gnewsense-dev] grub-yeeloong
Hi Karl, Le mardi 15 décembre 2009 à 14:01 +1030, Karl Goetz a écrit : Can you give more details on what you mean here? They do boot perfectly without boot.cfg, if the correct settings are made in pmon. (Mine still boots this way). kk Do you mean one should modify a specific setting in pmon? Then, I assume that the parameter that should be modified is al, which initial value is /dev/fs/e...@wd0/boot/vmlinux. Is it correct to set this parameter to /dev/fs/e...@wd0/boot/grub.elf? BTW, what are the preliminary operations? I have installed grub-yeeloong and yeeloong-base, then I executed: grub-image -0 elf -o grub.elf -f font.bin sm712 gfxterm sh normal at_keyboard ata linux part_msdos ext2 with the following error: grub-mkimage: error: cannot stat font.bin then grub-install /dev/hda It created a grub.elf file. Is the grub porting at an too early stage to update the http://wiki.gnewsense.org/Projects/GNewSenseToMIPS page with the detailed procedure? Thank you for your help Samy ___ gNewSense-dev mailing list gNewSense-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/gnewsense-dev
Re: [Gnewsense-dev] grub-yeeloong
On Sun, Dec 13, 2009 at 04:37:37PM +0100, Sam Geeraerts wrote: I've just finished a new install myself. After a load /dev/fs/e...@wd0c/boot/grub.elf I'm getting the grub menu, but just with plain looks instead of the gNewSense theme. Maybe that's because I only did a standard system install instead of the full desktop install. Install desktop-base package. -- Robert Millan ___ gNewSense-dev mailing list gNewSense-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/gnewsense-dev
Re: [Gnewsense-dev] grub-yeeloong
Robert Millan schreef: On Sun, Dec 13, 2009 at 04:37:37PM +0100, Sam Geeraerts wrote: I've just finished a new install myself. After a load /dev/fs/e...@wd0c/boot/grub.elf I'm getting the grub menu, but just with plain looks instead of the gNewSense theme. Maybe that's because I only did a standard system install instead of the full desktop install. Install desktop-base package. That's better, but the background image is only 640x480, sitting in the upper left corner. ___ gNewSense-dev mailing list gNewSense-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/gnewsense-dev
Re: [Gnewsense-dev] grub-yeeloong
On Sun, Dec 13, 2009 at 07:04:48PM +0100, Sam Geeraerts wrote: Robert Millan schreef: On Sun, Dec 13, 2009 at 04:37:37PM +0100, Sam Geeraerts wrote: I've just finished a new install myself. After a load /dev/fs/e...@wd0c/boot/grub.elf I'm getting the grub menu, but just with plain looks instead of the gNewSense theme. Maybe that's because I only did a standard system install instead of the full desktop install. Install desktop-base package. That's better, but the background image is only 640x480, sitting in the upper left corner. Known problem, will be fixed soon with a branch merge. -- Robert Millan ___ gNewSense-dev mailing list gNewSense-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/gnewsense-dev
Re: [Gnewsense-dev] grub-yeeloong
On Wed, Dec 09, 2009 at 11:31:58PM +0100, Robert Millan wrote: Hi, A new grub-yeeloong package has been pushed and will be available with next archive rebuild. Please try it out if you can. Pushed new version. This one provides grub-install script, which should make the install process simpler: sudo grub-install /dev/hda then simply instruct PMON to load /boot/grub.elf. -- Robert Millan The DRM opt-in fallacy: Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all. ___ gNewSense-dev mailing list gNewSense-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/gnewsense-dev
