Anyone able to compile kernel 2.6.38.6 on Slackware 13.37 successfully using the config from testing/2.6.38.4? I was able to get .4 and .5 to compile successfully, but with .6 I get the following after running "make modules".
Code:
WARNING: modpost: Found 11 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
Running "make CONFIG_DEBUG_SECTION_MISMATCH=y 2>&1 > outfile" gives me a bunch of WARNINGS as follows:
Code:
WARNING: vmlinux.o(.text+0xe656a): Section mismatch in reference from the function build_all_zonelists() to the function .meminit.text:setup_zone_pageset.clone.56()
The function build_all_zonelists() references
the function __meminit setup_zone_pageset.clone.56().
This is often because build_all_zonelists lacks a __meminit
annotation or the annotation of setup_zone_pageset.clone.56 is wrong.....
WARNING: drivers/watchdog/nv_tco.o(.devinit.text+0x14): Section mismatch in reference from the function nv_tco_init() to the function .init.text:nv_tco_getdevice()
The function __devinit nv_tco_init() references
a function __init nv_tco_getdevice().
If nv_tco_getdevice is only used by nv_tco_init then
annotate nv_tco_getdevice with a matching annotation.
I've getting strange build errors when using make-kpkg with the latest (2.6.39-rc5) vanilla kernel.I'm using the procedure outlined here: https:[url]....e.g.:
Code: Building modules, stage 2. MODPOST 3053 modules WARNING: modpost: Found 60 section mismatch(es).To see full details build your kernel with:'make CONFIG_DEBUG_SECTION_MISMATCH=y' CC arch/x86/crypto/aesni-intel.mod.o[code]....
There is even much more error output but it looks like it is basically the same issue.
I am trying to compile and install a new kernel. I have downloaded the 2.6.37 version from kernel.org and I have extracted it in usr/src/linux-2.6.37/ folder.I have tried to compile it and install it according to the instruction given in the following web site and which I found very useful:ttp://www.digitalhermit.com/linux/K...WTO.html#INTRONevertheless, I am encountering some problems during the make install modules process as I get some warnings (i.e. The title of this post).I thought to ignore the warnings and continue by copying the modules in /lib/modules/linux-2.6.37 but this is not possible since at that directory there is no folder created with the new kernel I am trying to install and thus I get a msg saying: FATAL: could not load /lib/modules/2.6.37/modules.dep.
The warning message: WARNING: modpost: found X section mismatch(es) suggests to run a make CONFIG_DEBUG_SECTION_MISMATCH=y.At the moment I am running a make again and saving the output to a file so that I can see later on what are the mismatches that I get. In any case we are talking about more than 50 mismatches so I am wondering if these mismatches are not that serious and the problem I cannot install and copy the modules is something else
I would like to extract debug information but I have some problems. For example, I have a executable a.out...
Quote:
nm -f sysv a.out | grep ".global_var" >vars.txt
With this command I extract all my variables. All of them are in .global_var section, and it give me follow information:
Quote:
CAN_station_n |08073258| D | OBJECT|00000001| |.global_var CONTROLend |080732a7| D | OBJECT|00000001| |.global_var
[code]....
Well, I have only address of my vars, but I would like to know type var or struct of the variables. With dwarf dump I have all of information, but it is a mess...
I haven't used slackware for many years. There used to be a sticky thread with a great kernel compiling guide for slackware. It feels somewhat unnatural to me to use slackware without a shiny new kernel. Does that guide still exist? I'm working from memory right now.
I want to compile a kernel to add a few options that are not enabled in the huge-smp-2.6.29.6 that comes with slackware. specifically, i want to add TASK_DELAY_ACCT and TASK_IO_ACCOUNTING so that I can use iotop. I just want to add those 2 options to the new kernel, everything else I'd like to keep the way it is as the system has been running just fine. Will running 'make menuconfig' in /usr/src/linux default to the options that are used in the stock kernel?
I am currently having an issue installing the FGLRX driver in slackware 13.1. I use a customer kernel due to buggy acpi on my toshiba laptop. The steps i took to compile my kernel are as followed. hu
make mrproper in /usr/src/linux directory patch /usr/src/linux directory copy kernel config from /boot directory make menguconfig and load config the make all make modules install i have also tried make install as well then i mopy system.map the kernel file and config file into /boot directory edit lilo reboot ... everything works fine acpi works properly like before.. now the problem comes.. I try to install the fglrx drivers and i get the error message Code: Error: kernel includes at /lib/modules/2.6.33.4-smp/build/include do not match current kernel. they are versioned as "" instead of "2.6.33.4-smp". you might need to adjust your symlinks: - /usr/include - /usr/src/linux ERROR: I don't have make module Am I doing something wrong setting up my kernel. Issue on my gentoo box I have.
I compiled a kernel using a previous kernel config after I switched to the ext4 file system. Previously it was using ext3 and the kernel compiled and ran fine. I added support for ext4 to the config but when I went to boot I had a kernel panic. The error was "kernel can't mount vfs on (8,5)". Root is on sda5, I don't know what the 8 is. I started over, using mrproper and made a new config, but got the same error. I created an initrd with the ext4 file system but then the kernel said it couldn't mount root on ext3 because of unique options. (something along those lines) I booted back into the default kernel and saw that it had a similar error right after the bios check, but it loaded fine. I'm wondering why the kernel is saying that the ext4 file system is ext3.
This is my first effort in making something more appropriate for laptop users (exclusively). This is a kernel config for 2.6.30.5. I started with the Slackware Generic-SMP 32bit kernel config (this is a 32bit kernel config). All credit for (in my opinion) the best starting place for any kernel config goes to Patrick Vokerding. (Please tell me if I am or am not doing this properly in terms of respecting the work of others, GPL, GNU, etc.)
Which directly is accessible during the %pre section? I try to use wget to retrieve a file from FTP to /root but after the machine is build, I don't see that file in /root directory.
The new 2.6.35.7 kernel fails to boot on my Lenovo laptop. I had previously compiled a 2.6.35 kernel with a couple of different .config files and never had it boot properly. The failure occurs very quickly and I am including the final screenshot in case that helps.
Experienced that building the vbox guest additions (on the binary/non-free vbox) on a slackware --current guest (with windows *and* linux as a host) fails now with the new kernel's just released in --current?
i'm using this guide videos - howto: debian linux kernel compilation, part 1 and the author says i need kernel 2.6.26 this version of kernel doesnt longer exist in kernel.org website and the only 2.6.26 i found is a patch here. should i use the patch? or download another version of kernel?
probably an obvious error so I apologise in advance - trying to install vmware player, and it needs the kernel-source to build drivers. I've gone out and downloaded kernel-source for my running kernel.
However it's complaining that the kernel-source (2.6.31.12-0.1) does not match the running kernel (2.6.31.12-0.1-desktop).
Presumably there's something I need to do in order to get the 2.6.31.12-0.1 aligned to 2.6.31.12-0.1-desktop?
uname -r prints 2.6.18-164.el5 Yum install kernel-headers/kernel-devel gives me 2.6.18-194 When trying to run virtualbox I get an error: Kernel Driver not installed: (rc=-1908) Please reinstall the kernel module by running "/etc/init.d/vboxdrv setup" as root...
/etc/init.d/vboxdrv setup Stopping VirtualBox kernel modules [OK] Uninstalling old VirtualBox DKMS kernel modules [OK] Trying to register the VirtualBox kernel modules using DKMS Error! Your kernel headers for kernel 2.6.18-164.el5 cannot be found at /lib/modules/2.6.18-164.el5/build or /lib/modules/2.6.18-164.el5/source. [FAILED] (Failed, trying without DKMS) Recompiling VirtualBox kernel modules [FAILED] (Look at /var/log/vbox-install.log to find out what went wrong)
I'm assuming the setup program is using the output from uname -r to determine the kernel, the problem is the kernel sources I've got from yum do not jibe with the uname value.
I am running a server with a GRSecurity patched Kernel 2.6.32.36. I've tried to optimize the kernel as much as I can and know it (removing options, not needed drivers and so on) and compiled the modules into the kernel (no loadable modules anymore). I've started with Slackware 13.0 and the default config for 2.6.29.6-huge. Still I am not sure what to remove/optimize further now.
My question: Is there a way to boot with a kernel with loadable modules, check which modules are really needed for this hardware, (do something like lsmod) and save the running configuration modules for a next kernel compile to be the default .config instead of writing them down by hand and search for the appropriate names in .config or during menuconfig? (Note: zcat /proc/config.gz > .config is NOT the way I want, as it gives me just the current kernel config)
Trying to compile DOSbox version 0.70. Apparently this is the only version that can run Privateer flawlessly.Problem is, when I extract the source and try to './configure', I get an error that SDL 1.2 is not installed.
Code: anthony@anthony-1010:~/Games/DOS/dosbox-0.70$ ./configure checking build system type... i686-pc-linux-gnu
I just installed 2.6.35.12-88.fc14.x86_64 via Software Update and rebooted. When selecting new kernel to boot from, the boot sequence doesn't finish. I am not sure how t o troubleshoot; I am prompted for the PassWord for encrypted /home, but after that, it freezes.
You maybe know that VirtualBox has an "immutable" feature for HDD images. I.e. setup the system, if the stuff is in place, you can set the image to IMMUTABLE to prevent any changes to the image. Differences are written to a separated image. So on the next boot you'll see that all the (unintended) changes are gone and the "old" system is up & running again. I run an old SuSE 10.3 on a write-protected SD-IDE-Adapter. Changing and playing with RPMs is a mess due to around 50 changes I had to do to make that work. Is there any option to mount an SD-card as RO and having all the changes written to e.g. /dev/sda3? To make it clear: I thought about something like a RAID-X system, but could not find any description on how to setup a raidtab.
Recently, I upgraded 11.1 to 11.2. Everything seemed to go fine. However, for some reason the system boots with the debug kernel - 2.6.31.5-0.1-debug. According to Yast every kernel under the sun seems to be loaded on the system. Grub, however, gives two choices - one for the regular and one for the failsafe system. They both boot to the debug kernel.
How do I get this thing to load into the regular, as opposed to the debug, kernel?
I am having a problem with lockups on a new FC12 box (dual core 3 ghz, 4 gb memory, HDPVR, nvidia 8400gs). This happens reliably when replaying MythTV videos, but also randomly at other times using other apps. Usually but not always this is accompanied by a kernel panic (caps lock + scroll lock lights flash on keyboard).
I did a core dump with kdump and it reports: Thread 1 (<main task>):
Cannot access memory at address 0xffff880028025b70I am in the process of running memtest86+ right now, and it's been through several passes without errors. I know it needs to run more, but given the reliability of this problem with MythTV video playback I am wondering if the problem could be in the video card memory. Any linux (or bootable) tester for video memory? All I am able to find are some things for windoze such as this. Also is there any way to track that address from the core dump back to a physical location?
Googled this and found the same problem mentioned in the yum site: [root@plouton ~]# yum update kernel Loaded plugins: refresh-packagekit Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package kernel.x86_64 0:2.6.33.6-147.fc13 set to be installed --> Finished Dependency Resolution --> Running transaction check ---> Package kernel.x86_64 0:2.6.33.4-95.fc13 set to be erased --> Finished Dependency Resolution Dependencies Resolved
Now I've got debug, default, desktop, ec2, trace, vanilla, xen installed im my system. I usually only boot with desktop, and I was wondering if it is OK to remove other stuff except debug, default, and desktop.
I'm trying to run extract-ikconfig because I've mistakenly deleted an old kernel config that I'd like to recover. However, when running the script from the latest (2.6.32.5) tree I run into this error:
Quote:
ERROR: Unable to extract kernel configuration information.
This kernel image may not have the config info.
Coincidentally, this happens with all of my kernel images. Is it a fixable problem? I should really set CONFIG_IKCONFIG_PROC next time..
