NicoLarve

New Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About NicoLarve

  • Rank
    Newbie
  1. Thanks for the feedback! I don't have a Windows PC, all BIOS version that I have processed so far have been with the same tools and copied to the same USB stick. However, I may try another USB stick (or reformat it) since I experienced dock station crash while the USB key was plugged into it and mounted in my PC. I did run fsck on it (from a Linux system) and if the BIOS flashing utility VERY is touchy, this could explain why it does not see the other BIOS versions. But sincerely, I doubt this is the case. I will try and let you know. In the end, note that I have the same problem than fenguoerbian. And note also that my current BIOS version (v1.60) is not available online, likely meaning it is crappy.
  2. Thank you. This is what I did: all of the BIOS I have come from the same page: https://asrock.com/mb/Intel/J3455-ITX/#BIOS I do really have a J3455-ITX board (=lshw= confirmed it). Files have been unzipped of course and are all of the same type, according to =file= command: $ file A* APLITX1.30: Intel serial flash for PCH ROM APLITX1.40: Intel serial flash for PCH ROM APLITX1.70: Intel serial flash for PCH ROM APOITX1.80: Intel serial flash for PCH ROM Only v1.80 is detected by the BIOS. That is why I am interested in afudos.exe and bootable MSDOS.
  3. When I do that, I can only see v1.80 proposed by the BIOS updater utility. In the end I cannot upgrade to v1.80 since one have first to install v1.70 beforehand, but it never shows up even when it is the only BIOS file present in the USB stick. I thought that using a DOS bootable stick + afudos.exe would allow me to control what can be done (either to install v1.70+v1.80 or to downgrade to v1.30 as some are suggesting in this thread).
  4. More importantly, I have front USB2/USB3 (those from the mobo connectors) that have unstable powering making, for example, keyboard's LEDs to blink! I have other issues with this motherboard, including "CMCI Storm" reported in system logs. These issues are the reasons why I wanted to give a try to more recent firmware versions at first. By the way, with v1.60, I have /dev/dri/ (Debian 10.5 - Linux 4.19).
  5. I wonder how could you have flashed this *UEFI motherboard* with MSDOS. I used to flash motherboard using Freedos, but it is not possible on UEFI hardware anymore. :( What is the trick I am missing here? (I left the windows world since so long, ...) I have the same motherboard with firmware v1.60, and like others, it was impossible for me to upgrade to v1.70 (not seen by flash utility), so I gave up with the idea to upgrade to v1.80. However, I am very interested in downgrading to v1.30. Thanks for your help.