#
…

2024-10-29

00:08CME has quit [Ping timeout: 480 seconds]
00:21Calandracas has joined #asahi
00:23CME has joined #asahi
00:27reverser has joined #asahi
00:38reverser has quit [Ping timeout: 480 seconds]
00:42c10l has quit [Remote host closed the connection]
00:52c10l has joined #asahi
01:12ellyq_ has quit []
01:25Brainium_ has quit []
01:28disaster has quit [Ping timeout: 480 seconds]
01:37disaster has joined #asahi
01:37ddxtanx has quit [Remote host closed the connection]
01:45reverser has joined #asahi
01:47shintyl has joined #asahi
01:53reverser has quit [Ping timeout: 480 seconds]
01:57chrisl has quit [Ping timeout: 480 seconds]
02:00KxCORP58940003455 has quit [Quit: Bye!]
02:00KxCORP58940003455 has joined #asahi
02:01pb17 has quit [Ping timeout: 480 seconds]
02:01disaster has quit [Ping timeout: 480 seconds]
02:05disaster has joined #asahi
02:07chrisl has joined #asahi
02:11ddxtanx has joined #asahi
02:12pb17 has joined #asahi
02:14Yachtie has quit [Quit: Yachtie]
02:15chrisl has quit [Ping timeout: 480 seconds]
02:58reverser has joined #asahi
03:06reverser has quit [Ping timeout: 480 seconds]
03:12larunbe has joined #asahi
03:13alarumbe has quit [Ping timeout: 480 seconds]
03:14chrisl has joined #asahi
03:21jnn has joined #asahi
03:22chrisl has quit [Ping timeout: 480 seconds]
03:25jn has quit [Ping timeout: 480 seconds]
03:31yuyichao has joined #asahi
03:32tobhe has joined #asahi
03:35shiggitay has joined #asahi
03:36yuyichao_ has quit [Ping timeout: 480 seconds]
03:39tobhe_ has quit [Ping timeout: 480 seconds]
03:44artemist has joined #asahi
03:53reverser has joined #asahi
03:58nela has quit [Ping timeout: 480 seconds]
03:58ddxtanx has quit [Remote host closed the connection]
03:59pb17 has quit [Ping timeout: 480 seconds]
04:01reverser has quit [Ping timeout: 480 seconds]
04:07reverser has joined #asahi
04:11marvin24_ has joined #asahi
04:15marvin24 has quit [Ping timeout: 480 seconds]
04:15reverser has quit [Ping timeout: 480 seconds]
04:18chrisl has joined #asahi
04:26pb17 has joined #asahi
04:26chrisl has quit [Ping timeout: 480 seconds]
04:28shintyl has quit [Remote host closed the connection]
04:41reverser has joined #asahi
04:49reverser has quit [Ping timeout: 480 seconds]
05:24reverser has joined #asahi
05:32reverser has quit [Ping timeout: 480 seconds]
05:36pb17 has quit [Ping timeout: 480 seconds]
05:50pb17 has joined #asahi
05:58aak has joined #asahi
06:19reverser has joined #asahi
06:22chrisl has joined #asahi
06:27reverser has quit [Ping timeout: 480 seconds]
06:30chrisl has quit [Ping timeout: 480 seconds]
06:42reverser has joined #asahi
07:01reverser has quit [Quit: leaving]
07:19pb17 has quit [Ping timeout: 480 seconds]
07:21pb17 has joined #asahi
07:31VasilisTheChu has quit [Ping timeout: 480 seconds]
07:35VasilisTheChu has joined #asahi
07:42aak has quit [Quit: Textual IRC Client: www.textualapp.com]
07:43aak has joined #asahi
07:43VasilisTheChu has quit [Ping timeout: 480 seconds]
07:44aak has quit []
07:45aak has joined #asahi
07:46aak_ has joined #asahi
07:47aak_ has quit []
07:49kode54 has quit [Ping timeout: 480 seconds]
07:49chrisl has joined #asahi
07:54ddxtanx has joined #asahi
07:57chrisl has quit [Ping timeout: 480 seconds]
08:01sand4rt has joined #asahi
08:21kode54 has joined #asahi
08:23aak has quit [Ping timeout: 480 seconds]
08:37aak has joined #asahi
08:38kode541 has joined #asahi
08:44kode54 has quit [Ping timeout: 480 seconds]
09:04Sebastian2 has joined #asahi
09:05pb17 has quit [Ping timeout: 480 seconds]
09:16Sebastian2 has quit [Read error: Connection reset by peer]
09:28aak has quit [Quit: aak]
09:30john-cabaj has joined #asahi
09:37pb17 has joined #asahi
09:38VasilisTheChu has joined #asahi
09:42chrisl has joined #asahi
09:42reverser has joined #asahi
09:44reverserHey. A quick question: I want to make some small modifications to the Asahi Linux kernel on my local install. I am now looking for instruction on how to build the kernel?
09:46VasilisT- has joined #asahi
09:50chrisl has quit [Ping timeout: 480 seconds]
09:51VasilisTheChu has quit [Ping timeout: 480 seconds]
10:09reverserHey, I am trying to build asahi linux kernel on my machine? Is there a set of resources someone could point me to, where I can see what is required to build Asahi linux?
10:12j`eyreverser: have you built any kernel before?
10:12reverserWell, not really. This is why I am trying to familiarize myself. I need it for a project.
10:14j`eydo you need the GPU?
10:14reverserFor now, not. I am using Asahi Fedora Remix, with the server install on a Mac Mini M1.
10:17j`eythen pretty much any guide about building the kernel works, and you can use this config https://copr-dist-git.fedorainfracloud.org/cgit/@asahi/kernel/kernel.git/tree/kernel-aarch64-16k-fedora.config
10:18reverserThis is the repo you are referring to, right? https://gitlab.com/fedora-asahi/kernel-asahi
10:27Juesto has joined #asahi
10:29Juest is now known as Guest7853
10:29Juesto is now known as Juest
10:35Guest7853 has quit [Ping timeout: 480 seconds]
10:38Juest is now known as Guest7854
10:38Juest has joined #asahi
10:42Guest7854 has quit [Ping timeout: 480 seconds]
10:45chrisl has joined #asahi
10:48flokli has quit [Ping timeout: 480 seconds]
10:53chrisl has quit [Ping timeout: 480 seconds]
10:53reverser has quit [Quit: Page closed]
10:57flokli has joined #asahi
11:01shiggitay has quit [Ping timeout: 480 seconds]
11:10Mrmaxmeier has quit [Quit: The Lounge - https://thelounge.chat]
11:14kode541 has quit []
11:14kode54 has joined #asahi
11:14VasilisT- has quit [Ping timeout: 480 seconds]
11:24sand4rt has quit [Ping timeout: 480 seconds]
11:41sand4rt has joined #asahi
12:00john-cabaj has quit [Ping timeout: 480 seconds]
12:02Moprius has joined #asahi
12:03rvalue has quit [Read error: Connection reset by peer]
12:03rvalue has joined #asahi
12:27Moprius has quit [Ping timeout: 480 seconds]
12:27chrisl has joined #asahi
12:35chrisl has quit [Ping timeout: 480 seconds]
12:39Brainium has joined #asahi
12:41malfunction54 has quit [Remote host closed the connection]
12:41malfunction54 has joined #asahi
12:42yuyichao has quit [Read error: Connection reset by peer]
12:45yuyichao has joined #asahi
12:57john-cabaj has joined #asahi
13:03sand4rt has quit [Ping timeout: 480 seconds]
13:04john-cabaj has quit [Remote host closed the connection]
13:17pb17 has quit [Ping timeout: 480 seconds]
13:24chrisl has joined #asahi
13:29VasilisTheChu has joined #asahi
13:33chrisl has quit [Ping timeout: 480 seconds]
13:46pb17 has joined #asahi
13:47chrisl has joined #asahi
14:08Yachtie has joined #asahi
14:41cisco87 has quit [Ping timeout: 480 seconds]
14:45sand4rt has joined #asahi
14:56Brainium has quit [Quit: Konversation terminated!]
14:56Brainium has joined #asahi
15:15sand4rt has quit [Quit: WeeChat 4.4.2]
15:16sand4rt has joined #asahi
15:36JayBeeFOSS has quit [Ping timeout: 480 seconds]
15:37JayBeeFOSS has joined #asahi
15:53DarkShadow44 has quit [Remote host closed the connection]
15:53chrisl has quit [Remote host closed the connection]
15:54chrisl has joined #asahi
15:54DarkShadow44 has joined #asahi
16:00ten1572377432463050661821503 has quit [Remote host closed the connection]
16:00ten1572377432463050661821503 has joined #asahi
16:05delsol has joined #asahi
16:06sand4rt has quit [Ping timeout: 480 seconds]
16:11DarkShadow44 has quit []
16:11DarkShadow44 has joined #asahi
16:19delsol has quit [Remote host closed the connection]
16:35chrisl has quit [Ping timeout: 480 seconds]
16:42pb17 has quit [Ping timeout: 480 seconds]
16:53delsol has joined #asahi
17:03chrisl has joined #asahi
17:03delsol has quit [Remote host closed the connection]
17:03delsol has joined #asahi
17:07bdju has quit [Ping timeout: 480 seconds]
17:08pb17 has joined #asahi
17:11chrisl has quit [Ping timeout: 480 seconds]
17:22bdju has joined #asahi
17:35xal has quit [Quit: bye]
17:37bdju has quit [Ping timeout: 480 seconds]
17:44bdju has joined #asahi
17:51delsol has quit [Remote host closed the connection]
18:04DarkShadow44 has quit []
18:05DarkShadow44 has joined #asahi
18:06DarkShadow44 has quit []
18:07DarkShadow44 has joined #asahi
18:07chrisl has joined #asahi
18:15chrisl has quit [Ping timeout: 480 seconds]
18:32pb17 has quit [Ping timeout: 480 seconds]
18:40pb17 has joined #asahi
18:47Yachtie has quit [Ping timeout: 480 seconds]
18:54anarsoul has joined #asahi
19:01chrisl has joined #asahi
19:05anarsoul has quit [Quit: ZNC 1.9.1 - https://znc.in]
19:06anarsoul has joined #asahi
19:09chrisl has quit [Ping timeout: 480 seconds]
19:22sand4rt has joined #asahi
19:48Yachtie has joined #asahi
19:59vx has quit [Quit: G-Line: User has been permanently banned from this network.]
19:59vx has joined #asahi
20:00sam_ has quit [Quit: ZNC - http://znc.in]
20:01chrisl has joined #asahi
20:02delsol has joined #asahi
20:08Sebastian2 has joined #asahi
20:09chrisl has quit [Ping timeout: 480 seconds]
20:10aszeszo has joined #asahi
20:15harlock59 has joined #asahi
20:16harlock59hello i installed asahi on imac m1 but the maic keyboard and magic mouse don't work with asahi
20:18harlock59i have an old version of asahi, is that bug now fixed with new versions ?
20:20nicolas17hmm I don't know if bluetooth pairing sync is working yet
20:20Sebastian2 has quit [Quit: Sebastian2]
20:20nicolas17you may need to pair it as if it was a new, non-Mac computer
20:21harlock59do i have to use a pc usb keyboard and try bluetootoothctl ?
20:22harlock59bluetoothctl
20:24ddxtanx has quit [Remote host closed the connection]
20:25nicolas17what doesn't work?
20:25harlock59i can't type or move mouse cursor on asahi
20:26harlock59keyboard and mouse
20:26nicolas17the iMac is listed on the wiki as "Keyboard: -" because the iMac doesn't *have* a built-in keyboard, that's a laptop thing :P
20:27nicolas17connecting a USB keyboard should work
20:27harlock59so asahi only works with laptop macs ?
20:28harlock59can i pair the magic bluetooth keyboard after that ?
20:29nicolas17it should be possible like on any Linux or Windows computer, maybe you need to put the keyboard in pairing mode somehow?
20:31jannauharlock59: connecting the apple keyboard via usb will work. the mouse would work as well if not apple
20:32harlock59ok so i have to use a pc mouse ?
20:33jannauthere is asahi-btsync which is not fully integrated
20:34jannauI think it's not installed by default so you have to install it first
20:36harlock59what is the package manaer on asahi linux ?
20:36jannauafter that it's sudo `systemctl stop bluetooth.service; sudo asahi-btsync sync; sudo systemctl start bluetooth.service`. unfortunately it's still not working after that. you have to connect to the devices once manually
20:36nicolas17jannau: oh the Apple keyboard works as a normal HID keyboard over USB?
20:36harlock59is it apt or pacman ?
20:37jannaunicolas17: as out of spec HID keyboard
20:37j`eyharlock59: are you using fedora or arch?
20:37nicolas17seems my googling got confused with info about the *iPad* magic keyboard which is a different beast
20:37harlock59no asahi linux
20:37j`eyasahi linux isn't really a separate thing
20:37j`eywhen did you install?
20:38j`eyor just type "uname -a" at a terminal
20:38harlock59but is there a package manager on asahi linux ?
20:38harlock59i installed it two years ago
20:39harlock59so it is sudo dnf -i asahi-btsync ?
20:39nicolas17j`ey: wouldn't Discover work as a frontend for either anyway? :)
20:40j`eyno idea
20:40sam_ has joined #asahi
20:40nicolas17(works fine on Fedora but I don't remember if it was working on Arch-asahi)
20:40sam_ has quit [Remote host closed the connection]
20:41harlock59on arch-asahi it should be sudo pacman -Syu asahi-btsync
20:42jannau2 years ago is probably archlinuxarm. I don't think we ever packaged the nvram utils there. you're probably better of backing up your data (if any) and reinstall fedora-asahi-remix
20:42sam_ has joined #asahi
20:44harlock59i have no data on asahi sinc i've never been able to use neither keyboard nor mouse
20:48harlock59the speakers and the microphone still don't work with fedora-asahi-remix on imac m1...
20:51nicolas17the built-in microphone doesn't work on any Mac yet, but there was recent progress on that
21:01harlock59 has quit [Quit: Page closed]
21:03sand4rt has quit [Ping timeout: 480 seconds]
21:42Yachtie has quit [Quit: Yachtie]
21:58delsol has quit [Remote host closed the connection]
22:12pb17 has quit [Ping timeout: 480 seconds]
22:20Juest has quit [Read error: Connection reset by peer]
22:21Juest has joined #asahi
22:25chrisl has joined #asahi
22:26pb17 has joined #asahi
22:30jawmare has joined #asahi
22:30jawmareSystem Monitor (ksystemstats) keep crashing, where does bug report go?
22:32fl0_idjawmare to kde I guess? or "it depends"
22:33chadmed has quit [Quit: Konversation terminated!]
22:33chadmed has joined #asahi
22:34ayn2op has joined #asahi
22:34fl0_idif you are sure it's an asahi issue, then to the relevant repo. like asahi-linux if it's a kernel issue. (https://github.com/AsahiLinux/linux/issues) if it's not, then wherever the issue is. Sorry if that is not very helpful, but you'd really have to find out where the issue is first. Like f.e. what error messages are there if you start ksystemstats from the terminal?
22:35ayn2op has quit []
22:36jawmare@flo_id Got it. so the order is Asahi -> Fedora -> upstream i guess
22:38jawmareyep, 493093 is the bug, ksystemstats daemon
22:38batman has joined #asahi
22:38batmanHello everyone! I am new to the project and I want to contribute, where do I get started?
22:41batman has left #asahi [#asahi]
22:43Halian has quit [Ping timeout: 480 seconds]
22:46Halian has joined #asahi
22:51jannaujawmare: no, that's a different issue. /proc/cpuinfo only contains processor related information on asahi systems
22:52DarkShadow44 has quit []
22:52Yachtie has joined #asahi
22:52DarkShadow44 has joined #asahi
23:07charnam has joined #asahi
23:07charnamhello. i was here at one point not too long ago, and i'm back with more information about the issue i was facing
23:08charnambasically, applications on my system were randomly crashing, as well as ksystemstats creating at least 10 notifications as i logged in after upgrading my system to the newest version
23:09charnamnow, i've tried starting a plasma session, starting firefox from a TTY, and then looking in the tty console for whatever errors appear when firefox crashes. i'm usually able to get it to do that by zooming in, under certain circumstances
23:09charnamit gave me some things about memory issues. i don't believe it would be the computer itself's fault, but i'm not opposed to testing that, since nobody else here seems to have even heard of this issue
23:10charnams/memory issues/memory allocation issues
23:11jawmarewe were just talking about ksystemstats
23:12charnamoh, really?
23:12jawmareyeah, right before you joined
23:12charnamsimilar crashes? or what
23:13charnaminteresting
23:13charnamwell in that case, they're probably unrelated
23:13charnambut they both started happening after i upgraded to plasma 6
23:13charnamor, to be more specific, a newer version of Asahi
23:13jawmareplasma 5 uses ksysguard
23:13jawmarediffernt backend
23:14jawmare(I like it more than the new system monitor)
23:15jawmareanyways, lets move on to firefox
23:15charnami can type out the errors i saw here. i took pictures of it but i wasn't able to copy the text (since it was in a TTY) and i don't feel like getting the error to happen again. should i just type that here, or in a paste service? can't share the pictures themselves for privacy reasons
23:16charnamoh, also, when firefox crashed, it also closed chromium, which i had open at the same time. if i ran it in konsole and got it to crash, konsole would close as well
23:17charnamand i know that because of the picture i took. is that all the information needed?
23:18jawmareis it systemd oom or kernel oom?
23:18charnamnot sure how to tell but i'm seeing phrases like "IOCTL" "Cannot allocate enough memory (handle=...)" -- would this be kernel?
23:20jawmareyeah thats kernel oom killer kicking in
23:21charnamwould a swap file fix this, or is kernel a more severe thing?
23:22charnami mean, i've never had this issue before, and i've been able to open several instances of different applications without (too many) problems
23:23jawmarethere is something spooky going on, either its firefox memory leak, or somehow oom killer too eager to kill processes
23:23charnamwell unfortunately i can't see my memory usage anymore because of ksystemstats not working anymore
23:24jawmareim not 100% but the memory usage readout should be correct
23:25charnaminteresting, i can try to put it back in that case. i just removed all of the monitors since none were working
23:26charnami click on the memory usage widget and plasmashell crashes, that's great
23:27charnamand yeah, now i can see i'm using a little bit more memory than i should be. that's probably why i'd never encountered this issue before, honestly
23:27jawmareor you can use top to monitor memory usage
23:27PaulFertser_There's also an issue where OOM does something nobody can explain yet, without any apparent memory pressure and with enough swap...
23:29charnamjawmare: i could also use top, but it's just inconvenient since it's not going to stay on my screen unless i put it on top, and then it's taking up more screen space than it should
23:30charnamPaulFertser_: interesting. maybe it's related, hopefully it gets looked into
23:30PaulFertser_Full OOM kernel messages contains all the information about userspace processes and the amount of memory they used, no need for top or other ways of monitoring memory usage really, full kernel log should be enough.
23:31PaulFertser_Do you also get OOM with kernel-level allocation of order=0?
23:34charnami'm not sure how to do that
23:34charnamyou want me to post the output of dmesg?
23:35PaulFertser_You can even just do something like "sudo dmesg | nc termbin.com 9999"
23:35charnamthat likely wouldn't give you any information on my crashes since i don't believe any have happened since i've booted. would you still like me to do it?
23:35PaulFertser_Post a link to a pastebin (any you like) containing your dmesg, yes.
23:36PaulFertser_No, from the previous boot.
23:36PaulFertser_You can request logs for the previous boots with journalctl.
23:36charnami'm sorry, i don't have experience with these things. do you have an example?
23:37PaulFertser_If the crashes were the previous boot, "journalctl -b -1" should show full log from that. If it was the one before previous, -b -2 etc.
23:37PaulFertser_You need root permissions there to run journalctl and see kernel messages.
23:39charnami see. it looks like the output contains some private information (like filenames only i should be knowing), i can post specific parts if you'd like though. i found the part where it killed firefox due to a memory issue
23:40PaulFertser_You can add -k option to see only the messages from the kernel.
23:41charnamyes, i believe that's what i was just looking at. i'll post that part then
23:43charnamif this isn't the correct part i can find another relevant one
23:47PaulFertser_charnam: so yes, same weird symptoms: (GFP_KERNEL), order=0
23:47charnaminteresting #3
23:48PaulFertser_Haha, proc_pid_cmdline_read() is the function you wouldn't expect to cause OOM
23:48lena6 has joined #asahi
23:48ten1572377432463050661821503 has quit [Remote host closed the connection]
23:48ten1572377432463050661821503 has joined #asahi
23:49charnami haven't got much experience with the linux kernel, so i don't know what that command is
23:49PaulFertser_What kernel do you normally use?
23:50charnam[ LAUGH TRACK ]
23:50charnamno, i mean i just don't know how kernels work, that's all
23:50PaulFertser_(I think it's the function called when an app reads a file like /proc/1/cmdline )
23:50charnami don't know technical details
…