DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-allwinner
<DC-IRC> <c0rnelius77> The USB ports are still borked on the Tritium H5 even after this change; https://github.com/armbian/build/pull/5920
<DC-IRC> <lanefu> still confused how tritium h5 got f'd up in the first place
<DC-IRC> <c0rnelius77> After a few a seconds if running headless they just kind of die or lose the will to work. ```[ 221.557605] ieee80211 phy1: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x1000 with error -19
<DC-IRC> <c0rnelius77> [ 221.557629] ieee80211 phy1: rt2800_probe_rt: Error - Invalid RT chipset 0x0000, rev 0000 detected
<DC-IRC> <c0rnelius77> [ 221.557641] ieee80211 phy1: rt2x00lib_probe_dev: Error - Failed to allocate device
<DC-IRC> <c0rnelius77> [ 221.558135] usb 5-1: USB disconnect, device number 3
<DC-IRC> <c0rnelius77> [ 223.097481] usb 5-1: new high-speed USB device number 4 using ehci-platform
<DC-IRC> <c0rnelius77> [ 223.265896] usb 5-1: device descriptor read/all, error -71
<DC-IRC> <c0rnelius77> ```
<DC-IRC> <c0rnelius77> If you bypass the changes it works as it should. But that doesn't explain why it's a problem.
<DC-IRC> <lanefu> yeah.. also curious if that means official LC images have similar problems
<DC-IRC> <c0rnelius77> I am also curious about this. I scanned through the linux repo but didn't see anything concerning it.
<DC-IRC> <c0rnelius77> I don't think its just the tritium personally but I only have two H5's. My Nanopi neo plus2 was also flaking out before I took it off line. I originally thought it was just dying but now I think its that driver.
<DC-IRC> <lanefu> hmm i think i gave away my non tritium h5's lemme check archive
<DC-IRC> <lanefu> i've got a Opi PC2
<DC-IRC> <c0rnelius77> when you get a chance give it a whirl
<DC-IRC> <lanefu> test for USB errors?
<DC-IRC> <Tonymac32> I have a K1+ or whatever as well as the Tritium H5
<DC-IRC> <lanefu> test with -edge or -current?
<DC-IRC> <c0rnelius77> yeah. it only happens in my testing when the board is headless. so with armbian run through the setup, setup wifi and reboot and see if it dies.
<DC-IRC> <c0rnelius77> 6.x.y but i've done my testing on 6.1.
<DC-IRC> <c0rnelius77> in my testing the dongle will stop being responsive within the first 60 seconds. usually less.
<DC-IRC> <c0rnelius77> in my testing the dongle will stop being responsive within 60 seconds. usually less.
<DC-IRC> <lanefu> wifi dongle?
<DC-IRC> <c0rnelius77> I've been using wifi dongles as its the easiest why I can think of to check the status. being headless an all and lazy 🙂
<DC-IRC> <c0rnelius77> I've been using wifi dongles as its the easiest way I can think of to check the status. being headless an all and lazy 🙂
<DC-IRC> <lanefu> gonna start by testing.. a _before_
<DC-IRC> <lanefu> which is whatever i commit i currently hve checked out lol
<DC-IRC> <c0rnelius77> and for clarity I did test 5.15.y and I don't see the issue there.
<DC-IRC> <lanefu> something's fucked.. cpu got hot AF instantly
<DC-IRC> <lanefu> built from `d1d86a342 Bump Allwinner kernels (#5893)` edge kernel
<DC-IRC> <lanefu> trying my current
<DC-IRC> <lanefu> tehn i'll try that RC from igor
<DC-IRC> <lanefu> okay -current was fine from above
<DC-IRC> <lanefu> trying igors now
<DC-IRC> <lanefu> i plugged in LED usb keyboard and a wifi dongle
<DC-IRC> <lanefu> dmesg was clean
<DC-IRC> <lanefu> seems fine on Igor's --curent kernel as well..
<DC-IRC> <lanefu> i'm dd-ing a a usb-sd adapter
<DC-IRC> <lanefu> and have wifi dongle
<DC-IRC> <lanefu> yeah tried another -edge 6.6.y build from main branch.... dropped dead on me
<DC-IRC> <lanefu> 6.1 happy 6.6 sad
<DC-IRC> <lanefu> somebody wanna ELI5 wtf crust is?
<DC-IRC> <c0rnelius77> I thought it might be crust related, but after trying diff kernels and experiencing same issues be it, happens right or a way or happens later, I started veering from that. Plus I've flash older versions of u-boot that don't depend on crust and the same thing happens.
<DC-IRC> <c0rnelius77> I thought it might be crust related, but after trying diff kernels and experiencing same issues be it, happens right a way or happens later, I started veering from that. Plus I've flash older versions of u-boot that don't depend on crust and the same thing happens.
<DC-IRC> <c0rnelius77> crust is basically a PWR MNGT thing
<DC-IRC> <c0rnelius77> In my opinion it is a depends we never needed for an EOL SoC, but here we are.