|
Kernel 2.6.0 Guides
The new modprobe uses /etc/modprobe.conf rather than
/etc/modules.conf. In Debian you now need to put the component
files into /etc/modprobe.d instead of /etc/modutils. On 13 July 2003 I downloaded the 2.6.0-test1 kernel. To build
it, I need the QT development packages, or libqt3-mt-dev, and
installing this package had this result: The following packages will be REMOVED:For the first time, "make xconfig" worked for the 2.5 / 2.6 series!! So this is the new configuration interface. I started out with the .config file /boot/kernel-2.5.69-5.config, which contains some iptable stuff for the ipaq and otherwise the normal vpr laptop configuration. The kernel built perfectly! With an eerily tidy screenprint during the build, showing only the compiled components and not the compile commands. I installed it right away, and then added it to grub. I'll have to rebuild the nVidia kernel -- there's a new patch for the 2.6.0-test1. However, the new kernel won't boot -- there's some ACPI problem, possibly connected with the yenta module. Notes from the configuration lspnp -- try it! from pcmcia-cs Software Suspend (EXPERIMENTAL) (SOFTWARE_SUSPEND) Enable the possibilty of suspendig machine. It doesn't need APM. You may suspend your machine by 'swsusp' or 'shutdown -z <time>' (patch for sysvinit needed). It creates an image which is saved in your active swaps. By the next booting the, pass 'resume=/path/to/your/swap/file' and kernel will detect the saved image, restore the memory from it and then it continues to run as before you've suspended. Intel Pentium 4 clock modulation (X86_P4_CLOCKMOD) This adds the CPUFreq driver for Intel Pentium 4 / XEON processors. For details, take a look at linux/Documentation/cpu-freq. CardBus yenta-compatible bridge support (YENTA) CardBus is a bus mastering architecture for PC-cards, which allows for 32 bit PC-cards (the original PCMCIA standard specifies only a 16 bit wide bus). Many newer PC-cards are actually CardBus cards. This option enables support for CardBus PC Cards, as well as support for CardBus host bridges. Virtually all modern PCMCIA bridges are CardBus compatible. A "bridge" is the hardware inside your computer that PCMCIA cards are plugged into. To use your PC-cards, you will need supporting software from David Hinds' pcmcia-cs package (see the file <file:Documentation/Changes> for location). Initial RAM disk (initrd) support (BLK_DEV_INITRD) The initial RAM disk is a RAM disk that is loaded by the boot loader (loadlin or lilo) and that is mounted as root before the normal boot procedure. It is typically used to load modules needed to mount the "real" root file system, etc. See <file:Documentation/initrd.txt> for details. IP: tunneling (NET_IPIP) Tunneling means encapsulating data of one protocol type within another protocol and sending it over a channel that understands the encapsulating protocol. This particular tunneling driver implements encapsulation of IP within IP, which sounds kind of pointless, but can be useful if you want to make your (or some other) machine appear on a different network than it physically is, or to use mobile-IP facilities (allowing laptops to seamlessly move between networks without changing their IP addresses; check out <http://anchor.cs.binghamton.edu/~mobileip/LJ/index.html>). Saying Y to this option will produce two modules ( = code which can be inserted in and removed from the running kernel whenever you want). Most people won't need this and can say N. Support for USB Gadgets (USB_GADGET) USB is a master/slave protocol, organized with one master host (such as a PC) controlling up to 127 peripheral devices. The USB hardware is asymmetric, which makes it easier to set up: you can't connect two "to-the-host" connectors to each other. Linux can run in the host, or in the peripheral. In both cases you need a low level bus controller driver, and some software talking to it. Peripheral controllers are often discrete silicon, or are integrated with the CPU in a microcontroller. The more familiar host side controllers have names like like "EHCI", "OHCI", or "UHCI", and are usually integrated into southbridges on PC motherboards. Enable this configuration option if you want to run Linux inside a USB peripheral device. Configure one hardware driver for your peripheral/device side bus controller, and a "gadget driver" for your peripheral protocol. (If you use modular gadget drivers, you may configure more than one.) If in doubt, say "N" and don't enable these drivers; most people don't have this kind of hardware (except maybe inside Linux PDAs).
|