July 2010 - openSUSE Kernel - openSUSE Mailing Lists

[opensuse-kernel] building a vanilla 2.6.34.x kernel that will be patched with reiser4-for-2.6.34
by doiggl＠velocitynet.com.au 02 Aug '10

02 Aug '10

Hello I am trying to compile a vanilla 2.6.34.x kernel that will be patched with reiser4-for-2.6.34.patch.bz2 and use obs to to compile it to generate a .rpm of the kernel which has reiser4 enabled and I need some assistance. Here is some history so which got me this point [1] > The patches in the kernel-source package are packaged in the patches.xx.tar.bz2 tarballs, the order in which they are applied is > controlled by the series.conf file. There is a special tarball called patches.addon.tar.bz2 and this is where you put patch. > Create a tarballlike this: > $ tar tf patches.addon.tar.bz2 patches.addon/foobar.patch patches.addon/series where the series file contains this line: patches.addon/foobar.patch > And add it to your kernel-source package. If you need to apply more patches, simply list them all in the series file, in the order you want to apply them. So far I have done the following - 1. created patches.addon/series file # echo patches.addon/reiser4-for-2.6.34.patch > patches.addon/series 2. created patches.addon.tar.bz2 # tar -cvf patches.addon.tar patches.addon patches.addon/ patches.addon/series patches.addon/reiser4-for-2.6.34.patch # bzip2 -v patches.addon.tar patches.addon.tar: 5.330:1, 1.501 bits/byte, 81.24% saved, 2406400 in, 451444 out. Remaining items How do i set up a project to link to the 2.6.34 kernel vanilla. 3. Have you a .spec file I could use to do the following items. - unpack the vanilla 2.6.34 kernel - apply the reiser4-for-2.6.34.patch to the vanilla kernel - build the new reiser4 patched/enabled kernel [1] http://lists.opensuse.org/opensuse-packaging/2010-03/msg00125.html Thanks Glenn -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

2 6

[opensuse-kernel] [PATCH] opensuse kernel workflow with osc branch
by Brandon Philips 02 Aug '10

02 Aug '10

Hello Michal- Goldwyn, Petr and I were talking about how it is a bit time consuming to add a quick fix to an osc branch of the kernel source and make sure the .changes is updated and patches added to the tar ball. So, I wrote a quick script based on scripts/log.sh that can ease this workflow to look like this: $ osc branch openSUSE:11.3/kernel-source $ osc co home:philipsb:branches:openSUSE:11.3:Update:Test/kernel-source $ mv ~/linux-2.6/driver-fix-for-something.patch . $ vim series.conf # add patch to series.conf $ ./log.sh $ osc commit The nice thing about this workflow is that it makes it easy to create a quick testing Kernel based on a couple of patches without having to use the git repo. I have used osc_wrapper, which is really great, but it requires some knowledge of how our branches and tags work to checkout the right tree to apply your patch on. I guess it would need to be added to the rpm/ directory so it was accessible from an osc checkout. Obviously we could figure out a way of sharing code with scripts/log.sh. What do you think? Thanks, Brandon >From 4dd13769f5b75aea1c16c796ce98c6c23b920458 Mon Sep 17 00:00:00 2001 From: Brandon Philips <brandon(a)ifup.org> Date: Mon, 19 Jul 2010 05:03:30 -0700 Subject: [PATCH] scripts: rpm/log.sh to create an osc branch workflow Add a nice workflow for adding a patch or two to an osc branch of the kernel. $ osc co home:philipsb:branches:openSUSE:11.3:Update:Test/kernel-source $ mv ~/linux-2.6/driver-fix-for-something.patch . $ vim series.conf # add patch to series.conf $ ./log.sh $ osc commit Signed-off-by: Brandon Philips <bphilips(a)suse.de> --- rpm/log.sh | 170 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 170 insertions(+), 0 deletions(-) create mode 100755 rpm/log.sh diff --git a/rpm/log.sh b/rpm/log.sh new file mode 100755 index 0000000..39f03e0 --- /dev/null +++ b/rpm/log.sh @@ -0,0 +1,170 @@ +#! /bin/sh + +############################################################################# +# Copyright (c) 2004-2006,2008,2009 Novell, Inc. +# All Rights Reserved. +# +# This program is free software; you can redistribute it and/or +# modify it under the terms of version 2 of the GNU General Public License as +# published by the Free Software Foundation. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program; if not, contact Novell, Inc. +# +# To contact Novell about this file by physical or electronic mail, +# you may find current contact information at www.novell.com +############################################################################# + +# Construct a changes entry and commit log from a patch. + +if ! $using_git; then + echo "ERROR: not in a git working directory." + exit 1 +fi + +CHANGES=kernel-source.changes + +trap 'rm -rf "$tmpdir"' EXIT +tmpdir=$(mktemp -d /tmp/${0##*/}.XXXXXX) +message=$tmpdir/message + +log_entry() { + local entry=$1 + + echo "$entry" \ + | fmt --width 65 \ + | sed -e '1s/^/- /' -e '2,$s/^/ /' \ + >> $message +} + + +patch_meta() { + local patch=$1 + + subject=$(formail -c -x Subject < "$patch" \ + | sed -e 's, *\[[#/ A-Za-z0-9-]*\],,') + subject=${subject## } + subject=${subject%.} + + set -- $(formail -c -x References -x Reference < "$patch") + references="$*" +} + +patch_log_entry() { + local patch=$1 subject references old_subj old_ref old_patch="$tmpdir/old" + + git show "HEAD:$patch" >"$old_patch" 2>/dev/null + patch_meta "$old_patch" + old_subj="$subject" + old_ref="$references" + + patch_meta "$patch" + + local msg + if test -z "$subject" -o "$subject" != "$old_subj"; then + msg="$subject${references:+ ($references)}" + elif test "$references" != "$old_ref"; then + if test -n "$references"; then + msg="Update references ($references)" + fi + else + msg="Refresh" + fi + + log_entry "$patch: $msg${msg:+.}" +} + +find_patches() { + osc diff series.conf \ + | sed -n "s/^+\s*$patches.*$/\1/p" +} + +for file in "$@" $(find_patches); do + dirname=$(dirname $file) + basename=$(basename $file) + archive=$dirname.tar.bz2 + + if [ ! -f $basename ]; then + echo "ERROR: $basename added to series.conf but doesn't exist in $PWD" + exit 1 + fi + + if [ ! -d $dirname ]; then + tar xvf $archive + fi + + mv $basename $dirname + rm $archive + tar cfj $archive $dirname + + files[${#files[@]}]=$file +done + +if [ ${#files[@]} -eq 0 ]; then + echo "No modified files" >&2 + exit 1 +fi + +for file in "${files[@]}"; do + if [ "${file:0:1}" = - ]; then + log_entry "${file:1}: Delete." + else + case "$file" in + config/*) + if [ -z "$configs_updated" ]; then + log_entry "Update config files." + configs_updated=1 + fi + ;; + + patches.*) + patch_log_entry "$file" + ;; + + kabi/*/symvers-* | kabi/*/symtypes-* | kabi/*/symsets-* ) + if [ -z "$symvers_updated" ]; then + log_entry "Update reference module symbol versions." + symvers_updated=1 + fi + ;; + + series.conf) + # don't log changes in there + ;; + + *) + log_entry "$file: " + ;; + esac + fi +done + +if [ ! -s $message ]; then + echo "- " >> $message +fi + +if [ -z "$VC" ]; then + VC=vc + for search in $HOME/bin /work/src/bin scripts; do + if [ -x $search/$VC ]; then + VC=$search/$VC + break + fi + done +fi + +if $VC $CHANGES $message; then + entry=$(sed -ne '1,2d' -e '/^--*$/!p' -e '/^--*$/q' $CHANGES) + entry=${entry##$'\n'} + entry=${entry%%$'\n'} +fi + +for c in ls *.changes; do + [ $c = $CHANGES ] && continue + cp $CHANGES $c +done -- 1.7.1 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

3 7

[opensuse-kernel] i915 fix for future 11.3 updates?
by Andreas Jaeger 30 Jul '10

30 Jul '10

I've seen the following pull request, it contains a fix for Intel 915 chips that hang. I've heard many complains of hanging i915 in openSUSE 11.3. My question therefore is: Will this fix be available for the next 11.3 kernel update? http://thread.gmane.org/gmane.comp.video.dri.devel/48089 Andreas -- Andreas Jaeger, Program Manager openSUSE, aj(a){novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

3 4

[opensuse-kernel] SuSE Linux with GRSecurity
by Elmar Stellnberger 30 Jul '10

30 Jul '10

I want to run SuSE-Linux with the GRSecurity kernel extensions and was recommended to use a vanilla kernel on this behalf. What will the vanilla-kernel miss what the openSUSE-Kernel offers (except Apparmor)? Are there any extensions which I could most likely keep without running into trouble? Thanks for Your reply; ES. P.S.: Please send messages not only to the mailing list but also to estellnb(a)gmail.com because I am subscribed as nomail! -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

2 1

[opensuse-kernel] New wiki page for "Kernel of the day"
by Brandon Philips 30 Jul '10

30 Jul '10

Hello All- The Kernel of the Day is an useful tool for bug fixing and testing but using it isn't well documented. So, I created a wiki page based on the notes that I often paste into bug reports: http://en.opensuse.org/SDB:Kernel_of_the_day Please expand if you have anything to add. Thanks, Brandon -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

2 2

[opensuse-kernel] expanded kernel-source (fate 309637)
by Michal Marek 29 Jul '10

29 Jul '10

Hi, here is the first prototype of https://features.opensuse.org/309637: http://gitorious.org/mmarek-misc/kernel-source-expanded (clone url: git://gitorious.org/mmarek-misc/expand-kernel-source.git) It has the history of master, SLE11-SP1 and openSUSE-11.2 since their latest common commit. The scripts to generate this are at http://gitorious.org/mmarek-misc/expand-kernel-source There is still much to do, like handling of patches that do not apply, converting tags, adding merges with mainline / stable when the upstream version changes (to avoid useless huge diffs), converting commit id references in changelogs, etc. The goal is to have a repository that is automatically updated from kernel-source and is pullable. Right now, the repository can change at any time, so do not expect 'git pull' to work. On a related note: Could you please avoid committing dozens of patches at once and instead commit individual patches separately? This would make browsing the history and bisecting much more efficient. Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

3 9

[opensuse-kernel] New version of scripts/log
by Michal Marek 29 Jul '10

29 Jul '10

Hi, scripts/log in master no longer edits the kernel-source.changes file, but instead starts plain 'git commit' and let's you edit the commit message. Nothing should change for you, just continue adding changes and calling scripts/log. A generator of the rpm changelog from git log will be provided later. Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

1 2

[opensuse-kernel] USB-3 on 11.3 x64 error xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
by Bruno Friedmann 26 Jul '10

26 Jul '10

Hi all, I'm now using a new device usb3 ready. But hot-pluging it drive you nowhere dmesg full of xhci_hcd 0000:04:00.0: WARN: Stalled endpoint hardware reference : see http://www.smolts.org/client/show/pub_f42e5aaf-dce8-4423-a4c6-5a304d36dbc7 dmesg extract [703277.432552] usb 8-2: new SuperSpeed USB device using xhci_hcd and address 2 [703277.452250] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep [703277.453121] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep [703277.453876] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep [703277.454754] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep [703277.454915] usb 8-2: New USB device found, idVendor=1759, idProduct=5002 [703277.454923] usb 8-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [703277.454929] usb 8-2: Product: MassStorage Device [703277.454933] usb 8-2: Manufacturer: USB 3.0 [703277.454936] usb 8-2: SerialNumber: WD-WMAZ20161452 [703277.733066] Initializing USB Mass Storage driver... [703277.733493] scsi13 : usb-storage 8-2:1.0 [703277.733654] usbcore: registered new interface driver usb-storage [703277.733655] USB Mass Storage support registered. [703278.733479] scsi 13:0:0:0: Direct-Access USB 3.0 MassStorage 0100 PQ: 0 ANSI: 4 [703278.733659] sd 13:0:0:0: Attached scsi generic sg18 type 0 [703278.735622] sd 13:0:0:0: [sdj] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) [703278.736275] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint [703278.736957] sd 13:0:0:0: [sdj] Write Protect is off [703278.736965] sd 13:0:0:0: [sdj] Mode Sense: 03 00 00 00 [703278.736970] sd 13:0:0:0: [sdj] Assuming drive cache: write through [703278.738513] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint [703278.739234] sd 13:0:0:0: [sdj] Assuming drive cache: write through [703278.739249] sdj: unknown partition table [703278.862035] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint [703278.862603] sd 13:0:0:0: [sdj] Assuming drive cache: write through [703278.862611] sd 13:0:0:0: [sdj] Attached SCSI disk [703867.108949] usb 8-2: USB disconnect, address 2 [703884.744549] usb 8-2: new SuperSpeed USB device using xhci_hcd and address 2 [703884.763176] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep [703884.764063] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep [703884.764810] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep [703884.765704] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep [703884.765858] usb 8-2: New USB device found, idVendor=1759, idProduct=5002 [703884.765861] usb 8-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [703884.765864] usb 8-2: Product: MassStorage Device [703884.765866] usb 8-2: Manufacturer: USB 3.0 [703884.765868] usb 8-2: SerialNumber: WD-WMAZ20161452 [703884.768018] scsi14 : usb-storage 8-2:1.0 [703885.769261] scsi 14:0:0:0: Direct-Access USB 3.0 MassStorage 0100 PQ: 0 ANSI: 4 [703885.769392] sd 14:0:0:0: Attached scsi generic sg18 type 0 [703885.770484] sd 14:0:0:0: [sdk] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) [703885.771023] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint [703885.771915] sd 14:0:0:0: [sdk] Write Protect is off [703885.771915] sd 14:0:0:0: [sdk] Mode Sense: 03 00 00 00 [703885.771915] sd 14:0:0:0: [sdk] Assuming drive cache: write through [703885.773913] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint [703885.774582] sd 14:0:0:0: [sdk] Assuming drive cache: write through [703885.774597] sdk: sdk1 [703885.802118] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint [703885.802773] sd 14:0:0:0: [sdk] Assuming drive cache: write through [703885.802782] sd 14:0:0:0: [sdk] Attached SCSI disk Anybody have an idea ? Linux walt 2.6.34-12-default #1 SMP 2010-06-29 02:39:08 +0200 x86_64 x86_64 x86_64 GNU/Linux -- Bruno Friedmann bruno(a)ioda-net.ch Ioda-Net Sàrl www.ioda-net.ch openSUSE Member User www.ioda.net/r/osu Blog www.ioda.net/r/blog fsfe fellowship www.fsfe.org (bruno.friedmann (at) fsfe.org ) tigerfoot on irc GPG KEY : D5C9B751C4653227 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

2 5

[opensuse-kernel] nouveau
by Donn Washburn 23 Jul '10

23 Jul '10

I am new to this list so here goes an attempt. I have openSuSE1.3 latest version "Teal" on a i686 machine with about everything NVidia. I have an AGP 8x card that used to work correctly with NVidia.run including 3D. However, now under nouveau programs fail. Like a self compiled Flightgear (fgfs) and openSuSE's Blender 2.49b. Both fail with a "nv40_screen_get_param:68 - Unknown PIPE_CAP 29" error. Besides nouveau missing <CTRL><ALT>+/- function. questions 1. Can nouveau be completely removed? 2. Install NV.run to resolve the problem? 3. Is this going to be fixed in Future versions I know that SaX2 is no more. So, I will need a custom /etc/X11/xorg.conf file. -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb(a)comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

2 1

[opensuse-kernel] Which .spec could I use to compile the latest unstable Linux kernel 2.6.35-rcX series ?
by doiggl＠velocitynet.com.au 23 Jul '10

23 Jul '10

Hello, Which .spec could I use to compile the latest unstable Linux kernel 2.6.35-rcX series. Just a vanilla version no patches. Please list a url to the .spec file I could use. Thanks Glenn -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

3 2