You are not logged in.
Hey all,
I made a post about this on the Unix stackexchange but thought others on this site might have a better idea of its cause, or rather if it has nothing to do with Arch specifically.
My laptop is a Toshiba CB35-B3340. Also called a Chromebook 2, with part number PLM02U-009008. I had a working installation of Arch on it yesterday, but accidentally destroyed it while moving partitions around.
On the previous installation, this weird glyph-like text error would occur in the middle of boot, but would resolve itself at the login prompt and I would proceed. I had intended to get to the cause of it, but decided not to bother.
I am now dealing with this same issue. During boot, the glyph-like text error appears. Unlike before, it does not resolve itself automatically. Please see attached my five images that illustrate the boot sequence.
Note that I'm certain that I'm actually interfacing with the system. I can tell from what I'm putting into the console and the length of the output that I am indeed dealing with a simple working installation of Arch.
http://i.stack.imgur.com/ONeSz.jpg
Normal text from the BIOS. I've installed SeaBIOS, as is necessary for chromebooks.
http://i.stack.imgur.com/6weMD.jpg
Getting the GRUB2 menu as normal. Arch Linux is the highlighted entry.
http://i.stack.imgur.com/Q8OgN.jpg
Nearing the end of the boot process. Then, right after Loading initial ramdisk,
http://i.stack.imgur.com/RzIST.jpg
Complete gibberish. This is the login prompt.
http://i.stack.imgur.com/Xj6st.jpg
More gibberish. This is the output of uname -a after having logged in as root.
I have tried changing the font with setfont, and it does have an effect; I can set Goha-12, Goha-14, and Goha-16 and the difference will be the height. The glyphs, however, will remain.
Does anyone have any ideas?
Thank You.
Mod note: Converted imgs to urls, please see the Code of Conduct regarding acceptable image sizes -- WorMzy
Last edited by WorMzy (2016-06-15 20:10:47)
Offline
What's the content of /etc/vconsole.conf. I suggest you leave out all fonts from this file for the default font to be pick up. Grub might be the problem as it try to configure the console (which is a very bad idea IMHO). Try to boot with another boot manager or put
terminal_input console
terminal_output consolein /boot/grub.cfg (and ensure that it is not overridden afterwards) (if that does not work really try to boot with another boot manager or find a grub GURU).
Offline
(First, my apologies about the images. Thanks for fixing it, WorMzy!)
Hey Olive,
Thanks for checking up on my post. When you asked for the content of vconsole.conf, I noticed that it was MISSING. I ended up realizing that I'd missed a few early steps in configuration and generating locales. While I don't entirely understand how that effected things, I just started over and the new installation is running as well as before. I haven't touched alt bootloaders so it's perfectly reasonable to assume the above problems are still problems-- but since it works I'll leave it be for the moment. XD
Offline