Results 1 to 2 of 2
This started with the last-but-one initscripts update which recommended taking a lot of stuff out of rc.conf and putting it in small specialised files, ready for systemd. Which I duly ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 08-18-2012 #1
Garbage printed during startup
Previously everything worked fine. Now it gets to the point where the console is being configured, then it spits out a load of cyrillic characters and other garbage. After this normal service is resumed but without Arch's usual bold highlighting (that depends on tput, and I've confirmed by logging in at a console that tput doesn't do highlighting any more).
It's a minor glitch but very annoying. I've tried booting with systemd instead of init, thinking that would work better but the same thing happens.
My vconsole.conf file contains only 2 lines:
I don't know what the second line does - I copied it from an example."I'm just a little old lady; don't try to dazzle me with jargon!"
- 08-19-2012 #2
Correction: I didn't boot with systemd yesterday; I only thought I had! In fact I gave the wrong pathname for the init parameter in my kernel command line (init=/sbin/systemd) and it silently defaulted to sysvinit. I thought a program like systemd would be in /sbin but it's actually in /bin. Anyway, I have used systemd today and, as it doesn't run the scripts that printed the garbage, no garbage appears. So I suppose that's an improvement."I'm just a little old lady; don't try to dazzle me with jargon!"