<ktnb>
Hi all, I'm trying to boot the crux install USB on a framework 16 and when I select the crux install it just goes to a black screen but never boots. Any ideas?
<ktnb>
It uses EFI booting only. There is no fallback on this machine
<jaeger>
No experience with framework hardware but does it make any difference if you add 'vga=0 nomodeset' to the boot command line?
ktnb has quit [Ping timeout: 276 seconds]
lavaball has quit [Remote host closed the connection]
ktnb has joined #crux
<ktnb>
I guess I disconnected..
<ktnb>
jaeger: I'll give that a shot. Do I put that in the EFI shell?
<jaeger>
Not the UEFI, rather the grub boot command line. So you hit 'e' to edit the grub choice and add that on the linux line
<ktnb>
Oh yes yes, I know what you mean
<jaeger>
ok
<ktnb>
jaeger: it didn't work
<ktnb>
Same experience
<jaeger>
no output at all?
<jaeger>
Not sure what to make of that, sadly... do you have an external monitor to connect to it, maybe?
<ktnb>
I do. It's turned on. Maybe I should unplug it entirely
<jaeger>
I was hoping it might display something when the main display didn't, heh... but worth a try
<jaeger>
Also if the fw16 has hotkeys for toggling display modes or something, would try those too
<jaeger>
Looking at a picture of it, maybe the F9 key
<ktnb>
Unplugged the monitor and still blank. I'll try the F9 (probably fn+F9)
<jaeger>
yeah, fn+F9, I could have clarified
<ktnb>
Just for context, I've had void Linux and Devuan installed on this before and both if their ISOs booted okay
<ktnb>
(I haven't tried F9 yet)
<jaeger>
Fair, just don't know what to think without some error messages or something :/
<jaeger>
It works on all the hardware I own, but I don't have a framework
<ktnb>
Yeah, I've never had an issue before this machine (with CRUX)
<jaeger>
If the void and devuan ISOs both work I'd suspect there's some issue with the kernel config related to the EFI framebuffer, though the 'vga=0 nomodeset' options were supposed to rule that out, in theory