You are not logged in.
Hi,
I've just done a clean install of Arch and right as the nvidia module gets loaded by udev during boot a whole load of corruption/non-printable ASCII gets dumped to the screen. Nothing actually goes wrong and everything works as expected post-boot, but my boot messages are impossible to read with all the garbage on the screen.
I've tried with the main nvidia package and with nvidia-beta from the AUR, both give the same issue. I didn't have the problem on my old install, so I suspect it's been introduced by Grub 2. I have disabled Grub's framebuffer and also tried the nomodeset kernel option. Now out of ideas ![]()
Also, no errors in dmesg.
Any ideas? It's an Nvidia 670 GPU.
Thanks ![]()
Last edited by tntcoda (2012-09-09 10:51:14)
Offline
I think the default /etc/default/grub file in Arch sets GRUB_GFXMODE=auto and GRUB_GFXPAYLOAD_LINUX=keep by default. Maybe changing those and rerunning grub-mkconfig would help. Is there anything notable going on with your hardware? RAID, overclocking, etc?
Offline
Thanks, no luck with those grub options sadly and exact hardware setup has been working for years on my previous fully updated install that used grub 1.
I've done a lot more digging and it seems I was wrong about it being both Nvidia and udev related ![]()
The problem occurs during vconsole setup. Specifically on this sysinit line:
# this must be done after udev has loaded the KMS modules
status 'Configuring virtual consoles' /usr/lib/systemd/systemd-vconsole-setupThat results in this boot.msg line:
Sun Sep 9 12:03:37 2012: :: Configuring virtual consoles [BUSY] %G [DONE]Note the sneaky %G there, only that prints out a whole load of garbage in the actual boot process.
So, it still looks like its related to some mode setting done by grub? I have blacklisted nvidia & nouveau and it still occurs.
I expected nomodeset to kill any kms problems:
GRUB_CMDLINE_LINUX="cryptdevice=UUID=**remvoed**:root:allow-discards nomodeset"Very strange - any other ideas?
--------------------------
EDIT: Ok problem solved ![]()
I failed at setting up /etc/vconsole.conf
I had only specified a KEYMAP and had omitted FONT and FONT_MAP which related in this weird behaviour (buggy feature of systemd-vconsole-setup anyway?). Glad it was that and not driver issues in the end ![]()
Last edited by tntcoda (2012-09-09 10:52:02)
Offline