Hi all,
It has "HZ-006" printed on the PCB. It does have Pm39LV512-70JCB on the board, but it seems no firmware written and no boot ROM messages.
lspci: 00:0f.0 RAID bus controller [0104]: VIA Technologies, Inc. VT6421 IDE RAID Controller [1106:3249] (rev 50) Subsystem: VIA Technologies, Inc. VT6421 IDE RAID Controller [1106:3249] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 32 Interrupt: pin A routed to IRQ 18 Region 0: I/O ports at a800 [size=16] Region 1: I/O ports at a400 [size=16] Region 2: I/O ports at a000 [size=16] Region 3: I/O ports at 9800 [size=16] Region 4: I/O ports at 9400 [size=32] Region 5: I/O ports at 9000 [size=256] [virtual] Expansion ROM at 20020000 [disabled] [size=64K] Capabilities: [e0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: sata_via 00: 06 11 49 32 07 00 90 02 50 00 04 01 00 20 00 00 10: 01 a8 00 00 01 a4 00 00 01 a0 00 00 01 98 00 00 20: 01 94 00 00 01 90 00 00 00 00 00 00 06 11 49 32 30: 00 00 00 00 e0 00 00 00 00 00 00 00 0a 01 00 00 40: 33 03 f1 44 0e af 00 00 00 00 00 03 00 00 00 00 50: 00 00 04 00 00 00 00 00 00 10 10 00 05 00 20 00 60: 00 00 ff ff 00 00 00 00 00 00 00 00 00 00 ff ff 70: 00 00 00 00 01 f0 00 00 01 00 01 00 11 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 0b f2 c9 35 10 ac c0 00 a8 a8 a8 a8 ff 00 b6 b6 b0: 0f 0f 0f 0f 34 00 00 00 00 00 20 00 00 00 00 00 c0: 00 02 00 00 00 00 00 00 00 02 00 00 00 00 00 00 d0: 02 01 00 00 00 00 00 00 02 01 00 00 00 00 00 00 e0: 01 00 02 00 00 00 00 00 50 01 49 32 06 11 49 32 f0: 00 00 70 00 00 00 00 00 00 00 00 00 00 00 00 00
flashrom v0.9.6.1-r1564 on Linux 2.6.32-5-686 (i686) flashrom is free software, get the source code at http://www.flashrom.org
flashrom was built with libpci 3.1.7, GCC 4.4.5, little endian Command line (3 args): ./flashrom -p atavia -V Calibrating delay loop... OS timer resolution is 1 usecs, 261M loops per second, delay more than 10% too short (got 87% of expected delay), recalculating... 296M loops per second, 10 myus = 10 us, 100 myus = 98 us, 1000 myus = 986 us, 10000 myus = 9789 us, 4 myus = 5 us, OK. Initializing atavia programmer Found "VIA VT6421A" (1106:3249, BDF 00:0f.0). === This PCI device is UNTESTED. Please report the 'flashrom -p xxxx' output to flashrom@flashrom.org if it works for you. Please add the name of your PCI device to the subject. Thank you for your help! === Requested BAR is ROM Error: No supported PCI device found.
HTH, Roy
On Thu, 27 Dec 2012 15:42:39 +0800 Roy roytam@gmail.com wrote:
Hi all,
It has "HZ-006" printed on the PCB. It does have Pm39LV512-70JCB on the board, but it seems no firmware written and no boot ROM messages.
Hello Roy,
thanks for your report! I am collecting some facts about existing cards in our wiki: http://flashrom.org/VT6421A I have added the ones I know about your card and would like to add the remaining ones...
[…]
flashrom v0.9.6.1-r1564 on Linux 2.6.32-5-686 (i686) flashrom is free software, get the source code at http://www.flashrom.org
flashrom was built with libpci 3.1.7, GCC 4.4.5, little endian Command line (3 args): ./flashrom -p atavia -V Calibrating delay loop... OS timer resolution is 1 usecs, 261M loops per second, delay more than 10% too short (got 87% of expected delay), recalculating... 296M loops per second, 10 myus = 10 us, 100 myus = 98 us, 1000 myus = 986 us, 10000 myus = 9789 us, 4 myus = 5 us, OK. Initializing atavia programmer Found "VIA VT6421A" (1106:3249, BDF 00:0f.0). === This PCI device is UNTESTED. Please report the 'flashrom -p xxxx' output to flashrom@flashrom.org if it works for you. Please add the name of your PCI device to the subject. Thank you for your help! === Requested BAR is ROM Error: No supported PCI device found.
I am not entirely sure what happens there. Obviously pcidev_readbar reads 0... but we are not using that anyway and don't abort in that case AFAICS. There has been some discussion about refactor these parts and that would at least get rid of that message. I'll have to investigate and discuss this with my colleagues. What happens after that? flashrom exits? Can you please add -VVV to the command line and resend the resulting log?
2012/12/28 Stefan Tauner stefan.tauner@student.tuwien.ac.at:
On Thu, 27 Dec 2012 15:42:39 +0800 Roy roytam@gmail.com wrote:
Hi all,
It has "HZ-006" printed on the PCB. It does have Pm39LV512-70JCB on the board, but it seems no firmware written and no boot ROM messages.
Hello Roy,
thanks for your report! I am collecting some facts about existing cards in our wiki: http://flashrom.org/VT6421A I have added the ones I know about your card and would like to add the remaining ones...
[=85]
flashrom v0.9.6.1-r1564 on Linux 2.6.32-5-686 (i686) flashrom is free software, get the source code at http://www.flashrom.or=
g
flashrom was built with libpci 3.1.7, GCC 4.4.5, little endian Command line (3 args): ./flashrom -p atavia -V Calibrating delay loop... OS timer resolution is 1 usecs, 261M loops per second, delay more than 10% too short (got 87% of expected delay), recalculating... 296M loops per second, 10 myus =3D 10 us, 100 myus =3D =
98 us,
1000 myus =3D 986 us, 10000 myus =3D 9789 us, 4 myus =3D 5 us, OK. Initializing atavia programmer Found "VIA VT6421A" (1106:3249, BDF 00:0f.0). =3D=3D=3D This PCI device is UNTESTED. Please report the 'flashrom -p xxxx' output to flashrom@flashrom.org if it works for you. Please add the name of you=
r
PCI device to the subject. Thank you for your help! =3D=3D=3D Requested BAR is ROM Error: No supported PCI device found.
I am not entirely sure what happens there. Obviously pcidev_readbar reads 0... but we are not using that anyway and don't abort in that case AFAICS. There has been some discussion about refactor these parts and that would at least get rid of that message. I'll have to investigate and discuss this with my colleagues. What happens after that? flashrom exits? Can you please add -VVV to the command line and resend the resulting log?
Sure.
flashrom v0.9.6.1-r1564 on Linux 2.6.32-5-686 (i686) flashrom is free software, get the source code at http://www.flashrom.org
flashrom was built with libpci 3.1.7, GCC 4.4.5, little endian Command line (3 args): ./flashrom -p atavia -VVV Calibrating delay loop... OS timer resolution is 1 usecs, 302M loops per second, 10 myus =3D 10 us, 100 myus =3D 100 us, 1000 myus =3D 998 us, 10000 myus =3D 9996 us, 4 myus =3D 4 us, OK. Initializing atavia programmer Found "VIA VT6421A" (1106:3249, BDF 00:0f.0). =3D=3D=3D This PCI device is UNTESTED. Please report the 'flashrom -p xxxx' output to flashrom@flashrom.org if it works for you. Please add the name of your PCI device to the subject. Thank you for your help! =3D=3D=3D PCI header type 0x00 Requested BAR is ROM Error: No supported PCI device found.
-- Kind regards/Mit freundlichen Gr=FC=DFen, Stefan Tauner
On Fri, 28 Dec 2012 16:52:58 +0800 Roy roytam@gmail.com wrote:
2012/12/28 Stefan Tauner stefan.tauner@student.tuwien.ac.at:
I am not entirely sure what happens there. Obviously pcidev_readbar reads 0... but we are not using that anyway and don't abort in that case AFAICS. There has been some discussion about refactor these parts and that would at least get rid of that message. I'll have to investigate and discuss this with my colleagues. What happens after that? flashrom exits? Can you please add -VVV to the command line and resend the resulting log?
Sure.
[…] Error: No supported PCI device found.
Ah, I missed an obvious exit call... attached hack should get you further. If it does not work out of the box you can try the offset parameter with different values where the n upper bits are all 1 and everything below that is 0, e.g. for n=12 -p atavia:offset=0xfff00000 Please resend a -VVV log.
在 Sat, 29 Dec 2012 18:14:23 +0800, Stefan Tauner stefan.tauner@student.tuwien.ac.at 寫道:
On Fri, 28 Dec 2012 16:52:58 +0800 Roy roytam@gmail.com wrote:
2012/12/28 Stefan Tauner stefan.tauner@student.tuwien.ac.at:
I am not entirely sure what happens there. Obviously pcidev_readbar reads 0... but we are not using that anyway and don't abort in that case AFAICS. There has been some discussion about refactor these parts and that would at least get rid of that message. I'll have to investigate and discuss this with my colleagues. What happens after that? flashrom exits? Can you please add -VVV to the command line and resend the resulting log?
Sure.
[…] Error: No supported PCI device found.
Ah, I missed an obvious exit call... attached hack should get you further. If it does not work out of the box you can try the offset parameter with different values where the n upper bits are all 1 and everything below that is 0, e.g. for n=12 -p atavia:offset=0xfff00000 Please resend a -VVV log.
The patch is not working for me, pcidev_dev in atavia_init() is NULL here.
-
Roy -
Stefan Tauner