summaryrefslogtreecommitdiffstats
path: root/sys/boot
Commit message (Collapse)AuthorAgeFilesLines
* Make sure to synchronize icache for the newly loaded loader. Not an issuenwhitehorn2012-02-162-3/+7
| | | | | | on most systems, when the relevant icache lines are not full. MFC after: 2 weeks
* Reduce diffs against i386.nyan2012-02-101-12/+14
| | | | MFC after: 1 week
* Fix clang warnings.rpaulo2012-02-052-3/+3
|
* Clarify and improve the boot menu with some small changes:pluknet2012-01-251-18/+18
| | | | | | | | | | | | | | | | | | - Enter instead of ENTER - Remove colons - Line up option values - Use dots to provide a line to visually connect the menu selections with their values - Replace Enabled/Disabled with off/On (bigger inital cap for "On" is a visual indicator) - Remove confusing "Boot" from selections that don't boot. - With loader_color=1 in /boot/loader.conf, use reverse video to highlight enabled options PR: misc/160818 Submitted by: Warren Block <wblock wonkity com> Reviewed by: Devin Teske <devin dot teske fisglobal com>, current@ MFC after: 1 week
* Experimental support for booting CHRP-type PowerPC systems from hard disks.nwhitehorn2012-01-251-1/+0
|
* Wrap changes from svn r212126 inside LOADER_NFS_SUPPORT such thatsbruno2012-01-191-0/+2
| | | | | | | | | | | | using LOADER_TFTP_SUPPORT excludes this code. Fixes compilation of pxeldr with -DLOADER_TFTP_SUPPORT Applicable to stable/9 and stable/8 now. This appears to not be needed on stable/7 as r212126 has not been MFC'd. Obtained from: Yahoo! Inc. MFC after: 2 weeks
* Fix some unreliability problems related to MSR bits inherited from kboot bynwhitehorn2012-01-151-1/+1
| | | | | setting an absolute MSR when during on the MMU. This prevents delay(), in particular, from intermittently malfunctioning.
* - Document TheDraw splash screens in the default loader.confeadler2012-01-141-1/+2
| | | | | | Submitted by: Jason Hellenthal Approved by: glebius MFC after: 3 days
* Get rid of a spurious warning on the console when booting the kernelpluknet2012-01-091-2/+13
| | | | | | | | | | | | | | | | | | | | from the interactive loader(8) prompt and beastie_disable="YES" is set in loader.conf(5). In this case menu.rc is not evaluated and consequently menu-unset does not have a body yet. This results in the ficl warning "menu-unset not found" when try-menu-unset invokes menu-unset. Check for beastie_disable="YES" explicitly, so that the try-menu-unset word will not attempt to invoke menu-unset because the menu will have never been configured. [1] Use the sfind primitive as a last resort as an additional safer approach conjuring a foreign word safely. [2] PR: kern/163938 Submitted by: Devin Teske [1] Reviewed by: Devin Teske [2] Reported and tested by: dim MFC after: 1 week X-MFC with: r228985
* Document comconsole_port and comconsole_pcidev loader variables.kib2012-01-071-1/+38
| | | | MFC after: 2 weeks
* MFi386: revision 229435nyan2012-01-041-31/+188
| | | | | | | Add special loader environment variables 'comconsole_port' and 'comconsole_pcidev'. MFC after: 2 weeks
* Fix 230MB MO support.nyan2012-01-041-1/+1
| | | | | Submitted by: Kaho Toshikazu MFC after: 1 week
* Add special loader environment variables 'comconsole_port' andkib2012-01-033-31/+195
| | | | | | | | | | | | | | | | | | 'comconsole_pcidev'. The former allows to set the base address of the serial console i/o port. The later takes the string of the format 'bus:device:function:[bar]' as a value and uses the serial port attached as PCI device at the specified location for console. Both variants pass 'hw.uart.console' variable to the uart driver to properly hand-over the kernel console. Change allows to use ISA serial ports other than COM1 for the loader/kernel console without loader recompilation. Also, you can use PCI-attached port as the console, e.g. Intel AMT serial pseudo-port on some motherboards based on Q67 chipset. Reviewed by: jhb MFC after: 2 weeks
* Replace index() and rindex() calls with strchr() and strrchr().ed2012-01-033-3/+3
| | | | | | | | | | The index() and rindex() functions were marked LEGACY in the 2001 revision of POSIX and were subsequently removed from the 2008 revision. The strchr() and strrchr() functions are part of the C standard. This makes the source code a lot more consistent, as most of these C files also call into other str*() routines. In fact, about a dozen already perform strchr() calls.
* Merge index() and strchr() together.ed2012-01-031-4/+4
| | | | | | | | | | | | | | | | | As I looked through the C library, I noticed the FreeBSD MIPS port has a hand-written version of index(). This is nice, if it weren't for the fact that most applications call strchr() instead. Also, on the other architectures index() and strchr() are identical, meaning we have two identical pieces of code in the C library and statically linked applications. Solve this by naming the actual file strchr.[cS] and let it use __strong_reference()/STRONG_ALIAS() to provide the index() routine. Do the same for rindex()/strrchr(). This seems to make the C libraries and static binaries slightly smaller, but this reduction in size seems negligible.
* Unset the environment variables associated with individual menu itemspluknet2011-12-303-18/+81
| | | | | | | | | | | | | | | | | | | | | | before invoking the kernel. Quoting submitter: The issue is with the new boot loader menu. It adds many loader variables including ones that contain ANSI color escapes. Obviously, these ANSI codes don't play well with serial consoles when kenv(1) is executed without arguments (reports vary as to what happens, but it's never pretty). The net-effect is that kenv(1) no longer reports menu-related variables. In essence, kenv(1) output should now appear the same as on RELENG_8 (which lacks the new boot loader and didn't use any such variables). Thus, restoring serial console glory. Submitted by: Devin Teske <devin dott teske fisglobal.com> MFC after: 2 weeks
* Clean up from the 4.x era.pluknet2011-12-271-3/+3
| | | | | | | | | | | | In an example of boot command: - rename wd(4) IDE disk drives name to ad(4) for the time being. - update the used kernel path "/kernel" to the current default. [It still worked occasionally by looking into the /boot/kernel directory, so the resulting path was "/boot//kernel/kernel", with two slashes.] Bump .Dd for this and previous changes. MFC after: 1 week
* Make the RTC checking for QEMU even more aggressive.ed2011-12-211-4/+6
| | | | | | | | | | | At work, where we use use KVM+QEMU, we notice that pxeboot is pratically impossible because of network timeouts. This is due to the fact that the RTC code makes aggressive jumps. Two RTC reads does not seem to be sufficient. Change the code to check for 8 identical RTC values. Sponsored by: Kumina bv
* Allow boot0cfg to force a PXE boot via boot0 on the next boot.jhb2011-12-201-1/+1
| | | | | | | | | | - Fix boot0 to check for PXE when using the pre-set setting for the preferred slice. - Update boot0cfg to use slice 6 to select PXE. Accept a 'pxe' argument instead of a number for the 's' option as a way to select PXE as well. Submitted by: Andrew Boyer aboyer averesystems MFC after: 2 weeks
* - Rename if_carp.ko to carp.ko.glebius2011-12-161-1/+1
| | | | - carp.ko depends on sha1.c
* Replace `inline static' by `static inline'.ed2011-12-131-2/+2
| | | | | | If I interpret the C standard correctly, the storage specifier should be placed before the inline keyword. While at it, replace __inline by inline in the files affected.
* zfsboot: print boot.config contents before parsing itavg2011-12-041-2/+2
| | | | | | as parsing can be a destructive operation MFC after: 2 weeks
* zfs boot: allow file vdevs to be used in testing (e.g. with zfsboottest)avg2011-12-041-0/+3
| | | | MFC after: 1 week
* Rename the linker emulation name for powerpc and powerc64. This is needed thatandreast2011-11-193-3/+3
| | | | | we can also use the upstream binutils linker where we have to have a unique name for the FreeBSD emulation.
* Initial version of cesa(4) driver for Marvell crypto engine and securityraj2011-11-192-0/+4
| | | | | | | | | | | accelerator. The following algorithms and schemes are supported: - 3DES, AES, DES - MD5, SHA1 Obtained from: Semihalf Written by: Piotr Ziecik
* - Add new loader_logo orbbw to default.confmiwi2011-11-191-1/+1
| | | | | | | PR: 162608 Submitted by: manolis Approved by: rwatson (mentor) MFC after: 3 Days
* - Whitespaces fixed onlymiwi2011-11-191-3/+3
| | | | Approved by: rwatson (mentor)
* Wire the kernel text RWX, rather than RX. We're not quite readymarcel2011-11-171-1/+1
| | | | | | for having kernel text non-writable, because we still need to apply relocations. On top of that, the PBVM page table has all pages marked as RWX, so it's an inconsistency to begin with.
* Add DTS for the Freescale P2020DS.raj2011-11-171-0/+754
| | | | Obtained from: Freescale
* Add DTS for the Freescale P1020RDB.marcel2011-11-141-0/+627
|
* Add DTS for the Freescale P3041DS.marcel2011-11-141-0/+753
|
* Revert some debugging printfs that crept into 223695.jhb2011-11-091-5/+1
|
* Remove the remnants of /stand/sysinstall.pluknet2011-11-031-1/+1
| | | | | | loader.8: Sync the default init_path list with kern/init_main.c. NOTES: Replace with /rescue/init in the INIT_PATH kernel option.
* Remove the long reprecated ``/stand/sysinstall'' from the init_path.pluknet2011-10-271-1/+1
| | | | | | | It can be put back using the INIT_PATH config option or init_path loader variable, if still needed (which I doubt). MFC after: 1 week
* - Add a new header for the x86 boot code that defines various structuresjhb2011-10-256-31/+128
| | | | | | | | | | | | | | | | | | | and constants related to the BIOS Enhanced Disk Drive Specification. - Use this header instead of magic numbers and various duplicate structure definitions for doing I/O. - Use an actual structure for the request to fetch drive parameters in drvsize() rather than a gross hack of a char array with some magic size. While here, change drvsize() to only pass the 1.1 version of the structure and not request device path information. If we want device path information you have to set the length of the device path information as an input (along with probably checking the actual EDD version to see which size one should use as the device path information is variable-length). This fixes data smashing problems from passing an EDD 3 structure to BIOSes supporting EDD 4. Reviewed by: avg Tested by: Dennis Koegel dk neveragain.de MFC after: 1 week
* Consolidate duplicate definitions of V86_CY() and V86_ZR() which check forjhb2011-10-2515-37/+27
| | | | | the carry and zero flags being set, respectively, in <btxv86.h> and use them throughout the x86 boot code.
* With LOADER_MBR_SUPPORT defined and LOADER_GPT_SUPPORT undefined we wouldpjd2011-10-201-2/+3
| | | | | | | never call disk_openmbr(). Submitted by: avg MFC after: 3 days
* - Correctly read gang header from raidz.pjd2011-10-201-51/+51
| | | | | | | | | | - Decompress assembled gang block data if compressed. - Verify checksum of a gang header. - Verify checksum of assembled gang block data. - Verify checksum of uber block. Submitted by: avg MFC after: 3 days
* Fix missing return when LOADER_GPT_SUPPORT is defined, but LOADER_MBR_SUPPORTpjd2011-10-191-1/+1
| | | | | | is not. MFC after: 3 days
* Always pass data size for checksum verification function, as usingpjd2011-10-191-1/+1
| | | | | | | | | | physical block size declared in bp may not always be what we want. For example in case of gang block header physical block size declared in bp is much larger than SPA_GANGBLOCKSIZE (512 bytes) and checksum calculation failed. This bug could lead to accessing unallocated memory and resets/failures during boot. MFC after: 3 days
* Never pass NULL block pointer when reading. This is neither expected norpjd2011-10-191-1/+2
| | | | | | | | handled by lower layers like vdev_raidz, which uses bp for checksum verification. This bug could lead to NULL pointer reference and resets during boot. MFC after: 3 days
* Don't mark vdev as healthy too soon, so we won't try to use invalid vdevs.pjd2011-10-191-2/+1
| | | | MFC after: 3 days
* Look for /boot/config in addition to /boot.config, with the former takingdes2011-10-186-13/+24
| | | | | | precedence over the latter if it exists. MFC after: 3 weeks
* Support for booting XLP using FDT.jchandra2011-10-181-0/+67
| | | | | | | | - update xlp_machdep.c to read arguments from FDT if FDT support is compiled in. - define rmi_uart_bus_space, and use it as fdtbus_bs_tag - update conf files for FDT support - add default dts file xlp-basic.dts
* - change "is is" to "is" or "it is"eadler2011-10-161-1/+1
| | | | | | | | - change "the the" to "the" Approved by: lstewart Approved by: sahil (mentor) MFC after: 3 days
* Allow ixp425 boot2 to compile after r219452thompsa2011-10-041-1/+1
|
* zfstest: rename to zfsboottest and move to toolsavg2011-09-161-144/+0
| | | | | Approved by: re (kib) MFC after: 1 week
* gpt/zfs boot blocks: reduce optimizing CFLAGS to -O1avg2011-09-133-29/+4
| | | | | | | | | | | | | | | | | | | | | | gpt and zfs boot blocks are not nearly as size-constrained as boot2 from which they inherited their current optimization and anti-optimization options. As such the current options do not provide any benefit, but make debugging of the code much harder. Also, it has been demonstrated that combination of -mrtd and -fno-unit-at-a-time may result in mis-compilation of the boot code with the current base gcc. Additionally, intermediate assembly file filtering is removed for zfsboot. The new boot blocks are all compile- and boot- tested using qemu. gptzfsboot is tested with real hardware. Reported by: Peter Jeremy <peterjeremy@acm.org> [miscompilation] Discussed with: bde, jhb Tested by: Sebastian Chmielewski <chmielsster@gmail.com> [gptzfsboot] Approved by: re (kib) MFC after: 3 weeks
* zfstest: cleanup the code, improve functionality and diagnosticsavg2011-09-131-16/+40
| | | | | | | | | | | | The utility is not connected to the build, so it should be safe to update it. To do: move the utility to tools/. Some code is provided by Peter Jeremy <peterjeremy@acm.org> Tested by: Sebastian Chmielewski <chmielsster@gmail.com>, Peter Jeremy <peterjeremy@acm.org> (earlier versions) Approved by: re (kib) MFC after: 4 days
* Restore behavior of the autoboot_delay="-1" boot menu setting to thejh2011-09-022-6/+11
| | | | | | | | | pre-r222417 state. The behavior was essentially reversed in r222417 which can cause confusion. PR: 159775 Submitted by: Devin Teske Approved by: re (kib)
OpenPOWER on IntegriCloud