marcan changed the topic of #asahi to: Asahi Linux: porting Linux to Apple Silicon macs | Not ready for end users / self contained install yet. Soon. | General project discussion | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Topics: #asahi-dev #asahi-re #asahi-gpu #asahi-stream #asahi-offtopic | Keep things on topic | Logs: https://alx.sh/l/asahi
eroux has quit [Ping timeout: 480 seconds]
yrlf has joined #asahi
espressocookie[m] has joined #asahi
<Glanzmann>
landscape15[m]: In the old days also 'chvt 0' worked. Not sure, if it still works.
Dcow_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
eroux has joined #asahi
eroux has quit [Ping timeout: 480 seconds]
riker77_ has joined #asahi
riker77 has quit [Ping timeout: 480 seconds]
riker77_ is now known as riker77
<yrlf>
landscape15[m], Glanzmann: usually tty1 or tty7 are where the graphical desktop runs (depending on distro and/or display manager)
<yrlf>
as you said, Ctrl+Alt+F? will switch to tty? (where ? is a number)
<yrlf>
'chvt ?' also works, though I think you need to run chvt as root on some systems
eroux has joined #asahi
eroux has quit [Ping timeout: 480 seconds]
darkapex4 has joined #asahi
darkapex3 has quit [Ping timeout: 480 seconds]
<SamAdams[m]>
<espressocookie[m]> "is asahi usable yet" <- Yes and No. It's not intended for end users, but I find it very usable with Debian and if you use a window manager, it may lessen the load on the cpu. There is no SMC support, which means no power management. There is no audio or Bluetooth. Wi-Fi is working if you have a second computer and run the pcie experiment. I would wait until SMC support is finalized into the kernel, and then Wi-Fi and
<SamAdams[m]>
Power Management will be added.
<SamAdams[m]>
If you are willing to take chances and want to learn how the Linux kernel and Mac OS work under the hood, this project is great!
<SamAdams[m]>
* Yes and No. It's not intended for end users, but I find it very usable with Debian and if you use a window manager, it may lessen the load on the cpu. There is no SMC support, which means no power management. There is no audio or Bluetooth. Wi-Fi is working if you have a second computer and run the pcie experiment. I would wait until SMC support is finalized into the kernel, and then Wi-Fi and Power Management will be added.
<SamAdams[m]>
If you are willing to take chances and want to learn how the Linux kernel and Mac OS work under the hood, this project is great!
<SamAdams[m]>
In regards to YouTube. NO, don't do it. It's horrible, since there's no video acceleration at all. Cinnamon DE runs great, but YouTube is a laggy mess. Even at 360p, it just can't handle it. Modern day CPUs have accelerators that can decode and encode video and that's not present in the kernel (yet).
<tpw_rules>
youtube works fine for me
<tpw_rules>
it's pointless because there was no sound but
<tpw_rules>
nor vsync
<SamAdams[m]>
Interesting, maybe just an issue with Firefox? I tried Debian and Ubuntu, and neither one works great. I probably need to move over to Arch.
<SamAdams[m]>
Wow, the Linux kernel compiles faster now! It already is fast on the M1. Probably not coming until 5.18 or later because of the scope of the changes.
<amw>
SamAdams[m]: YouTube is fine on my MBA / debian bullseye + firefox, my kernel is using CONFIG_DRM_SIMPLEDRM=y and X pkg is xserver-xorg-video-fbdev
<amw>
0 frames dropped even at HD quality
darkapex has joined #asahi
darkapex4 has quit [Ping timeout: 480 seconds]
jkcoxson[m] has joined #asahi
darkapex1 has joined #asahi
ewrvvvvvvvvvvvvvvvvvvvvvvvvvvd has quit [Remote host closed the connection]
darkapex has quit [Ping timeout: 480 seconds]
jeffmiw has quit [Ping timeout: 480 seconds]
jeffmiw has joined #asahi
<Glanzmann>
tpw_rules: pong
<Glanzmann>
tpw_rules: About the video, if you watch in a window, its fine. If you watch fullscreen, the best results were with fbdev xorg driver (which slow for all other tasks like regular work) and using mpv -vo drm.
<Glanzmann>
But any other sound card will do. But this one supports S/PDIF if you happen to have an echo cancler you want to hook it up to.
<Glanzmann>
amw: xserver-xorg-video-fbdev is fast for videoplayback, but slow for everything else (at least for me). So I'm using the modsetting xorg driver. Which is fast for everything else but not the best for videoplayback.
<landscape15[m]>
<yrlf> "as you said, Ctrl+Alt+F? will..." <- I tried with ctrl+alt+f2 and it works. I also get full resolution (icons are small).
<Glanzmann>
xserver-xorg-video-fbdev my xterm updates less fast, scrolling in firefox is not smooth, mouse curser jumps.
<landscape15[m]>
Glanzmann: with kde plasma Firefox works very well. Also ffmpeg works good, but the mouse cursor continually lags.
vx has joined #asahi
<Glanzmann>
landscape15[m]: yeah, exactly. This is why I switched to modesetting xorg driver because it feels faster for the regular tasks. KDE uses wayland. I'm using fvwm2 which is using xorg.
ewryyyyyyyyyyyyyyyyyyyyyyyyyyd has joined #asahi
<mps>
kettenis: what you think about setting BOOT_TARGET_DEVICES to usb0 first and then nvme0? that way machine will boot from usb by default if usb disk is found and if not then boot from nvme
<mps>
this way we could 'rescue' boot in case nvme is non bootable for some reasons
<Glanzmann>
mps / tpw_rules / kettenis: Is there a write up how to do the m1n1 / uboot / grub dance, yet?
<mps>
Glanzmann: I did it simply by install grub-efi on target partition
<mps>
i.e. mount rootFS target partititon, mkdir /boot/efi on it, mount ESP under this dir, and do grub install
<mps>
if I finish my $day_job on time I will create script to do this and put m1n1+u-boot+dtb for MB PRO and MB AIR somewhere
<mps>
and maybe mini also
<mps>
btw, what is dtb file name for air
<j`ey>
j313
<mps>
j`ey: thanks
<amw>
mps: For my 2020 M1 mba it is t8103-j313
<mps>
nice, I will put ready made u-boot on my site later (if something didn't trigger NMI on me)
<amw>
Glanzmann: I'm very happy with laggy mouse and firefox - it's so fast anyway
<amw>
mps: What works in your u-boot : Wifi, keyboard ?
<kettenis>
that results in a u-boot that works on all the M1 models
<mps>
amw: didn't tested wifi in u-boot but keyboard works
<amw>
Is it possible to patch the pcie_enable_devices into m1n1 ?
<mps>
kettenis: ah, that is nice, thanks
<kettenis>
u-boot already enables the wifi
<amw>
kettenis: Great!
<Glanzmann>
amw: I'm pretty sure it is, but noone has done so or told us about doing so. However hopefully SMC will be ready and then we can have wifi without needing a second machine to boot.
<Glanzmann>
amw: I also though about doing it myself, but did not.
<Glanzmann>
kettenis: Really, does u-boot enable wifi? I did not know.
<mps>
heh, also I looked at it but decide to wait some time
<Glanzmann>
kettenis: Wow u-boot enables, wifi did not know.
<Glanzmann>
kettenis: Which tree should I use to build u-boot?
<amw>
mps: How do I tell which partition is ESP? My first partition is APFS...
<Glanzmann>
mps: Thank you, I look forward to the instructions.
<kettenis>
the dtb's end up in arch/arm/dts in the u-boot tree after you build
<mps>
amw: with fdisk you change part type to efi system
<mps>
amw: parted also and some other partition tools
<amw>
mps: So I create a new FAT32 partition and set it's GPT GUID to EFI
<amw>
Sorry ESP I mean
<mps>
amw: EFI System Partition is ESP (shorthand)
<kettenis>
that's fine, everything that's needed has been built at that point
<landscape15[m]>
Is it possible to set default root device in the Linux config (so that you don’t need to set boot-args)?
<j`ey>
landscape15[m]: CONFIG_CMDLINE
<landscape15[m]>
j`ey: thanks. For example I can set ‘CONFIG_CMDLINE=nvme0n1p4’. How do I specify ext4 fs?
<amw>
kettenis: Yep I have a arch/arm/dts/t8103-j313.dtb but I think "make DEVICE_TREE=t8103-j313" builds that and doesn't complain
<landscape15[m]>
s/‘/`/, s/’./`./
<j`ey>
landscape15[m]: thats the entire command line, not just the root
<landscape15[m]>
s/‘/```/, s/’./```./
<amw>
So more like CONFIG_CMDLINE="earlycon console=tty0 console=tty0 debug net.ifnames=0 rw root=/dev/nvme0n1p6 rootfstype=ext4" ?
<j`ey>
yes
<landscape15[m]>
But I don’t think you need console=tty0
<Glanzmann>
amw: Did you compile u-boot on the m1? Or did you crosscompile?
<kettenis>
amw: picking a specific model in the config is a bit retarded, but that's how I "fixed" it in the upstreamed bits
<amw>
Glanzmann: Yes sorry - I compiled it on the M1 - so no cross compiling for me
<kettenis>
so maybe I should fix it that way on the branch as well
<sami-dev[m]>
Hey, I realise the project is far from ready for general consumption but if you were to put it into a sentence or two. How far do you think we're off from being able to use the M1 Max macs for general web-development using linux?
<j`ey>
some months
<j`ey>
I think it's just too hard to say much beyond that. If youre ok with compiling kernels etc, probably sooner, maybe even already
<j`ey>
although chromium doesnt seem to work OOTB with 16K pages
<landscape15[m]>
sami-dev: for the end user, I hope by the end of the year. But you can do it yourself for now.
<sami-dev[m]>
Can't say I have done much of it manually. My experience with compiling such has been through AUR packages where I simply would edit some options. Either way that sounds promising
<amw>
Ok - I think the CONFIG_CMDLINE above was for Linux as u-boot seems to just have =y in the .config
<kettenis>
amw: yes
<j`ey>
amw: yes it was for linux
<landscape15[m]>
amw: also in the Linux config I can’t find it. There is a CONFIG_CMDLINE_BOOL and CONFIG_FB_CMDLINE set to yes
<j`ey>
landscape15[m]: cant find it how?
<landscape15[m]>
j`ey: manually browsing the config. Should I use menuconfig?
<j`ey>
yes
<j`ey>
the .config doesnt contain all options
<landscape15[m]>
j`ey: there are some more but are all boolean
<amw>
landscape15[m]: It's in my "Boot options" section before CONFIG_EFI_STUB=y
<j`ey>
my defconfig has CONFIG_CMDLINE="", btw
<amw>
My linux also has CONFIG_CMDLINE_FROM_BOOTLOADER=y - I assume that is harmless...
<jannau>
you can search in menuconfig with '/', on the result screen use number keys to jump directly to a specific result
<landscape15[m]>
jannau: yeah I tried but I can’t find it. Maybe I should recompile.
<jannau>
that might disable CONFIG_CMDLINE doesn't make sense to have an internal cmdline if the one from the bootloader is used
<Glanzmann>
kettenis: Regarding '10:32 < kettenis> cat m1n1.macho *.dtb u-boot-nodtb.bin > u-boot.macho' Can I use multiple dtb or my sepcific version? Do I use the dtb from u-boot or the one from the kernel compile? I assume I can only use one and that is the one from the kernel compile?
<mps>
Glanzmann: from u-boot
<mps>
those from kernel doesn't work
<Glanzmann>
mps: I see. Thanks.
<mps>
Glanzmann: you can use just one for your machine and then have to cat it
<j`ey>
landscape15[m]: in menuconfig, of linux, type / and then CMDLINE
<kettenis>
there are a few tweaks in the u-boot dtbs
<j`ey>
landscape15[m]: what happens?
<Glanzmann>
mps: I see. Thank you.
<kettenis>
but they're based on the asahi and wifi/take5 branches
<kettenis>
so they should work
<amw>
landscape15[m]: Are you compiling for x86 ? that has the CONFIG_CMDLINE_BOOL but arm64 doesn't
<landscape15[m]>
j`ey: i send a pastelink
<j`ey>
amw: i did wonder if it was something like that
<j`ey>
you always need ARCH=arm64 set
<j`ey>
even when running menuconfig
<amw>
j`ey: I was burnt by that a couple times ...
<landscape15[m]>
yeah that was the problem. Now I see a CMDLINE string
<amw>
ok - from u-boot/tools/binman/etype/u_boot_ucode.py: Contains u-boot-nodtb.bin (i.e. U-Boot without the device tree).
davidcole has joined #asahi
<amw>
So the m1n1 dtb is passed through u-boot to the linux ?
davidcole has quit []
David[m]12345678 has joined #asahi
<mps>
dtb is 'applied' by bootloader
<mps>
in 'our' case by m1n1
<amw>
Does "applied" mean patched or just passed across?
<j`ey>
amw: patched
eroux has joined #asahi
<jannau>
as400[m]: yes, the t6000 branch doesn't work yet, the change itself appears to be fine
<as400[m]>
jannau: thx.
<jannau>
I haven't spend much time looking where it breaks
<as400[m]>
jannau: asking because I'm looking at the branch at there is no t6000.dtsi.
Techcable has quit [Remote host closed the connection]
Techcable has joined #asahi
<jannau>
use the dtbs from the linux asahi branch for now
<kettenis>
I didn't import the t6000 dts files yet on that branch since it doesn't work yet
Techcable has quit [Remote host closed the connection]
Techcable has joined #asahi
psykose has left #asahi [#asahi]
eroux has quit [Ping timeout: 480 seconds]
<as400[m]>
kettenis, jannau - thank you for the info.
<mps>
jannau: in drivers/hid/hid-apple.c I see few key mapping tables. is the macbookair_fn_keys only for air or also for pro?
<mps>
thinking to try to map number keys to Fkeys with Fn key combo
<j`ey>
i think it's 'apple_fn_keys' that is used
<Glanzmann>
I did the following: Created 1 GB efi partition, changed partition table, did a mkfs.vfat mounted it to /boot/efi. Than I isntalled grub-efi package and run the intaller. I build a debian kernel package and installed it. I have no efivars partition. Than I did the cat m1n1 uboot/dtb u-boot-nodtb.bin dance and installed it from 'options' menu. I saw m1n1 flush buy and now I'm in u-boot:
<jannau>
mps: that's in flux, i currently use apple_fn_keys_spi but that's probably to change due to magic keyboard 2021 patches on the mailing list
<j`ey>
on asahi/wifi/take5 it's apple_fn_keys
eroux has quit []
<j`ey>
Glanzmann: and does /boot/efi have the bootaa64.efi?
<mps>
jannau: j`ey: thanks
<amw>
Is it ok to GPT partitions not ordered by sector? i.e. I used fdisk to add a ESP partition out of the free space just before the Mac Recovery partition and it is numbered 8 (Recovery is 7)?
<amw>
I think MacOS diskutil must re-order the partitions in the GPT?
<Glanzmann>
j`ey: Yes, I checked, its there.
<Glanzmann>
I think it has the right device which is Scanning nvme 0:6
<Glanzmann>
But than it says unable to read file.
<Glanzmann>
j`ey: The bootaa64.efi? is not directly in /boot/efi IIRC but in EFI/bootaa64.efi?
<Glanzmann>
without the question mark at the end.
<mps>
Glanzmann: yesterday I posted image with u-boot trying to boot from nvme and looks like you hit the same problem
<kettenis>
Found EFI removable media binary efi/boot/bootaa64.efi
<landscape15[m]>
Is grub installed on the EFI partition? Wouldn’t be the same to run Linux via u-boot (without grub)?This is what happens with embedded devices.
<kettenis>
landscape15[m]: what ahppens with embedded devices is retarded
<sven>
:>
<landscape15[m]>
kettenis: yeah I imagine :) this means that the end user booting from the USB drive doesn’t need to install grub in order to install Linux, because grub is already there.
<kettenis>
frankly, this is all a solved problem
<kettenis>
any decent linux distro that supports "generic" arm64 will install an EFI bootloader for you and will probably even create an EFI system partition if one doesn't already exist
<mps>
kettenis: alpine does this
<j`ey>
Glanzmann: I feel like your bootaa64.efi is at the wrong path
<j`ey>
maybe it's one level too deep?
<amw>
grub-install has --target option arm-uboot as well as arm64-efi
<kettenis>
needs to be in efi/boot/bootaa64.efi
<kettenis>
but that's on the efi system partition
<amw>
grub also has --dtb=FILE option to embed a DTB - presumably don't need that?
<Glanzmann>
j`ey / kettenis: yes, than it is in the wrong path.
<Glanzmann>
I'll correct that, try again and report back.
<kettenis>
so if you're looking at it from linux it will have the path where the esp is mounted before that
<kettenis>
amw: no need for that
<landscape15[m]>
mps: there is also an image with u-boot preinstalled
<amw>
grub-install /dev/nvme0n1p8 - isn't creating a /boot/efi/bootaa64.efi under debian bullseye?
<Glanzmann>
amw: No, it is not. See above paste. But that one is with testing.
<kettenis>
Glanzmann: no the file needs to be named efi/boot/bootaa64.efi
<Glanzmann>
kettenis: I see. So when the mount point is /boot/efi it has to be /boot/efi/efi/boot/bootaa64.efi ?
<kettenis>
yup
<Glanzmann>
Thank you.
<Glanzmann>
I'll try and report back.
<amw>
Glanzmann: Won't it also want all the other files next to it in the same directory?
<Glanzmann>
amw: Nope, if I understood kettenis correctly than the grub has everything it needs built in to get to the ext4 partition to load additional modules and config file.
<landscape15[m]>
<landscape15[m]> "yeah that was the problem. Now I..." <- Is it possible to set a “rescue” boot device in Linux config (if the nvme partition is not set up)?
<Glanzmann>
as400[m]: Where do I put this config file?
<as400[m]>
Glanzmann: on your ESP partition in /boot/extlinux/extlinux.conf
<as400[m]>
obviously you don't need fdtdir as this is passed by m1n1
<mps>
landscape15[m]: this morning I asked kettenis should we change boot_targets to use 'usb0 nvme0' instead of 'nvme0 usb0' to boot from usb first if it plugged instead of nvme, to have simple rescue option ready
<kettenis>
mps: I think that's a bad idea
<mps>
kettenis: why
<mps>
granted, it can be changed form u-boot prompt when u-boot boots
<mps>
would be easier for end users if they don't have to stop u-boot and set this manually
<mps>
s/form/from/
<dottedmag>
(ahem) autorun.inf (ahem)
<kettenis>
indeed, you don't want to accidentally boot from a random usb stick that somebody plugged into your machine
<mps>
understand (though if someone can plug usb disk on my machine and boot I'll reformat machine)
<as400[m]>
Glanzmann: where is the kernel stored ?
<as400[m]>
afaict not on ESP partition
<Glanzmann>
as400[m]: On an ext4.
<as400[m]>
That's why u-boot can't find kernel
<Glanzmann>
I see. u-boot can't read ext4.
<as400[m]>
Yes
<Glanzmann>
So I have to copy and the initrd over and than it should work?
<as400[m]>
Yes
<as400[m]>
And change extlinux.cong accordingly
<Glanzmann>
Will do so.
<mps>
I got F1 on MBP by Fn+1 key, now can switch between xorg and console
<as400[m]>
*extlinux.conf
<mps>
Glanzmann: afaik u-boot can read ext4
<Glanzmann>
as400[m]: Did I understood you correctlty that debian does support extlinux out of the box. So when I mount the esp partition as /boot and install some package it does the right thing out of the box?
<j`ey>
it can
<as400[m]>
Glanzmann: yes, you need u-boot-menu package installed
<Glanzmann>
I see, thanks.
<Glanzmann>
as400[m]: Unfortunately I get the very same error message when I copy the kernel to 'boot' on the esp partition.
<landscape15[m]>
<mps> "landscape15: this morning I..." <- It’s fair to me. But many don’t want that for security reasons. I needed this because I waste time changing the boot object every time I have to switch to USB
<as400[m]>
with proper path to kernel and initramfs
<as400[m]>
I guess in your case it will be /boot/Image and initrd=/boot/initramfs.img
<Glanzmann>
as400[m]: I checked the paths in extlinux.conf using cut and paste and they point where they should be porting to.
<Glanzmann>
I think it is something else.
<Glanzmann>
So the paths in extlinux.conf are correct if the vfat esp partition is '/'
<as400[m]>
I think so
<as400[m]>
on the last screenshot you provided, u-boot says "Device 0: unknown device" - that does not look good
<Glanzmann>
I also checked the u-boot .config and both vfat and ext4 support is compiled in and CONFIG_CMD_SYSBOOT=y which seems to be extlinux as well.
<Glanzmann>
kettenis: Did you test u-boot/nvme on the air?
jeffmiw has quit [Ping timeout: 480 seconds]
<as400[m]>
Glanzmann: can you try "nvme info" after failed boot ?
<as400[m]>
or "nvme list"
<j`ey>
Glanzmann: well its reading the .conf from the nvme
<marcan>
fwiw I just updated some docs wiki pages (boot, storage, glossary) to try to fix the 1TR confusion
<kettenis>
well, that isn't grub but the OpenBSD bootloader
<marcan>
tl;dr the last partition on disk is *not* 1TR, it's "System RecoveryOS". 1TR just means "recovery booted by holding the power button down" and it *used* to be system recovery on 11.x but is now the paired OS recovery, and both are called 1TR when booted in this way
<marcan>
if you see any mentions of the old confused terminology feel free to fix them
<kettenis>
Glanzmann: anyway, this proves there is nothing wrong with the your ESP and u-boot just works
<kettenis>
So your problem must be that you didn't properly install your grub
<kettenis>
as I said, the grubaa64.efi from the debian install iso works fine
<Glanzmann>
I agree. I'll try the grub from the debian install iso.
kit_ty_kate has quit [Ping timeout: 480 seconds]
<Glanzmann>
as400[m]: I also tried the put the exlinux.conf as simple as possible, with your three liner, same issue.
<mps>
Glanzmann: please inform me where I can download this debian iso when you test it works for you
<j`ey>
Glanzmann: as400[m] the extlinux.conf isnt being read, its erroring earlier
<Glanzmann>
That is the one that fails for me if I have it alone in there.
<Glanzmann>
kettenis: Are you on latest and greatest or still on macos 11?
<kettenis>
shouldn't matter
<kettenis>
really, at the point where you have m1n1+u-boot running any generic arm64 distro should just work
<Glanzmann>
I get it. But I'm pretty sure that at least for me on the macbook air, grub only loaded after I added the shim file to the directory.
<Glanzmann>
I write down what I did for others to reproduce.
<j`ey>
bootaa64.efi is what u-boot looks for, not grubaa64.efi
<Glanzmann>
That explains it.
<Glanzmann>
Maybe I just have to rename grub and it will work, too.
<Glanzmann>
let me try.
<Glanzmann>
j`ey: You're right. The filename matters. Thank you.
<Glanzmann>
mps: So you just need to rename grub to bootaa64.efi and than it works.
yuyichao has quit [Ping timeout: 480 seconds]
<Glanzmann>
mps: Btw. I just booted the air without a second machine using uboot, m1n1, grub and have wifi. USB-C does not work for me. Don't know why.
<Glanzmann>
Okay I shut up, usb-c works as well.
<Glanzmann>
Since u-boot can read ext4, is it necessary to use the efi partition for this? I'm the efi partition is very helpful for transfering the firmware files, but other than that?
<mps>
Glanzmann: I think what is important is partition type (efi system) and iirc filesystem could be ext4
<kettenis>
nope, that's a stupid idea
<mps>
maybe even type is not important
<mps>
kettenis: it seems stupid but once I changed type to linux and uboot found bootaa64.efi
<Glanzmann>
marcan: I have a wifi bug for you. When I open a personal hotspot on my android mobile phone and try to connect using wifi take 5 I get the following in dmesg: ieee80211 phy0: brcmf_set_sae_password: failed to set SAE password in firmware (len=8) See kern.log: https://tg.st/u/9dd13d1cccccf0cafd96267d4edc838b-kern.log
<Glanzmann>
My personal wifi hot spot uses the same ssid and psk as my wlan I'm connected right on without any issue.
<Glanzmann>
mps: The palm detection with your config does not work so good for me. The mouse curser often jumps. Do you have a solution for that or the same problem. I thought I already had a configuration where it was better out of the box. Unfortunately I deleted the install so I have no way to check.
<landscape15[m]>
In order to fix my custom kernel config (with which I don’t get USB working) I’m cloning every USB option from mps’s config throw menuconfig. Could it work?
<Glanzmann>
landscape15[m]: I sometimes also have the feeling that usb does not work.
<Glanzmann>
landscape15[m]: I'm at the moment also using mps config because I was unable to get the debian defconfig for aarch64 adopted to boot on macbook air.
<tpw_rules>
Glanzmann: pretty sure that's an either-or
<tpw_rules>
i imagine what the dpkg-reconfigure option ultimately does is invoke grub-install with --removable
<Glanzmann>
tpw_rules: Yes it is either or. But if you do it with the flag.
<Glanzmann>
And than you update grub2 it will not update it on the alternate location.
<Glanzmann>
So yes, dpkg-reconfigure should be enough. I agree, I deleted the other line.
ewryyyyyyyyyyyyyyyyyyyyyyyyyyd has quit [Remote host closed the connection]
yuyichao has joined #asahi
yuyichao_ has quit [Ping timeout: 480 seconds]
Dcow__ has joined #asahi
Dcow_ has quit [Ping timeout: 480 seconds]
mlq has joined #asahi
<mps>
Glanzmann: palm detection never worked for me on any arm chromebook/laptop
mlq_ has quit [Ping timeout: 480 seconds]
<Glanzmann>
mps: I see, good to know. :-) I solved my particular problem by telling gpg to grab the keyboard, should be the default but on Debian it doesn't seem to be.
<Glanzmann>
mps: Also for me the mouse pointer seems to jump to the borders. Sometimes when I type, does that happen for you, too?
<Glanzmann>
So it is in the middle of the screen and than suddenly jumps all the way left side?
<Glanzmann>
While I'm typing.
<Glanzmann>
Anyway, have to hit the bed know. Read your answer tomorrow. :-) Macbook Air with wifi without second machine is really nice. :-)
<mps>
Glanzmann: didn't noticed jumping of pointer, maybe because I use st term with patch which hide pointer when starting to type
<mps>
but I never noticed jumping of it around without touching touchpad
<mps>
Glanzmann: yes, also mb pro, only waiting for sound card fix
joske has joined #asahi
<joske>
thx all, I also got my air booting all the way into linux :-)
<joske>
grub-install --removable was the final trick
<mps>
joske: which distro
<joske>
manjaro mate edition
<mps>
manjaro is arch linux based?
<joske>
yes
jeffmiw has joined #asahi
___nick___ has quit [Ping timeout: 480 seconds]
off^ has joined #asahi
joske has quit [Remote host closed the connection]
Dcow__ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Dcow_ has joined #asahi
yuyichao_ has joined #asahi
yuyichao has quit [Ping timeout: 480 seconds]
<mps>
jannau: what you think about this patch to have Fkeys on MB PRO https://tpaste.us/Bgyy is it worth to be added
<mps>
works fine on my machine
yuyichao has joined #asahi
yuyichao_ has quit [Ping timeout: 480 seconds]
<chengsun>
VinDuv: thanks for your instructions on how to get /dev/cu.debug-console on macOS 12
<chengsun>
I had to tweak it a little bit to get it working for me: /Library/KernelCollections was read-only (extended attr I think), so I dumped kc.noshim.macho into ~ instead