Jump to content

Binary_Nexus

Member
  • Posts

    24
  • Joined

  • Last visited

Awards

This user doesn't have any awards

2 Followers

Profile Information

  • Location
    The Moon
  • Occupation
    Electrical Engineer

System

  • CPU
    AMD Ryzen 9 3950X @4.3GHz
  • Motherboard
    Asus TUF X470-Plus Gaming
  • RAM
    64GB
  • GPU
    Nvidia Quadro RTX 5000
    Intel Xeon Phi 7120A Engineering Sample
  • Case
    LianLi Lancool One Champagne Limited Edition
  • Storage
    ~5.5TB
  • PSU
    Fractal Design Newton 1000W
  • Display(s)
    2x 1080p Monitors
  • Cooling
    Cooler Master MasterAir MA620M
  • Keyboard
    IBM Model M Terminal Keyboard (122-key)
  • Mouse
    Yes
  • Sound
    Yes
  • Operating System
    Windows 10 Pro

Recent Profile Visitors

420 profile views

Binary_Nexus's Achievements

  1. So, I've tried flashing that old BIOS to my card and now I've got something different from what I had before. Attempting to start the card with micctrl --start echos "The Intel(R) Xeon Phi(TM) coprocessor is starting. Error manipulating coprocessors: Error starting device." So instead I tried resetting the card using micctrl -r and nothing happens so I view the status of the card with micctrl -s and it echos the error "mic0: reset failed (mode: N/A image: C:\Program Files\Intel\MPSS\filesystem\bzImage-knightscorner.bin)", which I have never had before. With BIOS 1.0.0.1159 it would issue the node 0 reset command to the card correctly but starting the card would cause it to time out after attempting to boot from the knightscorner bzimage. I feel like the older BIOS is either confusing the card or MPSS (or both), and as 1.0.0.1140 is shorter compared to 1.0.0.1159 there may have been some slightly different configs or bugs that the newer version corrected? Which card did you get version 1.0.0.1140 from by the way? Was it Knights Ferry Rev. F or something earlier? Because if it's the same board revision as my card (Cherrypeak Fab. F) then that could mean that there are some smaller revisions for each major revision of A through F (i.e. small BIOS alterations, presence of debug ports, extra or fewer components, etc.), something which I hadn't really considered before.
  2. Interesting.. I've done some comparisons between my .bin file and yours and mine is slightly newer. It appears to actually be version 1.0.0.1159 and is 629 lines long compared to 1.0.0.1140 which is only 430 lines. Here's mine if anyone wants it to play with it. I may try and flash your older version to the card and see what happens. Though, my version does mention 1.0.0.1140 in it, but also mentions 1159. It's a bit of an odd one.. Intel KNF Rev F BIOS (v1.0.0.1159).Bin
  3. Oh that's a real shame! And regarding the BIOS encryption that's also a bummer. I knew that offloading programs to KNF required encryption but I didn't know the BIOS was encrypted too.. I used a USB BIOS flash/extractor tool to read the BIOS on my KNF and got the .bin file (which I guess is what you did too?). I may give the binary file a run through Ghidra to see if I can get anything else from it.
  4. Also, I wonder what the BIOS is on Linus' card...
  5. Awesome! I may give that a flash to my Knights Ferry card to see if I see anything different. I'll compare it to the BIOS currently on my card in case mine is corrupted in some way.
  6. I do have a Larrabee BIOS I extracted from mine. It's LRB Flash Image Version 1.0.0.1140, so a slightly later version. Different card revisions may have slightly different BIOSes but that would have to be explored if others are willing to try extracting their's.
  7. Yeah I saw that the bidding ended the other day. Far too expensive for me to have even considered bidding. I hope whomever has bought it can extract the Larrabee Customizable Video BIOS. I'd love to have a copy, both for archival purposes and for seeing if I can flash it to one of my KNF cards
  8. Oh fair enough Yeah I think it's going to be a challenge for me to get this working properly lol The KNF cards are very different from the production KNC cards
  9. I have a Larrabee/Knights Ferry card. It is the last revision of the Cherrypeak CRB (codename for the KNF boards) and doesn't have any display outputs (although it does have solder points for them). The card is essentially the same as Larrabee (i.e. it can be used to render a display via another display adapter).. So how exactly did you manage to explore the BIOS of your HD 5870? I imagine the BIOS of your card is slightly different as there will be tools designed for AMD/Nvidia/ATI, but maybe I can at least get somewhere with it. My card shows up as a coprocessor but it's only using a newer Intel MIC driver which doesn't properly work with it so it doesn't run properly.
  10. Hi, I'm having difficulty booting my Intel Bay Lake/Bay Trail-T development board. The screen hangs on the Intel Inside screen. I'm getting the POST code 012F (can't find any info on what that means) and in the boot log attached I get errors regarding an "Invalid OSIP". I managed to SSH into the board via serial connection to my laptop to get the boot log. Board is running an Engineering Sample Atom SoC equivalent to an Atom Z3775. I'd appreciate any help. Thanks. IntelBYTlog(1).txt
  11. Update I finally got round to installing MPSS 3.8.6 and the card seemed to be detected properly and everything seemed to set up fine, but issuing the command micctrl --start still doesn't cause the card to boot. I get the error mic0: boot failed (mode: Linux image: \bzImage-knightscorner.bin)
  12. I've got access to three Knights Ferry cards. One of them I'm pretty sure has a corrupted BIOS or something as it doesn't get as far as the other cards in terms of trying to boot the card uOS
  13. Fair enough! I'll have a try with 3.8.6 tomorrow
  14. My card doesn't show up as a display adapter for me. Just shows up in Device Manager as "coprocessor", not under display adapters GPU Z and Speccy both show nothing for me In cmd I can use micinfo and it just says "Knights Ferry - unknown error" Which exact driver did you use for the card and how exactly did you install it?
  15. Hi, I'm trying to mod the BIOS on my motherboard just to enable Above 4G Decoding. The option is available in AMIBCP v5 but when I change the setting and save the BIOS, trying to flash it in EzFlash doesn't work. EzFlash just refuses to flash the modded BIOS because it doesn't think that it's a proper BIOS. Asus didn't have any desire to help me with my issue. I am trying to get one of my Xeon Phis working in my PC and it requires Above 4G Decoding to be enabled for the system to boot with the card installed. Yes I know it's a pretty strange thing to do, especially since it's an AMD motherboard, however I am willing to experiment. I just don't really know where I'm going wrong with modding the BIOS so I'd really appreciate help.
×