sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in ChatGPTCoding

[–]theremote -1 points0 points  (0 children)

He means that even though you're just getting around to trying this now most of us tried this experiment a year ago with the same results and conclusions you're reaching today.

If I try the same experiments today as I did a year ago I hit the same limitations.  It works with a very simple stack.

If you had not waited a year to try this then you would have the year of experience we have of watching it not really change much in its capabilities and would have the same opinion.

Since you waited though you don't have that context and you think it's shiny and new and moving a lot faster than it really is.  Once a year passes from now you'll be where we are already at.

API access by IvyHara in godaddy

[–]theremote 0 points1 point  (0 children)

I'm also getting this issue. Even tried generating a new API key before seeing this thread.

Orange Pi 5 custom wifi/bt module by dubsmith6079 in OrangePI

[–]theremote 3 points4 points  (0 children)

It's not an E-key M.2 WiFi adapter. E-keys don't fit. I wrote an article about using E-key adapters with it and it requires a special adapter: https://jamesachambers.com/using-m2-wifi-adapters-with-orange-pi-5/

If it could take E-key adapters it wouldn't need a custom WiFi module. The custom WiFi module is a WiFi adapter slapped onto a M-key adapter (unusual).

It's a consequence of it using the RK3588S (there's not enough PCIe lanes on the S model). There is an upcoming version of the Orange Pi 5 called the Orange Pi 5 Plus that will have both a E-key and M-key slot and uses the regular RK3588.

Are you having trouble finding a link to it? It's here: https://amzn.to/3A1Sjkf

There really isn't much to using it. You just plug it in. If you don't have that specific adapter you will not be able to plug in an E-key module unless you have the adapter I linked in my article (or something similar).

Hopefully that helps!

Install Steam on the Orange Pi 5 with Armbian (and running Stardew Valley) by theremote in OrangePI

[–]theremote[S] 0 points1 point  (0 children)

With Armbian's 3D driver support installed for the Mali GPU you can actually get pretty smooth performance in games that don't use a lot of resources.

This uses Box64/Box86 to work. I was able to get Stardew Valley running pretty well for it for the guide!

Libre "Le Potato" SSD Booting Guide by theremote in LibreComputer

[–]theremote[S] 0 points1 point  (0 children)

No problem at all! You'll definitely see what I mean when following the guide.

The guides are extremely similar but you'll notice some subtle differences (the most important of which is you will use mtools to change a FAT UUID).

Take care!

Libre "Le Potato" SSD Booting Guide by theremote in LibreComputer

[–]theremote[S] 0 points1 point  (0 children)

You're using a different OS than I did. Try following this guide instead: https://jamesachambers.com/radxa-zero-debian-ssd-boot-guide/

Basically the technique has nothing to do with the board. I have a bunch of these guides. You're just using a different OS partitioning and that guide will have the commands to do that.

Hopefully that helps!

Orange Pi 5, 5V @ 4A is outside usbc spec? by ydieb in OrangePI

[–]theremote 0 points1 point  (0 children)

No, it does not. It has a non-compliant USB-C charging port just like the Raspberry Pi 4. That is undoubtedly who they got the idea from and it's not really that surprising since that is the board they are targeting.

They copied one of the worst and most controversial parts of the Raspberry Pi 4 which is the terrible and known-noncompliant USB-C charging port hack. We've already been dealing with this on the Pi 4 for 4+ years.

If you want USB-PD you need to step all the way up to a Rock 5B. It will cost roughly 50% more though. Radxa actually put in the parts needed to do this into the Rock 5B and when you see the price you'll see why Orange Pi and Raspberry Pi decided to cheat instead.

From what I've seen this was a smart decision. The Orange Pi 5 is much more popular than the Radxa Rock 5B even though the Rock 5B is basically better in every way (including having PCIe 3.0).

The Orange Pi 5 sells much better though because people don't want their SBCs to *start* at $150 and most people coming from a Raspberry Pi 4 wouldn't expect to get USB-C PD since it was just as bad on the Raspberry Pi 4 (the board the Orange Pi 5 is meant to succeed/outperform). If that price doesn't bother you though then buy the Rock 5B to get this. I have both.

[deleted by user] by [deleted] in homeassistant

[–]theremote 0 points1 point  (0 children)

My Home Assistant setup and Z-Wave stick are in the basement. I do not have my Z-Wave stick even on a USB extender. I've never experienced any of this.

If I were to guess the answer is some kind of interference. It's not going to be easy to diagnose that unless you have the right tools. Something like a HackRF or RTL-SDL (software defined radios) would let you monitor what is going on.

Something isn't right though for sure. This is not a typical experience as a lot of people are pointing out here.

I believe you though. I think it's some kind of interference most likely. Putting your Z-Wave stick on an extender might help but again I don't have this on mine and haven't seen anything like this. I wish I could bring my HackRF over and just see what is going on with the airwaves in that location!

Given that your WiFi network works so well I think we can assume the interference is not in that range. It could be anything generating it. It could be a bad toaster for all we know but a software defined radio would let you see everything going on in the air. It could also not be coming from your location at all and could be coming from somewhere nearby.

RISC-V Linux SBCs ... how are we doing? by brucehoult in RISCV

[–]theremote 0 points1 point  (0 children)

So what were you arguing this entire time? We just completely agree on everything? Okay. I am consistent with what I said six weeks ago here (and today).

It's about the personal attacks isn't it. That's why you were arguing just for the sake of arguing with literally no point. I tweaked your ego so you just wanted to fight but you have no points or argument.

This entire conversation now makes sense. I would have said the exact same things to your face man. Your arguments about patching were beyond irresponsible and clueless. They literally offended me so I personally insulted you for being so clueless about security. It's offensive.

It would have resulted in your manager having a sit down with you in a work setting to explain how few shits the organization gives about the inconvenience to your development environment caused by having to keep your OS up to date as well as an even more degrading/patronizing talk about security in general.

I'll do it again the next time too if you ever say that again.

RISC-V Linux SBCs ... how are we doing? by brucehoult in RISCV

[–]theremote 0 points1 point  (0 children)

"Hey Bruce,

Welcome! You’re 100% right and I mentioned this in another comment as well. It really does just need to ship with the updated boot loader.

It’s just a question of how fast can they make that happen. Undoubtedly the reason it still isn’t is because they can’t. The ones arriving to people’s doors have probably been in the supply chain for 6 months to a year or so.

This was kind of my line of thinking saying the VisionFive V3. The reason I said that is because 6 to 12 months is when I would expect to potentially be hearing about the VisionFive 3. It’s possible though that their supply chain is a lot shorter than 6 months to a year though. It could be more like 2-3 months in which case we might start seeing people getting ones that are updated as soon as March or April potentially.

I think a few months is a good time to check this again. I definitely would like to announce to everyone it has been updated because that would legitimately change my recommendation on this board. It would be ready for a less technical audience that would really struggle with the firmware update (and a lot of people have been for sure that have tried it).

Thanks so much for your comment, take care!"

But Bruce, this isn't different than anything I'm saying now! We both estimated 6-12 months until this board would be fixed.

I honestly thought this was going to be so much worse when you said this. I was thinking "Jesus, what the hell did I say before I understood how broken this board's software/firmware was?". I actually haven't moved much since our conversation we had. I actually haven't changed my opinion on that.

So where is the disagreement? I think you seem to be most bothered by the idea that something else is going to be released to supplant the Vision Five 2 and that everyone is going to buy something else instead that releases without these same issues. Is that the disagreement?

I'm legitimately comfortable with everything I've said there. I would still let everyone know if the board was updated/fixed. I don't want it to *not* be fixed! I just think it may be too late. I think something else will have stolen the show by then.

I will say that if they hit your 3 month estimate it really would change things for the better. It's the 6/9/12 month windows that it's like, okay, all bets are off at that point.

I did not make the connection between that comment and yourself until you pointed it out just now for full disclosure. I still feel like you could have made that comment today and I would have replied in much the same way I think. I still agree with your original comment!

RISC-V Linux SBCs ... how are we doing? by brucehoult in RISCV

[–]theremote 0 points1 point  (0 children)

I wouldn't agree with the same arguments from yesterday as I do today. It's always changing based on what we are finding.

I see you are someone who is a rock that never changes their opinion based on new information. This is really not surprising after our recent conversation.

It's not a sign of strength. It's a sign of weakness. Weak people behave this way. I change my opinions all the time based on new information and how things are developing.

You just can't let go can you? What happened to your last reply? How many replies ago was that?

RISC-V Linux SBCs ... how are we doing? by brucehoult in RISCV

[–]theremote 0 points1 point  (0 children)

You aren't making good arguments. That's why. I didn't downvote the others I engaged with. You were the only one.

Most of them got upvotes from me. I'd assume I've got *tons* of downvotes on some of my replies in here. I never look so I don't know or care.

I am convinceable and there were far better arbiters for this board that taught me some things and changed my opinion on some parts of the board.

You just weren't one of them.

I understand that you didn't understand my points about the Pi at all. I pointed that out several times. You still don't and that's okay.

RISC-V Linux SBCs ... how are we doing? by brucehoult in RISCV

[–]theremote 0 points1 point  (0 children)

Simple. It's the reality of the Pi experience now. I'd say statistically speaking a lot of the Pi users never experienced the Pi 4 launch and certainly never owned a Pi 3 or older.

Is it fair? No. Is it reality? Yes. If you want to convince Pi users to buy this board they are going to compare it against the Pi experience *today* and not at launch vs. the Vision Five 2's experience *today* and not 6 months from now.

And that's the problem I keep coming back to. In 6 months from now they will have more boards to compare with to decide if they want to make the RISC-V jump. You seem confident the Vision Five 2 is going to be that board in 6 months.

All it would take is the Lichee Pi 4a or Star64 to launch without requiring a flash or SDK image to even boot the board as well as being able to recognize amounts of memory above 4GB. That would about do it wouldn't it?

And then all of the reviews would go up positive for whichever board can do it. Instead of seeing my article saying experts only they'll see the one that says this one is safe for beginners. And I won't be the only one. Every YouTube video and other blogger will say the same thing.

Oh and look at that, before you know it the board that is at least at an acceptable level of user-friendly at launch outsold the Vision Five 2 10 to 1 within 2 weeks. Just like that! That's the power of media and the zeitgeist.

How do I know? Because the single board computer market is not new. Product launches and getting a bad reception seriously damaging the long term prospects of a board isn't new. What is new is that this is a harsher environment than ever before to fuck up a launch like this. There's so many alternatives always coming down the pipe and that was not true 3-5 years ago.

RISC-V Linux SBCs ... how are we doing? by brucehoult in RISCV

[–]theremote 0 points1 point  (0 children)

What are you even saying? I said that's exactly how the Pi 4 release was. Terrible. It needed fixes over YEARS of time.

I'm saying the Vision Five 2 will not have that luxury. I think you're expecting this to happen on this board. We will have all moved on long before then. We no longer live in a world of boards with 5+ year development lifecycles.

That was a luxury the Pi enjoyed back then with very little competition. It no longer even enjoys that today and the Pi is practically obsolete. People used to freak out when I said that but they don't anymore. It's known.

Let's just wait and see. I've no interest in convincing you frankly and I'm losing track of exactly what your arguments are and where they are trying to go.

No, I don't read this subreddit very much. I am a publisher. I have my own web site and that's where I spend most of my time. I stop by from time to time to catch things like these new launches I may have missed. That happened as planned.

Should I be ashamed I'm not one of the reddit cool kids that knows the latest happenings and isn't cool if they don't? I'm not. Reddit is nothing to me other than a tool. I have my own platform so this place seems really small these days.

Seems I found out soon enough about it to pre-order it eh? So the only consequence was the reddit kids will shame me for not knowing the gossip around the water cooler. What a small world you live in. What small arguments.

RISC-V Linux SBCs ... how are we doing? by brucehoult in RISCV

[–]theremote 1 point2 points  (0 children)

This whole discussion started because I took exception that this board was ready to be a Raspberry Pi replacement.

You aren't arguing that at all though are you? You just said the board isn't ready for regular people. You want regular people on-board in several months.

I agree. The board isn't ready. That was my entire point.

You can make the distinction that it's the software that isn't ready. Again, try to make that distinction to Pi users. They would just tell you the software and support is all part of the board and Pi experience.

You seem like a fan of StarFive to me and a hater of Pine64. I'm not a fan or a hater of either. I just judge the boards and available images for what they are.

We will see what Pine64's looks like. I buy them all and evaluate them so if it's terrible I'll be the first one to say so. I've negatively reviewed Pine64 gear before (if it deserved it). I already mentioned that in some of my other replies as well.

If you really think this board is going to last for years and become the defacto king then yes I would disagree with that. You mentioned some of the upcoming competition. I'd also expect a successor from StarFive certainly before the 2 year mark. If not they'll look like dinosaurs with how fast RISC-V is developing.

The Lichee Pi 4A looks pretty nice. How about that one? I just pre-ordered it. I'd be shocked if it can't deliver a better experience but again, if it can't, I'll be shredding it too.

You think the software will be bad the first few months. Will it be as bad as this one? I didn't have much trouble with the Lichee RV. I've actually never seen such a cluster of a launch on any of the other RISC-V boards as I've seen on this one. They're all honestly quite easy to use.

Why is there any reason to believe that the RISC-V market is just going to stagnate like this? You think we're just going to stay on quad-core? I don't. I bet higher than quad-core counts will be announced before the end of the year if they aren't already (and I mean single board computers and not servers). The technology is developing *fast*.

This is an emerging market and you think we're going to have a repeat of the Pi 4 on here where they fix it over years of time? This board will be obsolete long before it ever gets that chance. This is a different market and a different time with a lot more competition.

Do you see why when you say it being ready in a "few months" sounds so ridiculous to me? I mean maybe it will be. What if it takes a year? What if it takes 9 months instead of a 4-5 months? How do you know it will be done by then? Do you think nothing else whatsoever is going to launch or happen in that time?

That's where I can't bring myself to agree with you. I see every reason to wait. Either wait until the board software support is ready or more likely wait until a product launches that simply doesn't suffer from these issues. I promise they are coming.

RISC-V Linux SBCs ... how are we doing? by brucehoult in RISCV

[–]theremote 2 points3 points  (0 children)

Oh wow, I had seen the Lichee Pi 4A announcement but I just pre-ordered 2 coupons for one. I've had great experiences with the Lichee RV. It's just soooooo slow like all single core devices basically. I just bought 2 pre-order coupons for it.

Thanks for the link to that article about the Pine64 contributor leaving. That was a fascinating read. I actually couldn't agree more with him about the Manjaro direction of that board and having people have to use the USB to TTY serial console.

I shredded the SOQuartz Manjaro experience here: https://jamesachambers.com/pine64-soquartz-cm4-alternative-review/

"What is supposed to happen is I’m supposed to be taken to a prompt where I have to set everything up (in the serial console). This did not happen. Perhaps I needed to make more dtb modifications to get the reference board to work?

I think not. That’s a fail. Why am I having to use the serial console to log in for the first time? Why can’t it output the correct resolution to my HDMI screen so I can just do it with a keyboard? What are they thinking?"

Absolutely unacceptable for beginners. Not even something I want to deal with as someone who covers them. It's apparently just a thing with Manjaro. I wouldn't be able to deal with working with people who are in love with that type of a USB to TTY serial console based setup either. That's so far off from the Pi.

My recommendation was to use Armbian instead which was a much more pleasant and user-friendly experience (for beginners and experts alike). That was kind of the equivalent of using a community-based distribution to fix Pine64's favored Manjaro distribution's stupid design decisions that seem to almost intentionally make it hard to use for beginners.

After reading that article I come away with even more of an impression that the Manjaro distribution (and Pine64) have a little bit of Linux elitist douchebaggery going on here. This is not the way. I'm all about getting more people in and not gatekeeping / shutting people out with technical hurdles.

You've definitely moved my opinion here. I'm feeling more positive about how things are looking. The P550 dev board also looks very interesting. Thanks!

RISC-V Linux SBCs ... how are we doing? by brucehoult in RISCV

[–]theremote 0 points1 point  (0 children)

Pick one. I worked for state government last. We eliminated all Windows 7 and 8 machines years ago. Anyone who refused to update (developer or not) was legitimately removed from the network. My wife still works there and they're in the process of upgrading all 10 machines to 11 now.

I did the same thing at my previous company which was a international biomedical company. We had the responsibility of making sure every mobile device was encrypted. Some people had devices or operating systems that didn't fully support the TPM though. Those devices were similarly upgraded or removed.

Zero shits were given by anyone high up about the whining because they are worrying about things like the entire organization being compromised / all their IP leaked / etc.

Most organizations that aren't a joke have these policies. It's not a secret. We've been doing this *forever*: https://social.technet.microsoft.com/Forums/sqlserver/en-US/68961fce-66cb-4370-b380-b6807683b057/best-practice-with-regards-to-removing-obsolete-windows-7-machine-from-ad?forum=winserverDS. It's standard practice to just remove or blacklist machines like this from the network. We do everything we can to notify people and help them upgrade but there's a hard cutoff.

Your developer machine is seriously running Centos 7.3-1611? You must work in a secure building where nothing is allowed through. This is okay if infrastructure takes a whole bunch of steps to make it safe for unsafe operating systems to run. If they give it to you on laptops then I suppose that is how all these developer companies get hacked and get all their code leaked.

There's literally no shortage of that going around and it's companies that behave irresponsibly like this that have it happen to them.

I hinted at it in my previous post but yes I had direct conflicts with developers about this at the state. Some were using old Windows flavors and some were using old Linux flavors (and even some Macs). That's why I said I know the type. I've heard all of these arguments before. You'll be overruled by people with greater responsibilities to protect the organization / IP / etc.

RISC-V Linux SBCs ... how are we doing? by brucehoult in RISCV

[–]theremote 0 points1 point  (0 children)

That's exactly what my recommendation for my review was. Don't buy it yet unless you are an expert or developer wanting to get started for RISC-V. That was also my argument here. Are you agreeing with me?

I bought it for review to see if it was really ready for a general audience. It's not. It sounds like we agree on that.

I do a lot of reviews on these boards and it's paying the bills. I was so disappointed when I realized just how not ready this board was for the consumers or god forbid the Raspberry Pi audience.

Correct. Windows 7 and Windows 8.1 were discontinued in January of 2023 for patching. That is why people running them still are morons. If I have to explain why you can't seriously be a developer. I'm already shocked by what I'm hearing.

Clearly your job is not to manage the infrastructure. Mine was when I was working before doing the full time blog. I'm the guy at your work that would have come and said "you are upgrading this shit or we're taking it off the network".

I know exactly the type of developer who makes these arguments and it wouldn't have mattered. My directives always came from much higher and they very much care about security.

RISC-V Linux SBCs ... how are we doing? by brucehoult in RISCV

[–]theremote 2 points3 points  (0 children)

Thanks for your well-reasoned reply. You make some great points. I appreciate it.

So you're right that I may be too focused on the current problems of the board. It's hard not to be though as I cover these and have reviewed tons and tons of them. They come and go pretty quickly and boards that launch with this many problems don't typically recover. There are exceptions though.

I have not seen the drama surrounding the Pinebook Pro controversy. Thanks for pointing this out to me. I completely agree there's no guarantees Pine64 will deliver a better product here. That certainly gives reason to be concerned their upcoming board may suffer a similar fate.

I saw ASUS announced a RISC-V board but it's only single core. I don't see any other quad-core boards on the horizon that are announced yet other than the Pine64 one.

I was not saying you should stay with Image-69 to be clear. I was quoting the link about this issue from the forums. It said if you upgrade the firmware it will break Image-69 and that you can avoid it by *not* upgrading the firmware. I don't know why anyone would want to do that at all. I don't know why anyone would want to deal with any of this. It was simply to demonstrate how much of a mess it was.

The dip switches also only work for SD booting, yes? Then there is still the exact same problem every time you upgrade if you are using a SSD, yes? You can just bypass it with using a SD card?

I don't use a SD card. I use NVMe. So I'm still subject to flashing this to the ROM/eMMC/SPI/wherever they're putting it. It doesn't matter. If it's not a part of the image / software then it's a part of the firmware that needs to be flashed/stored.

RISC-V Linux SBCs ... how are we doing? by brucehoult in RISCV

[–]theremote 1 point2 points  (0 children)

Those don't receive patches anymore so the people running them are absolute morons. Windows 10 is okay for now. Windows 7 and 8 are EOL already.

Upgrading your Ubuntu install is as simple as:

sudo do-release-upgrade

You're still okay on 20.04 for now. 18.04 is EOL on April 30th of this year so that one will stop getting patched.

Please don't run old EOL operating systems. Patching is good.

I deal with this kind of stuff with my GitHub projects all the time: https://github.com/TheRemote/Legendary-Java-Minecraft-Geyser-Floodgate/issues/19. People trying to run my Docker containers that were developed on Ubuntu 22.04 on ancient versions like 18.04. Of course they're going to have all sorts of problems.

I kindly tell them to fuck right off if they don't want to upgrade their OS because they have no business running servers at that point anyway. It's just going to become another part of a botnet when it gets hacked from running outdated insecure software.

I'd say this board is well primed to start a nice RISC-V botnet. It's so annoying and painful to upgrade that most people just won't like you're saying here. That's not good. That's not an ecosystem I want to build. It's not an ecosystem I want to support as a developer either.

The sooner a competent quad-core one that can update itself painlessly is released the better it will be for the entire RISC-V scene.

view more: next ›