Bug#422794: Starting is impossible

2007-05-13 Thread Robert Millan
On Fri, May 11, 2007 at 09:31:03AM -0300, Otavio Salvador wrote: Jonny [EMAIL PROTECTED] writes: Robert Millan [EMAIL PROTECTED] write: Can you try 800x600x32 and 640x480x8 ? Since my machine is't supporting a 32-bit color, 800x600x32 can't be used. If it's 800x600x24, it works

Bug#422794: Starting is impossible

2007-05-11 Thread Jonny
Robert Millan [EMAIL PROTECTED] write: Can you try 800x600x32 and 640x480x8 ? Since my machine is't supporting a 32-bit color, 800x600x32 can't be used. If it's 800x600x24, it works well. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL

Bug#422794: Starting is impossible

2007-05-11 Thread Otavio Salvador
Jonny [EMAIL PROTECTED] writes: Robert Millan [EMAIL PROTECTED] write: Can you try 800x600x32 and 640x480x8 ? Since my machine is't supporting a 32-bit color, 800x600x32 can't be used. If it's 800x600x24, it works well. Ah nice. Robert, I think we might reduce the color depth used by

Bug#422794: Starting is impossible

2007-05-10 Thread Otavio Salvador
Jonny [EMAIL PROTECTED] writes: Does your video hardware support vesa? Yes, it works correctly if c is typed and input. grub font /boot/grub/unifont.pff grub insmod gfxterm grub set gfxmode=800x600x8 grub terminal gfxterm Does: grub font /boot/grub/unifont.pff grub set

Bug#422794: Starting is impossible

2007-05-10 Thread Robert Millan
On Thu, May 10, 2007 at 05:14:02AM +0900, Jonny wrote: Does your video hardware support vesa? Yes, it works correctly if c is typed and input. grub font /boot/grub/unifont.pff grub insmod gfxterm grub set gfxmode=800x600x8 grub terminal gfxterm [...] font /boot/grub/unifont.pff

Bug#422794: Starting is impossible

2007-05-09 Thread Robert Millan
clone 422794 retitle -1 gfxterm breaks boot tags -1 moreinfo thanks Ok, this bug is for discussing customisation now. For the boot problem, please use the newly created one (Jonny, please answer my question about boot failure there). On Tue, May 08, 2007 at 05:22:43PM -0300, Otavio Salvador

Bug#422794: Starting is impossible

2007-05-09 Thread Otavio Salvador
Robert Millan [EMAIL PROTECTED] writes: On Tue, May 08, 2007 at 05:22:43PM -0300, Otavio Salvador wrote: Robert Millan [EMAIL PROTECTED] writes: Please do not perform update-grub compulsorily by postinst. It is very unpleasant to overwrite grub.cfg freely. I suppose it doesn't harm

Bug#422794: Starting is impossible

2007-05-09 Thread Robert Millan
On Wed, May 09, 2007 at 09:32:09AM -0300, Otavio Salvador wrote: I propose that we add a variable to select terminal, so that user can disable this feature altogether if he wants. Jonny, does that work for you? While I ack that we ought to offer this option I also think we need to

Bug#422794: Starting is impossible

2007-05-09 Thread Jonny
Robert Millan [EMAIL PROTECTED] write: Can you explain that? What happens when font is processed? A screen shot is attached. The operation is not accepted from this state at all. begin 644 grub.png MB5!.1PT*@[EMAIL PROTECTED]0$`(```!8%1QY7!(67,```L2

Bug#422794: Starting is impossible

2007-05-08 Thread Jonny
Package: grub-pc Version: 1.95+20070507-1 Severity: grave grub.cfg which broke in update-grub is generated. /etc/grub.d/00_header: if test -e /boot/grub/unifont.pff ; then cat EOF font /boot/grub/unifont.pff set gfxmode=640x480x32 insmod gfxterm insmod vbe terminal gfxterm EOF fi

Bug#422794: Starting is impossible

2007-05-08 Thread Robert Millan
tags 422794 moreinfo thanks On Tue, May 08, 2007 at 05:13:23PM +0900, Jonny wrote: font /boot/grub/unifont.pff does not run normally. The command which continues after that worsens the very thing further. Can you explain that? What happens when font is processed? Does your video hardware

Bug#422794: Starting is impossible

2007-05-08 Thread Otavio Salvador
Robert Millan [EMAIL PROTECTED] writes: Please do not perform update-grub compulsorily by postinst. It is very unpleasant to overwrite grub.cfg freely. I suppose it doesn't harm to add an option to disable it; perhaps we could even reuse /etc/kernel-img.conf. Could you file a separate bug