2024-06-16
01:00KxCORP5894 has quit [Quit: Bye!]
01:07KxCORP5894 has joined #asahi-alt
01:38duckworld_ has quit [Ping timeout: 480 seconds]
01:41zerdox has quit [Ping timeout: 480 seconds]
01:42duckworld has joined #asahi-alt
01:52zerdox has joined #asahi-alt
03:21zerdox has quit [Ping timeout: 480 seconds]
04:42lactose has joined #asahi-alt
04:47lactose has quit []
05:04SalimTer- has joined #asahi-alt
05:09SalimTerryLi has quit [Ping timeout: 480 seconds]
07:09chadmedthe only thing that really tempts me over to sd is better plymouth integration and faster default runlevel booting but i dont really care about anything else it offers
07:17MichaelLongwhat ever works for you
07:32TellowKrinkle has joined #asahi-alt
07:46runxiyuchadmed: It's just that I don't personally have a lot of time, and using Gentoo doesn't help
07:48JayBeeFOSS has quit [Ping timeout: 480 seconds]
07:49JayBeeFOSS has joined #asahi-alt
08:50leiorunxiyu: if you don't care for tweaking your USE flags a lot and compiling for armv8.5-a specifically, you can use a desktop profile without global USE tweaks and the binhost and get most as ready binaries.
08:51leio(you can still set your CFLAGS and co to get that small side benefit when you do end up having to compile something yourself)
08:55runxiyuhttps://wiki.gentoo.org/wiki/Profile_(Portage) only shows that there are ones for GNOME and KDE though
09:00leiothere's a generic desktop profile too, though I think the binary packages are built with USE flag defaults for desktop/gnome/systemd and desktop/plasma/systemd
09:00leiowhich just means that some packages that actually do have USE flags that are toggled on in gnome or plasma profiles (but not desktop) and you don't turn them on, will force you to compile the occasional thing yourself.
09:02leioI don't use binhost myself (I compile firefox in 28 minutes, webkit-gtk in 10 minutes), but I've seen it in user reports telling you why it doesn't pick a binary package when it doesn't, so if it's some big package you don't want to wait, allows you to tweak the USE flags to match to get the binary package still.
09:17chadmed has quit [Quit: Konversation terminated!]
09:17chadmed has joined #asahi-alt
09:30KxCORP5894 has quit [Quit: Bye!]
09:40u154ss has joined #asahi-alt
09:41KxCORP5894 has joined #asahi-alt
09:45u154ss@chadmed et all Again thinking of installing Gentoo alongside my existing Debian installation, running a M2 Mini with 24GB mem. I presume the install documentation is up to date? I had a look at Chadmed's version, but the docs make some assumptions that have me scratching me head. My fault, as installing Gentoo on apple silicon as not the same as on an x86 box. Any (major) caveats?
09:48u154ssI have 40Gb free space resserved for the install, small but enough to install the basics and see how things pan out.. I tried with your guide before (six months ago), but somewhere towards the end of the installation, installing boot loader, something major went wrong - most likely my fault. That is why I am posing the question again... Sorry for the bother.
09:55u154ssIn other words, I would like to keep my existing Debian installing AND install Gentoo alongside same, aka dual-boot in the x86 world. I am not sure whether this is covered in the Gentoo wiki docs. Hence my question(s).
10:02chadmedthe supported way is to use the asahi installer to spin out a new apfs stub and linux root
10:07u154ssSo, because of the way Asahi does its magic, I will need need more time at the drawing board.. If I understand you correctly, I will have to basically "duplicate" the Debian Asahi environment (APFS stub and another Linux root partition) and go from there. That is most likely what happened six months ago - I overwrote, unwittingly the existing Debian entries.
10:09u154ssI would basically need to arrive at a situation, using 1TR where I see three images on the splash screen i) Debian ii) Gentoo aand iii) macos.
10:16opticron_ has quit [Read error: Connection reset by peer]
10:16opticron has joined #asahi-alt
10:17chadmedgo back to macos and run the asahi installer again, installing a new os into the free space created
10:21u154ss@chadmed indeed, simple if you have done it multiple times, for me, I must approach things with a considered approach as I do NOT want to torpedo my existing Debian installation again. If it is (the Gentoo) installation) successful, I would probably wipe Debian and do a an install on the ex-Debian partition ca. 350GB.
10:46cocateh has joined #asahi-alt
10:47leioI guess then you could shrink from macOS instead to see how it goes, if you'd re-do it anyways if first is successful?
10:59u154ss has quit [Remote host closed the connection]
11:05cocateh is now known as nickiminjaj
12:37zerdox has joined #asahi-alt
12:59u154ss has joined #asahi-alt
13:05u154ss@chadmed Did as you suggested - created a seperate APFS stup and Linux root partition. Installed a minimal fedora image in the partition. Then switched to your wiki and continued. Downloaded a Gentoo image (install.iso), ran genstrap.sh and rebooted into Grub and selected Gentoo Live Image. Unfortunately, immediately after "LoadingInitial Ramdisk" I am receiving "XHCE timeout on event type 0..." messages, it would seem in a loop. No terminal input possi
13:08u154ssThe keyboard/mouse are dead. I tried swapping the mouse/keyboard into the USB-A ports, no difference. Peripherals still dead. At this stage, I have no ideas. At least my Debian image is still here... Again, I am running an M2 Mini.
13:10chadmedthat sounds like it could be a red herring. if it was just a usb issue youd still get sent to a tty
13:11chadmedi can try play around with a from-scratch install next weekend, its been a while since i did one (would have been around the time i updated genstrap to work with fedora)
13:15u154ssFair enough. I booted into the Gentoo Live Image a few times, swapping USB cables etc. No change, still the XHCI... messages with keyboard and mouse dead. Thanks for the assistance anyway.
13:16u154ssI am typing this from the same environment (Hardware) as I tried to boot the Gentoo Live Image stuff.
13:52u154ss has quit [Remote host closed the connection]
14:43zerdox_ has joined #asahi-alt
14:47zerdox has quit [Ping timeout: 480 seconds]
14:51zerdox_ is now known as zerdox
15:23zerdox has quit [Ping timeout: 480 seconds]
16:24zerdox has joined #asahi-alt
16:42Guest9623 has quit [Quit: Bridge terminating on SIGTERM]
16:42rhysmdnz has quit [Quit: Bridge terminating on SIGTERM]
16:43Jamie has joined #asahi-alt
16:43Jamie is now known as Guest9806
16:43rhysmdnz has joined #asahi-alt
16:51john-cabaj has joined #asahi-alt
17:02ethantwardy has quit [Quit: WeeChat 4.3.2]
17:02ethantwardy has joined #asahi-alt
17:03ethantwardy has quit []
17:04ethantwardy has joined #asahi-alt
17:05ethantwardy has quit []
17:06ethantwardy has joined #asahi-alt
17:07ethantwardy has quit []
17:07ethantwardy has joined #asahi-alt
17:14ethantwardy has quit [Quit: WeeChat 4.3.2]
17:15ethantwardy has joined #asahi-alt
17:15ethantwardy has quit []
17:16ethantwardy has joined #asahi-alt
17:17john-cabaj has quit [Ping timeout: 480 seconds]
17:17ethantwardy has quit []
17:17ethantwardy has joined #asahi-alt
18:19glem has joined #asahi-alt
18:35birate17 has joined #asahi-alt
19:44cylm has quit [Ping timeout: 480 seconds]
20:02zerdox_ has joined #asahi-alt
20:04zerdox has quit [Ping timeout: 480 seconds]
20:04zerdox_ is now known as zerdox
21:28birate17 has quit [Remote host closed the connection]
23:10cow123 has quit [Ping timeout: 480 seconds]