I was wondering if anyone on the list had a copy of a functional video option ROM from the ASRock E350M1 board. As it uses an UEFI BIOS, bios_extract doesn't recognize it. I do not yet have the board in hand (still enroute) to extract it from the factory ROM in Linux, though I have read that it is possible from a previous thread. I'd much prefer starting with a known good ROM as opposed to troubleshooting my own ineptitude. I am sure I will have plenty of opportunities with that elsewhere in the process!
On a side note, I was unable to entice coreboot to build in Ubuntu 11.10 due to the broken linker, but was also further unable to build with the crossgcc toolchain. I sidestepped by loading 10.10 on an unused machine (which appears to have been successful), but thought it should be mentioned. Logs available for the interested parties.
Thanks, Todd
Todd wrote
]I was wondering if anyone on the list had a copy of a functional video ]option ROM from the ASRock E350M1 board. As it uses an UEFI BIOS, ]bios_extract doesn't recognize it. I do not yet have the board in hand ](still enroute) to extract it from the factory ROM in Linux, though I have ]read that it is possible from a previous thread. I'd much prefer starting ]with a known good ROM as opposed to troubleshooting my own ineptitude. I am ]sure I will have plenty of opportunities with that elsewhere in the ]process!
I know of two ways to extract the legacy video option rom:
a) Download the image from the manufacture's web site: 1. ftp://174.142.97.10/bios/CPU/E350M1(1.50)ROM.zip 2. Extract the 4MB UEFI image (E350M11.50) 3. Use 7-zip (version 9.21 beta) to decompress. 4. Hex edit this file: E350M1(1.50)ROM\2\CSMCORE\1.raw 5. Find the start of the video option rom. It starts with 55 AA and contains text "AMD Fusion Wrestler generic VBIOS" 6. The length is the byte after 55 AA (71) * 200h = E200h. 7. Extract E200 bytes starting at 55 AA.
b) When the board arrives... 1) Boot MSDOS and start DOS debug 2) At the - prompt, enter these commands: -n vga.bin -rbx -1 -w 3) The option rom is vga.bin in the current directory.
Thanks, Scott
On a side note, I was unable to entice coreboot to build in Ubuntu 11.10 due to the broken linker, but was also further unable to build with the crossgcc toolchain. I sidestepped by loading 10.10 on an unused machine (which appears to have been successful), but thought it should be mentioned. Logs available for the interested parties.
Thanks, Todd
On 11/03/12 05:04, Scott Duplichan wrote:
I know of two ways to extract the legacy video option rom:
a) Download the image from the manufacture's web site: 1. ftp://174.142.97.10/bios/CPU/E350M1(1.50)ROM.zip 2. Extract the 4MB UEFI image (E350M11.50) 3. Use 7-zip (version 9.21 beta) to decompress. 4. Hex edit this file: E350M1(1.50)ROM\2\CSMCORE\1.raw 5. Find the start of the video option rom. It starts with 55 AA and contains text "AMD Fusion Wrestler generic VBIOS" 6. The length is the byte after 55 AA (71) * 200h = E200h. 7. Extract E200 bytes starting at 55 AA.
b) When the board arrives... 1) Boot MSDOS and start DOS debug 2) At the - prompt, enter these commands: -n vga.bin -rbx -1 -w 3) The option rom is vga.bin in the current directory.
Thanks, Scott
a) is good. b) is just going to get you 64KB of unintialised data. There is nothing in those instructions to access the video BIOS AFAICT.
Andrew
Regarding ATI cards, (and i assume this board has such card), you can grab the bios from /proc under linux. That worked for R300/R500 radeon video cards, maybe it still works on more recent ones :
as root: cd /sys/bus/pci/devices/<pci bus id>/ echo 1 > rom cat rom > /tmp/vbios.rom echo 0 > rom
Keep in mind, i am not sure it's 100% complete ram bios, but that's what xorg ati devs suggested as steps to dump the bios when identifying some bugs with radeon hardware on linux.
2012/3/12 Andrew Goodbody ajg4tadpole@gmail.com
On 11/03/12 05:04, Scott Duplichan wrote:
I know of two ways to extract the legacy video option rom:
a) Download the image from the manufacture's web site:
- ftp://174.142.97.10/bios/CPU/**E350M1(1.50)ROM.zipftp://174.142.97.10/bios/CPU/E350M1%281.50%29ROM.zip
- Extract the 4MB UEFI image (E350M11.50)
- Use 7-zip (version 9.21 beta) to decompress.
- Hex edit this file: E350M1(1.50)ROM\2\CSMCORE\1.**raw
- Find the start of the video option rom. It starts with 55 AA and contains text "AMD Fusion Wrestler generic VBIOS"
- The length is the byte after 55 AA (71) * 200h = E200h.
- Extract E200 bytes starting at 55 AA.
b) When the board arrives...
- Boot MSDOS and start DOS debug
- At the - prompt, enter these commands: -n vga.bin -rbx -1 -w
- The option rom is vga.bin in the current directory.
Thanks, Scott
a) is good. b) is just going to get you 64KB of unintialised data. There is nothing in those instructions to access the video BIOS AFAICT.
Andrew
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/**mailman/listinfo/coreboothttp://www.coreboot.org/mailman/listinfo/coreboot
Andrew Goodbody wrote:
]> ]> b) When the board arrives... ]> 1) Boot MSDOS and start DOS debug ]> 2) At the - prompt, enter these commands: ]> -n vga.bin ]> -rbx ]> -1 ]> -w ]> 3) The option rom is vga.bin in the current directory. ]> ]> Thanks, ]> Scott ] ]a) is good. ]b) is just going to get you 64KB of unintialised data. There is nothing ]in those instructions to access the video BIOS AFAICT. ] ]Andrew
Oops, make that: -n vga.bin -rbx -1 -w c000:0 -q
Thanks, Scott
HighlyCaffeinated wrote:
unable to build with the crossgcc toolchain. I sidestepped by loading 10.10 on an unused machine (which appears to have been successful), but thought it should be mentioned. Logs available for the interested parties.
Yes, logs are neccessary for any action to be taken.
It would be nice if you could perform various xgcc experiments, to isolate the problem. This is not practical over email, but perhaps on IRC.
//Peter
Extracting the vga.rom from the BIOS file appears to have gone well. The board has arrived and I am waiting for a fresh flash chip to start playing. Thank you very much for taking the time for the fishing lesson... it is very much appreciated. Many are unwilling to commit the time to teach while answering a question.
I took the time to look up the recommended debug commands, and from what I learned I was left curious where the data source was specified. Given the corrections I think I get it now. Thanks for that as well!
I will make a concerted effort to catch someone on IRC in the next few days to give it a look. I'm curious as to the fault, and I am certain I will learn a lot in the process. Thanks again!
-Todd
________________________________ From: Peter Stuge peter@stuge.se To: coreboot@coreboot.org Sent: Monday, March 12, 2012 8:21 PM Subject: Re: [coreboot] ASRock E350M1 video option ROM?
HighlyCaffeinated wrote:
unable to build with the crossgcc toolchain. I sidestepped by loading 10.10 on an unused machine (which appears to have been successful), but thought it should be mentioned. Logs available for the interested parties.
Yes, logs are neccessary for any action to be taken.
It would be nice if you could perform various xgcc experiments, to isolate the problem. This is not practical over email, but perhaps on IRC.
//Peter
Appears as though the toolchain build failure was user error. I was missing m4. Once I figured that out, I installed with 'apt-get install m4' and the build completed successfully. Might want to add that to the list of required packages on the page here: http://www.coreboot.org/Build_HOWTO
Thanks! -Todd
________________________________ From: HighlyCaffeinated javatodd32@yahoo.com To: Peter Stuge peter@stuge.se; "coreboot@coreboot.org" coreboot@coreboot.org Sent: Monday, March 12, 2012 11:53 PM Subject: Re: [coreboot] ASRock E350M1 video option ROM?
Extracting the vga.rom from the BIOS file appears to have gone well. The board has arrived and I am waiting for a fresh flash chip to start playing. Thank you very much for taking the time for the fishing lesson... it is very much appreciated. Many are unwilling to commit the time to teach while answering a question.
I took the time to look up the recommended debug commands, and from what I learned I was left curious where the data source was specified. Given the corrections I think I get it now. Thanks for that as well!
I will make a concerted effort to catch someone on IRC in the next few days to give it a look. I'm curious as to the fault, and I am certain I will learn a lot in the process. Thanks again!
-Todd
________________________________ From: Peter Stuge peter@stuge.se To: coreboot@coreboot.org Sent: Monday, March 12, 2012 8:21 PM Subject: Re: [coreboot] ASRock E350M1 video option ROM?
HighlyCaffeinated wrote:
unable to build with the crossgcc toolchain. I sidestepped by loading 10.10 on an unused machine (which appears to have been successful), but thought it should be mentioned. Logs available for the interested parties.
Yes, logs are neccessary for any action to be taken.
It would be nice if you could perform various xgcc experiments, to isolate the problem. This is not practical over email, but perhaps on IRC.
//Peter