From ab093813be4246d6963b39ff58ee91f1cda110f8 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 19 Jun 2006 22:15:58 +0000 Subject: * Document new aliases added in preseed 1.17 for common debconf boot parameters: fb, url, file, locale, interface. --- en/boot-installer/i386.xml | 4 ++-- en/boot-installer/m68k.xml | 8 ++++---- en/boot-installer/parameters.xml | 26 +++++++++++++++----------- en/boot-installer/trouble.xml | 3 +-- 4 files changed, 22 insertions(+), 19 deletions(-) (limited to 'en/boot-installer') diff --git a/en/boot-installer/i386.xml b/en/boot-installer/i386.xml index fe94b6c27..d58bea242 100644 --- a/en/boot-installer/i386.xml +++ b/en/boot-installer/i386.xml @@ -334,7 +334,7 @@ be useful can be found by pressing F2 through F8. If you add any parameters to the boot command line, be sure to type the boot method (the default is linux) and a space before the first parameter (e.g., -linux debconf/priority=medium). +linux fb=false). @@ -358,7 +358,7 @@ enact this keypress, for example the IRA uses Ctrl past the splash screen and at the help text your keystrokes will be echoed at the prompt as expected. To prevent the installer from using the framebuffer for the rest of the installation, you will also want to add -debian-installer/framebuffer=false to the boot prompt, +fb=false to the boot prompt, as described in the help text. diff --git a/en/boot-installer/m68k.xml b/en/boot-installer/m68k.xml index 62f11cb39..25308353d 100644 --- a/en/boot-installer/m68k.xml +++ b/en/boot-installer/m68k.xml @@ -48,8 +48,8 @@ The only method of installation available to amiga is the hard drive Amiga does not currently work with bogl, so if -you are seeing bogl errors, you need to include the kernel parameter -debian-installer/framebuffer=false. +you are seeing bogl errors, you need to include the boot parameter +fb=false. @@ -65,8 +65,8 @@ drive (see ) or from floppies Atari does not currently work with bogl, so if -you are seeing bogl errors, you need to include the kernel parameter -debian-installer/framebuffer=false. +you are seeing bogl errors, you need to include the boot parameter +fb=false. diff --git a/en/boot-installer/parameters.xml b/en/boot-installer/parameters.xml index 5c5a35a73..0bad667df 100644 --- a/en/boot-installer/parameters.xml +++ b/en/boot-installer/parameters.xml @@ -74,10 +74,10 @@ The installation system recognizes a few additional boot parameters -Note that the kernel accepts a maximum of 8 command line options and +Note that the 2.4 kernel accepts a maximum of 8 command line options and 8 environment options (including any options added by default for the installer). If these numbers are exceeded, 2.4 kernels will drop any -excess options and 2.6 kernels will panic. With kernel 2.6.9 or newer, +excess options. With kernel 2.6.9 or newer, you can use 32 command line options and 32 environment options. @@ -92,21 +92,22 @@ you can use 32 command line options and 32 environment options. This parameter sets the lowest priority of messages to be displayed. +Short form: priority -The default installation uses debconf/priority=high. +The default installation uses priority=high. This means that both high and critical priority messages are shown, but medium and low priority messages are skipped. If problems are encountered, the installer adjusts the priority as needed. -If you add debconf/priority=medium as boot parameter, you +If you add priority=medium as boot parameter, you will be shown the installation menu and gain more control over the installation. -When debconf/priority=low is used, all messages are shown +When priority=low is used, all messages are shown (this is equivalent to the expert boot method). -With debconf/priority=critical, the installation system +With priority=critical, the installation system will display only critical messages and try to do the right thing without fuss. @@ -214,15 +215,16 @@ one device. Some architectures use the kernel framebuffer to offer installation in a number of languages. If framebuffer causes a problem on your system you can disable the feature by the parameter -debian-installer/framebuffer=false. Problem -symptoms are error messages about bterm or bogl, a blank screen, or -a freeze within a few minutes after starting the install. +debian-installer/framebuffer=false, or +fb=false for short. Problem symptoms are error messages +about bterm or bogl, a blank screen, or a freeze within a few minutes after +starting the install. The video=vga16:off argument may also be used -to disable the framebuffer. Such problems have been reported on a Dell -Inspiron with Mobile Radeon card. +to disable the kernel's user of the framebuffer. Such problems have been +reported on a Dell Inspiron with Mobile Radeon card. @@ -290,6 +292,7 @@ this misbehavior. Specify the url to a preconfiguration file to download and use in automating the install. See . +Short form: url @@ -300,6 +303,7 @@ automating the install. See . Specify the path to a preconfiguration file to load to automating the install. See . +Short form: file diff --git a/en/boot-installer/trouble.xml b/en/boot-installer/trouble.xml index 843f29201..17d1bbc6a 100644 --- a/en/boot-installer/trouble.xml +++ b/en/boot-installer/trouble.xml @@ -115,8 +115,7 @@ If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter -debian-installer/framebuffer=false or -video=vga16:off to disable the framebuffer +fb=false video=vga16:off to disable the framebuffer console. Only the English language will be available during the installation due to limited console features. See for details. -- cgit v1.2.3