Voodooprojects
Chameleon => General Discussion => Topic started by: gds on May 22, 2010, 06:55:13 PM
-
hi all
i have a gigabyte UD7 with i7 980X, 9800GT and 6Go of G skill
straight after to click on the logo of install dvd i have this message: failed to read boot sector from bios device 100h error =1
after: "starting darwin x86_64" and the computer reboot automatically!
here the video: sorry it is not a good one, but can help i think!
http://img94.imageshack.us/img94/2748/imag0003.mp4
i use chameleon 2 RC4
i tried many changes in bios and nothing change :(
if anyone has some ideas please feel free to write it here :D
ps: i use this method to install chameleon: http://efixusers.com/showthread.php?t=768
many people have the save configuration and no pbs with them!!!
thx a lot
-
I also see "failed to read boot sector from bios device 100h error =1" but it works anyway. I've seen reports from other people as well seeing this mysterious message, on perfectly working systems.
I don't think it's anything to worry about and I don't think it's related to your instant reboot. Most likely something went wrong when you installed Chameleon but it could be several things, it's not possible to tell what went wrong just from the information you've given. And the guide you followed is not much help either, who knows if you followed it to the letter.
I don't like it when people post guides and then say "please don't ask me for technical support".
-
thx
the reboot happens when it is written: starting darwin x86_64
also i tried with an efix 1.1 and the same pbs!
very strange...
But for sure this configuration is ok for chameleon and other!
i will see
-
Guys, I also wanted to confirm that I get this error on my mobo, when in -v (verbose) mode, but the thing is that I got it in the past, using Chameleon 2 RC4 but also getting it now, using AsereBLN 1.1.9 too... it has to be something in the original code.
What could it be, though? Is the bootloader looking for an MBR partition? I have GUID. Is it looking for PATA device? I have SATA only. Did anyone manage to find an answer to this?
Of course, this is a displayed message--doesn't affect operation at all.
-
I know that message... almost forgot it :) it's harmless.
Device 100h is a ramdisk (rd) (http://forge.voodooprojects.org/p/chameleon/source/tree/HEAD/trunk/i386/libsaio/sys.c#L96); the booter throws the message if there's no ramdisk mounted, when tries to check rd(0,0)/Extra... here (http://forge.voodooprojects.org/p/chameleon/source/tree/HEAD/trunk/i386/libsaio/stringTable.c#L650). I found the message when testing some code changes; it was there all the time, just hidden by that brief moment after pressing Enter to boot, when the screen gets dark before verbose kicks in.
Why some of you guys see the message and others don't, must be related with the way the boot process flows on you configuration!?
We can also get it while booting after unmounting a ramdisk.
-
Dear Azimutz, thank you for taking the time to clarify this issue. In your experience, do you think this is some code bug/residue or a normal functionality but with "poorer" code check as to when the error should be displayed?
At least us people now know that the brief text "Failed to read boot sector from BIOS device 100h error = 1" is not really an error ;D
I know that message... almost forgot it :) it's harmless.
Device 100h is a ramdisk (rd) (http://forge.voodooprojects.org/p/chameleon/source/tree/HEAD/trunk/i386/libsaio/sys.c#L96); the booter throws the message if there's no ramdisk mounted, when tries to check rd(0,0)/Extra... here (http://forge.voodooprojects.org/p/chameleon/source/tree/HEAD/trunk/i386/libsaio/stringTable.c#L650). I found the message when testing some code changes; it was there all the time, just hidden by that brief moment after pressing Enter to boot, when the screen gets dark before verbose kicks in.
Why some of you guys see the message and others don't, must be related with the way the boot process flows on you configuration!?
You can also get it while booting after unmounting a ramdisk.
-
Konsti, in my little experience i'd say that this either got unnoticed or it was ignored, as it's just a warning message.
There's another rd(0,0) check here (http://forge.voodooprojects.org/p/chameleon/source/tree/HEAD/trunk/i386/boot2/drivers.c#L185), when loading drivers; the "if" statement prevents the message, as the path is only checked if the statement is true (there's a ramdisk mounted), else it's ignored.
So, you be the judge :)
All i can say is, i don't have the knowledge to fit that "if" statement on the function that issues the message (loadOverrideConfig). That stuff uses a loop and i hate loops >:( they are not noob friendly :P kidding.. but true, at least to me atm.
-
Dear Azimutz thanks again for explaining. I see in your signature you post RC5 versions of Chameleon (for "testing").
Do you know if RC5 has fixed this error, or if the code has been indeed improved and we don't get the error unless it's necessary? Just speculating...
Konsti, in my little experience i'd say that this either got unnoticed or it was ignored, as it's just a warning message.
There's another rd(0,0) check here (http://forge.voodooprojects.org/p/chameleon/source/tree/HEAD/trunk/i386/boot2/drivers.c#L185), when loading drivers; the "if" statement prevents the message, as the path is only checked if the statement is true (there's a ramdisk mounted), else it's ignored.
So, you be the judge :)
All i can say is, i don't have the knowledge to fit that "if" statement on the function that issues the message (loadOverrideConfig). That stuff uses a loop and i hate loops >:( they are not noob friendly :P kidding.. but true, at least to me atm.
-
Konsti, this stuff is not fixed on RC5. I have it fixed on the booter i use, but that's because i've been playing with a "different" search algorithm to load files, one that doesn't uses loops and has that "if" statement. That's how i found the message and were it came from. You shouldn't worry to much about it! :)
By the way, those builds i have on my signature have no changes at all to the original code! I mention they are for "testing" just because there's no official RC5 release. They are meant for people that don't know how to compile from source.
-
Konsti, this stuff is not fixed on RC5.
I have an idea how to fix it at low level. I'll do it when i get back later this evening :)
-
Looking forward to see what your cooking :)
-
Looking forward to see what your cooking :)
Bon appetit! :)
http://forge.voodooprojects.org/p/chameleon/source/commit/264/
-
Dear zef and other members, I have to thank you for your work, I guess we will now wait for a courageous guy to compile it and release it as newer RC5 version? Is this a final code that you're submitting, zef? Are we expecting to see it implemented? 8)
EDIT: Dear Azimutz will you perhaps include this fix in your next build/compilation that you offer in your signature?
-
Konsti, going to check now what Zef cooked up :) still didn't checked the repo today.
Will update this post later....
Chefe Zef, the meal was delicious :) thanks for the recipe.
You just missed removing a check on drivers.c, loadDrivers.
That's it, nice job!
-
Chefe Zef, the meal was delicious :) thanks for the recipe.
You just missed removing a check on drivers.c, loadDrivers.
That's it, nice job!
Hehe :)
The the check in drivers.c is on purpose. The first extension loading attempt starts on rd(0,0)/Extra if it's not redirected to bt(0,0).
-
The the check in drivers.c is on purpose. The first extension loading attempt starts on rd(0,0)/Extra if it's not redirected to bt(0,0).
Yeah, you're right. I'm so used to the search algo i use that i forgot that detail :) have to commit that stuff.
-
Dear zef, Azimutz, thank you for taking time to check and fix/improve this error/feature :lol:
Please let us know when you submit it to the repo and it's officially approved and also, Azimutz, when you compile a new RC with this fix in it--to test and enjoy!
EDIT: I am currently using AsereBLN 1.1.9 bootloader; last I read, it seems that the Chameleon team was expecting Asere (from EFi-X) to release the memory detection module, if I'm not mistaken; is this latest RC5 (including boot error fix) surpassing AsereBLN 1.1.9? I plan to use it on my new Core i7-860 mobo...
-
Dear zef, Azimutz, thank you for taking time to check and fix/improve this error/feature :lol:
Please let us know when you submit it to the repo and it's officially approved and also, Azimutz, when you compile a new RC with this fix in it--to test and enjoy!
EDIT: I am currently using AsereBLN 1.1.9 bootloader; last I read, it seems that the Chameleon team was expecting Asere (from EFi-X) to release the memory detection module, if I'm not mistaken; is this latest RC5 (including boot error fix) surpassing AsereBLN 1.1.9? I plan to use it on my new Core i7-860 mobo...
Dear konsti,
You can follow the recent commits here:
http://forge.voodooprojects.org/p/chameleon/source/changes/HEAD/
I think the current trunk version is already gives you all functions (and more) what Asere's (abandoned?) closed source booter offers.
-
Konsty,
check the commit log like Zef showed you, than check my signature; if you don't find the latest revision there,
it's either because i still didn't had time to update it, or the latest revision it's not as stable as the one i have posted :)
I will keep this until there's a new release.
Just don't forget that, if you're using anything older than rev 186, you should do a complete install!