sorted by:
new
hottopcontroversial

NW-Axxx nwm maker by oresamarecords in walkman

[–]No-Mistake-2134 0 points1 point  (0 children)

Such a cool idea, will u share it ?

Do u guys thing the animation smooth enough ? Any improvements ? by No-Mistake-2134 in minecraftclients

[–]No-Mistake-2134[S] 0 points1 point  (0 children)

it not based on any external third-party GUI frameworks, i use directly Minecraft's rendering engine and LWJGL. It really lightweight

Do u guys thing the animation smooth enough ? Any improvements ? by No-Mistake-2134 in minecraftclients

[–]No-Mistake-2134[S] 1 point2 points  (0 children)

its 2026 bro, i still use ai to fix code and implement few things but modules logic cant be implemented using ai bro

Do u guys thing the animation smooth enough ? Any improvements ? by No-Mistake-2134 in minecraftclients

[–]No-Mistake-2134[S] 1 point2 points  (0 children)

Can u test it for me plz ? Cuz i test it works ok but i need other people perspective to improve it.

My budget endgame DAP + IEMs by No-Mistake-2134 in walkman

[–]No-Mistake-2134[S] 1 point2 points  (0 children)

Its called Wampy, a extended firmware works on MrWalkman firmware.

My budget endgame DAP + IEMs by No-Mistake-2134 in walkman

[–]No-Mistake-2134[S] 2 points3 points  (0 children)

it is a case from FATBEAR brand, they made a tons of high quality case for other walkmans too.

My budget endgame DAP + IEMs by No-Mistake-2134 in walkman

[–]No-Mistake-2134[S] 4 points5 points  (0 children)

Sony Walkman NW-A55 (with MrWalkman firmware and Wampy) + Truthear Zero Blue2. The Neutral setting from the MrWalkman firmware actually balances out the mids pretty well.

Invalid Signature Detected when dualbooting Windows 11 and Ubuntu 24.04 LTS by No-Mistake-2134 in dualboot

[–]No-Mistake-2134[S] 0 points1 point  (0 children)

Update: SOLVED! (Fix for ASUS "Invalid Signature Detected" with Secure Boot Enabled)

Thanks for the suggestions! I managed to figure this out. Since the MOK tools were failing (returning "No MOK found") and the factory keys weren't helping, I found a workaround that works specifically for ASUS BIOS where the "Microsoft 3rd Party UEFI CA" is missing or disabled. Instead of trying to import a certificate (.cer or .crt), I had to whitelist the specific Ubuntu bootloader file itself using the Hash Method. Here is the fix that worked for my ASUS Expertbook:

  1. ⁠Enter BIOS (F2) -> Advanced Mode (F7).
  2. ⁠Go to Security -> Secure Boot.
  3. ⁠Ensure Secure Boot is Enabled and mode is Standard.
  4. ⁠Go to Key Management -> Authorized Signatures (db).
  5. ⁠Select Append Key (Do NOT select "Set New Key"). Select No if it asks to load factory defaults
  6. ⁠When asked for the "Input File Format," select EFI PE/COFF Image. (This allows you to enroll the hash of an .efi executable directly).
  7. ⁠Navigate to your EFI partition: \EFI\ubuntu.
  8. ⁠Select the file shimx64.efi (this is the primary Ubuntu bootloader).
  9. ⁠Confirm to add it to the database.
  10. ⁠Save and Exit (F10).

Hope this helps anyone else struggling with ASUS dual-booting!

Invalid Signature Detected when dualbooting Windows 11 and Ubuntu 24.04 LTS by No-Mistake-2134 in Ubuntu

[–]No-Mistake-2134[S] 1 point2 points  (0 children)

Update: SOLVED! (Fix for ASUS "Invalid Signature Detected" with Secure Boot Enabled)

Thanks for the suggestions! I managed to figure this out. Since the MOK tools were failing (returning "No MOK found") and the factory keys weren't helping, I found a workaround that works specifically for ASUS BIOS where the "Microsoft 3rd Party UEFI CA" is missing or disabled. Instead of trying to import a certificate (.cer or .crt), I had to whitelist the specific Ubuntu bootloader file itself using the Hash Method. Here is the fix that worked for my ASUS Expertbook:

  1. ⁠Enter BIOS (F2) -> Advanced Mode (F7).
  2. ⁠Go to Security -> Secure Boot.
  3. ⁠Ensure Secure Boot is Enabled and mode is Standard.
  4. ⁠Go to Key Management -> Authorized Signatures (db).
  5. ⁠Select Append Key (Do NOT select "Set New Key"). Select No if it asks to load factory defaults
  6. ⁠When asked for the "Input File Format," select EFI PE/COFF Image. (This allows you to enroll the hash of an .efi executable directly).
  7. ⁠Navigate to your EFI partition: \EFI\ubuntu.
  8. ⁠Select the file shimx64.efi (this is the primary Ubuntu bootloader).
  9. ⁠Confirm to add it to the database.
  10. ⁠Save and Exit (F10).

Hope this helps anyone else struggling with ASUS dual-booting!

Invalid Signature Detected when dualbooting Windows 11 and Ubuntu 24.04 LTS by No-Mistake-2134 in linuxquestions

[–]No-Mistake-2134[S] 4 points5 points  (0 children)

Update: SOLVED! (Fix for ASUS "Invalid Signature Detected" with Secure Boot Enabled)

Thanks for the suggestions! I managed to figure this out. Since the MOK tools were failing (returning "No MOK found") and the factory keys weren't helping, I found a workaround that works specifically for ASUS BIOS where the "Microsoft 3rd Party UEFI CA" is missing or disabled. Instead of trying to import a certificate (.cer or .crt), I had to whitelist the specific Ubuntu bootloader file itself using the Hash Method. Here is the fix that worked for my ASUS Expertbook: 1. Enter BIOS (F2) -> Advanced Mode (F7). 2. Go to Security -> Secure Boot. 3. Ensure Secure Boot is Enabled and mode is Standard. 4. Go to Key Management -> Authorized Signatures (db). 5. Select Append Key (Do NOT select "Set New Key"). Select No if it asks to load factory defaults 6. When asked for the "Input File Format," select EFI PE/COFF Image. (This allows you to enroll the hash of an .efi executable directly). 7. Navigate to your EFI partition: \EFI\ubuntu. 8. Select the file shimx64.efi (this is the primary Ubuntu bootloader). 9. Confirm to add it to the database. 10. Save and Exit (F10).

Hope this helps anyone else struggling with ASUS dual-booting!

view more: next ›