lanefu changed the topic of #armbian-rockchip to: Armbian - Linux for ARM development boards | Rockchip SoC | www.armbian.com | This channel is relayed to the equivalent Discord channel | this channel is logged
<DC-IRC> [Discord] <menu> is usb broken on `6.10.6-current-rockchip-rk3588`?
<DC-IRC> [Discord] <menu> `lsusb` reports a series of root hubs but no devices
lanefu has joined #armbian-rockchip
<DC-IRC> [Discord] <amazingfate> that depends on the board
<DC-IRC> [Discord] <Werner> 6.10 is still early mainline stage for rk3588 so the answer is as suggested _maybe_.
<DC-IRC> [Discord] <zeeto9> This may be just what I was looking for. I’ve wanted to integrate the npu usage into btop++ somehow. I doubt it’s as simple as adding to the collect code, but maybe it will work. https://github.com/aristocratos/btop/blob/main/src/linux/btop_collect.cpp
<DC-IRC> [Discord] <fridtjof> submitted! looking at https://www.armbian.com/authors/ is there some nickname field i missed or did i take the "last name" field too literally? the form confused me a bit, admittedly :D (I dont really care about being displayed either way, was just wondering)
lanefu has quit [Ping timeout: 264 seconds]
<DC-IRC> [Discord] <igorpec> this form has manual approve feature 😉 and i was hibernating until this very moment
lanefu has joined #armbian-rockchip
<DC-IRC> [Discord] <menu> it's an oPi5, USB worked fine on 5.10 LTS
<DC-IRC> [Discord] <amazingfate> devicetree of opi5 is rewritten in 6.1 rkr3: https://github.com/armbian/linux-rockchip/commit/7792131c30109389040c7943a22055fd68126b16, I don't know if it is related
<DC-IRC> [Discord] <menu> hmm, just connected a USB 2.0 device and it showed up immediately
<DC-IRC> [Discord] <menu> narrowed it down, it's definitely the USB 3.0/xHCI that's not working now
<DC-IRC> [Discord] <superkali> try a usb meter if you keep it or a usb stick with a led so you can see if it's not a power problem
<DC-IRC> [Discord] <menu> i do not have any USB 3.0 test gear, although i do have another hard drive, i should stress that this configuration previously worked fine, and the drive will still mount on 5.10, just not 6.10
<DC-IRC> [Discord] <menu> i do not have any USB 3.0 test gear, although i do have another hard drive, i should stress that this configuration previously worked fine, and the drive will still enumerate on 5.10, just not 6.10
<DC-IRC> [Discord] <menu> aw man i'm even more confused
<DC-IRC> [Discord] <superkali> lsusb -t what say?
<DC-IRC> [Discord] <menu> a different drive works, it's just this one drive in this one port
<DC-IRC> [Discord] <menu> this is the darndest thing, it would appear the oPi doesn't like the *cable*
<DC-IRC> [Discord] <menu> cable works fine on my macbook, but not the oPi5, man i hate USB
<DC-IRC> [Discord] <superkali> i can't understand if you don't check those stuff
<DC-IRC> [Discord] <superkali> i can't understand the issue if you don't check those stuff
<DC-IRC> [Discord] <superkali> you've a mouse?
<DC-IRC> [Discord] <superkali> plug it and see if the led works
<DC-IRC> [Discord] <menu> i'm telling you it's the cable
<DC-IRC> [Discord] <menu> i've got two drives, two cables, and there's one cable the pi don't like, though it previously worked
<DC-IRC> [Discord] <menu> dmesg even suggests this: `[34528.137302] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?`
<DC-IRC> [Discord] <menu> i know i'm not browning out because the fan speed isn't dropping
<DC-IRC> [Discord] <menu> hmm no, it's only using USB 2.0: ```
<DC-IRC> [Discord] <menu> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
<DC-IRC> [Discord] <menu> |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 480M```
<DC-IRC> [Discord] <menu> `lsusb` indicates no connected devices with the original cable, with a replacement it indicates a USB 2.0 device
<DC-IRC> [Discord] <menu> this leads me to believe the cable is 3.0 only, which is not an issue, i need to get 3.0 working
<DC-IRC> [Discord] <johnthecoolingfan> Something weird is going on with BigTreeTech CB2, I desperately need help as I have no idea what causes this.
<DC-IRC> [Discord] <johnthecoolingfan> Basically I am trying to get mainline u-boot working instead of having to use btt's fork (2017.09 from radxa `stable-4.19-rock3`). The issue is that at around 2 minutes 50 seconds of uptime (as reported by the `uptime` command) the board freezes solid. status LED stops blinking, no signals on serial, unresponsive. Until the board gets reset or power cycled. This is what happend o <clipped message>
<DC-IRC> [Discord] <johnthecoolingfan> n mainline u-boot 2024.10 and 2024.07, but doesn't on btt's `stable-4.19-cb2` which is 2017.09. I am setting up u-boot in the config just like other rk3566 and rk3568 boards (using odroid m1, rock 3a and 3c boards as an example), but the board just does that. Every time. Does anyone have any good clues on what is going on? I've already wentover quite a bit of stuff and left the r <clipped message>
<DC-IRC> [Discord] <johnthecoolingfan> esults in my PR to add the board: https://github.com/armbian/build/pull/6860
<DC-IRC> [Discord] <johnthecoolingfan> Getting a schematic would be nice, since it has been suggested that voltage regulators might be the cause, but there is no difference in that regard between btt's fork and the device tree I am using. How could just changing u-boot from that fork (which JUST adds a defconfig and device tree on top of radxa stuff) starts causing the issue? And why wasn't it observed on other rk356x boards?
<DC-IRC> [Discord] <johnthecoolingfan> I know I keep asking about this issue but I am really feeling like I'm in a dead end with no leads and the main "clue" is only confusing me.
<DC-IRC> [Discord] <efectn> Which usb is it?
_whitelogger has joined #armbian-rockchip
<DC-IRC> [Discord] <menu> the upper USB-A, the only 3.0 port on the board
<DC-IRC> [Discord] <johnthecoolingfan> Something weird is going on with BigTreeTech CB2, I desperately need help as I have no idea what causes this.
<DC-IRC> [Discord] <johnthecoolingfan> Basically I am trying to get mainline u-boot working instead of having to use btt's fork (2017.09 from radxa `stable-4.19-rock3`). The issue is that at around 169-170 seconds of uptime (as reported by the `cat /proc/uptime` command) the board freezes solid. status LED stops blinking, no signals on serial, unresponsive. Until the board gets reset or power cycled. This is what happ <clipped message>
<DC-IRC> [Discord] <johnthecoolingfan> end on mainline u-boot 2024.10 and 2024.07, but doesn't on btt's `stable-4.19-cb2` which is 2017.09. I am setting up u-boot in the config just like other rk3566 and rk3568 boards (using odroid m1, rock 3a and 3c boards as an example), but the board just does that. Every time. Does anyone have any good clues on what is going on? I've already wentover quite a bit of stuff and left <clipped message>
<DC-IRC> [Discord] <johnthecoolingfan> the results in my PR to add the board: https://github.com/armbian/build/pull/6860
<DC-IRC> [Discord] <johnthecoolingfan> Getting a schematic would be nice, since it has been suggested that voltage regulators might be the cause, but there is no difference in that regard between btt's fork and the device tree I am using. How could just changing u-boot from that fork (which JUST adds a defconfig and device tree on top of radxa stuff) starts causing the issue? And why wasn't it observed on other rk356x boards?
<DC-IRC> [Discord] <johnthecoolingfan> I know I keep asking about this issue but I am really feeling like I'm in a dead end with no leads and the main "clue" is only confusing me.
<DC-IRC> [Discord] <johnthecoolingfan> Something weird is going on with BigTreeTech CB2, I desperately need help as I have no idea what causes this.
<DC-IRC> [Discord] <johnthecoolingfan> Basically I am trying to get mainline u-boot working instead of having to use btt's fork (2017.09 from radxa `stable-4.19-rock3`). The issue is that at around 169-170 seconds of uptime (as reported by the `cat /proc/uptime` command) the board freezes solid. status LED stops blinking, no signals on serial, unresponsive. Until the board gets reset or power cycled. This is what happ <clipped message>
<DC-IRC> [Discord] <johnthecoolingfan> end on mainline u-boot 2024.10 and 2024.07, but doesn't on btt's `stable-4.19-cb2` which is 2017.09. I am setting up u-boot in the config just like other rk3566 and rk3568 boards (using odroid m1, rock 3a and 3c boards as an example), but the board just does that. Every time. Does anyone have any good clues on what is going on? I've already wentover quite a bit of stuff and left <clipped message>
<DC-IRC> [Discord] <johnthecoolingfan> the results in my PR to add the board: https://github.com/armbian/build/pull/6860
<DC-IRC> [Discord] <johnthecoolingfan> Getting a schematic would be nice, since it has been suggested that voltage regulators might be the cause, but there is no difference in that regard between btt's fork and the device tree I am using. How could just changing u-boot from that fork (which JUST adds a defconfig and device tree on top of radxa stuff) starts causing the issue? And why wasn't it observed on other rk356x boards?
<DC-IRC> [Discord] <johnthecoolingfan> I know I keep asking about this issue but I am really feeling like I'm in a dead end with no leads and the main "clue" is only confusing me.
<DC-IRC> [Discord] <efectn> Are there any log like bad usb cable etc.?
<DC-IRC> [Discord] <menu> one of my cables does, the other doesn't - it just connects as USB 2.0
<DC-IRC> [Discord] <koutsie> is armbian back to bootable on orange pi 3b?
<DC-IRC> [Discord] <koutsie> on latest builds, has anyone tested?
<DC-IRC> [Discord] <koutsie> please ping if you respond.