Recently, Somebody Somewhere wrote these words > On Wed, Jun 29, 2005 at 06:43:49PM +0100, Declan Moriarty wrote: > > > > Should I choose a 2.6 kernel, the loadkeys script doesn't start, and > > I get this curious messing with no cursor. > > To me it smells like a framebuffer issue. Ok, here is (almost) all I > know about the framebuffer: > > Try 'modprobe fbcon'. If you compiled a framebuffer module for your > vga hardware, modprobe it first.
modprobe radeon got me a module which found the right type of card in the agp bus. That looked good. modprobe fbcon gave me: FATAL: Module fbcon not found. Which kind of tells me I didn't compile in a framebuffer at all. [EMAIL PROTECTED] /usr/src/linux-2.6.12.1]# grep FRAMEBUFFER .config # CONFIG_FRAMEBUFFER_CONSOLE is not set but the radeon module loaded a module called fb. Same thing? > > With kernel 2.6 modules are not loaded automatically the same way as > with kernel 2.4. /etc/modules.conf has been renamed to > /etc/modprobe.conf (and maybe there are some more changes, I don't > know). At least some modules seem to be not loaded automatically at > all anymore. You have to load them explicitely with 'modprobe xyz'. > The dependencies between modules still work though, so some modules > still pull up others behind them. Play with lsmod, modprobe, rmmod and > 'cat /proc/devices'. 'fb' is a character device. What you are saying is than the "new" module-init tools are crap. I agree. Also some dweeb changed the names of all these modules. > > Install fbset. It may save you some boot processes when you are > dealing with framebuffer issues. Get it from > http://packages.debian.org/unstable/base/fbset It's at the bottom of > the page. Get the diff too, it produces some nice documentation (and > the usual debianisms of course). Untar it, then > > cd fbset-2.1 patch -Np1 -i ../fbset_2.1-17.diff make install mkdir -p > /usr/share/doc/fbset cp -a etc/* /usr/share/doc/fbset cp -a > debian/doc/* /usr/share/doc/fbset > > Copy the appropriate fb.modes file to /etc (or make one yourself, I > don't know how yet.) I think you take lines pretty much like the XFConfig mode lines that don't blow your monitor up. Get the stahndard vesa ones and you are fairly safe. > > cp etc/fb.modes.ATI /etc/fb.modes Got fb.modes - I had it from my lfs-3.3, which did have a framebuffer. > > Use it with 'fbset 800x600-60'. 'fbset' is very old and very cool, > trust me. > I have a feeling the issue is this: When the 2.6 kernel came out, it had alpha or beta versious of all the support packages required to support it. The 2.6.0 kernel gave a huge list of things to check versions on. I updated them for the 2.6.0 kernel. Now of course, things have moved on. I just updated module-init-tools from 0.15xx to 3.2xx which gives you an idea. I haven't updated anything else, so I could be tripping over dud versions ofthings like procps. I stayed away from framebuffer in general because I don't want the display to get any smaller - I have nerdy kids who will read tiny fonts at 1024x768, whereas my eyesight is telescoping a bit. -- With best Regards, Declan Moriarty. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
