#Asahi arch CLI wifi setup M1 Mac

43 messages · Page 1 of 1 (latest)

sly edge
#

I totally forgot that computers don’t magically connect to wifi…. And now I’m super stuck.

#

Asahi arch CLI wifi setup M1 Mac

slate sparrow
#

Can you see if "iwctl" and see if that works?

sly edge
#

Waiting for iwd to start…

slate sparrow
#

Can you send a pic?

sly edge
#

It’s literally just the prompt saying “waiting for iwd to start…”

slate sparrow
#

Hmmmm

sly edge
slate sparrow
#

Try "nmcli device wifi list"

#

Also do Ctrl+C

sly edge
#

Nmcli: command not found

slate sparrow
#

hmmmm

#

Which mac are you using?

sly edge
#

Studio.

#

Err mini

#

Idk why I said studio

slate sparrow
#

Ohhhh

#

I don't think that's supported

#

If I'm not wrong asahi is still in alpha

sly edge
#

No it is

slate sparrow
#

Ohhh

#

Hmmm it should work

sly edge
#

I know the mini is supported, but idk if they expected a newb to try this

slate sparrow
#

Do you have a Ethernet cable?

sly edge
#

No and I really can’t get one to here

slate sparrow
#

Ohhhh

sly edge
#

If I need to try and bail to macOS that’s fine

#

That should still be possible, just a PITA

slate sparrow
#

In this video I will be demonstrating how to install Asahi Linux (Arch Linux ARM) on an Apple Silicon M1 Mac. This version of Asahi Linux is in an alpha release stage, however it’s still very impressive what has been accomplished after 14 months of hard work.

Special thanks to Hector Martin (@marcan42), Alyssa Rosenzweig (@alyssarzg), Sven Pet...

▶ Play video
#

I don't have a mac (My hackintosh is a thing) so I don't know much.

sly edge
#

Yeah gonna bail and try again with the gui

#

Thanks

slate sparrow
#

Welcome

fast flint
#

"waiting for iwd to start" you need to enable iwd.service

#

sudo systemctl enable --now iwd should do

slate sparrow
#

I'm gonna add him

fast flint
#

oh okay

#

gonna unfollow this thread then

muted nestBOT
# sly edge .s litany

Please follow the Standard Litany when asking a question:
What was your environment? What was your operating system, configuration?
What did you do? What did you run or test? Where?
What actually happened? What were the exact results, complete log contents, exact error messages?
What did you expect? What were you aiming to achieve? What result were you looking for?

Vague or superficial questions will yield vague or superficial answers. False information leads to false solutions.

Also see this similar guide on how to ask smart questions.

muted nestBOT
# sly edge .s q

When requesting support, please include specific, detailed, and relevant information about your system and issue.

We need such information because we don't know what it's like inside your system, and it's unlikely that we know much about the issue you're facing. The more information you can provide, the better we can help you with your specific issue.

Some examples of frequently requested information include the steps you took before your issue occurred (such as system updates), the steps you took to resolve your issue and their results, and your environment (such as your display manager or desktop environment).

Vague or superficial questions lead to vague or superficial answers. False information leads to false solutions.