2016年9月8日 星期四

RU 5.18.291 BETA

This release is mainly for saving snapshot from RU screen as BMP file.  Which is requested by Gary and other users.  Special thanks to Mykhaylo for the help.

I didn't test this version at all, so it could be buggy.  Please leave me a message if you find any bug.

New features
  • RU.EFI: Add F12 key to capture the screen snapshot to BMP file.
    File name is auto-generated: Format: "YYYYMMDDhhmmss.bmp"
    RU.EXE does not support this.

Bug fixes / improvements
  • Fix hangs sometimes when displaying system info (CTRL-I)
  • Fix SMBUS slave address is not remembered when re-enter RU
  • RU.EFI hangs after command line executed
  • Fix displaying wrong PCI base class code
  • Detect PCI functions with more tolerance
  • RU.EFI: Fix display wrong size of HDD information "1 Phy = XX Logi sec"
  • RU.EFI Fix HOME/END/UP/DOWN,etc. not working for select bar
  • Fix UEFI variable list with wrong color for variable attributes
  • RU.EFI: Fix screen scrambled with some VGA devices
  • Minor UI improvements
Download 5.18.0291 from Github.
Password: 199f784df37f

18 則留言:

Yan Chu 提到...

Hi James, I have an issue so I come to ask you for help .
When I enable legacyfree keyboard and enter RU.exe(DOS version),the keyboard doesn't work.However the machine doesn't hang.When I use KBC controlled by SIO ,this situation won't happen.
Thank you for reading my message.

James Wang 提到...

Hi Yan,

I think it is the problem that RU does not detect KBC correctly. I will check it later.

宗蔚林 提到...

Hi James, I am a BIOS engineer works in Taiwan and i find a interesting thing.
In Purley platform, there is a memory device defined in Intel datasheet but device can't be fund in these utility, RU/ UEFI shell /Linux lspci / Window RW.
The device VendorID/DeviceID is 0x8086/0x2069 and only first 16 bytes have value, other PCI space are all 0x00. I list first 16 bytes for your reference.
8086 2069 0000 0000 0002 0880 0000 0080
I think it should be a device and should be listed in PCI scanner tool.
Could you please check it, why these PCI scanner tool ignore the device.
Thank you for reading my message.

宗蔚林 提到...

Because i use 0xcf8, 0xcfc utility to scan PCIe device, i find the special device.

James Wang 提到...

Hi 林宗蔚

It should be scanned by RU because it has valid vendor device and IDs. RU also scans using 0xcf8 and 0xcfc.

Anyway I will simulate a PCI device with these 16 bytes and see what happens.

James Wang 提到...

Hi 林宗蔚,

Where is the location of this PCI device? Is it located at function 0? If it is not, what is the function 0?

宗蔚林 提到...

Hi James,
Thanks for your response. From your question, i think the key point is what you mentioned.
The device location in hex is B:64,D:16,F:1. However, The device of B:64,D:16,F0 registers are all 0xFF. There is no PCIe device 0, but device 1 exist. Is it reasonable ?

James Wang 提到...

Hi 林宗蔚

RU used to checked if the function 0 is invalid then it will not scan other functions. But this version it will scan all functions no matter function 0 is valid or not. Have you tried this 0291 build yet?

宗蔚林 提到...

Hi Jame
Thanks for your response. I test 291 build on DOS/shell, the device still not be scanned by RU.

James Wang 提到...

Hi 林宗蔚,

Than I have to review my code and see what could be the problem, thanks for the testing.

宗蔚林 提到...

Hi James

I will wait for your good news.

James Wang 提到...

Hi 林宗蔚,

Can you please get this test version and see if it can find the PCI device?

https://github.com/JamesAmiTw/ru-uefi/raw/master/Ru292.zip
password: 12411016

宗蔚林 提到...

Hi James

The special device fail to be detected by ru292 (by pressing F6 page).
I press Alt+1 to fill bus/Dev/function to find the device and dump the device register for your reference.

Type:PCI Bus 3A Device 16 Function 01
Offset:0000 Width:01
86 80 69 20 00 00 00 00 02 00 80 08 00 00 80 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

James Wang 提到...

Hi

I think I made a mistake, please get this one:
https://github.com/JamesAmiTw/ru-uefi/raw/master/RU0292.ZIP
password: 11331108

宗蔚林 提到...

Hi James,
Device is be detected by the latest RU.
Thanks for your great support.

Tony Cheng 提到...

Hi James,

I use the RU DOS version, and have a question.
In Intel Braswell platform, when I update the Intel VBIOS version to 1009 or newr, and check the CMOS byte0(second),the auto refresh rate become very slow, about 40 seconds. If I point to the specify register, the refresh rate will be normal.
What is the RU refresh method?

Thank you.

James Wang 提到...

Hi Tony,

RU refresh is from a infinite loop. There will be a count to decide when to refresh. So basically the refresh rate should not be affected.

Tony Cheng 提到...

Hi James,

OK, thanks.
I will check VBIOS with Intel.