#
…

2022-02-18

00:07axboe has quit [Ping timeout: 480 seconds]
00:30axboe has joined #asahi
01:06yuyichao has quit [Ping timeout: 480 seconds]
02:06a_fellow_human[m] has joined #asahi
02:16yuyichao has joined #asahi
02:17refi64 has quit [Remote host closed the connection]
02:18refi64 has joined #asahi
02:20mmarchini has joined #asahi
02:21refi64 has quit []
02:23refi64 has joined #asahi
02:46ciggi_ has joined #asahi
02:49ciggi has quit [Ping timeout: 480 seconds]
03:27phiologe has joined #asahi
03:28kov has quit [Quit: Coyote finally caught me]
03:31PhilippvK has quit [Ping timeout: 480 seconds]
04:11axboe has quit [Quit: leaving]
04:35wasd has joined #asahi
04:38ciggi_ has quit [Ping timeout: 480 seconds]
04:47jmr2 has joined #asahi
04:47jmr2Regarding the "Unable to determine primary OS" issue: At 11:45 in the original "Installer research" video, marcan mentions that the Volume UUID is the same as the APFS volume group UUID.
04:48jmr2This isn't the case on my setup.
04:48wasd has quit [Quit: Page closed]
04:49marcanjmr2: diskutil apfs listVolumeGroups shows a different VGUUID from the data role volume?
04:50jmr2Errr... Sorry... I don't understand...
04:50marcanthe "Volume Groups <foo>" should be the same as "Volume UUID: <foo>" for the data volume under it
04:53jmr2So no.
05:19the_lanetly_052___ has joined #asahi
05:21eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
05:36jmr2 has quit [Remote host closed the connection]
05:38marcanwell then.
05:38marcanthat's new.
05:46jmr2 has joined #asahi
05:49jmr2In David[m]123456789 and in my case, it seems that we both created a second MacOS admin user. No idea how that can be related to volume UUIDs.
05:49jmr2I'm refraining from experimenting on partitions at this time - let me know if you need anything else.
05:55jmr2 has quit [Remote host closed the connection]
06:22eroux has joined #asahi
06:57marcanjmr2, David[m]123456789: I just updated the installer, please try again
06:58linearcannon has quit [Read error: Connection reset by peer]
06:58linearcannon has joined #asahi
07:55David[m]123456789The installer got stuck on 'Setting up Recovery volume...'
07:55David[m]123456789(I had a network outage, not sure it's related), would there be an issue if I restart it?
08:01GlanzmannIt retried 5 times and than gives up.
08:01GlanzmannDavid[m]123456789: Can you paste the complete output?
08:03David[m]123456789 % Total % Received % Xferd Average Speed Time Time Time Current... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/YOMXMcZUcawcKWsflWgWBTqv)
08:04GlanzmannDavid[m]123456789: I see. Hmm. For me, when it happens, it lets me know that there was an error.
08:07GlanzmannDavid[m]123456789: Retry anyway, it can't hurt you need to delete the stub partition.
08:07GlanzmannDavid[m]123456789: Can you please paste me the output of 'diskutil list'
08:07a_fellow_human[m] has left #asahi [#asahi]
08:07yuyichao_ has joined #asahi
08:09Major_Biscuit has joined #asahi
08:11yuyichao has quit [Ping timeout: 480 seconds]
08:12MajorBiscuit has joined #asahi
08:13GlanzmannDavid[m]123456789: If I would like to reinstall the stub partition I had to do the following: https://tg.st/u/delete_stub_parition.txt
08:18Major_Biscuit has quit [Ping timeout: 480 seconds]
08:25David[m]123456789Welp! I booted on the righoust most asahi startup disk (though it would be the most recent one, so the one where installation finished), but now I'n in a boot loop!
08:27David[m]123456789I have no guarantee
08:27GlanzmannDavid[m]123456789: that is normal.
08:27GlanzmannSo you need to power off the machine.
08:27Glanzmannthan you press and hole the power button and select options
08:28GlanzmannThan from utilities > terminal you open a terminal and type: /Volumes/Linux/step2.sh
08:28GlanzmannThan you will be promoted for password, y, username, password.
08:28GlanzmannAfterwards you should have m1n1 on your system and no longer a boot loop.
08:28GlanzmannIf you want u-boot that, you need to install boot loop
08:28David[m]123456789I'm in a boot loop when I go in 1TR
08:29David[m]123456789* when I try go in, * in 1TR or boot normaly
08:31GlanzmannThat is not 1tr.
08:31GlanzmannThat is recovery.
08:32GlanzmannShut it down. Completly.
08:32GlanzmannThan press and hold the power button for 15 seconds.
08:32GlanzmannLet it go.
08:32Glanzmannchoose options. Than you're in 1tr.
08:32Glanzmann1tr and recovery look similiar, but are not.
08:38David[m]123456789I pressed power until the second options restant (ie. 1TR)
08:39David[m]123456789s/I pressed power until the second options restant (ie. 1TR)/I pressed power until the second options restart (1TR I think) before it goes in boot loop marcan @marcan:matrix.org /
08:44GlanzmannDavid[m]123456789: That is not normal.
08:44GlanzmannDavid[m]123456789: I assume you need to recovery your mac using a second mac or idevicerestore.
08:44GlanzmannI never tried idevicerestore only the other thing.
08:46GlanzmannDavid[m]123456789: Here is a quickstart for idevicerestore. https://tg.st/u/idevicerestore_quickstart.txt
08:47the_lanetly_052___ has quit [Ping timeout: 480 seconds]
08:49David[m]123456789Thanks for the info, how is the debian machine connected? I will also go to an apple store
08:49VinDuvidevicerestore works fine in my experience but you need to install the right parts from source, start usbmuxd beforehand and have sufficient disk space
08:52j`eyDavid[m]123456789: so did you delete a partition or something?
08:53David[m]123456789No I didn't, I must have boot on the wrong Asahi startup disk (the one who did not complete the install)
08:54j`eyyou should be able to get to 1TR or something then
08:54VinDuvDavid[m]12345678: any USB cable which can be connected to the USB-C port on the Mac and to a USB-A or USB-C port on the other machine should work
08:55VinDuvThe other machine doesn’t even needs to have USB3 ports, USB2 will work fine
08:56VinDuv(ok given that this is USB maybe saying “any USB cable” is a bit optimistic :)
09:06David[m]123456789<j`ey> "you should be able to get to 1TR..." <- The installer did not finished due to a network outage, not the 1st of the 2 step install
09:07j`eyyeah, I saw the vid now.. not sure how that could have caused a boot loop :(
09:11David[m]123456789I should have deleted the wrong partition and don't assume the one on the rigth i s the most recent/rigth one
09:12David[m]123456789s/assume/assumed/, s/i/is/, s/s//
09:12j`eyDavid[m]123456789: so did you delete a partition?
09:16David[m]123456789None, I just restarted on the stub for which the install did not finish
09:17j`eyIm not sure why you changed the startup disk to that one, if you knew the install didnt finish
10:07kov has joined #asahi
10:56bps has joined #asahi
11:27kloenk has quit [Remote host closed the connection]
12:34eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
12:53roxfan2 has joined #asahi
12:58jmr2 has joined #asahi
12:59jmr2David[m]123456789: when you selected Asahi as the boot disk, how many options were avaiable there? Can you describe them all?
12:59jmr2For info, the order in which those are displayed is random.
13:00roxfan has quit [Ping timeout: 480 seconds]
13:01jmr2Macintosh HD and Asahi ?
13:01David[m]123456789s/2 options/Machintosh HD + 2 Asahi L/
13:03jmr2OK. Any idea why there were 2 Asahi listed? I though you only managed to get the installer to run with the latest fix from a few hours ago. Did you run the installer twice since? Did it jam at the same place both times?
13:04axboe has joined #asahi
13:05eroux has joined #asahi
13:18jmr2 has quit [Remote host closed the connection]
13:22jmr2 has joined #asahi
13:22jmr2marcan: tested successfully. Thank you!
13:27jmr2 has quit [Remote host closed the connection]
13:39jmr2 has joined #asahi
13:41jmr2David[m]123456789: in case you didn't try already, try other patterns with the power button. Hold it even longer, or release it as soon as "Chargement des options de démarrage" appears.
13:42David[m]123456789From debian live
13:43j`eylooks like you dont have enough space
13:45David[m]123456789a 16gb stick should be enough? That leaves 12 CB for the downloads
13:45j`eywell i guess check how much space is actually used
13:46j`eyVinDuv did say 'you have to have sufficient space', so it might be quite big..
13:48jmr2If you check (I suggest "du -h"), what does it says?
13:50jmr2Given that it's a "live" OS, I wonder if the available space isn't limited by your RAM instead of the USB stick size.
13:52David[m]123456789<jmr2> "OK. Any idea why there were 2..." <- Due to a network outage it failed later but still installed itself, I then later installer it properly and reboot on what I though was the correct install
13:52David[m]123456789* Due to a network outage it failed later but still installed itself, I then later installed it properly and rebooted on what I though was the correct install
13:53David[m]123456789* Due to a network outage it failed but still installed itself, I then later installed it properly and rebooted on what I though was the correct install
13:53jmr2OK. Thanks for clarifying.
13:59David[m]123456789It's the firmware image (.ipsw) taking 8 gb
13:59jmr2Shoot. That should have been "df -h". Brain fart. Sorry.
13:59matthewayers[m]jmr2: I thought it was funny that the command spelled out “duh” at first
14:00jmr2Well, duh :-D
14:02jmr2David[m]123456789: I only have the .app installer here, which is 12GB. I'd guess that the IPSW has a similar size.
14:06David[m]123456789It's seems to be copied on udev and tmpfs 2 times
14:06David[m]123456789s/udev/overlay/
14:07jmr2I'm booting a live debian to check exactly, but in any case, it doesn't matter. There's no partition larger than 7.7GB, so no way to store a 14GB file anywhere.
14:08David[m]123456789s/on/in/, s/udev/overlay/
14:09VinDuvWhen I restored the mini, idevicerestore downloaded a 13.2 GiB ipsw and extracted 11.8 GiB of files out of it for a total of 24.9 GiB used
14:10VinDuv(yes idevicerestore has a -l option that automatically downloads the right ipsw… but if you happen to run out of disk space while it downloads the files, it produces confusing error messages, unfortunately)
14:13jmr2 has quit [Remote host closed the connection]
14:15David[m]123456789I downloaded it manually
14:15jmr2 has joined #asahi
14:15David[m]123456789<jmr2> "I'm booting a live debian to..." <- So no way to do it from a live system?
14:18jmr2Looks like you need 24GB of free space. From my test, the root filesystem is indeed mounted on RAM, but on this system with 16GB RAM, I'm offered ~8GB of rootfs space, just as you are.
14:19jmr2You might be able to use the machine's disk and mount that.
14:21jmr2But I'd recommend not doing it on a FAT/NTFS filesystem. So you might need to repartition its disk, which, again, isn't risk-free.
14:22jmr2If you have an unused USB backup hard disk, that might be another option.
14:23jmr2Full disclosure: I've never done an idevicerestore recovery.
14:24jmr2I also kind of remember you telling that you have a lot of data on the Air. I'm not sure if idevicerestore will preserve any of that, you might want to consider other options.
14:25David[m]123456789I did a timemachine backup before
14:29jmr2OK. I have to go for now. Keep us posted.
14:29jmr2 has quit [Quit: Page closed]
14:33ifthenelse2 has joined #asahi
14:33Raqbit7 has joined #asahi
14:34ifthenelse has quit [Quit: Ping timeout (120 seconds)]
14:34Raqbit has quit [Quit: Ping timeout (120 seconds)]
14:34ifthenelse2 is now known as ifthenelse
14:34Raqbit7 is now known as Raqbit
14:40yuyichao_ has quit [Ping timeout: 480 seconds]
14:44GlanzmannThere is also another very interesting tree, which is: https://git.kernel.dk/cgit/linux-block/log/?h=m1-test-nvme
14:59yuyichao_ has joined #asahi
15:00jbowen_ has joined #asahi
15:02jbowen_ has quit []
15:05axboe has quit [Ping timeout: 480 seconds]
15:06Glanzmannmps: Thanks, noted and going to try.
15:13mpsmy advice: use alpine linux edge (aka development release) and you will have bleeding edge software
15:13mpsnot that I promote alpine
15:14mpsalpine is bad distro (I know) but other ones are worse
15:14mpsthis is my POV
15:17patience[m]why is it bad?
15:18mpspatience[m]: if I explain it will be off-topic here, but try to use it and you will see
15:20mpsmy msgs above were intended for Glanzmann
15:29thinkofher has joined #asahi
15:30kendfinger has quit [Remote host closed the connection]
15:30robher has quit [Read error: No route to host]
15:30kendfinger has joined #asahi
15:31robher has joined #asahi
15:34the_lanetly_052___ has joined #asahi
15:38axboe has joined #asahi
15:41Glanzmannmps: I'll probably continue to use Debian, maybe I give alpine a go. In the early days, I tried a lot of distros and Operating Systems, but Debian is what got stuck.
15:46Glanzmannpovik: When I need bleeding edge software in Debian, I either use Debian and wait a little while or I pull it from sid and build a deb that I use, or compile and install it locally.
15:47GlanzmannBut actually I like Debian because it is not bleeding edge and well tested.
15:54marcanthere should be *some* way to get into system recovery if the paired recovery doesn't work, but I don't know what it is
15:54mpsGlanzmann: sure, use what you feel is best for you (I don't want to tell anyone what to do)
15:54marcanlet me try some stuff on my Air...
15:58axboemy main gripe with trying a new distro is the packaging system
15:58axboeI don't need to learn Yet Another One
16:03Glanzmannaxboe: I agree, but i packaged more rpms in my live than debs. :-)
16:05Glanzmannaxboe: Btw. the new m1-test-nvme branch is that the the one with half the cpu but get everything possible?
16:06axboeGlanzmann: that one was mostly just for sven to see the apple-nvme changes to support some of the effiency features
16:06axboeGlanzmann: outside of that, it's just sitting on top of the stuff I currently run on it
16:07axboewhich does have the "kill dead cores on my m1 pro"
16:07GlanzmannI saw that. :-)
16:07j`eyaxboe: how do you kill what is already dead? :P
16:07axboemostly good stuff in there, a few work-arounds that are specific to my setup
16:07axboej`ey: with fire!
16:08Glanzmannaxboe: I saw you have a keyboard backlight patch, what is necessary from the userland in order to use that?
16:08axboeGlanzmann: nothing
16:09landscape15[m]Glanzmann: thanks. It’s the same script you shared in the docs right?
16:10axboeGlanzmann: fwiw, I also run an m1n1 hack to have it work with the disabled cores
16:10axboejust for full disclosure
16:10eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
16:12Glanzmannaxboe: And another thing I wanted to ask, you. I have a lot of Samsung SSDs with uncorrectable read errors that I bought last yaar with uncorrectable read errors, evo 2TB/4TB, qvo 4TB, NVMe pro 980 2 TB. Pattern is everywhere the same. Debian does a raid check every month, or I read a lot of data, and the uncorrectable read errors pop up. I did not loose anything, but I wonder if you heard something. I
16:12Glanzmannsee more and more people on the internet seeing simliar things. For me the pattern is always the same barely used SSD ( 10 - 30 TB written in 3 months), uncorrectable read erros. Out of 20 disks I bought last year, 15 show these symptoms.
16:12Glanzmannlandscape15[m]: Yeah, it is the same script, I test the new stuff and if I consider it stable, I put it in there.
16:16GlanzmannI saw one bug with tagged command queueing trims, I trimmed the drives, same issue pops up 4 weeks later during raid check.
16:17kendfinger has quit [Read error: No route to host]
16:18tardyp has quit [Remote host closed the connection]
16:18mmarchini has quit [Remote host closed the connection]
16:18robher has quit [Remote host closed the connection]
16:18kendfinger has joined #asahi
16:18mmarchini has joined #asahi
16:18robher has joined #asahi
16:18tardyp has joined #asahi
16:18mpswhere is the keyboard backlight patch?
16:20marcanok, I found the override
16:21marcanDavid[m]123456789: when in the bootloop, double-press and hold the power button before the apple shows up
16:21marcantiming might be tricky
16:21marcanbut it should go into fallback recovery
16:22mpsGlanzmann: aha, thanks
16:22mpslets test it
16:23Glanzmannmps: Let me know how it goes, maybe i try it, too.
16:23GlanzmannBut need to get poviks macbook air speaker development setup ready first.
16:27mpsGlanzmann: applied patch and looking in .config, though don't see changes for DTS
16:28the_lanetly_052___ has quit [Remote host closed the connection]
16:29Glanzmannmps: I think they're already in. because in axboes tree there is patch for adding it to m1 max/pro but it that patch it appears they're already in: https://git.kernel.dk/cgit/linux-block/log/?h=m1-test Search for 'Andreas Heider' patches.
16:30mmarchini has quit [Read error: No route to host]
16:30mmarchini has joined #asahi
16:30tardyp has quit [Read error: No route to host]
16:31robher has quit [Read error: No route to host]
16:31kendfinger has quit [Read error: No route to host]
16:31kendfinger has joined #asahi
16:31tardyp has joined #asahi
16:32robher has joined #asahi
16:32the_lanetly_052 has joined #asahi
16:35mpsGlanzmann: I don't see backlight word in dts in spmi/work jannau's branch
16:36Glanzmannmps: I think you have to look for fpwm
16:37mpsfpwm is there
16:37mpsbut not backlight
16:37j`eyjannau's branch doesnt have the backlight, that's only in that branch
16:39mpsj`ey: ah, that is, thanks
16:44mpsI think this will not work on t8103 without dts patching
16:45mpsbut will build it to see if it will not break something
16:47mpsj`ey: so pipcet worked on this
16:47Glanzmannmps: The patch is from pipcet.
16:47Glanzmannj`ey: You don't have the device tree changes for macbook air lying around as well, do you?
16:48j`eyGlanzmann: no, pip only had the mbp
16:48GlanzmannI see. Never mind it my default color for xterms is white, so let that my keyboard backlight. :-)
16:50kovapropos recovery modes and all that, how does one upgrade the stub macos install used for m1n1?
16:51kovI would like to upgrade to the latest to not be using obsolete macho m1n1 and procedures
16:51j`eyI don't think that is possible yet? I guess you can just reinstall the stub over the old one?
16:52Glanzmannkov: You boot to 1tr or macos, delete the old stub and run the asahi installaer again.
16:52GlanzmannI have done that many times successfully.
16:52kovj`ey, Glanzmann cool, thanks!
16:52GlanzmannYou can also delete the stub partition from LInux.
16:52Glanzmannkov: If you want to do it from macos, see here: tg.st/u/delete_stub_parition.txt (tip came from marcan, IIRC).
16:53marcankov: there will eventually be some kind of upgrade process, but it's not done yet, so yeah, just wipe and re-create
16:53kov++ I've done the diskutil dance a few times, before the installer
16:53Glanzmannj`ey: You need to delete the old stub first, but yes that's it.
16:53j`eyGlanzmann: in all the examples youve shown of the installer, I think the freespace was the whole area? or did you create the 3gb parition
16:54GlanzmannI've done a lot of videos. In the old days, I always started from scratch (fresh macos).
16:54GlanzmannIn the most recent u-boot video, too.
16:54marcanhttps://photos.app.goo.gl/VjNnWGxTZra5oUeu5 <- video on how to break out of the boot loop
16:54ChaosPrincesshow do apple do kernel updates w/o a trip through 1tr? just by being apple and having special signatures or a mechanism that we can use?
16:54GlanzmannBut the latest debian installer video had u-boot already installed. But in none of the videos I creaed a '3gb' partition. Btw. the stub is 2.5 GB.
16:55marcanChaosPrincess: yes
16:55j`eyGlanzmann: so does the installer create the stub parition from the freespace?
16:55j`eyGlanzmann: and yes i was using 3gb as an estimate for 2.5 :P
16:55ChaosPrincessmarcan: okay, s/or/xor/
16:55marcanthe former
16:55marcanthey don't use the fuOS mechanism which requires 1TR to provision a kernel
16:56Glanzmannj`ey: Yes, the installer creates the stub partition from free space, it is a prerequisit.
16:57j`eyGlanzmann: so if there's only 2.5g there it can just use all of that space?
16:58j`eyDavid[m]123456789: marcan made a video for getting out of the bootloop https://photos.app.goo.gl/VjNnWGxTZra5oUeu5
16:58Glanzmannj`ey: 2.5GB is used by the asahi installer for the stub. Than you need extra free space if you want a esp and root partition.
16:58Glanzmannj`ey: Or if you have the stub, of course you can also boot from usb using u-boot or tethered using m1n1.
16:58axboeGlanzmann: an ssd should never throw uncorrectable read errors, that's a huge red flag
16:59Glanzmannaxboe: I know. And I think I'm starting to return them all. I already started using Intel DC which are slower and more expansive, but hopefully are stable.
17:00axboeGlanzmann: I've been using samsung in other boxes and my other laptop, I've never seen that. I'm curious if it's some side effect of an issue with eg queued trim like you mentioned, because if not, the fw is pretty buggy
17:00Glanzmannaxboe: After I told the issue a friend of mine, he did a dd if=/dev/sdX of=/dev/null bs=8M over is evo 4TB, guess what .... 17 MB were not readable. He returned the drive after evacuating the data and bought a micron.
17:01the_lanetly_052__ has joined #asahi
17:01axboethe way ssds do error correction these days, it should rewrite the block if the read confidence is marginal
17:01axboeif after a straight overwrite, defective hw for sure
17:02Glanzmannaxboe: In the past I had a lot of Samsung SSDs 840/850 EVOs. Actually 36 of them, I used them for 8 years+, no a single one had any issues whatever. I'm still using them today.
17:03axboeI generally find them pretty solid too, some models end up being dodgy but most are good
17:03Glanzmannaxboe: I see. Here are smartctl output of a few of them: https://ab34.de/u/ryzen_smartctl_2021-11-04.txt
17:05axboeGlanzmann: yeah thath doesn't look great
17:05GlanzmannThat is what I thought, I'll replace them all, I guess. A lot of money ...
17:05axboeGlanzmann: yeah, that sucks...
17:05mpsGlanzmann: bad cables or adapter (that is my experience)
17:06axboecabling would usually show transport issues, not uncorrectable media errors
17:06axboethough of course who knows what'll happen with a marginal setup
17:07the_lanetly_052 has quit [Ping timeout: 480 seconds]
17:07axboeshould not show up in smartlog from the drive
17:07jmr2 has joined #asahi
17:09robher has quit [Read error: No route to host]
17:09tardyp has quit [Read error: No route to host]
17:09robher has joined #asahi
17:10jmr2marcan: that video is a great testimony to your old "Safe Hacking" blog post. Thanks for caring.
17:10tardyp has joined #asahi
17:10marcanI'm going to fix the installer so this can't happen too
17:10marcanin fact it couldn't in 11.x, this is a 12.x regression due to the paired recovery
17:10kovnow that I read marcan's thread on twitter I think I actually managed to get into a similar state once, but since I had another mac I used their Apple Configurator 2 thingy and just reflashed
17:11jmr2Out of curiosity, once booted in a recovery, how can you tell which one was used?
17:12j`eyI think the device tree has it?
17:12marcanthe installer will tell you too
17:13j`ey(hence why step2.sh errors out)
17:15jmr2OS Type in the output of bputil -d ?
17:16j`eyor Current OS environment:
17:16jmr2Let me retry it. BRB.
17:16jmr2 has quit [Quit: Page closed]
17:19sami-dev[m]Making the jump to a M1 Max, super excited to follow this project more closely. I'll be sure to drop some money on sponsors/patreon as well. Does anyone know if it's better to donate through sponsor or patreon (not sure if github takes a cut like patreon might)
17:21jmr2 has joined #asahi
17:22jmr2So from MacOS, that says macos. From shutdown, booting with a long press returns "one true recovery", and double-click and hold returns "ordinary recovery os".
17:23jmr2Is the systemwide recovery the "ordinary recovery os", or is there a 4th option ?
17:27ChaosPrincesson 12.x, its always the paired recovery, unless it is broken, and then its systemwide recovery
17:28ChaosPrincess1tr vs normal recovery is the same image, just the security coprocessor configuration is different
17:28axboecurious if anyone have experienced: "Synchronous Exception at 0x664C" when running qemu?
17:29marcansami-dev[m]: github has no fees :)
17:30marcan"ordinary recovery os" means any recovery OS that was not booted through the very special 1TR process
17:30j`eyaxboe: that sounds like it's an error fro UEFI itself?
17:30marcanthat field does not tell you what recovery OS was booted
17:30marcanthe DT stuff does
17:30marcanthat field tells you what *mode* the system is booted in
17:31axboej`ey: good point, I was a bit puzzled in figuring out where it's coming from
17:31axboeI get it sporadically here
17:32axboej`ey: will try and remove the efi bios argument, boots fine without it
17:32opticronhmmm...maybe I'll swap over to github, then
17:32jmr2Thanks.
17:32j`eycan you pay on paypal with github?
17:33jmr2 has quit [Quit: Page closed]
17:41Glanzmannmps / axboe: This was with different cables, mothboards, power supplies, and datacenters. Also with downgraded link speed, disabled tagged command queuing and disabled trim. So I tried a lot of stuff. For now I'll keep my hands away from Samsung. But the Samsung datacenter edition doesn't seem to have the issues. At least only one drive failed.
17:46Glanzmannjmr: I also always end up in recovery os instead of 1tr. No idea why, but I'm certain that I don't let go of the power button and that it is off. Before I try. See here: https://tg.st/u/asahi-installer-u-boot.mp4
17:47axboe15 second press always does it for me, the two minor blinks at 10 and 11 seconds help my synchronize it :)
17:48Glanzmannhrhr. I always count 21, 22, ...
17:55sami-dev[m]<marcan> "sami-dev: github has no fees :)" <- Great! Is there posts on github as well about progress etc?
17:55sami-dev[m]I know patreon has that functionality but unsure about github 😅
17:56j`eysami-dev[m]: they go here https://asahilinux.org/blog/
17:58marcanI do mail out things via GH/Patreon when I post an update, but the updates themselves go on the blog, yeah
17:58marcanand thank you for helping out :-)
18:01j`ey🎉 You sponsored @marcan for $100
18:05j`eymarcan: ty for the continious hard work!
18:07marcanj`ey: you really didn't have to, you're helping out tons already ^^
18:08j`eymarcan: :-)
18:10* marcanoff to sleep
18:10tpw_rulesi seem to recall the next revision of linux-asahi is coming soon?
18:10marcanyes, I did some git cleanup today
18:10marcanhope to wrap it up tomorrow
18:10tpw_rulesexcellent. sleep well
18:15mpsand sweet dreams
18:15sami-dev[m] You're now sponsoring @marcan for $24 a month
18:15sami-dev[m]I'm just a simple webdev so while I can't help out with kernel things I can at least help out with something so people like you can help me run my favorite OS on some really nice hardware ;)
18:15bisko has joined #asahi
18:21marcanthank you! :)
18:23MajorBiscuit has quit [Ping timeout: 480 seconds]
18:25axboe has quit [Quit: leaving]
18:26Glanzmanntpw_rules: I read a line in -dev that hinted that marcan thinks about doing the first release within a month.
18:26tpw_rulesmaybe my m1 max will finally be here by then
18:27David[m]123456789That worked! Thanks a lot marcan @_oftc_marcan:matrix.org
18:27Glanzmanntpw_rules: But if you want a good tree, use jannaus for the moment, I keep this one up2date and don't put anything in there which is not stable: https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/blob_plain/refs/heads/master:/bootstrap.sh
18:29tpw_rulesGlanzmann: is it possible for you to fix your site so that i don't have to download the files? iirc there is some http header you can send
18:32Glanzmanntpw_rules: I like downloading them. I hate people that give me a web page, but if you prefer a web page that you can view in your browser: https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/blob/master:/bootstrap.sh
18:33tpw_rulesGlanzmann: i just want to see the text file i can copy and paste from
18:33GlanzmannOkay, than use that.
18:33tpw_rulesthen you get the line numbers
18:34GlanzmannI think the issue is that it sends the right content type of the file and browsers refuse to show it.
18:35Glanzmann< Content-Type: text/x-sh; charset=ISO-8859-1
18:43tpw_rulesoh, yeah they probably don't have a handler for sh
18:49axboe has joined #asahi
19:14tpw_rulescool, thanks
19:14tpw_rulesi think tg.st is the same way
19:15Glanzmanntpw_rules: Yep, that is because the standard mime.types file for Debian has it.
19:15tpw_ruleswhat mime type does tg.st send? lots of the files don't have extensions
19:17Glanzmanntpw_rules: I tried the files which have 'sh' and there I get application/stream.
19:18Glanzmanntpw_rules: Fixed as well. tg.st/u/uboot.sh
19:19Glanzmanntpw_rules: If you find something tell me, than I change it.
19:23Gaspare has joined #asahi
19:23Glanzmanntpw_rules: *.patch I fixed, about the 5nly I'm not going to anything, but I'll in the future upload all patches with the .patch extension.
19:24Glanzmannjannau: congrats. Do you think we should run the dcp so that you get some testing?
19:27Glanzmanntpw_rules: I copied the two patches to .patch and updated the bootstrap.sh
19:32the_lanetly_052__ has quit [Remote host closed the connection]
19:33jannauGlanzmann: just fixing a regression after changing the way how the bootloader allocated framebuffer is handled
19:39tpw_rulesassuming sha-1 is not broken, two git repositories having a commit with the same hash will have the same repo state, right?
19:39tpw_rulesif that commit is checked out in both
19:40Glanzmanntpw_rules: Yep.
19:41Glanzmanntpw_rules: A checksum of a 'commit' object in git checksums the tree and the complete history leading to that tree.
19:41tpw_rulesokay i was 99% sure that was the case, thank you
19:55axboe has quit [Ping timeout: 480 seconds]
20:06bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
20:13axboe has joined #asahi
20:14bisko has joined #asahi
20:29tardyp has quit [Read error: No route to host]
20:29tardyp has joined #asahi
20:46sebastinez has joined #asahi
20:48sebastinezHey folks, not able to contribute in code, but will look forward to it and eventually documentation contributions!?
20:49David[m]123456789Step 2 of the installer doesn't seems to acknowledge/log in an account when having 2 (admin) accounts
21:00Raito_Bezarius has quit [Ping timeout: 480 seconds]
21:00sebastinez has quit [Quit: Textual IRC Client: www.textualapp.com]
21:03axboe_ has joined #asahi
21:05axboe has quit [Ping timeout: 480 seconds]
21:09Raito_Bezarius has joined #asahi
21:50Gaspare has quit [Quit: Gaspare]
21:58jmr2 has joined #asahi
22:00jmr2David[m]123456789: screnshot ?
22:07jmr2 has quit [Quit: Page closed]
22:22kovremoving the stub and re-running the install worked, but I ended up in a grub rescue prompt due to the numbering of the partitions changing, setting the prefix manually, loading the normal module and running it was enough to boot properly though \o/
22:22kov(and re-installing grub after that of course)
22:22jmr2 has joined #asahi
22:25jmr2David[m]123456789: first time I see this one. Is it the same username that's displayed when step2.sh prompts you for your password the first time ?
22:32jmr2 has quit [Quit: Page closed]
22:34jmr2 has joined #asahi
22:35jmr2David[m]123456789: I believe your second screenshot is from the MacOS login screen. If this is the case, this is your full name, which may or may not be the same as your account name.
22:36jmr2Go back to MacOS, open System Preferences, Users & groups, unlock the lock, right click on your account, select advanced options.
22:37jmr2You're looking for the Account name field.
22:37jmr2I'm going to guess david, with lowercase D.
22:46jmr2 has quit [Quit: Page closed]
…