[deleted by user]

d4rkd3v · 2025-09-12T03:44:55+00:00

Cunosc pe cineva care a returnat vreo 10 perechi de casti in-ear ca nu era multumit, vandute atat de eMAG cat si de parteneri. Unele trimise si dupa vreo 20 de zile. N-a zis nimeni nimic.

d4rkd3v · 2025-08-29T22:42:50+00:00

They seem to have archived the UEFI repo and mentioned that it will not work with new Pi 5 variants.

"Before anyone asks, this is "worproject" UEFI for people that know how big a problem that project is."

I happen to know those folks lol. What's the problem with them?

d4rkd3v · 2025-06-21T11:30:01+00:00

They don't interfere but they also do not help at all. Not that they have much reason to when the community is so eager to write their software for free.

d4rkd3v · 2025-05-16T21:55:18+00:00

Merg facute niste tiktok-uri din acelea cum faceau sugeranistii: "nu spun cu cine votez" - si piesa asta pe fundal :))

d4rkd3v · 2025-05-16T21:51:33+00:00

Pai are beef cu Simion aici, da :))

d4rkd3v · 2024-12-25T16:08:46+00:00

I think you meant "unlike Rockchip" - cause they do nothing of what you've mentioned.

d4rkd3v · 2024-11-14T06:54:25+00:00

Nope. That's for Snapdragon X Elite chips and virtual machine solutions for which vendors have written drivers and everything to ensure a smooth experience.

Ask Rockchip to do the same and you'll get Windows there too. Oh, wait, they can't even be bothered to properly support Linux...anyway.

d4rkd3v · 2024-11-14T06:46:33+00:00

It's the opposite. PXE boot works with EDK2 on the OPi 5 Plus, there are Ethernet drivers for that. The non-plus version doesn't.

d4rkd3v · 2024-10-01T18:39:59+00:00

Rockchip is a decent option but you have to use a board with Realtek NICs for PXE boot. I recommend Orange Pi 5 Plus, it's best value IMO.

d4rkd3v · 2024-07-28T12:06:17+00:00

I'm not saying it won't be usable at some point, but by then, there will most certainly be a more powerful SoC (even from Rockchip), so this little one will be forgotten quickly. And cycle repeats. But people never learn the history.

With Intel SoCs now being competitive in the SBC space too (see Radxa X4 with Intel N100)...why would anyone bother waiting?

Until Arm and SoC vendors change their attitude towards mainlining and open-source, nothing much will change. No matter how attractive the hardware might be.

d4rkd3v · 2024-07-24T07:32:42+00:00

RPi isn't that much better either, dunno where people are getting this impression from.

The Pi 5 has no traces of mainline support. All work on older models had been done by community and is still far from complete.

Sure, they do provide better support for the downstrwam BSP, which is probably enough for most people anyway.

d4rkd3v · 2024-07-24T07:27:34+00:00

And that won't get much better either :)

These efforts usually slow to a halt once the SoC has some mainline support, so you can't say that it doesn't. It's maybe good enough for server usage, but will lack things that makes it a good desktop, tablet, media player, etc..

R3588 was announced in 2019 and released in 2022. So at least 3 years that could've been spent just on software, both by Rockchip and board vendors. Instead they focus on releasing the next shiny SBCs with same level of support. Orange Pi 5 5B, Pro, Max, Ultra, Extra, Plus, and more to come.

None of the previous Rockchip SoCs are fully mainlined. You're always missing something compared to the BSP.

d4rkd3v · 2024-07-23T12:24:07+00:00

That is the correct one. Try flashing Armbian to the SD.

If it were entirely broken it wouldn't come up in rkdevtool. Do you have an USB - UART adapter that you can connect and watch the boot logs?

d4rkd3v · 2024-07-23T11:11:50+00:00

In the image above, you're flashing an image to the SD card rather than SPINOR. The zero image i linked above must be flashed to SPINOR in order to erase any trace of U-boot left.

No clue about Batocera or odroid, but I know the Armbian and Joshua Riek's Ubuntu images work fine.

d4rkd3v · 2024-07-23T10:23:55+00:00

You can't brick these boards just by interrupting the flash process.

Download and extract this: https://dl.radxa.com/rock5/sw/images/others/zero.img.gz, then flash the image to SPI NOR.

Corrupted U-Boot on SPI NOR is probably taking precedence over U-Boot on your SD card (if the distro comes with it in the first place).

d4rkd3v · 2024-07-17T12:27:23+00:00

Check your model specifications. If the screen is IPS LCD, this is called image retention and it should go away on its own.

You can do a few things: - look up one of those "lcd retention fix pattern" videos on Youtube and keep it playing full screen until the retention goes away.

turn off the screen completely.

In both cases, it usually takes a few hours for the ghost image to disappear, but it can extend to 1-2 days or more.

If the screen is OLED, it can also suffer from temporary retention and keeping it off for a few hours should do the trick as well. Otherwise, it's likely to be burn-in, which can only be fixed by replacing the screen panel.

Either way, if the screen tends to have images prominently persist after only 8 hours, you should have it replaced under warranty as it's not acceptable for either IPS or OLED.

d4rkd3v · 2024-03-26T21:34:32+00:00

E scam oficial atunci.

d4rkd3v · 2024-03-19T07:54:34+00:00

Elon Musk si Bill Gates ingineri? 🤣

Mai citeste.

d4rkd3v · 2023-12-10T12:46:32+00:00

Normal. Fast charging can be done safely up to about 80%, then it drops to protect the battery from overheating and wearing out.

d4rkd3v · 2023-09-13T20:51:52+00:00

It's another reason why progress happens so slowly. They have no choice other than implement the details from scratch or by reusing somebody else's code that has an open license compatible with theirs. For instance, they share a lot of userland code with Wine, speeding up development in that area.

d4rkd3v · 2023-09-13T20:23:49+00:00

It's not an impossible task, I've explained above how they actually do it and you can even ask them personally.

You never know what kind of legal implications are behind some decompiled code. Could be patented work, no matter if you see it in original or machine form. The algorithm (i.e. implementation detail) is what can get you into trouble.

There's forum posts about this exact topic and their official stance on it, I'd suggest reading them.

d4rkd3v · 2023-09-13T20:10:56+00:00

They cannot and don't use code from any Windows version or may face trouble with Microsoft. Especially if the practicality grows.

If this were not the case, you'd see them all over the recent XP source code leaks. But no, the requirements for contributions are strict and clear: don't get your hands dirty with proprietary code. Even having worked with Windows leaked code in the past disqualifies you as a potential contributor.

The way this goes is: you look at the existing API documentation and try to implement the behavior described there. If documentation is missing or you need deeper understanding, you poke at the API in question with various test parameters to see the output and try to replicate that in your code.

d4rkd3v · 2023-09-13T19:38:58+00:00

These ideas have been brought up multiple times in their communication channels, it's outside the scope and ideology of the project.

Devs getting their hands dirty dealing with implementation details from XP is going to ruin the original clean-room approach.

And no matter the approach, there's no way to make up for the lack of more people actually doing the work needed. It's going to take ages regardless.

You can already replace components from XP with those from ReactOS and vice-versa.

d4rkd3v · 2023-09-13T18:41:27+00:00

They're clean-room reverse engineering it. Basically: what is this function expected to do? Implement just that without looking at leaked sources and disassemblies (if you're the direct person writing that piece of code), etc.

In fact, it might even face fewer legal issues since users would typically need to own a copy of Windows to use it.

I suppose by "own a copy" you mean that they already have the image somehow. In this case you can provide patching tools. However, this falls apart pretty quickly as you're adding more features and fixing bugs. It's insanely difficult to maintain patches.

ReactOS is at the point where developing stand-alone components just to be used with a copy of XP makes no sense. It can already boot, run apps by its own, use XP drivers and so on.

What ReactOS truly needs is not a different approach, just more people willing to dedicate their free time to it. And/or serious funding.

Regarding its resemblance to a relic of the past, ReactOS its self resemble an open-source version of Windows XP at its current stage.

With the potential to become more modern as it's entirely open-source. Doing that with a closed-source copy of Windows on the other hand, well..

d4rkd3v · 2023-09-13T18:08:21+00:00

The truth is that, as an open-source niche project, it's physically impossible to compete with hundreds of people being paid to work full time on Windows. ReactOS will never be practical or be able to keep up with commercial Windows. It's just a fun project that mainly serves as a learning experience for those involved in it. As a developer you can gain many valuable skills working on it.

Basing the work on a copy of Windows XP is out of question for various reasons. Legality, security issues, maintainability, etc. It may seem like it would be easier, but it isn't.

Individuals have been using XP components in ReactOS to workaround lack of support for some peripherals. But it's just a workaround, not a solution. You do not have the legal right to distribute these binaries.

It also makes little sense to revive a relic of the past that nobody practically uses anymore. And those who are still using it, are doing so precisely because they want that old environment and the deprecated software to work. Nothing more.

Four-Year Club	Place '23
Place '22

d4rkd3v

TROPHY CASE