I've used an ATI RageII card with frame buffer driver atyfb compiled into the kernel and specified 'append = "video=atyfb:800x600@72"' in lilo.conf. I've just gotten a second computer with a ATI RagePro128 card (frame buffer driver aty128fb) and compiled both driver as modules. Now the 'append...' doesn't work any more with any driver. It seems as if the kernel parameters don't get propagated to the driver modules. Okay I specified the options for the modules in modules.conf (i.e. options atyfb 800x600@72) but it didn't help. Both modules use an resolution of 80x30 (characters), regardless what I specify. Afterwards I can switch the resolution with fbset 800x660-72. When I use modinfo at both drivers no options where shown. But when I look into the source it seems both drivers have these options. Now how can the kernel switch the resolution (append...) if the drivers doesn't have these options? I's it true that these options won't get propagated to the drivers if compiled as modules? How can I figure out which options where allowed? How does/doesn't modinfo get this information (i.e. matrox frame buffer)? Is there another solution to get the modularized drivers working besides compiling into the kernel? I'm using kernel 2.4.3 with kernel module loader, etc. on i386. O. Wyss Please CC, I'm not on the list. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
