Marcin Juszkiewicz

Twenty-one years of blogging

2026-04-01T10:13:00+02:00

This is 3th (or 4th) version of my website and I hope that this time it will stay for much longer and that I will use it more often to publish some OpenEmbedded related articles and informations.

And here we are, 21 years later. With the same website.

Time flows

For sure I managed to keep it running “for much longer” than any earlier version of my website. The previous one existed for about two years. Older ones were more Lynx bookmarks split into several files rather than a website.

Engines

When I started this website in 2005, WordPress was something new. Easy to use, no HTML knowledge needed etc.

In 2006, I created my own consulting company and moved to WordPress MU (MultiUser). I had two separate websites then — one for my company and my personal blog. Merged them into one a few years later.

In the meantime WPMU got integrated into WordPress. And one day I recreated the whole website on a fresh install of WP to cut more than half of the database size — there was a lot of unused data left from several plugins I used through all those years.

And then, in 2019, I said “good bye” to WordPress and moved to Pelican, static page generator. It was a good move. It cost me a day or two of handling WP export, cleaning posts, sorting out tags, images etc. It was worth it — I still use Pelican to generate this website.

Grammar and language

Reading old posts (especially pre-2010 ones) shows how awful my English grammar and vocabulary were. In 2010, when I signed contract with Canonical to work at Linaro, I went to language school to work on improving both grammar and vocabulary. And it paid off.

I am not going to edit language of my old posts. I may alter tags, formatting or fix/remove links in them. But not how they were written. I keep them as a reminder how my English looked in the past. Not that it is fluent and nice nowadays :D

Markdown all the time

I have never been a fan of using HTML to edit blog posts. So when I discovered Markdown I started using it. With PHP Markdown Extra extensions.

My current Pelican configuration for Markdown is simple:

MARKDOWN = {
    'extension_configs': {
        'markdown.extensions.extra': {},
        'markdown.extensions.meta': {},
        'markdown_del_ins': {},
        'yafg': {},
    },
    'output_format': 'html5',
}

It gives me abbreviations, attribute lists, definition lists, fenced code blocks, footnotes, markdown in html, tables, meta-data, delete and insert tags and the ‘yafg’ extension wraps images into the <figure> tag with a caption. In other words: all stuff I ever used in any post.

Social Media

Around 2009 - 2011 I started using social media and blog slowly started getting fewer short entries as those went to twitter, facebook and google+ services.

Still kept the rule of posting long texts on my website with links shared rather than posting only on social media.

Article	Hacker News	Lobster	points	comments
RISC-V Is Sloooow	thread	thread	317	379 + 111
64-bit ARM desktop hardware?	thread		243	169
Bought myself an Ampere Altra system	thread	thread	206	97 + 9
Arm desktop: emulation	thread	thread	98	50 + 7
Twenty years of my work with Arm architecture	thread		94	54
What is wrong with all those AArch64 desktops?	thread		90	141
AArch64 Boards and Perception	thread	thread	67	31
How to Survive FOSDEM	thread	thread	42	15 + 5

Popular tags

It is easier to check which tags were the most popular during all those 21 years:

tag name	number of articles
Linaro	177
Ubuntu	170
AArch64	154
OpenEmbedded	129
Fedora	114
Nokia	90
development	84
Debian	82
Openmoko	70
conferences	64
life	64
phone	58
travels	52
Linux	51
Maemo	47
OpenZaurus	45
Arm	44
website	41
Poky	40
Zaurus	40
Red Hat	31

The high position of the Ubuntu tag suggests a need for review as for some posts it was used to get them placed on the Planet Ubuntu aggregator.

With the Nokia-related posts comes a story. Each post bumped ‘karma’ on Maemo.org website. And I mostly complained in them. But ‘karma is a beach’, right? I got it high enough to get invitation to the Nokia N900 developer program. It was a nice phone with software written to gather complaints.

Requested edits

During all those years there were some requests to edit some of my posts. I rejected some and fulfilled others.

No camera, please

In 2009 I received NHK15 developer board from ST-Ericsson. As I had not signed any NDA, I decided to show them the post before publishing to make sure I do not mention too much.

Can you remove the camera module from it? It will not be in a boxes we give out during the event.

I took one photo again, removed mentions of a camera module and published.

Move forward two months to the ST-Ericsson Community Workshop 2009 event. A day before it, decision was made to include that camera module. One guy was going through each box to add it…

Pre-announced SBC

Most of Linaro Connect events had a ‘Demo day’ event where companies, projects and developers presented some interesting things related to our work. I was there walking, looking and asking questions.

And one year I asked a company (sorry, no names this time) will they have an SBC similar to the Beagleboard. And the answer was “yes, it will be called A_NAME”. I asked was this information public and can I write about it on my blog. Got confirmation, so an hour later I mentioned it in a blog post.

A few minutes later, when I was going to the hotel bar for an evening event, I was asked by my manager where I got that info from. And then got a request to remove it “because they plan to announce it next week on some BIG trade show”.

I took my phone from my pocket, edited and we went for a beer.

Lessons learnt

Whenever non-public information is shared, wait until it is properly announced publicly. Then, check how much information was released. My work is related to many non-disclosure agreements (NDAs). So, if I know something, it needs to be checked against public information before I can disclose any of it. You may also want to confirm with an official source that the public disclosure was not due to a leak or other incorrect source of information.

Fewer technical posts

If you look into archives page you may notice that there are fewer technical posts than there were in previous years. There is a simple explanation for it:

Well, you are some kind of influencer, get over it. People do pay attention to what you write.

Writing a technical post nowadays means:

asking a few people who know stuff to check whether I was right or wrong
asking a few people who do not know stuff to check what I missed
doing some technical review and correction

This changes writing a post for a personal blog into writing a technical article.

And then publishing still means a lot of online comments where maybe 25% of them make any sense.

Plans for the future

I do not have any special plans for the future of this website. Will keep it operational and add posts from time to time. I still have some ideas for the content and have some drafts which wait for my retirement.

Upgraded to OpenWRT 25.10

2026-03-24T08:18:00+01:00

I upgraded my router to OpenWRT 25.10. Nothing strange right?

And then I realized that I use OpenWRT for over twenty years…

All started with Linksys WRT54GS

Long, long time, when I worked from an office, I got Linksys WRT54GS as a donation. IIRC I got money to buy it as this was simpler than sending device from abroad.

Having Wi-Fi at home allowed me to test more stuff on Sharp Zaurus devices. Or install/upgrade packages in an easy way.

It was running OpenWRT WhiteRussian for quite a while as device upgrades were quite problematic at that time.

Other devices

During next years I used a mix of devices running OpenWRT. Routers, access points or devices which served both those functions at the same time.

Netgear WNDR4300 N750 brought 5GHz Wi-Fi network to my flat. Running MiniPC + Belkin BT3200 (aka Linksys E8450) combo brought network separation as I started using VLANs. Etc. etc.

Why OpenWRT?

Having a unified way of doing network setup was a key for me when I was choosing next router/AP device. Or ability to install additional packages which brings more functions. Especially since 512 MB RAM became popular in a router.

Why it matters to me? I am not a network admin. Never planned to be. So being able to switch to a new device and restore configuration from a previous one saves my time.

There are no limitations on how I name my Wi-Fi networks (national characters, emojis, spaces), how many of them will be, what kind of firewall zones I want and which devices/networks are in which zone. Etc…

RISC-V is sloooow

2026-03-10T18:53:00+01:00

About 3 months ago I started working with RISC-V port of Fedora Linux. Many things happened during that time.

Triaging

I went through the Fedora RISC-V tracker entries, triaged most of them (at the moment 17 entries left in NEW) and tried to handle whatever possible.

Fedora packaging

My usual way of working involves fetching sources of a Fedora package (fedpkg clone -a) and then building it (fedpkg mockbuild -r fedora-43-riscv64). After some time, I check did it built and if not then I go through build logs to find out why.

Effect? At the moment, 86 pull requests sent for Fedora packages. From heavy packages like the “llvm15” to simple ones like the “iyfct” (some simple game). At the moment most of them were merged, and most of these got built for the Fedora 43. Then we can build them as well as we follow ‘f43-updates’ tag on the Fedora koji.

Slowness

Work on packages brings the hard, sometimes controversial, topic: speed. Or rather lack of it.

You see, the RISC-V hardware at the moment is slow. Which results in terrible build times — look at details of the binutils 2.45.1-4.fc43 package I took from koji (Fedora and RISC-V Fedora):

Architecture	Cores	Memory	Build time
aarch64	12	46 GB	36 minutes
i686	8	29 GB	25 minutes
ppc64le	10	37 GB	46 minutes
riscv64	8	16 GB	143 minutes
s390x	3	45 GB	37 minutes
x86_64	8	29 GB	29 minutes

That was StarFive VisionFive 2 board, while it has other strengths (such as upstreamed drivers), it is not the fastest available one. I asked around and one of porters did a built on Milk-V Megrez — it took 58 minutes.

Also worth mentioning is that the current build of RISC-V Fedora port is done with disabled LTO. To cut on memory usage and build times.

RISC-V builders have four or eight cores with 8, 16 or 32 GB of RAM (depending on a board). And those cores are usually compared to Arm Cortex-A55 ones. The lowest cpu cores in today’s Arm chips.

The UltraRISC UR-DP1000 SoC, present on the Milk-V Titan motherboard should improve situation a bit (and can have 64 GB ram). Similar with SpacemiT K3-based systems (but only 32 GB ram). Both will be an improvement, but not the final solution.

Hardware needs for Fedora inclusion

We need hardware capable of building above “binutils” package below one hour. With LTO enabled system-wide etc. to be on par with the other architectures. This is the speed-related requirement.

There is no point of going for inclusion with slow builders as this will make package maintainers complain. You see, in Fedora build results are released into repositories only when all architectures finish. And we had maintainers complaining about lack of speed of AArch64 builders in the past. Some developers may start excluding RISC-V architecture from their packages to not have to wait.

And any future builders need to be rackable and manageable like any other boring server (put in a rack, connect cables, install, do not touch any more). Because no one will go into a data centre to manually reboot an SBC-based builder.

Without systems fulfilling both requirements, we can not even plan for the RISC-V 64-bit architecture to became one of official, primary architectures in Fedora Linux.

I still use QEMU for local testing

Such long build times make my use of QEMU useful. My AArch64 desktop has 80 cores, so with the use of QEMU userspace riscv64 emulation, I can build the packages without buying RISC-V hardware. Still, there are timed out tests because single thread is slower than native one.

btop shows 80 cores being busy

There are package (like LLVM) which make real use of both available cores and memory. I am wondering how fast would it go on 192/384 cores of Ampere One-based system.

Still, I used QEMU for local builds/testing only. Fedora, like several other distributions, does native builds only.

Future plans

We plan to start building Fedora Linux 44. If things go well, we will use the same kernel image on all of our builders (the current ones use a mix of kernel versions). LTO will still be disabled.

When it comes to lack of speed… There are plans to bring new, faster builders. And probably assign some heavier packages to them.

Books I read in 2025

2025-12-30T23:06:00+01:00

I enjoy reading and I am known for being a fast reader. In 2025, I read one hundred books…

So what kind of books did I read? Mostly science-fiction, but also some biographies, thrillers and a few random ones.

Space operas

As in previous years, I continued reading the “Undying Mercenaries” series by B.V. Larson. It is an easy to read series — I can read a book in the evening and forget what was there during sleep.

There was “The Murderbot Diaries” by Martha Wells. Mostly because there was an announcement of a TV series (which (surprise, surprise) turned out to be worse than the books). I read the first five books in Polish and the last two in English, as they had not been published yet. If you plan to read them, I recommend the “1, 2, 3, 4, 6, 5, 7” order as “System Collapse” (7th book) starts at the end of “Network Effect” (5th one), while “Fugitive Telemetry” is more a single story happening before “Network Effect” one.

I started reading “Expeditionary Force” by Craig Alanson. It was an interesting space opera, but became boring at some point so I ended on “Aftermath” (the 17th book). How long you can keep up with a series where humans keep playing with other galactic civilisations, all thanks to the help of an ancient AI?

After many years, I collected all parts of “Sector General” by James White. All twelve books. It was fun to read but it feels old. And recently Russ Allbery mentioned “Machine” and “Ancestral Night” by Elisabeth Bear as a modern series with similar vibe.

When it comes to old authors, I also read “To the Stars” series by Harry Harrison.

The other series was “Shadow Raptors” by Sławomir Nieściur. Common theme: humans fighting some other species. In space.

Military fiction

Another space series was “Stark’s War” by John G. Hemry (as Jack Campbell). A war on the Moon over the control of resources.

There were two series by Vladimir Wolff: “Nowy porządek świata” (“A new world order”) and “Armaggedon”. It is hard to tell how they differ cause they share some ideas. The world as we know it ends, old forces vanish, and new ones appear. It is fun to read about a “near future” where Poland becomes a new global force, while the United States vanishes due to a virus killing nearly entire population.

The “All You Need Is Kill” by Hiroshi Sakurazaka shows how much story can be changed before film adaptation is created (the “Edge of Tomorrow” was based on this book). Highly recommend.

Other fiction

There were books by Andrzej Kwiecień — “Metamorf” and “Dori”. Some kind of cyberpunk stories in a world where androids can take human’s form and personality. Light read.

“Kaori” by Marta Sobiecka was a cyberpunk crime story. Reading reviews does not remind me a book, which shows that it was mediocre one.

Other cyberpunk was set of stories called “Cyberpunk Girls”. Some were good, some were not.

Another collection was the “Frostpunk, Antologia” — a set of four stories in the steampunk world of the Frostpunk game (which I have never played).

And while we are around alternative world of XXI century I have to mention “Ciepło-zimno” by Joanna Mazur. Deeper in climate change, with nine months long summer, no electricity during some parts of a day, main character is a freelance worker, happy to have some work at all.

There was “Czarownica znad Kałuży” postapo story by Artur Olchowy. Small village in a middle of nowhere, with “a witch” living just outside of it. And one day a priest arrives and tries to change the way those people live. It was an interesting read, despite common oversimplifications (as usual in postapo stories).

Then was Blake Crouch with his “Dark matter” and “Recursion” books. Both are about travelling to the other versions of the world. In “Dark matter” those are parallel universes, where the main character can meet the other selves. “Recursion” loops the live of the main character to his younger self. Both were a good read.

“Good Omens” by Terry Pratchett and Neil Gaiman was a must after watching TV series.

“Senni zwycięzcy” by Marek Oramus about multi-generation spaceship flying towards the Earth. Society there is in terrible state and there are mysterious people with paranormal abilities trying to change things. And it turns out to be transmitted as some sick reality TV. Good book from 1970s.

And “Triplet” by Timothy Zahn. Fantasy book in space.

Literary Role-Playing Game (LitRPG)

Some time ago, someone suggested me to check books by Василий Маханенко (Vasily Mahanenko in one transcription, Wasilij Machanienko in the other). His “Way of Shaman” series was an interesting one. Kind of reading how someone plays the game instead of watching it on Twitch or Youtube.

History

Between science fiction books I smuggled some history ones. Mostly around the Second World War.

There was “Wojna oczami wroga, sojusznicy Hitlera” by Grzegorz Bobrek. A book showing WW2 from a view of German allies: Italy, Hungary, Romania or Japan. And Germany itself. Was boring at some points but if someone wants to see the other view, I recommend this book.

Friedrich Sander’s book titled “Blood, Dust and Snow: Diaries of a Panzer Commander in Germany and on the Eastern Front, 1938-1943” was another one showing WW2 from the German side.

The “Operation Paperclip” by Annie Jacobsen is about secret US project of gathering as much of German research and scientists as possible during the end of WW2. If you were deemed valuable enough, you were moved to the USA with a new identity as long as you were ready to work for “your new country”.

The “Ludzie na mydło” (“Humans for soap”) by Tomasz Bonek is about German anatomists turning human corpses into school material. And that soap made from human fat was more of a side effect of that work rather than primary purpose.

There was also something not about WW2: “The Hot Zone” by Richard Preston. Worth reading book about the Ebola virus.

The end of the world

There were some books which can be described as “the end of the world we know”.

“The End of Men” by Christina Sweeney-Baird shows the world where 90% of men died due to unknown disease. When vaccination arrives, international travel is allowed only between countries with 99.9% of population being vaccinated. And that book was written before COVID-19 pandemic. Very interesting position to read.

The “Blackout: Tomorrow Will Be Too Late” by Mark Elsberg was another book in this category. Imagine Europe without electricity. Which means no water, no fuel, no food, no hospitals, no communication etc.. All because of a cyberattack.

Biographies

I read some biographies during 2025.

There was “The Outsider: My Life in Intrigue” by Frederick Forsyth. From the youngest pilot in RAF, to journalist, almost a spy and the author. Quick read, despite 368 pages.

And then were books about Jan Himilsbach (“Ja to chętnie napiłbym się kawy”) and Zdzisław Maklakiewicz (“Zaczęło się od tego, że jestem brzydki…”). Both by Ryszard Abraham. Add “Rejs na krzywy ryj” by Anna Poppek and you have three interesting books about famous Polish duo and the film which started their common career. I was also reading stories written by Jan Himilsbach but did not finished it in 2025 so it was not counted.

The book by Chrysta Bilton “A Normal Family: The Surprising Truth About My Crazy Childhood (And How I Discovered 35 New Siblings)” was a fun read. Author described her crazy childhood and later finding out that author’s father was a sperm donor. Which ended with her “expanded family” of 35 brothers and sisters…

Another book from this category was “American Sniper” by Chris Kyle, Scott McEwen and Jim DeFelice.

Journalism

A few books here. Starting with “ZATO” by Alice Lugen — a book about closed cities in Soviet Union (and later Russia). Very good read, describing how Soviet maps were falsified to hide those cities even from neighbours, how life there was different etc.

“Głusza” by Anna Goc described world of deaf people. Their language, culture and problems. How world of “those who hear” tries to force them “to fit”. Highly recommend.

Edyta Żemła in “Armia w ruinie” described how Polish Armed Forces changed during last years. To worse.

“Miła robótka” by Ewa Stusińska describes how everything around sex and porn arrived in Poland during 1990s. From VHS films to sex toys. How people started explore new areas of sexual freedom.

“Breasts” by Corien van Zweden is a wonderful book about breasts. Their role, how they change during life and what breast cancer can mean. Highly recommend. Even if you lack them yourself.

And the last entry: “Pogo” by Jakub Sieczko describes life of an ambulance workers.

Summary

It might look that I had a lot of free time in 2025, because reading all those books takes time.

I mostly read in the evening. Lying in bed, with my Onyx Nova2 e-book reader. Sometimes during day (there was lot of reading during time when I had a problem with my arm).

In those one hundred books, I read a few of them in English. Rest was in Polish (I had to look out for English titles for most of this post).

How many books I will read inn 2026? No idea. Probably fewer.

From the diary of AArch64 porter — RISC-V

2025-12-04T18:47:00+01:00

Wait, what? RISC-V? In ‘the diary of AArch64 porter’? WTH?

Yes, I started working on Fedora packaging for the 64-bit RISC-V architecture port.

All started with discussion about Mock

About a week ago, one of my work colleagues asked me about my old post about speeding up Mock. We had a discussion, I pointed him to the Mock documentation, and gave some hints.

It turned out that he was working on RISC-V related changes to Fedora packages. As I had some spare cycles, I decided to take a look. And I sank…

State of the RISC-V Fedora port

The 64-bit RISC-V port of Fedora Linux is going quite well. There are over 90% of Fedora packages already built for that architecture. And there are several packages with the riscv64 specific changes, such as:

patches adding RISC-V support
disabling some parts of test suites
disabling some build options due to bootstrapping of some languages being in progress (like Java)
disabling of debug information due to some toolchain issues (there is a work-in-progress now to solve them)

Note that these changes are temporary. There are people working on solving toolchain issues, languages are being bootstrapped (there was a review of Java changes earlier this week), patches are being integrated upstream and in Fedora, and so on.

There is the Fedora RISC-V tracker website showing the progress of the port:

package name
current status (new, triaged, patch posted, patch merged, done)
version in RISC-V port Koji
version in Fedora Koji (F43 release is tracked now)
version in CentOS Stream 10
notes

This is a simple way to check what to work on. And there are several packages, not built yet due to use of “ExclusiveArch” setting in them.

My work

The quick look at work needed reminded me of the 2012-2014 period, when I worked on the same stuff but for AArch64 ports (OpenEmbedded, Debian/Ubuntu, Fedora/RHEL). So I had a knowledge, I knew the tools and started working.

In the beginning, I went through entries in the tracker and tried to triage as many packages as possible, so it will be more visible which ones need work and which can be ignored (for now). The tracker went from seven to over eighty triaged packages in a few days.

Then I looked at changes done by current porters. Which usually meant David Abdurachmanov. I used his changes as a base for the changes needed for Fedora packaging, while trying to minimise the amount of them to the minimum required.

I did over twenty pull requests to Fedora packages during a week of work.

Hardware?

But which hardware did I use to run those hundreds of builds? Was it HiFive Premier P550? Or maybe Milk-V Titan or another RISC-V SBC?

Nope. I used my 80-core, Altra-based, AArch64 desktop to run all those builds. With the QEMU userspace helper.

You see, Mock allows to run builds for foreign architectures — all you need is the proper qemu-user-static-* package and you are ready to go:

$ fedpkg mockbuild -r fedora-43-riscv64

You can extract the “fedora-43-riscv64” Mock config from the mock-riscv64-configs.patch hosted on Fedora RISC-V port forge. I hope that these configuration files may be found in the “mock-core-configs” in Fedora soon.

At some point I had 337 qemu-user-static-riscv processes running at same time. And you know what? It was still faster than a native build on 64-bit RISC-V hardware.

But, to be honest, I only compared a few builds, so it may be better with other builders. Fedora RISC-V Koji uses wide list of SBCs to build on:

Banana Pi BPI-F3
Milk-V Jupiter
Milk-V Megrez
SiFive HiFive Premier P550
StarFive VisionFive 2

Also note that using QEMU is not a solution for building a distribution. I used it only to check if package builds, and then scrap the results.

Future

Will I continue working on the RISC-V port of Fedora Linux? Probably yes. And, at some point, I will move to integrating those changes into CentOS Stream 10.

For sure I do not want to invest in RISC-V hardware. Existing models are not worth the money (in my opinion), incoming ones are still old (RVA20/RVA22) and they are slow. Maybe in two, three years there will be something fast enough.

Wałek na Inpost

2025-11-12T19:47:00+01:00

Dawno nie pisałem tutaj po polsku ale dzisiaj “pani Antonina” próbowała kupić ode mnie telefon.

Wprowadzenie

Nabyłem w okazyjnej cenie telefon Xiaomi Redmi Note 14 Pro+ 5G. A że nie mam potrzeby go używać to postanowiłem go sprzedać.

Na początek wrzuciłem go na Facebook Marketplace. Bo wiecie: “za darmo”. No tak sobie tam leżał, co jakiś czas ktoś pytał czy aktualne lub zadawał więcej pytań.

Po czym dzisiaj pojawiła się “pani Antonina” (w cudzysłowie bo to przejęte konto raczej). Na początek zadała klasyczne pytania o aktualność oferty, stan telefonu itp…

A może być InPostem?

Czy jest możliwość wysyłki kurierem Inpost po wcześniej wpłacie na konto? Zamówię kuriera i pokryję koszty wysyłki.

Lub paczkomatom zapłacę +20.

Nie wiem jak Wy, ja lubię usługi InPostu. W promieniu 15 minut piechotą mam pewnie z 10 ich “automatów paczkowych”. Więc owszem, czemu by nie miało być.

Parę minut później dostałem info:

Gotowe. Zaplaciłam na InPost powinieneś otrzymać list na swój adres maila.

Sprawdź swoją skrzynkę mail proszę.

I okazała potwierdzenie przelewu:

potwierdzenie przelewu

I tu już zaczęło śmierdzieć…

Potwierdzenie przelewu

Uznałem, że nie wiem, może i potwierdzenie z banku Pekao SA tak powinno wyglądać. Popytałem znajomych, czy ktoś ma tam konto.

Dostałem informację, że zawsze jest data i godzina wystawienia dokumentu. Zawsze jest numer rachunku nadawcy, dane właściciela rachunku itp.

Na potwierdzeniu powyżej jest jeszcze kilka innych błędów ale co ja będę naprowadzać scammerów…

Mail

Skoro była prośba o sprawdzenie skrzynki to sprawdziłem. Nie było nic. No to zaglądam GMailowi do spamu, a tam owszem jest mail “od InPostu”.

O ile InPost używa adresów email w domenie tp5142.com :D

pierwszy spam: InPost Pay - podsumowanie

Link “Otwórz panel InPost Pay” to 320 znaków prowadzących do jeszcze innej domeny. Poza adresem był blok “onload=eval(decodeURIComponent(atob(ZNACZKI)))”. Po zdekodowaniu otrzymałem kolejny “eval(decodeURIComponent(atob(InneZnaczki)))” który dał mi url:

h00ps://confirm-orderNUMERKI.xyz/LosoweZnaczki=InneLosoweZnaczki

Tu już zacząłem szukać po sieci artykułów w temacie “wałek na InPost”…

Dziwne literki

Tymczasem “pani Antonina”:

To jest numer śledzenia przesyłki kսrіеrѕkіеј. Zaplaciłam na ǏnΡost. Proszę odebrać pieniądze na konto przez zamówienie.

Tam jest przycisk Dalej i wybierz bank i wprowadź dane, aby zweryfikować i otrzymać pieniądze. Po potwierdzeniu zaⅿóԝіеոіа kսrіеr zadzwoni się w celu dogadania kiedy przyjechać i pod jaki adres.

Nie wiem czy widzicie to co ja: “Ǐ” w “ǏnΡost” to nie jest nasze “I” tylko “duże łacińskie i z caronem”. Przyznaję, że nie wiem w jakim języku używa się tej litery.

Do tego “m” w “zaⅿóԝіеոіа” też nie jest naszym “m” tylko “Small Roman Numeral One Thousand” czyli “małe rzymskie oznaczenie liczby tysiąc”.

Oba znaczki złapałem bo mi edytor podświetlił słowa z nimi jako błędne.

Drugi mail

W międzyczasie dostałem jeszcze jednego maila — ten przeszedł filtry antyspamowe. Tym razem adres nadawcy był zbudowany z losowych literek w domenie zohomail.in.

Nic tylko czytać i klikać co nie?

drugi spam: Odbierz etykietę nadawczą

Tym razem link prowadzi prosto do h00ps://elektrizitaet-muenchen.com/LosoweLiterki który także kieruje do znanego już adresu:

h00ps://confirm-orderNUMERKI.xyz/LosoweZnaczki=InneLosoweZnaczki

Koniec zabawy

Na tym etapie uznałem, że postaram się być miły:

Przepraszam bardzo, ale na tym kończymy - nie mam zamiaru klikać podejrzanych linków w podejrzanych mailach.

Na co dostałem:

O czym ty mówisz? Moje pieniądze już są na stronie, zaufałam Ci. Potwierdź proszę zаⅿóԝіеոіе , mam nadzieję na Twoją uczciwość.

Pieniądze już zostały pobrane i nie da się cofnąć transakcji, bo to był pobraniowy przelew

Nieprzyjęcie pobrania to kradzież. InPost pracuje do 22:00 jeśli nie przyjmiesz, pieniądze po prostu przepadną i się spalą, i to będzie traktowane jako kradzież

Przyznaję, ciekawe podejście do sprawy. Później jeszcze była wiadomość głosowa męskim głosem strasząca policją itp.

Koniec

Zgłosiłem “panią Antoninę” i podzieliłem się historią ze znajomymi. Ktoś rzucił pomysłem posta na bloga. Więc macie historię.

From the diary of AArch64 porter — ID registers

2025-11-12T09:19:00+01:00

People are used to looking at “Features” field in the /proc/cpuinfo file under Linux. But does it show everything about the CPU cores present in the system?

What ID registers?

AArch64 CPUs have a set of “identification registers” which are named “ID_AA64*_EL1”, where “*” can be:

AFR — Auxiliary Feature Registers
DFR — Debug Feature Registers
FPFR — Floating-Point Feature Registers
ISAR — Instruction Set Attribute Registers
MMFR — Memory Model Feature Registers
PFR — Processor Feature Registers
SMFR — SME Feature ID Registers
ZFR — SVE Feature ID Registers

They can be used to check which features are present in a given CPU core. Their presence depends on things like age, generation, revision, and the design of the SoC.

Introductions of registers

As the AArch64 architecture was progressing, more and more identification registers were needed to describe CPU core features.

From a quick look through Arm docs, I compiled a simple table of chronology:

ID register	Architecture version	Year	First Arm core
ID_AA64DFR0_EL1	v8.0-A	2011/2012	Cortex-A53, Cortex-A57
ID_AA64PFR0_EL1	v8.0-A	2011/2012	Cortex-A53, Cortex-A57
ID_AA64ISAR0_EL1	v8.0-A	2011/2012	Cortex-A53, Cortex-A57
ID_AA64MMFR0_EL1	v8.0-A	2011/2012	Cortex-A53, Cortex-A57
ID_AA64AFR0_EL1	v8.0-A	2013/2014	Cortex-A53, Cortex-A73
ID_AA64AFR1_EL1	v8.0-A	2013/2014	Cortex-A53, Cortex-A73
ID_AA64DFR1_EL1	v8.0-A	2013/2014	Cortex-A53, Cortex-A73
ID_AA64PFR1_EL1	v8.0-A	2013/2014	Cortex-A53, Cortex-A73
ID_AA64ISAR1_EL1	v8.0-A	2013/2014	Cortex-A53, Cortex-A73
ID_AA64MMFR1_EL1	v8.0-A	2013/2014	Cortex-A53, Cortex-A73
ID_AA64MMFR2_EL1	v8.2-A	2016	Cortex-A55, Cortex-A75
ID_AA64ZFR0_EL1	v8.2-A (SVE)	2017	Fujitsu A64FX, Cortex-A710
ID_AA64MMFR3_EL1	v8.3-A	2017	Cortex-X4
ID_AA64ISAR2_EL1	v8.5-A	2018	Cortex-A520
ID_AA64ISAR3_EL1	v8.5-A	2018	Cortex-A520
ID_AA64MMFR4_EL1	v8.7-A	2021	Cortex-A715
ID_AA64SMFR0_EL1	v9.0-A (SME)	2021	Neoverse V1
ID_AA64FPFR0_EL1	v9.5-A	2023
ID_AA64PFR2_EL1	v8.9-A/9.5-A	2023	C1

I am not 100% sure about years and architecture versions. Not every document has all versions available on the Arm developer website.

It also shows that the Cortex-A53 was a very popular core design — it had multiple revisions, which added several features.

How to read those?

In my opinion, the easiest way is to use my ArmCpuInfo tool. It runs on any EFI environment (EDK2, U-Boot, and so on), reads the ID registers and prints their meaning. I wrote about it some time ago.

Empty registers

A TRM document may list an ID register, explain all its fields, and it still can look like something to ignore because it only contains zeros. Like the ID_AA64MMFR3_EL1 register in the Neoverse-V3 TRM:

SpecFPACC
ADERR
SDERR
RPZ
ANERR
SNERR
D128_2
D128
MEC
AIE
S2POE
S1POE
S2PIE
S1PIE
SCTLRX
TCRX

All those fields have descriptions and they mean something. At the same time, they all have a 0b0000 value. I assume that the value of some fields may change when the SoC vendor pays more and begins designing its own version of a CPU core based on Arm’s design.

Strange cases

Cortex-A75 present in the MediaTek Helio G70 SoC reports SSBS (Speculative Store Bypass Safe) feature under Linux:

processor       : 6
BogoMIPS        : 26.00
Features        : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp
                  asimdhp cpuid asimdrdm lrcpc dcpop asimddp asimddp sha512 ssbs
CPU implementer : 0x41
CPU architecture: 8
CPU variant     : 0x3
CPU part        : 0xd0a
CPU revision    : 1

But to read it, you need the ID_AA64PRF1_EL1 register, which is not mentioned in the Cortex-A75 technical reference manual (TRM). It is present in the newer versions of the Cortex-A55 TRM, and both CPU core models are present in the Helio G70 SoC.

SSBS (and SSBS2) were introduced into Arm v8.5 and then added to v8.0 to allow every CPU core to have it implemented.

Let me list it for you

As you may know, I have a page about ARM CPU cores where I list some basic information. Last weekend I added showing of potential CPU features to it. Small example:

CPU core name	features
Cortex-A53	AA32EL0, AA32EL1, AA32EL2, AA32EL3, AA64EL0, AA64EL1, AA64EL2, AA64EL3, AES, ASID16, AdvSIMD, CRC32, Debugv8, DoubleLock, FP, MixedEnd, MixedEndEL0, PMULL, PMUv3, SHA1, SHA256
Cortex-A520	AA64EL0, AA64EL1, AA64EL2, AA64EL3, AES, AFP, AMUv1, ASID16, AdvSIMD, BBM, BF16, BTI, CCIDX, CONSTPACFIELD, CRC32, CSV2_2, CSV3, DGH, DIT, DPB2, Debugv8p4, DotProd, E0PD, ECBHB, ECV_POFF, EVT, FCMA, FGT, FHM, FP, FP16, FRINTTS, FlagM2, HAFDBS, HCX, HPDS2, HPMN0, I8MM, IDST, IESB, JSCVT, LOR, LRCPC, LRCPC2, LSE, LSE2, MTE3, MixedEnd, MixedEndEL0, PACQARMA3, PAN3, PAuth2, PMULL, PMUv3p7, RASv1p1, RDM, S2FWB, SB, SHA1, SHA256, SHA3, SHA512, SM3, SM4, SPECRES, SSBS2, SVE, SVE2, SVE_AES, SVE_BitPerm, SVE_PMULL128, SVE_SHA3, SVE_SM4, TLBIOS, TLBIRANGE, TRBE, TRF, TTCNP, TTL, TTST, UAO, VHE, VMID16, XNX, XS, nTLBPA

CPU core name

features

Cortex-A53

AA32EL0, AA32EL1, AA32EL2, AA32EL3, AA64EL0, AA64EL1, AA64EL2, AA64EL3, AES, ASID16, AdvSIMD, CRC32, Debugv8, DoubleLock, FP, MixedEnd, MixedEndEL0, PMULL, PMUv3, SHA1, SHA256

Cortex-A520

AA64EL0, AA64EL1, AA64EL2, AA64EL3, AES, AFP, AMUv1, ASID16, AdvSIMD, BBM, BF16, BTI, CCIDX, CONSTPACFIELD, CRC32, CSV2_2, CSV3, DGH, DIT, DPB2, Debugv8p4, DotProd, E0PD, ECBHB, ECV_POFF, EVT, FCMA, FGT, FHM, FP, FP16, FRINTTS, FlagM2, HAFDBS, HCX, HPDS2, HPMN0, I8MM, IDST, IESB, JSCVT, LOR, LRCPC, LRCPC2, LSE, LSE2, MTE3, MixedEnd, MixedEndEL0, PACQARMA3, PAN3, PAuth2, PMULL, PMUv3p7, RASv1p1, RDM, S2FWB, SB, SHA1, SHA256, SHA3, SHA512, SM3, SM4, SPECRES, SSBS2, SVE, SVE2, SVE_AES, SVE_BitPerm, SVE_PMULL128, SVE_SHA3, SVE_SM4, TLBIOS, TLBIRANGE, TRBE, TRF, TTCNP, TTL, TTST, UAO, VHE, VMID16, XNX, XS, nTLBPA

There may be some mistakes in the table — I strongly advise checking Technical Reference Manuals (TRMs) to be sure. Please report any error — I will take a look at fixing them.

Finished Factorio: Space Age under 40 hours

2025-10-22T19:53:00+02:00

Factorio: Space Age added new achievements, so I no longer had 100% done. So, some time ago, I started “finish SA under 40 hours” challenge to get back to fully finished game state.

Gathering of hints

Before starting, I decided to check how people approached this achievement. One of solutions was the ‘Express Delivery: a brief guide for the best achievement in the game. Ask me anything!’ post by “Intrepid_Teacher1597” on Reddit. With clean split to parts:

Nauvis
Vulkanus
Fulgora
Gleba
Nauvis (to redesign using technologies from other planets)
Aquillo
Solar’s Edge

I went through my old blueprints, refreshed my ‘Microfactories for Space Age’ set from some old savegame and started playing.

I opted for rich resource settings and made islands on Fulgora large enough to not have issues with space. Later, it turned out that I did not looked closely at how Aquillo would look…

Nauvis

I do not like the first hours in Factorio. No bots means everything needs to be built by hand. The awful part. So, I used ‘Brian’s bootstrap‘ by Brian White, as in some of my previous games, to make it as compact and quick as possible.

Once I had bots I designed Nauvis base using blueprints from my previous game. Which turned out to be a bad idea as it quickly showed that there would be serious lockdowns later.

So I moved back a bit and redesigned using Nilaus cityblocks 2.0 blueprints. Quick, simple and organised. Probably should have started with them.

Space platform and ships

To get to space you need space science. A simple ‘75 SPM space platform‘ by Brandon Lam was enough for a start. I did some edits to it later as some inserters required adding conditions to keep the platform operational.

For inner planets transport I wanted something small. The ‘Early Game Ship‘ by Ian Coleman was enough for most of the time. At some point, I enlarged storage space a bit and built a second one. One was used for transporting science packs and the other for deliveries.

Vulkanus

Landed, built a small base and went hunting.

Small demolishers are easy to kill when you have 50 gun turrets and a few thousand red ammo. Set a 5x10 block of turrets on your territory next to the border, fill them with ammo, use some decoys to make the demolisher angry and walk away. At some point, you get notification and a new territory. Repeat a few times and there will be more than needed space for expansion.

Got tungsten ore, setup a bus, a set of my microfactories making things, 300+ megawatts of power from sulfuric acid and was ready to go to the next planet.

Lava is a beautiful resource — infinite amounts of molten iron/copper make things so much easier.

Fulgora

The recycling planet. The usual process: land, walk around, find a large island, put few hundred accumulators for power and start building.

Again I used my microfactories set and something like six thousand accumulators for power.

Several recycler blocks to get basic components (like plates) and Fulgora is a place where you can build so many things…

Fulgora and Vulkanus were my main sources for several components for the other planets.

Gleba

I am not a fan of Gleba. It is too biological for me. Spoilage everywhere, nutrients everywhere…

In the beginning, I planned to use my microfactories. But kick-starting it took a bit too much time so I went back and used the Gleba starter factory instead. One complex block, built by bots, delivers everything I needed. This blueprint is expected to be replaced by the main base but it was enough for my challenge.

Nauvis again

While bots were building factory on Gleba I started redesigning base on Nauvis. Drilling machines from Vulkanus instead of electric miners gave me much more resources. And they stack items on belts once you research Gleba technologies.

Melting iron/copper ore solved another problem as liquids transfer faster than belts. Furthermore foundries from Vulkanus allow to produce several things without any intermediate steps (direct steel, pipes, wheels or copper wire).

Add EM plants from Fulgora and you get electronic chips (green, red, blue ones) in much bigger amounts than before. For example: my cityblock was making two red belts of electronic chips (that’s 60/s). After the redesign, it was 280/s on two green belts (required stack inserters to pass 75/s limit of one green belt).

Modules, LDS, and so on are also much faster. The old hub/mall “making everything”, can get upgrades, such foundries making wheels and pipes directly from molten iron instead of using iron plates.

Long distance space ship

At that stage I also finished building space ship for next stage. I used ‘Easy normal quality Edge ship‘ by Wobbleland as a base for it.

After some trial flights, I edited it to have a bit more cargo space. I cut ship in half, added some extra storage, and it became my only long distance ship.

Aquillo

The frozen hell. Planet where all you have is an ammoniacal ocean with some small islands here and there. Things freeze if you do not heat them, bots discharge five times quicker than usual etc.

This is a place where you need to be properly prepared. Mech armor is mandatory, along with 4 portable fission reactors and MK2 or MK3 batteries with MK2 roboports. Anything below that, and your bots are useless and for most of the time you run without any power in the armour.

Careful design is a must. I landed, tried to set up base and started adding what I had forgotten to take with me into my notes. Restarted and landed again. And again. And…

Then I took some time and designed whole base with the main bus idea. To not have to rely on bots for the most of the base.

First, I built some small starter to get water from ice (from ammoniacal solution) so I could have power. And two nuclear reactors to provide heat among heating towers powered by rocket fuel (which I took with me from Fulgora).

Then, I built the main bus piece by piece up to cryogenic science packs and the space port. It took some time to squeeze everything close to each other. Then cut it into pieces and restarted game from landing point. I have to admit — it looks nice at night:

Aquillo at night

Once production of science packs started I delivered them to Nauvis and started researching the final technologies:

quantum computing
fusion power
promethium science
railgun

Brought all components required for quantum processors and built enough of them to make two railguns for my space ship.

Solar’s Edge

With about two hours left before the 40 hours limit my ship was ready to fly to Solar’s Edge (which is the requirement to finish the game). Loaded with yellow magazines, yellow rockets and railgun ammo it went from Vulkanus to Aquillo, mounted the missing railguns and went away, to Solar’s Edge.

It was a one-way trip as all I needed was to get there, without having to go back. The railgun ammo ended just before the end, there were fewer than a hundred rockets left as well.

But it was enough to finish the game. Now I have 100% of achievements again:

100% of achievements done

That “finish under 40 hours” game started three months ago and took over 4.6 GB of storage for save files.

What’s next?

I should put Factorio away for a year or so. Because for me, Factorio is a drug.

Otherwise, I will start adding mods and try to get this base expanded, redone “in a proper way” and so on.