#asahi · 2024-05-08 14:18
PaulFertser(provided your app supports the needed framebuffer parameters)#asahi · 2024-05-08 14:18
PaulFertserbawj_: anyway, glad to hear it worked. I think it's a solid indication same would work on mac.#asahi · 2024-05-08 14:13
PaulFertserbawj_: just -device VGA and no tricks, no recompiling anything?#asahi · 2024-05-08 12:13
PaulFertserAnd probably that just works with VIDEO_VESA#asahi · 2024-05-08 12:02
PaulFertserbawj_: u-boot docs suggest "-serial stdio -device VGA" https://docs.u-boot.org/en/latest/board/emulation/qemu-arm.html#asahi · 2024-05-08 11:56
PaulFertserbawj_: I do not think U-boot supports virtio protocol, no. I expected qemu to have emulation for some simple on-chip "video card" as integrated in many SoCs.#asahi · 2024-05-08 11:41
PaulFertserbawj_: right. So probably the DT you're using doesn't define a video device?#asahi · 2024-05-08 11:37
PaulFertserI think there should be an easy way to do that but I can't tell what exactly to choose in the options. Would be really surprising if Qemu didn't support at least one board which is also supported by U-boot video drivers.#asahi · 2024-05-08 11:31
PaulFertserSo you need to build with CONFIG_LCD and run on supported emulated board.#asahi · 2024-05-08 11:30
PaulFertserbawj_: it was added long time ago https://patchwork.ozlabs.org/project/uboot/patch/1458063501-211379-1-git-send-email-agraf@suse.de/#asahi · 2024-05-08 11:28
PaulFertserbawj_: probably your u-boot was built without it?#asahi · 2024-05-08 09:46
PaulFertserIn this case it's "Apple Mac mini (M1, 2020)" running 6.6.3 Fedora#asahi · 2024-05-08 09:10
PaulFertserAnd now it's default either way#asahi · 2024-05-08 09:09
PaulFertserbluetail: 4k should be good#asahi · 2024-05-08 08:29
PaulFertserThe devs here should be able to give a better advice, yes.#asahi · 2024-05-08 08:28
PaulFertserI guess you should report instances of those as a github ticket. It's strange they only affect the xhci controller in your testing but it's up to the real devs to judge what other data or tests might be useful.#asahi · 2024-05-08 08:26
PaulFertsertranslation faults are bad mkay?#asahi · 2024-05-08 08:21
PaulFertserThose apple-dart errors look scary and probably that's what you need to discuss with the devs.#asahi · 2024-05-08 08:20
PaulFertserAnd then 30 seconds later exactly the hell broke loose.#asahi · 2024-05-08 08:19
PaulFertserIt might have started with that.#asahi · 2024-05-08 08:19
PaulFertserApr 16 00:39:17 archm1 kernel: apple-dart 502f80000.iommu: translation fault: status:0x81000404 stream:1 code:0x404 (unknown) at 0xffda4080#asahi · 2024-05-08 08:19
PaulFertserHuh that's another day and another problem.#asahi · 2024-05-08 08:17
PaulFertserThat's assuming your logs have full information. From what you show it looks like there's no issue detected at all anyhow on any level until suddenly access beyond the end is made.#asahi · 2024-05-08 08:13
PaulFertserUSB packets have CRC so silent data corruptions on USB level shouldn't be practically possible.#asahi · 2024-05-08 08:08
PaulFertserReading past end of device isn't supposed to not generate an error.#asahi · 2024-05-08 08:08
PaulFertserbluetail: I see no USB errors but I see "attempt to access beyond end of device sda: rw=524288, sector=39063650176, nr_sectors = 32"#asahi · 2024-05-08 08:01
PaulFertserbluetail: a log that's days old is still much better than no log at all.#asahi · 2024-05-08 07:58
PaulFertserAre the disks essentially powered by mac itself or is there an additional power supply adapter?#asahi · 2024-05-08 07:57
PaulFertserBut without kernel log one can't be sure it's a USB error even.#asahi · 2024-05-08 07:57
PaulFertserUSB-level errors are no good ever but shouldn't be related to btrfs or anything like that#asahi · 2024-05-08 07:55
PaulFertserbluetail: devil's in the details...#asahi · 2024-05-08 07:54
PaulFertserj`ey: a fix is not a workaround and u-boot is completely out of the picture once the kernel boots, unlike m1n1.#asahi · 2024-05-08 07:52
PaulFertserbluetail: so did you file a ticket with kernel logs from those USB drop outs? Also are you sure it's not a power supply issue?#asahi · 2024-05-08 07:50
PaulFertserbluetail: neither m1n1 source code nor commit log contain anything about "icy".#asahi · 2024-05-08 07:47
PaulFertserbluetail: but once Linux is booted the hypervisor shouldn't affect any kind of interaction with the USB Host Controller anyhow, right? So how is this relevant?#asahi · 2024-05-08 07:45
PaulFertserbluetail: what's the workaround btw, can you share a link?#asahi · 2024-05-08 07:43
PaulFertserSo you want a big tower to use as a NAS? :)#asahi · 2024-05-08 07:42
PaulFertserRack servers are nice for datacentres but too noisy for a living room.#asahi · 2024-05-08 07:39
PaulFertserMac workstation?#asahi · 2024-05-08 07:39
PaulFertserI mean what's normal setup?#asahi · 2024-05-08 07:39
PaulFertserbluetail: dump for what?#asahi · 2024-05-08 07:37
PaulFertserbawj_: btw, it's not like you can't use any popular ARM64 system in Qemu with U-boot to try to see how your app works with U-Boot's limited UEFI implementation.#asahi · 2024-05-08 07:35
PaulFertserbluetail: btw, why are you suspecting a hw issue?#asahi · 2024-05-08 07:35
PaulFertserbawj_: I think if you want networking for a UEFI app it's possible with U-Boot with one of the supported USB Ethernet adapters.#asahi · 2024-05-08 07:30
PaulFertserbawj_: btw, UEFI graphics is not so much a protocol rather static information about current linear framebuffer configuration.#asahi · 2024-05-08 07:29
PaulFertserbluetail: probably this U-boot binary was compiled without this command, why not, U-boot is highly configurable.#asahi · 2024-05-08 07:28
PaulFertserAlso, if you do not load anything non-essential almost all of the memory will be available to Linux userspace, and you could try https://linux.die.net/man/8/memtester#asahi · 2024-05-08 07:25
PaulFertserThere's also "mtest" in u-boot.#asahi · 2024-05-04 10:05
PaulFertserJust as the wiki mentions, the GUI is limited there.#asahi · 2024-05-04 10:05
PaulFertsernano: https://github.com/AsahiLinux/docs/wiki/Partitioning-cheatsheet