[b][/b]
[i][/i]
[u][/u]
[s][/s]
[code][/code]
[quote][/quote]
[spoiler][/spoiler]
[url][/url]
[img][/img]
[video][/video]
Smileys
smile
smile2
spook
alien
zunge
rose
shy
clown
devil
death
flash
sick
heart
idee
frage
blush
smokin
mad
sad
wink
frown
crazy
grin
hmm
laugh
mund
oh
rolling_eyes
lil
oh2
shocked
cool
[mail][/mail]
[pre][/pre]
Farben
[rot][/rot]
[blau][/blau]
[gruen][/gruen]
[orange][/orange]
[lila][/lila]
[weiss][/weiss]
[schwarz][/schwarz]
Ghaben
Posts: 2 | Last online: 08.14.2017
Date registered
08.11.2017
Sex
not specified
    • Ghaben has written a new post "X58 Chipset with problems to boot off a PCIe connected SSD" 08.14.2017

      Major problem is that system won't start at all if on-board USB 3.0 chip is enabled.

      Boot process halts at console screen with $ characters in red colour and the "Hello to EFI World!" message (also in red) on centre of the screen (i.e. even BEFORE the Tianocore logo would show up), I cannot even get to the Shell EFI screen...

      The only way to pass through this point is rebooting the computer and disabling the USB 3.0 chip from BIOS before booting DUET.

      On-board USB chip is Renesas u720200 (rev. 3) and I have updated its firmware to the latest available version (v3.0.3.4). GA-X58A-UD7 mobo has the latest available stable BIOS (ver. FD) and I couldn't even find newer betas to experiment with...

      For testing purposes I can dual boot my computer into my old copy of Windows residing on a SATA SSD via regular boot process (USB chip enabled in BIOS) and the USB 3.0 ports are properly recognized by Windows and the ports work flawlessly that way. However, if I use DUET for booting into the new copy of Windows on the PCIe NVMe drive I run into the problem described in the foregoing.

      If I disable the on-board USB 3.0 chip, DUET boots and Windows loads beautifully from the PCIe NVMe partition and the system works like a dream! However, in this case USB 3.0 ports (being disabled in BIOS) are not seen by Windows, therefore its drivers are not loaded either.

      Altogether, it isn't a real hardware issue (chip/ports work fine), it only looks that efildr20 doesn't like my USB 3.0 chip for some reason...
      Tried to compile DUET from the latest tianocore repositories on Git but my attempts were unsuccessful so far (probably I have wrong settings in the development environment - tried the newest Visual Studio 2017 and an older WINDDK, no luck so far.)

      Ultimately buying an USB 3.0/3.1 card could be an option, though I use the on-board USB 3.0 only for (faster) transferring of photos from my SDLR camera to the computer, so buying a dedicated extension card just for this reason would be a waste. And, I would like to see working everything which is supposed to work, anyway. :)

    • Ghaben has written a new post "X58 Chipset with problems to boot off a PCIe connected SSD" 08.11.2017

      Hi, (newby here on this forum)

      Works (almost) like a charm with Samsung EVO 960 512GB on a Gigabyte GA-X58A-UD7 mobo!!! (For the term 'almost', pls look below!)
      Intel SATA2 ports in legacy BIOS are set to RAID(XHD) whereas XHD (eXtreme Hard Drive) is set to 'eXtreme' to get the most out of the Intel end of the mobo and DUET boots with these setting w/o any problem.
      (Besides I also run an old WD SSD with my orig Windows 10 partition plus a Plextor BD optical driver as well as two WD Caviars in RAID1 array on the Intel SATA2 ports as well as another two WD-s in another RAID1 array on the Gigabyte (JMicron) SATA2 ports. RAID1 drives are for data storage/backup.)

      A new Windows10 partition is installed on the NVMe drive following the usual process. The whole system boots fine (via DUET on a USB 2.0 stick) and works as fast as one would expect.

      As for the term 'almost' there is one problem I cannot get over to this date:

      USB 3.0 had to be disabled in legacy BIOS to get DUET working, otherwise the boot process would halt at the red "Welcome to EFI world!" message. Loading the Xhci driver for USB 3.0 didn't make any difference, so there remained two unavoidable consequences:
      1. Windows install had to be done from an USB 2.0 port (no big deal, it lasted a little longer though...)
      2. USB 3.0 port are not seen at all in the fresh Windows install and ports are rendered unusable.

      I tried to load the Xhci driver from startup.nsh but that didn't help either.

      Am I doing something wrong? My startup.nsh looks the following:

      load fs0:\efi\drivers\nvmexpressdxe-64.efi
      load fs0:\EFI\Drivers\XhciDxe-64.efi
      map -r
      fs1:\efi\boot\bootx64.efi

      Should I perhaps try loading the Xhci driver differently (like to fsX, where X is not 0)?

      Is there a way at all to get my onboard USB 3.0 ports working properly (in Windows) or I should snap in a USB 3.1 extension card, perhaps? (I have no intention for booting from an USB 3.0 port, my next step is to create a boot partition on one of my RAID1 arrays. For now, I'm content with booting from the USB 2.0 stick.)

      Many thanks for any help!

Recipient
Ghaben
Subject:


text:
{[userbook_noactive]}


Xobor Forum Software von Xobor