On 07.02.10 Choe, Hyun-ho (choehyu...@gmail.com) wrote:
Dear Hyun-ho,
> Maybe the GRUB team already know the problem, and I hope this bug
> fixed in the next release. In the meanwhile, yes, you can change
> /etc/grub.d/10_linux like following.
>
Many thanks for your input. I fixed my grub.cfg a
d}
EOF
fi
cat << EOF
--
Regards,
-Original Message-
From: hill...@web.de [mailto:hill...@web.de]
Sent: Sunday, February 07, 2010 12:30 AM
To: Choe, Hyun-ho
Cc: 567...@bugs.debian.org
Subject: Re: Bug#567239: Same boot failure with VMWare guest in
1.98~20100128-1
On 06.02.
On 06.02.10 Choe, Hyun-ho (choehyu...@gmail.com) wrote:
Hi,
> Try to change linux/initrd to linux16/initrd16 in grub.cfg. In
> GRUB, you can change command line manually.
>
Thanks for the hint! However the next grub update/installation will
overwrite the file. Hence I guess it is a better idea
#567239: Same boot failure with VMWare guest in
1.98~20100128-1
On 01.02.10 Choe, Hyun-ho (choehyu...@gmail.com) wrote:
Hi,
> I also suffered boot failure with my VMWare guest.
>
> linux16 & initrd16 works fine.
>
Same problem here. Unfortunately I failed to figure out what exactlx
On 01.02.10 Choe, Hyun-ho (choehyu...@gmail.com) wrote:
Hi,
> I also suffered boot failure with my VMWare guest.
>
> linux16 & initrd16 works fine.
>
Same problem here. Unfortunately I failed to figure out what exactlx
I have to change. Could you tell me the exact lines or send my a
patch?
Man
Hello,
I also suffered boot failure with my VMWare guest.
linux16 & initrd16 works fine.
As I know the solution for boot, I didn't change grub.cfg to use legacy
loader, manually changed command line, and can reproduce and send some
useful debug information for you.
But, there is no mea
6 matches
Mail list logo
