On Tue, 2004-11-30 at 19:18, Andreas Janssen wrote:
> Hello
>
> Colin Alie (<[EMAIL PROTECTED]>) wrote:
>
> > I'm trying to figure out how boot-time loading of modules is
> > controlled. I'm trying to keep vesafb from loading. I'm running the
> > stock 2.6.8-1-386 kernel from sarge. Below is a little bit of
> > information regarding what I've tried so far:
> >
> > - I remved the parameter vga=xxx from my kernel command line; it now
> > stands as root=/dev/hda1 ro
>
> Try to append
>
> video=vesafb:off
Adding this parameter didn't have a noticeable effect.
> > - I thought that removing /lib/modules/2.6.8-1-386/initrd/vesafb,ko
> > would help but it's absence hasn't made a difference
>
> Probably the driver is in the initrd (initial ram disk). Is it activated
> directly after loading the kernel, or later?
>
Directly after loading the kernel, so it seems. There's a line near the
beginning of /var/log/messages right after mounting of initrd referring
to it:
vesafb: probe of vesafb0 failed with error -6
As it turns out, I needn't have worried so much about this. I was
worried about vesafb conflicting with sisfb which I was considering
loading later on. However, as long as vesafb was not `active' (i.e.,
vga=normal passed to kernel), a later `modprobe sisfb' didn't cause any
problems.
Until next time, Colin.
--
Colin Alie BSc, MASc
Research Assistant
Department of Chemical Engineering
University of Waterlo
Waterloo, Ontario N2L 3G1
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
