vika_nezrimaya has quit [Ping timeout: 258 seconds]
zupo has joined #nixos-aarch64
vika_nezrimaya has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
vika_nezrimaya has quit [Ping timeout: 245 seconds]
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
jtojnar has quit [Quit: jtojnar]
jtojnar has joined #nixos-aarch64
jtojnar has quit [Quit: jtojnar]
jtojnar has joined #nixos-aarch64
orivej has quit [Ping timeout: 244 seconds]
orivej has joined #nixos-aarch64
wildtrees has joined #nixos-aarch64
gchristensen is now known as gchrholiday
egasimus has joined #nixos-aarch64
<egasimus>
hi all
<egasimus>
anyone running nix on rpi 3 with the 7" touchscreen?
<samueldr>
"the" touchscreen may be a misnomer
<egasimus>
the "official" one
<samueldr>
it's probably best to have a model number
<samueldr>
ah, then it's probably well identifier
<egasimus>
yep, the default DSI one
<samueldr>
no I do not, but one of the most likely issue you will face is that by default we're using the mainline kernel, rather than the raspberry pi foundation's kernel
<samueldr>
linuxPackages_rpi would point to the foundation's kernel, but...
<egasimus>
yeah, had to downgrade to linuxPackages_4_19 to get anywhere
<samueldr>
... we're also building as 64 bit, rather than 32 bit, so that may also be an issue
<samueldr>
though I'm not saying it's impossible with the mainline kernel, only that it's something that's different from the usual raspbian-derivatives :)
ryantrinkle has joined #nixos-aarch64
<egasimus>
I think I'm just having trouble finding info about configuration parameters
<egasimus>
wanna hear what's going on? :)
<egasimus>
anyway here goes: during boot, I get console output from U-Boot on the DSI display in question
<egasimus>
and all is fine until it loads the kernel. my ttys keep showing on the HDMI output
<egasimus>
and I have no idea what I should set and where to select the touchscreen
<egasimus>
although you're right it might go deeper than that, since it only works before the kernel has loaded...
<egasimus>
@samueldr think it's worth a try with linuxPackages_rpi?
<egasimus>
I really don't wanna install X on this box and open a whole new can of worms
<egasimus>
I just want my console on the DSI LCD and not on the HDMI port
<samueldr>
things _will_ be different with the rpi package, but I don't know how :/
<samueldr>
(how different, that is)
<samueldr>
I have yet to look at all that properly to better understand it
<samueldr>
(now that I have some hardware to test with)
<egasimus>
ok, I'm gonna give it a shot in a few mins and let you know how it goes...
<samueldr>
I'm guessing, without having tried, that if the dtb filenames from the rpi kernel fork are different, u-boot may have trouble finding the right one
<samueldr>
I'm not sure whether it will stop or carry on
ryantrinkle has quit [Ping timeout: 244 seconds]
<egasimus>
ok, intermediate result
<egasimus>
had some changes to boot.loader that I wanted to try first
<egasimus>
with the raspberry pi bootloader and "display_default_lcd=1" in firmwareConfig (config.txt) the HDMI is set to 800x480 which is the LCD's resolution
<egasimus>
gonna try adding framebuffer_priority=0 or 1 and then the rpi kernel
zupo has joined #nixos-aarch64
<egasimus>
before, I was just messing with /boot/config.txt directly
<samueldr>
I don't know what will and will not be honoured when it goes through u-boot
<egasimus>
well, let's see
zupo_ has joined #nixos-aarch64
<egasimus>
not with framebuffer_priority=0
<egasimus>
here's what it says about that option though: "In a system with multiple displays, using the legacy (pre-KMS) graphics driver..."
zupo has quit [Ping timeout: 258 seconds]
<egasimus>
what's the legacy (pre-KMS) graphics driver?
<samueldr>
KMS is kernel-mode settings
<samueldr>
I'm not sure what it means in relationship to the raspberry pi and their fork of the kernel, and if it applies to the mainline kernel
<egasimus>
I think is kernel mode-setting ... so it has to do with the display driver in any case
<egasimus>
anyway trying out this hunch I have and then will retry with the rpi kernel
<egasimus>
no dice .. fuck this is time-consuming
<egasimus>
rebuiilding with linuxPackages_rpi now
zupo_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<egasimus>
rebooting ... hmm what's max_framebuffers though :)))
<egasimus>
doesn't matter
<egasimus>
samueldr you were right all the time ...
<egasimus>
all I had to do was switch to linuxPackages_rpi
<egasimus>
and now I have my TTY on my LCD
<samueldr>
great, though I didn't _know_ it was going to work :)
<egasimus>
:))) thanks for the pointer
<samueldr>
I only knew that they have their own ecosystem and our aarch64 images don't conform to it; they're generic aarch64 images
<samueldr>
good to know that at least for the 7" official DSI LCD this can work
<egasimus>
you know what I'm noticing though...
<egasimus>
I'm having that issue with the red and blue channels switched ... :D :D :D