Re: boot problems / redirection unexpected
Zbigniew Szalbot wrote: hello, Trying to boot 6.3. There seems to be some problem with /etc/rc.subr it gives me some message about redirection unexpected. I am trying to copy this file form a back-up to /etc but when I do that it says: read-only file system. I should add that I am operating as root (could not go into multiuser). What are my options now? How do I make files in /etc writeable so that I can copy the file from backup? Many thanks! Zbigniew Szalbot __ So it seems your problems were far more than not getting a GENERIC kernel... I guess this is the machine where you merged the changes of the conf files? If you do have a backup, reboot into single user mode and do something like: mount -o rw / This will remount you root partition read-write and you will be able to copy the backup back. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: boot problems / redirection unexpected
Hello, 2008/1/21, Manolis Kiagias [EMAIL PROTECTED]: Zbigniew Szalbot wrote: hello, Trying to boot 6.3. There seems to be some problem with /etc/rc.subr it gives me some message about redirection unexpected. I am trying to copy this file form a back-up to /etc but when I do that it says: read-only file system. I should add that I am operating as root (could not go into multiuser). What are my options now? How do I make files in /etc writeable so that I can copy the file from backup? Many thanks! Zbigniew Szalbot So it seems your problems where far more than not getting a GENERIC kernel... I guess this is the machine where you merged the changes of the conf files? If you do have a backup, reboot into single user mode and do something like: mount -o rw / This will remount you root partition read-write and you will be able to copy the backup back. Yes, thanks I was able to do that. However, there seem to be some other problems so I am right now looking at what mess I have and praying I can revert it somehow :) Thanks! Zbigniew Szalbot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual boot problems (RESOLVED)
On Tue, 13 Feb 2007 19:46:18 -0800 Garrett Cooper [EMAIL PROTECTED] wrote: RW wrote: On Tue, 13 Feb 2007 21:51:52 -0500 (EST) Questions [EMAIL PROTECTED] wrote: On Tue, 13 Feb 2007 20:44:03 -0500 (EST) Questions [EMAIL PROTECTED] wrote: However, when I try FreeBSD/amd64, grub won't compile (it's architecture is forced to i386 only in the Makefile. I haven't dug into why, but I'm confident there is a reason. Obviously, grub becomes a non-option. Gag has the same limitation of being i386 only. I'm not sure why gag is i386 only, all it does is install a binary floppy disk ISO. You can also install it from many Linux live CDs. Once it's installed it's independent of the original installation medium. Probably because architecture stuff and bit length in 32-bit is half :)? Instruction set's a bit different too. There are some new features in the new Intel processors like overflow protection, etc, so I wouldn't doubt there are differences in ISA at the assembler level. No, at the point Gag runs, the CPU isn't even 32-bit, let alone 64-bit. The port just extracts a precompiled ISO file. It won't run on anything that isn't PC compatible, so it isn't actually platform independent, but it should run on any CPU with a real mode. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual boot problems
Howdy, Hello, This weekend I purchased a laptop with a core2duo processor. The laptop came with windows Vista premier. Due to some applications that I require, removing Vista and installing FreeBSD is not an issue. (Please leave the Vista/Microsoft flames at the door) When I install FreeBSD/i386, I can then install grub (instead of FreeBSD's bootloader) and I can have grub chainload the Vista bootloader. All works fine. However, when I try FreeBSD/amd64, grub won't compile (it's architecture is forced to i386 only in the Makefile. I haven't dug into why, but I'm confident there is a reason. Obviously, grub becomes a non-option. Gag has the same limitation of being i386 only. Do you really need to use Grub to replace the FreeBSD MBR? I haven't had my hands on Vista yet - in no hurry either - but I think it should boot Vista OK. I've use it for several other MS versions from Win-95 - Win 2K - Xp-Pro and it works just fine. I haven't heard that any low level boot code (at the level the MBR works) has been changed in Vista, though I haven't been out looking yet either. I would be interested to know if they have changed the BIOS to MBR to boot sector handoff specs if something has happened to it. jerry Has anyone successfully been able to dual boot Vista + FreeBSD/amd64? I'm eager to have both on the laptop, however I've spent the entire weekend scouring google, and reinstalling both freebsd (i386 and amd64 versions) and have reinstalled vista at least 8 times. I've already thought about using the windows bootloader, but Vista has done away with NTLDR/boot.ini in favor of BCD. editing BCD seems non-trivial at best, and frankly I'm getting tired of reinstalling OS's; so I thought I'd ask around instead of reinventing the wheel. Thank you in advance for any advice, or input. Also thanks in advance for leaving the irrelevant MS hatred out of the thread. - Jeff Palmer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual boot problems
On Wed, Feb 14, 2007 at 12:04:57PM -0500, Jeff Palmer wrote: Do you really need to use Grub to replace the FreeBSD MBR? I haven't had my hands on Vista yet - in no hurry either - but I think it should boot Vista OK. I've use it for several other MS versions from Win-95 - Win 2K - Xp-Pro and it works just fine. I haven't heard that any low level boot code (at the level the MBR works) has been changed in Vista, though I haven't been out looking yet either. I would be interested to know if they have changed the BIOS to MBR to boot sector handoff specs if something has happened to it. jerry Jerry, I can confirm the FreeBSD bootloader does *not* work with vista.from my research, it appears vista now writes some kind of signature or hash into the MBR for the bitlocker technology.if you modify the MBR with a bootloader (that doesn't chainload) then the checksum/hash doesn't match, and vista complains that the drive/data is corrupted. It will not boot. Geez. Damn cretins. Just another attempt to jerk the user around and strongarm control the use of the system. Thanks for the info. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Dual boot problems
Hello, This weekend I purchased a laptop with a core2duo processor. The laptop came with windows Vista premier. Due to some applications that I require, removing Vista and installing FreeBSD is not an issue. (Please leave the Vista/Microsoft flames at the door) When I install FreeBSD/i386, I can then install grub (instead of FreeBSD's bootloader) and I can have grub chainload the Vista bootloader. All works fine. However, when I try FreeBSD/amd64, grub won't compile (it's architecture is forced to i386 only in the Makefile. I haven't dug into why, but I'm confident there is a reason. Obviously, grub becomes a non-option. Gag has the same limitation of being i386 only. Has anyone successfully been able to dual boot Vista + FreeBSD/amd64? I'm eager to have both on the laptop, however I've spent the entire weekend scouring google, and reinstalling both freebsd (i386 and amd64 versions) and have reinstalled vista at least 8 times. I've already thought about using the windows bootloader, but Vista has done away with NTLDR/boot.ini in favor of BCD. editing BCD seems non-trivial at best, and frankly I'm getting tired of reinstalling OS's; so I thought I'd ask around instead of reinventing the wheel. Thank you in advance for any advice, or input. Also thanks in advance for leaving the irrelevant MS hatred out of the thread. - Jeff Palmer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual boot problems
On 2/13/07, Questions [EMAIL PROTECTED] wrote: Hello, This weekend I purchased a laptop with a core2duo processor. The laptop came with windows Vista premier. Due to some applications that I require, removing Vista and installing FreeBSD is not an issue. (Please leave the Vista/Microsoft flames at the door) When I install FreeBSD/i386, I can then install grub (instead of FreeBSD's bootloader) and I can have grub chainload the Vista bootloader. All works fine. However, when I try FreeBSD/amd64, grub won't compile (it's architecture is forced to i386 only in the Makefile. I haven't dug into why, but I'm confident there is a reason. Obviously, grub becomes a non-option. Gag has the same limitation of being i386 only. to make sure i understand this correctly, you can install FreeBSD (assuming 6.1-RELEASE)/amd64 on your system but am having problems compiling grub in this environment from the ports tree? it looks like grub may only build correctly on i386 systems, but you may be able to define your cpu as a 32bit arch in /etc/make.conf while trying to build grub to see if that works. i've never had to do this though, but it's worth a shot. -pete -- ~~o0OO0o~~ Pete Wright www.nycbug.org NYC's *BSD User Group ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual boot problems
On Tue, 13 Feb 2007 20:44:03 -0500 (EST) Questions [EMAIL PROTECTED] wrote: However, when I try FreeBSD/amd64, grub won't compile (it's architecture is forced to i386 only in the Makefile. I haven't dug into why, but I'm confident there is a reason. Obviously, grub becomes a non-option. Gag has the same limitation of being i386 only. I'm not sure why gag is i386 only, all it does is install a binary floppy disk ISO. You can also install it from many Linux live CDs. Once it's installed it's independent of the original installation medium. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual boot problems
On 2/13/07, Questions [EMAIL PROTECTED] wrote: Hello, This weekend I purchased a laptop with a core2duo processor. The laptop came with windows Vista premier. Due to some applications that I require, removing Vista and installing FreeBSD is not an issue. (Please leave the Vista/Microsoft flames at the door) When I install FreeBSD/i386, I can then install grub (instead of FreeBSD's bootloader) and I can have grub chainload the Vista bootloader. All works fine. However, when I try FreeBSD/amd64, grub won't compile (it's architecture is forced to i386 only in the Makefile. I haven't dug into why, but I'm confident there is a reason. Obviously, grub becomes a non-option. Gag has the same limitation of being i386 only. to make sure i understand this correctly, you can install FreeBSD (assuming 6.1-RELEASE)/amd64 on your system but am having problems compiling grub in this environment from the ports tree? it looks like grub may only build correctly on i386 systems, but you may be able to define your cpu as a 32bit arch in /etc/make.conf while trying to build grub to see if that works. i've never had to do this though, but it's worth a shot. -pete -- ~~o0OO0o~~ Pete Wright www.nycbug.org NYC's *BSD User Group ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] !DSPAM:4,45d26f9c8487852311823! Thanks for the fast reply, Pete. It's actually 6.2-RELEASE/amd64, and I have tried compiling grub with the pentium3, and pentium4 CPUTYPE's in /etc/make.conf, to no avail. Sadly, it seems as though vista has code in the MBR now, that seems to be part of the bitlocker stuff. FreeBSD's standard bootloader interferes with it, causing Vista to give a error message about files being corrupted. Maybe there is a simple (to the MBR guru types) that could be implemented into the fbsd bootloader. -Jeff Palmer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual boot problems (RESOLVED)
On Tue, 13 Feb 2007 20:44:03 -0500 (EST) Questions [EMAIL PROTECTED] wrote: However, when I try FreeBSD/amd64, grub won't compile (it's architecture is forced to i386 only in the Makefile. I haven't dug into why, but I'm confident there is a reason. Obviously, grub becomes a non-option. Gag has the same limitation of being i386 only. I'm not sure why gag is i386 only, all it does is install a binary floppy disk ISO. You can also install it from many Linux live CDs. Once it's installed it's independent of the original installation medium. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] !DSPAM:4,45d274028483574158760! To help anyone out who is also attempting to dualboot FreeBSD/amd64 and Vista: here is what I did. Install Vista first. Use the disk manager to create a partition (or resize the partition) to make room for FreeBSD. reboot, and install FreeBSD, installing a standard MBR (the machine will reboot directly into FreeBSD) After back into a fresh FreeBSD, do: sysinstall Configure Distributions lib32 (this installs 32bit compatibility libraries. Now fetch ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.2-release/Latest/grub.tbz (yes, the i386 package) pkg_add grub.tgz It will now work in compatibility mode, and you can use it same as you can with a native FreeBSD/i386. Hope it helps someone! - Jeff Palmer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual boot problems (RESOLVED)
On Tue, 13 Feb 2007 21:51:52 -0500 (EST) Questions [EMAIL PROTECTED] wrote: On Tue, 13 Feb 2007 20:44:03 -0500 (EST) Questions [EMAIL PROTECTED] wrote: However, when I try FreeBSD/amd64, grub won't compile (it's architecture is forced to i386 only in the Makefile. I haven't dug into why, but I'm confident there is a reason. Obviously, grub becomes a non-option. Gag has the same limitation of being i386 only. I'm not sure why gag is i386 only, all it does is install a binary floppy disk ISO. You can also install it from many Linux live CDs. Once it's installed it's independent of the original installation medium. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] !DSPAM:4,45d274028483574158760! To help anyone out who is also attempting to dualboot FreeBSD/amd64 and Vista: here is what I did. Install Vista first. Use the disk manager to create a partition (or resize the partition) to make room for FreeBSD. reboot, and install FreeBSD, installing a standard MBR (the machine will reboot directly into FreeBSD) After back into a fresh FreeBSD, do: sysinstall Configure Distributions lib32 (this installs 32bit compatibility libraries. Now fetch ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.2-release/Latest/grub.tbz (yes, the i386 package) pkg_add grub.tgz It will now work in compatibility mode, and you can use it same as you can with a native FreeBSD/i386. FWIW gag will work without any of that, and will carry on working if you replace the FreeBSD partition. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual boot problems (RESOLVED)
RW wrote: On Tue, 13 Feb 2007 21:51:52 -0500 (EST) Questions [EMAIL PROTECTED] wrote: On Tue, 13 Feb 2007 20:44:03 -0500 (EST) Questions [EMAIL PROTECTED] wrote: However, when I try FreeBSD/amd64, grub won't compile (it's architecture is forced to i386 only in the Makefile. I haven't dug into why, but I'm confident there is a reason. Obviously, grub becomes a non-option. Gag has the same limitation of being i386 only. I'm not sure why gag is i386 only, all it does is install a binary floppy disk ISO. You can also install it from many Linux live CDs. Once it's installed it's independent of the original installation medium. Probably because architecture stuff and bit length in 32-bit is half :)? Instruction set's a bit different too. There are some new features in the new Intel processors like overflow protection, etc, so I wouldn't doubt there are differences in ISA at the assembler level. !DSPAM:4,45d274028483574158760! To help anyone out who is also attempting to dualboot FreeBSD/amd64 and Vista: here is what I did. Install Vista first. Use the disk manager to create a partition (or resize the partition) to make room for FreeBSD. reboot, and install FreeBSD, installing a standard MBR (the machine will reboot directly into FreeBSD) After back into a fresh FreeBSD, do: sysinstall Configure Distributions lib32 (this installs 32bit compatibility libraries. Now fetch ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.2-release/Latest/grub.tbz (yes, the i386 package) pkg_add grub.tgz It will now work in compatibility mode, and you can use it same as you can with a native FreeBSD/i386. FWIW gag will work without any of that, and will carry on working if you replace the FreeBSD partition. Yeah, but grub provides more power in choosing your load options though. Besides, gag has an ugly bootloader screen _.. I only use gag when I'm not afforded a choice with FreeBSD's bootloader and then grub. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
boot problems with FreeBSD, WindowsXP (and Linux)
Hello, I've been having some problems with my computer arising out of an install of FreeBSD 5.4 which I can't seem to solve. First of all, I started with an 80 GB HD partitioned as such: c: 20 GB NTFS d: 20 GB NTFS e: 40 GB FAT I first installed a copy of Ubuntu Linux 4.1 onto the Windows d:. This worked fine, but it was only to get a look at it before putting FreeBSD onto the same partition. My 5.4 installation works fine and I can mount both /dev/ad0s1 and /dev/ad0s3 (NTFS and MSDOS respectively). The problem is that Windows XP not fails to boot. It appears to start but then flashes blue and restarts the computer. Repairing with the Windows disk also causes a reboot and a reinstall would mean overwriting both FreeBSD (which I could reinstall) but more importantly the 40 GB FAT partition which I'd rather not loose. I don't need Windows in fact but my FreeBSD is a work in progress so I'd like to have a copy of Linux to tide me over until everything is up and working. The problem is that all of the Linux distros that I've tried (Fedora 4, SUSE, Mandirva, Ubuntu) have complained about the current partitioning scheme and want to use the entire disk. FreeBSD's fdisk gives the following: Disk name: ad0 FDISK Partition Editor DISK Geometry: 9729 cyls/255 heads/63 sectors = 156296385 sectors (76316MB) OffsetSize(ST) End Name PType Desc Subtype Flags 0 63 62 - 12 unused 0 63 40965687 40965749 ad0s1 4 NTFS/HPFS/QNX 7 40965750 39230730 80196479 ad0s4 8 freebsd 165 80196480 1 80196480 - 12 unused 0 80196481 173501981931499 ad0s2 4 extended DOS 5 81931500 74364885 156296384 ad0s3 4 extended DOS 5 56296385 5103 156301487 - 12 unused 0 Fdisk also complains about incorrect geometry but uses what it considers probably correct. And it says that ad0s2 does not begin on a track boundary. I cannot mount ad0s2 and I feel that it is somehow the problem. What can I do to either correct Windows or install Linux without destroying my 40GB FAT partition (ad0s3)? _ MSN Hotmail : créez votre adresse e-mail gratuite à vie ! http://www.imagine-msn.com/hotmail/default.aspx?locale=fr-FR ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Sparc dual boot problems
Here's the situation The machine is a SUN ULTRA 5 and I have 4 IDE devices. I am new to SUN hardware I know much more about PC's. The first device primary master is the cdrom which Solaris 10 and FreeBSD were successfully installed from. Currently Solaris 10 which is the primary slave is the default boot device. FreeBSD is installed on the primary slave drive. I am used to the FreeBSD install on a PC and during that install it gave time for configuring the boot loader but I can't find it on the recent Sparc FreeBSD edition? During the partition process it says I will have the option to configure the boot loader latter. Right now I can't boot FreeBSD and I have no idea how to configure this machine to make it dual boot? I would like to have Solaris 10 as the primary O/S, FreeBSD as the secondary and Sparc Linux on the third hd. Can you please help? Jason Harback ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sparc dual boot problems
- Original Message - From: jasonharback [EMAIL PROTECTED] To: freebsd-questions@FreeBSD.org Sent: Saturday, January 07, 2006 5:47 AM Subject: Sparc dual boot problems During the partition process it says I will have the option to configure the boot loader latter. Right now I can't boot FreeBSD and I have no idea how to configure this machine to make it dual boot? I would like to have Solaris 10 as the primary O/S, FreeBSD as the secondary and Sparc Linux on the third hd. I don't know if theres a possibility of using a boot loader, but I have multibooted my sparc boxes from the OFW prompt by writing the primary OS into OFW config and booting into other OS's using the ofw prompt (stop-a) and then giving boot command with the disk/cdrom name I want to boot from. I think neither NetBSD or FreeBSD supports a boot loader on Sparc but I'm not 100% sure about that. After trying Slowlaris I'm running all my boxes with BSD's only though. -Reko ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sparc dual boot problems
On Sat, 2006-01-07 at 03:47, jasonharback wrote: Here's the situation The machine is a SUN ULTRA 5 and I have 4 IDE devices. I am new to SUN hardware I know much more about PC's. The first device primary master is the cdrom which Solaris 10 and FreeBSD were successfully installed from. Currently Solaris 10 which is the primary slave is the default boot device. FreeBSD is installed on the primary slave drive. I am used to the FreeBSD install on a PC and during that install it gave time for configuring the boot loader but I can't find it on the recent Sparc FreeBSD edition? During the partition process it says I will have the option to configure the boot loader latter. Right now I can't boot FreeBSD and I have no idea how to configure this machine to make it dual boot? I would like to have Solaris 10 as the primary O/S, FreeBSD as the secondary and Sparc Linux on the third hd. Can you please help? Jason Harback Jason, You don't need to use a boot loader with the U5, just boot to the promt (Stop A). Then just type boot followed by the alias of the slice you want to boot. Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
boot problems
hello , i have already the sameproblem when i boot with freebsd 5.3 since i have had a power cut .The message of the error is : error 16 Iba 191 No /boot/loader FreeBSD/i386 boot Default: 0:ad(0,a)/kernel boot: error 16 Iba 191 No /kernel I have tried boot : /kernel.old but i have No /kernel.old and i don't know how do with the bootonly cd. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: boot problems
it was said: hello , i have already the sameproblem when i boot with freebsd 5.3 since i have had a power cut .The message of the error is : error 16 Iba 191 No /boot/loader FreeBSD/i386 boot Default: 0:ad(0,a)/kernel boot: error 16 Iba 191 No /kernel I have tried boot : /kernel.old but i have No /kernel.old and i don't know how do with the bootonly cd. Hello, The error you are seeing is caused by the boot loader looking in the wrong place for the kernel. Try this command at the boot prompt: boot: 0:ad(0,a)/boot/kernel/kernel My guess is the error you see will change to Invalid Format. I saw your post the other day and cut the power to a 5.3 test box to see if the same thing would happen. It did. I think something happened to your and my systems that prevents the boot loader from recognizing UFS2. Here are the things I have tried so far. I booted into FreeSBIE (www.freesbie.org) and ran fsck to fix the filesystems. The / filesytem reported clean, but /home and /var had amazing numbers of unrecoverable errors and bad blocks. But I still got the Invalid Format error. So I put the drive in another 5.3 system and everything in / _seems_ readable. Right now I am running a surface diagnostic on the drive to see if the platters are damaged. That will not be finished until sometime tomorrow, but so far over half the disk has been checked and reports as undamaged. I will report the results of the completed test. I will run the power outage test several times to see if the same problems appear each time. Those results will be posted when finished. Regards, stheg __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot problems afther reinstall windows
On Tue, Mar 15, 2005 at 07:05:58PM -0500, Jerry McAllister wrote: timeout=10 default=c:\freebsd.bin [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=Microsoft Windows XP Professional /fastdetect /NoExecute=OptIn c:\freebsd.bin=FreeBSD 5 This works for me. I still wonder why the stuff below didn't work. In the past I would do this with /stand/sysinstall. But I don't dare to do this with FreeBSD 5 because of drive geometric warnings. Remember there are two boot blocks, so to speak. There is the MBR that lets you choose which slice to boot. There is only one of those per disk and it lives in sector 0 of the disk. The MBR generally has a standard calling sequence (that the Bios calls) and sets things up to a fairly standard condition and looks for standard appearing boot sectors in slices and makes a standard call to the selected slice's boot sector. Almost any MBR that knows how to recognize a standard boot sector in a slice and lets you choose between them if there are more than one can be used interchangeably. Then there is the boot block with the actual boot loader that starts pulling the OS from the bootable partition. On a multi boot disk there are several - one per each bootable slice and they live in the boot sector of each slice.Those are specific to the OS they are booting. Though their calling sequence is standard, what they have to do to load and start their own OS is not. Is it posible to boot one OS if you only have the MBR? No, you need the boot sector. If you have only that in the first location, you can boot without an full MBR, I think, but not without the boot sector that the MBR loads and jumps to. But its not posible to put the code of the boot sector in the MBR place? (i.e. doesn't fit) I am guessing that you managed to overwrite or damage the MS slice' boot sector while you were doing things, or didn't get it written to the slice properly when you reloaded or something like that. Even though you put the MBR back with FreeBSD's fdisk, did you also make sure that the MS slice had its own boot loader? Anyway you did when you put the MS boot loader back. So it works now. I think the anwser to you question should be no. It booted before I put the MBR back. The previous time I first installed windows and then FreeBSD 5. The difference this time is that I didn't use /stand/sysinstall. This because I would get into serious troubel. (I never found out how to force the right geometry) So I was thinking maybe sysinstall does something (like copy the MBR to the second boot location) that I didn't do manualy. I think you are using MBR for boot sector. I think you mean by word and not on disk. The MBR is what goes in sector 0 of the disk itself. The boot sector/record/block goes in the first sector of the slice. The MBR lets you pick the slice you want to boot and then loads its boot sector/block/record and jumps to it in a standard location. MBR = /boot/boot0 (a copy of it) boot sector = /boot/boot1 What I was thinking is: Now windows overwrites the MBR. And I was thinking it would put the boot sector in the place of MBR. If this is the case then windows looses the capability to boot. -- Alex Please copy the original recipients, otherwise I may not read your reply. WWW: http://www.kruijff.org/alex/FreeBSD/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot problems afther reinstall windows
Windows was able to boot afhter I installed it. I never touched boot.ini. The content would have been: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=Microsoft Windows XP Professional /fastdetect /NoExecute=OptIn I now use a different solution. Instead of the freebsd bootloader (boot0). I now use the windows bootloader. I copied boot1 to c:\freebsd.bin. Then modified windows boot.ini as follow: [boot loader] timeout=10 default=c:\freebsd.bin [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=Microsoft Windows XP Professional /fastdetect /NoExecute=OptIn c:\freebsd.bin=FreeBSD 5 This works for me. I still wonder why the stuff below didn't work. In the past I would do this with /stand/sysinstall. But I don't dare to do this with FreeBSD 5 because of drive geometric warnings. On Tue, Mar 15, 2005 at 02:12:46AM +, Jason Henson wrote: What is in your windows boot.ini file? On 03/14/05 11:13:49, Alex de Kruijff wrote: Hi, I've recently reinstalled windows. Windows removes the MBR as you know. So ather I installed it I set partion 1 (FreeBSD) active and rebooted. Then I followed the handbook and did fdisk -B -b /boot/boot0 ad0. Now I get the orginal screen afther booting. Only it beeps when I press F2 (Windows). I can mount the second partion on FreeBSD, but cant boot. Any ideas to what I'm missing here? # fdisk *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=484521 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=484521 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 20971377 (10239 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 104/ sector 63 The data for partition 2 is: sysid 12 (0x0c),(DOS or Windows 95 with 32 bit FAT (LBA)) start 20980890, size 20948760 (10228 Meg), flag 80 (active) beg: cyl 1023/ head 0/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 3 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 41942880, size 446454288 (217995 Meg), flag 80 (active) beg: cyl 1023/ head 210/ sector 1; end: cyl 1023/ head 80/ sector 63 The data for partition 4 is: UNUSED -- Alex Please copy the original recipients, otherwise I may not read your reply. WWW: http://www.kruijff.org/alex/FreeBSD/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] -- Alex Please copy the original recipients, otherwise I may not read your reply. WWW: http://www.kruijff.org/alex/FreeBSD/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot problems afther reinstall windows
Windows was able to boot afhter I installed it. I never touched boot.ini. The content would have been: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=Microsoft Windows XP Professional /fastdetect /NoExecute=OptIn I now use a different solution. Instead of the freebsd bootloader (boot0). I now use the windows bootloader. I copied boot1 to c:\freebsd.bin. Then modified windows boot.ini as follow: [boot loader] timeout=10 default=c:\freebsd.bin [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=Microsoft Windows XP Professional /fastdetect /NoExecute=OptIn c:\freebsd.bin=FreeBSD 5 This works for me. I still wonder why the stuff below didn't work. In the past I would do this with /stand/sysinstall. But I don't dare to do this with FreeBSD 5 because of drive geometric warnings. Remember there are two boot blocks, so to speak. There is the MBR that lets you choose which slice to boot. There is only one of those per disk and it lives in sector 0 of the disk. The MBR generally has a standard calling sequence (that the Bios calls) and sets things up to a fairly standard condition and looks for standard appearing boot sectors in slices and makes a standard call to the selected slice's boot sector. Almost any MBR that knows how to recognize a standard boot sector in a slice and lets you choose between them if there are more than one can be used interchangeably. Then there is the boot block with the actual boot loader that starts pulling the OS from the bootable partition. On a multi boot disk there are several - one per each bootable slice and they live in the boot sector of each slice.Those are specific to the OS they are booting. Though their calling sequence is standard, what they have to do to load and start their own OS is not. I am guessing that you managed to overwrite or damage the MS slice' boot sector while you were doing things, or didn't get it written to the slice properly when you reloaded or something like that. Even though you put the MBR back with FreeBSD's fdisk, did you also make sure that the MS slice had its own boot loader? Anyway you did when you put the MS boot loader back. So it works now. jerry On Tue, Mar 15, 2005 at 02:12:46AM +, Jason Henson wrote: What is in your windows boot.ini file? On 03/14/05 11:13:49, Alex de Kruijff wrote: Hi, I've recently reinstalled windows. Windows removes the MBR as you know. So ather I installed it I set partion 1 (FreeBSD) active and rebooted. Then I followed the handbook and did fdisk -B -b /boot/boot0 ad0. Now I get the orginal screen afther booting. Only it beeps when I press F2 (Windows). I can mount the second partion on FreeBSD, but cant boot. Any ideas to what I'm missing here? # fdisk *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=484521 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=484521 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 20971377 (10239 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 104/ sector 63 The data for partition 2 is: sysid 12 (0x0c),(DOS or Windows 95 with 32 bit FAT (LBA)) start 20980890, size 20948760 (10228 Meg), flag 80 (active) beg: cyl 1023/ head 0/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 3 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 41942880, size 446454288 (217995 Meg), flag 80 (active) beg: cyl 1023/ head 210/ sector 1; end: cyl 1023/ head 80/ sector 63 The data for partition 4 is: UNUSED -- Alex Please copy the original recipients, otherwise I may not read your reply. WWW: http://www.kruijff.org/alex/FreeBSD/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] -- Alex Please copy the original recipients, otherwise I may not read your reply. WWW: http://www.kruijff.org/alex/FreeBSD/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe,
boot problems
hello , i have already the sameproblem when i boot with freebsd 5.3 since i have had a power cut .The message of the error is : error 16 Iba 191 No /boot/loader FreeBSD/i386 boot Default: 0:ad(0,a)/kernel boot: error 16 Iba 191 No /kernel I have tried boot : /kernel.old but i have No /kernel.old and i don't know how do with the bootonly cd. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot problems afther reinstall windows
On Tue, Mar 15, 2005 at 02:12:46AM +, Jason Henson wrote: What is in your windows boot.ini file? On 03/14/05 11:13:49, Alex de Kruijff wrote: Hi, I've recently reinstalled windows. Windows removes the MBR as you know. So ather I installed it I set partion 1 (FreeBSD) active and rebooted. Then I followed the handbook and did fdisk -B -b /boot/boot0 ad0. Now I get the orginal screen afther booting. Only it beeps when I press F2 (Windows). I can mount the second partion on FreeBSD, but cant boot. Any ideas to what I'm missing here? On Tue, Mar 15, 2005 at 08:53:25AM -0500, Jerry McAllister wrote: Windows was able to boot afhter I installed it. I never touched boot.ini. The content would have been: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=Microsoft Windows XP Professional /fastdetect /NoExecute=OptIn I now use a different solution. Instead of the freebsd bootloader (boot0). I now use the windows bootloader. I copied boot1 to c:\freebsd.bin. Then modified windows boot.ini as follow: [boot loader] timeout=10 default=c:\freebsd.bin [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=Microsoft Windows XP Professional /fastdetect /NoExecute=OptIn c:\freebsd.bin=FreeBSD 5 This works for me. I still wonder why the stuff below didn't work. In the past I would do this with /stand/sysinstall. But I don't dare to do this with FreeBSD 5 because of drive geometric warnings. Remember there are two boot blocks, so to speak. There is the MBR that lets you choose which slice to boot. There is only one of those per disk and it lives in sector 0 of the disk. The MBR generally has a standard calling sequence (that the Bios calls) and sets things up to a fairly standard condition and looks for standard appearing boot sectors in slices and makes a standard call to the selected slice's boot sector. Almost any MBR that knows how to recognize a standard boot sector in a slice and lets you choose between them if there are more than one can be used interchangeably. Then there is the boot block with the actual boot loader that starts pulling the OS from the bootable partition. On a multi boot disk there are several - one per each bootable slice and they live in the boot sector of each slice.Those are specific to the OS they are booting. Though their calling sequence is standard, what they have to do to load and start their own OS is not. Is it posible to boot one OS if you only have the MBR? I am guessing that you managed to overwrite or damage the MS slice' boot sector while you were doing things, or didn't get it written to the slice properly when you reloaded or something like that. Even though you put the MBR back with FreeBSD's fdisk, did you also make sure that the MS slice had its own boot loader? Anyway you did when you put the MS boot loader back. So it works now. The previous time I first installed windows and then FreeBSD 5. The difference this time is that I didn't use /stand/sysinstall. This because I would get into serious troubel. (I never found out how to force the right geometry) So I was thinking maybe sysinstall does something (like copy the MBR to the second boot location) that I didn't do manualy. I used the windows method for when something goes wrong (i.e. reboot) and just reinstalled Windows. A added bonus is that I now have one OS as default instead the last used. I alway was annoyed about loading the previous used. I only want to use Windows if I have to (mostly for word - there language functionality is superb). Tanks for you time. Appricate it. -- Alex Please copy the original recipients, otherwise I may not read your reply. WWW: http://www.kruijff.org/alex/FreeBSD/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot problems afther reinstall windows
timeout=10 default=c:\freebsd.bin [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=Microsoft Windows XP Professional /fastdetect /NoExecute=OptIn c:\freebsd.bin=FreeBSD 5 This works for me. I still wonder why the stuff below didn't work. In the past I would do this with /stand/sysinstall. But I don't dare to do this with FreeBSD 5 because of drive geometric warnings. Remember there are two boot blocks, so to speak. There is the MBR that lets you choose which slice to boot. There is only one of those per disk and it lives in sector 0 of the disk. The MBR generally has a standard calling sequence (that the Bios calls) and sets things up to a fairly standard condition and looks for standard appearing boot sectors in slices and makes a standard call to the selected slice's boot sector. Almost any MBR that knows how to recognize a standard boot sector in a slice and lets you choose between them if there are more than one can be used interchangeably. Then there is the boot block with the actual boot loader that starts pulling the OS from the bootable partition. On a multi boot disk there are several - one per each bootable slice and they live in the boot sector of each slice.Those are specific to the OS they are booting. Though their calling sequence is standard, what they have to do to load and start their own OS is not. Is it posible to boot one OS if you only have the MBR? No, you need the boot sector. If you have only that in the first location, you can boot without an full MBR, I think, but not without the boot sector that the MBR loads and jumps to. I am guessing that you managed to overwrite or damage the MS slice' boot sector while you were doing things, or didn't get it written to the slice properly when you reloaded or something like that. Even though you put the MBR back with FreeBSD's fdisk, did you also make sure that the MS slice had its own boot loader? Anyway you did when you put the MS boot loader back. So it works now. The previous time I first installed windows and then FreeBSD 5. The difference this time is that I didn't use /stand/sysinstall. This because I would get into serious troubel. (I never found out how to force the right geometry) So I was thinking maybe sysinstall does something (like copy the MBR to the second boot location) that I didn't do manualy. I think you are using MBR for boot sector. The MBR is what goes in sector 0 of the disk itself. The boot sector/record/block goes in the first sector of the slice. The MBR lets you pick the slice you want to boot and then loads its boot sector/block/record and jumps to it in a standard location. jerry I used the windows method for when something goes wrong (i.e. reboot) and just reinstalled Windows. A added bonus is that I now have one OS as default instead the last used. I alway was annoyed about loading the previous used. I only want to use Windows if I have to (mostly for word - there language functionality is superb). Tanks for you time. Appricate it. -- Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Boot problems afther reinstall windows
Hi, I've recently reinstalled windows. Windows removes the MBR as you know. So ather I installed it I set partion 1 (FreeBSD) active and rebooted. Then I followed the handbook and did fdisk -B -b /boot/boot0 ad0. Now I get the orginal screen afther booting. Only it beeps when I press F2 (Windows). I can mount the second partion on FreeBSD, but cant boot. Any ideas to what I'm missing here? # fdisk *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=484521 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=484521 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 20971377 (10239 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 104/ sector 63 The data for partition 2 is: sysid 12 (0x0c),(DOS or Windows 95 with 32 bit FAT (LBA)) start 20980890, size 20948760 (10228 Meg), flag 80 (active) beg: cyl 1023/ head 0/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 3 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 41942880, size 446454288 (217995 Meg), flag 80 (active) beg: cyl 1023/ head 210/ sector 1; end: cyl 1023/ head 80/ sector 63 The data for partition 4 is: UNUSED -- Alex Please copy the original recipients, otherwise I may not read your reply. WWW: http://www.kruijff.org/alex/FreeBSD/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot problems afther reinstall windows
What is in your windows boot.ini file? On 03/14/05 11:13:49, Alex de Kruijff wrote: Hi, I've recently reinstalled windows. Windows removes the MBR as you know. So ather I installed it I set partion 1 (FreeBSD) active and rebooted. Then I followed the handbook and did fdisk -B -b /boot/boot0 ad0. Now I get the orginal screen afther booting. Only it beeps when I press F2 (Windows). I can mount the second partion on FreeBSD, but cant boot. Any ideas to what I'm missing here? # fdisk *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=484521 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=484521 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 20971377 (10239 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 104/ sector 63 The data for partition 2 is: sysid 12 (0x0c),(DOS or Windows 95 with 32 bit FAT (LBA)) start 20980890, size 20948760 (10228 Meg), flag 80 (active) beg: cyl 1023/ head 0/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 3 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 41942880, size 446454288 (217995 Meg), flag 80 (active) beg: cyl 1023/ head 210/ sector 1; end: cyl 1023/ head 80/ sector 63 The data for partition 4 is: UNUSED -- Alex Please copy the original recipients, otherwise I may not read your reply. WWW: http://www.kruijff.org/alex/FreeBSD/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 5.3-RELEASE kernel boot problems
First the system specs: * Motherboard: SuperMicro 370SED (manuf. in 2000; see [1]) * CPU: Intel Pentium III 933 MHz * RAM: 384 MB (128 MB PC100; 256 MB PC133) * network: * Linksys LNE100TX Etherfast 10/100 (device dc0) * Linksys LNE100TX Etherfast 10/100 (device dc1; unused for now) * video: integrated * storage: * built-in primary IDE controller * primary master: 24x CD-ROM (unknown manuf.) * built-in secondary IDE controller: disabled in BIOS * Maxtor Ultra/ATA 100 PCI IDE controller: * primary master: Maxtor 80 GB ATA/133 DiamondMax Plus 9 (new) using entire disk for FreeBSD slice; geometry is OK. partitions: ad4s1a150 MB / ad4s1b768 MB swap ad4s4d8 GB/var ad4s1e7 GB/usr ad4s1f 61 GB/milo (misc) * primary slave: Maxtor 60 GB ATA/100 (DiamondMax Plus 60) * secondary master: Maxtor 30 GB (DiamondMax VL40) * secondary slave: none Now for my problem: If I install FreeBSD 4.10 from a miniinst CD-R on this system, it works great, no problems. If I install FreeBSD 5.3 from a miniinst CD-R on the same system with no hardware changes, the CD boots up fine (no need to disable ACPI), it fails to make it through the boot process; it just keeps rebooting. More on that in a sec. It also fails to install if all of the following are true: - partitions were set up already from a previous install; - in the slice editor I just re-entered the mount points (they come up as asterisks each time sysinstall is run... I assume that's normal?) - the newfs flag is NOT set on each partition Under these circumstances, the install process freezes at the first fsck_ffs operation (Doing fsck_ffs -y /mnt/dev/ad4s1f which is my /milo partition) ...and no key combos can get out of it. I thought it maybe just took a while but after 30 minutes I decided it was dead. OK, anyway, so if I set newfs on the partitions, then the base distribution installs OK. I can set up the network and root user password, enable SSH and inetd, and then let it boot... BSP CPU.Microcode OK Searching for Boot Record from CDROM..Not Found Searching for Boot Record from Floppy..Not Found Searching for Boot Record from SCSI..Not Found ...and then I get a stack dump that I can't copy here because it disappears as the system automatically reboots right away. If I press a key during the boot, before /boot/loader runs, I can enter 0:ad(0,a) /boot/kernel/kernel -p The result is a rapidly twirling - that then slows and then freezes. A cold reboot is then needed. Same effect when using -sv or -C. I have also tried putting in a different drive (an old 5 GB Seagate instead of the 80 GB Maxtor) and installing to that. For some reason, it doesn't automatically reboot after printing the kernel stack dump, but otherwise there's no change in behavior. I tried using an old 5 GB Seagate drive instead of the Maxtor 80 GB. I tried using a different drive cable. I tried disconnecting all drives other than the boot drive. I have tried setting the partition active and not modifying the MBR. I have also tried using UFS1 instead of UFS2 on all partitions. I have tried using the FreeBSD boot loader. No difference in any case. Twirl twirl twirl freeze. Help? Thanks, Mike [1] http://www.supermicro.com/manuals/motherboard/810/MNL-0618.pdf ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: 5.3-BETAx Boot Problems
Thank you both very much. This did indeed resolve my issues and I am now getting FreeBSD 5.3-BETA6 configured on my problem system. Ben -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gavin Atkinson Sent: Wednesday, September 29, 2004 12:50 PM To: Pratt, Benjamin E. Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: 5.3-BETAx Boot Problems On Wed, 29 Sep 2004, Pratt, Benjamin E. wrote: Hello, I am still trying to get FreeBSD Beta to work but am running into problems when my system boots. The boot problem appears to be occurring just after the IDE drives are detected but before the root file system is mounted. These are the last four lines of text that are displayed when I try to boot from either ISO or after running CVSUP: md0: Preloaded image /boot/mfsroot 4423680 bytes at 0xc09b6c5c ad0: 29314MB IC35L030AVV207-0/V21OA66A [59560/16/63] at ata0-master UDMA66 ATAPI_RESET time = 1630us acd0: CDRW Hewlett-Packard CD-Writer Plus 9100/1.0c at ata1-master UDMA33 Yes, this bug was present in BETA5 and BETA6. It will be fixed in BETA7. In the mean time, you can avoid it by disabling your floppy drive (by setting hint.fd.0.disabled=1 at the loader) Gavin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3-BETAx Boot Problems
Am Mittwoch, 29. September 2004 18:53 schrieb Pratt, Benjamin E.: Hello, I am still trying to get FreeBSD Beta to work but am running into problems when my system boots. The boot problem appears to be occurring just after the IDE drives are detected but before the root file system is mounted. These are the last four lines of text that are displayed when I try to boot from either ISO or after running CVSUP: md0: Preloaded image /boot/mfsroot 4423680 bytes at 0xc09b6c5c ad0: 29314MB IC35L030AVV207-0/V21OA66A [59560/16/63] at ata0-master UDMA66 ATAPI_RESET time = 1630us acd0: CDRW Hewlett-Packard CD-Writer Plus 9100/1.0c at ata1-master UDMA33 It's possibly a bug in the new fdc code. I also have one system with a floppy which stops booting since beta6. Just remove device fdc from the kernel (or try to disable the Floppy Controller in the BIOS) and see if that helps. Hadn't have time yet to look at -current if this bug is known and if applicable create a PR. -Mano When 5.2.1 or 6.0-CURRENT are installed on the system everything boots fine and the next line is: Mounted root from ufs:/dev/ad0s1a. I looked at /var/log/messages and did not see any boot problems logged when I had CVSUPed to 5.3-BETA5 or 5.3-BETA6, attempted to boot, and then re-booted with the 5.2.1 kernel so that would suggest a problem mounting the file system for writing. The boot problems are occurring after I build the world, build the kernel and install the kernel but before I install the world. I looked at the GENERIC kernel from both the 5.2.1 and 5.3-BETA6 systems and the only options that 5.2.1 had and 5.3-BETA6 doesn't are: options PFIL_HOOKS options INVARIANT_SUPPORT 5.3-BETA6 has two options and eight devices that 5.2.1 doesn't. The options are: options GEOM_GPT options ADAPTIVE_GIANT The only two devices that I could possibly see affecting my system are: devicemem deviceio I do have 5.3-BETAx installed on two other systems so I can't imagine why it's not working on this one Dell Celeron system that want it to be on. I don't imagine that I'm the only one having this problem as I have seen other cases reported but I haven't found a solution other than going to 6.0-CURRENT which I would like to stay away from since it'll probably be a while before it's considered stable. Any help anyone can give would be greatly appreciated. Thank you, Ben ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] pgpU7HeRbPOBd.pgp Description: PGP signature
pxe boot problems
Hi, Im trying to install freebsd on a system (i386 system) without cdrom or floppy. I created a loader.rc and the kernel (used from /boot/kernel) and I created an mfsroot from the mfsroot.flp which can be downloaded from freebsd.org. The kernel is loaded, then mfsroot is loaded. my loader.rc echo Loading mfsroot... load -t mfs_root /mfsroot echo booting... echo \007\007 echo initializing h0h0magic... set boot_userconfig set vfs.root.mountfrom=ufs:/dev/md0c boot after mfsroot has been loaded is see: initializing h0h0magic... then a loud BEEP and then it stops and the system reboots. What am i doing wrong? Any hints what to do now? Bye, Mipam. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxe boot problems
In loader.rc i did unset acpi and now it gets a little further: after loading mfsroot (rotating /), after that i see: no such file or directory Then press enter to boot kernel now the kernel is located /boot/kernel/kernel when i press enter all i see is a / and the system hangs. Any hints? Bye, Mipam. Im trying to install freebsd on a system (i386 system) without cdrom or floppy. I created a loader.rc and the kernel (used from /boot/kernel) and I created an mfsroot from the mfsroot.flp which can be downloaded from freebsd.org. The kernel is loaded, then mfsroot is loaded. my loader.rc echo Loading mfsroot... load -t mfs_root /mfsroot echo booting... echo \007\007 echo initializing h0h0magic... set boot_userconfig set vfs.root.mountfrom=ufs:/dev/md0c boot after mfsroot has been loaded is see: initializing h0h0magic... then a loud BEEP and then it stops and the system reboots. What am i doing wrong? Any hints what to do now? Bye, Mipam. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.9 install-boot problems
[EMAIL PROTECTED] writes: installed 4.9, when i boot i get the message: panic:contigmalloc1: size must not be 0 and that's as far as it goes. i dual boot with linux, the mbr is not a problemm since i can select either os without problems. anybody know what the problem is and a fix? appreciate ur help,thanks. This seems to be one of the symptoms of buggy AGP support in the system firmware. Unfortunately, there is no longer any supported way of installing FreeBSD without it -- AGP is in the GENERIC kernels, and has been for quite some time now. You might try booting to the loader and disabling AGP, but I'm not sure that will help. incidentally, / on 4.9 is well inside the 8g limit, though it seems that on freebsd that's not a requirement, at least i haven't seen any mention of it. The kernel has to be inside whatever *BIOS* limit exists for booting. -- Lowell Gilbert, embedded/networking software engineer, Boston area: resume/CV at http://be-well.ilk.org:8088/~lowell/resume/ username/password public ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
4.9 install-boot problems
installed 4.9, when i boot i get the message: panic:contigmalloc1: size must not be 0 and that's as far as it goes. i dual boot with linux, the mbr is not a problemm since i can select either os without problems. anybody know what the problem is and a fix? appreciate ur help,thanks. incidentally, / on 4.9 is well inside the 8g limit, though it seems that on freebsd that's not a requirement, at least i haven't seen any mention of it. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
sun ultra 5 boot problems
I have successfully installed freebsd on 9.1 gb hdd in my ultra 5 (freebsd had no errors during install.) However when i say probe-ide at the obp it doesn't even find the disk, which would explain why it can't boot of course. Any help would be appreciated. -Thanks ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Boot problems with SCSI card
Hi, I can't boot my FreeBSD 5.0-RELEASE (both with the stock kernel and with a self-compiled kernel), if my AdvanSys SCSI Host Adapter (ISA, ABP5140) is installed. The problem was also there while installing FreeBSD, but I simply removed the SCSI card during the installation. Without the card everything works perfectly. Here is some output during the boot process: (I had to type it off the screen, because it got never written to disk. Anybody got a solution for this?) [...] adv1: AdvanSys SCSI Host Adapter, SCSI ID 7, queue depth 16 adv1: ABP5140 at port 0x110 iomem 0xc8000-0xc irq 10 drq 5 on isa0 [...] Waiting 10 seconds for SCSI devices to settle [After about 1 minute] (probe6:adv1:0:6:0): Timed out (probe6:adv1:0:6:0): Attempting abort (probe6:adv1:0:6:0): Timed out (probe6:adv1:0:6:0): Resetting bus adv1: No longer in timeout [After about another minute] (probe5:adv1:0:5:0): Timed out (probe5:adv1:0:5:0): Attempting abort (probe5:adv1:0:5:0): Timed out (probe5:adv1:0:5:0): Resetting bus adv1: No longer in timeout After that output I waited about half an hour (!) and nothing happened. I don't think that it makes sense to wait any longer. There is only one SCSI drive attached to the SCSI card: An internal Yamaha CD-Writer (4416). Its SCSI ID is 3. Changing the ID just results in a slightly different output. For example if I change it to 6, the output is about timeouts on ID 3 and 5, instead of 6 and 5. With Writer on 4 the output is about ID 3 and 2. And so on. I tried every SCSI ID, but none works. The SCSI termination is also configured correctly. But I don't think that this is a hardware related problem, because the same hardware configuration worked perfectly under Linux. (And some time ago it worked under Windows.) Any ideas? Thanks, Leo ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
