Thanks Cristian, your solution seems to work great. Only one thing left needs to be solved.... Login vts now have the resolution I set in this init script. But even though syslogd is started earlier, and I also did an "echo "" > /dev/tty24" in the fb init script, tty24 (which is my syslog vt) does not want to change it resolution, and changing back and forth between a login vt and the syslog vt still forces a resolution change. Any idea to make all vts change resolution, not only login vts, but all vts I use? Gábor Cristian Gutierrez wrote: >>The scenario is the following: >>.. My system starts up >>.. I login as root >>.. # modprobe rivafb >>.. # modprobe fbcon (screen resultion is promptly set to 720x400-70 on >>all vts according to fbset -i) >>.. # fbset -a 800x600-76 >> >>In spite of the "-a", only the *first* vt's resolution is changed. >>I have to issue "fbset -a xxx" on all vt's to have their resolution >>changed, -a seems not to work at all. >> >>Why is that? How can I get "-a" to work actually? >> >> > >I don't exactly know, but then I put it in a init.d script and it gets >called before login screens come up on all other ttys, so everyone of >them inherits -somehow- tty0's framebuffer mode. > ># cd /etc ># cat init.d/fb >#!/bin/sh >fbset `cat /etc/fb-selected-mode` > ># cat fb-selected-mode >1024x768-90 > ># ls -la rc*/*fb* >lrwxrwxrwx 1 root root 12 Jan 29 05:24 rc0.d/K20fb -> ../init.d/fb >lrwxrwxrwx 1 root root 12 Jan 29 05:24 rc1.d/K20fb -> ../init.d/fb >lrwxrwxrwx 1 root root 12 Jan 29 05:24 rc2.d/S20fb -> ../init.d/fb >lrwxrwxrwx 1 root root 12 Jan 29 05:24 rc3.d/S20fb -> ../init.d/fb >lrwxrwxrwx 1 root root 12 Jan 29 05:24 rc4.d/S20fb -> ../init.d/fb >lrwxrwxrwx 1 root root 12 Jan 29 05:24 rc5.d/S20fb -> ../init.d/fb >lrwxrwxrwx 1 root root 12 Jan 29 05:24 rc6.d/K20fb -> ../init.d/fb > -- Gábor Gludovátz <ggabor@sopron.hu>
Attachment:
signature.asc
Description: OpenPGP digital signature