#
✕ nick:JMR2
#asahi · 2022-02-06 18:25
jmr2With all due respect, I'd encourage you to read a bit on how to build a linux kernel. This is nothing asahi-specific.
#asahi · 2022-02-06 18:24
jmr2caleb010[m]: it's a graphical tool to edit your kernel .config file.
#asahi · 2022-02-06 18:20
jmr2caleb010[m]: no.
#asahi · 2022-02-06 18:16
jmr2landscape15[m]; because it's one more operation, because I don't have access to the rootfs from my development machine, and because it can cause weird bugs if for some reasons, your kernel image become un-synchronized with the modules.
#asahi · 2022-02-06 18:14
jmr2It'll use more RAM, since everything will be loaded from the get-go, instead of on-demand.
#asahi · 2022-02-06 18:11
jmr2caleb010[m]: go back to "make menuconfig", and in the main page, disable "Enable loadable module support". Everything defined as to be built as a module will become built-in. Less memory efficient, but much simpler to manage.
#asahi · 2022-02-06 01:30
jmr2(and typo: only one R in Corellium)
#asahi · 2022-02-06 01:28
jmr2jeffmiw: you seem to have a mix of tabs & spaces in your files. Depending on the editor, the alignments are wrong.
#asahi · 2022-02-06 01:27
jmr2jeffmiw: Thanks for sharing. Good to see another area making progress.
#asahi · 2022-02-04 00:02
jmr2jeffmiw: are you starting from scratch, or from Corellium's ?
#asahi · 2022-02-01 16:37
jmr2Glanzmann: yes, I saw something similar elsewhere. But Catalina can't be installed on M1 Macs.
#asahi · 2022-02-01 16:18
jmr2Possible cause: macOS 12.3 beta.
#asahi · 2022-02-01 16:18
jmr2It's not - just switching to a different stub works, and switching back to the "problematic" one on the next occurence works also.
#asahi · 2022-02-01 16:18
jmr2For info, I now have 20-40% of my startups (both cold boot and restart) that fail with a message from recovery that says "The version of macOS on the selected disk needs to be reinstalled".
#asahi · 2022-01-30 19:05
jmr2landscape15[m]: you could probably just copy the DT nodes from the T6000 to the T8103 and read the info from dmesg... but that's definitely not risk-free.
#asahi · 2022-01-30 03:40
jmr2Thanks. Never heard of it.
#asahi · 2022-01-30 03:39
jmr2What was the "new" breakage you recently reported?
#asahi · 2022-01-30 03:39
jmr2I think you're just seeing less memory alloc/dealloc, and possibly better cache performance.
#asahi · 2022-01-30 03:36
jmr2feels like I'm doing the LinuxFromScratch install that I always wanted to do but never found the time to :-D
#asahi · 2022-01-30 00:47
jmr2In the end, installing grub is three commands: apt-get install grub-efi grub-efi-arm64-signed- ; grub-install --target=arm64-efi --efi-directory=/boot/efi --removable ; update-grub
#asahi · 2022-01-30 00:47
jmr22) I couldn't get dpkg-reconfigure grub-efi-arm64 to install grub. I ended up using mps's --efi-directory instead of your --removable, since it uses a path instead of a device - less risky.
#asahi · 2022-01-30 00:46
jmr2Two comments: 1) instead of deleting fbaa64.efi (I still have it without ill effects), you can uninstall grub-efi-arm64-signed and its dependencies.
#asahi · 2022-01-30 00:46
jmr2Glanzmann: thanks for your various documents. I just tether-booted the whole chain for the first time, and it's quite fun to watch.
#asahi · 2022-01-28 23:37
jmr2dwc3 502280000.usb: wakeup failed --> -22
#asahi · 2022-01-28 23:37
jmr2dwc3 502280000.usb: failed to send remote wakeup
#asahi · 2022-01-28 23:36
jmr2Anyone else seeing these one in a while in dmesg ? Related to https://github.com/AsahiLinux/m1n1/issues/101 ?
#asahi · 2022-01-26 12:51
jmr2Ah. OK.
#asahi · 2022-01-26 12:49
jmr2It already is easy. If you start fresh with the installer, you don't need a USB key. Just a tethered boot, with a custom kernel with no modules, and the initrd. I don't even have a bootargs in that case.
#asahi · 2022-01-26 12:46
jmr2That seems like a lot of trouble...
#asahi · 2022-01-26 12:45
jmr2OK. Can't help you there. In my eyes, you run d-i way before grub is in the equation. I'd only install uboot & grub in a second tethered boot, using the rootfs created by d-i.
#asahi · 2022-01-26 12:41
jmr2I'm... not sure why you're talking about grub.cfg. Do you have grub in the boot sequence for the installer ?
#asahi · 2022-01-26 12:39
jmr2Glanzmann: strange... For me, the fn-ctrl-option- thing works from the very start - I switched even before answering the "language" question. And I know there's at least three. The number might depend on the kernel config.
#asahi · 2022-01-26 12:28
jmr2Glanzmann: to answer your question, I don't know how to start the initrd installer in expert mode, so no. No issue switching terminals (ok, yes, the key sequence is cumbersome - fn-ctrl-option-fX), I didn't have a need for job control, just used more terminals as needed, but basically, it's two commands - nano, then wpa_supplicant.
#asahi · 2022-01-26 12:24
jmr2That's... politics :-D You won't get me there.
#asahi · 2022-01-26 12:23
jmr2chadmed: ... which you don't care about while you're running the installer.
#asahi · 2022-01-26 12:22
jmr2And given that I don't plan to use wpa_supplicant after install, I didn't bother to list more than the network I used for the test. If I wanted too, I'd redo it with better tools once the install was complete.
#asahi · 2022-01-26 12:21
jmr2only the network={} block, with ssid, key_mgmt and psk keys inside. Not 100% sure for scan_ssid.
#asahi · 2022-01-26 12:20
jmr2More seriously, that "ctrl_interface" line wasn't needed for me.
#asahi · 2022-01-26 12:19
jmr2Glanzmann: that "wheel" group thing: you're in the "example" section of the man page. Are you going to report that 'ssid="home"' is wrong too? ;-)
#asahi · 2022-01-26 08:34
jmr2Glanzmann: same here. Just switch to a different terminal, create the ~5 lines conf file (see the first example in man wpa_supplicant.conf), start wpa_supplicant, and continue with the install.
#asahi · 2022-01-26 04:23
jmr2Yup, concatenating the initrd works, and the d-i one contains wpa-supplicant. So using the d-i image to install over wireless works. Cool.
#asahi · 2022-01-26 01:25
jmr2Also, but for people installing over wifi (I didn't) and needing firmwares, it seems that multiple initrd can be just concatenated: https://wiki.debian.org/DebianInstaller/NetbootFirmware
#asahi · 2022-01-26 01:25
jmr2Details: https://bugs.debian.org/998668 and https://salsa.debian.org/installer-team/anna/-/commit/736553754b075660d6926fea99e529bcc4ffae51
#asahi · 2022-01-26 01:25
jmr2Daily initrd for Testing (bookworm): https://d-i.debian.org/daily-images/arm64/20220125-02:20/netboot/debian-installer/arm64/ I only used it for install, not for partitionning or anything related to grub.
#asahi · 2022-01-26 01:25
jmr2Followup to the Jan. 17 discussion on the "no kernel modules found" error running the initrd version of the debian installer: not sure if this has been posted already, but the d-i daily builds work fine.
#asahi · 2022-01-24 23:40
jmr2Easy way to check your stub OS version, through MacOS: System Preferences -> Startup Disk.
#asahi · 2022-01-23 23:00
jmr2Agreed. First time I'm running the beta, so I had the same confusion.
#asahi · 2022-01-23 22:46
jmr2jannau: 12.2 ReleaseCandidate is available if you're running the beta. Once installed, the about box looks like an official release. If you're not running the beta, it's not available yet.
#asahi · 2022-01-20 19:10
jmr2(FWIW, I did almost all my installs so far from MacOS, not from RecoveryOS. In that context, you can just relock the lock and wait ~10s, without clicking on restart, and the installer detects the change. Might be a way to avoid the race condition in recoveryOS.)
#asahi · 2022-01-20 19:04
jmr2Thanks :-)

plus ›