you don’t say it like that’s ok do you?
no it’s not but it’s a small company and i’ve owned samsung phones that have never received any updates. if a large company like samsung can’t do it then i don’t fault clockwork for not doing it. it’s a great device that’s why i put in a little extra effort to support it. so i can get the most out of the device and pass the improvements along.
5 Likes
For those who find all this too complicated, there’s always the option of buying Apple products.
Anyone who is pleased that Rex contributes so much to the community can show him their appreciation:
2 Likes
Uncalled for. Apple products should actually be the option if I wanted to be abused, but here we are.
this is not the hobby side of things, its not a gunpla kit. This is just outsourcing the development of the product to the costumer, for free. One should be able to pick what to deal with to a reasonable degree, but what the manufacturer does in essence here is pick when to ship new obstacles in their platform for the costumer to solve.
“they dont support radxa” well radxa supports their own products.
Ive actually donated to Rex before btw, he knows, no one is trying to demerit what he does; I just do it privately, I don’t need to mention it on every post for validation or as if for that alone I can have an opinion, or in lieu of being able to do anything else nor do it as a habit of trying to shame people online.
There are actually active ways of contributing, like doing the coding which I now will have to do, but this is not the kind of stuff open source communities around platforms do and share or buy a platform for like in the 70s. People usually have a pretty good idea already of what they want to build with it, spend the time on and share.
not sure if you meant offense but I’ll have to take it.please dont do that again.
1 Like
I don’t wish to offend anyone, but it’s tiresome to keep reading about people who can’t get to grips with the uConsole because they either misjudge the device or overestimate their own abilities.
The internet is full of information (about the device as well as about clockwork) that interested and savvy users can look into BEFORE making a purchase, and only then decide whether or not to buy it.
3 Likes
is using prebuilt image on cm4 reasonable enough?
2 Likes
I guess I’m confused here. You bought hardware that is explicitly not supported, with known and published limits. What brought you to be so settled on this setup?
1 Like
Is asking for the source of that image reasonable enough?
I did not buy hardware explicitly not supported, I think you know that, in fact I referenced many times its alleged lack of limits and great state of the art possibilities, which include Radxa and more, and which are now very clearly a myth.
But you’re just trying to make a point about me so no one tries to make the point about it, hence the canned attempt at sarcasm. Now you’re trying to say the platform is great for its chronic and periodic limits, and that there is definitely not a brazenly misleading and misinforming mess going on around about the product that starts with Clockwork’s subversive and totally not explicit lack of support, and I don’t even need to bring out Radxa, because many compatibilities even within and out their own environment are implied all the time and have been so for a veeeeery long time, way longer than it takes for a uConsole to be shipped, way longer than it takes to develop the minimum open and accessible support for it as a manufacturer, the kind where the costumer doesn’t have to read schematics on hardware they did not design to be able to use the console before they get to do what they bought it for, like making games, comms tools or just have a carrier device that is surveillance free or whatever.
In fact I seem to be one of the too few taking the responsibility of being explicit beyond doubt about the truth of the platform instead of doing the opposite, so that more people can chose not to buy it instead of being misled into it.
All over the place people pretend to buy the platform not as kernel and firmware developers but as someone else, some kind of hobbyist, even top contributors identify themselves by terms like “linux noobs”, but suddenly Clockwork is putting them to work to get their own products sold, and you suddenly pretend that to be the intention all along, suddenly it conveniently was meant for kernel developers for a very particular bunch of hardware, like some Altair computer in the 70’s when software wasn’t given any merit. And so this happens, the mess, because no one buying it is that person, because it is not explicit at all that they should be.
Not even support for their own Compute Modules and components within their own platform is the least reliable.
1 Like
Cool.
I don’t share your feelings of grievance over a piece of hardware that is an exceptionally useful toy.
I am a Linux noob and have found this community to be incredibly generous with time and knowledge. I hope you find the help you’re looking for.
3 Likes
Nobody misled you into it. You misled yourself into it. They sell two versions, and neither version even has the CM5 right now, let alone the Radxa. They should not have to enumerate all the things they do not support to make the point that if you do something they don’t sell (and thus support on some level), you’re on your own.
It will be cool if it can be made to work with other compute modules, but nobody anywhere actually owes you this.
3 Likes
Ok.
Ok.
Ok.
Replies to nothing but good for you.
1 Like
What a sparkling gaslight cope but still too cliche.
How much if I quote you back every reference on the thread that you did not read and more that lays out explicitly how the platform is solved and so universally made for lots of exactly compatible modules and components and so safe to buy not just the Radxa setup, which isn’t even the point any longer, but the Clockwork in-house setup that by the way is totally optional on purchase?
In fact, the A-06 module is also Rockchip (like Radxa), not Raspberry Pi. ClockworkPi supposedly ships official, vendor-published kernel patches for it in its repository, but conveniently omits mentions for the new display, and this applies for an A06 just as much as would be a Radxa, and not just because they’re cousins. Both target the exact same physical carrier board.
It’s not miselading to buy a Clockwork Rockchip and not have their own display supported on it? Not misleading that images and sources never seem to match or that you can’t reproduce images with their sources? The same people popped under that guy and others to come up for a new way to blame the costumer for buying in whatever way that didn’t work for him.
It’s like they insist so much on everyone using their mystery images that they may even break the source in case anyone tries to build it on their own. Lately I’ve been finding out drivers are not even ever included in the source of a couple of the most prevalent repositories used in the forums that say they do and I’ve been here cracking my head wondering why the device trees are good but aren’t mapping; there were no drivers to map to. What’s all that about?
Nah lad, I did not “mislead myself”, I wasn’t in love when I bought in so don’t give me the patent gaslighting girlfriend treatment.
You know the problem is that they enumerate what they do support; just more of your logic kung fu.
The narrative keeps switching sides all the time; mystery people say the platform is great and they were able to run everything and play the muppets and read the bible in it; but if you buy it to figure out that’s not possible with what they implement, then it was never meant to be supported, “no one owed you what you were told you were getting”, “is it too much to ask that you just use my mystery image on a google drive?”
1 Like
Found the real DSI driver bug + a strong hardware lead (I2C not reaching the CM5 through the adapter) — sharing in case it helps anyone else stuck here
Hey all,
Been fighting the exact same "everything works except the new-revision LCD"read (Radxa CM5Lite + HackerGadgets adapter + uConsole), and got far enoughwant to share finne else time — orin case someone here already has a fix for the last piece.
Setup: Radxa CM5 Lite, Arch Linux ARM, kernel 6.1.84 (ak-rex/Clockworkkr4.1),HackerGadgets Radxa CM5 adapter board.
- Ported the missing new-panel support
The Radxa kernel’s panel-cwu50.c driver is an old version thpredates Clockworel revision.Ported the relevant bits from ak-rex/ClockworkPi-linux (rpi-6.12.y) — GPtion, the newcwu50_init_sequence2() DCS sequence, separate vci/iovcc regulators.
2. Found and fixeall DSI commands
After porting, thn image — turnedout the runtime panel-detection mipi_dsi_dcs_read(dsi, 0x04,…) call inside ince GPIOdetection in probe() already works) triggers a bus-turnaroun(BTA) that the pa’s dw-mipi-dsi2controller. This permanently wedges the DSI command interfac(repeated command in dmesg), soevery DCS command sent afterward silently times out — includthe entire ~250-lRemoving that read fixes it completely: all 192 init commands now transmit cleawith zero errors,play-on ACK-waits that used to fail with -110 now return 0.
Also fixed: a NULL-pointer Oops from cwu50_get_modes() re-attaching the y on a secondconnector probe (needs a guard flag), and a reset-gpio active-high/activhe official device tree. - Still black — traced it to what looks like a missing I2C through the adapt
Even with clean D own internal BIST test pattern still showing nothing), the screen stays black.Went further: the @ 0x34) neverresponds on I2C — neither via hardware I2C nor bit-banged i2c-gpio replicatctly (300/300probes failed). Cross-checked with a second independent I2C device (ADC101C @PMIC itself isn’tdead (board boots/charges through it), and the backlight GPIO on the same adapter the I2C signalpath just isn’t routed through the adapter. Emailed HackerGadgets ask
If anyone has theto checkcontinuity on pins 3/5/27/28, a different adapter confirmed to pass I2C, or alreate it. Happy toshare the patched driver/logs.
(cc @Rex — same “everything but the LCD” symptom you mentioned in July; the DSI that point.)
2 Likes
The hackergadgets board works fine. You just need to change the init sequence for the driver to work on the newer panels I’d look at my existing driver that works with all 3 panels and all RPi CMs. It might just work out of the box with no changes.
1 Like
Thanks Rex! That driver sounds like what I already ported from ClockworkRadxa-linux/rpi-linux. DSI init is clean now (192/192 commands, no errors). Still black though, traced to the mainboard I2C (PMIC/ADC101C) not responding through the HackerGadgets adapter. What image are you testing with? Couldn’t find a public download link for your Radxa CM5 build anywhere in the threads – if you can share it, happy to test against it directly.
The one from clockworkradxa-linux is an old one. Check this more recent one out that had all 3 panels working on it.
Thanks a lot @Rex, i got it booting but… turned out it just didn’t have enough charge to boot. Once it hit like 30% battery it booted fine, below that it still powers on but no display.
Also updated everything on the system, was 921 packages behind. That fixed a weird bug I had where the screen would sometimes go psychedelic with strong greens and reds — hasn’t come back since.
One thing still bugging me: shutdown doesn’t fully power off, neither the SSD nor the HackerGadgets AIO V2 board — everything else does (radxa, bt, display) but those two stay lit. Found a forum thread on it though, seems like a known CM5 thing — poweroff goes through PSCI and just halts the SoC, nothing left to cut the rails after that. Only real fix people found is soldering a physical battery-cut switch onto the HackerGadgets board (desolder R14, wire J6 to a microswitch). No software fix apparently
what you found is a raspi cm5 thing, that’s not necessarily a radxa cm5 thing
1 Like
Just looked at this thread and… Christ… Buying a uConsole and then complaining that an explicitly unsupported configuration happens to not work fully out of the box, and blaming Clockwork for that…
4 Likes