#
✕ nick:Glanzmann
#asahi · 2023-01-04 15:41
Glanzmannsven: Debian example: https://pbot.rmdir.de/S91KOYOzF9PE2EK_qpsNcw
#asahi · 2023-01-04 15:40
Glanzmannsven: The stuff that we extract to the esp partition and the file we dd to the partition we create.
#asahi · 2023-01-04 15:37
Glanzmannsven: Yes, but it might be the case that this streaming behaviour is only possible with 'zip' and not with tar besides urllib3 now having zstd support.
#asahi · 2023-01-04 15:36
Glanzmannkettenis: Nope, it does not. But building the debian installer most of the time I wait for zip to finish. For m a r c a n it is worse because his image is 10 times bigger.
#asahi · 2023-01-04 15:27
Glanzmannmarcan: https://sethmlarson.dev/urllib3-in-2022 seems to support zstandard compression. Can we use that instead of zip for the installer or does it not support streaming? I would prefer zstandard over zip because it compresses better and can use multiple cpus for compression.
#asahi · 2022-12-16 08:37
Glanzmannc
#asahi · 2022-12-16 08:29
GlanzmannSee: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025419
#asahi · 2022-12-16 08:27
Glanzmannpsykose: They updated the libunwind to a new release. The new release assumes 4k pages. Upstream has the patch but have not releasesd a new version since then.
#asahi · 2022-12-16 08:05
Glanzmannjmr2: The root cause for your xorg crashing is that Debian updated libunwind with a 4k bug. So you need a patched version. See my repository 'libunwind.sh' or install the updated libunwind package from my repository. Let us know if it works for you (tm).
#asahi · 2022-12-16 08:03
GlanzmannMoving to asahi-alt
#asahi · 2022-12-16 08:02
Glanzmannjmr2: Have you tried: https://thomas.glanzmann.de/asahi/README.txt
#asahi · 2022-12-15 17:35
Glanzmannaxboe: No, idea. Maybe jannau has an idea. I'm brb groceries.
#asahi · 2022-12-15 17:26
GlanzmannI checked the mesa options again but did not find any differnce.
#asahi · 2022-12-15 17:17
GlanzmannMaybe I'm missing a commandline argument for mesa?
#asahi · 2022-12-15 17:11
Glanzmannaxboe: ALso I noticed that the chromioum package in Debian testing was update from 107 to 108.
#asahi · 2022-12-15 17:11
Glanzmannaxboe: But he has a newer version than we have.
#asahi · 2022-12-15 17:10
Glanzmannaxboe: mkurz says it is also working on x11: https://github.com/AsahiLinux/linux/issues/73
#asahi · 2022-12-15 17:01
GlanzmannAh, I see.
#asahi · 2022-12-15 17:00
GlanzmannBecause webgl is also not working for me.
#asahi · 2022-12-15 17:00
Glanzmannaxboe: So the problem is not that chrome does not start, but that webgl is not working?
#asahi · 2022-12-15 16:57
GlanzmannThis is the output I get when I start chromium: https://pbot.rmdir.de/waMUG8ixl-rkl5mLG_y9sg
#asahi · 2022-12-15 16:55
GlanzmannAnd also the bloated debian kernel.
#asahi · 2022-12-15 16:55
GlanzmannThjat is the most recent: https://thomas.glanzmann.de/asahi/pool/main/linux-image-6.1.0-asahi_6.1.0-asahi-61_arm64.deb
#asahi · 2022-12-15 16:55
GlanzmannSOryr, wrong one.
#asahi · 2022-12-15 16:55
Glanzmannhttps://thomas.glanzmann.de/asahi/pool/main/linux-image-6.1.0-rc8-asahi_6.1.0-rc8-asahi-57_arm64.deb
#asahi · 2022-12-15 16:54
Glanzmannaxboe: Try my kernel.
#asahi · 2022-12-15 16:54
GlanzmannSame version, strange.
#asahi · 2022-12-15 16:54
Glanzmanndpkg -l | grep chromium > 108.0.5359.94-1
#asahi · 2022-12-15 16:52
Glanzmannaxboe: Might be possible that you have some old mesa lying around in /usr/local/lib? YOu can check with ldd /usr/bin/mpv | grep local
#asahi · 2022-12-15 16:52
Glanzmannaxboe: That starts for me: MESA_LOADER_DRIVER_OVERRIDE=asahi chromium --ignore-gpu-blocklist
#asahi · 2022-12-15 16:49
Glanzmanniaguis: We're not on wayland.
#asahi · 2022-12-15 16:47
Glanzmannthis works for me, but jannau had a better one: LIBGL_ALWAYS_SOFTWARE=1 chromium
#asahi · 2022-12-15 16:47
Glanzmannaxboe: Do you still have the chromium command line that jannau gave us?
#asahi · 2022-12-15 16:44
Glanzmannaxboe: Nope, I have: 3fc6e787ce9da1b5e323974ca134647d69dd2573
#asahi · 2022-12-15 16:43
Glanzmannaxboe: I have the tip of asahi.
#asahi · 2022-12-15 16:42
Glanzmannaxboe: Let me try to build xfce 4.18.
#asahi · 2022-12-15 16:42
Glanzmanniaguis: Not all, but axboe and few others are.
#asahi · 2022-12-15 16:39
Glanzmannaxboe: I also added a lot of scripts to the m1-debian repository to build rust, kernel, m1n1, u-boot and mesa
#asahi · 2022-12-15 16:38
GlanzmannIncluding chromium.
#asahi · 2022-12-15 16:38
Glanzmannaxboe: These packages work for me: https://thomas.glanzmann.de/asahi/README.txt
#asahi · 2022-12-12 00:12
Glanzmannn8
#asahi · 2022-12-12 00:12
Glanzmannanyhow mystery solved.
#asahi · 2022-12-12 00:12
Glanzmannhttps://pbot.rmdir.de/fXfjqRkJZU6uag62mXaRIg
#asahi · 2022-12-12 00:12
GlanzmannYes, I can trigger the oops by unloading and reloading the wifi driver: https://pbot.rmdir.de/rF351aWmwCiFcjX4rfjzNQ
#asahi · 2022-12-12 00:09
GlanzmannFor completnes https://tg.st/u/0001-add-blacklist-file.patch
#asahi · 2022-12-12 00:08
Glanzmannhits bed.
#asahi · 2022-12-12 00:08
GlanzmannIn the old days it worked but with the more recent kernel version it no longer does.
#asahi · 2022-12-12 00:07
Glanzmannmarcan: Turned out that the oops was trigger by unloading and reloading the brcmfmac module. I now changed my code so that it blacklists the module and only loads the module once the firmware is available. And does not reload module when the firmware is updated, but only updates the firmware. https://tg.st/u/0001-be-less-aggrassive-on-the-wifi-driver-it-is-fragile.patch
#asahi · 2022-12-11 23:45
GlanzmannMaybe I managed to corrupt my firmware files somehow. That would at least explain why the issue was gone after removed them and put them back.
#asahi · 2022-12-11 23:42
Glanzmannmarcan: Must be something I'm missing. Because I took checksums of the firmware files and they're the same.

plus ›