On Friday, 28 July 2006, you (Steffen Joeris) wrote: [...] > Can you maybe test your suggestion and tell me if and how it works? > I normally would think the current situation is optimal, but please tell me > how it works for you.
Hi Steffen, I made the following simple changes directly on the i386 binary package: - removed -rc.d related stuff, by deleting postinst, postrm and prerm; Probably not the best thing if we want to let admin change the run order, but changing the level when it is run (rcS.d) should be pointless. This was simpler and faster for me to do like this, rather than using update-rc.d; Also, invoke-rc.d is pointless (for me) since /etc/default/915resolution is empty at first time, and I will never remove it after initial installation so it's always being run once at startup. After testing Ubuntu Dapper, I saw there's now some kind of resolution auto-detection and setup, because simply installing the package did the trick. This is another point against removing those package scripts. - manually added /etc/rcS.d/S07915resolution as a symbolic link to /etc/init.d/915resolution. 07 is the same level as hdparm so it's executed about the same time, which means some kind of hardware setup. As stated in /etc/rcS.d/README, the scripts linked in this directory are always "start"ed exactly once, whatever runlevel you're booting to, and before any other /etc/rc[1-5].d/ scripts. This actually works as expected: If I boot to normal runlevel, X & xdm start with the correct resolution (1280x800); If I boot directly into single user, I am also able to start X from the command line, and it also displays the correct resolution. These changes have been used in "production" since months, without any spotted problem. PS: FYI I have an 915GM chipset/graphics in my laptop. I think my changes are independant from host hardware, so I expect these to work everywhere. -- Hope this helps, Fabien. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
