Kernel 2.6.25

ph0tios · 2008-03-28 01:49:23

http://linuxdevices.com/news/NS5637467946.html

Pretty cool. I haven't been around Arch too long...so I don't know how fast new kernels hit testing, etc. Will it be in AUR likely before testing or?

bangkok_manouel · 2008-03-28 02:03:59

ABS ftw! using 2.6.25-rc7 and got no problem so far.

ph0tios · 2008-03-28 02:53:58

Sweet!

Is using ABS hard?

Allan · 2008-03-28 02:58:31

It will probably hit [testing] within a couple of days of the official release coming out and into [core] after it stabilizes a bit (around 2.6.25.1 or 2.6.25.2 usually)

tigrmesh · 2008-03-28 03:20:35

ph0tios wrote:

Is using ABS hard?

It's quite easy. Here a a couple of wiki pages to get you started: http://wiki.archlinux.org/index.php/ABS … ild_System and http://wiki.archlinux.org/index.php/Ker … n_with_ABS.

Or, you can just wait for it to move into [core]. It won't take long .

ph0tios · 2008-03-28 03:29:53

tigrmesh wrote:

ph0tios wrote:
Is using ABS hard?
It's quite easy. Here a a couple of wiki pages to get you started: http://wiki.archlinux.org/index.php/ABS … ild_System and http://wiki.archlinux.org/index.php/Ker … n_with_ABS.
Or, you can just wait for it to move into [core]. It won't take long .

Awesome, it's not really any different than using AUR. I would wait, but I kind want to try it out...since I've never used ABS before. I believe it is the kernel pkgbuild in unstable? It has rc5...should I just change it to rc7 in the pkgbuild?

bangkok_manouel · 2008-03-28 03:37:28

ph0tios wrote:

tigrmesh wrote:
ph0tios wrote:
Is using ABS hard?
It's quite easy. Here a a couple of wiki pages to get you started: http://wiki.archlinux.org/index.php/ABS … ild_System and http://wiki.archlinux.org/index.php/Ker … n_with_ABS.
Or, you can just wait for it to move into [core]. It won't take long .
Awesome, it's not really any different than using AUR. I would wait, but I kind want to try it out...since I've never used ABS before. I believe it is the kernel pkgbuild in unstable? It has rc5...should I just change it to rc7 in the pkgbuild?

You can adapt kernel26 PKGBUILD easily as well as it is "rc-ready" already... just have to comment/uncomment and adjust versions, that's all... FTR, I removed all the patches except the GCC one and got no build problem at all.

Allan · 2008-03-28 03:37:38

ph0tios wrote:

It has rc5...should I just change it to rc7 in the pkgbuild?

That and changing the md5sums is usually enough to get most packages to build.

ph0tios · 2008-03-28 03:45:12

Where do I find the correct md5sums? Sorry, I just don't want to mess anything up. Not sure I want to mess with the patches since, when it comes to that I'm not exactly sure what I am doing.

Do I just need to change the basepatch?

pkgname=kernel26mm
_basekernel=2.6.24
_basepatch=2.6.25-rc5
#_mmver=${_basekernel}-mm1
_mmver=${_basepatch}-mm1
pkgver=${_mmver//-/.}

Last edited by ph0tios (2008-03-28 03:47:25)

tomk · 2008-03-28 08:23:31

You want the kernel26 PKGBUILD from the core repo, not the kernel26mm PKGBUILD from the unstable repo.

shining · 2008-03-28 10:11:09

I find the kernel PKGBUILD so messy and confusing, I got something wrong every time I tried to configure it as I wanted.
And when something gets wrong during the build / install, you usually have to restart the whole thing.
Same when you make a change to the config.
So for all these reasons, I prefer using the kernel manually, I find it much easier and practical.
Besides, the files installed are easy to track down manually, there is just /lib/modules/<version> created by make modules_install,
and the kernel image copied to /boot/.
(I built 2.6.25-rc7 on my two pc yesterday that way)

Just to be clear, for all other apps that are smaller, have a more standard PKGBUILD, don't have a complex build time config, and have files splattered on the filesystem, I highly prefer using makepkg.

ph0tios · 2008-03-28 12:47:21

tomk wrote:

You want the kernel26 PKGBUILD from the core repo, not the kernel26mm PKGBUILD from the unstable repo.

Ok...so I have the one from core...I just change the pkgver right?

bangkok_manouel · 2008-03-28 12:56:09

That's the one I used.

>>>!*USE AT YOUR OWN RISK*!<<<

# $Id: PKGBUILD,v 1.297 2008/03/24 17:14:29 tpowa Exp $
# Maintainer: Tobias Powalowski <tpowa@archlinux.org>
# Maintainer: Thomas Baechler <thomas@archlinux.org>
pkgname=kernel26
_basekernel=2.6.24
pkgver=2.6.25
pkgrel=1
pkgdesc="The Linux Kernel and modules"
arch=(i686 x86_64)
license=('GPL2')
groups=('base')
url="http://www.kernel.org"
backup=('boot/kconfig26' etc/mkinitcpio.d/${pkgname}.preset etc/mkinitcpio.d/${pkgname}-fallback.conf)
depends=('coreutils' 'module-init-tools' 'mkinitcpio>=0.5.18')
replaces=('kernel24' 'kernel24-scsi' 'kernel26-scsi'
          'alsa-driver' 'ieee80211' 'hostap-driver26'
          'pwc' 'nforce' 'squashfs' 'unionfs' 'ivtv'
      'zd1211' 'kvm-modules' 'iwlwifi' 'rt2x00-cvs')
install=kernel26.install
source=(ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-$_basekernel.tar.bz2
    #for rc kernel building
    http://www.kernel.org/pub/linux/kernel/v2.6/testing/patch-$pkgver-rc7.bz2
    # the main kernel config files
    config config.x86_64
    # the archlinux boot logos
    logo_linux_clut224.ppm
    logo_linux_mono.pbm
    logo_linux_vga16.ppm
    # standard config files for mkinitcpio ramdisk
    kernel26.preset
    mkinitcpio-$pkgname.conf
    fix-gcc43.patch
)

build() {
  [ "${CARCH}" = "i686" ]   && KARCH=x86
  [ "${CARCH}" = "x86_64" ] && KARCH=x86

  cd $startdir/src/linux-$_basekernel
  # add upstream patch from 2.6.24 series
  patch -Np1 -i ../patch-$pkgver-rc7 || return 1

  patch -Np1 -i ../fix-gcc43.patch || return 1

  # extraversion
  sed -i 's|^EXTRAVERSION = .*$|EXTRAVERSION =-rc7|g' Makefile
  # Arch logo!
  cp ../logo_linux_clut224.ppm drivers/video/logo/
  cp ../logo_linux_mono.pbm drivers/video/logo/
  cp ../logo_linux_vga16.ppm drivers/video/logo/
  if [ "$CARCH" = "x86_64" ]; then
    cat ../config.x86_64 >./.config
  else
    cat ../config >./.config
  fi
  # build the full kernel version to use in pathnames
  . ./.config
  ###for rc kernels
  _kernver="2.6.25-rc7${CONFIG_LOCALVERSION}"
  # load configuration
  make menuconfig
  # build!
  ####################
  # stop here
  #msg "Stopping build"
  #return 1
  ####################
  make 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.map26
  cp arch/$KARCH/boot/bzImage $startdir/pkg/boot/vmlinuz26
  install -D -m644 Makefile \
    $startdir/pkg/usr/src/linux-${_kernver}/Makefile
  install -D -m644 kernel/Makefile \
    $startdir/pkg/usr/src/linux-${_kernver}/kernel/Makefile
  install -D -m644 .config \
    $startdir/pkg/usr/src/linux-${_kernver}/.config
  install -D -m644 .config $startdir/pkg/boot/kconfig26
  mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/include

  for i in acpi asm-{generic,x86} config linux math-emu media net pcmcia scsi sound video; do
    cp -a include/$i $startdir/pkg/usr/src/linux-${_kernver}/include/
  done

  # copy files necessary for later builds, like nvidia and vmware
  cp Module.symvers $startdir/pkg/usr/src/linux-${_kernver}
  cp -a scripts $startdir/pkg/usr/src/linux-${_kernver}
  # fix permissions on scripts dir
  chmod og-w -R $startdir/pkg/usr/src/linux-${_kernver}/scripts
  #mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/.tmp_versions

  mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/arch/$KARCH/kernel

  cp arch/$KARCH/Makefile $startdir/pkg/usr/src/linux-${_kernver}/arch/$KARCH/
  cp arch/$KARCH/Makefile_32 $startdir/pkg/usr/src/linux-${_kernver}/arch/$KARCH/
  cp arch/$KARCH/Makefile_64 $startdir/pkg/usr/src/linux-${_kernver}/arch/$KARCH/
  if [ "$CARCH" = "i686" ]; then
    cp arch/$KARCH/Makefile_32.cpu $startdir/pkg/usr/src/linux-${_kernver}/arch/$KARCH/
  fi
  cp arch/$KARCH/kernel/asm-offsets.s $startdir/pkg/usr/src/linux-${_kernver}/arch/$KARCH/kernel/

  # add headers for lirc package
  mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/drivers/media/video
  cp drivers/media/video/*.h  $startdir/pkg/usr/src/linux-${_kernver}/drivers/media/video/
  for i in bt8xx cpia2 cx25840 cx88 em28xx et61x251 pwc saa7134 sn9c102 usbvideo zc0301; do
   mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/drivers/media/video/$i
   cp -a drivers/media/video/$i/*.h $startdir/pkg/usr/src/linux-${_kernver}/drivers/media/video/$i
  done
  # add dm headers
  mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/drivers/md
  cp drivers/md/*.h  $startdir/pkg/usr/src/linux-${_kernver}/drivers/md
  # add inotify.h
  mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/include/linux
  cp include/linux/inotify.h $startdir/pkg/usr/src/linux-${_kernver}/include/linux/
  # add CLUSTERIP file for iptables
  mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/net/ipv4/netfilter/
  cp net/ipv4/netfilter/ipt_CLUSTERIP.c $startdir/pkg/usr/src/linux-${_kernver}/net/ipv4/netfilter/
  # add wireless headers
  mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/net/mac80211/
  cp net/mac80211/*.h $startdir/pkg/usr/src/linux-${_kernver}/net/mac80211/
  # add dvb headers for external modules
  # in reference to:
  # http://bugs.archlinux.org/task/9912
  mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/drivers/media/dvb/dvb-core
  cp drivers/media/dvb/dvb-core/*.h $startdir/pkg/usr/src/linux-${_kernver}/drivers/media/dvb/dvb-core/
  # add xfs and shmem for aufs building
  mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/fs/xfs
  mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/mm
  cp fs/xfs/xfs_sb.h $startdir/pkg/usr/src/linux-${_kernver}/fs/xfs/xfs_sb.h
  cp mm/shmem.c $startdir/pkg/usr/src/linux-${_kernver}/mm/shmem.c
  # add vmlinux
  cp vmlinux $startdir/pkg/usr/src/linux-${_kernver}
  # copy in Kconfig files
  for i in `find . -name "Kconfig*"`; do 
    mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/`echo $i | sed 's|/Kconfig.*||'`
    cp $i $startdir/pkg/usr/src/linux-${_kernver}/$i
  done

  cd $startdir/pkg/usr/src/linux-${_kernver}/include && ln -s asm-$KARCH asm

  chown -R root.root $startdir/pkg/usr/src/linux-${_kernver}
  find $startdir/pkg/usr/src/linux-${_kernver} -type d -exec chmod 755 {} \;
  cd $startdir/pkg/lib/modules/${_kernver} && \
    (rm -f source build; ln -sf ../../../usr/src/linux-${_kernver} build)
  # install fallback mkinitcpio.conf file and preset file for kernel
  install -m644 -D $startdir/src/${pkgname}.preset $startdir/pkg/etc/mkinitcpio.d/${pkgname}.preset || return 1
  install -m644 -D $startdir/src/mkinitcpio-$pkgname.conf $startdir/pkg/etc/mkinitcpio.d/$pkgname-fallback.conf || return 1
  # set correct depmod command for install
  sed -i -e "s/KERNEL_VERSION=.*/KERNEL_VERSION=${_kernver}/g" $startdir/kernel26.install
  echo -e "# DO NOT EDIT THIS FILE\nALL_kver='${_kernver}'" > ${startdir}/pkg/etc/mkinitcpio.d/${pkgname}.kver
  # remove unneeded architectures
  rm -rf $startdir/pkg/usr/src/linux-${_kernver}/arch/{alpha,arm,arm26,avr32,blackfin,cris,frv,h8300,ia64,m32r,m68k,m68knommu,mips,parisc,powerpc,ppc,s390,sh,sh64,sparc,sparc64,um,v850,xtensa}
}

ph0tios · 2008-03-28 13:29:15

Where would I find the fix-gcc43 patch? It's not in the kernel26 directory...so I am assuming you downloaded it from somewhere?

bangkok_manouel · 2008-03-28 13:33:14

ph0tios wrote:

Where would I find the fix-gcc43 patch? It's not in the kernel26 directory...so I am assuming you downloaded it from somewhere?

http://cvs.archlinux.org/cgi-bin/viewcv … ag=TESTING

ph0tios · 2008-03-28 14:29:03

bangkok_manouel wrote:

ph0tios wrote:
Where would I find the fix-gcc43 patch? It's not in the kernel26 directory...so I am assuming you downloaded it from somewhere?
http://cvs.archlinux.org/cgi-bin/viewcv … ag=TESTING

Thanks again, so far it seems to be building fine.

ph0tios · 2008-03-28 15:03:29

loading package data...
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: catalyst: requires kernel26<=2.6.24.9999
:: ndiswrapper: requires kernel26<=2.6.25-0
:: wlan-ng26: requires kernel26<=2.6.25-0

Do I need to find newer versions of these or uninstall them and reinstall after the kernel is upgraded?

bangkok_manouel · 2008-03-28 15:09:00

ph0tios wrote:

loading package data...
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: catalyst: requires kernel26<=2.6.24.9999
:: ndiswrapper: requires kernel26<=2.6.25-0
:: wlan-ng26: requires kernel26<=2.6.25-0

Do I need to find newer versions of these or uninstall them and reinstall after the kernel is upgraded?

i'm not using those packgages but chances are that you have to rebuild them with the correct kernel version in the PKGBUILD and .install file if any. as I told you, not using them and did not even check file list...

ph0tios · 2008-03-28 15:30:42

Yeah, looks like I do, but I have more interesting troubles at the moment:

FATAL: Hook 'keymap' cannot be found.

ha, why this is missing...I have no idea. How did the previous kernel even install without it I wonder as well. Is there a way I can create it?

Last edited by ph0tios (2008-03-28 15:44:08)

ph0tios · 2008-03-28 16:14:53

Actually, I'll just move this discussion to the section about kernel issues..since it is becoming pretty off topic.

Rokixz · 2008-08-09 09:41:21

ph0tios wrote:

Yeah, looks like I do, but I have more interesting troubles at the moment:
FATAL: Hook 'keymap' cannot be found.
ha, why this is missing...I have no idea. How did the previous kernel even install without it I wonder as well. Is there a way I can create it?

I have this issue too.

rooloo · 2008-08-09 10:27:36

Rokixz wrote:

ph0tios wrote:
Yeah, looks like I do, but I have more interesting troubles at the moment:
FATAL: Hook 'keymap' cannot be found.
ha, why this is missing...I have no idea. How did the previous kernel even install without it I wonder as well. Is there a way I can create it?
I have this issue too.

???? and?????

???

I'll give you a hint, its easier to help when people provide useful information.

cat /etc/mkinitcpio.conf

I assume you have a keymap hook for one of two reasons.

#1 being your in a different country and you need this hook, unlikely, but maybe

#2 you are using an old mkinitcpio.conf file. MORE LIKELY!!! double check /etc and see if you have a mkinitcpio.conf.pacnew file. Then double check the hook line in there. Is there a difference?

Rokixz · 2008-08-09 11:15:05

Sorry about that. Yes, I'm from different country, my keyboard use lithuanian symbols, but I'm not panic. I just wan't to know, why I'm getting this message. I'm never get it until last kernel upgrade.

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="ata_generic ata_piix ide_disk"

# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""

# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
#
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect ide scsi sata filesystems"
#
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev ide scsi sata usb filesystems"
#
# This setup assembles an ide raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev ide raid encrypt filesystems"
#
# This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect pata scsi ide filesystems keymap"

rooloo · 2008-08-09 11:49:11

Do you have any mkinitcpio.conf.pacnew files?

I do not have the keymap hook, so I am not sure how you got the keymap hook, as we all download the same package.

Rokixz · 2008-08-09 13:34:57

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""

# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""

# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
#
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
#
# This is identical to the above, except the old ide subsystem is
# used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
#
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
#
# This setup assembles an pata raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev pata raid encrypt filesystems"
#
# This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect pata scsi sata filesystems"

mkinitcpio -H keymap
/sbin/mkinitcpio: line 92: /lib/initcpio/install/keymap: No such file or directory

Hm, maybe you're right. Whatever, I don't have any problems for this.

Last edited by Rokixz (2008-08-09 13:36:39)

Arch Linux

#1 2008-03-28 01:49:23

Kernel 2.6.25

#2 2008-03-28 02:03:59

Re: Kernel 2.6.25

#3 2008-03-28 02:53:58

Re: Kernel 2.6.25

#4 2008-03-28 02:58:31

Re: Kernel 2.6.25

#5 2008-03-28 03:20:35

Re: Kernel 2.6.25

#6 2008-03-28 03:29:53

Re: Kernel 2.6.25

#7 2008-03-28 03:37:28

Re: Kernel 2.6.25

#8 2008-03-28 03:37:38

Re: Kernel 2.6.25

#9 2008-03-28 03:45:12

Re: Kernel 2.6.25

#10 2008-03-28 08:23:31

Re: Kernel 2.6.25

#11 2008-03-28 10:11:09

Re: Kernel 2.6.25

#12 2008-03-28 12:47:21

Re: Kernel 2.6.25

#13 2008-03-28 12:56:09

Re: Kernel 2.6.25

#14 2008-03-28 13:29:15

Re: Kernel 2.6.25

#15 2008-03-28 13:33:14

Re: Kernel 2.6.25

#16 2008-03-28 14:29:03

Re: Kernel 2.6.25

#17 2008-03-28 15:03:29

Re: Kernel 2.6.25

#18 2008-03-28 15:09:00

Re: Kernel 2.6.25

#19 2008-03-28 15:30:42

Re: Kernel 2.6.25

#20 2008-03-28 16:14:53

Re: Kernel 2.6.25

#21 2008-08-09 09:41:21

Re: Kernel 2.6.25

#22 2008-08-09 10:27:36

Re: Kernel 2.6.25

#23 2008-08-09 11:15:05

Re: Kernel 2.6.25

#24 2008-08-09 11:49:11

Re: Kernel 2.6.25

#25 2008-08-09 13:34:57

Re: Kernel 2.6.25

Board footer