#
…

2022-03-15

00:07mrkajetanp has quit [Ping timeout: 480 seconds]
00:10yuyichao has quit [Ping timeout: 480 seconds]
00:16al3xtjames3 has joined #asahi
00:16al3xtjames has quit [Read error: Connection reset by peer]
00:16al3xtjames3 is now known as al3xtjames
00:33hendry has quit [Quit: WeeChat 3.4]
00:33hendry has joined #asahi
00:44zamadatix has joined #asahi
00:48zamadatixIs uninstall to do a clean slate re-install as simple as clearing out the volume or are there more steps to do it properly?
00:50zamadatixwow full guides this stuff is getting fancy ;). Thanks!
01:13mrkajetanp has joined #asahi
01:17zamadatix has quit [Quit: Page closed]
01:19damien_vancouver has joined #asahi
01:34creechy has quit [Remote host closed the connection]
01:35creechy has joined #asahi
01:56creechy has quit [Ping timeout: 480 seconds]
01:59hizon has joined #asahi
02:11creechy has joined #asahi
02:19yuyichao has joined #asahi
02:19creechy has quit [Ping timeout: 480 seconds]
02:47creechy has joined #asahi
02:50kreechy has joined #asahi
02:54catlover999[m] has joined #asahi
02:55creechy has quit [Ping timeout: 480 seconds]
03:00riker77_ has joined #asahi
03:02riker77 has quit [Ping timeout: 480 seconds]
03:02riker77_ is now known as riker77
03:20phiologe has joined #asahi
03:23PhilippvK has quit [Ping timeout: 480 seconds]
03:29kreechy has quit [Quit: WeeChat 3.4]
03:59chadmedhttps://github.com/chadmed/asahi-audio <-- if anyone wants to test this, thatd be nice
03:59chadmed(ive made changes to the FIRs since the last bunch, these ones are a bit nicer
04:00chadmedalso theres an installer script that does everything automatically for you
04:05kov has quit [Quit: Coyote finally caught me]
04:05kov has joined #asahi
04:16jochum_ has joined #asahi
04:18jochum has quit [Ping timeout: 480 seconds]
04:20marvin24_ has joined #asahi
04:24marvin24 has quit [Ping timeout: 480 seconds]
05:09bluetail[m]chadmed: The DSP will only apply to the internal speakers, right? If I were to use a interface, it wouldn't receive the changes, right?
05:23marcaneither way the way this is done now isn't likely to be the way we actually do it in the long term
05:25chadmedi mean all that really needs to change is for pipewire and wireplumber to actually provide features we need, like hiding an interface
05:26chadmedi dont see an issue long-term with the architecture of this setup other than its not totally seamless to the end user, which again is just pipewire/wireplumber lacking features
05:28chadmedi watched the entirety of kiagiadakis's presentation on managing streams via wireplumber scripts and nothing it can do is really what we want which really sucks
05:58gladiac has joined #asahi
06:13the_lanetly_052 has joined #asahi
06:34the_lanetly_052 has quit [Ping timeout: 480 seconds]
07:26marcanyeah, that's what I mean, we need pw/wireplumber feature changes to automate it
07:27marcanand ideally the DSP description should be somewhat decoupled from that single sound system
07:27marcanthe problem we're trying to solve here isn't "decent audio for macbooks", it's "linux still doesn't have any kind of database/configuration system for speaker DSP at all"
07:47bluetail[m]It’s a privilege to converse with you all. Love you.
07:53tmlindmps: i configured my m1 air lid open/close with the busybox acpi scripts along what pmos does for n900 slider, see the files at http://muru.com/linux/m1/etc/
07:54tmlindmps: afaik the acpi.map works only if busybox is started as acpid
07:55tmlindnot sure what's the best way to deal with this for other distros that don't use busybox acpid
08:01MajorBiscuit has joined #asahi
08:14mpstmlind: yes, that is how I do set events handlers for different things on my machines, and I think it is right method for busybox acpid
08:16mpstmlind: interesting thing is that I also set nearly same scripts for slider on n900
08:18mpstmlind: other (non busybox based) distros uses acpid2 package, and it is added in alpine few months ago (so also in postmarketOS) so it can be also used but the config is different
08:19mpsyou are using pmOS on M1 or alpine?
08:20mpstmlind: ^
08:21mpson alpine busybox acpid applet is symlink to busybox and it is started by default after alpine is installed with setup-alpine
08:23tmlindmps: no, just plain alpine but using the pmos n900 slider config
08:23tmlindmps: hmm yeah i just untarred and run some parts of the setup scripts..
08:26mpstmlind: I started writing guide about using acpi.map and scripts about events handling with BB acpid about year ago but didn't finished yet
08:26mpsas usual, I don't finish much of my writings :)
08:46ChaosPrincess has joined #asahi
08:47OwOwA has joined #asahi
09:22tmlindmps: well at least the events are somewhat documented in that pmos pull req
09:24tmlindanybody have experimental patches or info somewhere on the m1 backlight brightness?
09:24tmlindother than the 0 and 1 values that is :)
09:25tmlindok, maybe it's some pmic pwm controller?
09:26firefox317tmlind, nope its controlled by the dcp, if you are talking about the backlight of the screen
09:27tmlindfirefox317: ok yeah the lcd backlight brightness
09:29firefox317tmlind, yep so thats controlled by the dcp. We do have an initial driver for dcp written by alaysa and jannau, so it might not be to hard to add the required functionality
09:29Major_Biscuit has joined #asahi
09:30tmlindfirefox317: ok, additionally to dcp, i guess it could be there is some lcd bridge chip or i2c device too with pwm and dcp only controls the gpio for the bridge?
09:34bluetail[m]Is it possible to automatically connect to Bluetooth devices once they are visible? On macOS itself it isn’t, only through Automator.
09:34j`eyBT doesn't work yet
09:34bluetail[m]but given bt isn’t yet supported…
09:34bluetail[m]I know. But would it be technically possible?
09:35MajorBiscuit has quit [Ping timeout: 480 seconds]
09:35bluetail[m]scenario is pretty straightforward. Capturing MIDI
09:35psykosemacos can't autopair once you turn on a device?
09:35psykose(without extras)
09:36bluetail[m]It isn’t possible
09:36psykoselol, both linux and windows and phones and .. support that
09:36bluetail[m]you have to have Ministudio open and click a connect button each time and once connected leave the device on always
09:36bluetail[m]its stupid
09:37bluetail[m]midi studio *
09:39j`eymy BT headphones re connect automatically
09:40OwOwA has quit [Ping timeout: 480 seconds]
09:42bluetail[m]They do? Perhaps this only applies to non audio devices like MIDI KEYBOARDS
09:43firefox317tmlind, yeah that might be the case indeed. The only interface we can see is the dcp, so how it actually controls the backlight is a black box and also doesnt matter anyway
09:43bluetail[m]My Roland fp30 can’t connect to a device itself. Instead another device has to connect to it for comms
09:46bluetail[m]j`ey: A Thomann.de salesperson probably will tell me I would require to instead use the usb cable or get some weird usb device that allows to be programmed to auto connect the bit midi itself and transmits to the Mac.
09:46mpsI guess backlight could be in some registers which control PWM in mvram
09:47bluetail[m]that isn’t an option cause the Mac is 6m away. I know I could also hide a raspberry nearby but it would mean more clutter
09:50sheepgoose_ has quit [Ping timeout: 480 seconds]
10:08kameks has joined #asahi
10:10tmlindfirefox317: yeah sounds the lcd backlight brightness is hidden in the dcp firmware then
10:40myon9821 has joined #asahi
10:41myon98 has quit [Ping timeout: 480 seconds]
10:42chadmed has quit [Ping timeout: 480 seconds]
10:52chadmed has joined #asahi
11:23PaterTemporalis has joined #asahi
11:26shenki has joined #asahi
11:29hizon has quit [Remote host closed the connection]
12:23jn has quit [Read error: Connection reset by peer]
12:24jn has joined #asahi
12:37apg has joined #asahi
13:14apg has quit [Quit: Leaving]
13:41zopieux has quit [Ping timeout: 480 seconds]
13:42yuyichao has quit [Ping timeout: 480 seconds]
13:43zopieux has joined #asahi
13:55matthewayers[m]chadmed: the readme for asahi-audio is priceless :)
13:59kameks has quit [Ping timeout: 480 seconds]
14:02yuyichao has joined #asahi
14:10Glanzmannkov: Just saw your comment about d-i. Have to test it. Will fix it. Btw. did the dm-crypt work for you?
14:11kovGlanzmann, yes! installed debian on a friend's Air with it this weekend, thank you!
14:12kovhe was a bit too eager and selected 'use the entire disk' though, so a DFU restore had to be performed xD
14:15bluetail[m]matthewayers: I think so too. It’s a good thing to share.
14:17mpsdoes anyone know how to disable boot on keypress or lid open on macos 12.1
14:17mpsand remove chime on boot
14:18j`eyremoving the boot chime is via system prefences > audio, 'play startup sound'
14:18j`eysomething like that
14:18mpsj`ey: ah, thanks. (I tried with nvram, heh)
14:26marcanGlanzmann: < kov> he was a bit too eager and selected 'use the entire disk' though, so a DFU restore had to be performed xD <- FYI, this is the kind of thing why I'm not going to add your installer to the list until we have an "user-contributed, unsupported" heading for them
14:26marcanI'm happy to add user-contributed images, but people need to understand they are not supported by the project nor do we vouch for them
14:29kovmarcan, tbf I think Glanzmann's installer image is not d-i, it should be a lot safer, we used d-i because we wanted encryption and I believe that is not possible atm with the debian rootfs approach
14:29marcanah, I thought it was his guide
14:31kovmarcan, his guide has 3 pieces, the asahi installer one, which does simple partition creation + rootfs unpacking, a debian live one, which I use as my usb rescue boot whenever I break something, and a debian installer image for anyone who wants to do their own custom installation
14:33kovmarcan, that said I understand having the user-contributed thing, especially after reading your post on being very careful with the user's system
14:41Glanzmannkov: Uh abot the 'DFU restore' part ...
14:43Glanzmannmarcan: As kov explained I have currently 4 different methods of installing Debian in the wiki. The preferred method is using your asahi installer and does more or less the same thing you do for alarm.
14:44marcanstill, hope you see where I'm coming from here
14:44Glanzmannkov: If you feel comfortable about adding debian to the installer_data.json with whatever heading you like to that would be nice, but if not, I'll just provide a copy of your installer with the edited json as long as it helpful like it currently is.
14:44Glanzmannmarcan: Of course, I got the point.
14:45Glanzmanns/kov/marcan/g
14:46Glanzmannmarcan: At the moment i see from the logs that 3-7 people install Debian using the asahi installer.
14:52leah2actually it's one person that fucks up their system a lot *duck*
14:53Glanzmannleah2: Nope, I see the different IPs. Some come per v4, some per v6 from different parts of the world.
14:54opticronGlanzmann, ah, nice stats! that's higher than I'd expect at this stage
14:54mpsGlanzmann: you spy on your users ;p
14:54opticronand 2 were me :D
14:55eroux has quit [Remote host closed the connection]
15:02Glanzmannopticron: 61 users total, two of them is me: https://pbot.rmdir.de/VmTWVX7aC7MBl6fQT56nKA
15:02GlanzmannThat is for the asahi installer.
15:14eroux has joined #asahi
15:14mpsso, also asahi installer spies on users?
15:15svenpretty sure that's Glanzmann's server logs
15:15immychan[m]Basic data collection =/= spying
15:15mpsimmychan[m]: it is
15:16danielsmarcan: Wayland has 32-bit keycodes …
15:17mpsimmychan[m]: I worked some years with GDPR people and learned that any unnecesary data collection is spying, be it intentional or not
15:17sveni don't necessarily agree, but depending on which lawyer you ask GDPR possibly already defines an IP address as personally identifiable data fwiw
15:17mpssven: yes
15:17marcanFWIW the Asahi CDN logs are properly anonymized for GDPR compliance
15:18mpspersonally I don't care, so Glanzmann you are free to spy on me :)
15:21creechy has joined #asahi
15:25danielsmarcan: and yeah, anything using xkbcommon (not the X server) can do overlays, but ideally for common things they’d be upstream in the common definitions, not in random downstream
15:25danielsmarcan: what specifically did you have in mind?
15:26marcanthere's no sane jp(mac) keyboard layout for one, everything upstream is broken in some way
15:26marcaneither capslock is wrong, or it's kana, or it doesn't have a backslash key
15:26marcandepending on how you do it
15:27marcan(it's also extremely confusing how the layouts and the symbols for the applealu stuff interact)
15:27marcanoh and the eisuu/kana keys are wrong most of the time too
15:28danielsyeah, that should be fixed for sure
15:28danielsis applealu actually still completely compatible up to M1?
15:28marcanI'm not entirely sure what applealu is supposed to be :-)
15:29danielspresumably AlBook era?
15:29danielsistr they changed the layouts about then
15:30marcanthe whole thing is very confusing
15:30marcanlike apparently applealu_jis with jp means macintosh_vndr/apple(alukbd)+macintosh_vndr/jp(usmac)+macintosh_vndr/jp(mac):2
15:31danielsyeeeeah. it’s not the nicest.
15:32danielsso alukbd will presumably map the core symbols and modifiers, then US on level 1, then JP on level 2
15:32marcanthe only useful thing alukbd does here is fix capslock. unfortunately, "usmac" does not have backslash, so it's useless
15:33marcanit also doesn't fix kana/eisu, which are the alujiskeys patch
15:33marcanthat is this part I guess?
15:33marcanrules/0026-evdev.m_s.part: applealu_jis = +inet(evdev)+macintosh_vndr/jp(alujiskeys)
15:34marcanbut yeah, without backslash, it's obviously not usable
15:34marcanof course the keyboard *physically* has no backslash, but that's only because Apple is stupid
15:35marcanon macos you can toggle ¥ into typing \, and get the other one with option+, except the terminal always defaults to backslash, which is a mess
15:35danielsah, that's interesting
15:35marcanhere in the real world, either ¥ is always backslash (JIS style, jp(106) in xkb) or ¥ is ¥ and backslash is the unshifted underscore key (which is how it is labeled in OADG109A keyboards, jp(OADG109A) in xkb)
15:35marcanbut neither of those layouts has a mac variant
15:36marcanjp(mac) is... kana mode
15:36danielsI was going to say - and this is absolutely not to deflect from how shit the XKB rules syntax is - that one of the biggest problems is that people look at keyboards and say 'this is obviously dumb as hell, the correct thing to do is $thing, no-one else could ever possibly want anything else'
15:36marcanwhich is ridiculous and almost nobody here uses for anything
15:36danielsthen before you know it we have multiple layouts for Icelandic Dvorak
15:37danielsanyway, what you want to do is to ignore the part files, and just look at build/rules/evdev
15:37marcanwell, considering xkb can't magically do the nonsense macOS does, the next best thing is make the special keys do the right thing and then let users pick between 106 and OADG109A modes, which is what they'll be used to from other machines anyway
15:38danielsI mean you _can_ make it do that
15:38marcanmake it do a different thing in terminal apps?
15:38danielsyou cannot do that, no :P
15:39marcanyou know this is all microsoft's fault, right?
15:39danielsI meant wrt Option acting as a secondary shift for defined keys
15:39marcanwhere even in unicode mode, to this day, \ renders as ¥ if you have a japanese locale
15:39danielsI have to admit I'm not well-versed in history or use of Japanese keyboards
15:39marcanso most japanese people don't *know* what a backslash is
15:39danielsdealing with European keyboard politics was enough to make me abandon input
15:39marcanand I get emails with currency denominated in backslash
15:40marcanapple tries to do the right thing in the OS with font rendering, but the keyboard is still weird because of this
15:40danielsbrilliant
15:42danielsso, looking at build/rules/evdev, you end up with keycodes/evdev + macintosh_vndr/macintosh(jisevdev) which just fixes kana and is harmless
15:43danielsthen you end up with symbols/macintosh_vndr/jp(usmac), where usmac does everything correctly _but_ it also overrides AE13 -> [yen,bar], and you'd like it to be [backslash,bar] right?
15:43Glanzmannmps: I'll never spy on me, because I only have debian images in my server.
15:43Glanzmanns/on me/on you/g
15:45marcandaniels: the problem is replace key <AB11> { [ underscore ] };
15:45danielsmarcan: oh?
15:45marcanthat was originally key <AB11> { [ backslash, underscore] };
15:45marcanwhich is the OADG109A version
15:45marcanhowever, some people might prefer the AE13 -> backslash,bar version
15:45marcanwhich is what jp(106) does
15:46marcan(which is actually the default)
15:46marcanmy normal PC keyboard is OADG109A, most are these days
15:46marcanso if you want what's printed on the keycaps on the vast majority of machines today, you want that
15:46marcanhowever, jp(106) is the default because microsoft
15:47marcanand then apple kind of went with JIS plus that option hack, but most Linux users probably would rather have either of the above two modes
15:47danielsmm, I was going to say 'but if you're using your normal PC keyboard then just use the evdev model, not the mac model'
15:47marcanespecially considering the _ key having no shifted variant is completely silly
15:47danielsbut I'm assuming you're going to counter here with 'I'm actually using both'
15:47danielsin which case, yeah, you have to pick one and eat the cognitive dissonance
15:47marcanI mean, I'm talking about people coming from the PC world
15:48marcanif you want to do what macos does then we need the option thing, but then that kind of clashes with the whole "macos doesn't do keybindings like linux does"
15:48danielsas someone who types US on a UK keyboard, I can sympathise with ignoring the keycaps
15:48marcanand if you want to fix *that* you need userspace daemons (which is how people actually do it)
15:49marcanbut given we can't do that in xkb, I argue the reasonable thing to offer by default is "provide a layout that matches the keycaps without trying to do fancy third level shifts that don't fit into the standard linux modifier model, and stick backslash somewhere sane"
15:49marcanwhere the two options for "somewhere sane" are replacing ¥ or putting it where it would be on every other PC keyboard
15:53marcandaniels: there's also the Fn thing, any ideas about what to do with that?
15:54marcanthe driver properly reports it in evdev, and also synthesizes Fn+top bar = Fxx keys, and Fn+arrow keys = paging/home/end keys in-kernel (although that can be disabled)
15:54marcanthe latter is probably a decent idea given that having those keys missing kind of sucks, and most people wouldn't want to do anything else there
15:54marcanbut that still leaves Fn+everything else unused
15:54marcanproblem is evdev Fn is >255 so Xorg can't see it
15:56danielsonce you've built and installed xkeyboard-config, you can use xkbcommon's tools to poke at it, e.g. /build-x86-64/compile-keymap --include ~/x/xkb/xkeyboard-config/foo/usr/local/share/X11/xkb --rules evdev --model applealu_jis --layout jp --option apple:jp_oadg109
15:56marcanpc106 should be AE13
15:56daniels(or some of the other ones to test)
15:56danielsah yeah, good point
15:56danielsas for 'what about Fn?', there are two options
15:57danielsthere are a few (laptop mainly) HID specials in the kernel which fake up the relevant keycodes for you by handling Fn, much like up/down
15:57marcanfwiw I had already done the ~same thing except as layout variants instead of options :-)
15:57danielsthey get away with that because they're all multimedia keys, which have no interaction with modifiers etc
15:57marcanbut it's in a git repo that is in a machine that's not booted right now
15:58danielsusually for stuff like that you try to stick it as options rather than variants; you can only have a single variant active at a time, so most 'I want this thing, but with this one small tweak' go in as options
15:58marcanyeah, makes sense
15:58marcanthe only remaining confusing thing is jp(mac) has, if nothing else, a terrible name
15:58marcanit should probably be called "Japanese (Macintosh, Kana)" or something
15:59danielsback to Fn - if you can fake up a fixed set of multimedia keys in the kernel, then great - if not then you're in to adding a new keytype, which definitely gets a little bit fun within XKB. but Wayland can handle it completely perfectly, it's only Xorg-native stuff that struggles
15:59danielsand, well, easy fix for that
15:59marcanbecause right now if you select it ンラナ トカチスカ カンセニミキ リニノイ カクニト
15:59marcan("you start typing like this", no, that is not legible in japanese either)
16:00marcan(I actually don't know and have never met any japanese computer users that use kana mode)
16:02danielsyeah, steering people towards better defaults, and giving them better prompts to work with, is definitely doable
16:03marcanso Fn, the HID codes the top row reports are indeed Fx, but the keycaps say they are actually media keys unshifted and F-keys with Fn, though on macOS you can swap them if you want
16:03marcanthe hid-apple driver does the same, defaulting to mapping to media keys unshifted and Fx with Fn, but you can swap it via module arg, or disable the conversion entirely
16:04danielsmy XPS randomly flips between whether media or Fx is the unshifted mode, which is always a pleasure
16:04danielsanyway, I would file an issue/MR on xk-c with something that steers people by default to something as close to possible as what macOS does ootb, with a note about the backslash-happy variants, and then following that notes and opinions about the various modes
16:05daniels'I have looked at a keyboard and I have ideas on a better way to do things' is usually not the best start in that repo; 'here's what the native OS does on that device and this gets us as close as practically possible to it, with an explanation of the tweaks' is A+++ merge on sight
16:05marcanI mean, I think I got close to option #2 in this conversation? :)
16:06danielsyep! exactly, just suggesting how to frame it
16:06danielslmk if you need any more eyes on XKB stuff, or a shoulder to cry on
16:07marcanhaha, sure :)
16:08marcanand then I need to hack up calamares to preconfigure the keyboard model properly on the macbooks... which is also going to require some extra devicetree shenanigans to forward the layout from the ADT... (as we just confirmed in #asahi-dev)
16:11kettenisI don't think any of the spi/hid/keyboard/touchpad stuff was submitted updtream yet, is it?
16:12marcanwell, the spi controller was
16:12marcanbut not merged yet
16:21mpsGlanzmann: no worries, I'm just kidding a little
16:29brentr123[m]anyone know if asahi alpha is ready?
16:30immychan[m]Depends what you mean by “ready”
16:30j`eybrentr123[m]: it isnt
16:31j`eybrentr123[m]: there will be an announcement
16:43coderobe has quit [Remote host closed the connection]
16:55brigarian[m] has joined #asahi
16:57brigarian[m] has left #asahi [#asahi]
17:12marcanPSA: pushed a m1n1 bugfix that affects stage 1. I *could* work around it in stage 2, but this doesn't affect normal u-boot chainload cases yet. however, it will break SEP once we get there.
17:13marcanso if you were thinking of leaving your existing stage 1 lying around for months, might want to do one final update
17:13marcaninstaller has been updated (just m1n1, also sets the partition UUID in lowercase now)
17:20_jannau_would it make sense to pass the 1st stage m1n1 version to the 2nd stage?
17:21the_lanetly_052 has joined #asahi
17:24marcanI thought of doing that at some point
17:24marcanbut to be honest, it's probably not necessary
17:26Major_Biscuit has quit []
17:31Fabrcio[m] has joined #asahi
17:37mavericks5 has joined #asahi
17:41artemist has quit [Ping timeout: 480 seconds]
17:41mavericks has quit [Ping timeout: 480 seconds]
17:41mavericks5 is now known as mavericks
17:50Sellerie1 has joined #asahi
17:52Sellerie has quit [Ping timeout: 480 seconds]
17:52Sellerie1 is now known as Sellerie
17:58j`eymps: I didnt boot using uboot, but yes display worked
17:59mpsj`ey: could you post me kernel config?
17:59j`eymps: mine is too cut down to be useful, but all the same options should work
18:00mpsI upgraded m1n1 and u-boot to latest
18:00j`eyonly the sound drivers changed really
18:01mpsj`ey: I think I have to find proper FB and DRM combo
18:02j`eywhatever previously worked should still
18:02m6wiq has joined #asahi
18:03coderobe has joined #asahi
18:04mpshm, lets try
18:05Sellerie9 has joined #asahi
18:11Sellerie has quit [Ping timeout: 480 seconds]
18:11Sellerie9 is now known as Sellerie
18:16mpshm, no luck
18:18j`eymps: so you get the u-boot screen, and then after it boots the kernel it goes blank?
18:20Glanzmannmps: Rebuilding now and let you know if it works for me.
18:20Glanzmannj`ey: What's in todays forced update?
18:21j`eyGlanzmann: povik's sound branch
18:21j`eyand a few more s2idle fixes
18:21Glanzmannpovik / marcan: Does not build for me: https://pbot.rmdir.de/XcX6X2bbLOlCa7i9_-Zymw
18:21Glanzmannj`ey: I see, thanks.
18:22j`eyyou hae to build that into the kernel, not a module to fix that
18:22j`ey(until there's a proper fix)
18:23Glanzmannj`ey: by that you mean the sound stuff?
18:23povikCONFIG_SND_SIMPLE_CARD=y
18:24povikor wait a minute or two for me to post a proper fix
18:25mpsj`ey: yes, kernel starts but only got blank screen, led on caps lock works on/off by pressing key
18:30Glanzmannpovik: Thank you, that builds.
18:38Glanzmannmps: For me the new kernel works, including display output: https://tg.st/u/config-2022-03-15-4k
18:39GlanzmannFor the Debian users: curl -sL tg.st/u/ksh # for todays kernel
18:39GlanzmannI also updated all the other build artefacts.
18:39creechy has quit [Quit: WeeChat 3.4]
18:40opticronI like new kernels
18:40mpsGlanzmann: could you kernel config, please
18:40mpsGlanzmann: sorry, I see you posted it
18:41Glanzmannopticron: Tested on the macbook air.
18:41mpsGlanzmann: looks like you config is not for latest asahi merge
18:42povikproper fix for asoc_simple_parse_routing build error: https://tpaste.us/QN40
18:42Glanzmannpovik: With the new sound code, are speakers supposed to work on the air? I just builded using this config: https://pbot.rmdir.de/Vuq52wIhK_E4u3HY2pDzXw
18:42mpspovik: thanks
18:43Glanzmannmps: Second half of the sentence was for you. https://pbot.rmdir.de/Vuq52wIhK_E4u3HY2pDzXw
18:44Glanzmannpovik: Audio jack works.
18:45povikthey are supposed to be ignored unless you modify the DT source to enable them
18:45povikthat's on purpose until we make sure you can't damage them from userspace
18:45povikor at least not easily...
18:46povikin simple terms: we are missing amp gain limit
18:46Glanzmannpovik: I see, than I wait until you say its safe to use.
18:47Glanzmannpovik: Btw. I also noticed that the jack is very loud. I was just watching a netflix movie and I had to scale the volume down: https://tg.st/u/screenshot-air-2022-03-15-19_46_58.png
18:47___nick___ has joined #asahi
18:50Glanzmannpovik: In the old version the audio jack output control in alsamixer was doing something, but now I can change it to whatever I want and the output volume does not change: https://tg.st/u/screenshot-air-2022-03-15-19_50_05.png
18:50GlanzmannYou probably already know that, just in case you don't.
18:51Glanzmannmps: Yes, that is the log of the kernel build among other things with that config.
18:52the_lanetly_052 has quit [Ping timeout: 480 seconds]
18:54sheepgoose_ has joined #asahi
18:54matthewayers[m]Does anyone know how I can connect to internet using a captive portal and wpa supplicant?
18:56opticronmatthewayers[m], captive portals shouldn't matter to wpa_supplicant
18:56Glanzmannmatthewayers[m]: You open a browser and browse to log.me.in or blog.fefe.de
18:56opticronthat's all router-side stuff, so it just looks like a normal open or wpa[2] connection to supplicant
19:12Glanzmanndmesg for the new kernel, if someone wants to have a look. That is from the air: https://pbot.rmdir.de/pyLIO3MepRhInZu4Pi1sQw
19:14opticronI'm seeing a couple of: nvme0: Admin Cmd(0x6), I/O Error (sct 0x0 / sc 0xb)
19:14opticronthere were some different errors on the last kernel
19:15sventhat’s just a new print in the nvme code
19:15sventhat command always failed because apple’s not following the spec there and I never got around to add a quirk because there’s already a fallback
19:15opticronfair enough
19:16opticronI also see a few errors with the wifi, but those are the same as last kernel (and it still works just fine)
19:17opticronI can paste the exact text somewhere, but the summary is ...firmware: failed ot update device address ret -52, p2pdev: set p2p_disc error, ...add_iface: add iface p2p-dev-wlp1s0f type 10 fialed err=-52
19:18opticronman, my fingers really can't fing
19:19matthewayers[m]Looks like my 14” MBP cannot find the audio jack output device
19:19matthewayers[m]Any suggestions? I’m on Debian Bookworm
19:20Glanzmannmatthewayers[m]: Can you paste your dmesg to tg.st/p ?
19:20opticronI haven't tried audio on mine, but I have the same laptop
19:20opticronI'm mostly interested the speakers, but I guess I should poke the jack
19:20Glanzmannmatthewayers[m]: Install pavucontrol and alsamixer and umute everything that is mute.
19:21Glanzmannmatthewayers[m]: I need to press F6 to selec the second sound card.
19:24opticronyeah, I don't see a second device in alsamixer
19:24Glanzmannopticron: Strange. Can you paste your dmesg to tg.st/p ?
19:28Glanzmannpovik: Any idea why there is no sound on mbp 14"? https://pbot.rmdir.de/fZ2bCPrUGVFQSgUqQzjyJA
19:30Glanzmannmatthewayers[m]: Yours look very similiar to opticron. The sound card appears not to be detected. Maybe something with the device trees, maybe something else.
19:32povikbecause jack isn't supported on the 2021 macbooks (and speakers are behind that DT edit on your own risk)
19:33opticronyeah, I'll avoid destroying my speakers for the moment :D
19:33povikalthough i am surprised the card (although empty) isn't registered at all
19:33Glanzmannopticron: Just to verify, I thought you have the 2020 model?
19:34povik14" is 2021, t600x
19:34matthewayers[m]I have the 2021 14" Macbook Pro with M1 Max silicon
19:34GlanzmannOkay, I just saw it.
19:34opticronyeah, we both have the 2021 14"
19:34Glanzmannpovik: Thank you for the explanation.
19:34matthewayers[m]povik: Thank you for helping us not destroy our speakers :)
19:35povikmatthewayers[m]: haha, you're welcome!
19:49sheepgoose has joined #asahi
19:55sheepgoose_ has quit [Ping timeout: 480 seconds]
19:59gladiac has quit [Quit: k thx bye]
20:44m6wiq1 has joined #asahi
20:45m6wiq has quit [Ping timeout: 480 seconds]
21:08___nick___ has quit [Ping timeout: 480 seconds]
21:14s1gtrap[m]uh, I guess I screwed up when installing because now I have a full ext4 part with no way of extending it: can't be done from asahi, doesn't seem to be any tools for this on macos so unless there's bootable live media available somewhere?
21:15j`eyI guess its only 5g?
21:21Mary has quit [Quit: The Lounge - https://thelounge.chat]
21:21Mary has joined #asahi
21:22j`eyGlanzmann: do you have the `parted` steps for resizing?
21:23m6wiq1 has quit []
21:24s1gtrap[m]j`ey: I tried to figure this out earlier but couldn't be done w/o umounting
21:24s1gtrap[m]at least to my understanding
21:24Mary has quit []
21:25j`eyi think it can be done live
21:25Glanzmanns1gtrap[m]: The steps are in the wiki. You can also watch the video.
21:26Glanzmanns1gtrap[m]: If you want I can walk you through it. Can you run 'parted /dev/nvme0n1 print free' and paste the output to tg.st/p
21:27Glanzmanns1gtrap[m]: Btw, there is also a bootable live media: https://github.com/AsahiLinux/docs/wiki/Debia
21:27s1gtrap[m]ah ahh! using that as live media
21:27Mary has joined #asahi
21:28Glanzmanns1gtrap[m]: The resize can be done online.
21:28Glanzmanns1gtrap[m]: But there is also a Debian live image
21:28GlanzmannWhich can be used to do the resizing offline.
21:29s1gtrap[m]Glanzmann: I thought parting a mounted drive was a big no-no?
21:30Glanzmanns1gtrap[m]: I thought so, too. Until I found out that you can make it bigger without an issue.
21:30Glanzmanns1gtrap[m]: Steps are these:
21:31s1gtrap[m]yea, definitely giving this a shot: thanks!
21:32tpw_rulessgdisk -n 0:0 will also do that
21:32GlanzmannThere is a video of me doing this operation.
21:32Glanzmanntpw_rules: And you're telling us that now?
21:33Glanzmanntpw_rules: You always come up with nice commands. :-) You're the first how teached me how to stream tar a tgz disk image.
21:33GlanzmannI need to write that down.
21:33tpw_rulesmaybe you should read my guide :D
21:33Glanzmanntpw_rules: I did once. A lot of text.
21:34tpw_rulesi just redid it a couple days ago. i like words
21:39GlanzmannRebuilding Debian stuff to include 'gdisk'. Eta 5 minutes.
22:05nobodynada has joined #asahi
22:05nobodynada has quit []
22:36artemist has joined #asahi
23:15sheepgoose_ has joined #asahi
23:21sheepgoose has quit [Ping timeout: 480 seconds]
23:43ChaosPrincess has quit [Remote host closed the connection]
…