December 2012 - openSUSE Kernel - openSUSE Mailing Lists

[opensuse-kernel] Will the built 3.7.x kernel builds be put into factory and replace the version 3.6.3x builds.
by doiggl＠velocitynet.com.au 16 Dec '12

16 Dec '12

Hello Will the built 3.7.x kernel builds[1] be put into factory[2] and replace the version 3.6.3x builds. Just wondering if it will be included in milestone 3 or 4 for 12.3. Havent seen it used in any openqa tests[eg boot] http://openqa.opensuse.org/results/?sort=-mtime&hours=24&match= Cheers Glenn [1]https://build.opensuse.org/package/show?package=kernel-source&project=Ker… [2]https://build.opensuse.org/package/show?package=kernel-source&project=ope… -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 1

[opensuse-kernel] [PATCH] Fix armv7 kernel-default config
by Guillaume Gardet 13 Dec '12

13 Dec '12

Hi, please find in attachment a patch to fix armv7 kernel-default config. CONFIG_USB_EZUSB_FX2 must be a module instead of built-in to fix build Signed-off-by: Guillaume GARDET <guillaume.gardet(a)opensuse.org> Regards, Guillaume

4 9

[opensuse-kernel] [PATCH] Update omap2plus (armv7) config
by Guillaume Gardet 11 Dec '12

11 Dec '12

Hi, please find in attachment a patch to update omap2plus (armv7) config. It enables TWL* USB drivers and some MUSB drivers. Signed-off-by: Guillaume GARDET <guillaume.gardet(a)opensuse.org> Regards, Guillaume

2 2

[opensuse-kernel] How can external disk be mounted so a ordinary user can write to the disk.
by doiggl＠velocitynet.com.au 11 Dec '12

11 Dec '12

Hello, I have an external drive formatted and attached at bootup. The /etc/fstab entry is this: /dev/sdb1 /media/disk reiserfs acl,user_xattr 1 2 The problem is that a ordinary user cannot write to the disk , only root can. I am using opensuse 12.2 on this machine. Questions. -How can the disk be mounted so a ordinary user can write to the disk ? -What commands do I need to run to to do this, examples would be useful ? Thanks Glenn -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 1

[opensuse-kernel] factory kernel again
by Stephan Kulow 11 Dec '12

11 Dec '12

Hi, Please submit kernel-source more often - the last submission from kernel:head (that I didn't do) is from october ;( Greetings, Stephan -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

1 0

[opensuse-kernel] Use ext4 kernel driver for ext3 filesystems?
by Jan Kara 10 Dec '12

10 Dec '12

Hello, so it has been about 1 year since openSUSE uses ext4 kernel driver for ext2 filesystems. I haven't heard any complaints so I feel it's time to do the same for ext3 as well. Fedora actually uses this setting for over an year already so it's not like we are going to use something heavily experimental. I'd just add that this transition is desirable as ext3 is slowly being deprecated upstream in favor of ext4 (so that we can get rid of similar code bases). Anyone has any objections? Honza -- Jan Kara <jack(a)suse.cz> SUSE Labs, CR -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 2

[opensuse-kernel] script failure
by Giacomo Comes 07 Dec '12

07 Dec '12

I have encountered a bug when running a certain script. The following is the simplest script I can make that triggers the bug: 1) create a cpio archive: gzip -dc /boot/initrd >initrd.cpio 2) run this script: if cpio --quiet -t <initrd.cpio ; then echo true-$? >&2 ; else echo false-$? >&2 ; fi | grep libz The output is: lib64/libz.so.1.2.7 lib64/libz.so.1 true-0 But if I add the option -q to grep: if cpio --quiet -t <initrd.cpio ; then echo true-$? >&2 ; else echo false-$? >&2 ; fi | grep -q libz the output is: false-141 instead of the correct one: true-0 This bug is present in opensuse 12.2, 12.1 and 11.4 and also CentOS 6 (if it matters) opensuse 11.3 is bug free as well as CentOS 5. I discovered the bug while running: lsinitrd /boot/initrd | grep libz whithout the -q option to grep the otuput is correct, when I add the option -q the output is: xz: /boot/initrd: File format not recognized I have tested different version of cpio and grep but it doesn't make any difference. I'm guessing it's a kernel bug or may be it is a compiler bug? By the way, I hope someone is intrested and can hunt the bug. Giacomo -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

5 8

[opensuse-kernel] Why is the kernel doing this?!
by Basil Chupin 06 Dec '12

06 Dec '12

I have 2 identical HDDs (1TB Seagates) and a DVDWriter in my system and all are connected using SATA 3 cables. I couldn't but help noticing last night that transferring data between a new external SATA 3 HDD I bought yesterday and one of my internal drives was at ~130 MB/s as agaist ~27 MB/s with the second drive. So I went looking in /var/log/messages. Sure enough the kernel had decided that the second HDD has a 40-wire cable and has therefore configured it to have UDMA 33! The devices are shown as: ata1 max UDMA 133 configured as 133 UDMA ata5 max UDMA 133 configured as 33 UDMA (because connected using 40-wire cable) ata3 max UDMA 100 configured as 100 UDMA (this is the DVD writer) This was also occurring on my other 32-bit system (different devices of course) and there I was able to overcome this nonsense by adding to the kernel boot parameters- libata.force=1:80c,2:80c but doing similar on the system (see signature line below) the kernel locks up when the system is booting. How the heck can the kernel get it so wrong re the cabling (I know that the SATA and ATA use the same controller) and treats the second HDD as a poor relative? Is the kernel designed to only always know about one single HDD? Does anyone know, please, what I need to add in the kernel boot parameters to get this second HDD running at full UDMA speed? BC -- Using openSUSE 12.2 x86_64 KDE 4.9.4 & kernel 3.6.8-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

3 5

[opensuse-kernel] config updates suggestions
by Cristian Rodríguez 06 Dec '12

06 Dec '12

Hi: The following config options could be changed to match userspace requirements. - CONFIG_AUTOFS4_FS=m --> CONFIG_AUTOFS4_FS=y Rationale: systemd will load the module anyway in all cases. it is used for mount parallelization. The list of modules unconditionality loaded can be seen here http://cgit.freedesktop.org/systemd/systemd/tree/src/core/kmod-setup.c static const KModule kmod_table[]... - CONFIG_PACKET=m --> CONFIG_PACKET=y Rationale: Required and always loaded in userspace, used by dhcp client at least. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

1 0

[opensuse-kernel] [PATCH] Use new suse-module-tools package
by Jan Engelhardt 06 Dec '12

06 Dec '12

The "weak-modules" programs moved to "suse-module-tools" in openSUSE 12.3. "modutils" is an unversioned virtual provides to get at an implementation that has the "insmod", "modprobe"-named executables. Because "modutils" is not even new, it is now unconditionally used in macros.kernel-source. --- rpm/kernel-binary.spec.in | 8 ++++++-- rpm/macros.kernel-source | 2 +- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/rpm/kernel-binary.spec.in b/rpm/kernel-binary.spec.in index 26e2332..654c7c2 100644 --- a/rpm/kernel-binary.spec.in +++ b/rpm/kernel-binary.spec.in @@ -62,7 +62,7 @@ Release: @RELEASE@ License: GPL-2.0 Group: System/Kernel Url: http://www.kernel.org/ -BuildRequires: coreutils module-init-tools sparse +BuildRequires: coreutils modutils sparse BuildRequires: fdupes Provides: multiversion(kernel) Provides: %{name}_%_target_cpu = %version-%release @@ -73,8 +73,12 @@ Provides: kernel-base = %version-%source_rel Obsoletes: %name-base <= 2.6.31 %endif Requires(pre): coreutils awk -# Need a module-init-tools with /usr/lib/module-init-tools/weak-modules2 +# We need the weak-modules2 utility +%if 0%{?suse_version} >= 1230 +Requires(post): suse-module-tools +%else Requires(post): module-init-tools >= 3.4 +%endif # This Requires is wrong, because the post/postun scripts have a # test -x update-bootloader, having perl-Bootloader is not a hard requirement. # But, there is no way to tell rpm or yast to schedule the installation diff --git a/rpm/macros.kernel-source b/rpm/macros.kernel-source index f584129..27fa8bb 100644 --- a/rpm/macros.kernel-source +++ b/rpm/macros.kernel-source @@ -1,6 +1,6 @@ # A few cross-distro definitions: %kernel_module_package_release 1 -%kernel_module_package_buildreqs module-init-tools kernel-syms +%kernel_module_package_buildreqs modutils kernel-syms # Defines %flavors_to_build and %kernel_source() as a side effect. %_kernel_module_package(n:v:r:t:f:Xp:b) \ -- 1.7.10.4 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 5