|
|
413.
|
|
|
You can also build your own customized kernel to support SMP. You can find a discussion of how to do this in <xref linkend="kernel-baking"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
hardware.xml:1745
|
|
|
416.
|
|
|
Debian's support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. Most AGP, PCI and PCIe video cards work under X.Org. Details on supported graphics buses, cards, monitors, and pointing devices can be found at <ulink url="&url-xorg;"></ulink>. Debian &release; ships with X.Org version &x11ver;.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
hardware.xml:1765
|
|
|
417.
|
|
|
The X.Org X Window System is only supported on the SGI Indy and the O2. The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url="&url-bcm91250a-hardware;">compatibility listing</ulink> for Broadcom evaluation boards is available.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
hardware.xml:1774
|
|
|
418.
|
|
|
The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url="&url-bcm91250a-hardware;">compatibility listing</ulink> for Broadcom evaluation boards is available.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
hardware.xml:1783
|
|
|
419.
|
|
|
Most graphics options commonly found on Sparc-based machines are supported. X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards (glint driver). To use an Elite3D card with X.org you additionally need to install the <classname>afbinit</classname> package, and read the documentation included with it on how to activate the card.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
hardware.xml:1790
|
|
|
422.
|
|
|
Almost any network interface card (NIC) supported by the Linux kernel should also be supported by the installation system; modular drivers should normally be loaded automatically. <phrase arch="x86">This includes most PCI and PCMCIA cards.</phrase> <phrase arch="i386">Many older ISA cards are supported as well.</phrase> <phrase arch="m68k">Again, see <ulink url="&url-m68k-faq;"></ulink> for complete details.</phrase>
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
hardware.xml:1823
|
|
|
432.
|
|
|
OSA-Express in QDIO mode, HiperSockets and Guest-LANs
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
hardware.xml:1883
|
|
|
433.
|
|
|
On &arch-title;, most built-in Ethernet devices are supported and modules for additional PCI and USB devices are provided. The major exception is the IXP4xx platform (featuring devices such as the Linksys NSLU2) which needs a proprietary microcode for the operation of its built-in Ethernet device. Unofficial images for Linksys NSLU2 with this proprietary microcode can be obtained from the <ulink url="&url-slug-firmware;">Slug-Firmware site</ulink>.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
hardware.xml:1892
|
|
|
438.
|
|
|
In some cases the driver you need may not be available as a Debian package. You will then have to look if there is source code available in the internet and compile the driver yourself. How to do this is outside the scope of this manual. <phrase arch="x86">If no Linux driver is available, your last resort is to use the <classname>ndiswrapper</classname> package, which allows you to use a Windows driver.</phrase>
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
hardware.xml:1930
|
|
|
443.
|
|
|
This is a common problem on Netra systems with a Davicom (DEC-Tulip compatible) NIC. In that case the <literal>tulip</literal> driver is probably the correct one. You can prevent this issue by blacklisting the wrong driver module as described in <xref linkend="module-blacklist"/>.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
hardware.xml:1964
|
