![]() ![]() The board is acceptably responsive in IDE mode.Web Presentation and Text Copyright © 2012, 2013, 2021 by Daniel B. THE INSTALLATION WAS PERFORMED IN AHCI MODE BUT WOULD ONLY BOOT AND SHUT DOWN IN IDE MODE. I went backwards and forwards a few times to make sure. I retried the installation after wiping the HDD and this made no difference.Īfter following several red herrings, I tried changing the SATA mode from AHCI to IDE in the BIOS and the machine booted and shut down perfectly. Or get stuck at the message "ata1.00: failed command: READ FPDMA". On attempting several reboots from the HDD, I would drop into into "(initramfs)" most times When the installation finished, it went to restart but got stuck in the shell with a message "ModemManager. I installed Linux Mint 17.2 with xfce 32 bit from a reliable CD-ROM. I had a similar problem with a Gigabyte GA-J1800N-D2H which looks like a similar board featuring an Intel J1800 SoC. It may be that the AHCI mode just doesn't work very well with the American Megatrends BIOS. Does anyone have any ideas as to why or where I should look to help figure out why the custom bios with SATA Mode AHCI does not boot? I am currently looking for what is making the difference. In IDE mode, still fails on transfer to root.īUT, when I select Arch's fallback boot menu option, and SATA mode is IDE, I get semi successfully boot that is I get to login prompt, but there is a decent amount of errors during boot. Next, and finally, I installed arch again, but this time to a single partition and used dev, not UUID or LABEL. Then I figured I would try Arch Linux, which also failed in IDE mode, and wasn't seen in AHCI. The Jetway engineers suggested upgrading the kernel, I thought fair enough, this did not help. The Crux OS has slightly outdated custom kernel on it and uses initramfs (also custom). Vista does not boot successfully (more, boot process doesn't start) Linux (crux) does not boot successfully (more, the boot process doesn't start) Linux (crux) boots until looking for root When I put it in custom bios, not successful.Īfter further debugging, this is what I think I know: So I can take the disk, boot it in the standard bios, and everything is successful. Further, I have an exact copy (hardware & software wise) of this system, using the standard bios that came with the NF98. To start, I have decent experience debugging Linux boot. This time it makes it a bit further, and fails when looking for root /. This allows the disk to be seen, but boot still fails. So I plug my SATA disk in running a custom version of the Crux Linux distro, and bios reports please connect a disk, as if it sees none (even though a glance into bios settings shows a disk connected to port 0).Īfter some debugging I change the SATA-Mode from AHCI to IDE. What they provided did almost exactly that, except it was not configurable, it just was set to not allow anything other than SATA Port 0 to boot. The goal was simple, allow me to configure bios to refuse any other medium besides the disk connected via SATA Port 0 to be booted from. ![]() I told them my goal, and they got right to it and shipped a custom bios. So I reached out to Jetway, and they have been unbelievably helpful. I learned that they just provide the source code to compile (? or maybe just a logo?) but Jetway is the one who configures and produces the actual bios. The original bios says American Megatrends at the top. Obviously, this is difficult to ask considering its a *custom bios, but hopefully I can provide enough detail so that somebody could provide some ideas, because I am running out. In a nutshell, I am trying to figure out for some Jetway engineers and myself, why the custom bios they made me does not allow SATA devices to boot in AHCI mode. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |