Dne 6.12.2010 13:18, Daniel Baumann napsal(a):
by default, this is working since there's this:
lrwxrwxrwx 1 root root 27 Aug 14 11:59 /etc/rcS.d/S21console-screen.sh
-> ../init.d/console-screen.sh
lrwxrwxrwx 1 root root 23 Aug 14 11:59 /etc/rcS.d/S22console-setup ->
../init.d/console-setup
make sure your system is not altered manually wrt/ to above.
Hello Daniel,
First, I have forgot to mention that console font is setup if I boot
with "nosplash" boot param. So my rc.S symlinks do probably work.
Second, I tried to manage what happening by examine /var/log/boot.log as
mentioned in /usr/share/doc/plymouth/README, but there is no such file.
/var/log is owned by root.root, access is 0755.
LC_ALL=C plymouth-log-viewer
Failed to open file '/var/log/boot.log': No such file or directory
Now to your question:
I use kdb instead of console-tools, therefore no console-screen.sh
init.d script.
lrwxrwxrwx 1 root root 13 30. lis 23.29 S16kbd -> ../init.d/kbd
lrwxrwxrwx 1 root root 23 30. lis 23.29 S17console-setup ->
../init.d/console-setup
These symlinks match with dependencies in their init.d scripts. I run
"insserv -d kbd console-setup" for sure, but nothing has been changed.
Next I replaced kbd package with console-tools (1:0.2.3dbs-69).
Now I have
lrwxrwxrwx 1 root root 27 7. pro 00.45 S17console-screen.sh ->
../init.d/console-screen.sh
lrwxrwxrwx 1 root root 13 7. pro 00.45 S18kbd -> ../init.d/kbd
lrwxrwxrwx 1 root root 23 7. pro 00.45 S19console-setup ->
../init.d/console-setup
Start script are shifted now because console-screen.sh depends on $local_fs.
I restarted and console fonts were still not set.
Next I disabled gdm3 starting and console font is setup right (same as
with nosplash boot param).
I tried install kdm instead, but didn't work neither.
$ cat /etc/initramfs-tools/modules
i915 modeset=1
xorg: 7.5+8
graphics card: Integrated Graphics Chipset: Intel(R) 965GM (X3100 on
notebook placket)
xorg using intel driver
ACER 5313
Cheers,
Petr
--
S pozdravem,
Petr Gajdůšek
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
