Tips for Testing the 2.5 Kernel
Okay, now that you actually have been convinced to try the 2.5 Linux kernel (see previous article), how can you test this kernel out. And, what should you do if you have any problems?
First off, before you configure the 2.5 kernel--say, while you are downloading it--go read Dave Jones's excellent "What to Expect from 2.5" document. In that document, pay specific attention to the sections covering the Input Layer, the Framebuffer layer and module information. These sections of the kernel configuration process are the most confusing for newcomers to the 2.5 series. If you don't pay attention, it is very easy to end up with a kernel that either displays nothing on the screen or doesn't accept any input from the keyboard.
After configuring the kernel with the specific hardware you have on your system, build the kernel, install it and reboot. Don't select all the drivers, here; a number of them do not compile because no one seems to have hardware for them anymore. If you've never done this build and install process before, I suggest you read the Linux Kernel HOWTO, which details all of the necessary steps involved. I also do not recommend that 2.5 be the first kernel you ever build on your own. Try the 2.4 kernel first to rule out any operator errors you might come across.
If you do have hardware for a driver that does not build, please report this. Most kernel developers do not have access to a wide range of hardware, so they are apprehensive about fixing drivers they cannot test. If you post your building problem to the linux-kernel or kernel-janitor's mailing list, and if you have the hardware for the driver and are willing to test patches, you should be able to find a willing developer to provide you with updated code.
Now that your 2.5 kernel is up and running, what should you do to test it? It's simple; do the normal tasks you always do on your 2.4 or 2.2 kernels: run X, browse the Web, read e-mail, play games, write documentation, write code and so forth. Every user stresses the operating system in different ways; therefore, there is no one, correct way to test.
If you think you've found a problem, first off, search the past week or so of the linux-kernel mailing list to see if others have had the same problem; a fix already may have been posted. If you do not see anything relevant, try searching the 2.5 kernel bug database for your specific issue. If you still cannot find anything relevant, please create a new bug in the database so the kernel developers can realize there is a problem. From there, the bug will be assigned to someone to look at, and more importantly, it can be found by others having the same problem in the future.
I hope this short mini-article helps people start testing out the 2.5 kernel. Without users testing, there is no way that the kernel can become stable enough for everyone to use in the future.
Greg Kroah-Hartman is currently the Linux USB and PCI Hot Plug kernel maintainer. He works for IBM, doing various Linux kernel-related things.
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- A Topic for Discussion - Open Source Feature-Richness?
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Validate an E-Mail Address with PHP, the Right Way
- RSS Feeds
- Readers' Choice Awards
- Tech Tip: Really Simple HTTP Server with Python
3 hours 28 min ago
- Reply to comment | Linux Journal
4 hours 1 min ago
- All the articles you talked
6 hours 24 min ago
- All the articles you talked
6 hours 28 min ago
- All the articles you talked
6 hours 29 min ago
10 hours 54 min ago
- Keeping track of IP address
12 hours 45 min ago
- Roll your own dynamic dns
17 hours 58 min ago
- Please correct the URL for Salt Stack's web site
21 hours 10 min ago
- Android is Linux -- why no better inter-operation
23 hours 25 min ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?