RME Audio DIGI32/8 Spécifications Page 22

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 35
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 21
often be used with some other boot argument. Hence if you specify a reserve region to protect a specific
device, you must generally specify an explicit probe for that device. Most drivers ignore the port registration
table if they are given an explicit address.
For example, the boot line
reserve=0x300,32 blah=0x300
keeps all device drivers except the driver for `blah' from probing 0x300−0x31f.
As usual with boot−time specifiers there is an 11 parameter limit, thus you can only specify 5 reserved regions
per reserve keyword. Multiple reserve specifiers will work if you have an unusually complicated
request.
The `resume=' Argument
If you are using software suspend, then this will allow you to specify the file name of the suspend to disk data
that you want the machine to resume from.
The `vga=' Argument
Note that this is not really a boot argument. It is an option that is interpreted by LILO and not by the kernel
like all the other boot arguments are. However its use has become so common that it deserves a mention here.
It can also be set via using rdev −v or equivalently vidmode on the vmlinuz file. This allows the setup
code to use the video BIOS to change the default display mode before actually booting the Linux kernel.
Typical modes are 80x50, 132x44 and so on. The best way to use this option is to start with vga=ask which
will prompt you with a list of various modes that you can use with your video adapter before booting the
kernel. Once you have the number from the above list that you want to use, you can later put it in place of the
`ask'. For more information, please see the file linux/Documentation/svga.txt that comes with all
recent kernel versions.
Note that newer kernels (v2.1 and up) have the setup code that changes the video mode as an option, listed as
Video mode selection support so you need to enable this option if you want to use this feature.
4. Boot Arguments to Control PCI Bus Behaviour (`pci=')
The `pci=' argument (not avail. in v2.0 kernels) can be used to change the behaviour of PCI bus device
probing and device behaviour. Firstly the file linux/drivers/pci/pci.c checks for architecture
independent pci= options. The remaining allowed arguments are handled in
linux/arch/???/kernel/bios32.c and are listed below for ???=i386.
4.1 The `pci=assign−busses' Argument
This tells the kernel to always assign all PCI bus numbers, overriding whatever the firmware may have done.
4.2 The `pci=bios' and `pci=nobios' Arguments
These are used to set/clear the flag indicating that the PCI probing is to take place via the PCI BIOS. The
The Linux BootPrompt−HowTo
The `resume=' Argument 18
Vue de la page 21
1 2 ... 17 18 19 20 21 22 23 24 25 26 27 ... 34 35

Commentaires sur ces manuels

Pas de commentaire