Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #263308 > unrolled thread
| Started by | Kent West <westk@acu.edu> |
|---|---|
| First post | 2023-11-09 21:50 +0100 |
| Last post | 2023-11-10 22:00 +0100 |
| Articles | 7 — 4 participants |
Back to article view | Back to linux.debian.user
Hardware Misses on MacBook Air M1 2020 Kent West <westk@acu.edu> - 2023-11-09 21:50 +0100
Re: Hardware Misses on MacBook Air M1 2020 "Marco M." <mm@dorfdsl.de> - 2023-11-09 22:00 +0100
Re: Hardware Misses on MacBook Air M1 2020 jeremy ardley <jeremy.ardley@gmail.com> - 2023-11-10 02:30 +0100
Re: Hardware Misses on MacBook Air M1 2020 Kent West <westk@acu.edu> - 2023-11-10 15:20 +0100
Re: Hardware Misses on MacBook Air M1 2020 Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2023-11-10 05:50 +0100
Re: Hardware Misses on MacBook Air M1 2020 Kent West <westk@acu.edu> - 2023-11-10 15:20 +0100
Re: Hardware Misses on MacBook Air M1 2020 Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2023-11-10 22:00 +0100
| From | Kent West <westk@acu.edu> |
|---|---|
| Date | 2023-11-09 21:50 +0100 |
| Subject | Hardware Misses on MacBook Air M1 2020 |
| Message-ID | <Hyk8p-4iYh-5@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
I have an M1-chip 2020 MacBook Air on which I have dual-booted with Debian 12 initially, then "upgraded" to sid (in hopes of getting better hardware support). It has several hardware ... glitches, and my google-fu is failing me in finding solutions. I'm hoping someone here can help. First, the good news: Basic functionality works fine. Both Gnome and Plasma work on both X11 and Wayland; graphics are crisp (albeit tiny, until I use the GUI's size-mag feature to bump it to about 175%), and both wired and wireless networking work, even with our certificate-based authentication wireless network, that I could never get to work with a version of Debian around 9 or 10 or so (but the connection is a little daunting for the average Joe). I can't really speak for Sleep/Hibernation, as I haven't had it running that long (UPDATE: It just announced it was automatically suspending as I was typing this; I suspect it'll wake when I try it in a few (UPDATE: Yes, it woke up instantly, perhaps too instantly?)), but screen time-out/wake-up works fine. Audio via my Bluetooth ear buds works great. Now the bad news: - keyboard backlight. Ag, how I need this in my usually-dark computing environs! - display brightness. It's either full-on or full-off. This is a much more minor concern. - audio. As mentioned above, audio works fine via Blluetooth (watched an interesting Adam Savage video about a $13 USB-c cable vs Apple's $130 version; I can't believe I'm saying it, but I think the Apple version might actually be worth that), but I can't get a peep out of the built-in speakers. Everything *seems* to be in order; alsamixer sees both the Pipewire device and the native Mac sound device; volume controls move up and down (or left/right); there's just never any sound. Not even from "speaker-test" after I've killed X/Wayland/gdm3, although "speaker-test" (as a non-root user) looks like it's working. It acts like the speakers are muted, but I can find no way to unmute them. When I run "speaker-test" as root, it complains that the service (server? device?) is not running/available? (Sorry; don't recall the exact message at the moment.) - Though not really a hardware matter, thought I'd mention this for anyone who wants to try Debian on their MacBook Air M1; when I updated to Sid, apparently the Mac got "confused", and when I tried to boot back into macOS, the system insisted on having my decryption password (which I guess is normal, now that I think about it, 'cause FileVault 2 does that also, just ... differently, so that I didn't recognize it), but then it also insisted on a Recovery Key being typed in (like when Bitlocker locks you out of Windows when it thinks the hardware has been tampered with). Thankfully I had that key available, or it would have been a wipe/reimage (or perhaps worse, the way Apple has locked things down of late). So if anyone has any help for these issues, especially audio and the keyboard backlight, I'm all ears. Thanks! Linux debian kernel 6.1.0-rc8-asahi #1 SMP Tue Dec 6 21:41:25 CET 2022 aarch64 GNU/Linux trixie/sid -- Kent West <")))>< IT Support / Client Support Abilene Christian University Westing Peacefully - http://kentwest.blogspot.com
[toc] | [next] | [standalone]
| From | "Marco M." <mm@dorfdsl.de> |
|---|---|
| Date | 2023-11-09 22:00 +0100 |
| Message-ID | <Hyki5-4j1r-19@gated-at.bofh.it> |
| In reply to | #263308 |
Am 09.11.2023 um 14:44:20 Uhr schrieb Kent West: > Not even from "speaker-test" after I've killed X/Wayland/gdm3, although > "speaker-test" (as a non-root user) looks like it's working. It acts > like the speakers are muted, but I can find no way to unmute them. > When I run "speaker-test" as root, it complains that the service > (server? device?) is not running/available? (Sorry; don't recall the > exact message at the moment.) Have you checked alsamixer for MM? Can you check which chip it is with lspci and which kernel module is loaded? What does dmesg say?
[toc] | [prev] | [next] | [standalone]
| From | jeremy ardley <jeremy.ardley@gmail.com> |
|---|---|
| Date | 2023-11-10 02:30 +0100 |
| Message-ID | <Hyovn-4lBz-1@gated-at.bofh.it> |
| In reply to | #263308 |
On 10/11/23 04:44, Kent West wrote: > I have an M1-chip 2020 MacBook Air on which I have dual-booted with > Debian 12 initially, then "upgraded" to sid (in hopes of getting > better hardware support). Out of curiosity, does Debian 12 support the M1 NPU (Neural Processing Unit) ?
[toc] | [prev] | [next] | [standalone]
| From | Kent West <westk@acu.edu> |
|---|---|
| Date | 2023-11-10 15:20 +0100 |
| Message-ID | <HyAwx-4t5q-7@gated-at.bofh.it> |
| In reply to | #263313 |
[Multipart message — attachments visible in raw view] — view raw
[Sorry; sent to Jeremy only the first time; meant to send it to the list.] Sorry, no clue. Don't even know how I'd ascertain that, but if you can give me a simple test, I'd be happy to try it for you. On Thu, Nov 9, 2023 at 7:22 PM jeremy ardley <jeremy.ardley@gmail.com> wrote: > > On 10/11/23 04:44, Kent West wrote: > > I have an M1-chip 2020 MacBook Air on which I have dual-booted with > > Debian 12 initially, then "upgraded" to sid (in hopes of getting > > better hardware support). > > > Out of curiosity, does Debian 12 support the M1 NPU (Neural Processing > Unit) ? > > -- Kent West <")))>< IT Support / Client Support Abilene Christian University Westing Peacefully - http://kentwest.blogspot.com
[toc] | [prev] | [next] | [standalone]
| From | Timothy M Butterworth <timothy.m.butterworth@gmail.com> |
|---|---|
| Date | 2023-11-10 05:50 +0100 |
| Message-ID | <HyrCV-4nqI-1@gated-at.bofh.it> |
| In reply to | #263308 |
[Multipart message — attachments visible in raw view] — view raw
On Thu, Nov 9, 2023 at 11:31 PM Kent West <westk@acu.edu> wrote: > I have an M1-chip 2020 MacBook Air on which I have dual-booted with Debian > 12 initially, then "upgraded" to sid (in hopes of getting better hardware > support). It has several hardware ... glitches, and my google-fu is failing > me in finding solutions. I'm hoping someone here can help. > > First, the good news: Basic functionality works fine. Both Gnome and > Plasma work on both X11 and Wayland; graphics are crisp (albeit tiny, until > I use the GUI's size-mag feature to bump it to about 175%), and both wired > and wireless networking work, even with our certificate-based > authentication wireless network, that I could never get to work with a > version of Debian around 9 or 10 or so (but the connection is a little > daunting for the average Joe). I can't really speak for Sleep/Hibernation, > as I haven't had it running that long (UPDATE: It just announced it was > automatically suspending as I was typing this; I suspect it'll wake when I > try it in a few (UPDATE: Yes, it woke up instantly, perhaps too > instantly?)), but screen time-out/wake-up works fine. Audio via my > Bluetooth ear buds works great. > > Now the bad news: > > - keyboard backlight. Ag, how I need this in my usually-dark computing > environs! > > - display brightness. It's either full-on or full-off. This is a much more > minor concern. > > - audio. As mentioned above, audio works fine via Blluetooth (watched an > interesting Adam Savage video about a $13 USB-c cable vs Apple's $130 > version; I can't believe I'm saying it, but I think the Apple version might > actually be worth that), but I can't get a peep out of the built-in > speakers. Everything *seems* to be in order; alsamixer sees both the > Pipewire device and the native Mac sound device; volume controls move up > and down (or left/right); there's just never any sound. Not even from > "speaker-test" after I've killed X/Wayland/gdm3, although "speaker-test" > (as a non-root user) looks like it's working. It acts like the speakers are > muted, but I can find no way to unmute them. When I run "speaker-test" as > root, it complains that the service (server? device?) is not > running/available? (Sorry; don't recall the exact message at the moment.) > > - Though not really a hardware matter, thought I'd mention this for anyone > who wants to try Debian on their MacBook Air M1; when I updated to Sid, > apparently the Mac got "confused", and when I tried to boot back into > macOS, the system insisted on having my decryption password (which I guess > is normal, now that I think about it, 'cause FileVault 2 does that also, > just ... differently, so that I didn't recognize it), but then it also > insisted on a Recovery Key being typed in (like when Bitlocker locks you > out of Windows when it thinks the hardware has been tampered with). > Thankfully I had that key available, or it would have been a wipe/reimage > (or perhaps worse, the way Apple has locked things down of late). > > So if anyone has any help for these issues, especially audio and the > keyboard backlight, I'm all ears. > Have you considered just running Debian in a Virtual Machine until hardware support matures. > Thanks! > > Linux debian kernel 6.1.0-rc8-asahi #1 SMP Tue Dec 6 21:41:25 CET 2022 > aarch64 GNU/Linux > trixie/sid > > -- > Kent West <")))>< > IT Support / Client Support > Abilene Christian University > Westing Peacefully - http://kentwest.blogspot.com > -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀
[toc] | [prev] | [next] | [standalone]
| From | Kent West <westk@acu.edu> |
|---|---|
| Date | 2023-11-10 15:20 +0100 |
| Message-ID | <HyAwx-4t5q-3@gated-at.bofh.it> |
| In reply to | #263320 |
[Multipart message — attachments visible in raw view] — view raw
On Thu, Nov 9, 2023 at 10:39 PM Timothy M Butterworth < timothy.m.butterworth@gmail.com> wrote: > > > On Thu, Nov 9, 2023 at 11:31 PM Kent West <westk@acu.edu> wrote: > >> I have an M1-chip 2020 MacBook Air on which I have dual-booted with >> Debian 12 initially, then "upgraded" to sid (in hopes of getting better >> hardware support). It has several hardware ... glitches, and my google-fu >> is failing me in finding solutions. I'm hoping someone here can help. >> >> <snip hardware issues> >> > > Have you considered just running Debian in a Virtual Machine until > hardware support matures. > I started to look at that yesterday, but apparently VirtualBox doesn't support the Mac's M1 chip, and QEMU looked a bit daunting on the Mac, so I gave up on that pursuit for now. The issues I'm currently having seem less painful to me than getting a VM up and running on the M1 Mac. -- Kent West <")))>< IT Support / Client Support Abilene Christian University Westing Peacefully - http://kentwest.blogspot.com
[toc] | [prev] | [next] | [standalone]
| From | Timothy M Butterworth <timothy.m.butterworth@gmail.com> |
|---|---|
| Date | 2023-11-10 22:00 +0100 |
| Message-ID | <HyGLD-4wAu-7@gated-at.bofh.it> |
| In reply to | #263333 |
[Multipart message — attachments visible in raw view] — view raw
On Fri, Nov 10, 2023 at 9:16 AM Kent West <westk@acu.edu> wrote: > > > On Thu, Nov 9, 2023 at 10:39 PM Timothy M Butterworth < > timothy.m.butterworth@gmail.com> wrote: > >> >> >> On Thu, Nov 9, 2023 at 11:31 PM Kent West <westk@acu.edu> wrote: >> >>> I have an M1-chip 2020 MacBook Air on which I have dual-booted with >>> Debian 12 initially, then "upgraded" to sid (in hopes of getting better >>> hardware support). It has several hardware ... glitches, and my google-fu >>> is failing me in finding solutions. I'm hoping someone here can help. >>> >>> <snip hardware issues> >>> >> >> Have you considered just running Debian in a Virtual Machine until >> hardware support matures. >> > > > I started to look at that yesterday, but apparently VirtualBox doesn't > support the Mac's M1 chip, and QEMU looked a bit daunting on the Mac, so I > gave up on that pursuit for now. The issues I'm currently having seem less > painful to me than getting a VM up and running on the M1 Mac. > On Mac most people use Parallels for virtual machines. https://www.parallels.com/ > -- > Kent West <")))>< > IT Support / Client Support > Abilene Christian University > Westing Peacefully - http://kentwest.blogspot.com > -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web