flashrom

flashrom@flashrom.org

5 participants
9154 discussions

Chipset enable for nVidia nForce4/MCP4.
by Luc Verhaegen 05 Oct '09

05 Oct '09

Please test whether your board is matched correctly. When the board enable gets provided, please apply that on top of this patch, and if both work correctly, reply to both mails with Acked-by: Martin ##DeineRichtigeNachname## <info(a)sukimashita.com> Also, the pci id matched here is not in the pciids.sf.net database. You might want to work with them to get your pciids in their list (my guess is that they need you to dig through some windows driver .inf files.) Thanks, Luc Verhaegen.

2 2

[commit] r744 - trunk
by svn＠flashrom.org 05 Oct '09

05 Oct '09

Author: libv Date: 2009-10-05 18:04:47 +0200 (Mon, 05 Oct 2009) New Revision: 744 Modified: trunk/chipset_enable.c Log: Chipset support for the nVidia nForce 4. Add pciids for the new isa bridge, and hook it to the nforce2 chipset enable. Signed-off-by: Luc Verhaegen <libv(a)skynet.be> Acked-by: Martin Szulecki <opensuse(a)sukimashita.com> Modified: trunk/chipset_enable.c =================================================================== --- trunk/chipset_enable.c 2009-10-03 17:08:02 UTC (rev 743) +++ trunk/chipset_enable.c 2009-10-05 16:04:47 UTC (rev 744) @@ -1018,6 +1018,7 @@ {0x8086, 0x7000, OK, "Intel", "PIIX3", enable_flash_piix4}, {0x8086, 0x7110, OK, "Intel", "PIIX4/4E/4M", enable_flash_piix4}, {0x8086, 0x122e, OK, "Intel", "PIIX", enable_flash_piix4}, + {0x10de, 0x0030, NT, "NVIDIA", "nForce4/MCP4", enable_flash_nvidia_nforce2}, {0x10de, 0x0050, OK, "NVIDIA", "CK804", enable_flash_ck804}, /* LPC */ {0x10de, 0x0051, OK, "NVIDIA", "CK804", enable_flash_ck804}, /* Pro */ {0x10de, 0x0060, OK, "NVIDIA", "NForce2", enable_flash_nvidia_nforce2},

1 0

"ERASED FAILED!" messages for ICH2 / SST49LF0002A/B
by Allan Bjorklund 05 Oct '09

05 Oct '09

Hello, I'm wanting to upgrade the BIOS on an older machine that I have. A Sony Vaio (PCV-RX650(UC)), with an ASUSTeK mother board (P4B266LM Rev: 1.xx), running Linux kernel 2.6.28. Running flashrom (today's trunk version) with no arguments gives this: flashrom v0.9.1-runknown No coreboot table found. Found chipset "Intel ICH2", enabling flash write... OK. This chipset supports the following protocols: Non-SPI. Calibrating delay loop... OK. Found chip "SST SST49LF002A/B" (256 KB, FWH) at physical address 0xfffc0000. No operations were specified. I saved a copy of my existing BIOS image with: flashrom -r original_bios.bin That appears to work, as the file is the same size as the updated BIOS .bin file I downloaded from the vendor's site. To test writing, I attempted to write the original BIOS image back with flashrom -w original_bios.bin, and here is the output: flashrom v0.9.1-runknown No coreboot table found. Found chipset "Intel ICH2", enabling flash write... OK. This chipset supports the following protocols: Non-SPI. Calibrating delay loop... OK. Found chip "SST SST49LF002A/B" (256 KB, FWH) at physical address 0xfffc0000. Flash image seems to be a legacy BIOS. Disabling checks. Writing flash chip... ERASE FAILED at 0x00000000! Expected=0xff, Read=0x25, failed byte count from 0x00000000-0x00003fff: 0x3fa4 ERASE FAILED! ERASE FAILED! ERASE FAILED! ERASE FAILED! FAILED! Your flash chip is in an unknown state. Get help on IRC at irc.freenode.net channel #flashrom or mail flashrom(a)flashrom.org ------------------------------------------------------------ DO NOT REBOOT OR POWEROFF! If I do a flashrom -v original_bios.bin, I get: flashrom v0.9.1-runknown No coreboot table found. Found chipset "Intel ICH2", enabling flash write... OK. This chipset supports the following protocols: Non-SPI. Calibrating delay loop... OK. Found chip "SST SST49LF002A/B" (256 KB, FWH) at physical address 0xfffc0000. Flash image seems to be a legacy BIOS. Disabling checks. Verifying flash... VERIFIED. And reading a second copy and doing a binary diff shows no differences, so my BIOS checks out as not being damaged. (At least, I think so.) So, any advice on what to look for/change to make this work? Thanks. --Allan

4 4

Board support for ASUS P5ND2-SLI Deluxe.
by Luc Verhaegen 05 Oct '09

05 Oct '09

Can you attach the output of lspci -vvnnxxx? I will soon send in a patch for the chipset enable. When the full lspci is provided, i will be able to quickly provide you with a board enable for your board. Oh, and about your blog entry: my first linux box was a SuSE 6.0, but undoubtedly Stepan can easily trump that as i believe he was working for SuSE (already/still) at the time. Also, please use your real and full name for acknowledging patches later on. Luc Verhaegen.

1 0

Re: [flashrom] [coreboot] #131: New flashrom motherboard support
by Martin S. 05 Oct '09

05 Oct '09

On Mon, 2009-10-05 at 01:45 +0000, coreboot wrote: > #131: New flashrom motherboard support > ---------------------------------+------------------------------------------ > Reporter: anonymous | Owner: somebody > Type: enhancement | Status: new > Priority: trivial | Milestone: flashrom v1.0 > Component: flashrom | Version: > Keywords: flashrom asus | Dependencies: > Patchstatus: there is no patch | > ---------------------------------+------------------------------------------ > > Comment(by hailfinger): > > Please send a short mail to flashrom(a)flashrom.org which has a link to this > ticket and mentions that you're the person with the "ASUS P5ND2-SLI > Deluxe". This will make it easier for us to stay in touch with you. > Thanks. > Ticket URL: <http://tracker.coreboot.org/trac/coreboot/ticket/131#comment:4> It's me. ;) Cheers. --- Martin S.

1 0

Data regarding GA-MA790GP-UD4H board
by Yair K. 05 Oct '09

05 Oct '09

Hi, Per discussion in IRC, I'm attaching "flashrom -V" and "lspci -nnvx" output. Flashrom 0.9.0 flashing works. Hopefully the attached files will help with autodetection. Yours, Yair K.

2 1

flashing results for the MS-7094 board
by Jelle Geerts 05 Oct '09

05 Oct '09

Hello, I've ran flashrom -v {-E,-r,-v,-w} on my MS-7094 board. For more info regarding the board, please see http://www.msi.com/index.php?func=proddesc&maincat_no=1&cat2_no=&cat3_no=&p… I've attached the results to this e-mail. Reading/verifying/writing worked fine. Erasing however, didn't go so well, as you can see in the attached log. BTW, two thumbs up to the flashrom developers: the Award flash utility did not work (kept saying 'Unknown flash type'), but flashrom did. ;) HTH, Jelle Geerts

3 2

Non-working board submission: Asrock K7VT4A+
by Putlinuxonit 04 Oct '09

04 Oct '09

Hi, I've tested this board with flashrom-0.9.0-r695 as well as superiotool r4424. Also contained are dumps from* #lspci -vvnnxxxx*, *#dmidecode* and *#lshw*. i tried a forced read via *#flashrom -f -r -c SST39SF020A oldfirmware.bin*and provide the dumps as well though that maybe useless as i was warned. A lot of the info is probably duplicated but is provided for the sake of completeness. Bios: AMI > Board: Asrock K7VT4A+ > Flash Chip: SST39SF020A (PLCC) > Chipset: Via VT8235 > Enjoy!, Udu E. Ogah .~~~~~~~~~~.

2 1

Asus M4A79T deluxe
by Sander Sweers 04 Oct '09

04 Oct '09

Hello Flashrom people, I just successfully did a flash from linux for the first time ever, yeah :-) Attached are the logs (bzipped) for flashrom -V -rV and flashrom -V -wV. I hope this help you guys adding official support for this motherboards. If you need more info please let me know. Greets Sander

1 0

Re: [flashrom] [coreboot] [PATCH]Remove non-CBFS
by Carl-Daniel Hailfinger 03 Oct '09

03 Oct '09

[adding flashrom(a)flashrom.org to CC] On 03.10.2009 18:40, Peter Stuge wrote: > Carl-Daniel Hailfinger wrote: > >> Given that flashrom already has a generic image layout feature, I >> propose to have cbfstool spit out an image layout file which is >> then read by flashrom. This makes flashrom independent of CBFS and >> that's a good thing (think upgrade). >> > > This is trivial to implement and might be a good first step, but it's > absolutely horrible from a usability perspective; > > The user would need to keep track of and understand no less than two > tools, AND an intermediary layout file, in order to perform the > single task of partial firmware update. > The user has to understand cbfstool and lar anyway right now if he/she wants to do anything useful with fallback/normal. The user also has to understand flashrom to flash the resulting image. The user will not directly inspect the ROM image, nor will he/she directly inspect the layout file. > I think it is quite neccessary for flashrom to understand CBFS (and > LAR, for v3 users). > What about WPH and other formats from proprietary BIOS vendors? Flashrom has more users who deal with WPH and related formats than it has users who deal with CBFS or LAR. IIRC the Unix philosophy is roughly "Create programs that do one thing and do it well. Use simple programs together." I like that philosophy. One option would be to have cbfstool and lar execute the flashrom binary. Regards, Carl-Daniel -- http://www.hailfinger.org/

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom