Current does not boot - BIOS problem?

Niki Denev ndenev at
Wed Jun 20 13:33:28 UTC 2007

Hash: SHA1

Niki Denev wrote:
> Marinos Ilias wrote:
>> Hello list,
>> Yesterday I upgraded to latest -CURRENT.Although the build and installing was successful, the system refuses to boot.It stops at the boot sequence with the following error:
>> Can't work out which disk we are booting from.
>> Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0:
>> panic: free: guard1 fail @0x5195c from /home/ncvs/src/sys/boot/i386/loader/../../common/module.c:957
>> --> Press a key on the console to reboot <--
>> I cannot figure out what kind of problem is it.It's weird that the system cannot find which disk to boot from.I didn't have such problems at past and I run CURRENT at this desktop for over a year.Also I want to add that I cannot either boot the kernel.old , as it hangs when I try :
>> kernel /boot/kernel.old/kernel
>> at boot prompt.
>> If you have any ideas, you're welcome!
>> Thank you.
>> Ilias Marinos
>> _______________________________________________
>> freebsd-current at mailing list
>> To unsubscribe, send any mail to "freebsd-current-unsubscribe at"
> I have exactly the same problem with recent -current sources with my
> ThinkPad X31. I had to tell the loader to boot /boot/loader.old
> and then i copied loader.old to loader and since then i have no
> problems, but i do this after each rebuild. So, it's clearly something
> wrong with the loader, but i wansn't able to find something suspicious
> looking at recent commit logs
> Niki

My other laptop a Sony VAIO PCG-U3 does not exhibit this problem,
only the ThinkPad chokes on the new loader.


Version: GnuPG v1.4.7 (FreeBSD)
Comment: Using GnuPG with Mozilla -


More information about the freebsd-current mailing list