Re: System can not boot, seems can not find right partition after add new label

2008-03-15 Thread Kemian Dang
I have reinstall the system, just done the gnome from ports... On 15/03/2008, Nikola Lečić <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: RIPEMD160 > > > On Sat, 15 Mar 2008 22:16:58 + > > "Kemian Dang" <[EMAIL PROTECTED]> wrote: > > > > Problem is the boot partition

Re: System can not boot, seems can not find right partition after add new label

2008-03-15 Thread Nikola Lečić
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 On Sat, 15 Mar 2008 22:16:58 + "Kemian Dang" <[EMAIL PROTECTED]> wrote: > Problem is the boot partition can not be found. > I burned a install cdm using it I find I have set ad4s2 to be > bootable, so I changed it back. > But this time, the

Re: System can not boot, seems can not find right partition after add new label

2008-03-15 Thread Kemian Dang
Thanks for reponse, Problem is the boot partition can not be found. I burned a install cdm using it I find I have set ad4s2 to be bootable, so I changed it back. But this time, the system said I have missing something on boot... I do not want to waste too much time on it, as I can have the back u

Re: System can not boot, seems can not find right partition after add new label

2008-03-15 Thread Nikola Lečić
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 On Sat, 15 Mar 2008 11:26:52 + "Kemian Dang" <[EMAIL PROTECTED]> wrote: [...] > I can not remember whether I do something stupid, I just dd > if=/dev/zero of=/dev/ad4s2 to write zero, then when I want to use > bsdlabel to create new slice,

System can not boot, seems can not find right partition after add new label

2008-03-15 Thread Kemian Dang
Hi,there: A short story is: When I boot my laptop, the screen tells me "invalida partition" and then give me the prompt "default: 0:ad(0,a)/boot/kernel/kernel". My FreeBSD / partition is at /dev/ad4s3a, so I tried "4:ad(3,a)/boot/kernel/kernel", but without lucky. Could someone tell me how should

Re: can not boot

2006-04-18 Thread Max N. Boyarov
> "dp" == dharam paul writes: dp> My freebsd box reports dp> Code: dp> libexec/Id_elf.so.1:shared object "libedit.so.4" not dp> found by "-sh" dp> Enter full path name or RETURN for (bin/sh): dp> When I press enter , same error is repeated. dp> Any remedy please? if you have res

can not boot

2006-04-18 Thread dharam paul
My freebsd box reports Code: libexec/Id_elf.so.1:shared object "libedit.so.4" not found by "-sh" Enter full path name or RETURN for (bin/sh): When I press enter , same error is repeated. Any remedy please? Regards __

Re: I can not boot my FreeBSD-5.2 partition, please help

2004-01-16 Thread Dany
Using SBM "Smart Boot Manager" http://btmgr.sourceforge.net/ I was able to boot my FreeBSD 5.2R out of the box which is located on the upper part of the disk (40G to 80G). It uses MBR for installation, so you can boot from a DOS floppy. Backup your existing MBR and isntall this nice tool. Dan

Re: I can not boot my FreeBSD-5.2 partition, please help

2004-01-16 Thread Dany
Using SBM "Smart Boot Manager" http://btmgr.sourceforge.net/ I was able to boot my FreeBSD 5.2R out of the box which is located on the upper part of the disk (40G to 80G). It uses MBR for installation, so you can boot from a DOS floppy. Backup your existing MBR and isntall this nice tool. Dan

Re: I can not boot my FreeBSD-5.2 partition, please help

2004-01-16 Thread Hanspeter Roth
On Jan 16 at 12:30, Juan Rodriguez Hervella spoke: > Hello, > > I've got a 40 GBytes hard disk on an old Pentium MMX 266 MHz. > The first time I plugged it into the motherboard my BIOS didn't recognize > the drive, but fortunately there is a jumper that reduces the size of the > disk to 32 GByt

I can not boot my FreeBSD-5.2 partition, please help

2004-01-16 Thread Juan Rodriguez Hervella
Hello, I've got a 40 GBytes hard disk on an old Pentium MMX 266 MHz. The first time I plugged it into the motherboard my BIOS didn't recognize the drive, but fortunately there is a jumper that reduces the size of the disk to 32 GBytes, and that's enough for my BIOS at this moment. So I've got som