21:32 < Cy8aer[m]> Glanzmann: Ok, brute force: Try: `DEBIAN_FRONTEND=gtk` - sic

[m1-debian] / doc / notes.txt

diff --git a/doc/notes.txt b/doc/notes.txt
index ccddce8694cae82c07d93fd7d6564509e12c4d54..955a998f30f61316b3c63eee8630392d99c1a801 100644 (file)
--- a/doc/notes.txt
+++ b/doc/notes.txt
@@ -21,6 +21,7 @@ Chromium 16KB patch: https://tg.st/u/Set-kernal-page-size-to-16K-on-loongson-MIP
 15:26 < tpw_rules> Glanzmann: https://pastebin.com/NzJEQJDW - https://tg.st/u/NzJEQJDW
 15:26 < tpw_rules> last i checked the built chromium only worked with the flags --in-process-gpu --no-sandbox --no-zygote but that may have been a kernel config problem
 Upstream BUG: https://bugs.webkit.org/show_bug.cgi?id=236564
 15:26 < tpw_rules> Glanzmann: https://pastebin.com/NzJEQJDW - https://tg.st/u/NzJEQJDW
 15:26 < tpw_rules> last i checked the built chromium only worked with the flags --in-process-gpu --no-sandbox --no-zygote but that may have been a kernel config problem
 Upstream BUG: https://bugs.webkit.org/show_bug.cgi?id=236564

+16:21 < tpw_rules> https://bugs.chromium.org/p/chromium/issues/detail?id=1301788

 
 22:39 < jannau> `dtc -I fs -O dts -o - /proc/device-tree` will output the device-tree as seen by linux
 
 
 22:39 < jannau> `dtc -I fs -O dts -o - /proc/device-tree` will output the device-tree as seen by linux
 


@@ -191,6 +192,8 @@ exec /bin/bash
 21:56 < povik> that mode of playing in parallel through the speakers and jack has a defect
 21:57 < povik> there's noise mixed-in then, at a period
 21:57 < povik> don't know how that happens yet
 21:56 < povik> that mode of playing in parallel through the speakers and jack has a defect
 21:57 < povik> there's noise mixed-in then, at a period
 21:57 < povik> don't know how that happens yet

+When disabling the speakers, run rm -rf ~/.config/pulse/ and reboot otherwise the jack will be in the future off or 100% (which is too loud).
+

 
 If you see this in Xorg.0.log, it means that simpledrm has not initialized.
 ...
 
 If you see this in Xorg.0.log, it means that simpledrm has not initialized.
 ...


@@ -396,10 +399,20 @@ ctl.!default {
 
 16:43 < povik> marcan: two fixes on top of 'asahi' that should make it into the release: https://github.com/povik/linux/commits/asahi-fixes
 
 
 16:43 < povik> marcan: two fixes on top of 'asahi' that should make it into the release: https://github.com/povik/linux/commits/asahi-fixes
 

-# Manually install m1n1 in chainloading mode:

 # boot into 1tr
 diskutil list
 diskutil info <identifier of esp>
 curl -sLo tg.st/u/m1n1-rust.bin
 # boot into 1tr
 diskutil list
 diskutil info <identifier of esp>
 curl -sLo tg.st/u/m1n1-rust.bin

-cat m1n1-rust.bin <(echo 'chainload=<Partition UUID>;m1n1/boot.bin') > object.bin
+cat m1n1-rust.bin <(echo 'chainload=<ESP Partition UUID>;m1n1/boot.bin') <(echo 'chosen.asahi,efi-system-partition=<ESP Parition UUID>') > object.bin

 kmutil configure-boot -c object.bin --raw --entry-point 2048 --lowest-virtual-address 0 -v /Volumes/Linux
 kmutil configure-boot -c object.bin --raw --entry-point 2048 --lowest-virtual-address 0 -v /Volumes/Linux

+
+20:29 < Glanzmann> One question though what is difference between chosen.asahi,efi-system-partition=EFI-PARTITION-PARTUUID and chainload=EFI-PARTITION-PARTUUID;m1n1/boot.bin?
+20:30 < jannau> chainload tell's the 1st stage m1n1 from where to load the second stage
+20:31 < jannau> chosen.asahi,efi-system-partition is added to the dt mostly to allow u-boot to boot from the correct ESP
+20:32 < Glanzmann> I see. Thank you for the elaboration.
+20:32 < jannau> chosen.asahi,efi-system-partition is passed from the 1st stage forward to the second stage
+20:33 < Glanzmann> I see, so the first stage informs the second stage about the uuid of the esp partition which is than passed using dt to u-boot which can than select the right esp to select the efi binary.
+
+17:25 < Jamie[m]1> I had a dumb idea and had to implement it: using http range requests and DEFLATE trickery to download Wifi firmware from Apple's CDN with only 18MB of transfer (out of a 13GB ipsw) http://github.com/JJJollyjim/firmware-abomination
+
+23:23 <@jannau> Glanzmann: on the mini vram can fit 5.5 million pixels, would be good for 3440x1600 or 3840x1433 at 32bpp