Here is a recent whitepaper entitled "Migrating to Linux kernel 2.6 -- Part 3: Using the 2.6 kernel with your current system"
http://linuxdevices.com/articles/AT5793467888.html It's not bad, a reasonable balance between technical and overview. Anyway, it covers some of the system changes you may have to make in order for 2.6 to work correctly (e.g. sysfs, module-init-tools, etc.). You may find some pointers there. On Thu February 26 2004 03:37, [EMAIL PROTECTED] wrote: <snip> > too long since I built a kernel). I am booting up off of my compiled > kernel, but I am still using the initrd from the 2.6.3 RPM. I am also > unsure about the System.map file, as I have one for each kernel, but there > isn't one that's just labeled System.map. You need the System.map that got built with each kernel you compile. As I understand it, System.map contains symbols or pointers (or something else important) that the kernel needs to properly map, er, "stuff" (maybe system calls?) while it boots/runs. My understanding obviously fades at this point; I guess it's time for a refresher. ;-) You can find the System.map for your newly built kernel in the <kernel source>/arch/i386/boot directory along with the bzImage kernel. Personally, I keep all my old kernel/System.map/config files in /boot and just create a symbolic link to the currently used bunch. For example: $ls -l /boot/ total 2206 -rw-r--r-- 1 root root 730340 Feb 17 23:52 2.6.3-System.map -rw-r--r-- 1 root root 1461190 Feb 17 23:52 2.6.3-vmlinuz -rw-r--r-- 1 root root 23944 Feb 17 23:52 2.6.3.config lrwxrwxrwx 1 root root 16 Feb 17 23:53 System.map -> 2.6.3-System.map -rw-r--r-- 1 root root 512 Nov 28 13:16 boot.0300 lrwxrwxrwx 1 root root 12 Feb 17 23:54 config -> 2.6.3.config -rw------- 1 root root 31232 Feb 17 23:55 map lrwxrwxrwx 1 root root 13 Feb 17 23:54 vmlinuz -> 2.6.3-vmlinuz (Okay, so there's only one kernel in there right now, but when I'm testing a new build I keep multiple kernels). Mind you, I use Slackware so your directory structure might not be the same. The article is fairly vendor-neutral so it should be able to help you in this respect. HTH, Curtis > Anyways, I don't think this will > be a problem. > Things seemed to work better when booting off the 2.6 kernel, I didn't seem > to get the HD errors on boot, and I was able to the the forcedeth driver > for the NIC working, and didn't have the slowdown problem with the web > browsing. The problem I'm having is that the system will not boot fully > when not in failsafe mode. I had to take out the vga kernel option to > actually see why the machine wasn't booting. Both modes boot into runlevel > 3, but when I select the "Linux" option in grub, it gets to about the same > point starting services and then hangs. My next step is to go through the > list of options that are disabled in failsafe mode, and see which one will > allow my system to boot. > On a side note, I'm still thinking about trying to sell this board and get > one that will work with linux right out of the box. After this experience, > can anyone recommend what boards have good Linux support, and what I should > stay away from? > > Thanks again, > > Jesse > > > > _______________________________________________ > clug-talk mailing list > [EMAIL PROTECTED] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
