GA-890GPA-UD3H boot problems

[Bad2theBone]

Often there are problems when IDE and SATA are mixed on the one board. I think it would be worth trying a SATA optical drive and disconnect the IDE ones.

Don't have a SATA ODD, but I could just boot without the ODDs connected to see if that changes things.

[Dark Mantis]

Well that would be the next best thing.

[Bad2theBone]

Well that would be the next best thing.

Just tried first removing 3 of my harddrives which did not change anything which was something Gigabyte support wanted me to do. And then I tried diconnecting both ODDs, also no change just sat there without getting to the prompt for passPhrase.

[Christoph]

ohhhhhhhhh


ok

now we are getting somewhere, you gonna have to install everything again

the thing here is Fedora's actually breaking everything up, this happened to me twice

you gonna have to Install first Fedora with Grub to handle the installation of Windows


I tried installing first Windows and then Fedora which everything was working fine at the beginning, but (this is just my guess) in some point along the way Fedora recognize the installation of windows and try to handle it from the Grub and breaking up the MBR written first to the motherboard by windows

[babdi]

Is your BIOS version FF ?.

[Bad2theBone]

Is your BIOS version FF ?.

Yep, updated a couple of weeks ago.

[Bad2theBone]

ohhhhhhhhh


ok

now we are getting somewhere, you gonna have to install everything again

the thing here is Fedora's actually breaking everything up, this happened to me twice

you gonna have to Install first Fedora with Grub to handle the installation of Windows


I tried installing first Windows and then Fedora which everything was working fine at the beginning, but (this is just my guess) in some point along the way Fedora recognize the installation of windows and try to handle it from the Grub and breaking up the MBR written first to the motherboard by windows

Uhh,,, Windows does not come into play in my case, as I do not have it installed, strictly Fedora 14 lives all alone on HDD and that's the way I plan on keeping it. I believe I mentioned Windows on an earlier post just after starting communicating with Gigabyte Support. They at first insisted that I install windows and see if all works at that point and that's as far as they were going to go. When I came back with the fact that the newest version on Windows I had in my possession (if I could find it) was Win2K and I had no intention of spending $200.00 just for Windows, not on disability income. I told them I'd rather put my money into better hardware such as Gigabyte than in software that chokes you. They are now on daily communique with me.

[Christoph]

my bad


this is really strange

did you updated Fedora or installed some application before the problem?


I just tried Fedora 14 for a few hours after get it to install, so didn't get to know it quite well

is that the latest Kernel for Fedora? is it stable? you don't know if it has any known bugs?


have you check this post?

http://forums.fedoraforum.org/showthread.php?p=1432695

[Bad2theBone]

my bad


this is really strange

did you updated Fedora or installed some application before the problem?


I just tried Fedora 14 for a few hours after get it to install, so didn't get to know it quite well

is that the latest Kernel for Fedora? is it stable? you don't know if it has any known bugs?


have you check this post?

http://forums.fedoraforum.org/showthread.php?p=1432695

I could try 2.6.35.9-64 as that is still on my drive, but I don't think that that is my problem as I would think that would mean I would be able to boot from the Install DVD or LiveCD for F 14 or even F 13. I am currently running 2.6.35.10-74.

[Christoph]

and what kernel does it have your live cd?


my ubuntu server does the exact thing with kernel 2.6.35-24

but if I boot with 2.6.35-22 it works perfectly

[Bad2theBone]

and what kernel does it have your live cd?


my ubuntu server does the exact thing with kernel 2.6.35-24

but if I boot with 2.6.35-22 it works perfectly

Whichever was the current version for Fedora 14 when it was first released. I can check it tomorrow and let you know. I had also tried a LiveCD for Fedora 13 which I believe was a 2.6.33 -xx and got the same results. I may try downloading Ubuntu's LiveCD and see if the problem goes away. All of my Ubuntu and other distros are probably too old for this MoBo as the chipset came out last March. I did have a RescueCD which is based on Knoppix that was within the last 9 months and that gave me similar results.

It'll be easier to test this on the fly later tomorrow when I get my 35ft DVI-HDMI cable from MonoPrice so I don't have to be moving my TV back and forth to hook up to my PC.

[Christoph]

ok

take your time to make it easy

we'll be here

[Bad2theBone]

Latest Update.

A friend/acquaintance brought up a copy of both the 32bit and 64bit Win7Pro. We installed 1st the 32Bit on a spare drive and that seemed to work with booting the HD5770 and onboard disabled. We then installed the 64bit and on the 1st reboot from hdd it froze. Later I tried at Gigabyte's support request booting with just the one hdd (which is the way I had been, I wasn't going to take the chance of Win7 taking over control of my other drives), removing at least 1 ODD which I just removed both, removing 1 stick of RAM, and disconnecting all fans except CPU. When I booted that way I got the infamous BSOD. I am able to run 32bit versions of either WIN or Linux. If I boot 64bit through the onboard video, I can use the PCIe card once logged in. I still believe that it is hardware and the failure occurs on initializing it full 64bit. It can be initialized after the boot in a 64bit environment.

[Dark Mantis]

When you installed the 64 bit version did you change the HPET in the BIOS to 64 ?

What was the Stop Code on the BSOD ?

[Bad2theBone]

When you installed the 64 bit version did you change the HPET in the BIOS to 64 ?

What was the Stop Code on the BSOD ?

HPET enabled, also used in Linux kernels 2.6 and above, it's also the default setting in the BIOS for this board.

STOP: c000021a [FATA7 System Error]
The windows subsystem process terminated unexpectedly with a status of 0xc0000005 (0x77163a37 0x0021e990)
The system has been shut down.

That's with just one hdd, no optical drives, 1 stick of memory and the PCIe x16 video card. On board video disabled.