marcan changed the topic of #asahi to: Asahi Linux: porting Linux to Apple Silicon macs | 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
kgarrington has joined #asahi
kgarrington has quit [Remote host closed the connection]
<j`ey>
NightRaven[m]: you need to install the cross compiler
<NightRaven[m]>
oh ok
<j`ey>
Jamie[m]1: I should probably fix my stuff to use it, rather that use CONFIG_CMDLINE
<mps>
ah, I thought that for hypervisor it is possible to set cdmline in python script
<Jamie[m]1>
mps: there’s an option for it but they seem to be ignored
<j`ey>
Jamie[m]1: they get passed to the hv
<mps>
aha
<j`ey>
not the guest
<Jamie[m]1>
ah nice
<NightRaven[m]>
j`ey: how do you install a cross compiler
<NightRaven[m]>
* cross compiler on mac
<j`ey>
NightRaven[m]: with your package manager
<j`ey>
NightRaven[m]: we told you not to compile on a mac
<j`ey>
make a vm or something
<NightRaven[m]>
j`ey: i am going to compile the kernel on my rpi then transfer the Image.gz to my m1
<NightRaven[m]>
and do the cat m1n1.macho <(echo 'boot-args=root=PARTUUID=3d20affd-c082-421b-a111-f5d6b1587fe4 rootwait') nk.gz nk-t8103-j293.dtb > ../nk.macho
<Jamie[m]1>
in that case you don’t need a cross compiler, adding the pi is aarch64
<Jamie[m]1>
s/adding/assuming/
<mps>
compiling kernel on rpi will take time
<NightRaven[m]>
mps: that is fine
<mps>
especially if the filesystem is on mmc
<NightRaven[m]>
but i am not sure how i can install a cross compiler on rpi
<mps>
NightRaven[m]: if you install arm64 distro on rpi you don't need cross compiler
<NightRaven[m]>
yea i do have it and i get that error
<Jamie[m]1>
right, so remove the toolchain prefix variable from before your make command
<j`ey>
NightRaven[m]: do you have gcc at all?
<NightRaven[m]>
j`ey: i do
<j`ey>
as Jamie[m]1 said try remove the CROSS_COMPILE var
<NightRaven[m]>
j`ey: ok i removed it
<Jamie[m]1>
now press enter :P
<NightRaven[m]>
it still building
<zimsneexh>
Wont it take forever to build the kernel on RPi? A VM on the Mac would be alot faster
hendry1 has quit []
hendry has joined #asahi
<Jamie[m]1>
on that note, has anyone else had kernel panics when trying to run VMs from macos, or is that just a me problem? :P
<Jamie[m]1>
(xnu kernel panic, not guest linux kernel panic)
<zimsneexh>
hm, haven't had that. Parallels is just fine for me.
<Jamie[m]1>
(M1 pro on 12.0.1, UTM from App Store with default settings and a nixos aarch64 sd card image)
<NightRaven[m]>
<zimsneexh> "Wont it take forever to build..." <- i am not sure
<NightRaven[m]>
it is at this part ```CC crypto/rsa.o
<NightRaven[m]>
CC crypto/rsa_helper.o```
<zimsneexh>
I guess if it's a Pi4 it'll be fine
<Jamie[m]1>
pi4 is still SD right, it doesn't have a fast EMMC or anything?
<zimsneexh>
yep, SD
<j`ey>
my build is about 20mins, from scratch, but its very trimmed down
<psykose>
it has fast usb if you add one
<NightRaven[m]>
it just an sd card
aleasto has joined #asahi
riker77 has joined #asahi
<marcan>
Jamie[m]1: the hypervisor does not boot linux directly, it boots m1n1 which boots linux
<marcan>
the commandline arguments specified in run_guest.py are *xnu bootargs*, not Linux args
<marcan>
m1n1 does not attempt to pass through any of those to Linux
<Jamie[m]1>
yeah gotcha, that was my assumption based on the usage example
<marcan>
they are useful when booting macOS under the HV :)
<Jamie[m]1>
hmm gotcha has different meaning elsewhere doesn't it haha
<Jamie[m]1>
I meant "got you", "I understand you" :P
<marcan>
yeah, I gotcha :p
<mps>
NightRaven[m]: if you have usb ssd disk you can use it on rpi, build will a lot faster
<mps>
anyone have u-boot working? I had it about 10 days ago and now can't make it to boot
<mps>
I mean, on mb pro 2020, j293
<kettenis>
still works for me on j293
<mps>
kettenis: this is how I creare it: cat m1n1.macho u-boot/arch/arm/dts/t8103-j293.dtb u-boot/u-boot-nodtb.bin > u-boot.macho
<mps>
create*
<mps>
on boot it says something about bad fdt
<kettenis>
I am booting u-boot through linux.py
<mps>
ah
<kettenis>
there have been subtle breakages because of changes in m1n1
<marcan>
linux.py *should* be roughly equivalent to the cat method, but I can't say there aren't any bugs
<marcan>
you can test it by chainloading the appending m1n1 instead of using linux.py
<marcan>
*appended
<mps>
marcan: I'm doing this way, don't use linux.py
<marcan>
we did have that breaking change about requiring a compatible DT, but that shouldn't be the problem here
<sven>
i've been using linux.py up until ~two weeks ago or so when i updated my macbook air monterey. back then it still worked
<mps>
I will try with some of previous m1n1 commits
<marcan>
I doubt anything recent in m1n1 caused it
<kettenis>
also, I'm exclusively using "my" t8103-j293.dtb, not the one from the asihi Linux branch
<kettenis>
things are converging, but there are still subtle differences
BlitzWorks has joined #asahi
<mps>
kettenis: you mean t8103-j293.dtb in u-boot apple-m1-m1n1-nvme branch
<kettenis>
the one built from that, yes
<kettenis>
it gets built in arch/arm/dts
darkapex2 has joined #asahi
<mps>
yes, that one I concatenate to u-boot.macho
darkapex1 has quit [Ping timeout: 480 seconds]
darkapex3 has joined #asahi
riker77 has quit [Quit: Quitting IRC - gone for good...]
<NightRaven[m]>
CC [M] drivers/gpu/drm/nouveau/nvkm/subdev/timer/gk20a.o i am at this part
<NightRaven[m]>
how much left
<NightRaven[m]>
is there a prebuilt image.gz i can get
<NightRaven[m]>
`warning: An error occurred while redirecting file 'boot-args=root=PARTUUID=3d20affd-c082-421b-a111-f5d6b1587fe4 rootwait'
<NightRaven[m]>
open: No such file or directory`
<NightRaven[m]>
but it show's this
<NightRaven[m]>
can i remove that
<mps>
I see that you have '.gz'
<NightRaven[m]>
Image.gz
<NightRaven[m]>
ya
<mps>
are you sure have this file
<NightRaven[m]>
yep
<NightRaven[m]>
do i remove `echo 'boot-args=root=PARTUUID=3d20affd-c082-421b-a111-f5d6b1587fe4 rootwait'`
<j`ey>
NightRaven[m]: what shell / machine are you running this on?
<mps>
yes, shell looks suspicious
<NightRaven[m]>
so the shell if fish but the machine is my rpi running manjaro
<mps>
use ash or bash
<NightRaven[m]>
ok
<NightRaven[m]>
ok done
<NightRaven[m]>
but i changed .dtb to .dts
<NightRaven[m]>
since there was no .dtb
<j`ey>
that doesnt work
<NightRaven[m]>
but there is not .dtb in the root directorty
<mps>
you can't use dts, it is source from which dtb is compiled
<j`ey>
NightRaven[m]: you need to run that make command in the linux dir and put 'dtbs' at the end, then it should just build the dtbs
<NightRaven[m]>
s/directorty/directory/
<NightRaven[m]>
ohhh ok
<NightRaven[m]>
ty
<mps>
make dtbs
<j`ey>
not just that ^, you nee ARCH and whatever set still
<mps>
if it run it on aarch64 then ARCH is not needed
<NightRaven[m]>
ok so i tried booting and the kernel failed it said
<NightRaven[m]>
it booted me back to recovery mode any idea ?
slicey has quit [Quit: zzz]
<j`ey>
that's too little info!
<NightRaven[m]>
then how can i show how it failed it just kept glitching and then it said kernel failed to laid and it gave me an option to restart or go back to recovery mode
<NightRaven[m]>
But when I combine image.gz and the keyboard thing then it breaka
<NightRaven[m]>
s/breaka/breaks/
<mps>
kettenis: marcan: I found what is my problem with u-boot, and why it stopped to work. it doesn't find proper partition with grub and it stops. so no problem with m1n1
<NightRaven[m]>
so when i run `make ARCH=arm64 -j8 Image dtbs` i get this `make: *** [Makefile:1477: dtbs] Error 2`
<j`ey>
sorry but, if you see this error: "make[2]: *** No rule to make target 'arch/arm64/boot/dts/apple/t8103-j293.dtb', needed by '__build'. Stop.
<j`ey>
"
<j`ey>
you should probably realise it's related to a file you randomly moved
<NightRaven[m]>
so i can do ```cat m1n1.macho <(echo 'boot-args=root=PARTUUID=3d20affd-c082-421b-a111-f5d6b1587fe4 rootwait') nk.gz nk-t8103-j293.dtb > ../nk.macho```
<j`ey>
I'm willing to help, but at a certain point you have to help yourself
<NightRaven[m]>
oops sorry i did not read it probably i thought the bulid will generate it
<j`ey>
yes but it geneerates it from that .dts file
<NightRaven[m]>
oh ok sorry
<NightRaven[m]>
the image.gz is right but what if i don't put ```echo 'boot-args=root=PARTUUID=3d20affd-c082-421b-a111-f5d6b1587fe4 rootwait``` this in
<j`ey>
it's unlikely that is the issue, but you can try remove it, to get it minimally working
<NightRaven[m]>
hmm ok i will only put the image.gz in and the .dtb
riker77 has quit [Quit: Quitting IRC - gone for good...]
riker77 has joined #asahi
<NightRaven[m]>
i am going to build linux again on ubuntu
<j`ey>
open .config to verify CONFIG_FB_SIMPLE was set
<zimsneexh>
Are you trying to build the asahi branch? Keyboard wont work, then. Right?
<NightRaven[m]>
<j`ey> "open .config to verify CONFIG_FB..." <- it is
<NightRaven[m]>
but like it is supposed to build it it worked on my raspberry pi
<NightRaven[m]>
but on my ubuntu vm it is not
<steev>
neither of those commands builds the kernel, one creates the .config, one modifies it. you attempt to "cd .config" but .config is a file, not a directory
<NightRaven[m]>
i thought ```make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- defconfig``` build its
<j`ey>
NightRaven[m]: no, that makes the config
<NightRaven[m]>
ohh ok
<NightRaven[m]>
ok so when i do make i get an openssl error but i have openssl installed
<j`ey>
NightRaven[m]: you can probably google that one
<NightRaven[m]>
it is libssl-dev
<NightRaven[m]>
but ubuntu has to have that
<NightRaven[m]>
```"cat m1n1.macho <(echo 'boot-args=root=PARTUUID=3d20affd-c082-421b-a111-f5d6b1587fe4 rootwait') nk.gz nk-t8103-j293.dtb > ../nk.macho``` instead of this can i use this ```$ cat build/m1n1.macho Image.gz build/dtb/apple-j274.dtb initramfs.cpio.gz > m1n1-payload.macho``` and how can i get initramfs.cpio.gz i already have the .dtb file and Image.gz file
<j`ey>
it has no kernel args and no rootfs, so it just panics
<NightRaven[m]>
Ok but how can I get rootFS working on a usb and what kernel args
<j`ey>
I think Glanzmann sent some instructions, you could look into those
<NightRaven[m]>
Glanzmann: so to create a rootFS USB do I have to format the drive to ext and copy everything in / and put it into the USB
<zimsneexh>
you download the rootfs tar, extract it with bsdtar to preserve permissions (i' and
<zimsneexh>
set it as rootfs in kernel params
<zimsneexh>
hit enter to soon :P
<NightRaven[m]>
<zimsneexh> "you download the rootfs tar..." <- Ok sorry I am a noob at linux but how do you get rootFS.tar and then put it in kernel params
<zimsneexh>
like j`ey said, Glanzmann sent some instructions. Did you look at those?
<NightRaven[m]>
I can't find it i went up and I only see the mkfs.ext4
<NightRaven[m]>
Oh ok I will extract that to my USB
<zimsneexh>
careful to preserve permissions when extracting that
<NightRaven[m]>
Just sudo
<NightRaven[m]>
For root
<NightRaven[m]>
i have a question when i extract the rootfs can the FAT
<NightRaven[m]>
or does it have to be ext4
<zimsneexh>
no, ext4
<NightRaven[m]>
hmm ok
<NightRaven[m]>
btw
<NightRaven[m]>
if i want to move all the files from tmpdir so i do sudo mv * /mnt/DRIVENAME or do i just leave tmpdir as a folder and move it to DRIVENAME
jmr2 has joined #asahi
dsrt^ has quit [Remote host closed the connection]
<jmr2>
I... wasn't expecting to see the nor flash nodes appear in the DT. Did I miss something?
<j`ey>
jmr2: spi driver stream
<jmr2>
I haven't had the time to fully watch it yet, but I thought that all SPI tests would happen with the keyboard, given the extra risks with the nor flash.
<j`ey>
jmr2: not such a big deal when you have 6 machines :P
<j`ey>
(and marcan thinks DFU restore would be fine anyway..)
<jmr2>
True. But jannau's tree now has it too, and not all users of that tree are that savvy.
<jmr2>
Anyway, thanks. I should spend more time watching the streams and less asking questions :-D
<j`ey>
jmr2: yeah probably a good idea for it to be disabled by default
<NightRaven[m]>
so i have a question i have the tempdir folder do i just move the tempdir folder to the usb that has ext4 or do i move everything in the folder to the usb and if i have to move everything in tempdir then how do i do it since i have tried to do sudo mv * /mnt/DIskname since it won't move dev
linearcannon has quit [Read error: Connection reset by peer]
jmr2 has quit [Quit: Page closed]
<jannau>
jmr2: it's in AsahiLinux:linux/asahi, I haven't really thought about about it
<zimsneexh>
Anyone managed to get firefox to work without changing to fbdev?
<NightRaven[m]>
i already have a macho file with kernel and the .dtb file
<NightRaven[m]>
zimsneexh: and it panics since there is not rootfs
<NightRaven[m]>
so if i plug in the and run the .macho file again will it work or do i have to add some params to do it ?
<Glanzmann>
NightRaven[m]: If you create a new macho file, you have to boot in 1tr again by holding the power button key long and bless it using kmutil configure-boot -c m1n1.macho -C -v /Volumes/Linux
<Glanzmann>
NightRaven[m]: So what did you manage so far? Are you able to boot to the usb stick already?
<NightRaven[m]>
Glanzmann: "/Volumes/MyUSB"
<NightRaven[m]>
right ?
<Glanzmann>
Nope.
<Glanzmann>
We want Linux to boot from usb.
<NightRaven[m]>
but there is nothing in /Volumes/Linux
<Glanzmann>
NightRaven[m]: I thought about making a video showing all the steps.
<Glanzmann>
But in order to prepare the usb stick you have to do the following from a __linux__ machine:
<NightRaven[m]>
Glanzmann: which i do have
<NightRaven[m]>
Glanzmann: but /Volumes/Linux has nothing right ?
<NightRaven[m]>
* has nothing in it right ?
<Glanzmann>
So you created an ext4 fs on a usb stick and extracted the rootfs?
<NightRaven[m]>
Glanzmann: yes
<Glanzmann>
Perfect.
<NightRaven[m]>
and i made a macho file with the kernel in it and the .dtb file
<Glanzmann>
have you managed to boot a Linux kernel with the usb stick as root?
<NightRaven[m]>
Glanzmann: No
<NightRaven[m]>
not with the usb stick
<NightRaven[m]>
that is what i am stuck on
nabaiste^ has joined #asahi
<NightRaven[m]>
i have not made the /Volumes/Linux Yet
<NightRaven[m]>
Glanzmann: does there have to be anything in /Volumes/Linux
<j`ey>
NightRaven[m]: btw you wont have internet
<NightRaven[m]>
ohh no internet driver right ?
<NightRaven[m]>
j`ey: for now that is fine
<NightRaven[m]>
i just want arch working
<Glanzmann>
NightRaven[m]: forget about /Volumes/Linux that is not a thing.
<Glanzmann>
NightRaven[m]: Have you managed to install m1n1 on the mac?
<NightRaven[m]>
<NightRaven[m]> "PXL_20211211_155426605.jpg" <- as i have said i have gotten it working but it is not permanently installed and it panics since no rootfs
<NightRaven[m]>
Glanzmann: but my question is how can i get rootfs working with m1n1.macho
<NightRaven[m]>
the macho has the kernel and the .dtb
<Glanzmann>
Okay good. Now you have to build another one and specify as kernel command line: net.ifnames=0 rw root=/dev/sda rootwait rootfstype=ext4
<Glanzmann>
NightRaven[m]: You did not put a partition table on the usb stick, right? And you did a tar -xf of the rootfs on the usb stick and you can see the usual directories like etc lib usr etc on the usb stick?
<NightRaven[m]>
so this ```cat m1n1.macho <(echo 'net.ifnames=0 rw root=/dev/sda rootwait rootfstype=ext4') > m1n12.macho``` m1n1.macho is the one with the kernel and the .dtb file
<NightRaven[m]>
Glanzmann: yep
<NightRaven[m]>
NightRaven[m]: is this right
<Glanzmann>
Nope, the syntax is different.
<NightRaven[m]>
can you show it please
<NightRaven[m]>
?
<Glanzmann>
Forget about the chroot for now.
<NightRaven[m]>
i already did that
<NightRaven[m]>
Glanzmann: i already set the root password
<Glanzmann>
Perfect.
<NightRaven[m]>
so that is gone
<Glanzmann>
Okay than we need the right syntax.
<NightRaven[m]>
but what is the correct sysntax for this ```cat m1n1.macho <(echo 'net.ifnames=0 rw root=/dev/sda rootwait rootfstype=ext4') > m1n12.macho```
<Glanzmann>
No, it is not.
<Glanzmann>
I wrote it yo yesterday. Give me one second I search it again.
<Glanzmann>
That is the right syntax. m1n1.macho is the m1n1, Image.gz is the kernel model.dtb is the dtb for your notebook.
<NightRaven[m]>
yep
<Glanzmann>
Than you have to boot in 1tr (one true recovery) on your macbook and run: kmutil configure-boot -c nr.macho -C -v /Volumes/Linux
<NightRaven[m]>
Glanzmann: but i do not have /Volumes/Linux
<Glanzmann>
You need to transfer the nr.macho somehow maybe using a webserver.
<NightRaven[m]>
Glanzmann: i have that
<NightRaven[m]>
do not worry
<Glanzmann>
NightRaven[m]: The /Volumes/Linux or however you called it is just a stub partition that is necessary to kick off the bootloader (m1n1 which than loads the kernel, sets the kernel command line and boots).
<NightRaven[m]>
Glanzmann: but i do /Volumes/Macintosh HD
<Glanzmann>
NightRaven[m]: Than you're done. You have installed Linux. However. If you want to boot linux without the usb stick.
<Glanzmann>
Again you need to boot to 1tr.
<NightRaven[m]>
Glanzmann: yea
<Glanzmann>
Have you created a dos partition on macos which you can later use to put linux on?
<NightRaven[m]>
Glanzmann: nope not yet
<Glanzmann>
NightRaven[m]: I'll probably record all the steps from scratch in a video and talk a little bit while I'm doing it so that it is easier for others to follow the steps.
<NightRaven[m]>
hmm ok just give me a ping when you do it : )
<Glanzmann>
NightRaven[m]: You should do that as well while you're in macos so that once you managed to boot from the the usb stick that you can copy the files over.
<NightRaven[m]>
for now i will boot into the usb too see if it works
<NightRaven[m]>
then i will do it
<Glanzmann>
do that.
<Glanzmann>
Once you managed to boot from the usb stick you're mostly done.
<NightRaven[m]>
ok i will create one
<Glanzmann>
You just need to create the partition, format it with ext4, copy the content over without screwing up the permissions and change the kernel command line again.
<NightRaven[m]>
hmm ok
<Glanzmann>
Than, since you're on a laptop you also need to do the wifi firmware dance, or us a usb network adapter. for the start use a usb network adapter.
<NightRaven[m]>
Glanzmann: might try to get the wifi firmware
<NightRaven[m]>
i have no usb adapter
<Glanzmann>
Buy one.
<NightRaven[m]>
hmm ok
<Glanzmann>
Buy one with a wifi card and 3 usb a ports.
<NightRaven[m]>
any good ones on amazon you can recommend
<Glanzmann>
Yes, one second.
<sven>
fwiw, this will all be done automatically in the installer once we are actually ready for a end user release
<Glanzmann>
kettenis: Is there a howto for using uboot in order to load m1n1 and kernel?
<Glanzmann>
zimsneexh: I'll install Linux on my macbook air later tonight and will work for a few days with it. Let you know how it goes for me.
<zimsneexh>
Glanzmann: I've been messing with it today and yesterday and with sway it's quite usable actually
<zimsneexh>
apart from the wifi not working and my only usb-wifi dongles driver not building on aarch64
<kettenis>
Glanzmann: u-boot can't load m1n1; it's the other way around (you use u-boot as a payload for m1n1)
sproede[m] has joined #asahi
<mps>
Glanzmann: today I tested u-boot, it works on mb pro 2020, j293
<jannau>
zimsneexh: kind of known although I think I say corrupted packet messages (ignore the first). dmesg might have at the top a git hash
<mps>
Glanzmann: tested with usb stick, kernel boots fine but have to use usb keyboard because internal one doesn't work
<zimsneexh>
jannau: Yep, the kernel is from apple-m1-exp_v5.16-rc4_1-keyboard
<zimsneexh>
Just happened for a second time just now
<kettenis>
the idea is that you use an EFI bootloader (like grub) with u-boot
<kettenis>
then you can load your kernel from any device supported by u-boot (and any filesystem supported by grub)
<kettenis>
the same way as you do on an x86 system
<mps>
kettenis: yes, looks like plain u-boot doesn't work
aidenfoxivey has quit [Quit: aidenfoxivey]
aidenfoxivey has joined #asahi
<NightRaven[m]>
ok i am going to try with the new Image.gz again and the .dtb
<mps>
could I somehow tell u-boot to first try external usb disk and if it is not found to try to find uefi on nvme
nico_32 has quit [Ping timeout: 480 seconds]
<Glanzmann>
kettenis: I see.
<Glanzmann>
Has marcan already agreed on a method to pass the wifi firmware from macos to Linux? Because we could already dd a ext4 on the linux parition, would make installation less cumbersome and would not require a second system.
<Glanzmann>
I used the following command line: cat ./m1n1/build/m1n1.macho <(echo 'boot-args=net.ifnames=0 rw root=/dev/sda rootwait rootfstype=ext4') ./linux-2.6/arch/arm64/boot/Image.gz ./linux-2.6/arch/arm64/boot/dts/apple/t8103-j293.dtb > nr.macho
inffy[m] has joined #asahi
<NightRaven[m]>
Oh ok thx
as400 has joined #asahi
aidenfoxivey has quit [Read error: Connection reset by peer]
zimsneexh has quit [Read error: Connection reset by peer]
<as400>
jannau: I can also confirm kbd and touchpad working on t6000.
<NightRaven[m]>
<Glanzmann> "NightRaven: ping https://ab34.de..." <- When I curl that it does not work
<NightRaven[m]>
It says 301 moved permanently
<NightRaven[m]>
Nvm
<NightRaven[m]>
I got it now
zimsneexh has joined #asahi
Graypup_ has quit [Quit: meow]
Graypup_ has joined #asahi
<Glanzmann>
No big news, but I also have working keyboard with jannau branch on the macbook air.
<NightRaven[m]>
OMG the keyboard works thanks so much I appreciate your help
<Glanzmann>
NightRaven[m]: Next step is to do crate a dos fat partition under macos, reboot into linux and put your archlinux on it.
<NightRaven[m]>
Ok so help me here I make one partion
<as400>
is cpufreq scaling working ?
<Glanzmann>
If you want, you can watch me do it because I'm doing it right now.
<NightRaven[m]>
Sure can I see
<Glanzmann>
Or I record it for you.
<NightRaven[m]>
Sure you can record it if you want
<NightRaven[m]>
But do I only make one partion
<NightRaven[m]>
And make it dos
<NightRaven[m]>
And put arch rootFS there
<Glanzmann>
Yes, but you don't keep it as dos.
<jannau>
as400: no, there is no cpufreq driver in the tree. m1n1 changes the P cores cpu clock to 2 GHz though, the E cores are already running at their max
<Glanzmann>
You just create it on macos because that is the safe thing to do.
<Glanzmann>
And than under Linux you format this partition to ext4.
<Glanzmann>
And than you putch arch on it.
<as400>
jannau: thx, is this subject to change in the future ?
<sven>
nah, it would not be fair to run these cpus at 100% speed :-p
<j`ey>
sven: :P
<as400>
sven: having a good mood tonight, right ? :)
<NightRaven[m]>
Glanzmann: So then format the one partion to ext4 and put rootFS there
<Glanzmann>
Correct.
<Glanzmann>
So you have to partitions for linux, one for the m1n1, kernel, cmdline args.
<Glanzmann>
And one for the rootfs.
<NightRaven[m]>
Wait this is confusing
<NightRaven[m]>
So
<j`ey>
as400: saturday night! and I think sven is off for the winter break too
<NightRaven[m]>
3 partions
<Glanzmann>
NightRaven[m]: The asahi installer created one 2.5 GB partition. This is the one you're using to boot from right now.
<Glanzmann>
And than you put one additional one for the rootfs.
<jannau>
as400: look at proxyclient/experiments/cpu_pstates.py or src/cpufreq.c to change the frequency
<Glanzmann>
Than you have one partition for macos and one for 1tr (the last one 5,7 GB in size)
<NightRaven[m]>
Ok I will make a 100gb partion for rootFS
<as400>
j`ey: yeah :)
<NightRaven[m]>
3gb for m1n1 so the macho file
<Glanzmann>
NightRaven[m]: For example, yes.
<Glanzmann>
NightRaven[m]: yeah, but the 3gb partition is already there, you do not need to create it.
<Glanzmann>
I forgot how to create a msdos parition on macos. Once I figure it out, I'll record it.
<as400>
jannau: I'm not really pursuing high clock frequencies. Was just asking out of curiosity.
<NightRaven[m]>
Ok do you have the rootfs for arch
<Glanzmann>
I should actually record the whole process once, because I'm always struggeling with the same steps.
<NightRaven[m]>
Hmm ok
<Glanzmann>
NightRaven[m]: jannau posted the link, so that will be easy to get.
<NightRaven[m]>
Tell me when you finish the recording give me a ping
<NightRaven[m]>
well i have to go now but good luck on the partion c ya tomorrow : )
<Glanzmann>
NightRaven[m]: have a good night sleep. Will put the recording in the irc.
tertu2 has joined #asahi
tertu has quit [Ping timeout: 480 seconds]
as400 has quit [Quit: Page closed]
<landscape15[m]>
Is it possible to run my custom rootFS from an external USB, without connecting with an other pc?
<Glanzmann>
Yes.
<Glanzmann>
But you need a 2.5 GB Partition on your internal ssd to to kick of m1n1.
<Glanzmann>
jannau: Thank you for your tree. I have X running on my macbook air with keyboard and touchpad.
<landscape15[m]>
Glanzmann: yeah I have the stub macOS partition set up (with m1n1 installed), but I don’t know what to do next.
<Glanzmann>
landscape15[m]: You put whatever you wanto to put on your usb drive.
<Glanzmann>
landscape15[m]: Than you build a chain with m1n1, linux commandline, linux kernel and optional ramdisk copy it in 1tr and run the kmutil to bless it that's it.
<Glanzmann>
See backlog for details, NightRaven[m] just did that.
Bicet[m] has joined #asahi
<landscape15[m]>
Glanzmann: ok, so I only need to change the boot object in 1TR. I read this https://ab34.de/u/asahi.txt
<Glanzmann>
But I think I copied the wrong files from macos, becasue there should be a clmb but I have a txcb.
<zimsneexh>
I tried aswell but I cant seem to get it to work
Techcable has quit [Ping timeout: 480 seconds]
<Glanzmann>
zimsneexh: I see, I try again. Update in a few minutes.
<zimsneexh>
Also not quite sure what I'm looking for. Can't see anything about wifi in the kernel log
<Glanzmann>
zimsneexh: I can see something, but I screwed up first.
<Glanzmann>
Now I think I did everything right, but it still does not work.
<Glanzmann>
jannau: mps: j`ey: Do you have working wifi on macbook air / pro?
<Glanzmann>
zimsneexh: I tried without the ramdisk
<landscape15[m]>
NightRaven: Do I only need to run kmutil to set the new boot object?
<Glanzmann>
landscape15[m]: Yes.
<Glanzmann>
But from 1tr.
<Glanzmann>
So I think about the wifi, the patch is missing.
<Glanzmann>
But I know that alyssa had one in her tree. So I'm digging it up.
<j`ey>
Glanzmann: No I havent tried yet
<Glanzmann>
'13
<zimsneexh>
Hm, sounds good
bps2 has quit [Ping timeout: 480 seconds]
<Glanzmann>
I tried with alyssas patches, but no luck so far.
<zimsneexh>
I feel like it might be because the wifi card is missing from the devicetree?
<Glanzmann>
zimsneexh: Yes, might be. And you're right, alyssa only exposed the j274 (mini) in the device tree.
<Glanzmann>
zimsneexh: I just checked the devie tree and the wifi node including register and mac address is in there.
<Glanzmann>
Even without the patches, so that made it at least into jannau's branch.
jmr2 has joined #asahi
<jmr2>
Glanzmann: I'm the one who wrote those steps about how to extract the wifi firmware.
<jmr2>
While it's possible to get the corellium wifi driver to work, marcan has explicitly asked us to stop doing so (see the log from Dec. 2).
<jmr2>
He mentioned that he want to rewrite it soon, and asked us to be patient.
<jmr2>
We need to keep in mind that any time one of us ask for support from one of the dev, we slow the project down.
<Glanzmann>
jmr2: I see.
Glanzmann has quit [Quit: EOF]
<marcan>
the way that driver does things is completely crazy and will never fly upstream; therefore trying to use it is largely a waste of time since it needs a complete rewrite
<marcan>
same with the keyboard driver btw; the patches to that aren't crazy, and it can be made to work (I spent some time the past few days poking around the corellium patches to that to validate the SPI driver I wrote), but it turns out the *original* driver in Linux there was written with the wrong understanding and we're going to be writing a new driver from scratch that does things properly
<marcan>
ideally that would also be ported to Intel macbooks and end up replacing the old driver altogether at some point in the future
<marcan>
(to clarify: the wifi *patches* need a rewrite, the existing driver is fine; the keyboard *driver* needs a rewrite because the existing driver is doing entirely the wrong thing)
riker77 has quit [Quit: Quitting IRC - gone for good...]