- openSUSE Kernel

[opensuse-kernel] mkinitrd script
by Sergei Kanevski 25 Sep '09

25 Sep '09

Hallo, wenn i compile multiple different kernel versions on OpenSuSE_11.1 box and then call: mkinitrd -k bla.img -i bla.rd -m "blub1 blub2 blub3" -M /usr/src/linux-XXX/System.map , i become a monstrous initial RAM-disk file with modules for all kernel versions found in /lib/modules !!! I want just a handy initrd with only modules matching my kernel bla.img . I think there is a bug in mkinitrd-scripts. Best regards Sergei Kanevski -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

2 1

Re: [opensuse-kernel] KOTD release numbering
by Michal Marek 24 Sep '09

24 Sep '09

Coly Li napsal(a): > > Michal Marek Wrote: >> Michal Marek napsal(a): >> FYI, something like this is implemented now. >> E.g. on master there is: >> kernel-desktop-2.6.31-8.99.10.050bdf9.x86_64.rpm >> (the latest factory kernel is kernel-desktop-2.6.31-8.2.x86_64.rpm, 10 >> commits old. The ugly .99 is a hack to override the rebuild counter). >> > > Can you explain a little bit more on "10 commits old". Does it mean the latest > factory kernel is 10 commits older then the latest git kernel-source ? Exactly. Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

1 0

[opensuse-kernel] KOTD release numbering
by Michal Marek 24 Sep '09

24 Sep '09

Hi, (sorry for the long mail, jump to "== Examples ==" below for the important part) I'm thinking about changing the versioning of KOTD packages (http://ftp.suse.com/pub/projects/kernel/kotd/) as the current scheme is a bit of mess. I'd like to 1) make the release string shorter, 2) make the release string sort with official distro kernels nicely, so that with some luck, an older kotd will be replaced by a newer update kernel and vice versa. I'm thinking about the following: drop the branch name and timestamp from the release string (same information is in rpm -qi output, no need to duplicate it here). Instead of the timestamp, use the number of commits (see below) so that the release string increases. To get proper ordering with official kernels, prepend the release string of the last official kernel. More precisely: last update kernel: $version-$release current kotd: $version2-??? if $version == $version2 $release2 = $release.$ncommits.$hash else $release2 = 0.0.0.$hash remember "$version2-0.0" as a fake update kernel and count from there next time endif $ncommits would be the number of commits to the kernel repository since the last update, $hash would be the commit id (same as today). == Examples == The current SLE11_BRANCH kotd would be named kernel-default-2.6.27.25-0.0.22.8dd1bfd.x86_64.rpm because the last released update was 2.6.27.23 and Greg updated to 2.6.27.25 22 commits ago. The next update (if the version stays at .25) will be 2.6.27.25-0.1, i.e. correctly newer than the kotd. The SL110_BRANCH kotd would be named kernel-default-2.6.25.20-0.4.23.4d35a02.x86_64.rpm because the last released update was 2.6.25.20-0.4, 23 commits ago. The next update will be 2.6.25.20-0.5 at least, again newer than the kotd. Maybe the commit id should be prefixed with a "g", just like git-describe does, to make it clear what it is. Does this make sense to everyone? Does anyone depend on the current numbering scheme? Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

3 5

[opensuse-kernel] Re: [opensuse-factory] 'zypper dup' updating kernel when 'zypper up' does not? (fwd)
by Gerald Pfeifer 22 Sep '09

22 Sep '09

[ -> opensuse-kernel ] On Wed, 29 Jul 2009, Michael Schroeder wrote: > On Wed, Jul 29, 2009 at 10:16:55AM +0200, Stephan Kulow wrote: >> I'm afraid the problem is that it sees 2.6.30_10 as higher version >> than 2.6.30.2_1 because it compares by split(/\./, $version) - and >> there you only compare 30 with 30_10 - and there usually _10 is the >> higher one > Just to clarify things, rpm splits by /[^a-zA-Z0-9]/, so > 2.6.30_10 compares to 2.6.30.2_1 as > > 2 6 30 10 > 2 6 30 2 1 > > and 10 > 2. So, reading this again, it seems the best workaround/fix will be to name the next version of the kernel 2.6.32.0 instead of 2.6.32? For somewhat similar reasons this is why I got upstream GCC versioning for the first release from any given branch changed from 4.x to 4.x.0. Can we do the same for the openSUSE kernel? Or actually upstream even? Gerald -- Dr. Gerald Pfeifer E gp(a)novell.com SUSE Linux Products GmbH Director Product Management F +49(911)74053-483 HRB 16746 (AG Nuremberg) SUSE Linux Enterprise, openSUSE, Appliances GF Markus Rex -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

3 4

[opensuse-kernel] Need some kernel symbols
by Johannes Obermayr 17 Sep '09

17 Sep '09

Hi, I built source package "drm-all" from my home:jobermayr repository on my local system and installed the built package but I can not load radeon module (on startup and by myself) because below output of dmesg. I also include some rpm queries for an overview of installed packages (openSUSE-factory - non-released from api.opensuse.org). Can anyone tell me what I have to do that the "Unknown symbols" will become "Known symbols"? Information: Package includes kernel modesetting (KMS) kernel modules and it is based on source code from http://cgit.freedesktop.org/nouveau/linux-2.6/tree/. Thanks in advance, Johannes *[ 9.167503] radeon: Unknown symbol drm_helper_initial_config [ 9.168650] radeon: Unknown symbol drm_fb_helper_fill_fix [ 9.172460] radeon: Unknown symbol drm_fb_helper_blank [ 9.172603] radeon: Unknown symbol drm_fb_helper_check_var [ 9.172746] radeon: Unknown symbol drm_fb_helper_setcolreg [ 9.176061] radeon: Unknown symbol drm_fb_helper_single_fb_probe [ 9.176460] radeon: Unknown symbol drm_fb_helper_fill_var *[ 9.177124] radeon: Unknown symbol drm_helper_mode_fill_fb_struct *[ 9.178015] radeon: Unknown symbol drm_helper_connector_dpms [ 9.178541] radeon: Unknown symbol drm_fb_helper_pan_display [ 9.179252] radeon: Unknown symbol drm_fb_helper_init_crtc_count *[ 9.179729] radeon: Unknown symbol drm_helper_probe_single_connector_modes [ 9.180610] radeon: Unknown symbol drm_fb_helper_free *[ 9.181720] radeon: Unknown symbol drm_helper_resume_force_mode *[ 9.181857] radeon: Unknown symbol drm_crtc_helper_set_config [ 9.182309] radeon: Unknown symbol drm_fb_helper_set_par Symbols marked with * should be available (see below) $ rpm -q --provides kernel-pae | grep drm | grep helper ksym(pae:drm_crtc_helper_set_config) = 5e6378d1 ksym(pae:drm_crtc_helper_set_mode) = b35748ca ksym(pae:drm_helper_connector_dpms) = b8f448c2 ksym(pae:drm_helper_crtc_in_use) = dd6f72c ksym(pae:drm_helper_disable_unused_functions) = 5bcfa2d9 ksym(pae:drm_helper_encoder_in_use) = 88c2650c ksym(pae:drm_helper_hotplug_stage_two) = 3d4ca21f ksym(pae:drm_helper_initial_config) = abdc90b2 ksym(pae:drm_helper_mode_fill_fb_struct) = a7043e ksym(pae:drm_helper_probe_connector_modes) = f6c552a5 ksym(pae:drm_helper_probe_single_connector_modes) = ea224038 ksym(pae:drm_helper_resume_force_mode) = ce9b95d $ rpm -qa | grep kernel kernel-syms-2.6.31-8.2.i586 kernel-pae-devel-2.6.31-8.1.i586 kernel-source-2.6.31-8.2.noarch kernel-firmware-20090909-1.2.noarch kernel-pae-base-2.6.31-8.1.i586 kernel-pae-2.6.31-8.1.i586 linux-kernel-headers-2.6.31-1.9.noarch *I know that other kernel-...-devel packages should also be installed but so I can compile only the one needed flavour package (needs not so much time for compiling...) $ rpm -qa | grep drm-all drm-all-kmp-pae-20090916_2.6.31_8-1.1.i586 rpm -qa | grep xorg-x11-driver-video- xorg-x11-driver-video-ati-debuginfo-6.99_20090914-1.2.i586 xorg-x11-driver-video-unichrome-20090829-1.1.i586 xorg-x11-driver-video-unichrome-debuginfo-20081229-7.15.i586 xorg-x11-driver-video-debuginfo-7.4-139.2.i586 xorg-x11-driver-video-7.4-139.1.i586 xorg-x11-driver-video-ati-6.99_20090914-1.2.i586 * ati driver is excluded from xorg-x11-driver-video and packed in a new package (for better maintenance...) -- 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]
by Кузьминский Михаил 17 Sep '09

17 Sep '09

I've tested today patched default x86-64 kernel from OpenSuSE 11.1 repo (2.6.27.7-9). The kernel was built from source using SRAT/NUMA patches by Kurt Garloff. Kernel w/patches works OK w/my Supermicro X8DTi mobo (w/dual Nehalem Xeon E5520). So the problem is solved. But as I wrote in my previous message here, this problem remains w/11.2 kernels (I checked default binary 2.6.31-4.1 version). Taking into account that Xeon/Nehalem platform is now popular, I beleive this problem is quite common, and may be it's reasonable to insert this patches into 11.2 kernels. Mikhail -- 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] Nehalem/SRAT problem message: sorry
by Кузьминский Михаил 17 Sep '09

17 Sep '09

Pls sorry for sent message about Nehalem/SRAT w/o Subject field (I forgot it): I'm using external mailagent specially for this maillist (my main e-mail address don't work w/opensuse-kernel maillist :-( ). Mikhail -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

1 0

[opensuse-kernel] Power Outage
by ml-admin＠opensuse.org 11 Sep '09

11 Sep '09

Broadcast message from ml-admin(a)opensuse.org (/dev/pts/0) at 07:30 GMT ... The system is going down for halt NOW! -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

1 0

[opensuse-kernel] proc/<pid>/stat timestamp will not be altered
by Stefan Haas 10 Sep '09

10 Sep '09

Hi, I'm trying to readout some load values out of the /proc/<pid>/stat file. As I want to do this only when there were some values changed I do a fstat beforehand on this file to check the modification time. Unfortunatelly, this value never changed even I this file was altered (it is working systems with kernel 2.4). I've tested it on several 2.6 kernels. So, is it possible to enable the "timestamping" for procfs (again) or do you now some workaround how I can check if some values has been changed without parsing the stat-file it every time. Thanks, Stefan -- 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] kvm broken in current factory?
by Andreas Jaeger 08 Sep '09

08 Sep '09

Just tried to boot the current NET Media (openSUSE-NET-x86_64-Build0265- Media.iso - same result with the i586 one) on my Intel Laptop with kvm and it stops very early, last line on the console is (see also appended screenshot): CPU0: Intel QEMU Virtual CPU version 0.10.50 stepping 03 Any ideas what's wrong? Does it work for others? Btw. I had to unset MALLO_CHECK_ first, otherwise qemu would crash (I opened a bug for that already). Andreas -- Andreas Jaeger, 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

1 0