January 2013 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] SELinux on openSUSE
by Vitezslav Cizek 04 Jan '13

04 Jan '13

Hello, You might have noticed that selinux-policy didn't build on Factory for a long time. Recently, some of the selinux tools and libraries were updated and especially the selinux-policy received a big update. If you want to give it a try, take a look at https://en.opensuse.org/SDB:SELinux You can find there the needed steps to start using SELinux on openSUSE. -- Vita Cizek

1 0

[opensuse-factory] Netinstall-CD
by Markus Koßmann 04 Jan '13

04 Jan '13

Today I've tried to install factory from openSUSE-NET-i586-Build0310-Media. The installation system missed to make device nodes for existing LVM volumes ( no /dev/system directory at all but lvscan listed them as existing) and the installation failed with error -4014 when trying to create a new lv ( looks like BNC 790724). Is there an installation media, which might not be affected by this bug or do I have to install 12.2 first and upgrade it to factory to get a new factory installation ? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] How secure boot grub2 is going to find its configuration?
by Andrey Borzenkov 04 Jan '13

04 Jan '13

I am still not sure how secure grub2 is going to find its grub.cfg. Normally its location is dynamically added to core.img. In case of secure grub2 core.img is prebuilt and signed during package creation (or may be signed later, not sure). So it is impossible to store information about grub root directory there. The only place which can be guaranteed to be auto-detected is ESP itself. But it is not where grub2 related files are installed currently ... Do I miss something here? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] broadcom-wl connects only after sleep/wakeup
by Alin M Elena 03 Jan '13

03 Jan '13

Hi, I have this wireless broadcom card.. 02:00.0 Network controller [0280]: Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller [14e4:432b] (rev 01) Subsystem: Apple Inc. Device [106b:008d] Flags: bus master, fast devsel, latency 0, IRQ 21 Memory at d3200000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [58] Vendor Specific Information: Len=78 <?> Capabilities: [e8] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [d0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Virtual Channel Capabilities: [160] Device Serial Number 35-fe-39-ff-ff-be-78-ca Capabilities: [16c] Power Budgeting <?> Kernel driver in use: wl unfortunately wl is the only driver that works for these models... tested both b43 and brcmsmac... with no luck. starting the computer (a laptop) totally fails to connect although the card is listed by /sbin/ifconfig if I suspend to ram and wake up... the card connects to the network without any issue... I did some digging and I have found that after suspend I have 3 extra kernel modules loaded (michael_mic arc4 and ecb) all crypto related. diff afterSleep.mod beforeSleep.mod 2,4d1 < michael_mic 12613 4 < arc4 12616 2 < ecb 12816 0 7c4 < af_packet 39587 6 --- > af_packet 39587 4 I have also attached the lsmod output before sleep and after wake up(beforeSleep.mod and afterSleep.mod) I have also added the journalctl output for the current boot (afterSleep.out) I have already read that michael_mic module shall be loaded by wpa_supplicant but for reasons beyond me fails to do so. /var/log/wpa_supplicant.log is empty for the failure case which makes me think wpa_supplicant is not even called... Alin -- Without Questions there are no Answers! ______________________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath ----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________

1 0

[opensuse-factory] Dropping ksymoops package from Factory and the Base:System repository
by Lars Müller 02 Jan '13

02 Jan '13

Hi, ksymoops fails to build for openSUSE Factory since quite some time. Following https://bugzilla.novell.com/show_bug.cgi?id=793544#c2 it doesn't make sense to offer ksymoops when the Linux kernel is built with KALLSYMS enabled. Therefore I'm going to drop the package and ask to get it removed from openSUSE Factory too. If one is willing to keep it please speak up in the next days. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

2 2

[opensuse-factory] openqa - zypper_up tests as failed other status listed as missing
by doiggl＠velocitynet.com.au 02 Jan '13

02 Jan '13

Hello, This page[1] lists the results for Build0xxx alot of tests showed zypper_up as failed. See attached. Cheers Glenn [1] http://openqa.opensuse.org/buildview/Build0302

1 0

[opensuse-factory] ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8
by Markus Koßmann 02 Jan '13

02 Jan '13

Everytime when grub2-branding-openSUSE is update, I'am getting: ( 6/32 ) Installation von: grub2-branding-openSUSE-12.3-1.16 ..............................[fertig] Zusätzliche rpm-Ausgabe: Generating grub.cfg ... Found theme: /boot/grub2/themes/openSUSE/theme.txt Found linux image: /boot/vmlinuz-3.7.0-1-desktop Found initrd image: /boot/initrd-3.7.0-1-desktop Found linux image: /boot/vmlinuz-3.7.0-1-default Found initrd image: /boot/initrd-3.7.0-1-default Found linux image: /boot/vmlinuz-3.6.3-1-desktop Found initrd image: /boot/initrd-3.6.3-1-desktop Found linux image: /boot/vmlinuz-3.6.3-1-default Found initrd image: /boot/initrd-3.6.3-1-default ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8 ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8 ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8 ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8 ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8 ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8 ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8 ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8 ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8 ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8 ERROR: sil: invalid metadata checksum in area 4 on /dev/dm-8 Found Windows 7 (loader) on /dev/sda1 Found openSUSE 11.4 (x86_64) on /dev/sda6 Running fsck -f on that ext4 partition doesn't find any problem however. But on a clone of that partition done with dd that error also shows up. Even if it is not mounted. Very strange. Does anyone have an idea, what might cause that problem, how to fix it and ( if needed) to file a bug against what ? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 4

[opensuse-factory] Will we be using Dracut?
by Roger Luedecke 01 Jan '13

01 Jan '13

Dracut seems like a brilliant technology. Will we be using it? -- Roger A. Luedecke openSUSE Ambassador http://www.opensuseadventures.blogspot.com -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2