Master Kernel Thread

[Elrohir]

What about Edgy? has anyone tried to compile 2.6.21 on Edgy? Tried the other day and some warning appear at boot, no kernel panic (as it happened to me once), and then EasyBOX comes to end it all... I'll try once again doing some changes (not disabling Budget Cards), what can I lose?!

[nyinge]

I tried 2.6.21 from feisty and no luck - it almost boots or probably does but I get plenty of errors
for device-mapper table 253.1 or something like that...just after LVM starts

Here for example:

Apr 27 19:24:56 ***** kernel: Inspecting /boot/System.map-2.6.21
Apr 27 19:24:56 ***** kernel: Loaded 25114 symbols from /boot/System.map-2.6.21.
Apr 27 19:24:56 ***** kernel: Symbols match kernel version 2.6.21.
Apr 27 19:24:56 ***** kernel: No module symbols loaded - kernel modules not enab
led.
Apr 27 19:24:56 ***** kernel: inear: Device lookup failed
Apr 27 19:24:56 ***** kernel: [ 72.397106] device-mapper: ioctl: error adding
target to table
Apr 27 19:24:56 ***** kernel: [ 72.646848] device-mapper: table: 254:1: linear
: dm-linear: Device lookup failed
Apr 27 19:24:56 ***** kernel: [ 72.646854] device-mapper: ioctl: error adding
target to table
Apr 27 19:24:56 ***** kernel: [ 72.647623] device-mapper: table: 254:1: linear
: dm-linear: Device lookup failed
Apr 27 19:24:56 ***** kernel: [ 72.647628] device-mapper: ioctl: error adding
target to table
Apr 27 19:24:56 ***** kernel: [ 72.648376] device-mapper: table: 254:1: linear
: dm-linear: Device lookup failed
Apr 27 19:24:56 ***** kernel: [ 72.648380] device-mapper: ioctl: error adding
target to table
Apr 27 19:24:56 ***** kernel: [ 72.649133] device-mapper: table: 254:1: linear
: dm-linear: Device lookup failed
Apr 27 19:24:56 ***** kernel: [ 72.649138] device-mapper: ioctl: error adding
target to table
Apr 27 19:24:56 ***** kernel: [ 72.649881] device-mapper: table: 254:1: linear
: dm-linear: Device lookup failed

Never had so much stress compiling a kernel in Gentoo...

Is it because you're missing some raid support modules? I'm not entirely sure. I've attached an image of how my config looks like. It's running on RAID-0 using dmraid.

[nyinge]

... How large is your kernel image?...

 -rw-r--r--  1 root    root    6.5M Apr 29 00:12 linux-image-2.6.21.1_0429_amd64.deb

[schmolch]

Has anyone successfully rebuilt the ipw3945 module for the 2.6.21 kernel?

I downloaded the module-sources but get an error when i run make about the ieee80211 subsystem.
Am i supposed to use the kernel's ieee80211 support or another version?

This is the error:
WARNING: Your kernel contains ieee80211 symbol definitions and you
are not using the kernel's default ieee80211 subsystem. (Perhaps you
used the out-of-tree ieee80211 subsystem's 'make install' or have
provided a path to the ieee80211 subsystem via IEEE80211_INC.)

I have ieee80211 enabled in the kernel as modules.
Also, /usr/src/linux does point to the 2.6.21 sources.

[lcohen999]

Has anyone successfully rebuilt the ipw3945 module for the 2.6.21 kernel?

I downloaded the module-sources but get an error when i run make about the ieee80211 subsystem.
Am i supposed to use the kernel's ieee80211 support or another version?

This is the error:
WARNING: Your kernel contains ieee80211 symbol definitions and you
are not using the kernel's default ieee80211 subsystem. (Perhaps you
used the out-of-tree ieee80211 subsystem's 'make install' or have
provided a path to the ieee80211 subsystem via IEEE80211_INC.)

I have ieee80211 enabled in the kernel as modules.
Also, /usr/src/linux does point to the 2.6.21 sources.

search in this thread for my name, someone posted a patch you do before you compile the kernel which will get your ipw3945 working

[quark_77]

Hi schmolch,

Here if you can't be bothered searching: http://ubuntuforums.org/showpost.php...&postcount=232.

Can verify this patches and builds successfully using 2.6.21.1 - will be trying a reboot on the new kernel soon. When I have enough time I'm going to pull this patch apart and understand what it does so I can get later versions working - I'm in the middle of A-levels...

Don't forget the ipw3945 daemon to be located in /sbin (/sbin/ipw3945-xyz where xyz='uname -r' for your kernel) and the microcode ipw3945.ucode in /lib/firmware/xyz.

Hope this helps,

Quark_77

[quark_77]

Hi Elrohir,

What about Edgy? has anyone tried to compile 2.6.21 on Edgy? Tried the other day and some warning appear at boot, no kernel panic (as it happened to me once), and then EasyBOX comes to end it all... I'll try once again doing some changes (not disabling Budget Cards), what can I lose?!

Try editing GRUB for your new kernel. Instead of root=/dev/sdaX or /dev/hdaX, first do the following:

sudo vol_id -u /dev/sdaX

This will give you a UUID. Then change the root option I mentioned to:

root=UUID=[the uuid from your root partition]

I can't promise this'll work, I had some problems with my root not being picked up. Feisty uses UUIDs not /dev/sdaX etc perhaps this is the way modern kernels will boot? Editing partitions changes the X number on /dev/sdaX which can be a pain, the UUID never changes.

Hope this helps,

Quark_77

[zarathustra]

Hi Elrohir,



Try editing GRUB for your new kernel. Instead of root=/dev/sdaX or /dev/hdaX, first do the following:

sudo vol_id -u /dev/sdaX

This will give you a UUID. Then change the root option I mentioned to:

root=UUID=[the uuid from your root partition]

I can't promise this'll work, I had some problems with my root not being picked up. Feisty uses UUIDs not /dev/sdaX etc perhaps this is the way modern kernels will boot? Editing partitions changes the X number on /dev/sdaX which can be a pain, the UUID never changes.

Hope this helps,

Quark_77

I'm trying to run 2.6.21.1 on Feisty and my grub is set up correctly like this, but when it tries to boot the kernel is says the drive does not exist (/dev/disk/by-uuid/"long uuid number here" does not exist).

[dannyboy79]

I'm trying to run 2.6.21.1 on Feisty and my grub is set up correctly like this, but when it tries to boot the kernel is says the drive does not exist (/dev/disk/by-uuid/"long uuid number here" does not exist).

and are you sure that when you ran the command to get the UUID for your root partition that you used the correct partition number??? for example, if your feisty root install drive and partition is hard drive 2 and it's on the 3rd partition than the sdXY you would have used would be

sdb3

which will give you the correct UUID fot that drive.


OR

you could just chroot into your install from a livecd and change all references from UUID's back to /dev/sdb3 like in Edgy. You don't have to use UUID's. but also make sure that your device.map is correct and doesn't still call for hdb3 since Feisty is referring to all hard drives as sdXY instead of edgy was still calling ide drives hdXY and sata as sdXY. good luck

[zarathustra]

and are you sure that when you ran the command to get the UUID for your root partition that you used the correct partition number??? for example, if your feisty root install drive and partition is hard drive 2 and it's on the 3rd partition than the sdXY you would have used would be

sdb3

which will give you the correct UUID fot that drive.


OR

you could just chroot into your install from a livecd and change all references from UUID's back to /dev/sdb3 like in Edgy. You don't have to use UUID's. but also make sure that your device.map is correct and doesn't still call for hdb3 since Feisty is referring to all hard drives as sdXY instead of edgy was still calling ide drives hdXY and sata as sdXY. good luck

I think they were already like that, and I've double checked the UUID numbers to make sure they were correct