2021年5月7日 星期五

RU5.28.0397 BETA

Updated: 0396 build was removed and here is the new update 0397 build, thanks to @martin reporting the problem.

This version fixed mainly SIO and keyboard not working properly.  But I just did some very limited tests and some are not even tested.  Please note that It's not guaranteed that it works as expected.

Fix

  • Fix RU can't remember SIO LDN
  • Possibly fix the problem of reading keyboard input
  • Fix the problem of showing many non-existed SIOs
  • Possibly fix RU /L for SMBUS not working

RU /Sxx (Safe mode)

        xx stands for bits, for examples: RU /S4 means to skip SIO detection
  • BIT0=1: Read MTRR only for ALT-8 CPU
  • BIT1=1: Display readings from keyboard
  • BIT2=1: Skip detecting SIO
  • BIT3=1: Skip initializing text mode

Files

於

59 則留言:

  1. gary2021年5月11日 上午9:56

    Hi James,
    The given password can't extract the zip file.

    回覆刪除
  2. James Wang2021年5月11日 上午11:07

    Hi Gary,

    Somehow I put the wrong link, I've corrected. Thanks!

    回覆刪除
  3. martin2021年5月13日 晚上7:50

    Hi James,
    just tried this version but doesn´t work for me: almost all rows are blank, some words are in english, others looks like chinese (not sure if it´s chinese). Basically there´s no way to find any string or word.
    The good news are: keyboard is working (in previous version I had to use an external USB keyboard) and the windows is almost full screen (previous version was a litle windows, less than a quart of the screen). Thanks

    回覆刪除
  4. James Wang2021年5月13日 晚上11:12

    Hi Martin,

    OK I will check, I have updated EDK II packages. Maybe it was the cause.

    回覆刪除
  5. Andeddokira2021年5月15日 下午3:49

    Hello James, I have a Lenovo ideapad 720-15ikb (81c7) with a phoenix securecore v2.5 bios, when running any version of the ru.efi I only see 2 entries in uefi variables, that sometimes do and don't have names, when the names appear they both reference the splash screen, any idea on how to utilize your for my device and bios? Thanks

    回覆刪除
  6. Andeddokira2021年5月15日 下午4:48

    Hi James,

    Sorry after sending the last message I realized maybe i was meant to launch ru.efi named as bootx64.efi rather than launching it using opencore shell.

    Your amazing tool worked like a charm when i launched it first, thank you for all your work

    回覆刪除
  7. James Wang2021年5月15日 晚上11:40

    Hi Daniel,

    That's OK, glad it helped you!

    回覆刪除
  8. James Wang2021年5月15日 晚上11:42

    Hi Martin,

    I hope this version fix the problem you've reported.

    回覆刪除
  9. Martin2021年5月17日 晚上7:58

    Hi James,
    characters problem and blank rows problem are solved in this version.
    Screen size is OK too but now keyboard is not working like in previous version in my Matebook 14 2020 (i5 10210u). I guess using an external USB keyboard would be the solution but I couldn´t try it yet.
    Thanks for your work

    回覆刪除
  10. James Wang2021年5月17日 晚上10:02

    Hi Martin,

    Let me check if I broke anything again.

    回覆刪除
  11. digitalboy2021年5月25日 凌晨3:49

    Hi James, thank you as always for your work
    I'd like to report that since 5.26.0386 RU.EFI doesn't work for my ThinkPad P15 (Intel W-10885M | Intel WM490) black screen upon launch, Caps Lock and Numlock keys do not lit up if pressed

    5.25.0379 seems to work fine

    I'm willing to be a tester if necessary

    Thank you

    db

    回覆刪除
  12. James Wang2021年5月25日 上午10:49

    Hi digitalboy,

    Thanks for the testing and it's good news that 5.25.0379 works OK!

    回覆刪除
  13. goodwon2021年5月26日 晚上10:08

    Thanks for the update, but built-in keyboard still not working

    回覆刪除
  14. James Wang2021年5月27日 下午5:01

    goodwon,

    But do you find your keyboard work on any RU version? If so can you please tell me which version it is? Thanks.

    回覆刪除
  15. luchaloupka2021年5月29日 清晨5:40

    PS/2 keyboards have been broken on RU.efi since the May 2020 version (5.25.0379). USB keyboards work, but PS/2 keyboards like what are found in most laptops, do not. Thanks!

    回覆刪除
  16. Unknown2021年6月7日 凌晨12:34

    Thank you very much for this great tool.
    I just wonder if the modification of UEFI is not good, will it damage the bios or brick the motherboard? Are there any methods to recover the original value?

    回覆刪除
  17. James Wang2021年6月7日 中午12:00

    Hi luchaloupka,

    I will check if I need to revert something, thanks for the information.


    Hi Unknown,

    It's possible to damage the system. Recent systems are all well protected for flash write so using RU should not damage your BIOS.

    Unless you are using RU to write the disk directly with random data then your OS may not boot or data can be lost.

    As long as BIOS is not damaged I think you can always restore the default values.

    回覆刪除
  18. luchaloupka2021年6月11日 晚上9:49

    Thank you, Mr. Wang! Greatly appreciate all your work on this tool! :)

    回覆刪除
  19. Karl2021年6月18日 上午11:19

    Hello James, thank you for your work. Greatly appreciated. I tried the version ru5.28 after reading the changelog on improved keyboard input and although for some folks the keyboard work as I read above in the comments for me using a Dell G5 the onboard keyboard did not work. Everything else works as expected.

    Just wanted to let you know.

    Thanks,
    Karl

    回覆刪除
  20. James Wang2021年6月18日 上午11:22

    Hi Karl,

    Thanks! But do you know which version of RU works for your onboard keyboard?

    回覆刪除
  21. Karl2021年6月21日 凌晨1:50

    I only tried the ru 5.28. Do earlier versions support onboard keyboards? From which version does the onboard keyboard support start? I can try from thereon.

    回覆刪除
  22. luchaloupka2021年6月21日 清晨5:00

    Karl, please see my comment above regarding PS/2 keyboards. This is why laptop keyboards are not working on RU since the built-in keyboards use PS/2. Try version 5.25.0379. That version has working PS/2 keyboard support. Thank you!

    回覆刪除
  23. Karl2021年6月23日 晚上11:15

    Luchaloupka, I had seen your comment but somehow missed the version you had mentioned earlier. Thank you for posting this again. I will definitely try version 5.25.0379 and get back to you.

    - Karl

    回覆刪除
  24. Karl2021年6月24日 凌晨1:53

    Luchaloupka, many thanks I have tested version 5.25.0379, and the internal laptop keyboard works!

    James, it would be great if you could include this support for PS/2 keyboards from version 5.25.0379 in your future builds. Much appreciated. Thanks for all the support to the community.

    -Karl

    回覆刪除
  25. 匿名2021年7月4日 下午2:25

    請問在UEFI SHELL環境下執行RU.efi,但執行後發生螢幕全黑的畫面狀況.
    不知道可能哪裡設定錯誤了呢?謝謝
    感謝回答.

    回覆刪除
  26. James Wang2021年7月4日 晚上7:59

    Hi Anonymous,

    Can you please try "RU /S" or "RU /S8" to see if the screen is still black?

    回覆刪除
  27. 匿名2021年7月6日 下午6:03

    非常謝謝~

    請問主程式下 /S 與 /S8是甚麼涵義呢? 謝謝~

    回覆刪除
  28. James Wang2021年7月19日 晚上8:56

    If you type "ru /?" (help) it will show you:

    /Sxx - Safe mode, xx is in hex format. Each bit of xx representing an option:
    BIT0=1: Read MTRR only for ALT-8 CPU
    BIT1=1: Display readings from keyboard
    BIT2=1: Skip detecting SIO
    BIT3=1: Skip initializing text mode

    回覆刪除
  29. James Wang2021年7月19日 晚上10:33

    @karl, @luchaloupka and @digitalboy,

    Can you please try this test version of ru?
    https://github.com/JamesAmiTw/ru-uefi/files/6841733/RU.zip

    回覆刪除
  30. Unknown2021年7月24日 凌晨2:39

    在lenovo t460s笔记本上，不能uefi变量不能保存。ctrl-w时提示0x00000008错误。请问怎么处理？

    回覆刪除
  31. James Wang2021年7月24日 下午4:07

    0x00000008 means write-protected, I don't think you can write that variable.

    回覆刪除
  32. luchaloupka2021年7月26日 凌晨12:48

    Hello Mr. Wang,
    The new version you posted still doesn’t work on PS/2 keyboards. Reverted back to 5.25.0379 as that is the last one that works correctly. Thanks!

    回覆刪除
  33. James Wang2021年7月28日 下午2:31

    Hi luchaloupka,

    It's difficult to find out which modification caused the problem because I can't reproduce but I will check again.

    回覆刪除
  34. 匿名2021年8月14日 下午4:01

    I am running a 2021 X1 Extreme Gen 4. I have tried both files in the comments and latest release on your page.

    I have a black screen. With your files in the thread, I get black screen with a tiny white rectangle. It looks like a vintage cursor but does not blink or move. I have to force reset my computer to restart or shutdown. No key press responds either.

    回覆刪除
  35. James Wang2021年8月14日 下午4:12

    Can you please first try safe mode by "ru /s"?

    回覆刪除
  36. Alderon2021年8月20日 清晨6:30

    James 請問最新版本可以支援asus g15 advantage ed 筆電(或著所有筆電)的內建鍵盤嗎?如果不行是否可以以接外接鍵盤操作? 多謝!

    回覆刪除
  37. Chen2021年8月20日 上午10:25

    Hi James,

    我用Eagle Stream Sapphire Rapids ES1 C-2 Stepping的CPU
    進RU會直接hang, 最後一行log是Uknown.Entry
    不知道有沒有其他人回報過這個問題
    有空可以幫忙看一下嗎? 感謝!

    回覆刪除
  38. James Wang2021年8月20日 上午10:26

    Chen,

    Can you first try "RU /S"?

    回覆刪除
  39. Chen2021年8月20日 上午11:01

    Hi James,

    改下"RU /S"就不會hang了
    另外
    "/S1" (success)
    "/S2" (hang)
    "/S4" (hang)
    "/S8" (hang)
    這樣看起來, 是不是在讀MTRR的時候出現的問題?


    回覆刪除
  40. 匿名2021年8月22日 晚上11:58

    Hi James,
    lenovo legion 7i 2021 after pressing alt + (+=） the interface will hang, how to solve it? Thanks.

    回覆刪除
  41. 匿名2021年8月24日 晚上11:21

    Hi james,
    7i can access uefi variable(CpuSetup) now but ctrl + pgdn "not working"
    Does it mean there is 1 page only?

    回覆刪除
  42. James Wang2021年8月25日 上午9:54

    You should try PgDn without CTRL.

    回覆刪除
  43. James Wang2021年8月25日 上午9:55

    @Chen
    Thank you for the information, yes it is the problem of reading CPU MSRs.

    回覆刪除
  44. 匿名2021年11月11日 下午2:19

    Hi James.
    I got a issue about RU5.28.0397 in my laptop (acer TraveMate P249-G2-M) whitch InsydeH2O bios. It doesn't work well, I can see the loaded RU（efi) interface,but can't press any key,like a crash.I can see the time is beating, but the keyboard doesn't respond.what's the matter?

    回覆刪除
  45. James Wang2021年11月11日 下午4:14

    @anonymous

    Can you please try "RU /S" ?
    Or try the version 5.25.0379?

    回覆刪除
  46. 匿名2021年12月15日 晚上7:19

    Can't start RU.EXE with MS-DOS 7 in some Award BIOS 4.5 motherboards, even use RU.EXE /S. Unless load HIMEM.SYS and EMM386.EXE.

    回覆刪除
  47. 匿名2021年12月16日 凌晨2:35

    Can't start RU.EXE with MS-DOS 7 in some Award BIOS 4.5 motherboards (PCem), even use RU.EXE /S. Unless load HIMEM.SYS and EMM386.EXE in CONFIG.SYS.

    回覆刪除
  48. James Wang2021年12月16日 晚上10:56

    Have you tried older versions of RU.exe?

    回覆刪除
  49. Unknown2022年1月4日 晚上7:23

    Just want to share my experience. Accessing UEFI variable menu using ver 5.25.0379 on Huawei MateBook E 2022 with the latest BIOS(1.17) is not working(it hangs). It works when using the 0379 version.

    回覆刪除
  50. 匿名2022年1月15日 凌晨1:01

    I tested ru.efi on somne new intel 12th gen notebook, seems not working.

    回覆刪除
  51. 匿名2022年1月15日 凌晨1:04

    Which I mean not working is when I boot from usb, the system will stop there, and only I can do is to shut it down

    回覆刪除
  52. 匿名2022年1月15日 下午3:16

    I use ru.efi /S and it works, thanks

    回覆刪除
  53. James Wang2022年1月17日 凌晨1:24

    Thanks!
    Can you try /s1, /s2, /s4, /s8 separately and see which one works for you?

    回覆刪除
  54. 匿名2022年1月19日 晚上9:00

    ru.efi /S4 works for me.
    thanks

    回覆刪除
  55. Unknown2022年1月31日 凌晨12:41

    12th gen latpot can not use it

    回覆刪除
  56. James Wang2022年11月2日 下午5:30

    Hi Unknown,

    I think I find the cause of why UEFI variable hangs, will be fixed in the next version.

    回覆刪除
  57. 匿名2023年2月21日 凌晨2:09

    家明，我的电脑是15款的电脑，用这个EFI键盘就失灵了，有什么好的办法嘛？同学的dell是好的，求助

    回覆刪除
  58. KGDEBUG2024年1月25日 凌晨2:59

    Hi James, I'd like to add the RU.EFI binary into my "TORO UEFI SHELL" https://github.com/KilianKegel/Visual-UEFI-SHELL#edk2-uefi-shell--toro-uefi-shell and publish with the next version as an integrated PLUGIN command. Would you mind if I do so?

    Best regards,
    Kilian
    kilian_kegel@hotmail.com

    回覆刪除
  59. James Wang2024年2月5日 下午4:18

    @KGDEBUG

    That's fine as long as it is not a commercial use. I saw your your project and it looks interesting.

    回覆刪除

歡迎留下意見, 但是我可能會回可能不會回
I may or may not respond, but welcome.