-
Posts
873 -
Joined
-
Last visited
-
Days Won
14
Content Type
Profiles
Forums
Downloads
Posts posted by jacobsson
-
-
Hi guys, I ordered the EXP GDC V7.0 Ares on Nov 24 and it hasn't arrived to me yet... did you guys have the same problem?
Since you're importing from China it takes all from 10 days up to four weeks (depending on time of the year). Wait another week and see.
Sent from my iPhone
-
A: 1) Since it's not listed in any earlier implementatios it means that we can't recommend it as a candidate even if we wanted too.
A: 2) Your TOLUD seems to be BFA00000 =~ 2.99GB, which it less than the limit of 3.25GB so you should be safe.
A: 3) You can at best achieve x1 2.0 (5Gb/s) bandwidth with EXP GDC Beast / PE4L 2.1b / PE4C etc.
A: 4) Given the fact that some EXP GDC revisions have signal integrity problems I'd go for the PE4C mPCIe solution for now, or wait for an improved "EPX GDC V9"
A: 5) Dell DA-2 is an excellent choice of PSU for the GTX 660 SC, I just to run a GTX670 from a DA-2 myself.
- 1
-
hi, I have a problem with the detection of the graphics card with a PE4C 2.1b with mPCIe adapter.
I have a MSI GE60 dgpu 860m / egpu 9600gs. When I try to connect the 9600 is not detected, I have already tried to uninstall nvidia drivers but nothing.
how can I fix this?
thank you
Why would you want to use a 9600gs when you have a 860m? For testing purposes?
That card is very old and I think you might need setup 1.x in order to accommodate it into the PCI space.
What system are you using?
-
-
I did manage to un-brick it, read my post above (made me very happy)
My question is if I should go for a round 2 with the "ME FW image re-flash" setting or not, what do you think?
Would this do? (I'll use a raspberry pi)
Sent from my iPhone
-
UPDATE:
Alright so the "CTRL + HOME + POWER" method did not work initially, so I put the V209 bios file on my original hard drive and installed that one in system... And yeees I did go to emergency recovery! Now computer boots up again.
What do you say, flash back to unlocked BIOS again and try to enable the "ME FW Image re-flash"?
The reason I ask is because the G46VW/G75VW BIOS:es are easily corrupted, some people had their system bricked by just choosing "Don't save changes" in original BIOS, which makes me think that my problem could be random/unlucky.
-
Does clearing the CMOS do anything?
If you are referring to the battery it does nothing, I never understood what that battery do in my system. I'm going to attempt putting the original v209 bios on c: root, then home + ctrl + power to see if I can re-flash my old locked bios. Any objections to this method since I'm using an unlocked BIOS atm?
Sent from my iPhone
-
Hi guys.
I found a hidden BIOS option:
"ME FW image re-flash" and I set it to enable, the save and reboot. Now I ended up bricking in my system
It only lits the power led for 1 sec, then turns off, no screen no nothing. Dammit.. That's what you get for careless when using an unlocked BIOS...
Sent from my iPhone
-
Holy shit dude, nice work!
Are you planning to put in some guard mesh or just leave it naked? =)
-
"What do you mean?"
OK so I misunderstood your suggestion.
I thought:
1. If my ME was unlocked, then there wouldn't be any problem modify it and flash it back, no HDA_SDO unlock necessary.
Or
2. My ME is locked (like it is now), HDA_SDO or ponoma soil clip method in order to be able to dump the bios+me.
I do own a raspberry pi though.
Sent from my iPhone
-
Hi guys.
I found these two solder joints (resistors or diodes?) which had contact with Pin 1 and Pin 5:
There is no problem reaching them and shorting them doesn't help
One note though, Pin 5 and Pin 9 seems to be connected to each other (they are both DVDD so that's logical).
I tested just to dump the bios:
fptwin64 -d bios.bin -bios
No problem, yielded a 6.1MB bios.bin -file,
I guess the ME is in the missing restricted 1.9MB.
fptwin64 -d me.bin -me
Gives as expected: error 26.
------------------------------------------------------------------------------------------------------
Well that pretty much sums it up about the HDA_SDO method for my system.
I'm thinking I should find my self a "ponoma soic clip", as suggested by @Arise.
Finding an old system with LPT-port is the probably the biggest challenge.
Could you point me to which exact components names and values I need?
Then I'll be making an order tonight. Many thanks!
-
If you talking about an FPT version that doesn't require an unlocked descriptor: it does not exist. As people said above, if you cannot do the HDA_SDO method then an SPI Programmer is your only choice.
I'm gonna test the HDA_SDO method using 1K resistor tomorrow, if it doesn't work I'll have to figureout how to dump the BIOS via SPI programmer.
I'll post results asap, again thanks!
-
My G750JW required no hardware mod like shorting any pins or so. Only had to run the proper version of fpt and that was it!
Sent from my iPhone using Tapatalk
Interesting, may I ask which version?
Thanks for sharing this info!
Sent from my iPhone
-
It's definitely a valid way of unlocking the descriptor according to numerous Intel documentation. Noone said it's easy though... FPT will detect whether it's locked, it's not playing any games.
So I should probably try some more using the same method. Could it be possible that I need to use a resistor or something between pin1 + pin5?
Could Windows UEFI boot be any factor here? Thanks!
Sent from my iPhone
-
Alternative #1: see if there are hidden BIOS setup settings you could change to unlock the flash descriptor. Example: http://forum.techinferno.com/dell-latitude-vostro-precision/8176-%5Bguide%5D-dell-e6530-cpu-tdp-multi-unlocking.html
I guess that @Klem (that unlocked the BIOS) would already know about this if it was possible.
Reply from Klem:
"Hi!
If ME FW is realy locked in descriptor, then it can be unlock only with hardware programmer device.
Best Regards,
Klem"
(I hope you didn't mind me sharing your reply)
I see that you've done a lot of work on BIOS side of the G75VW, is your flash descriptor unlocked on that system?
-
Tested very carefully to short pin1 + pin5 on startup (found a joint that had direct contact with VDD pin1):
This didn't work, I measured ~70mA between pin1+pin5 at startup, which seems quite a lot (what do I know)?
Then in windows got the earlier mentioned behavior of sound chip disabled and ERROR 26 during "FPTw64 -d -bios.bin" (in Flash Programming Tool\windows64\).
I don't believe this is a valid method for unlocking flash descriptor newer ASUS laptops
EDIT: could it be the FPTw64 that plays me a prank, UEFI boot settings or anything else I can try?
-
Good luck trying to touch pin1+5. They are so tiny.
Instead, see if pin 5 has a track that leads to a larger pad somewhere. If it does, The can just short that pad to GND. Ideally via a small resistor to prevent shorting.
Alternative #1: see if there are hidden BIOS setup settings you could change to unlock the flash descriptor. Example: http://forum.techinferno.com/dell-latitude-vostro-precision/8176-%5Bguide%5D-dell-e6530-cpu-tdp-multi-unlocking.html
Alternative #2: remove the flash eeprom chip and read it with a SPI eeprom burner, flash the modified version, then solder back on the eeprom chip. You'd need a SMT hotgun to do properly. Not soldering iron type work.
I'm going to see if those pins leads to something more accessible, I brought the notebook to work where we have a lab and equipment.
I'll update you guys during the day, thank you so much for all suggestions so far!
-
wow, that chip is so tiny!
I have tried 15 times now,
Only reaction I've got so far is that sound chip get disabled after boot. Reboot and it works again, still error 26.
hmm.. I'm starting to lose hope about this method. Gonna give it 5 more tries
Edit: Nope, no dice...
-
Alright guys, my audio chip is a Realtek:
10EC = Realtek 0269 = ALC269
My system have two audio chips, guess the latter one is for HDMI?
Realtek High Definition Audio: 10EC 0269
and
High Definition Audio Device 10DE 0042 (Nvidia)
I will now do the following:
1. shut down system
2. find Realtek audio chip
3. jump 1 -> 5 with paper clip
4. pass post-screen then remove clip
5. dump my ME
Correct?
-
hi guys - totally new to this nice place - I wanted to ask if someone know - what size DC port is on EXP GDC Beast??!! Can it be 5.5x2.5 or its smaller ? thanks in advance
You are correct sir!
...And It allows for a maximum load of 150W.
-
@pluromaniac
I will check my audio chip tomorrow and come back to you, thank you very much for helping me out buddy.
Sent from my iPhone
-
To unlock the descriptor you need to use the HDA_SDO method which requires you to have physical access to the audio chip of the motherboard. So you would need to open the laptop for that.
Oh that's no problem at all, had it fully disassembled 10 times or more.
Is there any guide I can use to localize everything I need?
Thanks buddy!
EDIT: I found your example here
Help Wrong version update of Intel ME need to update back the good one
Now the question is which pins are corresponding to my audio chip:
I suspect the VIA chip in the lower right of this image:
-
hmm so that means it is locked. I have seen ASUS without it locked, but I guess they changed that policy. I do not know how to unlock your descriptor, but if you find out I will modify the ME FW.
Damn, that's too bad
Weird enough I don't find that G75VW users have the same problem...
Thanks anyway!
-
Send me your ME FW and I'll mod it. Asus does not lock the ME FW in the flash descriptor so it's easy.
I do get this error though:
EXP GDC Beast/Ares-V7/V6 discussion
in Enclosures and Adapters
Posted
@troshlyak
The DA-2 is enough for a GTX 670 so you don't need to worry.
Sent from my iPhone