- Joined
- Jan 19, 2010
- Messages
- 241
No, you can also put it on a USB Stick/HD and use Qflash from Bios startupadamsmasher said:Does the BIOS update need to be installed from windows?
No, you can also put it on a USB Stick/HD and use Qflash from Bios startupadamsmasher said:Does the BIOS update need to be installed from windows?
longtom said:No, you can also put it on a USB Stick/HD and use Qflash from Bios startupadamsmasher said:Does the BIOS update need to be installed from windows?
Actually, no, I'm not "too scared" to update it. I've already updated my BIOS from F3 to F5. Also, it really isn't adding functionality. It's only really needed if you want your hackintosh to be more vanilla.thelostswede said:And in this specific case it obviously adds something that would improve the functionality of your hackingtosh, but you're too scared to update to it?
From Gigabyte's website:thelostswede said:There's nothing missing, it's just not what they've deemed to be final versions, as they're still tweaking a few things here and there.
Gigabyte's Website said:What is a BETA?
BETA describes a new version that is reliable yet may not include all the features of the final product. During this phase we are previewing new features and gathering customer input to insure our product provides the best experience possible.
Yea Gigabyte's boards have two BIOS chips, but what if when you flash, something in both of the BIOS's gets screwed up? Or am I just misunderstanding DualBIOS? IMO, the less times I have to flash my BIOS, the better.thelostswede said:I'm not meaning to be rude here, but you're being overly cautious about something that won't cause any damage. Even more so as Gigabyte boards have a pair of BIOS chips, so even if something would go wrong, there's a backup BIOS on the board.
Cantello said:edit: Ok, works now after removing and re-installing AppleHDA.kext (10.6.2). However, I still get numerous errors pertaining to this kext during the boot process, is this normal?
Jan 25 23:16:57 localhost kernel[0]: Not loading kext com.apple.driver.AppleHDAController - not found and kextd not available in early boot.
--- (deleted stuff)
Jan 25 23:16:58 Home kernel[0]: Sound assertion "0 == pciVendorProductID" failed in "/SourceCache/AppleHDA/AppleHDA-179.1.4/AppleHDAController/AppleHDAController.cpp" at line 2682 goto Exit
--- (deleted stuff)
Jan 25 23:17:07 Home kernel[0]: Sound assertion "0 != result" failed in "/SourceCache/AppleHDA/AppleHDA-179.1.4/AppleHDA/AppleHDAWidget.cpp" at line 3641 goto handler
Jan 25 23:17:07 Home kernel[0]: Sound assertion "0 != widget->setUnsolicited ( true )" failed in "/SourceCache/AppleHDA/AppleHDA-179.1.4/AppleHDA/AppleHDACodecGeneric.cpp" at line 989 goto handler
Jan 25 23:17:07 Home kernel[0]: Sound assertion "0 != result" failed in "/SourceCache/AppleHDA/AppleHDA-179.1.4/AppleHDA/AppleHDAWidget.cpp" at line 3641 goto handler
Jan 25 23:17:07 Home kernel[0]: Sound assertion "0 != widget->setUnsolicited ( true )" failed in "/SourceCache/AppleHDA/AppleHDA-179.1.4/AppleHDA/AppleHDACodecGeneric.cpp" at line 989 goto handler
Jan 25 23:17:07 Home kernel[0]: Sound assertion "0 != result" failed in "/SourceCache/AppleHDA/AppleHDA-179.1.4/AppleHDA/AppleHDAWidget.cpp" at line 3641 goto handler
Jan 25 23:17:07 Home kernel[0]: Sound assertion "0 != widget->setUnsolicited ( true )" failed in "/SourceCache/AppleHDA/AppleHDA-179.1.4/AppleHDA/AppleHDACodecGeneric.cpp" at line 989 goto handler
Evildemon989 said:Yea Gigabyte's boards have two BIOS chips, but what if when you flash, something in both of the BIOS's gets screwed up? Or am I just misunderstanding DualBIOS? IMO, the less times I have to flash my BIOS, the better.
Also, next time instead of getting mad by the fact that I am being "too cautious", how about you just inform me of my possible misunderstandings because addressing the situation like you just did, just makes you sound like an idiot.
Alright, that does make sense.thelostswede said:Yes, you misunderstood how dual BIOS works, as you only flash the primary BIOS chip, not the secondary. The second chip is just there as a backup and retains the original BIOS.
Even if they are still "tweaking and a few things here and there", isn't it feasible that there could still be a few stability issues that people who have install the BIOS update have found that the internal testers didn't? It's not out of the realm of possibility.And thank you for calling me names, I wasn't mad, I just think you should do some research before you go and post things, especially when it's something you obviously don't know enough about.