klaus has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
amw has quit [Ping timeout: 265 seconds]
<Glanzmann>
bastilian: Do you have Linux amd64 machine, if so just follow the developper quickstart or look at this:
<Glanzmann>
bastilian: sudo apt install -y gcc-aarch64-linux-gnu libc6-dev-arm64-cross device-tree-compiler imagemagick; git clone --recursive https://github.com/AsahiLinux/m1n1.git; cd m1n1; make
<Glanzmann>
and you're done.
<Glanzmann>
I'm using debian for this.
<bastilian>
Glanzmann: Thank you! Yeah, i have a amd64 box. somehow I had it in my head that I do need an aarch64 machine to compile it. ...after half my life working with computers I should finally learn more about gcc and compiling in general. :D
<Glanzmann>
I put the packages for debian in there.
<bastilian>
I'm currently going through the Dev Quickstart.
<bastilian>
for some reason the install of Big Sur on the second partition estimates to take 2 hours. at least it's counting down steadily.
<bastilian>
... it heard me complain and jumped to "About a minute remaining" :D
phiologe has quit [Ping timeout: 260 seconds]
phiologe has joined #asahi-dev
<bastilian>
I wrote a Dockerfile with all the build requirements installed and it seems to build. not sure if it's properly build, but I'm gonna find out later when I try the macho file on the other machine.
<bastilian>
Wonder if I should submit a PR with the container setup added. Those who are running Docker on M1 already could also use it to build without requiring a separate Linux build machine.
<bastilian>
Success! \o/ I got the Asahi logo on my screen. Woohoo!
<bastilian>
I have a mac mini M1 booted into m1n1 and connected a M1 MacBook via the DFU ports, which should be right and the mini reacts to macvdmtool commands, but when trying to run proxyclient/shell.py I get an error: https://gist.github.com/bastilian/7787799e3a814efbc1c24857e2679f09
VinDuv has joined #asahi-dev
<Glanzmann>
no idea, I'm qaiting for my second mac.
klaus has joined #asahi-dev
maor26 has joined #asahi-dev
thestr4ng3r has joined #asahi-dev
thestr4ng3r_ has quit [Ping timeout: 256 seconds]
<sven>
bastilian: which usb-c cable are you using? it sounds like it's one that just doesn't support usb 3.0
fl35[m] has quit [Quit: Idle for 30+ days]
bostjan has joined #asahi-dev
bgb has joined #asahi-dev
<j`ey>
marcan: so youre thinking of changing #define DAIF_PROCCTX_NOIRQ PSR_I_BIT to include F too?
<bgb>
bastilian: usb-c cable shipped with macbook will NOT work
bgb has quit [Ping timeout: 256 seconds]
<bastilian>
sven: I am using the charge cable that the macbook came with. I also tried another USB-C cable same thing. ;/
acelogic has quit [Remote host closed the connection]
<marcan>
j`ey: yeah
<marcan>
bastilian: you need a USB 3.0 cable
<marcan>
the charge cable is not one
<marcan>
if it's thin, it isn't one
<marcan>
there are two types of standard type C cables (not counting thunderbolt stuff), 2.0-only and full spec
<marcan>
you need a full spec cable
<dottedmag>
marcan: Do they differ only by the actual number of the wires and plug contacts connected, or is there some other trickery (crossed connections, required resistances etc)?
<marcan>
dottedmag: usb2 cables do not have the SBU1/2 pins connected; usb3 ones do (per spec)
KindOne has quit [Ping timeout: 272 seconds]
<marcan>
although we *can* map the UART out to pins that exist on a USB2-only cable (the USB2 pins themselves), those pins are not crossed, so it will never work for connecting two macs together; SBU1/2 *are* crossed over so that works
<marcan>
USB2 cables have a grand total of 5 wires inside them; full spec ones have upwards of 15, including the two we need for this to work
<marcan>
I just updated the developer quickstart guide with a whole paragraph on this, because it seems everyone is runningintothe same thing
<dottedmag>
Thanks, now the USB-C plug diagrams from Wikipedia make sense.
KindOne has joined #asahi-dev
<j`ey>
earlier I added an extra comment on the wiki saying that the charging cables that come with the macs wont work
<marcan>
yeah, I expanded on that :)
<j`ey>
the first PCB I ever designed/manufactured worked perfectly... apart from the fact I was testing it with a power-only USB cable for the first 8 hours and had no idea what was wrong
<bastilian>
marcan: Thank you. I thought I had a proper USB-C 3.0 cables. I tried the charge cable after it didn't work with the others.
<bastilian>
.... I wonder if someone woke up some day and thought "How can we make USB more annoying"
<TheLink>
it's a bit like codec vs container :P
klaus has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
klaus has joined #asahi-dev
<bastilian>
Speaking of containers... I used a Docker container to build m1n1, which worked like a charm and doesn't require a dedicated linux machine to build. Would it make sense to submit a PR adding the Dockerfile to the m1n1 repo?
bostjan has quit [Quit: Leaving]
<Bluerise>
The cheap cable my employer sells with its products doesn't have SBU1/2...
<Bluerise>
the cable that came with my external display does have it
<Bluerise>
The gist I guess is: buy cables that are not too cheap (no SBU 1/2) and not too expensive (like thunderbolt capable, chips in the cables itself...)
<bastilian>
Yeah, I'm currently browsing through lists of USB-C cables trying to find a few that look like they'd work. 🤞let's hope this time I'll grab the right one.
<j`ey>
bastilian: probably post the link to the one youre going to buy here, maybe someone can confirm it
<bastilian>
that was my plan. :D
<bastilian>
It's hilarious how bad the USB experience has become. now I wish the only thing I have to worry about is the cable orientation... i miss these times.
<marcan>
Bluerise: apple's thunderbolt cable works fine
<marcan>
e-marked cables are fine
<marcan>
I can't think of why a fancy cable would mess with SBU1/2
<Glanzmann>
I see.
<Glanzmann>
marcan: Cables that come with eizo monitors (USB-c) will probably also work fine.
<Glanzmann>
The difference between thunderbolt and usb-c(3) is the throughput isn't it? usb is 10 Gbit/s and thunderbolt is 40 Gbit/s?
<gruetzkopf>
active thunderbolt cables (and usb4 cables) *will* mess with SBU
<gruetzkopf>
they're running the low speed sideband (for link setup, amplifier control, stuff like that) over those pins
<marcan>
gruetzkopf: I think the basic (short) apple tb cable is passive
<marcan>
gruetzkopf: the spec seems to say SBU should be passive by default
<marcan>
only in USB4 mode does it turn into a digital thing
<davidrysk[m]>
marcan: what exactly is "USB4 mode" and how does it differ from passive and active TBT3?
<davidrysk[m]>
(I should just go read the spec shouldn't I)
<marcan>
AIUI USB4 is mostly a superset of TBT3, it's just that the doc I read was a USB doc and thus won't mention TBT3
<marcan>
bastilian: the USB-IF certified one will *definitely* be OK as long as they aren't lying; the other one is probably OK unless it's a really horrible one.
<bastilian>
marcan: Really? Because I do have two cables that say they are USB-IF certified and they didn't work. Maybe because they are advertised as "charge cables"? https://www.belkin.com/us/p/P-CAB003/
<winocm>
Yes.
<winocm>
That is just USB2 in practice really
<never_released>
which is fun
<never_released>
a random USB Type-C cable
<never_released>
can be anything from USB2 to TB4
<bastilian>
Ok. :) how confusing can one make a connection standard.... Thank you all for figuring it out. somewhat. :)
<davidrysk[m]>
is it possible to make a program where you plug the cable into both USB ports on your computer and it identifies and tests the cable?
<bastilian>
I think marcan posted a tester recently.
<bastilian>
I might be possible to build one with USB-C breakout boards and an arduino to test the lines.