marcan changed the topic of #asahi to: Asahi Linux: porting Linux to Apple Silicon macs | "Does XXX work yet?": https://alx.sh/fs | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Topics: #asahi-dev #asahi-re #asahi-gpu #asahi-alt #asahi-stream #asahi-offtopic | Keep things on topic | Logs: https://alx.sh/l/asahi
<jaythefruit>
I have a USB-C hub, but when I try to connect it the USB-A ports on the hub get power but not data. For example, if I plug in a keyboard it lights up but none of the keys do anything. Is this expected behavior on the 2022 13" M2 Macbook Pro?
<nicolas17>
have you tried the hub on other computers, or on macOS?
<jaythefruit>
It works on macOS as well as my desktop computer
JayBeeFOSS has quit [Remote host closed the connection]
JayBeeFOSS has joined #asahi
marvin24 has joined #asahi
marvin24_ has quit [Ping timeout: 480 seconds]
enick_78 has quit [Ping timeout: 480 seconds]
rhysmdnz has quit [Ping timeout: 480 seconds]
ahuar88 has quit [Remote host closed the connection]
ahuar88 has joined #asahi
chadmed has quit [Ping timeout: 480 seconds]
chadmed has joined #asahi
possiblemeatball has quit [Quit: Quit]
delsol has quit [Ping timeout: 480 seconds]
<PaulFertser>
jaythefruit: I wonder what new messages appear in "dmesg -w" when you insert the hub and then when you insert a device in it.
<PaulFertser>
Also if that's the same regardless of Type-C orientation.
m5zs7k_ has quit [Read error: Connection reset by peer]
m5zs7k has joined #asahi
jaythefruit has quit [Ping timeout: 480 seconds]
<PaulFertser>
Another meaningful test would be connecting a Super Speed device to an A port.
jaythefruit has joined #asahi
jaythefruit has quit [Ping timeout: 480 seconds]
rhysmdnz has joined #asahi
enick_78 has joined #asahi
<MichaelLong>
I've the same issue as jaythefruit.
<MichaelLong>
there's no dmesg output when plugin in a new USB-device. It hapens with "pure" USB 3.x Hubs as well as USB-C docks (which are essential USB-hubs with additonal internally connected USB-devices. Looks like some hw events are not reported by the USB root hub somehow.
<PaulFertser>
MichaelLong: so can you show full output from dmesg -w that appears after plugging a hub? Both directions.
<PaulFertser>
And also with SS and HS/FS devices attached to the hub.
<MichaelLong>
PaulFertser, I can try later that day but I fear there's nothing to report/show. However I have not yet plugging in the hub in both ways intentionally. Tested the issue with multiple devices USB 3.x and USB 2.0 storage devices, and several HID-devices.
<MichaelLong>
Macbook Pro M1
<MichaelLong>
if you re-plug the USB-hub _all_ connected devices are available.
* MichaelLong
should probably file a gihub issue
<PaulFertser>
MichaelLong: questions to be answered by tests: 1. Do both SS and HS hubs get detected when it's plugged either way; 2. Are hotplug events missing for both SS and HS devices attached to the hub; 3. When the device is present before the hub is connected, and you connect the hub, see the device available, then unplug the device, do you get the disconnection message right away? And if you plug that
<PaulFertser>
device back do you not get any connection message at all?
<PaulFertser>
I'm not sure if it's obvious and so not worth mentioning but a Super Speed hub is actually two hubs in one, see e.g. this datasheet https://www.ti.com/lit/gpn/tusb8041
<PaulFertser>
So it can't be a single "USB root hub" involved, there're normally two connections established via the upstream port at the same time: SS and HS.
<MichaelLong>
ok this is interesting: 1) both hubs (SS and HS) are recognised when the Hub/dock is connected. Orientation does not matter. 2) It looks like hotplug events are missing for HS devices (tested with a keyboard and a USB 2.0 USB-Stick), however I just tested this also with a SS-USB-Stick and here hotpluging is working! 3) yes, (HS) device is available and an USB disconnect event is present and replugging the HS usb device works!
<MichaelLong>
so if the HS device is known right from the start, it keeps working. Didn't catch that when I was testing this last time
<PaulFertser>
I suggest you attach the dmesg output to a github ticket, there might be some more interesting details present in that. Or sometimes just looking over the log again and again after checking the sources gives a good idea, so having the log verbatim is always good for the devs.
<PaulFertser>
Also, is that the same with other Type-C ports, especially if there's a difference between the port you normally use for charging and the others.
<MichaelLong>
PaulFertser, yes I'll do that. I will also tests with another USB-C hub to see if it is consistent. However I was using both USB-C docks in macOS with no apparent issues.
<PaulFertser>
MichaelLong: that's a good data point too
<MichaelLong>
the "other" USB-C has a USB-C power in port. And I've a USB-C "charging"-cable that displays the wattage. In macOS it shows the full possible load, connected to Fedora Asahi Remix it does not surpass 10W. So there might be another PD-related issue but - that's another topic for another time
<PaulFertser>
I wonder if Asahi provides interesting data in /sys/class/power_supply/tcpm-*/current_max and other relevant nodes there.
<PaulFertser>
(probably it doesn't switch to higher voltage or probably it does but limits the current more than you expect it, and these two cases are impossible to tell apart just by looking at power number alone)
<MichaelLong>
there was at least one other person reporting/confirming USB-C hub/dock related issues. I wonder why it is not more widespread. Probably also depends on the apple device
<PaulFertser>
That's why all the details matter: the hub model, the port used, full dmesg, devices tried etc. So that the devs could reproduce or probably guess the reason by assembling all the info into a unified picture.
<sven>
power info should be in s/tcpm/tipd/ probably
t2p4 has joined #asahi
<t2p4>
hello. I just installed asahi on m1 mini, but chose an existing username on the first boot setup step. got message "username already exists" and then was presented with a logon prompt. Is there a default root credential I can use ? or do I need to re-install ?
<j`ey>
how can a user already exist on a new install? o_O
<t2p4>
there are plenty of legacy default users on a unix / linux system, eg "operator". MacOS lets you however use some of these, other do not, OpenBSD, various Linux variants do not allow these
<t2p4>
I guess this is not so much an Asahi issue, but still it affects the initial setup process and locks you out
<j`ey>
sounds like a calamares issue, if you installed kde
<j`ey>
t2p4: so what username did you actually try?
* t2p4
tried "operator"
<j`ey>
I didnt think that was a reserved/legacy one! at least it's not on my ubuntu rpi machine
hightower2 has quit [Ping timeout: 480 seconds]
bruse has joined #asahi
<t2p4>
its probably off topic, but the operator group exist on ubuntu. most distro still have the user, too. I guess this is more a fedora issue, although default distros let you choose another user name if already taken or not "allowed"
<j`ey>
t2p4: KDE right?
<t2p4>
nothing to do with KDE
<j`ey>
if so it would be the calamares setup wizard thing
<t2p4>
well yes the wizard. never used fedora
<j`ey>
was it KDE or GNOME?
<t2p4>
it was KDE
<t2p4>
there was no option to chang the username, just straight to the prompt
<j`ey>
I agree though, seems weird to allow a duplicate username, with just a warning and not allow you to try again
qyliss has quit [Quit: bye]
<t2p4>
yeah, I figued I would need to reinstall. "forbidden user name".. what world we are living in ? off topic, the operator user is just legacy is it not ?
qyliss has joined #asahi
<j`ey>
you could create a bug there, to say it should give you the option to change it instead of just going forward
<t2p4>
I dont know, I installed OpenSuse Tumbleweed on x86 KDE with "operator" fine, perhaps not worth the hassle. I just re-install.. what a rare case this may be
* t2p4
is just unhappy as it took hours to get the install done over congested 4g network in rural area
* t2p4
crying a river
hightower2 has joined #asahi
maxg_ has joined #asahi
maxg_ has quit []
<j`ey>
can probably rename the user once it is done
maxg_ has joined #asahi
<t2p4>
you can do sorts of hacks on linux to /etc/group and /etc/passwd and become "
<t2p4>
operator" but not on OpenBSD.
<t2p4>
anyway, I will take my strife elsewhere and re-install
qyliss has quit [Quit: bye]
<t2p4>
j`ey: Thanks in any case for the feedback
<j`ey>
t2p4: good luck!
<t2p4>
thats all I need
qyliss has joined #asahi
<t2p4>
so I am back in the installer and it wants to resize now the existing fedora partition. Can I not blow it away or overwrite it ?
<j`ey>
I think you will need to delete to with diskutil, the installer doesnt have a way to reuse them
<t2p4>
j`ey: Thanks, my layout and the instructions differed, but I got there. now downloading again, will be back in several hours to confiirm it worked or not
<t2p4>
s/confiirm/confirm
tertu has quit [Quit: so long...]
tertu has joined #asahi
jaythefruit has joined #asahi
jaythefruit has quit [Remote host closed the connection]