Re: Boot Loader Issue
On Sun, 23 Jun 2013, Doug Hardie wrote: On 23 June 2013, at 20:39, Warren Block wbl...@wonkity.com wrote: On Sun, 23 Jun 2013, Doug Hardie wrote: I had to convert a system from GPT to MBR. All went fine till I tried to reboot the system. It gets to mountroot and dies trying to mount from ufs:/dev/ada0p2. That won't work. The loader should be getting that information from /etc/fstab. Have the entries there been changed? That was the problem. The system used GPT before and I can't believe I forgot to update fstab. That was a really dumb mistake. Not really, the only reason it occurred to me was because I've forgotten to do it many, many times. As Polytropon points out, labels can help avoid the problem. In this case, it would have had to be a UFS label on the filesystem: http://www.wonkity.com/~wblock/docs/html/labels.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Boot Loader Issue
On Sun, 23 Jun 2013 15:47:53 -0700, Doug Hardie wrote: I need to alter mountroot so it tries the right partition/slice. How do I do that? I couldn't find anything in the handbook on that. You need to install the GPT boot code, e. g. # gpart add -t freebsd-boot -l gpboot -b 40 -s 512K ad0 # gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ad0 See http://www.wonkity.com/~wblock/docs/html/disksetup.html for details. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Boot Loader Issue
On Sun, Jun 23, 2013 at 4:12 PM, Polytropon free...@edvax.de wrote: On Sun, 23 Jun 2013 15:47:53 -0700, Doug Hardie wrote: I need to alter mountroot so it tries the right partition/slice. How do I do that? I couldn't find anything in the handbook on that. You need to install the GPT boot code, e. g. # gpart add -t freebsd-boot -l gpboot -b 40 -s 512K ad0 Why the offset? Why 512k? # gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ad0 I think it's simpler to make an entry in /boot/loader.conf: vfs.root.mountfrom=ufs:/dev/ada0s1a ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Boot Loader Issue
On Sun, 23 Jun 2013, Doug Hardie wrote: I had to convert a system from GPT to MBR. All went fine till I tried to reboot the system. It gets to mountroot and dies trying to mount from ufs:/dev/ada0p2. That won't work. The loader should be getting that information from /etc/fstab. Have the entries there been changed? If I enter ufs:/dev/ada0s1a then the system boots fine and runs. I need to alter mountroot so it tries the right partition/slice. How do I do that? I couldn't find anything in the handbook on that. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-blocks.html has some information. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Boot Loader Issue
On Mon, 24 Jun 2013, Polytropon wrote: On Sun, 23 Jun 2013 15:47:53 -0700, Doug Hardie wrote: I need to alter mountroot so it tries the right partition/slice. How do I do that? I couldn't find anything in the handbook on that. You need to install the GPT boot code, e. g. # gpart add -t freebsd-boot -l gpboot -b 40 -s 512K ad0 # gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ad0 See http://www.wonkity.com/~wblock/docs/html/disksetup.html for details. That is GPT bootcode, but he was switching to MBR. That is documented in the second half of the link. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Boot Loader Issue
On Sun, 23 Jun 2013, Michael Sierchio wrote: On Sun, Jun 23, 2013 at 4:12 PM, Polytropon free...@edvax.de wrote: On Sun, 23 Jun 2013 15:47:53 -0700, Doug Hardie wrote: I need to alter mountroot so it tries the right partition/slice. How do I do that? I couldn't find anything in the handbook on that. You need to install the GPT boot code, e. g. # gpart add -t freebsd-boot -l gpboot -b 40 -s 512K ad0 Why the offset? Why 512k? Block 40 is the first 4K-aligned block after the 32 blocks occupied by the GPT. It won't hurt anything if the drive is not a 4K Advanced Format drive, won't really make a big difference if it is since bootcode is not really disk I/O-limited. Just good practice to keep everything aligned. 512K is the largest size of bootcode that will work. The loader loads the whole partition regardless of how large the bootcode is, and will fail with larger sizes. It's no loss of space because the first UFS partition will start at 1M. Why 1M? Because it's an unofficial standard, and aligned with 4K, 8K, 128K, and so on. This article talks about it a bit more: http://www.wonkity.com/~wblock/docs/html/ssd.html # gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ad0 I think it's simpler to make an entry in /boot/loader.conf: vfs.root.mountfrom=ufs:/dev/ada0s1a These are different things. The command is for a GPT disk, and the boot device being set is for MBR. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Boot Loader Issue
On 23 June 2013, at 20:39, Warren Block wbl...@wonkity.com wrote: On Sun, 23 Jun 2013, Doug Hardie wrote: I had to convert a system from GPT to MBR. All went fine till I tried to reboot the system. It gets to mountroot and dies trying to mount from ufs:/dev/ada0p2. That won't work. The loader should be getting that information from /etc/fstab. Have the entries there been changed? That was the problem. The system used GPT before and I can't believe I forgot to update fstab. That was a really dumb mistake. Thanks very much. If I enter ufs:/dev/ada0s1a then the system boots fine and runs. I need to alter mountroot so it tries the right partition/slice. How do I do that? I couldn't find anything in the handbook on that. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-blocks.html has some information. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Boot Loader Issue
On Sun, 23 Jun 2013 21:35:20 -0700, Doug Hardie wrote: On 23 June 2013, at 20:39, Warren Block wbl...@wonkity.com wrote: The loader should be getting that information from /etc/fstab. Have the entries there been changed? That was the problem. The system used GPT before and I can't believe I forgot to update fstab. That was a really dumb mistake. Thanks very much. If you can use labels instead of device names, this problem can be avoided. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FB 9.1 boot loader problem in VirtualBox
jb jb.1234abcd at gmail.com writes: jb jb.1234abcd at gmail.com writes: ... Next problem: the FB 9.1 dmesg differs on: - VB VM pnp bios: Bad PnP BIOS data checksum ... orm0: ISA Option ROM at iomem 0xc-0xc7fff pnpid ORM on isa0 Correction - on real hardware none of the above dmesg: ... isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 pmtimer0 on isa0 orm0: ISA Option ROMs at iomem 0xc-0xc,0xe-0xe pnpid ORM on isa0 sc0: System console at flags 0x100 on isa0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 ... That msg in FB VM: pnp bios: Bad PnP BIOS data checksum it means what is says - do not trust it; or also do not use PnP ? But it may also mean a problem accessing it in VM only, as opposed to a real machine. Searched Google, it shows often, but no clear interpretation. jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FB 9.1 boot loader problem in VirtualBox
jb jb.1234abcd at gmail.com writes: Hi, host=CentOS guest=FreeBSD in VirtualBox FB 9.1 installation seemed to be normal (there was a one page text at the end that quickly disappeared, but could not catch it ...), Perhaps those messages I could not catch were relevant, because it seems that the installation did not finish properly (most of base dirs and kernel dir were not populated) - it just died. I guessed that 192MB RAM assigned to VM was insufficient. This has been already reported for FB 9.1 recently. Next problem: the installation's dmesg shows net driver em0, which is Intel PRO/1000 - and this is how install offers to configure the network; but my host has Broadcom Corporation NetLink BCM5787M Gigabit Ethernet PCI Express, which is bge0 driver in FB. How to force it to discover the right net device during install, and/or after install ? Next problem: I selected powerd service during install, but after boot, there was error msg: starting powerd powerd lookup freq: No such file or directory /etc/rc: WARNING failed to start powerd Next problem: when I am logged out from FB, and I do (I tested it repeatedly) Machine-Close-Power off the machine to cloce VM with FB, then on subsequent VM Start and FB reboot I get error msgs: ... Trying to mount root from ufs:/dev/ada0s1a [rw]... WARNING: / was not properly dismounted ... Starting file system checks: ** SU+J Recovering /dev/ada0s1a ... but when I do Machine-Close-Send the shutdown signal there are no errors, just normal msgs: ... Trying to mount root from ufs:/dev/ada0s1a [rw]... ... Starting file system checks: /dev/ada0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS ... jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FB 9.1 boot loader problem in VirtualBox
On 06/01/2013 11:19, jb wrote: Next problem: the installation's dmesg shows net driver em0, which is Intel PRO/1000 - and this is how install offers to configure the network; but my host has Broadcom Corporation NetLink BCM5787M Gigabit Ethernet PCI Express, which is bge0 driver in FB. How to force it to discover the right net device during install, and/or after install ? This is normal for VirtualBox -- it doesn't matter what NIC the host has, VB always presents it as an em(4) interface to the guest. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: FB 9.1 boot loader problem in VirtualBox
On 06/01/2013 11:19, jb wrote: Next problem: I selected powerd service during install, but after boot, there was error msg: starting powerd powerd lookup freq: No such file or directory /etc/rc: WARNING failed to start powerd Again -- standard for VirtualBox hosts: powerd doesn't work -- the guest OS can't control the frequency of the host CPU, which is what you'ld expect thinking about it. Just disable powerd in /etc/rc.conf to get rid of the error message. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: FB 9.1 boot loader problem in VirtualBox
Matthew Seaman matthew at FreeBSD.org writes: On 06/01/2013 11:19, jb wrote: Next problem: the installation's dmesg shows net driver em0, which is Intel PRO/1000 - and this is how install offers to configure the network; but my host has Broadcom Corporation NetLink BCM5787M Gigabit Ethernet PCI Express, which is bge0 driver in FB. How to force it to discover the right net device during install, and/or after install ? This is normal for VirtualBox -- it doesn't matter what NIC the host has, VB always presents it as an em(4) interface to the guest. Cheers, Matthew OK. But I also could not ping: $ ping -c 1 google.com I have VM-Settings-Network Attached to NAT What is the correct setting here ? jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FB 9.1 boot loader problem in VirtualBox
On 06/01/2013 11:19, jb wrote: Next problem: when I am logged out from FB, and I do (I tested it repeatedly) Machine-Close-Power off the machine to cloce VM with FB, then on subsequent VM Start and FB reboot I get error msgs: ... Trying to mount root from ufs:/dev/ada0s1a [rw]... WARNING: / was not properly dismounted ... Starting file system checks: ** SU+J Recovering /dev/ada0s1a ... but when I do Machine-Close-Send the shutdown signal there are no errors, just normal msgs: ... Trying to mount root from ufs:/dev/ada0s1a [rw]... ... Starting file system checks: /dev/ada0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS ... Ummm... what did you expect to happen? 'Machine-Close-Power off' is essentially the same as ripping the power cord out of a physical machine. It's designed to stop the guest system no matter what: even if the guest is trapped in so tight a loop it can't respond to anything else. 'Machine-Close-Send shutdown' is more like pressing the power button on the front of most modern machines, in that what it does is signal the guest OS to shut itself off and power down the system after that. You can achieve the same effect from within the guest OS by typing: shutdown -p now 'Machine-Close-Send shutdown' is what you want to use routinely. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: FB 9.1 boot loader problem in VirtualBox
Matthew Seaman matthew at FreeBSD.org writes: On 06/01/2013 11:19, jb wrote: Next problem: I selected powerd service during install, but after boot, there was error msg: starting powerd powerd lookup freq: No such file or directory /etc/rc: WARNING failed to start powerd Again -- standard for VirtualBox hosts: powerd doesn't work -- the guest OS can't control the frequency of the host CPU, which is what you'ld expect thinking about it. Just disable powerd in /etc/rc.conf to get rid of the error message. Cheers, Matthew A general question: to what extent is FB Install aware of installation env (VB here) ? If so, would it make sense to sanitize it to avoid offering install options that are irrelevant/inappropriate ? jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FB 9.1 boot loader problem in VirtualBox
On 06/01/2013 11:52, jb wrote: Matthew Seaman matthew at FreeBSD.org writes: On 06/01/2013 11:19, jb wrote: Next problem: the installation's dmesg shows net driver em0, which is Intel PRO/1000 - and this is how install offers to configure the network; but my host has Broadcom Corporation NetLink BCM5787M Gigabit Ethernet PCI Express, which is bge0 driver in FB. How to force it to discover the right net device during install, and/or after install ? This is normal for VirtualBox -- it doesn't matter what NIC the host has, VB always presents it as an em(4) interface to the guest. OK. But I also could not ping: $ ping -c 1 google.com I have VM-Settings-Network Attached to NAT What is the correct setting here ? Not really enough information there to say exactly what has gone wrong. NAT+DHCP should work. You need: ifconfig_em0=DHCP in /etc/rc.conf obviously. Try tcpdump(1) on the external interface of your host system to see if the traffic shows up. You will also need to have a process called something like VBoxNetDHCP running on the host. Process name might be slightly different on different host OSes (I'm using MacOS X). It should be started automatically but no harm checking. If that hasn't led to a fix, please post the output of: ifconfig em0 netstat -rn from the guest system. If NAT won't work, you might try bridged mode -- this effectively makes the VM share your main host's NIC and gives it its own externally visible IP on the network. You generally need bridged mode if you want to run servers in the VM. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matt...@infracaninophile.co.uk signature.asc Description: OpenPGP digital signature
Re: FB 9.1 boot loader problem in VirtualBox
On 06/01/2013 12:09, jb wrote: A general question: to what extent is FB Install aware of installation env (VB here) ? If so, would it make sense to sanitize it to avoid offering install options that are irrelevant/inappropriate ? This is FreeBSD. It doesn't hold your hand and wipe the drool off your chin. You're assumed to know what you're doing, and to be able to configure your systems appropriately. And when you do know, and can configure things, then it doesn't get in your way. The installer doesn't know about all the various possible different execution environments it might get used in. To do so would add a lot of complexity for not very much gain to most users. Instead, it is targeted at the most common installation scenario: direct installation onto a PC with all the standard sort of capabilities.This should produce a working system for the vast majority of use cases, but you may need to go in and twiddle a few knobs and generally tune things up a bit to get the very best results. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: FB 9.1 boot loader problem in VirtualBox
jb wrote: [snip] But I also could not ping: $ ping -c 1 google.com I have VM-Settings-Network Attached to NAT What is the correct setting here ? Vbox will not allow ping and/or traceroute type traffic through NAT. It states this somewhere in the docs. This normal to NAT. I've used both NAT and bridged and have more recently come around to believing that bridged is the better of the two. Especially when/if you wish to serve content to the outside world. Trying to monkey around with the port forwarding rules of the NAT setup is for the birds. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FB 9.1 boot loader problem in VirtualBox
Matthew Seaman wrote: On 06/01/2013 12:09, jb wrote: A general question: to what extent is FB Install aware of installation env (VB here) ? If so, would it make sense to sanitize it to avoid offering install options that are irrelevant/inappropriate ? This is FreeBSD. It doesn't hold your hand and wipe the drool off your chin. You're assumed to know what you're doing, and to be able to configure your systems appropriately. And when you do know, and can configure things, then it doesn't get in your way. The installer doesn't know about all the various possible different execution environments it might get used in. To do so would add a lot of complexity for not very much gain to most users. Instead, it is targeted at the most common installation scenario: direct installation onto a PC with all the standard sort of capabilities.This should produce a working system for the vast majority of use cases, but you may need to go in and twiddle a few knobs and generally tune things up a bit to get the very best results. The converse may be applicable as well, that Vbox has configurability to know a little something about the environment for the proposed guest. When creating a new VM, you can choose BSD in the Operating System drop-down and then choose FreeBSD or FreebSD-64. I've had no trouble installing the 9.1 Release disk1 CD into a Vbox VM (amd64 version). What I have not done is tried all the various partitioning schemes available under Manual config. Possibly one, such as Dos MBR or BSD disklabel which I have not tried, may be broken boot-loading wise. I only went straight down the GPT road. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FB 9.1 boot loader problem in VirtualBox
Michael Powell nightrecon at hotmail.com writes: ... What I have not done is tried all the various partitioning schemes available under Manual config. Possibly one, such as Dos MBR or BSD disklabel which I have not tried, may be broken boot-loading wise. I only went straight down the GPT road. -Mike I have done Manual MBR paritioning here and it worked. jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FB 9.1 boot loader problem in VirtualBox
Michael Powell wrote: [snip] The converse may be applicable as well, that Vbox has configurability to know a little something about the environment for the proposed guest. When creating a new VM, you can choose BSD in the Operating System drop-down and then choose FreeBSD or FreebSD-64. I've had no trouble installing the 9.1 Release disk1 CD into a Vbox VM (amd64 version). What I have not done is tried all the various partitioning schemes available under Manual config. Possibly one, such as Dos MBR or BSD disklabel which I have not tried, may be broken boot-loading wise. I only went straight down the GPT road. Addendum: Also, which I forgot and left out in my haste, I think I have seen most reports of people having trouble seems to have revolved around the Auto partitioning scheme choice in the new bsdinstaller. I avoided it and went straight to Manual as I prefer to do my own. IIRC the Auto provides one slice and one partition and throws everything in there. I still wish to have separate partitions for /, /usr, /var, etc, so I've also never tried the Auto scheme either. Maybe if this is the problem the OP may wish to try avoiding Auto and proceed directly to Manual. Might rule something out. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FB 9.1 boot loader problem in VirtualBox
On 01/06/2013 01:51 PM, Michael Powell wrote: Michael Powell wrote: [snip] The converse may be applicable as well, that Vbox has configurability to know a little something about the environment for the proposed guest. When creating a new VM, you can choose BSD in the Operating System drop-down and then choose FreeBSD or FreebSD-64. I've had no trouble installing the 9.1 Release disk1 CD into a Vbox VM (amd64 version). What I have not done is tried all the various partitioning schemes available under Manual config. Possibly one, such as Dos MBR or BSD disklabel which I have not tried, may be broken boot-loading wise. I only went straight down the GPT road. Addendum: Also, which I forgot and left out in my haste, I think I have seen most reports of people having trouble seems to have revolved around the Auto partitioning scheme choice in the new bsdinstaller. I avoided it and went straight to Manual as I prefer to do my own. IIRC the Auto provides one slice and one partition and throws everything in there. I still wish to have separate partitions for /, /usr, /var, etc, so I've also never tried the Auto scheme either. Maybe if this is the problem the OP may wish to try avoiding Auto and proceed directly to Manual. Might rule something out. -Mike Auto configures your system with three gpt partitions freebsd-boot where the bootstrap code is installed freebsd-ufs which is the / partition freebsd-swap for swap obviously There are no slices involved in the default installation. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FB 9.1 boot loader problem in VirtualBox
On Sun, 6 Jan 2013 12:09:12 + (UTC), jb wrote: A general question: to what extent is FB Install aware of installation env (VB here) ? FreeBSD can only detect hardware certainly to a specific point. The idea behind virtualization is that it presents non-existent devices as if they were real. This technology has become so great that many operating systems don't distinguish anymore between real hardware and emulated hardware. :-) If so, would it make sense to sanitize it to avoid offering install options that are irrelevant/inappropriate ? FreeBSD is a general-purpose operating system. It can be used for desktops, for laptops, servers without GPU and keyboard, and for virtual environments. This is all possible with the _same_ OS distribution. Disabling things the OS or the installer can do in a way that it does _not_ do things depending on arbitrary circumstances (instead of operator decisions) doesn't sound as an ideal solution, it looks more like hey look at me, I'm a crippled OS installer which only works for one specific virtualisation environment, and when you're done with installation, there could be things you expect to work which I won't let you do simply because! However, there _are_ tailored appliances of FreeBSD which specificlally target virtualied environments. They are based on FreeBSD as the OS, and add certain preinstallation and preconfiguration. Just have a look at this: http://www.virtualbsd.info/ This interesting project even skips the step of manual installation. Instead it offers a fully functional image for VMware and VirtualBox. It builds on the foundation of FreeBSD, instead of demanding a change of the OS to fit one limited use case by predefining settings that might be inappropriate (or leaving out functionality that would be irrelevant) in this _one_ application. The strength of a general-purpose OS is that it can be applied in many settings. It's the administrator's task to deal with the implications that this set of features implies for any specific case. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FB 9.1 boot loader problem in VirtualBox
On Sun, 6 Jan 2013, Matthew Seaman wrote: On 06/01/2013 11:19, jb wrote: Next problem: the installation's dmesg shows net driver em0, which is Intel PRO/1000 - and this is how install offers to configure the network; but my host has Broadcom Corporation NetLink BCM5787M Gigabit Ethernet PCI Express, which is bge0 driver in FB. How to force it to discover the right net device during install, and/or after install ? This is normal for VirtualBox -- it doesn't matter what NIC the host has, VB always presents it as an em(4) interface to the guest. Under Network/Adapter1/Advanced, there are other choices for the emulated adapter type. Intel PRO/1000 MT Desktop (82540EM) is the default, and usually a good choice. The first choice is PCnet-PCI II (Am79C970A), and that one works with FreeBSD also. That first one is capable of PXE-booting in bridged mode, where the emulated Intel cards are not. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FB 9.1 boot loader problem in VirtualBox
On Sun, 6 Jan 2013, Michael Powell wrote: Matthew Seaman wrote: On 06/01/2013 12:09, jb wrote: A general question: to what extent is FB Install aware of installation env (VB here) ? If so, would it make sense to sanitize it to avoid offering install options that are irrelevant/inappropriate ? This is FreeBSD. It doesn't hold your hand and wipe the drool off your chin. You're assumed to know what you're doing, and to be able to configure your systems appropriately. And when you do know, and can configure things, then it doesn't get in your way. The installer doesn't know about all the various possible different execution environments it might get used in. To do so would add a lot of complexity for not very much gain to most users. Instead, it is targeted at the most common installation scenario: direct installation onto a PC with all the standard sort of capabilities.This should produce a working system for the vast majority of use cases, but you may need to go in and twiddle a few knobs and generally tune things up a bit to get the very best results. The converse may be applicable as well, that Vbox has configurability to know a little something about the environment for the proposed guest. When creating a new VM, you can choose BSD in the Operating System drop-down and then choose FreeBSD or FreebSD-64. I've had no trouble installing the 9.1 Release disk1 CD into a Vbox VM (amd64 version). What I have not done is tried all the various partitioning schemes available under Manual config. Possibly one, such as Dos MBR or BSD disklabel which I have not tried, may be broken boot-loading wise. I only went straight down the GPT road. MBR works also. Which is to be expected, it's an emulated machine, and isn't any more picky about boot blocks than physical hardware. Probably less picky, really. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FB 9.1 boot loader problem in VirtualBox
jb jb.1234abcd at gmail.com writes: ... Next problem: the FB 9.1 dmesg differs on: - VB VM pnp bios: Bad PnP BIOS data checksum ... orm0: ISA Option ROM at iomem 0xc-0xc7fff pnpid ORM on isa0 - on real hardware none of the above jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FB 9.1 boot loader problem in VirtualBox
Matthew Seaman matthew at FreeBSD.org writes: On 06/01/2013 11:19, jb wrote: Next problem: I selected powerd service during install, but after boot, there was error msg: starting powerd powerd lookup freq: No such file or directory /etc/rc: WARNING failed to start powerd Again -- standard for VirtualBox hosts: powerd doesn't work -- the guest OS can't control the frequency of the host CPU, which is what you'ld expect thinking about it. Just disable powerd in /etc/rc.conf to get rid of the error message. Cheers, Matthew If so, then bsdinstall should stop offering powerd as a service during installation (regardless of whethter in real or virtual env). It can discover this condition with checking for lack of sysctl -a | grep dev.cpu.0.freq sysctl -a | grep dev.cpu.0.freq_levels in /usr/libexec/bsdinstall/services, exactly as it does with if (sysctlnametomib(dev.cpu.0.freq, freq_mib, len)) err(1, lookup freq); ... if (sysctlnametomib(dev.cpu.0.freq_levels, levels_mib, len)) err(1, lookup freq_levels); in /usr/sbin/powerd (via /etc/rc.d/powerd) - see powerd.c. jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FB 9.1 boot loader problem in VirtualBox
Matthew Seaman matthew at FreeBSD.org writes: On 06/01/2013 11:19, jb wrote: Next problem: when I am logged out from FB, and I do (I tested it repeatedly) Machine-Close-Power off the machine to cloce VM with FB, then on subsequent VM Start and FB reboot I get error msgs: ... Trying to mount root from ufs:/dev/ada0s1a [rw]... WARNING: / was not properly dismounted ... Starting file system checks: ** SU+J Recovering /dev/ada0s1a ... but when I do Machine-Close-Send the shutdown signal there are no errors, just normal msgs: ... Trying to mount root from ufs:/dev/ada0s1a [rw]... ... Starting file system checks: /dev/ada0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS ... Ummm... what did you expect to happen? 'Machine-Close-Power off' is essentially the same as ripping the power cord out of a physical machine. It's designed to stop the guest system no matter what: even if the guest is trapped in so tight a loop it can't respond to anything else. 'Machine-Close-Send shutdown' is more like pressing the power button on the front of most modern machines, in that what it does is signal the guest OS to shut itself off and power down the system after that. You can achieve the same effect from within the guest OS by typing: shutdown -p now 'Machine-Close-Send shutdown' is what you want to use routinely. Cheers, Matthew Right, but the wordings are unfortunate and counterintuitive/misleading: 'Machine-Close-Send shutdown' means to 'shutdown -p now' (equivalent to 'poweroff') of Guest, followed by unforced Close of VM. 'Machine-Close-Power off' means Kill VM' without regard of the Guest - but the Power off in its name may make user believe that there is Poweroff (orderly shutdown, poweroff) involved as part of the process. It would be better, in my opinion, if these options were called Machine-Close-Shutdown-Guest Machine-Close-Kill-Guest No margin for error/misunderstanding. jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FB 9.1 boot loader problem in VirtualBox
Matthew Seaman m.seaman at infracaninophile.co.uk writes: ... There is no problem with interface em0, NAT, manual/DHCP config, and ping or traceroute. jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FB 9.1 boot loader problem in VirtualBox
On Sun, 6 Jan 2013 19:02:43 + (UTC), jb wrote: Right, but the wordings are unfortunate and counterintuitive/misleading: 'Machine-Close-Send shutdown' means to 'shutdown -p now' (equivalent to 'poweroff') of Guest, followed by unforced Close of VM. 'Machine-Close-Power off' means Kill VM' without regard of the Guest - but the Power off in its name may make user believe that there is Poweroff (orderly shutdown, poweroff) involved as part of the process. It would be better, in my opinion, if these options were called Machine-Close-Shutdown-Guest Machine-Close-Kill-Guest No margin for error/misunderstanding. A need for this interpretation may arise for those who did not do computing in the pre-ATX era (at least in the PC sector). Power off means _power off_, typically AC power off, a switch that would disconnect the mains source, so there is no way for the OS to shut anything down. On an AT PC, there was no real way to tell the OS to perform a shutdown, so shutdown -h would be the equivalent command to be issued by the operator, followed by mechanically switching the machine off. A command like shutdown -p combined both things when ATX (with APM, later with ACPI) became common. Similarly, emergency power off would carry this meaning: stop the machine at all costs NOW. A different term, delayed power off, was common on machines to allow the OS to perform the proper shutdown steps and _then_ power the machine off, but it's not common anymore. However, your transition of this knowledge to the terminology to be used in combination with _virtual_ machines makes sense. Maybe that wording is really not optimal. Kill guest matches today's understanding, but could possibly be formed better in regards of future use (like the power off vs. shutdown difference that was totally clear in the 1990's, but maybe isn't as clear anymore today). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FB 9.1 boot loader problem in VirtualBox
Polytropon freebsd at edvax.de writes: ... However, your transition of this knowledge to the terminology to be used in combination with _virtual_ machines makes sense. Maybe that wording is really not optimal. Kill guest matches today's understanding, but could possibly be formed better in regards of future use (like the power off vs. shutdown difference that was totally clear in the 1990's, but maybe isn't as clear anymore today). Well, I remember some time ago there were some changes done to shutdown, halt, poweroff commands and their interpretation/implementation. Since then Confusion Reigns Supreme ! See Google search: difference shutdown poweroff Enjoy it -:) jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FB 9.1 boot loader problem in VirtualBox
On Sun, 6 Jan 2013 20:02:04 + (UTC), jb wrote: Polytropon freebsd at edvax.de writes: ... However, your transition of this knowledge to the terminology to be used in combination with _virtual_ machines makes sense. Maybe that wording is really not optimal. Kill guest matches today's understanding, but could possibly be formed better in regards of future use (like the power off vs. shutdown difference that was totally clear in the 1990's, but maybe isn't as clear anymore today). Well, I remember some time ago there were some changes done to shutdown, halt, poweroff commands and their interpretation/implementation. Since then Confusion Reigns Supreme ! See Google search: difference shutdown poweroff I know it's just about terminology, and if you leave the PC sector, you'll be surprised about different interpretation and even deviating terminology. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FB 9.1 boot loader problem in VirtualBox
Hi, host=CentOS guest=FreeBSD in VirtualBox FB 9.1 installation seemed to be normal (there was a one page text at the end that quickly disappeared, but could not catch it ...), virtual disk was set up as ada0 ada0s1 BSD ada0s1a / ada0s1b swap but after reboot: No /boot/loader FreeBSD/i386 boot Default: 0:ad(0,a)/boot/kernel/kernel boot: No /boot/kernel/kernel FreeBSD/i386 boot Default: 0:ad(0,a)/boot/kernel/kernel boot: _ jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Graphic /boot/loader menu
On Sun, Dec 18, 2011 at 6:24 PM, Conrad J. Sabatier conr...@cox.net wrote: Myself, personally, as much as I dislike the look of FreeBSD's boot menu, it does have the advantage of being very lightweight and adding minimal overhead to the booting process, which is an important consideration for a lot of people, no doubt. Â YMMV. It's important to us running FreeBSD on headless machines, hooked up to remote serial consoles. A GUI boot menu wouldn't work there, since these machines don't even have VGA circuitry. Let us know if you learn anything interesting re: this issue. -- Conrad J. Sabatier conr...@cox.net Regards, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Graphic /boot/loader menu
On Sat, 17 Dec 2011 11:13:44 +0800 Fbsd8 fb...@a1poweruser.com wrote: What ever happened to the project to add an graphic boot/loader option menu? http://wiki.freebsd.org/OliverFromme/BootLoader I agree that FreeBSD could use a facelift in certain areas (the boot screen looks horribly antiquated and DOSian), but it seems the majority of FreeBSD developers are either not especially interested or are busy enough already working on other things. You'd probably do best to contact the Wiki page's author directly: Oliver Fromme o...@freebsd.org The last update to the Wiki page was in 2009, so this project may be dead in the water. Only Oliver could tell you for sure. Another possibility would be to contact the PC-BSD folks and see if they might let you borrow some of their work for porting over to FreeBSD (assuming you have some developer skills yourself). Then again, if this is *really* important to you, you could always just try switching over to PC-BSD. It does seem to be essentially the same as FreeBSD, but with a number of GUI tools added. Myself, personally, as much as I dislike the look of FreeBSD's boot menu, it does have the advantage of being very lightweight and adding minimal overhead to the booting process, which is an important consideration for a lot of people, no doubt. YMMV. Let us know if you learn anything interesting re: this issue. -- Conrad J. Sabatier conr...@cox.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Graphic /boot/loader menu
What ever happened to the project to add an graphic boot/loader option menu? http://wiki.freebsd.org/OliverFromme/BootLoader ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: boot/loader splash image
wayne mitchell wrote: hey got question/problem for /boot/loader system: freeBSD 8.1-RELEASE GENERIC trying to get a bitmap onscreen for bootup have read man page for all boot associated stuff (loader.conf...) and followed instructions using following values in /boot/loader.conf : bitmap_load=YES# have tried commenting this out also vesa_load=YES splash_bmp_load=YES bitmap_name=/boot/splash.bmp the splash.bmp size is about 900x700 does not work am using /boot/loader.rc as preset (includes loader.4th and beastie.4th) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Try putting vesa_load=YES first. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: boot/loader splash image
Sunday, July 17, 2011, 6:07:57 PM, Fbsd8 wrote: wayne mitchell wrote: hey got question/problem for /boot/loader system: freeBSD 8.1-RELEASE GENERIC trying to get a bitmap onscreen for bootup have read man page for all boot associated stuff (loader.conf...) and followed instructions using following values in /boot/loader.conf : bitmap_load=YES# have tried commenting this out also vesa_load=YES splash_bmp_load=YES bitmap_name=/boot/splash.bmp the splash.bmp size is about 900x700 does not work am using /boot/loader.rc as preset (includes loader.4th and beastie.4th) Try putting vesa_load=YES first. The image must also be 256-color. -- Best regards, Duanemailto:du...@duanemail.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: boot/loader splash image
Fbsd8 fb...@a1poweruser.com writes: wayne mitchell wrote: hey got question/problem for /boot/loader system: freeBSD 8.1-RELEASE GENERIC trying to get a bitmap onscreen for bootup have read man page for all boot associated stuff (loader.conf...) and followed instructions using following values in /boot/loader.conf : bitmap_load=YES# have tried commenting this out also vesa_load=YES splash_bmp_load=YES bitmap_name=/boot/splash.bmp the splash.bmp size is about 900x700 does not work am using /boot/loader.rc as preset (includes loader.4th and beastie.4th) Try putting vesa_load=YES first. It's not that useful without SC_PIXEL_MODE which is not in GENERIC. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Boot loader/kernel error
On Fri, Oct 08, 2010 at 07:09:48PM -0700, Hac Phan wrote: Hi, I'm having trouble with a machine that was recently rebooted and will no longer boot correctly. The boot process hangs with the following screen: Loading /boot/defaults/loader.conf It sounds like there is something in /boot/loader.conf, or another file that is sourced by /boot/defaults/loader.conf that it doesn't like. - The cursor does not move and no other text is displayed. After about 10 minutes, the boot finishes (without the splash screen) and displays the login prompt. I tried to login but it timed out after 300 seconds. The server was using a custom built kernel. I tried to get the GENERIC kernel from the livefs ISO and restore it via FIXIT console, but I realized that I actually don't know how to do that... So how do I go about fixing this? Thanks in advance. -- I'd try and boot into single user mode and edit the offending file: maybe comment out the various lines until you find the line that's causing the problem. I think that as you can get to a login prompt, you should be able to boot single user and shouldn't have to bother with the CD. Touch wood, I've never had a problem that required booting external media to fix, so I can't help you in that department. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Boot loader/kernel error
In the last episode (Oct 08), Hac Phan said: I'm having trouble with a machine that was recently rebooted and will no longer boot correctly. The boot process hangs with the following screen: Loading /boot/defaults/loader.conf - The cursor does not move and no other text is displayed. After about 10 minutes, the boot finishes (without the splash screen) and displays the login prompt. I tried to login but it timed out after 300 seconds. That behaviour is consistent with having a serial console setup in /boot/loader.conf . As soon as the loader sees console=comconsole, it will switch its output and the kernel's output to com1. If com1 doesn't exist, it will take a long time to boot. When the kernel finally finishes, init still start a getty on the physical console, which is when you see the login prompt. If you can boot your fixit CD and get the root filessytem mountd read/write, try commenting out that comconsole line. Most bad loader.conf problems can be fixed by hitting space just before the loader starts up the kernel and unsetting the bad variable, but comconsole is one of the commands that it runs immediately, and I don't think you can stop the loader from parsing loader.conf. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Boot loader/kernel error
On Oct 9, 2010, at 10:58 AM, Dan Nelson wrote: In the last episode (Oct 08), Hac Phan said: I'm having trouble with a machine that was recently rebooted and will no longer boot correctly. The boot process hangs with the following screen: Loading /boot/defaults/loader.conf - The cursor does not move and no other text is displayed. After about 10 minutes, the boot finishes (without the splash screen) and displays the login prompt. I tried to login but it timed out after 300 seconds. That behaviour is consistent with having a serial console setup in /boot/loader.conf . As soon as the loader sees console=comconsole, it will switch its output and the kernel's output to com1. If com1 doesn't exist, it will take a long time to boot. When the kernel finally finishes, init still start a getty on the physical console, which is when you see the login prompt. If you can boot your fixit CD and get the root filessytem mountd read/write, try commenting out that comconsole line. Most bad loader.conf problems can be fixed by hitting space just before the loader starts up the kernel and unsetting the bad variable, but comconsole is one of the commands that it runs immediately, and I don't think you can stop the loader from parsing loader.conf. In `/boot/loader.rc', I'm reviewing the ANS FICL (that's `Forth Inspired Command Language') and I see that it does indeed parse `/boot/loader.con' before throwing up the menu (once the menu is up, then you can escape to the loader prompt by selecting the appropriate numeric option -- in the new loader, the old loader you simply had to press space-bar during the count-down to boot). The bread-crumbs in `/boot/loader.rc' lead us off to `/boot/loader.4th' if you want to know precisely how `/boot/loader.conf' is read into the environment (note: real work for `comconsole=blah' is done in `/boot/support.4th' in the chain: include_conf_files - load_conf - process_conf - process_assignment - set_environment_variable; and the last part of that chain reveals that the internal FICL word `set' is used to set an environment variable, so comconsole should be visible at the interactive prompt via the `show' keyword). So, in reality, one ought to be able to do the following to deconfigure the comconsole setting... 1. Boot up the machine 2. Interrupt the boot loader (older FreeBSD, hit space, newer menu-based loader, choose the menu option to escape to the loader prompt) 3. Enter: show 4. Verify that comconsole is set (because loader.rc shows us `/boot/loader.conf' is loaded before the menu is thrown up) 5. Enter: unset comconsole 6. Enter: show 7. Verify that comconsole is no longer set 8. Enter: boot NOTE: If you prefer to boot into single-user mode, enter instead: boot -s NOTE: Boot should no longer be dumping to serial and instead you should see a normal boot process on the console. 9. Login and change /boot/loader.conf to remove comconsole=... NOTE: I do realize that in /boot/loader.4th, the FICL native `boot' keyword has been overridden, but it doesn't appear that anything is munged in the environment prior to execution of the loaded kernel, so the kernel should inherit the environment variables just as they appear when `show' is executed at the loader prompt. -- Devin (full sig at bottom) -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Cheers, Devin Teske - CONTACT INFORMATION - Business Solutions Consultant II FIS - fisglobal.com 510-735-5650 Mobile 510-621-2038 Office 510-621-2020 Office Fax 909-477-4578 Home/Fax devin.te...@fisglobal.com - LEGAL DISCLAIMER - This message contains confidential and proprietary information of the sender, and is intended only for the person(s) to whom it is addressed. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you have received this message in error, please notify the e-mail sender immediately, and delete the original message without making a copy. - END TRANSMISSION - ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: change default keymap for /boot/loader?
Dear Sir/Madam, Your email was unable reach the intended person that you were sending it to. For more information on our business please click on the following link: [1]Click here for our website We look forward to your continued business in the future. Regards, Webmaster References 1. http://www.downwind.com.au/avdir/rd.php?id=7564 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
change default keymap for /boot/loader?
hi there, just wanted to ask if there's a way to change the default US keymap for /boot/loader to something else? i have options UKBD_DFLT_KEYMAP makeoptions UKBD_DFLT_KEYMAP=german.iso in my kernel conf, however this doesn't seem to apply to /boot/loader. cheers. alex -- a13x ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD/amd: boot/loader ignores usb-keyboard
Hello, when i switched to an usb-keyboard some month ago, i realized, that boot/loader ignores input from this device. The bootmanager accepts input, loader not. Is there any configuration-parameter to fix this? Andreas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: change default keymap for /boot/loader?
On Tue, 17 Aug 2010 13:15:43 +, Alexander Best arun...@freebsd.org wrote: hi there, just wanted to ask if there's a way to change the default US keymap for /boot/loader to something else? i have options UKBD_DFLT_KEYMAP makeoptions UKBD_DFLT_KEYMAP=german.iso in my kernel conf, however this doesn't seem to apply to /boot/loader. I have noted this behaviour already in FreeBSD 7; in 5, I had both german settings for AT and USB keyboard - WORKING. Maybe support has been dropped? Is ignored? Hmmm... Anyway, I never noticed the boot loader was interested in that setting. It became active when booting into single user mode (boot -s, which had to be entered according to the US keymap). This is the whole set of options for the kernel: options SC_DFLT_FONT makeoptions SC_DFLT_FONT=iso options ATKBD_DFLT_KEYMAP makeoptions ATKBD_DFLT_KEYMAP=german.iso options UKBD_DFLT_KEYMAP makeoptions UKBD_DFLT_KEYMAP=german.iso I also included the ISO font for the syscons driver so the german specific letters could be displayed. Coming back to your basic question: I don't think there's a way to modify the early stage loader keymap. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Upgrading Boot Loader
Hi, I want to update my boot loader based on upgrading to FreeBSD 8.1. I originally installed FreeBSD 8.0 using the zfsinstall utility available at http://mfsbsd.vx.sk/ and so my tank zpool is currently using version 13, whereas my other non-boot zpool is using version 14. After upgrading (via make buildworld buildkernel installkernel installworld) to FreeBSD 8.1, running zpool status tells me: The pool is formatted using an older on-disk format. The pool can still be used, but some features are unavailable. Upgrade the pool using 'zpool upgrade'. Once this is done, the pool will no longer be accessible on older software versions. I vaguely remember reading that the zfsboot and/or zfsloader need to be updated properly before you upgrade your root zfs pool or the loader won't be able to boot from that partition. So, my question is: how do I update the zfsboot and/or zfsloader to the new version? I've read that bsdlabel can install new boot code, but I'm not sure which one of those files (or both) need to be used. My best guess is that I need to run: bsdlabel -B -b /boot/zfsboot Is that correct? Is there anything else I should do? What's the proper way to roll back in the event that the system becomes unbootable? Tim Gustafson Baskin School of Engineering UC Santa Cruz t...@soe.ucsc.edu 831-459-5354 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrading Boot Loader
02.08.2010 21:49, Tim Gustafson МапОÑав(ла): Hi, I want to update my boot loader based on upgrading to FreeBSD 8.1. I originally installed FreeBSD 8.0 using the zfsinstall utility available at http://mfsbsd.vx.sk/ and so my tank zpool is currently using version 13, whereas my other non-boot zpool is using version 14. After upgrading (via make buildworld buildkernel installkernel installworld) to FreeBSD 8.1, running zpool status tells me: The pool is formatted using an older on-disk format. The pool can still be used, but some features are unavailable. Upgrade the pool using 'zpool upgrade'. Once this is done, the pool will no longer be accessible on older software versions. I vaguely remember reading that the zfsboot and/or zfsloader need to be updated properly before you upgrade your root zfs pool or the loader won't be able to boot from that partition. So, my question is: how do I update the zfsboot and/or zfsloader to the new version? I've read that bsdlabel can install new boot code, but I'm not sure which one of those files (or both) need to be used. My best guess is that I need to run: bsdlabel -B -b /boot/zfsboot Is that correct? Is there anything else I should do? What's the proper way to roll back in the event that the system becomes unbootable? Nope. Read http://www.mail-archive.com/freebsd-sta...@freebsd.org/msg103917.html You need the dd sequence. And you need to do that on exported pool. -- Sphinx of black quartz judge my vow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrading Boot Loader
Nope. Read http://www.mail-archive.com/freebsd-sta...@freebsd.org/msg103917.html You need the dd sequence. And you need to do that on exported pool. So, just to be clear, I need to boot off a USB key (which will then allow me to write to ad8 and ad10, my two boot zpool devices), and then: dd if=/boot/zfsboot of=/dev/ad8 bs=512 count=1 dd if=/boot/zfsboot of=/dev/ad10 bs=512 count=1 dd if=/boot/zfsboot of=/dev/ad8 bs=512 skip=1 seek=1024 dd if=/boot/zfsboot of=/dev/ad10 bs=512 skip=1 seek=1024 And that assumes that I copy the newly-compiled zfsboot to the USB key after creating it, correct? Tim Gustafson Baskin School of Engineering UC Santa Cruz t...@soe.ucsc.edu 831-459-5354 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrading Boot Loader
02.08.2010 22:11, Tim Gustafson wrote: Nope. Read http://www.mail-archive.com/freebsd-sta...@freebsd.org/msg103917.html You need the dd sequence. And you need to do that on exported pool. So, just to be clear, I need to boot off a USB key (which will then allow me to write to ad8 and ad10, my two boot zpool devices), and then: dd if=/boot/zfsboot of=/dev/ad8 bs=512 count=1 dd if=/boot/zfsboot of=/dev/ad10 bs=512 count=1 dd if=/boot/zfsboot of=/dev/ad8 bs=512 skip=1 seek=1024 dd if=/boot/zfsboot of=/dev/ad10 bs=512 skip=1 seek=1024 And that assumes that I copy the newly-compiled zfsboot to the USB key after creating it, correct? Yes. PS: I've just recently changed my mind and moved from dedicated vdevs to gpart. This gives possibility of: 1. Having raw swap partition suitable for swapping/dumping. 2. Updating bootcode online without loosing uptime. Just in expense of some kilobytes of disk space. -- Sphinx of black quartz judge my vow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrading Boot Loader
PS: I've just recently changed my mind and moved from dedicated vdevs to gpart. This gives possibility of: 1. Having raw swap partition suitable for swapping/dumping. 2. Updating bootcode online without loosing uptime. Just in expense of some kilobytes of disk space. I too am using gpart to partition the drives: ad8 and ad10 are partitioned using gpart. I'm attaching the output of gpart list to this e-mail. Is there an easier/better way to upgrade the boot loader with gpart partitions? Tim Gustafson Baskin School of Engineering UC Santa Cruz t...@soe.ucsc.edu 831-459-5354Geom name: ad8 fwheads: 16 fwsectors: 63 last: 1953525134 first: 34 entries: 128 scheme: GPT Providers: 1. Name: ad8p1 Mediasize: 65536 (64K) Sectorsize: 512 Mode: r0w0e0 rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f label: (null) length: 65536 offset: 17408 type: freebsd-boot index: 1 end: 161 start: 34 2. Name: ad8p2 Mediasize: 17179869184 (16G) Sectorsize: 512 Mode: r1w1e1 rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b label: (null) length: 17179869184 offset: 82944 type: freebsd-swap index: 2 end: 33554593 start: 162 3. Name: ad8p3 Mediasize: 983024916992 (916G) Sectorsize: 512 Mode: r1w1e1 rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b label: (null) length: 983024916992 offset: 17179952128 type: freebsd-zfs index: 3 end: 1953525134 start: 33554594 Consumers: 1. Name: ad8 Mediasize: 1000204886016 (932G) Sectorsize: 512 Mode: r2w2e4 Geom name: ad10 fwheads: 16 fwsectors: 63 last: 1953525134 first: 34 entries: 128 scheme: GPT Providers: 1. Name: ad10p1 Mediasize: 65536 (64K) Sectorsize: 512 Mode: r0w0e0 rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f label: (null) length: 65536 offset: 17408 type: freebsd-boot index: 1 end: 161 start: 34 2. Name: ad10p2 Mediasize: 17179869184 (16G) Sectorsize: 512 Mode: r0w0e0 rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b label: (null) length: 17179869184 offset: 82944 type: freebsd-swap index: 2 end: 33554593 start: 162 3. Name: ad10p3 Mediasize: 983024916992 (916G) Sectorsize: 512 Mode: r1w1e1 rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b label: (null) length: 983024916992 offset: 17179952128 type: freebsd-zfs index: 3 end: 1953525134 start: 33554594 Consumers: 1. Name: ad10 Mediasize: 1000204886016 (932G) Sectorsize: 512 Mode: r1w1e2 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrading Boot Loader
02.08.2010 22:29, Tim Gustafson МапОÑав(ла): PS: I've just recently changed my mind and moved from dedicated vdevs to gpart. This gives possibility of: 1. Having raw swap partition suitable for swapping/dumping. 2. Updating bootcode online without loosing uptime. Just in expense of some kilobytes of disk space. I too am using gpart to partition the drives: ad8 and ad10 are partitioned using gpart. I'm attaching the output of gpart list to this e-mail. Is there an easier/better way to upgrade the boot loader with gpart partitions? Then you have no need in zfsboot, you shoud use gptzfsboot instead. gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad8 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad10 This will install Protective MBR to first disk sector and bootcode to first partition. You can backup them just-in-case or update one disk and try to boot from it leaving second as the known to work solution. -- Sphinx of black quartz judge my vow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrading Boot Loader
On 02/08/2010 20:29:41, Tim Gustafson wrote: PS: I've just recently changed my mind and moved from dedicated vdevs to gpart. This gives possibility of: 1. Having raw swap partition suitable for swapping/dumping. 2. Updating bootcode online without loosing uptime. Just in expense of some kilobytes of disk space. I too am using gpart to partition the drives: ad8 and ad10 are partitioned using gpart. I'm attaching the output of gpart list to this e-mail. Is there an easier/better way to upgrade the boot loader with gpart partitions? Step 5 from: http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror All you need is some bootable media with the latest gptzfsloader -- either 8.1-RELEASE or a recent 8.1-STABLE or 9-CURRENT snapshot. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Upgrading Boot Loader
gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad8 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad10 When I run this, I get: r...@foo: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad10 ad10 has bootcode Does that mean it was successful, or that no change was made? Tim Gustafson Baskin School of Engineering UC Santa Cruz t...@soe.ucsc.edu 831-459-5354 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrading Boot Loader
02.08.2010 23:53, Tim Gustafson wrote: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad8 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad10 When I run this, I get: r...@foo: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad10 ad10 has bootcode Does that mean it was successful, or that no change was made? Successfull. -- Sphinx of black quartz judge my vow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrading Boot Loader
Does that mean it was successful, or that no change was made? Successful. Awesome, thanks! Tim Gustafson Baskin School of Engineering UC Santa Cruz t...@soe.ucsc.edu 831-459-5354 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Upgrading Boot Loader
Volodymyr == Volodymyr Kostyrko c.kw...@gmail.com writes: Volodymyr 02.08.2010 23:53, Tim Gustafson wrote: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad8 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad10 When I run this, I get: r...@foo: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad10 ad10 has bootcode Does that mean it was successful, or that no change was made? Volodymyr Successfull. I looked for that text in geom (which is linked to gpart, I think), and didn't find it, or I'd be submitting a patch. But ad10 has bootcode should really say something that makes it clearer so this question doesn't come up again. I know *I* had this question too. Maybe new ad10 bootcode successfully installed or something. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 mer...@stonehenge.com URL:http://www.stonehenge.com/merlyn/ Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: boot loader too large
Hey A 64kb freebsd-boot partition should be more than plenty for what you want to do, see my setup at: http://freebsd.pastebin.com/QS6MnNKc If you want to setup a ZFS boot/root configuration and make your life easier, just use the installation script provided by the guy who wrote ManageBE: http://anonsvn.h3q.com/projects/freebsd-patches/browser/manageBE/create-zfsboot-gpt_livecd.sh - Sincerely, Dan Naumov ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: boot loader too large
Dan Naumov wrote: Hey A 64kb freebsd-boot partition should be more than plenty for what you want to do, see my setup at: http://freebsd.pastebin.com/QS6MnNKc Interesting. I read somewhere that the boot partition should not be too large as the entire partition is loaded into memory. I re-partitioned my drive to create a 64KiB freebsd-boot partition and I no longer get the error. It would appear that there is an undocumented maximum size to the freebsd-boot partition. In my case, a 1MiB boot partition was too large. Now I need to teach gptboot in ad4p1 how to find my root partition in ad4p4 without manual intervention. Is there a GPT equivalent to boot0cfg? gptboot currently attempts to boot: 0:ad(0p2)/boot/kernel/kernel I'd like it to boot: 0:ad(4p4)/boot/loader How does the boot process discover the partition in which the gptboot loader resides? And GPT is pretty damn slick. Nice work FreeBSD hackers. Thanks, Jason C. Wells ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Grub demage my boot loader
Hello, I am new in this mailing list and my english is very poor :) I have installed FBSD 8.0 on my first SATA disk. I downloaded Ubuntu 9.10 CD and boot into the Ubuntu installation. After booting proces a choose 4GB USB memory for installation as hard drive. There is option: delete and use whole disk for Ubuntu. After installation and reboot I have error message - error: no such disk and something like CLI (grub rescue). A tried steps by this link: http://lists.freebsd.org/pipermail/ freebsd-questions/2004-May/047549.html but without luck - there is still Grub! Also I tried step from this page: https://help.ubuntu.com/community/ Grub2 but advices/commands (like boot, normal or dump, etc) doesn't work! Is there any way to solve my issue? Thank you very much for any advices! Jindra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Grub demage my boot loader
On Fri, Mar 26, 2010 at 3:56 PM, JindÅich KáÅa jindr...@kana.at wrote: Hello, I am new in this mailing list and my english is very poor :) I have installed FBSD 8.0 on my first SATA disk. I downloaded Ubuntu 9.10 CD and boot into the Ubuntu installation. After booting proces a choose 4GB USB memory for installation as hard drive. There is option: delete and use whole disk for Ubuntu. After installation and reboot I have error message - error: no such disk and something like CLI (grub rescue). A tried steps by this link: http://lists.freebsd.org/pipermail/freebsd-questions/2004-May/047549.html but without luck - there is still Grub! Also I tried step from this page: https://help.ubuntu.com/community/Grub2 but advices/commands (like boot, normal or dump, etc) doesn't work! Is there any way to solve my issue? Looks like you are not that fluent in dual/multiple boot schemes. I would suggest that you buy another sata disk and install FBSD in one and Linux on the other and boot selection with your BIOS. Either that, or RTFM on multiple boot systems, whether it's booting FBSD from Linux (grub) or the other way around. You could start by Googling this: dual boot linux freebsd there are many references on the list archives on the subject and many other references as well. Best, Alejandro Imass Thank you very much for any advices! Jindra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Grub demage my boot loader
I love the RTFM - who came up with that anyway? That said JindÅich, your English is more than passable! Have a good weekend! G -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Alejandro Imass Sent: Friday, March 26, 2010 4:46 PM To: freebsd-questions@freebsd.org Subject: Re: Grub demage my boot loader On Fri, Mar 26, 2010 at 3:56 PM, JindÅich KáÅa jindr...@kana.at wrote: Hello, I am new in this mailing list and my english is very poor :) I have installed FBSD 8.0 on my first SATA disk. I downloaded Ubuntu 9.10 CD and boot into the Ubuntu installation. After booting proces a choose 4GB USB memory for installation as hard drive. There is option: delete and use whole disk for Ubuntu. After installation and reboot I have error message - error: no such disk and something like CLI (grub rescue). A tried steps by this link: http://lists.freebsd.org/pipermail/freebsd-questions/2004-May/047549.html but without luck - there is still Grub! Also I tried step from this page: https://help.ubuntu.com/community/Grub2 but advices/commands (like boot, normal or dump, etc) doesn't work! Is there any way to solve my issue? Looks like you are not that fluent in dual/multiple boot schemes. I would suggest that you buy another sata disk and install FBSD in one and Linux on the other and boot selection with your BIOS. Either that, or RTFM on multiple boot systems, whether it's booting FBSD from Linux (grub) or the other way around. You could start by Googling this: dual boot linux freebsd there are many references on the list archives on the subject and many other references as well. Best, Alejandro Imass Thank you very much for any advices! Jindra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: boot loader I/O through ethernet
Hi, More and more systems are made without serial ports these days. This means I can't access the loader prompt on FreeBSD without a monitor and keyboard, which is an annoyance. So my question is, is there a way to channel input and output of the loader through LAN / Ethernet by software only and somehow receiving it on the other side? Thanks in advance. I may be wrong but... I think that depends on the hardware (and the BIOS), not on the specific OS that you are using. The loader is in charge of loading the OS, it is not possible to launch a redirection program at the loader stage. Any plateform that do not offer PS/2 port (but I expet them to offer USB port anyway) will offer some kind of keayboard/screen redirection (on serial, ethernet...) Bests, olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: boot loader I/O through ethernet
question. More and more systems are made without serial ports these days. This means I can't access the loader prompt on FreeBSD without a monitor and keyboard, which is an annoyance. So my question is, is there a way to channel input and output of the loader through LAN / Ethernet by software only and somehow receiving it on the other side? Thanks in advance. Regards, FreeBSD can be PXE booted, but as it's PC, you have to connect keyboard and monitor to change BIOS settings to PXE. It's as stupid as keyboard not detected, press F1 to continue But it's PC anyway ;) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to change default boot loader location
Hi, All. problem solved by hack-fix /sys/boot/i386/boot2.c On 05.02.2009, Victor M. Blood wrote: I have a SATA-II disk, which split for 4 primary partitions, eg: 1. NTFS (Active) / ntldr 2. BSD (/var, /usr) 4. NTFS 3. BSD (/, swap) * partitions showed as 'how it's phisicaly placed on drive' Used bootpart I have create 'freebsd.bin' and try to loadup it into ntldr, boot.ini eg: bootpart 2 LBA freebsd.bin Freebsd loader shows two error messages about 'Invalid Partition' and prompt me boot: 0:ad(0,a)/boot/kernel/kernel Then I 'by hands' try: 0:ad(4,3,a)/boot/loader, Free BSD has normal start loader, menus, kernel, etc... works! I try write this line in /boot.config, but have no any result... eg: echo 0:ad(4,3,a)/boot/loader /boot.config Help me please, how I can get autoboot from slice 3, unit 4 ? PS: sorry for my english. -- With all regards, Victor M. Blood. mailto: free...@masm.elcom.ru FTN: 2:5024/1...@fidonet.org, ICQ#3567656 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
How to change default boot loader location
Hi, All. I have a SATA-II disk, which split for 4 primary partitions, eg: 1. NTFS (Active) / ntldr 2. BSD (/var, /usr) 4. NTFS 3. BSD (/, swap) * partitions showed as 'how it's phisicaly placed on drive' Used bootpart I have create 'freebsd.bin' and try to loadup it into ntldr, boot.ini eg: bootpart 2 LBA freebsd.bin Freebsd loader shows two error messages about 'Invalid Partition' and prompt me boot: 0:ad(0,a)/boot/kernel/kernel Then I 'by hands' try: 0:ad(4,3,a)/boot/loader, Free BSD has normal start loader, menus, kernel, etc... works! I try write this line in /boot.config, but have no any result... eg: echo 0:ad(4,3,a)/boot/loader /boot.config Help me please, how I can get autoboot from slice 3, unit 4 ? PS: sorry for my english. -- With all regards, Victor M. Blood. mailto: free...@masm.elcom.ru FTN: 2:5024/1...@fidonet.org, ICQ#3567656 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
no boot/loader
No /boot/loader no /boot/kernel/kernel I isntalled FreeBSD 7.0 with the defaults for partiioning. I am using one hard drive in which I followed with the ASQ (auto, tag for boot, quit) command. I choose the standard boot loader option. I installed through the master freebsd site via ethernet. Upon the congratulation screen is asks for a reboot, and to remove the boot disk, I resart to the error message above. I believe it is because a boot loader is not installed, however, it should be. Is it not in the set up, it is one of the first steps. Following the errors I am in put into a boot prompt: boot: Are there any commands I can run from this prompt to manually boot? How can I make the boot work? Will I need to install my own boot loader? How can I install a manul boot loader? How can I check if the boot loader is installed, but just not loading properly? -- View this message in context: http://www.nabble.com/no-boot-loader-tp18899421p18899421.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: no boot/loader
At 04:42 PM 8/8/2008, acmeinc wrote: No /boot/loader no /boot/kernel/kernel I isntalled FreeBSD 7.0 with the defaults for partiioning. I am using one hard drive in which I followed with the ASQ (auto, tag for boot, quit) command. I choose the standard boot loader option. I installed through the master freebsd site via ethernet. Upon the congratulation screen is asks for a reboot, and to remove the boot disk, I resart to the error message above. I believe it is because a boot loader is not installed, however, it should be. Is it not in the set up, it is one of the first steps. Following the errors I am in put into a boot prompt: boot: Are there any commands I can run from this prompt to manually boot? How can I make the boot work? Will I need to install my own boot loader? How can I install a manul boot loader? How can I check if the boot loader is installed, but just not loading properly? You would do well do try the install again, but check things BEFORE you allow sysinstall to exit and reboot. Also check that your BIOS has any anti-virus settings not allowing the boot area of the hard disk to be written, turned off. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: no boot/loader
At 07:00 PM 8/8/2008, acmeinc wrote: Check things? Which things should I be checking for? And where should I be checking them, to be more specific, which optoin should I choose within sysinstall to check the things? I am reading on another forum the installation is incorrect and to try again, however I have tried many times. Do you think the minimun install is not enough to allow for bootup? Before you exit sysinstall, go to the emergency shell I believe alt+F4 will get you there. Then do: mount The output from mount will show where the new filesystems are mounted. You can check that /boot is populated and that you have a kernel in /boot/kernel/kernel. To check those you'd type: ls -al [fill in the root mount point]/boot and ls -al [fill in the root mount point]/boot/kernel/kernel Check your BIOS settings. It is likely you have a setting in the BIOS preventing the boot area being written. -Derek Derek Ragona wrote: At 04:42 PM 8/8/2008, acmeinc wrote: No /boot/loader no /boot/kernel/kernel I isntalled FreeBSD 7.0 with the defaults for partiioning. I am using one hard drive in which I followed with the ASQ (auto, tag for boot, quit) command. I choose the standard boot loader option. I installed through the master freebsd site via ethernet. Upon the congratulation screen is asks for a reboot, and to remove the boot disk, I resart to the error message above. I believe it is because a boot loader is not installed, however, it should be. Is it not in the set up, it is one of the first steps. Following the errors I am in put into a boot prompt: boot: Are there any commands I can run from this prompt to manually boot? How can I make the boot work? Will I need to install my own boot loader? How can I install a manul boot loader? How can I check if the boot loader is installed, but just not loading properly? You would do well do try the install again, but check things BEFORE you allow sysinstall to exit and reboot. Also check that your BIOS has any anti-virus settings not allowing the boot area of the hard disk to be written, turned off. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/no-boot-loader-tp18899421p18900779.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: no boot/loader
On Fri, 8 Aug 2008 17:00:54 -0700 (PDT), acmeinc [EMAIL PROTECTED] wrote: Check things? Which things should I be checking for? And where should I be checking them, to be more specific, which optoin should I choose within sysinstall to check the things? Be sure to write your settings. In the partition editor, make sure your desired FreeBSD slice is marked active and ensure you have selected to install the standard MBR loader. (If you want to be able to boot into more than one OS, you need to install the boot manager.) Afterwards, when creating the partitions within the slice, I assume you've done everything correctly, else no installation success would be able to happen. I am reading on another forum the installation is incorrect and to try again, however I have tried many times. There seems to be something you've missed, but at this point, I can't guess what it could be. Do you think the minimun install is not enough to allow for bootup? It is, if done correctly. To boot, a correct modification of the boot record is essential. As it has been mentioned, there are some BIOS variants that prohibit any modification of these hard disk areas. But that does not seem to be the problem. The message you gave seems to indicat that something is already in the boot area, but the loader itself cannot be run. The loader is placed into your FreeBSD slice (partition), it resides in /boot; if started, the loader invokes the kernel from /boot/kernel, but that's to be happing after you could solve the problem in question. This is what yould happen, summarized: 1. BIOS runs loader found in MBR (standard loader) 2. Standard loader runs /boot/loader 3. /boot/loader runs /boot/kernel/kernel (GENERIC) 4. Kernel initializes system, runs rc script 5. rc script controls system startup 6. System is up and running While number 1 is connected to the hard disk infront of any partitions, numbers 2 and 3 depend on the FreeBSD's slice and its partitions (usually /dev/ad0s1a). If the required content of this partition is not present, the error you mentioned is completely understandable. -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Restoring freeBSD boot loader
Derek Ragona [EMAIL PROTECTED] writes: At 05:12 PM 6/13/2008, Lionel wrote: I've had to install Windows XP in dual boot on a freeBSD box, and of course it erased the bootloader to replace it with its own. Now I'd like to restore the freeBSD bootloader. I've tried booting with the install CD and I use the fdisk utility to mark the fbsd partition bootable and then said I wanted to install the freeBSD bootloader, but I didn't know how to make it actually write the changes to the disk. So... is it possible to restore the bootloader this way? Maybe I could install lilo from a live CD but I don't want to install grub from windows because I'll probably remove it soon, but I think lilo just places itself in the boot segment so it should be fine. Any help would be most welcome... -- Lionel Look in the tools folder on the FreeBSD install CD for booteasy. Booteasy will run from Windows and install the boot loader. It will also save the old MBR to a floppy, hard disk, or USB disk for safety. -Derek Ah, thank you and all those who answered me, really helpful. I'm going to try this right away. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. And a very special thank to you, MailScanner :-) -- Lionel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Restoring freeBSD boot loader
I've had to install Windows XP in dual boot on a freeBSD box, and of course it erased the bootloader to replace it with its own. Now I'd like to restore the freeBSD bootloader. I've tried booting with the install CD and I use the fdisk utility to mark the fbsd partition bootable and then said I wanted to install the freeBSD bootloader, but I didn't know how to make it actually write the changes to the disk. So... is it possible to restore the bootloader this way? Maybe I could install lilo from a live CD but I don't want to install grub from windows because I'll probably remove it soon, but I think lilo just places itself in the boot segment so it should be fine. Any help would be most welcome... -- Lionel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Restoring freeBSD boot loader
Lionel [EMAIL PROTECTED] wrote: I've had to install Windows XP in dual boot on a freeBSD box, and of course it erased the bootloader to replace it with its own. Now I'd like to restore the freeBSD bootloader. I've tried booting with the install CD and I use the fdisk utility to mark the fbsd partition bootable and then said I wanted to install the freeBSD bootloader, but I didn't know how to make it actually write the changes to the disk. So... is it possible to restore the bootloader this way? Maybe I could install lilo from a live CD but I don't want to install grub from windows because I'll probably remove it soon, but I think lilo just places itself in the boot segment so it should be fine. 3.8 in http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/install.html -- Sahil Tandon [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: Restoring freeBSD boot loader
At 05:12 PM 6/13/2008, Lionel wrote: I've had to install Windows XP in dual boot on a freeBSD box, and of course it erased the bootloader to replace it with its own. Now I'd like to restore the freeBSD bootloader. I've tried booting with the install CD and I use the fdisk utility to mark the fbsd partition bootable and then said I wanted to install the freeBSD bootloader, but I didn't know how to make it actually write the changes to the disk. So... is it possible to restore the bootloader this way? Maybe I could install lilo from a live CD but I don't want to install grub from windows because I'll probably remove it soon, but I think lilo just places itself in the boot segment so it should be fine. Any help would be most welcome... -- Lionel Look in the tools folder on the FreeBSD install CD for booteasy. Booteasy will run from Windows and install the boot loader. It will also save the old MBR to a floppy, hard disk, or USB disk for safety. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Restoring freeBSD boot loader
On Fri, Jun 13, 2008 at 06:46:13PM -0400, Sahil Tandon wrote: Lionel [EMAIL PROTECTED] wrote: I've had to install Windows XP in dual boot on a freeBSD box, and of course it erased the bootloader to replace it with its own. Now I'd like to restore the freeBSD bootloader. I've tried booting with the install CD and I use the fdisk utility to mark the fbsd partition bootable and then said I wanted to install the freeBSD bootloader, but I didn't know how to make it actually write the changes to the disk. So... is it possible to restore the bootloader this way? Maybe I could install lilo from a live CD but I don't want to install grub from windows because I'll probably remove it soon, but I think lilo just places itself in the boot segment so it should be fine. 3.8 in http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/install.html -- Sahil Tandon [EMAIL PROTECTED] Indeed, fdisk(8) can be used to do this. frase pgp9Ly5X508FR.pgp Description: PGP signature
can't 'kldload zfs' if loaded not via /boot/loader
Hi! I'm trying to boot up from my usb stick using grub 1.96 (/boot/loader gave me the 'BTX halted bug') and I've managed to succeed in that. After booting up in the command promth I've issued 'kldload zfs'. The command gives me 'link_elf: symbol hardlink_check_uid undefined', after that kldload fails. If I boot up from standart /boot/loader (on VMWARE or some other PC) there are no such problems exist. Any ideas how to fix it? My idea is that some variable (kenv or sysctl) is missing and link_elf can't find 'hardlink_check_uid' in /boot/kernel/kernel. P.S. uname -a FreeBSD devil.localdomain 7.0-STABLE FreeBSD 7.0-STABLE #5: Wed Mar 12 12:19:10 MSK 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYKERNEL i386 diff /usr/src/sys/i386/conf/GENERIC /usr/src/sys/i386/conf/MYKERNEL 19c19 # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.474.2.3 2008/02/03 07:28:37 scottl Exp $ --- # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.474.2.2.2.1 2008/02/06 03:24:28 scottl Exp $ 31c31,32 options SCHED_4BSD # 4BSD scheduler --- #options SCHED_4BSD # 4BSD scheduler options SCHED_ULE 69a71,74 # for flash usb options ROOTDEVNAME=\ufs:da0s2a\ deviceacpi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Rebuilding boot loader under 7.0-STABLE
Hi I've got 7.0-STABLE installed on an embedded Soekris 5501 box and I'm trying to rebuild the boot loader to not use terminal emulation so I can read the boot messages and menu, as per: https://neon1.net/misc/minibsd.html#t3 # cd /sys/boot # make clean make Gives the following error: make: don't know how to make /usr/src/sys/boot/i386/gptboot/../btx/lib/ crt0.o. Stop *** Error code 2 Stop in /usr/src/sys/boot/i386. *** Error code 1 Stop in /usr/src/sys/boot. The sources are recently csup'd, I'd appreciate some help. Thanks Gianni ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: boot loader anomaly
I'm getting an error message zpool_cache...failed! during boot. Ok, I'm a little slow 8o) It had me confused because I hadn't configured any ZFS. I had forgetten about the existence of /boot/defaults/loader.conf. I find it ODD that the default for zpool_cache_load is YES. Anyway, I added zpool_cache_load=NO to my /boot/loader.conf and now I don't see the error message. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot Loader Broken?
Schiz0 wrote: Can someone help me either solve the bootloader problem, or just how to get into single user mode? If, instead of the pretty, numbered boot loader menu, you get the old 4.x style 'Hit [Enter] to boot immediately' autoboot prompt, hit any key other than enter, then type 'boot -s' at the loader prompt and hit enter. That should boot the kernel, then drop you into single user mode. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net [EMAIL PROTECTED] Furry Peace! - http://.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot Loader Broken?
On Jan 21, 2008 10:08 PM, Bob Johnson [EMAIL PROTECTED] wrote: On 1/21/08, Schiz0 [EMAIL PROTECTED] wrote: On Jan 9, 2008 1:38 PM, Schiz0 [EMAIL PROTECTED] wrote: [...] Now, I'm even in a bigger hole. My power died this weekend, and I guess the / partition has some errors on it, so it is being mounted read-only. But I'm unable to get into single user mode. I tried shutdown now and init 1 and they both brought me back to the multi-user login prompt. And there's no menu to reboot and select single user mode from. What do you mean by multi-user login prompt? I mean it just asks me to login with a username. Like the normal... FreeBSD/i386 (Hostname) (ttyv0) login: ...thing. Can someone help me either solve the bootloader problem, or just how to get into single user mode? When you reboot the system (e.g. press ctrl-alt-delete or issued the shutdown -r now command), it should present a boot menu with numbered choices. What happens if you select the one corresponding to boot in single user mode. Or do you never get to the menu? If you never got that menu, you are almost certainly in single-user mode. Is there anything in /boot/loader.conf ? loader.conf has: # --- Generated by sysinstall --- hint.acpi.0.disabled=1 I actually ran a diff on the files from the 7.0-RC1 installer iso and on my /boot. I ran the diff on loader.conf, loader.rc, and all the .4th files. No diff output came up (meaning they were obviously the same). I was told to also check my fstab, and nothing odd was in there either. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot Loader Broken?
On Jan 21, 2008 10:08 PM, Bob Johnson [EMAIL PROTECTED] wrote: On 1/21/08, Schiz0 [EMAIL PROTECTED] wrote: On Jan 9, 2008 1:38 PM, Schiz0 [EMAIL PROTECTED] wrote: [...] Now, I'm even in a bigger hole. My power died this weekend, and I guess the / partition has some errors on it, so it is being mounted read-only. But I'm unable to get into single user mode. I tried shutdown now and init 1 and they both brought me back to the multi-user login prompt. And there's no menu to reboot and select single user mode from. What do you mean by multi-user login prompt? Can someone help me either solve the bootloader problem, or just how to get into single user mode? When you reboot the system (e.g. press ctrl-alt-delete or issued the shutdown -r now command), it should present a boot menu with numbered choices. What happens if you select the one corresponding to boot in single user mode. Or do you never get to the menu? If you never got that menu, you are almost certainly in single-user mode. Is there anything in /boot/loader.conf ? - Bob Sorry for the double post, I hit Send before I realized I didn't answer half your questions :-X I tried doing ctrl+alt+del, and it just reboots into the normal login prompt for multiuser. I do not get any boot menu (And I'm definitely not in single user mode already, all demons are running and such), just an error saying: - FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Tue Jan 21 14:22:21 EST 2008) \ \: unknown command - /boot/kernel/kernel text=0x29e868 data=0x2db8c+0x23814 syms=[0x4+0x34c10+0x4+0x43ef1] Hit [Enter] to boot immediately, or any other key for a command prompt. Booting [/boot/kernel/kernel] in 4 seconds ... - ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot Loader Broken?
On Jan 9, 2008 1:38 PM, Schiz0 [EMAIL PROTECTED] wrote: Hey, I recently upgraded from 6.3-PRERELEASE to 7.0-PRERELEASE. I had some problem with the ports, but I got that taken care of. Now I'm having another very odd problem. I originally noticed something odd when I tried to shutdown from multiuser mode into single user mode. I ran shutdown now as root in multiuser. It said it was shutting down, etc. But then, it gave me the normal multiuser login prompt. So then I tried rebooting completely, and that's where the big error came up: - FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Tue Jan 8 14:22:21 EST 2008) \ \: unknown command - /boot/kernel/kernel text=0x29e868 data=0x2db8c+0x23814 syms=[0x4+0x34c10+0x4+0x43ef1] Hit [Enter] to boot immediately, or any other key for a command prompt. Booting [/boot/kernel/kernel] in 4 seconds ... - Why it trying to run the command \ ? Right before I did this, I rebuilt world, including the kernel. I installed the new kernel, and was moving down to single user to install world. Is my bootloader corrupt somehow? Thanks. I'm still having this problem. I installed from the 7.0-RC1 Boot Only iso. It worked fine. I csuped RELENG_7 and built world, and now it's giving me the same error. There's nothign weird in /etc/fstab. I didn't change any files in /boot. I put the 7.0-RC1 CD in the drive, and diff'ed the /boot from MY system and the /boot from the CD. Nothing was different. I ran diff on the loader.conf, loader.rc, and all the .4th files. Note, I can still boot up fine. I just hit enter at that error prompt and it boots ok. Now, I'm even in a bigger hole. My power died this weekend, and I guess the / partition has some errors on it, so it is being mounted read-only. But I'm unable to get into single user mode. I tried shutdown now and init 1 and they both brought me back to the multi-user login prompt. And there's no menu to reboot and select single user mode from. Can someone help me either solve the bootloader problem, or just how to get into single user mode? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot Loader Broken?
On 1/21/08, Schiz0 [EMAIL PROTECTED] wrote: On Jan 9, 2008 1:38 PM, Schiz0 [EMAIL PROTECTED] wrote: [...] Now, I'm even in a bigger hole. My power died this weekend, and I guess the / partition has some errors on it, so it is being mounted read-only. But I'm unable to get into single user mode. I tried shutdown now and init 1 and they both brought me back to the multi-user login prompt. And there's no menu to reboot and select single user mode from. What do you mean by multi-user login prompt? Can someone help me either solve the bootloader problem, or just how to get into single user mode? When you reboot the system (e.g. press ctrl-alt-delete or issued the shutdown -r now command), it should present a boot menu with numbered choices. What happens if you select the one corresponding to boot in single user mode. Or do you never get to the menu? If you never got that menu, you are almost certainly in single-user mode. Is there anything in /boot/loader.conf ? - Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot Loader Broken?
On 1/10/08, Lowell Gilbert [EMAIL PROTECTED] wrote: Schiz0 [EMAIL PROTECTED] writes: I recently upgraded from 6.3-PRERELEASE to 7.0-PRERELEASE. I had some problem with the ports, but I got that taken care of. Now I'm having another very odd problem. I originally noticed something odd when I tried to shutdown from multiuser mode into single user mode. I ran shutdown now as root in multiuser. It said it was shutting down, etc. But then, it gave me the normal multiuser login prompt. So then I tried rebooting completely, and that's where the big error came up: Note that rebooting completely *is* the normal procedure, so that you know your kernel boots before you overwrite anything that depends on it. - FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Tue Jan 8 14:22:21 EST 2008) \ \: unknown command - /boot/kernel/kernel text=0x29e868 data=0x2db8c+0x23814 syms=[0x4+0x34c10+0x4+0x43ef1] Hit [Enter] to boot immediately, or any other key for a command prompt. Booting [/boot/kernel/kernel] in 4 seconds ... - Why it trying to run the command \ ? Right before I did this, I rebuilt world, including the kernel. I installed the new kernel, and was moving down to single user to install world. Is my bootloader corrupt somehow? I would suspect something more like some extra text in loader.conf. I just did a fresh install from the iso for 7.0-RC1. It worked fine. I csup'ed the RELENG_7 src, and compiled and installed world and a kernel. All of this with no error. I rebooted into the new kernel, and it was fine. Then I rebooted after make installworld and I'm getting that same error. I did not modify any file at all. Looks like there's a typo in the bootloader config for 7.0-RC1? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot Loader Broken?
Schiz0 [EMAIL PROTECTED] writes: I recently upgraded from 6.3-PRERELEASE to 7.0-PRERELEASE. I had some problem with the ports, but I got that taken care of. Now I'm having another very odd problem. I originally noticed something odd when I tried to shutdown from multiuser mode into single user mode. I ran shutdown now as root in multiuser. It said it was shutting down, etc. But then, it gave me the normal multiuser login prompt. So then I tried rebooting completely, and that's where the big error came up: Note that rebooting completely *is* the normal procedure, so that you know your kernel boots before you overwrite anything that depends on it. - FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Tue Jan 8 14:22:21 EST 2008) \ \: unknown command - /boot/kernel/kernel text=0x29e868 data=0x2db8c+0x23814 syms=[0x4+0x34c10+0x4+0x43ef1] Hit [Enter] to boot immediately, or any other key for a command prompt. Booting [/boot/kernel/kernel] in 4 seconds ... - Why it trying to run the command \ ? Right before I did this, I rebuilt world, including the kernel. I installed the new kernel, and was moving down to single user to install world. Is my bootloader corrupt somehow? I would suspect something more like some extra text in loader.conf. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot Loader Broken?
On Jan 10, 2008 10:23 AM, Lowell Gilbert [EMAIL PROTECTED] wrote: Schiz0 [EMAIL PROTECTED] writes: I recently upgraded from 6.3-PRERELEASE to 7.0-PRERELEASE. I had some problem with the ports, but I got that taken care of. Now I'm having another very odd problem. I originally noticed something odd when I tried to shutdown from multiuser mode into single user mode. I ran shutdown now as root in multiuser. It said it was shutting down, etc. But then, it gave me the normal multiuser login prompt. So then I tried rebooting completely, and that's where the big error came up: Note that rebooting completely *is* the normal procedure, so that you know your kernel boots before you overwrite anything that depends on it. - FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Tue Jan 8 14:22:21 EST 2008) \ \: unknown command - /boot/kernel/kernel text=0x29e868 data=0x2db8c+0x23814 syms=[0x4+0x34c10+0x4+0x43ef1] Hit [Enter] to boot immediately, or any other key for a command prompt. Booting [/boot/kernel/kernel] in 4 seconds ... - Why it trying to run the command \ ? Right before I did this, I rebuilt world, including the kernel. I installed the new kernel, and was moving down to single user to install world. Is my bootloader corrupt somehow? I would suspect something more like some extra text in loader.conf. My /etc/loader.rc: --- \ Loader.rc \ $FreeBSD: src/sys/boot/i386/loader/loader.rc,v 1.4.2.1 2005/10/30 14:37:02 scottl Exp $ \ \ Includes additional commands include /boot/loader.4th \ Reads and processes loader.conf variables start \ Tests for password -- executes autoboot first if a password was defined check-password \ Load in the boot menu include /boot/beastie.4th \ Start the boot menu beastie-start --- My /etc/loader.conf: --- # --- Generated by sysinstall --- hint.acpi.0.disabled=1 --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: amd64 native boot loader?
snowcrash+freebsd wrote: hi, i've FBSD/amd64 62Rp9 installed. kernel world are my own builds from latest cvsup. on boot I see: FreeBSD/i386 bootstrap loader odd. i'd expect a native loader ... checking in, /usr/src/sys/boot ls Makefile alpha/arm/ efi/ forth/ia64/ pc98/ sparc64/ READMEarc/ common/ ficl/ i386/ ofw/ powerpc/ other arches seem to be there ... just not amd64. where's the src for the amd64? AMD64 CPUs are backwards compatible with i386; they boot in 16-bit real mode and only get switched into 64-bit 'long mode' by the kernel later on. Since both i386 and amd64 start booting in the same way, there's no need for separate bootloaders. -- Bruce ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: amd64 native boot loader?
On Dec 22, 2007, at 3:32 AM, Bruce Cran wrote: AMD64 CPUs are backwards compatible with i386; they boot in 16-bit real mode and only get switched into 64-bit 'long mode' by the kernel later on. Since both i386 and amd64 start booting in the same way, there's no need for separate bootloaders. -- Bruce I've thought about this too, but do wonder why the boot loader couldn't go into long mode in one of the loader stages. I don't know if there'd be any significant improvements or drawbacks other than duplication of some code(which I imagine isn't changed often). Somewhat offhand, can the OpenBSD loader chain boot FreeBSD? Due to my dvd drive being sata over atapi, it wasn't recognized by the 6 branch until recently(many thanks to whoever committed the change). But I recall that the boot cd for FreeBSD wouldn't boot, but the boot cd for OpenBSD would. Of course that does primarily relate to cdboot and not boot0. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
amd64 native boot loader?
hi, i've FBSD/amd64 62Rp9 installed. kernel world are my own builds from latest cvsup. on boot I see: FreeBSD/i386 bootstrap loader odd. i'd expect a native loader ... checking in, /usr/src/sys/boot ls Makefile alpha/arm/ efi/ forth/ia64/ pc98/ sparc64/ READMEarc/ common/ ficl/ i386/ ofw/ powerpc/ other arches seem to be there ... just not amd64. where's the src for the amd64? thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
triple boot loader
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have vista+freebsd (both boot well off btx) and fedora (which doesn't boot at all of the current btx install I have)... I want to keep btx instead of having to reconfigure for grub or some piece of linux (*(*(*... help? -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHXbRmzIOMjAek4JIRAqP/AKCbpuTHKMkwZPlzc2/coVpGWZqb7ACfURUb hGZPB1biL2604sC2Us0T3ik= =7/L+ -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]
No /boot/loader
Hi, I installed FreeBSD 7.0-current snapshot [200710] on my laptop. I have two issues, of which second is major: 1. It could not find any X filesets 2. After rebooting, it tells me something like No /boot/loader, and does not boot. I tried to google for #2, but found no solution. I am surely making a mistake somewhere, but am unable to figure out. Any help regarding this is much appreciated. Thanks! This laptop already had a FreeBSD slice, so I did no create new partitions inside it, but just mounted and formatted the existing ones. -Amarendra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: boot loader
Thanks Doug for your help. I am cc'ing freebsd-questions and I will drop freebsd-hackers from the next email on. A few things: 1. it's not a requirement, but I'd like to keep the current partitions (therefore dual boot) just in case anything goes wrong. 2. can you point me to more readings regarding how I might perform the following: However in order to set the new slice bootable you'd have to then use the disk editor 3. I guess what you are saying is that if I go with the upgrade path release 4-5-6, I can do in place upgrade over network. Again appreciate your help. Thomas -Original Message- From: Doug Barton [mailto:[EMAIL PROTECTED] Sent: Friday, October 26, 2007 1:47 PM To: Thomas Ching Cc: [EMAIL PROTECTED] Subject: Re: boot loader FYI, for future reference this question is really more appropriate for [EMAIL PROTECTED] On Fri, 26 Oct 2007, Thomas Ching wrote: Hi, I am trying to do the following with existing systems running 4.5. I'd really appreciate if anyone has any hints, pointers, opinions, or even just you should talk to this other group for me. 1.Existing system: FreeBSD 4.5 based with FreeBSD boot loader (boot0) in MBR You're not planning to dual-boot anything, right? Just boot and run one operating system? 2.I am trying to install a new software based on either FreeBSD 6.2 or later, or LINUX with the following restrictions: a. No console access b. No media access other than serial port, Ethernet, existing HD with 4.5 installed (i.e. NO CD/DVD, floppy, USBetc) 3.The hard drive (1) has enough empty space (currently not partitioned/used) so I can create a new slice to put the new OS/software in and boot from the new OS, but I am not sure how I can achieve that. You definitely can't use any of the standard installation methods without console access. You also can't dual boot without console access. 1.Is it possible for me to boot of FreeBSD 4.5 and run an installation over Ethernet/ftp? No. 2.Is it possible for me to tar up a FreeBSD 6.2 partition, put onto the 4.5 disk (new partition) then sysinstall (or something like that) to make the system boot from the new partition? You could theoretically install onto a local system, tar it up, then unpack it in the unused partition on your remote machine, yes. However in order to set the new slice bootable you'd have to then use the disk editor, and if you get even one thing the tiniest bit wrong, you've bricked it. If I were in your position I'd do this with make world, but that's going to take a long time because you'll first have to update to the latest RELENG_4, then 5-stable, then 6-stable (at least) and then if you don't want to have to do this again for a while I'd update to 7.0 when it is released. The other alternative is to bribe someone who is local to do the installation for you, which all things considered would probably be easier all around. hope this helps, Doug -- This .signature sanitized for your protection ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: boot loader
On Fri, 26 Oct 2007, Thomas Ching wrote: Thanks Doug for your help. I am cc'ing freebsd-questions and I will drop freebsd-hackers from the next email on. Cool, thanks. A few things: 1. it's not a requirement, but I'd like to keep the current partitions (therefore dual boot) just in case anything goes wrong. You can't dual boot without a console. Even if you could, as I said previously you're running the (non-trivial) risk of bricking your system. 3. I guess what you are saying is that if I go with the upgrade path release 4-5-6, I can do in place upgrade over network. Yes. This isn't trivial either, but it's a moderately well tested upgrade path. hth, Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Multi BSD boot loader
I've brought back to life a P3 I got at a school auction years back to use for testing software under various operating systems(presently all bsd) on i386. My main server is FreeBSD/amd64. The P3 has a 10 gig hard drive I'm not intending to upgrade(unless I buy an sata hard drive and find that the bootloader works for atapi sata hard drives in 7.0). I've currently partitioned it into four partitions, with FreeBSD, OpenBSD, and DragonFlyBSD. The fourth is unused at the moment, and I left it open for a fourth system to test on, but I partitioned it as FreeBSD. Here comes the problem. The boot menu currently looks like this. F1: FreeBSD F2: BSD F3: FreeBSD F4: FreeBSD Given the minimalistic nature of the 512 byte bootloader, and my understandings of the bootloader itself, it would be difficult to adapt to suit my needs. I doubt I'll be installing any linux on the fourth partition as linux/i386 is well tested(for this software anyway). As well, I have considered getting a null serial cable to connect the P3 to my amd64 box and, aside from ssh, manage it that way. At least until I get a larger hard drive for my main system that runs 24/7, I do not want to use netbooting. I also may want to install another operating system on the fourth partition(not necessarily BSD, or else I'd automatically choose netbsd). Also, I may not be in the room when I reboot into another operating system, and I know that net booting would be best in this regard. Is there a good bootloader that would suit my needs, of easily and mostly remotely(such as via ssh) being able to control which operating system to boot next? I almost wonder if FreeBSD's loader could be repurposed for my needs but my forth isn't that good. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Multi BSD boot loader
On 9/18/07, Joshua Isom [EMAIL PROTECTED] wrote: I've brought back to life a P3 I got at a school auction years back to use for testing software under various operating systems(presently all bsd) on i386. My main server is FreeBSD/amd64. The P3 has a 10 gig hard drive I'm not intending to upgrade(unless I buy an sata hard drive and find that the bootloader works for atapi sata hard drives in 7.0). I've currently partitioned it into four partitions, with FreeBSD, OpenBSD, and DragonFlyBSD. The fourth is unused at the moment, and I left it open for a fourth system to test on, but I partitioned it as FreeBSD. Here comes the problem. The boot menu currently looks like this. F1: FreeBSD F2: BSD F3: FreeBSD F4: FreeBSD Based on my experience FreeBSD loader (slice boot-sector) tries to load the system from the first FreeBSD (A5) slice it can find. So even is you press F3 you will load FreeBSD rather than DragonFlyBSD. I resolved this issue by installing GRUB and temporarily changing the slice type of the slices I didn't want to boot from. In addition you can edit menu.lst before rebooting to specify which entry should be booted next. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: no /boot/loader - after installation
So I got a copy of boot-only 6.2 onto cd and went back into the bios and changed a few options: LBA mode: off Multi-sector transfers: auto Fast PIO: auto 32 bit transfer mode: on Ultra DMA: auto then ran the 6.2 install using dangerously dedicated which went fine and then on reboot now it comes up with Not ufs no /boot/loader so a slightly different message now, but still no go anyone? - jc On 20/07/07, John Clement [EMAIL PROTECTED] wrote: The burner's been playing up recently so I've just been using the copy of 6.1 I've got. Maybe I'll get a copy of 6.2 burnt at work to try after the weekend. The locked MBR hadn't occured to me, but having checked, unfortunately it wasn't that. So back to the drawing board. If anyone's got any other idea, I'de love to hear them! cheers -jc On 19/07/07, Derek Ragona [EMAIL PROTECTED] wrote: At 03:31 AM 7/19/2007, John Clement wrote: I'm installing 6.1 on an HP Vectra VL420, I've been in the BIOS to set the C/H/S as per what the install reports (I've tried an 80GB Seagate and a 250GB WD), the install all seems to go fine. I've tried the FreeBSD boot manager, a standard MBR and even setting the disk as dedicated, but regardless I end up with the same 'no /boot/loader' when it reboots. I suspect (and hope) I'm making a simple mistake, I just haven't seen this happen before. Thanks in advance!! First you should try 6.2 which is the latest release. Check your BIOS that you are allowing to write to the boot area. Many BIOS have a setting to not allow this to prevent a virus writing to the boot area. -Derek -- This message has been scanned for viruses and dangerous content by *MailScanner* http://www.mailscanner.info/, and is believed to be clean. MailScanner thanks transtec Computers http://www.transtec.co.uk/ for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: no /boot/loader - after installation
At 02:06 PM 7/23/2007, John Clement wrote: So I got a copy of boot-only 6.2 onto cd and went back into the bios and changed a few options: LBA mode: off Multi-sector transfers: auto Fast PIO: auto 32 bit transfer mode: on Ultra DMA: auto then ran the 6.2 install using dangerously dedicated which went fine and then on reboot now it comes up with Not ufs no /boot/loader so a slightly different message now, but still no go anyone? - jc I've never used the boot-only version. So let me ask if you saw any issues with sysinstall? Did you partition the disk and did newfs run without error? Before you exit sysinstall you can check and see what is on the disks from the emergency shell on vtty4. You can do a mount command and see what and where things are mounted and do an ls on those filesystems. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
no /boot/loader - after installation
I'm installing 6.1 on an HP Vectra VL420, I've been in the BIOS to set the C/H/S as per what the install reports (I've tried an 80GB Seagate and a 250GB WD), the install all seems to go fine. I've tried the FreeBSD boot manager, a standard MBR and even setting the disk as dedicated, but regardless I end up with the same 'no /boot/loader' when it reboots. I suspect (and hope) I'm making a simple mistake, I just haven't seen this happen before. Thanks in advance!! jc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: no /boot/loader - after installation
At 03:31 AM 7/19/2007, John Clement wrote: I'm installing 6.1 on an HP Vectra VL420, I've been in the BIOS to set the C/H/S as per what the install reports (I've tried an 80GB Seagate and a 250GB WD), the install all seems to go fine. I've tried the FreeBSD boot manager, a standard MBR and even setting the disk as dedicated, but regardless I end up with the same 'no /boot/loader' when it reboots. I suspect (and hope) I'm making a simple mistake, I just haven't seen this happen before. Thanks in advance!! First you should try 6.2 which is the latest release. Check your BIOS that you are allowing to write to the boot area. Many BIOS have a setting to not allow this to prevent a virus writing to the boot area. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: no /boot/loader - after installation
The burner's been playing up recently so I've just been using the copy of 6.1 I've got. Maybe I'll get a copy of 6.2 burnt at work to try after the weekend. The locked MBR hadn't occured to me, but having checked, unfortunately it wasn't that. So back to the drawing board. If anyone's got any other idea, I'de love to hear them! cheers -jc On 19/07/07, Derek Ragona [EMAIL PROTECTED] wrote: At 03:31 AM 7/19/2007, John Clement wrote: I'm installing 6.1 on an HP Vectra VL420, I've been in the BIOS to set the C/H/S as per what the install reports (I've tried an 80GB Seagate and a 250GB WD), the install all seems to go fine. I've tried the FreeBSD boot manager, a standard MBR and even setting the disk as dedicated, but regardless I end up with the same 'no /boot/loader' when it reboots. I suspect (and hope) I'm making a simple mistake, I just haven't seen this happen before. Thanks in advance!! First you should try 6.2 which is the latest release. Check your BIOS that you are allowing to write to the boot area. Many BIOS have a setting to not allow this to prevent a virus writing to the boot area. -Derek -- This message has been scanned for viruses and dangerous content by *MailScanner* http://www.mailscanner.info/, and is believed to be clean. MailScanner thanks transtec Computers http://www.transtec.co.uk/ for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
