RE: [gentoo-user] Boot stalls after install of 2005.1

["Marcel Romijn" <MRomijn@seagullsoftware.com>]

 

> -----Original Message-----
> From: A. Khattri [mailto:ajai@bway.net] 
> Sent: Tuesday, 23 August, 2005 16:08
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] Boot stalls after install of 2005.1
> 
> On Tue, 23 Aug 2005, Marcel Romijn wrote:
> 
> > vesafb: VBE version: 3.0
> > vesafb: protected mode interface info at c000:8846
> > vesafb: pmi: set display start = c00c8897, set palette = c00c88f7
> > vesafb: pmi: ports = b4c3 b503 d403 d503 cc03 d703 d803 d903 ff03
> > vesafb: hardware supports DDC2 transfers
> > vesafb: monitor limits: vf = 200 Hz, hf = 133 kz, clk = 350 MHz
> > vesafb: scrolling: redraw
> > (nothing more)
> 
> Im assuming you removed any references to frame-buffers in 
> grub.conf after
> building a new kernel without framebuffer support?
> 
> Also, did you use genkernel to build your kernel?

Yes, I used everything as default as possible.
I used 'genkernel' to build my kernel with the default configuration.

I assumed that even though the kernel has framebuffer support built in,
it won't use it if it is not configured as kernel parameter in
grub.conf.
Maybe that was a wrong assumption?

I used to initially have "video=vesafb-tng:mtrr,ywrap,1024x768-32@85" in
the kernel parameters.
However, I removed it when the boot process stalled after "vesafb:
scrolling: redraw"

So it looks like I could go two ways:
- Configure the framebuffer properly in grub.conf.
- Build a new kernel with framebuffer disabled.

I would prefer the first option...

> You might want to try building the kernel "by hand" instead.
> 
> 
> -- 
> 
> -- 
> gentoo-user@gentoo.org mailing list
> 
> 
> 

Marcel Romijn

-- 
gentoo-user@gentoo.org mailing list