Translations by tbds

tbds has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.

101150 of 1377 results
251.
Detecting hardware to find CD-ROM drives
2010-03-07
252.
Manually select a CD-ROM module and device?
2010-03-07
253.
Your CD-ROM drive may be an old Mitsumi or another non-IDE, non-SCSI CD-ROM drive. In that case you should choose which module to load and the device to use. If you don't know which module and device are needed, look for some documentation or try a network installation instead of a CD-ROM installation.
2010-03-07
255.
Your installation CD-ROM couldn't be mounted. This probably means that the CD-ROM was not in the drive. If so you can insert it and try again.
2010-03-07
256.
Module needed for accessing the CD-ROM:
2010-03-07
258.
Device file for accessing the CD-ROM:
2010-03-07
259.
In order to access your CD-ROM drive, please enter the device file that should be used. Non-standard CD-ROM drives use non-standard device files (such as /dev/mcdx).
2010-03-07
260.
You may switch to the shell on the second terminal (ALT+F2) to check the available devices in /dev with "ls /dev". You can return to this screen by pressing ALT+F1.
2010-03-07
261.
Scanning CD-ROM
2010-03-07
262.
Scanning ${DIR}...
2010-03-07
268.
Error reading Release file
2010-03-07
269.
The CD-ROM does not seem to contain a valid 'Release' file, or that file could not be read correctly.
2010-03-07
270.
You may try to repeat CD-ROM detection but, even if it does succeed the second time, you may experience problems later in the installation.
2010-03-07
274.
The installer can use hdparm to tune some CD-ROM drive parameters, which may significantly speed up reading packages from the CD. You can change the parameters to be used. To disable hdparm, enter an empty parameter list.
2010-03-07
275.
no ethernet card
2010-03-07
278.
No Ethernet card was detected. If you know the name of the driver needed by your Ethernet card, you can select it from the list.
2010-03-07
279.
Do you intend to use FireWire Ethernet?
2010-03-07
280.
No Ethernet card was detected, but a FireWire interface is present. It's possible, though unlikely, that with the right FireWire hardware connected to it, this could be your primary Ethernet interface.
2010-03-07
281.
Ethernet card not found
2010-03-07
282.
No Ethernet card was found on the system.
2010-03-07
283.
Detecting network hardware
2010-03-07
285.
Detect disks
2010-03-07
286.
Detecting disks and all other hardware
2010-03-07
287.
continue with no disk drive
2010-03-07
288.
Driver needed for your disk drive:
2010-03-07
289.
No disk drive was detected. If you know the name of the driver needed by your disk drive, you can select it from the list.
2010-03-07
290.
No partitionable media
2010-03-07
291.
No partitionable media were found.
2010-03-07
292.
Please check that a hard disk is attached to this machine.
2010-03-07
293.
Activate Serial ATA RAID devices?
2010-03-07
294.
One or more drives containing Serial ATA RAID configurations have been found. Do you wish to activate these RAID devices?
2010-03-07
295.
login to iSCSI targets
2010-03-07
296.
Detecting hardware, please wait...
2010-03-07
299.
Waiting for hardware initialization...
2010-03-07
301.
The following Linux kernel modules were detected as matching your hardware. If you know some are unnecessary, or cause problems, you can choose not to load them. If you're unsure, you should leave them all selected.
2010-03-07
302.
Start PC card services?
2010-03-07
303.
Please choose whether PC card services should be started in order to allow the use of PCMCIA cards.
2010-03-07
304.
PCMCIA resource range options:
2010-03-07
305.
Some PCMCIA hardware needs special resource configuration options in order to work, and can cause the computer to freeze otherwise. For example, some Dell laptops need "exclude port 0x800-0x8ff" to be specified here. These options will be added to /etc/pcmcia/config.opts. See the installation manual or the PCMCIA HOWTO for more information.
2010-03-07
306.
For most hardware, you do not need to specify anything here.
2010-03-07
307.
Additional parameters for module ${MODULE}:
2010-03-07
308.
The module ${MODULE} failed to load. You may need to pass parameters to the module to make it work; this is common with older hardware. These parameters are often I/O port and IRQ numbers that vary from machine to machine and cannot be determined from the hardware. An example string looks something like "irq=7 io=0x220"
2010-03-07
309.
If you don't know what to enter, consult your documentation, or leave it blank to not load the module.
2010-03-07
310.
Error while running '${CMD_LINE_PARAM}'
2010-03-07
311.
Load missing drivers from removable media?
2010-03-07
312.
A driver for your hardware is not available. You may need to load drivers from removable media, such as a USB stick, or driver floppy.
2010-03-07
313.
If you have such media available now, insert it, and continue.
2010-03-07
314.
Load missing firmware from removable media?
2010-03-07
315.
Some of your hardware needs non-free firmware files to operate. The firmware can be loaded from removable media, such as a USB stick or floppy.
2010-03-07
316.
The missing firmware files are: ${FILES}
2010-03-07