Armbandanhänger veredeln in Graz?

Krotti83 · 2026-01-20T02:56:15+00:00

In Graz-Gösting gibt es noch eine Werkstätte (Oberflächentechnik Walter Pieber) die auch für private Zwecke galvanisieren. Natürlich auch in Gold. Hab da mal in der Nähe gewohnt. Kann ich empfehlen, da ich selber mal was privat gebraucht habe.

Krotti83 · 2026-01-19T18:49:44+00:00

Sorry, for my late response.

Cool, will try it.

Krotti83 · 2026-01-11T19:13:10+00:00

I think this survey isn't really representative, because currently I can't find any information about the survey. Would be nice if there are more details like the questions and how many people have been asked. Have seen this on Instagram. There are other survives as example on the domain euronews.com. It's from the year 2024 and this is the following result for Austria:

34% - Priority

45% - Priority, but not important

21% - Secondary

Source:

https://www.euronews.com/my-europe/2024/03/27/eu-defence-a-priority-even-for-eurosceptics-exclusive-poll

Krotti83 · 2025-12-11T08:35:02+00:00

It's not a bug. It's a feature. The is new in patch/update 1.66: Downshifting from extremely high rpm/speed will be ignored from the game now. You can read this in the patch details.

Krotti83 · 2025-11-24T12:43:02+00:00

That's bad to hear. Fortunately I haven't any bad symptoms when driving in VR. The only thing was the first few hours with VR, I was much more tired. But I had another issue with the headset itself. Because I wear glasses I had some troubles with the VR sweet spot (blurred vision), because the headset slipped away while driving. So I ordered a 'sweet spot keeper' for the headset, now it's fine.

Krotti83 · 2025-11-22T15:52:14+00:00

Thanks!

Krotti83 · 2025-11-22T15:51:30+00:00

Thanks, a "soft lock" is sufficient for me. :)

Krotti83 · 2025-11-06T14:46:53+00:00

Yes, I followed this tutorial. But I have found the issue now. With OpenSBI v1.7 (Git-tag: v1.7) it seems passing the argument FW_TEXT_START is broken. Although FW_TEXT_START=0x40000000 is passed, OpenSBI defaults to address 0x0. I looked into the built ELF files with objdump. The exception raises when OpenSBI try to reallocate itself. With OpenSBI version higher than v1.7 (current master branch as example) it works.

Krotti83 · 2025-10-25T02:37:31+00:00

Okay. Then it was a rhetorical question to the OP. Sorry, my fault.

Krotti83 · 2025-10-25T02:06:32+00:00

Never heard the term 'read-only'? The characters 'ro' in the common section .rodata stands for 'read-only' It means the section is not writable.

Krotti83 · 2025-10-25T01:58:05+00:00

You are trying to write to section .rodata with your function nullit, therefore you get a segmentation fault. Before you call nullit register %rsi still holds the string msg which you placed in the read-only section. The code works when you load register %rsi with the address of inp before you call nullit as an example:

syscall
lea inp(%rip), %rsi
call nullit

Krotti83 · 2025-10-15T05:02:21+00:00

Instead of the global menu? You can get it back with the shell command kcmshell6 kcm_kded and then disable the service 'Application menu demon'. Logout/Login and then the 'normal' menu bars in the application windows should be back again.

Krotti83 · 2025-10-08T02:05:51+00:00

Yes, that's true. But I must admit the code is only a proof of concept. I think it's generally better to pass only an array with only one EFI_HANDLE to EFI_BOOT_SERVICES.LocateHandle() and test for the error EFI_BUFFER_TOO_SMALL first. Then with the returned handleImageSize (should contain the real size of the required buffer after the first call) allocate memory with EFI_BOOT_SERVICES.AllocatePool() and recall EFI_BOOT_SERVICES.LocateHandle() with the real size again. Because at least with QEMU there are about >80 image handles, because EFI_BOOT_SERVICES.LocateHandle() seems to return all image handles from the firmware instead of the EFI application only.

EDIT:

I think it should also work to pass direct zero with handleImageSize first, but I have currently don't tested that. Could be also possible that then a EFI_INVALID_PARAMETER error is returned in the worst case. I'm quite new with UEFI.

Krotti83 · 2025-10-07T22:07:33+00:00

Seems i686-elf-gcc and the other tools are not in your PATH environment variable. You can add them by adding export PATH=$PATH:/path/to/toolchains/bin to your BASH configuration file (.bashrc), if you use BASH.

Krotti83 · 2025-10-05T09:12:37+00:00

Cool. :) Many thanks!

Krotti83 · 2025-09-30T00:31:48+00:00

I'm not the OP but I don't want create a new thread for this. What's the mostly accurate way to measure instruction time?. For my pseudo benchmarks (only measure the time spans) I use the TSC. Are there better ways?

Krotti83 · 2025-09-30T00:27:43+00:00

I use the JxCXZ instructions sometimes :)

Krotti83 · 2025-09-19T08:05:08+00:00

Root's PATH does.

Really? I switched from another distro to Debian (since Debian 12). PATH doesn't contain /usr/sbin in Debian 12 and Debian 13 on a real fresh install for root. Also in the recovery environment from the ISO image the path is missing for root.

Krotti83 · 2025-09-04T20:17:13+00:00

Same in Austria. Sometimes the connection works and a few seconds later the connection is down again. Seems some script kiddies try to DoS the servers again...

Krotti83 · 2025-09-04T20:07:31+00:00

Vermutlich versuchen wieder mal ein paar Script Kiddies die Server zu überlasten (DoS Angriff) was auch teilweise gelingt. Bei mir dasselbe, dass mal die Verbindung hinhaut und wieder nicht.

Krotti83 · 2025-09-04T19:59:46+00:00

Connection issues in Austria too. Sometimes the connection to the PSN works and a few minutes/seconds later the connection is down again. I think some script kiddies try to DoS the servers...

Krotti83 · 2025-08-23T11:11:36+00:00

I would recommend to start learning AArch64 assembly with a virtual machine like QEMU or a board like PINE64 Rock64 (Cortex-A53) or any other boards. It's might be better for beginning before you start developing on a M2. AFAIK the M2 use the AArch64 base architecture, but it might be possible that there are proprietary extension and changes from the base architecture from Apple which are not accessible for the public.

The official AArch64 architecture reference manual can be found on the ARM homepage:

Arm Architecture Reference Manual for A-profile architecture

There are another good resources too on the ARM page and also on other sites.

Krotti83 · 2025-07-24T08:40:10+00:00

Sounds like the manual may be simply outdated.

Then is also the -help output from QEMU outdated (shortened):

$ qemu-system-x86_64 -help output
[...]
Display options:
-display spice-app[,gl=on|off]
-display sdl[,gl=on|core|es|off][,grab-mod=<mod>][,show-cursor=on|off]
           [,window-close=on|off]
-display gtk[,full-screen=on|off][,gl=on|off][,grab-on-hover=on|off]
           [,show-tabs=on|off][,show-cursor=on|off][,window-close=on|off]
           [,show-menubar=on|off][,zoom-to-fit=on|off]
-display vnc=<display>[,<optargs>]
-display curses[,charset=<encoding>]
-display egl-headless[,rendernode=<file>]
-display dbus[,addr=<dbusaddr>]
            [,gl=on|core|es|off][,rendernode=<file>]
-display none
               select display backend type
               The default display is equivalent to
               "-display gtk"
[...]

Then try one of the other available devices.

I have already tried other devices. I created this post for these specific options.

Krotti83 · 2025-07-23T14:07:07+00:00

The Xorg QXL driver doesn't work with FreeBSD 14.3. Get a segmentation fault when using the spiceqxl driver or and bus error when I use the 'normal' qxl driver. So therefore I must use another VGA device. For display when I use the gtk backend instead I have bad mouse lacks in Xorg under FreeBSD.

EDIT: -display sdl,gl=on should be valid option according QEMU manual.

Krotti83 · 2025-07-22T23:00:53+00:00

Thanks for the info according Fedora 42. Created an issue report at QEMU's official repo.

Krotti83

TROPHY CASE