<elvishjerricco>
Note the `BAR 0: no space for [io size 0x0100]` near the end
<elvishjerricco>
Does the fact that my model only has 2GB of ram matter? (can't find the 4GB or 8GB models anywhere :/)
monk has left #nixos-aarch64 ["Error from remote client"]
<samueldr>
I don't know much, but I seem to recall it happens that some systems have limits that can't be fixed
monk has joined #nixos-aarch64
<samueldr>
e.g. RK3399 is limited to 32MiB of BAR or something like that
<samueldr>
(preventing use of external GPUs)
<elvishjerricco>
samueldr: The latest pi firmware enables up to 1G of BAR
<elvishjerricco>
I have no idea if it can be configured higher if you want
<samueldr>
yeah, just saying what I knew
<samueldr>
pretty sure it's limited to 1GB
<samueldr>
and in the *first* GB
<elvishjerricco>
I doubt this HBA needs 1G of BAR though, right?
<samueldr>
so if things are in the first GB of memory for other reasons, that's less space available
<samueldr>
but I don't know what to make of what I said
matthewcroughan has joined #nixos-aarch64
monk has left #nixos-aarch64 [#nixos-aarch64]
h0m1 has quit [Ping timeout: 260 seconds]
monk has joined #nixos-aarch64
h0m1 has joined #nixos-aarch64
awmv has quit [Quit: Connection closed for inactivity]
spacetato has joined #nixos-aarch64
evils has joined #nixos-aarch64
orivej has joined #nixos-aarch64
<clever>
samueldr: https://youtu.be/u7DzPvkzEGA, the glitching is just due to pushing it too far over the edge, it can do the same thing (with less sprites) without glitching
orivej has quit [Ping timeout: 244 seconds]
<patagonicus>
elvishjerricco: https://www.youtube.com/watch?v=ikpgZu6kLKE talks about BARs a bit, trying to get GPUs working on the CM4 (not really successful, but they get past the BAR no space problems).
<clever>
patagonicus: jeff geerling?
<patagonicus>
Yep. Don't really watch the channel, but happened to watch that video a couple of days ago.
<elvishjerricco>
patagonicus: yea, he just increased how much BAR space there was. The latest rpi firmware does this on its own
<clever>
elvishjerricco: i saw something about the default being cranked up to 1gig
<patagonicus>
Ah, ok, didn't know that.
<elvishjerricco>
I think my problem is that my model is a 2GB RAM model. Reading some forum posts, it seems like the 4GB+ models work a little better with this stuff
<clever>
there are also dma bugs, where the pci-e can only access the lower 3gig of ram
<clever>
fixed in later revisions, but not documented well enough
<elvishjerricco>
I wish I knew how to interpret the numbers in that paste I linked before. Might make it possible to understand the actual issue...
<clever>
2021-03-22 22:17:47 < elvishjerricco> Note the `BAR 0: no space for [io size 0x0100]` near the end
<elvishjerricco>
I did manage to find a 4GB model tonight though, so we'll see if that's the magic fixer.
<clever>
elvishjerricco: the CM4 has zero support for IO BAR's
<clever>
IO is an x86 concept, and not all arm systems have translation for it
<clever>
some devices have both io and mmio BAR's, but the driver needs to support switching over
<elvishjerricco>
clever: Oh so this card just relies on stuff the cm4 fundamentally can't handle?
<clever>
depends on if there is a fallback in mmio or not
<clever>
and if the drivers support that
<elvishjerricco>
Is there something I could do to test that?
<clever>
load the driver and see if it worsk :P
<clever>
to get a more detailed answer, you would have to learn what the driver is doing to talk to the card
<elvishjerricco>
fwiw, geerling did manage to get a fairly modern hardware RAID card working in some of his recent videos
<elvishjerricco>
dunno if that's at all relevant
<clever>
every pci-e card behaves in a different way
<elvishjerricco>
So I might just have to wait until someone finds a HBA that works on the CM4 and then find one of those on ebay or something :P
<clever>
or find a kernel developer that is familiar with a given card, and loan him a CM4
adamzivcak has joined #nixos-aarch64
cole-h has quit [Ping timeout: 246 seconds]
zupo has joined #nixos-aarch64
monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
orivej has joined #nixos-aarch64
FRidh has joined #nixos-aarch64
Raito_Bezarius has quit [Ping timeout: 260 seconds]
monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
<artturin>
Ales Huzik: download the demo rootfs then flash it and build and flash the boot partition and uboot they can be crosscompiled
monk has left #nixos-aarch64 ["Error from remote client"]
zupo_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<clever>
,stty
<{^_^}>
echo "stty rows $(tput lines) cols $(tput cols)" # Alternatively eval `resize` may work
<clever>
samueldr: ive just confirmed, just running resize, without even an eval, worked
apache8080 has joined #nixos-aarch64
monk has left #nixos-aarch64 ["Error from remote client"]
<apache8080>
I want my /boot on a separate device from the rest of /, so could I simply add fileSystem."/boot" and fileSystems."/" to my config file and point them to the respective drives