-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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 _at_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_freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGeBPcHNAJ/fLbfrkRAveBAKCCWHt/yudZf8LbEeFygT0XHLmHCwCgk/vh LKkBwHYfufqBiYfo4xPKsck= =iyft -----END PGP SIGNATURE-----Received on Tue Jun 19 2007 - 15:35:27 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:12 UTC