On Fri, Jan 06, 2006 at 09:31:05AM +0100, Tobias Powalowski wrote: >Am Freitag, 6. Januar 2006 09:20 schrieb Magnus Therning: >> On Thu, Jan 05, 2006 at 07:34:18PM -0500, Eric Belanger wrote: >> >On Thu, 5 Jan 2006, Magnus Therning wrote: >> >> I've noticed some strange X-related stuff after the latest kernel >> >> upgrade. Artefacts are appearing every now and then on my screen >> >> (squares in different colours). Forcing a repaint in the area (e.g. by >> >> moving a window over it) removes it... >> >> >> >> Could this be related to the fact that I have an absolutely massive >> >> amount of kernel modules loaded. Many more than I could possibly need! >> >> >> >> I'm using hwdetect to load modules. >> > >> >I would doubt that your problem is caused by the large amount of >> >modules loaded. However, I'm not an expert on kernel stuff. Did you >> >upgrade your video drivers recently or use the xorg in testing? >> >> I don't think it's the amount of modules either, but I suspect there >> might be some FB module in there and my experience with FB is not very >> good. I'm not using X from testing. >> >> >If you want to reduce the amount of loaded modules, you could use a >> >custom initrd and blacklist the modules for hardware you don't use. >> >> Huh? Now I'm really confused. Here is what I thought was going on: >> >> Installing a (recent) kernel causes a ramdisk to be created. That >> ramdisk contains the minimal set of modules needed to bring _my_ system >> up to a state where hwd/hwdetect can be used to load more modules. >> >> Your statement together with the massive amount of loaded modules >> suggests that my ramdisk contains a hell of a lot more than what's >> needed and it's all loaded (e.g. several filesystems I don't use are >> loaded). Then hwd/hwdetect comes along just in case something is >> missing. >> >> It seems to me that hwd is doing a good job of loading modules, but it's >> being sabotaged by a bloated ramdisk. Is there an easy way of creating a >> smaller ramdisk? >> >> /M >Hi >i would still recommend hwdetect for module loading because it uses >dynamic tables and not static tables to detect hardware, and initrd can >be tweaked to use hwdetect too for modules. >check /etc/mkinitrd.conf for AUTODETECT=1 option or check the arch wiki >to find out more about mkinitrd tweaking
Thanks. This cleared up a bit for me. I was expecting AUTODETECT=1 by default I guess, since it makes sense to me. Turned it on and my ramdisk size was cut in half. Some tuning of the filesystems and another few Ks disappeared. Now let's hope it boots ;) /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) [EMAIL PROTECTED] http://therning.org/magnus Software is not manufactured, it is something you write and publish. Keep Europe free from software patents, we do not want censorship by patent law on written works. Necessity is the plea for every infringement of human freedom. It is the argument of tyrants; it is the creed of slaves. -- William Pitt, House of Commons, 18/11/1783.
pgp4zn6tfurhR.pgp
Description: PGP signature
_______________________________________________ arch mailing list arch@archlinux.org http://www.archlinux.org/mailman/listinfo/arch
