OpenBSD 7.1 on PINE64 RockPro64
bsandro.tech
OpenBSD 7.1 on PINE64 RockPro64
1–10 of 28 posts
Re: OpenBSD 7.1 on PINE64 RockPro64
#2And if you don't like because they misrepresented functionality, then they point at the sign "developer hardware"... And it's all dev hardware.
And they even sell dead and irrecoverable (without soldering/hacking) on devices like the pinephone keyboard/battery. Or how dare you use the phone usb-c port when on the keyboard - if you do, you fry the charging chip and possibly the battery.
Or that the rockpro64 is said to be able to boot with eMMC rather than microSD. But when you try to, it doesn't work. Back to microSD. Weirdly enough Ive heard some users whose boards DO work with eMMC. None of mine did. Again, since docu is terrible, I copied the command that works and didn't for me. Seems like bad hardware versions or something?
These sorts of landmines are everywhere with Pine hardware.
Re: OpenBSD 7.1 on PINE64 RockPro64
#3Have to say I'm not at all impressed with Pine as a whole. Their stuff is no support, bad documentation, lack of claimed functionality. They make hardware and then tell the community "whoop, you do OUR hard work". And if you don't like because they misrepresented functionality, then they point at the sign "developer hardware"... And it's all dev hardware. And they even sell dead and irrecoverable (without soldering/h…
This is such a shame too, because something that gives me a decent portable keyboard with Linux linked to mobile Internet, and proper Kernel mainline drivers meaning it's less likely to be abandoned after a year, was so enticing. But the same happened me - my P64 keyboard would connect but the battery wouldn't make pin contact with the phone, so charging the device was impossible without disassembly.
I understand it is low cost, but these rough edges impede enjoyment.
But, as an exception, I can say that the PineTime works wonderfully now. The PineBook Pro also is more or less functional with any Linux distro that targets it.
Re: OpenBSD 7.1 on PINE64 RockPro64
#4Have to say I'm not at all impressed with Pine as a whole. Their stuff is no support, bad documentation, lack of claimed functionality. They make hardware and then tell the community "whoop, you do OUR hard work". And if you don't like because they misrepresented functionality, then they point at the sign "developer hardware"... And it's all dev hardware. And they even sell dead and irrecoverable (without soldering/h…
Re: OpenBSD 7.1 on PINE64 RockPro64
#5Have to say I'm not at all impressed with Pine as a whole. Their stuff is no support, bad documentation, lack of claimed functionality. They make hardware and then tell the community "whoop, you do OUR hard work". And if you don't like because they misrepresented functionality, then they point at the sign "developer hardware"... And it's all dev hardware. And they even sell dead and irrecoverable (without soldering/h…
Re: OpenBSD 7.1 on PINE64 RockPro64
#6Have to say I'm not at all impressed with Pine as a whole. Their stuff is no support, bad documentation, lack of claimed functionality. They make hardware and then tell the community "whoop, you do OUR hard work". And if you don't like because they misrepresented functionality, then they point at the sign "developer hardware"... And it's all dev hardware. And they even sell dead and irrecoverable (without soldering/h…
Raspberry Pi feels more "polished" precisely because of that too - the active community means active project. And even then it is not free of hardware-backed errors and failing points.
Charging ICs are finicky things on its own - the risk of frying the board/device is always there.
So "landmines" are actually always present - get any random board like Radxa and try deviating even a little bit from "stock" GNU/Linux distribution and its outdated kernel, horrendous patches and binary blobs - and you'll get barely working hardware too.
In my experience the best outcome usually comes from developers being as open as possible; meticulously documenting and publishing everything related to the product, circuits and all.
p.s. Sheer manpower needed to fully QC and maintain at least PC-grade quality of circuitry of that level has to be comparable with said PC vendors employments, hundreds of people if not more. Pine64 and similar vendors operation is small, especially in comparison; they don't move product in that amounts.
p.p.s. being unable to boot from emmc on rk3399 device is new to me to be honest, if you drop by #pine64 irc channel on their server me and local folks can most certainly try to help with that.
Re: OpenBSD 7.1 on PINE64 RockPro64
#7Have to say I'm not at all impressed with Pine as a whole. Their stuff is no support, bad documentation, lack of claimed functionality. They make hardware and then tell the community "whoop, you do OUR hard work". And if you don't like because they misrepresented functionality, then they point at the sign "developer hardware"... And it's all dev hardware. And they even sell dead and irrecoverable (without soldering/h…
It's quite a shame how much better their hardware could be if they hired someone to do the in-house work for stable OS support on any of their devices.
Re: OpenBSD 7.1 on PINE64 RockPro64
#8Have to say I'm not at all impressed with Pine as a whole. Their stuff is no support, bad documentation, lack of claimed functionality. They make hardware and then tell the community "whoop, you do OUR hard work". And if you don't like because they misrepresented functionality, then they point at the sign "developer hardware"... And it's all dev hardware. And they even sell dead and irrecoverable (without soldering/h…
I read this as confirmation that "hardware is hard". Ie most of these premade SBCs have issues of this sort. The exception being the raspberry pi's generally. The alternative is designing and laying out the PCB yourself and with DDR3/4, that's a huge job (my understanding at least I've never done it myself).
Re: OpenBSD 7.1 on PINE64 RockPro64
#9Have to say I'm not at all impressed with Pine as a whole. Their stuff is no support, bad documentation, lack of claimed functionality. They make hardware and then tell the community "whoop, you do OUR hard work". And if you don't like because they misrepresented functionality, then they point at the sign "developer hardware"... And it's all dev hardware. And they even sell dead and irrecoverable (without soldering/h…
As marktangotango mentioned - the deal is roughly the same for all arm boards. Usually there is a lot of tinkering required, and boot process is convoluted and not standartized at all; and it is usually always up to the community to develop/adopt lots of that things. Raspberry Pi feels more "polished" precisely because of that too - the active community means active project. And even then it is not free of hardware-b…
The problem that you bring up in a meta- way is that these are the consistent responses I get from the open source devs. And as much as I appreciate the OS devs doing the hard stuff, basic functionality and hardware defect repair should ABSOLUTELY be part of Pine.
For example, when the PP keyboard has a bad support for the pogo pins, this should have been stopped, recalled, and fixed correctly. Instead, nothing. The open source devs said to use paper to shim it https://www.reddit.com/r/PinePhoneOfficial/comments/svc38r/v...
I mean, what the hell? Im glad fellow harmed users found a way forward, but seriously this is only 1 issue that makes Pine a shitshow to deal with.
And "Charging ICs are finicky things on its own - the risk of frying the board/device is always there." dismisses the fact that if a company wants to sell a product, "NOT CATCHING FIRE OR RELEASING SMOKE" is like the baseline here. Worst yet, early PP keyboard adoptees weren't even told this was an issue. Leaflets were only included later. But still, this is a shit situation - you have 2 USB-C ports. There should ne no situation where 1 port = hardware destruction. Again, make the hardware right or don't fucking do it.
Re: OpenBSD 7.1 on PINE64 RockPro64
#10Have to say I'm not at all impressed with Pine as a whole. Their stuff is no support, bad documentation, lack of claimed functionality. They make hardware and then tell the community "whoop, you do OUR hard work". And if you don't like because they misrepresented functionality, then they point at the sign "developer hardware"... And it's all dev hardware. And they even sell dead and irrecoverable (without soldering/h…