kernel26nitro [updated to 2.6.9-rc4-nitro1]

hyp0luxa · 2004-09-25 01:08:32

here's a PKGBUILD for 2.6.9-rc4-nitro1, adapted from dp's kernel26mm PKGBUILD.

# $Id: PKGBUILD,v 1.5 2004/08/22 16:43:06 damir Exp $
# Contributor: hyp0luxa <hyp0luxa@yahoo.com>

pkgname=kernel26nitro
origkernelver=2.6.9-rc4
newkernelver=2.6.9
rcver=4
nitrover=1
pkgver=${newkernelver}.rc${rcver}.nitro${nitrover}
kernelver=${origkernelver}-nitro${nitrover}
pkgrel=1
pkgdesc="The Linux Kernel and modules (IDE support) [nitro kernel]"
url="http://www.sepi.be/nitro.php"
backup=('boot/kconfig26nitro')
depends=('module-init-tools')

source=(http://www.kernel.org/pub/linux/kernel/v2.6/testing/linux-$origkernelver.tar.bz2 
          http://www.sepi.be/nitro/$kernelver/patch-$kernelver.bz2 
          config 
          logo_linux_clut224.ppm)

build() {

  # if we run the makepkg more than once and use 'makepkg -e' to save time:
  if [ -d $startdir/src/linux-${origkernelver} ]
  then
     cd $startdir/src/linux-${origkernelver}
     #apply nitro patchset
     patch -Np1 -i ../patch-$kernelver || return 1
     mv $startdir/src/linux-${origkernelver} $startdir/src/linux-$kernelver
  fi

  cd $startdir/src/linux-$kernelver

  #CLEAN-ME:
  if [ -f ../${kernelver} ]
  then
     rm ../${kernelver} # cleanup the existing patch (needed, if "makepkg -e" for another round)
  fi

  # get rid of the 'i' in i686
  carch=`echo $CARCH | sed 's|i||'`
  cat ../config | sed "s|#CARCH#|$carch|g" >./.config
  mv -f $startdir/config $startdir/config.orig

  # replace logo:
  cp $startdir/src/logo_linux_clut224.ppm $startdir/src/linux-$kernelver/drivers/video/logo/ && echo "==> logo replaced successfully"
  sleep 2

  # let's be "user-friendly":
  echo "==> "
  echo "==> How do you want to configure the kernel:"
  echo "==> ----------------------------------------"
  echo "==> (for ArchLinux defaults, use 'not_at_all (1)')"
  echo "==> "
  AUSWAHL="not_at_all menuconfig xconfig oldconfig config"
           select opt in $AUSWAHL; do
               if [ "$opt" = "not_at_all" ]; then
                yes "" | make config || return 1
                mv $startdir/config.orig $startdir/config
                break
               elif [ "$opt" = "menuconfig" ]; then
                make menuconfig || return 1
                cp .config $startdir/config && echo "==> your config was saved to $startdir/config"
                break
               elif [ "$opt" = "xconfig" ]; then
                make xconfig || return 1
                cp .config $startdir/config && echo "==> your config was saved to $startdir/config"
                break
               elif [ "$opt" = "config" ]; then
                make config || return 1
                cp .config $startdir/config && echo "==> your config was saved to $startdir/config"
                break
               elif [ "$opt" = "oldconfig" ]; then
                make oldconfig || return 1
                cp .config $startdir/config && echo "==> your config was saved to $startdir/config"
                break
               else
                clear
                echo "==> I don't understand (bad option) ... assuming you don't want "
                echo "==> to configure and use the defaults."
                sleep 1
                echo "==> 3..."
                sleep 1
                echo "==> 2..."
                sleep 1
                echo "==> 1..."
                sleep 1
                echo "==> 0: GO! --------------------------- :-)"
                yes "" | make config || return 1
                mv $startdir/config.orig $startdir/config
                break
               fi
           done

  echo ""
  echo "==> Building the kernel $kernelver will start in 2s ! "
  echo "==> Happy compiling and good luck :-)"
  echo ""
  sleep 2

  make clean bzImage modules || return 1

  mkdir -p $startdir/pkg/{lib/modules,boot}
  make INSTALL_MOD_PATH=$startdir/pkg modules_install || return 1

  cp System.map $startdir/pkg/boot/System.map26nitro

  cp arch/i386/boot/bzImage $startdir/pkg/boot/vmlinuz26nitro

  install -D -m644 Makefile $startdir/pkg/usr/src/linux-$kernelver/Makefile
  install -D -m644 .config $startdir/pkg/usr/src/linux-$kernelver/.config
  install -D -m644 .config $startdir/pkg/boot/kconfig26nitro

  mkdir -p $startdir/pkg/usr/src/linux-$kernelver/include
  mkdir -p $startdir/pkg/usr/src/linux-$kernelver/arch/i386/kernel

  for i in acpi asm-generic asm-i386 config linux math-emu net pcmcia scsi video; do
    cp -a include/$i $startdir/pkg/usr/src/linux-$kernelver/include/
  done

  # copy files necessary for later builds, like nvidia and vmware
  cp -a scripts $startdir/pkg/usr/src/linux-$kernelver/
  mkdir -p $startdir/pkg/usr/src/linux-$kernelver/.tmp_versions
  cp arch/i386/Makefile $startdir/pkg/usr/src/linux-$kernelver/arch/i386/
  cp arch/i386/kernel/asm-offsets.s $startdir/pkg/usr/src/linux-$kernelver/arch/i386/kernel/

  # copy in Kconfig files
  for i in `find . -name "Kconfig*"`; do
    mkdir -p $startdir/pkg/usr/src/linux-$kernelver/`echo $i | sed 's|/Kconfig.*||'`
    cp $i $startdir/pkg/usr/src/linux-$kernelver/$i
  done
  cd $startdir/pkg/usr/src/linux-$kernelver/include && ln -s asm-i386 asm
  chown -R root.root $startdir/pkg/usr/src/linux-$kernelver
  cd $startdir/pkg/lib/modules/$kernelver && 
    (rm -f build; ln -sf /usr/src/linux-$kernelver build)
}

Notes:
You can use SMP, SMT, and PREEMPT now.
If you run VMWARE, do not use 1GB_LOWMEM (VMWARE modules won't compile)
If you're going to compile in Reiser4, be sure that 4K stacks is off
If you have an nVidia card, you can use the regular arch nvidia package

Enjoy!

colnago · 2004-09-25 07:52:37

Hi,

Using the arch config I got scsi errors on qlaxxx. I am trying again with a stripped down config. Also note that it looks like ati cards are out for this one. Also note that nitro2 patches are out.

Thanks

Mr Green · 2004-09-25 08:06:20

Woahh that is waaaay cool 8) ....

EDIT gave it a go ... build failed in the same place.....:cry:

Why did you not use PKGBUILD in wiki for multiple kernels ?

colnago · 2004-09-25 09:50:39

I am running on it now. I took out the qla... stuff in the scsi low-level driver section. The preemption flag is CONFIG_PREEMPT, not CONFIG_PREEMT. I also took out the reiser4/xfs/jsf stuff and a bunch of drivers that I don't need. I put in APIC (my system doesn't reboot w/o it) and changed to amd processor. I have not tried the nvidia drivers yet since I did not have them in for 2.6.8.1 and I did not want to have to screw around when switching kernels.

The nitro page basically says stay away from nitro2.

hyp0luxa, thanks again for this.

I was wrong before, only the nitro2 patches kill the ati support.

Mr Green · 2004-09-25 09:58:06

low level drivers give us clue as much as I like looking at kernel configs (not!) ... yeah figured out .. PREEMT thing

If & when I can get it to compile then I will try it with Nvidia ...

did you patch it again to get acpi ?????

8)

hyp0luxa · 2004-09-25 10:00:29

yeah, the maintainers said nitro2 was unstable, because it's based on 2.6.9-rc2-mm2 which i had no luck with either. i don't use any scsi devices, so i wouldn't know about any of those issues, but on my P4/2.8 IDE system, this kernel is performing very well compared to 2.6.8.1 and 2.6.9-rc2-mm1.

i didn't add any additional patches to get ACPI working.

By the way, this, like all experimental kernels, is not guaranteed to work on all systems. I couldn't get mm2, ck8, or love to work on my box, but alas, this one did it for me! good luck!

by the way, dp's kernel26mm PKGBUILD was easier to work with for me than the one in the WIKI

Mr Green · 2004-09-25 10:06:00

I do not use any scsi stuff here but it breaks as above .. thing is I'm too much rolling kernel newbie to know what to remove ... yeah it may compile but it sure will not work

but hey thats half the fun.... & I want more 8)

hyp0luxa · 2004-09-25 10:15:12

Mr. Green: what's breaking?

dp · 2004-09-25 10:55:10

i had first to find out, what a nitro-kerneltree is ...

after the url, it seems to be a crossing of a ck-kernel with other patches added --- anyone has more info than on the $url?

dp · 2004-09-25 10:57:39

kexec http://kerneltrap.org/node/view/3870

Mr Green · 2004-09-25 11:14:55

http://www.sepi.be/ home of nitro.....

errr I will have another go & post error :-)

dp custom bleeding edge kernels are calling you .....

Mr Green · 2004-09-25 11:35:32

Ok....

drivers/scsi/qla2xxx/qla_os.c: In function `qla2x00_queuecommand':
drivers/scsi/qla2xxx/qla_os.c:315: sorry, unimplemented: inlining failed in call to 'qla2x00_callback': function not considered for inlining
drivers/scsi/qla2xxx/qla_os.c:269: sorry, unimplemented: called from here
drivers/scsi/qla2xxx/qla_os.c:315: sorry, unimplemented: inlining failed in call to 'qla2x00_callback': function not considered for inlining
drivers/scsi/qla2xxx/qla_os.c:269: sorry, unimplemented: called from here
make[3]: *** [drivers/scsi/qla2xxx/qla_os.o] Error 1
make[2]: *** [drivers/scsi/qla2xxx] Error 2
make[1]: *** [drivers/scsi] Error 2
make: *** [drivers] Error 2
==> ERROR: Build Failed.  Aborting...

HTH

:?

dp · 2004-09-25 12:28:33

Mr Green wrote:

http://www.sepi.be/ home of nitro.....

http://www.sepi.be/nitro.php yes, i know (it's the $url)... but i don't see the point using this tree (what's the big advantage compared to other trees)

actually, anyone can collect patches together and make a new kernel tree, but this takes a _lot_ of time and people tend to use work others already did (mm, bk, ck ...) --- the nitro tree must be made for an advantage i don0t yet see (it's a mix of ck, mm and some external patches, afics)

Mr Green wrote:

errr I will have another go & post error :-)
dp custom bleeding edge kernels are calling you .....

he he ... acutally, i don't have time at all for these, but as the vanilla troubles my own coding (my (primitive) code (comparing very large strings of 1-2gb) is using a lot of ram and a lot of swap that tends to kill the vanilla regularly) i'm forced to use mm (this means automatically, also run it mainly for everything, because i don't want to reboot every hour when i decide to do something else), so i included the mm in extra

maybe you realized that the mm was not upgraded to the release candidates that came out --- it is not, because i'm lazy but (because i have exams this month and) because the 2.6.9-rcX-mmY is a "bastard" (biological meaning) that do not want to run as it should on my machine (same with the vanilla 2.6.9-rcX) and if i cannot make it run on mine, how can it be usefull for others to use it instead of the older working one?

awaiting for the 2.6.9 to come out

dp · 2004-09-25 12:29:13

Mr Green wrote:

Ok....

drivers/scsi/qla2xxx/qla_os.c: In function `qla2x00_queuecommand':
drivers/scsi/qla2xxx/qla_os.c:315: sorry, unimplemented: inlining failed in call to 'qla2x00_callback': function not considered for inlining
drivers/scsi/qla2xxx/qla_os.c:269: sorry, unimplemented: called from here
drivers/scsi/qla2xxx/qla_os.c:315: sorry, unimplemented: inlining failed in call to 'qla2x00_callback': function not considered for inlining
drivers/scsi/qla2xxx/qla_os.c:269: sorry, unimplemented: called from here
make[3]: *** [drivers/scsi/qla2xxx/qla_os.o] Error 1
make[2]: *** [drivers/scsi/qla2xxx] Error 2
make[1]: *** [drivers/scsi] Error 2
make: *** [drivers] Error 2
==> ERROR: Build Failed.  Aborting...

HTH

:?

if you don't need it, disable it ;-)

if you use the config from kernel26mm, then have a look at this lines:

[damir@Asteraceae kernel26mm]$ more config | grep QLA
CONFIG_SCSI_QLA2XXX=y
CONFIG_SCSI_QLA21XX=m
CONFIG_SCSI_QLA22XX=m
CONFIG_SCSI_QLA2300=m
CONFIG_SCSI_QLA2322=m
CONFIG_SCSI_QLA6312=m
CONFIG_SCSI_QLA6322=m

by the way: this should be reported to the tree maintainer (nitro maintainer) to inform him/her to fix it or inform people

Mr Green · 2004-09-25 12:50:23

ahhhh I'm so stupid I should have guessed Linux tells you whats wrong :oops:

dp... I love you man ..... 8)

I'll report it to seppe but as he says its experimental stuff.. I love it .....

configs you love or hate em'

Back to compiling ........

EDIT 2.6.9-rc2-nitro3 built watch out for those nvidia drivers

hyp0luxa · 2004-09-27 15:27:23

2.6.9-rc2-nitro3 is kicking ass!

you can use CONFIG_PREEMPT now

nvidia was kind of a pain though

Mr Green · 2004-09-27 15:31:31

now you tell me I took it out .....

nvidia no luck yet .... have you got a fix ???

hyp0luxa · 2004-09-27 16:26:25

actually, it hardlocked on me after about an hour so i'm back to nitro1. i'm going to try rebuilding it without CONFIG_PREEMPT to see if that's what it is. I do have a fix for nvidia, i'll post the PKGBUILD for nvidia-nitro later today once i get the patch issues sorted out.

I think that it's just xorg locking up. Seems the nvidia patches i got from the darkside are a bit buggy, i'll work on it later.

hyp0luxa · 2004-09-29 03:08:24

nitro4 is out. apparently the stability issues with nitro3 have been fixed. I'll build and test it tomorrow.

Arch Linux

#1 2004-09-25 01:08:32

kernel26nitro [updated to 2.6.9-rc4-nitro1]

#2 2004-09-25 07:52:37

Re: kernel26nitro [updated to 2.6.9-rc4-nitro1]

#3 2004-09-25 08:06:20

Re: kernel26nitro [updated to 2.6.9-rc4-nitro1]

#4 2004-09-25 09:50:39

Re: kernel26nitro [updated to 2.6.9-rc4-nitro1]

#5 2004-09-25 09:58:06

Re: kernel26nitro [updated to 2.6.9-rc4-nitro1]

#6 2004-09-25 10:00:29

Re: kernel26nitro [updated to 2.6.9-rc4-nitro1]

#7 2004-09-25 10:06:00

Re: kernel26nitro [updated to 2.6.9-rc4-nitro1]

#8 2004-09-25 10:15:12

Re: kernel26nitro [updated to 2.6.9-rc4-nitro1]

#9 2004-09-25 10:55:10

Re: kernel26nitro [updated to 2.6.9-rc4-nitro1]

#10 2004-09-25 10:57:39

Re: kernel26nitro [updated to 2.6.9-rc4-nitro1]

#11 2004-09-25 11:14:55

Re: kernel26nitro [updated to 2.6.9-rc4-nitro1]

#12 2004-09-25 11:35:32

Re: kernel26nitro [updated to 2.6.9-rc4-nitro1]

#13 2004-09-25 12:28:33

Re: kernel26nitro [updated to 2.6.9-rc4-nitro1]

#14 2004-09-25 12:29:13

Re: kernel26nitro [updated to 2.6.9-rc4-nitro1]

#15 2004-09-25 12:50:23

Re: kernel26nitro [updated to 2.6.9-rc4-nitro1]

#16 2004-09-27 15:27:23

Re: kernel26nitro [updated to 2.6.9-rc4-nitro1]

#17 2004-09-27 15:31:31

Re: kernel26nitro [updated to 2.6.9-rc4-nitro1]

#18 2004-09-27 16:26:25

Re: kernel26nitro [updated to 2.6.9-rc4-nitro1]

#19 2004-09-29 03:08:24

Re: kernel26nitro [updated to 2.6.9-rc4-nitro1]

Board footer