Re: Dual booting problems
On Fri, Mar 02, 2007 at 12:34:10AM +, RW wrote: On Thu, 1 Mar 2007 13:30:26 -0900 Beech Rintoul [EMAIL PROTECTED] wrote: I should also mention that you need the FreeBSD boot manager on both disks, or an alternative boot manager such as grub or gag. Read the handbook. I recall reading that too, but I've never understood what it's supposed to achieve. I imagine it must be a quirk of the FreeBSD boot manager, I've certainly never needed to install more than one copy of GAG or LILO. You may have installed the single sector that is needed without knowing it. I don't play with those and so I am less familiar with how they operate. They use up some space that is normally available, but is not officially guaranteed to be available to have a larger program and more complex tables. In FreeBSD and according to how it is officially done in DOS partitioned disks, there is a one block utility that goes in sector 0. Since it is only one block, its ability to do things is highly limited. It has the slice table and some flags and just enough code to look at its slice table to see which slices are marked bootable and to look at other disk to see which ones have a similar boot block. This block is called the MBR. If there are more than one boot possibilities, it gives you a menu list. The first four menu numbers are reserved for slices on its own disk. Starting with 5, the menu items point to the MBR on other disk[s]. I have never tried it with more than 2 disks with bootable slices on them, so I don't know if it will list a 6 or beyond. The MBR is not supposed to be OS specific, but the MS MBR breaks that rule by not recognizing any slice or other MBR that is not MS. Each bootable slice on a disk (up to 4 are allowed) has its own boot sector. If you select F1-F4, then the MBR will cause the boot sector from that slice to be loaded and then it passes control to it. That slice' boot sector is OS specific and continues the boot process from there. If you select F5 (maybe F6 or more, I should try that some time) it will instead cause the MBR from that second (maybe third, etc) disk to be loaded and passes control to it. Then that MBR looks at its own slice table and makes up a menu if there are more than one bootable slices on that drive. Since the first drive's MBR does not read the second drive's slice table or attempt to boot any of its slices, but only passes control to the second MBR, then the second disk needs an MBR to take over and handle its own slice table and bootable slices. If there is only one bootable slice on a drive or you make it a 'dangerously dedicated drive' you can get away without a full MBR on that drive and put a 'standard' boot block on it, but why bother? Just always remember to put an MBR on every drive that has any bootable slices. Note that fdisk puts the MBR on the drive. But, bsdlabel puts the per slice boot sector on it. That per slice boot sector must always be there regardless of how many bootable slices or if the drive is 'dangerously dedicated' if you want that slice to be bootable. That is a different issue from the MBR. I hope that clarifies things rather than muddying them up. It is all in the handbook plus man pages, but the language is slightly more formal and there are still a couple places that mung the use of the words partition and slice even though most have been recently cleaned up. I found a couple the other day, I think in 6.1 (but I forgot to write them down. I should have sent in a PR). jerry ___ 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 booting problems
Jerry McAllister wrote: If you select F5 (maybe F6 or more, I should try that some time) it will instead cause the MBR from that second (maybe third, etc) disk to be loaded and passes control to it. F5 moves to the next disk. From that next disk F5 moves on to the next disk again and so forth until there are no more disks and then it moves you back to the first disk. No F6 or greater. F5 will only successfully move on if there is a FreeBSD MBR (*) on the next disk. If there is not such an MBR, the F5 option is displayed but will not work (maybe beep?) and after a while you will timeout and boot whatever default you have. Bad idea to lose the MBR from a disk in the middle of a chain, but easy to put back booting from CD1. So as the OP had: F1: FreeBSD F5: Disk 2 (Windows) but had not put FreeBSD MBR on that second disk, F5 did nothing and then the F1 default kicked in and booted FreeBSD. Had the MBR been on that second disk it would have started to boot windows and then likely rebooted because the disk was no longer in the same position in the chain as it had been when Windows was installed. I don't believe it is necessary for Windows to always be the first disk, just that the disk has to stay in the same position as it was in when Windows was installed, which is usually the first disk! (Never tested that though). --Alex (*) Actually I have no idea what would happen if you stuck some other booter like grub or gag on a later disk. But blank (new) disk or Windows MBR will not move on. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual booting problems
On Fri, Mar 02, 2007 at 05:39:05PM +, Alex Zbyslaw wrote: Jerry McAllister wrote: If you select F5 (maybe F6 or more, I should try that some time) it will instead cause the MBR from that second (maybe third, etc) disk to be loaded and passes control to it. F5 moves to the next disk. From that next disk F5 moves on to the next disk again and so forth until there are no more disks and then it moves you back to the first disk. No F6 or greater. OK. That makes sense. I have not had enough disk on hand to try beyond two. F5 will only successfully move on if there is a FreeBSD MBR (*) on the next disk. If there is not such an MBR, the F5 option is displayed but will not work (maybe beep?) and after a while you will timeout and boot whatever default you have. Hmmm. I thought it would still do a 'dedicated' FreeBSD disk as the second one without an MBR. It will do the first disk, but that is a different situation, of course. Bad idea to lose the MBR from a disk in the middle of a chain, but easy to put back booting from CD1. Yup. If you lose the MBR, it can be put back using the Fixit from the installation CD (CD-1). So as the OP had: F1: FreeBSD F5: Disk 2 (Windows) but had not put FreeBSD MBR on that second disk, F5 did nothing and then the F1 default kicked in and booted FreeBSD. Had the MBR been on that second disk it would have started to boot windows and then likely rebooted because the disk was no longer in the same position in the chain as it had been when Windows was installed. Makes sense. I don't keep up with the Windows stuff much, but I knew it would not be happy in that position and the lack of an MBR on the second disk was where the boot process was stopping. I don't believe it is necessary for Windows to always be the first disk, just that the disk has to stay in the same position as it was in when Windows was installed, which is usually the first disk! (Never tested that though). Hmmm. Might be interesting to experiment, though that time spent on MS could probably be better spend elsewhere. --Alex (*) Actually I have no idea what would happen if you stuck some other booter like grub or gag on a later disk. But blank (new) disk or Windows MBR will not move on. Don't know this one. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual booting problems
On Fri, 2 Mar 2007 11:37:26 -0500 Jerry McAllister [EMAIL PROTECTED] wrote: On Fri, Mar 02, 2007 at 12:34:10AM +, RW wrote: On Thu, 1 Mar 2007 13:30:26 -0900 Beech Rintoul [EMAIL PROTECTED] wrote: I should also mention that you need the FreeBSD boot manager on both disks, or an alternative boot manager such as grub or gag. Read the handbook. I recall reading that too, but I've never understood what it's supposed to achieve. I imagine it must be a quirk of the FreeBSD boot manager, I've certainly never needed to install more than one copy of GAG or LILO. If you select F5 (maybe F6 or more, I should try that some time) it will instead cause the MBR from that second (maybe third, etc) disk to be loaded and passes control to it. Then that MBR looks at its own slice table and makes up a menu if there are more than one bootable slices on that drive. In other words it *is* a quirk of the FreeBSD boot manager, in that it doesn't allow you to chainload a partition on another drive directly. You have to chainload the intermediate MBR which needs a second copy of the bootmanager. Most bootmanagers can do this directly, using the partition table on the other drive. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual booting problems
On Fri, 2 Mar 2007 12:49:23 -0500 Jerry McAllister [EMAIL PROTECTED] wrote: On Fri, Mar 02, 2007 at 05:39:05PM +, Alex Zbyslaw wrote: (*) Actually I have no idea what would happen if you stuck some other booter like grub or gag on a later disk. But blank (new) disk or Windows MBR will not move on. Don't know this one. Presumably it would just chainload the other bootmanager, but there's not much point in doing that. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual booting problems
On Fri, Mar 02, 2007 at 05:52:52PM +, RW wrote: On Fri, 2 Mar 2007 11:37:26 -0500 Jerry McAllister [EMAIL PROTECTED] wrote: On Fri, Mar 02, 2007 at 12:34:10AM +, RW wrote: On Thu, 1 Mar 2007 13:30:26 -0900 Beech Rintoul [EMAIL PROTECTED] wrote: I should also mention that you need the FreeBSD boot manager on both disks, or an alternative boot manager such as grub or gag. Read the handbook. I recall reading that too, but I've never understood what it's supposed to achieve. I imagine it must be a quirk of the FreeBSD boot manager, I've certainly never needed to install more than one copy of GAG or LILO. If you select F5 (maybe F6 or more, I should try that some time) it will instead cause the MBR from that second (maybe third, etc) disk to be loaded and passes control to it. Then that MBR looks at its own slice table and makes up a menu if there are more than one bootable slices on that drive. In other words it *is* a quirk of the FreeBSD boot manager, in that it doesn't allow you to chainload a partition on another drive directly. You have to chainload the intermediate MBR which needs a second copy of the bootmanager. Most bootmanagers can do this directly, using the partition table on the other drive. I wouldn't call it a quirk of FreeBSD. FreeBSD does it the 'canonical' way. The others use additional space on the rest of the track, that is technically not available, to make a bigger program and tables that can do additional things. That's nice, but not officially supported. So, it is really a _quirk_ of Grub/Gag/others and not guaranteed to work. What would be really nice is if the world just decided to create an official standard that makes that whole track available since it really most often is - actually, I don't know any modern system where it is not, but I haven't made a survey. jerry ___ 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]
Dual booting problems
I'm having a little problem trying to dual boot. I have two SATA hard drives, the first one with FreeBSD and the second with Windows XP. I installed the FreeBSD boot manager on the first drive, and when the computer boots, it displays: F1 FreeBSD F5 Drive 1 When I press F5, FreeBSD loads and not Windows. I know Windows is working because when I disconnect the first drive, Windows boots from the second just fine. I've tried using boot0cfg to reload the boot manager, but that doesn't help. The simplest thing to do would be to specify that F5 boots Windows, but I can't find anything. Is this configuration even possible? Or does Windows just make it impossible to boot from the second disk? -- Sam Jones [EMAIL PROTECTED] [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 booting problems
On Thursday 01 March 2007 12:36, Sam Jones said: I'm having a little problem trying to dual boot. I have two SATA hard drives, the first one with FreeBSD and the second with Windows XP. I installed the FreeBSD boot manager on the first drive, and when the computer boots, it displays: F1 FreeBSD F5 Drive 1 When I press F5, FreeBSD loads and not Windows. I know Windows is working because when I disconnect the first drive, Windows boots from the second just fine. I've tried using boot0cfg to reload the boot manager, but that doesn't help. The simplest thing to do would be to specify that F5 boots Windows, but I can't find anything. Is this configuration even possible? Or does Windows just make it impossible to boot from the second disk? You need to switch your drives around and setup accordingly. Windows (at least in my experience) will not boot from anything but the first drive. Beech -- --- Beech Rintoul - Port Maintainer - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.freebsd.org/releases/6.2R/announce.html --- pgpRs85yHX74L.pgp Description: PGP signature
Re: Dual booting problems
On Thursday 01 March 2007 13:21, Beech Rintoul said: On Thursday 01 March 2007 12:36, Sam Jones said: I'm having a little problem trying to dual boot. I have two SATA hard drives, the first one with FreeBSD and the second with Windows XP. I installed the FreeBSD boot manager on the first drive, and when the computer boots, it displays: F1 FreeBSD F5 Drive 1 When I press F5, FreeBSD loads and not Windows. I know Windows is working because when I disconnect the first drive, Windows boots from the second just fine. I've tried using boot0cfg to reload the boot manager, but that doesn't help. The simplest thing to do would be to specify that F5 boots Windows, but I can't find anything. Is this configuration even possible? Or does Windows just make it impossible to boot from the second disk? You need to switch your drives around and setup accordingly. Windows (at least in my experience) will not boot from anything but the first drive. I should also mention that you need the FreeBSD boot manager on both disks, or an alternative boot manager such as grub or gag. Read the handbook. Beech Beech -- --- Beech Rintoul - Port Maintainer - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.freebsd.org/releases/6.2R/announce.html --- pgpouHCKIYmQI.pgp Description: PGP signature
Re: Dual booting problems
On Thu, Mar 01, 2007 at 04:36:45PM -0500, Sam Jones wrote: I'm having a little problem trying to dual boot. I have two SATA hard drives, the first one with FreeBSD and the second with Windows XP. I installed the FreeBSD boot manager on the first drive, and when the computer boots, it displays: F1 FreeBSD F5 Drive 1 When I press F5, FreeBSD loads and not Windows. I know Windows is working because when I disconnect the first drive, Windows boots from the second just fine. I've tried using boot0cfg to reload the boot manager, but that doesn't help. The simplest thing to do would be to specify that F5 boots Windows, but I can't find anything. Is this configuration even possible? Or does Windows just make it impossible to boot from the second disk? You got it. As far as I know MSwin[p] insists on being on the first drive. Of course, FreeBSD doesn't have any such sloppy limitations. So, swap the drives. Make sure both have a FreeBSD MBR and things should work out fine. You will just have to use the two-step (F5 followed by F1) to boot FreeBSD. Actually, if FreeBSD is the only bootable slice on the second disk(after you move them) you might not have to hit the F1 after the F5. jerry -- Sam Jones [EMAIL PROTECTED] [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-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual booting problems
On Thu, 1 Mar 2007 13:30:26 -0900 Beech Rintoul [EMAIL PROTECTED] wrote: I should also mention that you need the FreeBSD boot manager on both disks, or an alternative boot manager such as grub or gag. Read the handbook. I recall reading that too, but I've never understood what it's supposed to achieve. I imagine it must be a quirk of the FreeBSD boot manager, I've certainly never needed to install more than one copy of GAG or LILO. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mfs_root booting problems
Hey all, I've been having a problem that hopefully someone would be able to help me with. I've been trying to boot FreeBSD via PXE for at least a couple of days now with no luck. I've read several online guides none of which explain using a root mfs to accomplish this task. Most of the manuals I've read go over mounting / as NFS which isn't ideal for me. I've got mostly everything working *up to* the point where the system begins bootstrapping. It loads the kernel, loads the mfs root and then the machine immediately reboots. For the life of me, I can't figure out why. I was hoping that someone has a documented method for initializing a FreeBSD system via PXE and without the use of NFS for the root filesystem. For refernce my loader.rc: echo Loading Your Kernel Fool!!! set hint.acpi.0.disabled=1## have tried it without it being disabled. load /boot/kernel/kernel echo echo Loading mfs filesystem YoYo!! load -t mfs_root /mfsroot echo booting... echo \007\007 set vfs.root.mountfrom=ufs:/dev/md0## have tried /dev/md0c as well boot -- wacko# ll /tftpboot/mfsroot -rw-r--r-- 1 root wheel 4423680 Nov 2 02:33 /tftpboot/mfsroot Assuming the mfs file sysetm is being create without error (I assume it is due to a lack of error messages), then I assume loader reads init like usual. wacko# file /mnt/mfsroot/sbin/init /mnt/mfsroot/sbin/init: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), statically linked, stripped And then continues on with /etc/rc wacko# file /mnt/mfsroot/etc/rc /mnt/mfsroot/etc/rc: Bourne shell script text executable As for the rest of the filesthey are certainly all there. I believe it's also worth mentioning, that if I use the mfsroot that comes with the installer, it loads/run fine. Not sure if this helps any or not. What could I possibly be missing? Thanks for the time. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: booting problems
On Wed, 19 Apr 2006 21:46:24 -, boy red [EMAIL PROTECTED] wrote: i have so far installed freeBSD OS and set up the accounts but im having some problems. it just takes me 2 a black DOS type screen and i dont know how 2 get in. by getting in i mean that it doesnt take me to the place where i actually start using the computer. please help. If your looking for a quick gui setup, try this: first go to root, do this by typing: su enter your root password. then type: pkg_add -r gnome2 exec csh gdm This will install ad start the gnome graphical user interface, to automaticly start it when FreeBSD starts, type(as root) ee /etc/ttys Scroll down a few lines and you'll see this line: ttyv9 /usr/X11R6/bin/xdm -nodaemon xterm off secur replace xdm with gdm and replace off with on. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
booting problems
i have so far installed freeBSD OS and set up the accounts but im having some problems. it just takes me 2 a black DOS type screen and i dont know how 2 get in. by getting in i mean that it doesnt take me to the place where i actually start using the computer. please help. __ 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: booting problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 boy red wrote: i have so far installed freeBSD OS and set up the accounts but im having some problems. it just takes me 2 a black DOS type screen and i dont know how 2 get in. by getting in i mean that it doesnt take me to the place where i actually start using the computer. please help. __ 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] How far do you get? Can you login? Do you get a prompt? Are you just missing a GUI? Dose it hang i the booting process? Write as verbose as you can 'cause I'm not getting how far you get, and then i can't help you. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFERrd5st+Hv5XgQPwRAiTOAJsGvUEeeoESeKep5fwnFitX5OgJvgCdGYh4 ztFvbfoGNcgt63s8J4cIORM= =wYJd -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: booting problems
On Wednesday 19 April 2006 16:46, boy red wrote: i have so far installed freeBSD OS and set up the accounts but im having some problems. it just takes me 2 a black DOS type screen and i dont know how 2 get in. by getting in i mean that it doesnt take me to the place where i actually start using the computer. please help. It sounds like everything has gone well so far, and that you are booting into a shell (command line interface). You ARE 'in' at this point. Where you go from there depends on how you intend to use the computer. You'll probably want to read the Handbook for further information. Here are a few chapters that will likely be helpful for you starting out: UNIX Basics: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/basics.html Installing Applications: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports.html Setting up a graphical user interface: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x11.html FreeBSD is going to give you a lot of choices in how you do things from this point on. (And honestly, up to this point as well ;) Which choices you make will depend on your personal preferences, what you want the machine to do for you, and how you want it do do those things. For all of these, the Handbook is your first and best resource.If you get lost along the way, this list isn't a bad place to ask for clarification. David -- Sure God created the world in only six days, but He didn't have an established user-base. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: booting problems
On 4/19/06, boy red [EMAIL PROTECTED] wrote: i have so far installed freeBSD OS and set up the accounts but im having some problems. it just takes me 2 a black DOS type screen and i dont know how 2 get in. by getting in i mean that it doesnt take me to the place where i actually start using the computer. please help. Welcome to the wonderful world of FreeBSD and Unix! This is the best place to start learning about your newly installed OS: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ -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]
HP AMD64 booting problems...
I recently picked up an HP5460 AMD64 laptop, and I recently wanted to try FreeBSD on it. Unfortunately, both the x86 and AMD64 versions will not boot, actually shutting the power down shortly after the kernel finishes loading. I've tried 5.3 and 4.8 with similar results, also cycling through disabling ACPI, safe mode, and going to the boot loader prompt and manually turning off whatever I can think of. Does anyone have any additional suggestions (either to boot it, or provide diagnostics), or will I be trapped to run Windows on this rather powerful machine? :) -Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HP AMD64 booting problems...
On Monday 28 February 2005 06:56 pm, Brian J. McGovern wrote: I recently picked up an HP5460 AMD64 laptop, and I recently wanted to try FreeBSD on it. Unfortunately, both the x86 and AMD64 versions will not boot, actually shutting the power down shortly after the kernel finishes loading. I've tried 5.3 and 4.8 with similar results, also cycling through disabling ACPI, safe mode, and going to the boot loader prompt and manually turning off whatever I can think of. Does anyone have any additional suggestions (either to boot it, or provide diagnostics), or will I be trapped to run Windows on this rather powerful machine? :) It's infamous Compaq/HP laptop problem. http://blackk.union.edu/~black/freebsd/ FYI, all the necessary fixes are integrated in 5-STABLE now. Jung-uk Kim -Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Booting problems
I am not an expert on FreeBSD and I am not an expert on hardware. I think I am going nuts compiling my kernel of release 4.11. It compliles all right but it wouldn't boot. The error I get is: panic no BSP found. Anyone has an idea of what that means? I'll give you my configuration file just in case someone takes the trouble to have a look at it. My machine is the HP t730m, 3GHz HT, 512 Meg of RAM. I would gladly give more info, thing is that install works just fine I just do not have sound or Internet (I use a wireless connection) Anyway, here is my conf file. % # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.62.2.1 2005/01/14 03:07:39 scottl Exp $ machine i386 #cpu I386_CPU #cpu I486_CPU #cpu I586_CPU cpu I686_CPU ident AURORITA maxusers 0 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support #options UFS_DIRHASH #Improve performance on big directories options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device #options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device, NFS required #options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] #options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev #options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O device isa #device eisa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device fd1 at fdc0 drive 1 # # If you have a Toshiba Libretto with its Y-E Data PCMCIA floppy, # don't use the above line for fdc0 but the following one: #device fdc0 # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering # SCSI Controllers #device amd # AMD 53C974 (Tekram DC-390(T)) #device isp # Qlogic family #device mpt # LSI-Logic MPT/Fusion #device ncr # NCR/Symbios Logic #device sym # NCR/Symbios Logic (newer chipsets) #options SYM_SETUP_LP_PROBE_MAP=0x40 # Allow ncr to attach legacy NCR devices when # both sym and ncr are configured #device adv0 at isa? #device adw #device bt0 at isa? #device aha0 at isa? #device aic0 at isa? #device ncv # NCR 53C500 #device nsp # Workbit Ninja SCSI-3 #device stg # TMC 18C30/18C50 # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) #device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) # RAID controllers interfaced to the SCSI subsystem #device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID #device dpt # DPT Smartcache - See LINT for options! #device iir # Intel Integrated RAID #device mly # Mylex AcceleRAID/eXtremeRAID #device ciss # Compaq SmartRAID 5* series #device twa # 3ware 9000 series PATA/SATA RAID # RAID controllers #device aac # Adaptec FSA RAID, Dell PERC2/PERC3 #device aacp # SCSI passthrough for aac (requires CAM) #device ida # Compaq Smart RAID #device ips # IBM/Adaptec ServeRAID #device amr # AMI MegaRAID
Booting problems
I am not an expert on FreeBSD and I am not an expert on hardware. I think I am going nuts compiling my kernel of release 4.11. It compliles all right but it wouldn't boot. The error I get is: panic no BSP found. Anyone has an idea of what that means? I'll give you my configuration file just in case someone takes the trouble to have a look at it. My machine is the HP t730m, 3GHz HT, 512 Meg of RAM. I would gladly give more info, thing is that install works just fine I just do not have sound or Internet (I use a wireless connection) Anyway, here is my conf file. % # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.62.2.1 2005/01/14 03:07:39 scottl Exp $ machine i386 #cpu I386_CPU #cpu I486_CPU #cpu I586_CPU cpu I686_CPU ident AURORITA maxusers 0 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support #options UFS_DIRHASH #Improve performance on big directories options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device #options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device, NFS required #options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] #options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev #options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O device isa #device eisa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device fd1 at fdc0 drive 1 # # If you have a Toshiba Libretto with its Y-E Data PCMCIA floppy, # don't use the above line for fdc0 but the following one: #device fdc0 # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering # SCSI Controllers #device amd # AMD 53C974 (Tekram DC-390(T)) #device isp # Qlogic family #device mpt # LSI-Logic MPT/Fusion #device ncr # NCR/Symbios Logic #device sym # NCR/Symbios Logic (newer chipsets) #options SYM_SETUP_LP_PROBE_MAP=0x40 # Allow ncr to attach legacy NCR devices when # both sym and ncr are configured #device adv0 at isa? #device adw #device bt0 at isa? #device aha0 at isa? #device aic0 at isa? #device ncv # NCR 53C500 #device nsp # Workbit Ninja SCSI-3 #device stg # TMC 18C30/18C50 # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) #device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) # RAID controllers interfaced to the SCSI subsystem #device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID #device dpt # DPT Smartcache - See LINT for options! #device iir # Intel Integrated RAID #device mly # Mylex AcceleRAID/eXtremeRAID #device ciss # Compaq SmartRAID 5* series #device twa # 3ware 9000 series PATA/SATA RAID # RAID controllers #device aac # Adaptec FSA RAID, Dell PERC2/PERC3 #device aacp # SCSI passthrough for aac (requires CAM) #device ida # Compaq Smart RAID #device ips # IBM/Adaptec ServeRAID #device amr # AMI MegaRAID #device mlx
Re: Booting problems
Teilhard Knight wrote: I am not an expert on FreeBSD and I am not an expert on hardware. Neither am I, but... The error I get is: panic no BSP found. Anyone has an idea of what that means? I'll give you my configuration file just in case someone takes the trouble to have a look at it. My machine is the HP t730m, 3GHz HT, 512 Meg of RAM. (sznipp) # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O BSP sounds suspiciously like something that has something to do with SMP (we're getting really technical here, eh?). I would try removing those two options from your kernel config and/or disabling Hyperthreading in BIOS, if that's an option. -- Toomas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Booting problems
- Original Message - From: Toomas Aas [EMAIL PROTECTED] To: Teilhard Knight [EMAIL PROTECTED] Cc: FreeBSD freebsd-questions@freebsd.org Sent: Wednesday, February 23, 2005 1:51 PM Subject: Re: Booting problems Teilhard Knight wrote: I am not an expert on FreeBSD and I am not an expert on hardware. Neither am I, but... The error I get is: panic no BSP found. Anyone has an idea of what that means? I'll give you my configuration file just in case someone takes the trouble to have a look at it. My machine is the HP t730m, 3GHz HT, 512 Meg of RAM. (sznipp) # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O BSP sounds suspiciously like something that has something to do with SMP (we're getting really technical here, eh?). I would try removing those two options from your kernel config and/or disabling Hyperthreading in BIOS, if that's an option. Thank you Toomas for taking the time. I commented out the two lines you suggested and unfortunately not even in that way I have a working kernel. When the system tries to boot it just shows the lame symbol | and then after a few seconds it reboots. I'll go through the configuration file again and try to see if something was related to a symmetric multiprocessor. I wouldn't like to disable hyperthreading in the bIOS because what would be the point of having an HT processor? Any more ideas from your part would be highly welcome. Teilhard ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Booting problems
___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Booting problems
Hi, I have an amd64 server machine with a 3ware 8506-4lp raid controller and succeeded in installing the FreeBSD 5.3-RELEASE on this machine in safe mode, but it boots only in safe mode. I've upgraded the kernel to stable, but there's no result. I don't know what's the difference between the safe mode and the normal mode, in fact. Anyway, I'd like to play around with the setings, and when there isn't a better solution, then I'd rather change the default boot method to safe mode. Please give me some advices, otherwise I'll get out of the time. The next week is the deadline, the server should work until then. Best regards, Gbor Kvesdn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
