Debian Codegraph @

debian/hw-detect.templates

raw
1 Template: hw-detect/detect_progress_step
2 Type: text
3 # :sl1:
4 _Description: Detecting hardware, please wait...
5
6 Template: hw-detect/load_progress_step
7 Type: text
8 # :sl1:
9 _Description: Loading module '${MODULE}' for '${CARDNAME}'...
10
11 Template: hw-detect/pcmcia_step
12 Type: text
13 # :sl1:
14 _Description: Starting PC card services...
15
16 Template: hw-detect/hardware_init_step
17 Type: text
18 # :sl1:
19 _Description: Waiting for hardware initialization...
20
21 Template: hw-detect/select_modules
22 Type: multiselect
23 Choices: ${list}
24 # :sl2:
25 _Description: Modules to load:
26 The following Linux kernel modules were detected as matching your
27 hardware. If you know some are unnecessary, or cause problems, you can
28 choose not to load them. If you're unsure, you should leave them all
29 selected.
30
31 Template: hw-detect/start_pcmcia
32 Type: boolean
33 Default: true
34 # FIXME: not in use and kept just while we're still in doubt it will
35 # be needed
36 # :sl2:
37 _Description: Start PC card services?
38 Please choose whether PC card services should be started in order to allow
39 the use of PCMCIA cards.
40
41 Template: hw-detect/pcmcia_resources
42 Type: string
43 # :sl2:
44 _Description: PCMCIA resource range options:
45 Some PCMCIA hardware needs special resource configuration options in
46 order to work, and can cause the computer to freeze otherwise. For
47 example, some Dell laptops need "exclude port 0x800-0x8ff" to be
48 specified here. These options will be added to /etc/pcmcia/config.opts.
49 See the installation manual or the PCMCIA HOWTO for more information.
50 .
51 For most hardware, you do not need to specify anything here.
52
53 Template: hw-detect/retry_params
54 Type: string
55 # :sl3:
56 _Description: Additional parameters for module ${MODULE}:
57 The module ${MODULE} failed to load. You may need to pass parameters
58 to the module to make it work; this is common with older hardware.
59 These parameters are often I/O port and IRQ numbers that vary from machine
60 to machine and cannot be determined from the hardware. An example string
61 looks something like "irq=7 io=0x220"
62 .
63 If you don't know what to enter, consult your documentation, or leave it
64 blank to not load the module.
65
66 Template: hw-detect/modprobe_error
67 Type: error
68 # :sl2:
69 _Description: Error while running '${CMD_LINE_PARAM}'
70
71 Template: hw-detect/load_media
72 Type: boolean
73 Default: false
74 # :sl2:
75 _Description: Load missing drivers from removable media?
76 A driver for your hardware is not available. You may need
77 to load drivers from removable media, such as a USB stick, or driver floppy.
78 .
79 If you have such media available now, insert it, and continue.
80
81 Template: hw-detect/load_firmware
82 Type: boolean
83 Default: true
84 # :sl2:
85 _Description: Load missing firmware from removable media?
86 Some of your hardware needs non-free firmware files to operate. The
87 firmware can be loaded from removable media, such as a USB stick or
88 floppy.
89 .
90 The missing firmware files are: ${FILES}
91 .
92 If you have such media available now, insert it, and continue.
93
94 Template: base-installer/progress/hw-detect
95 Type: text
96 # :sl1:
97 _Description: Checking for firmware...
98
99 # Temporary template to force old behavior of loading IDE modules by default
100 Template: hw-detect/load-ide
101 Type: boolean
102 Default: false
103 Description: for internal use; can be preseeded
104
105 # This is an initial implementation, which might evolve over time (#1029848):
106 Template: hw-detect/firmware-lookup
107 Type: text
108 Default:
109 Description: for expert use; can be preseeded
110 Setting this to "never" makes check-missing-firmware and install-firmware
111 hooks not try to find and install firmware packages (even if available on
112 the installation image).