August 2012 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] [Question] How to add local mirrors into our mirrorbrain?
by Marguerite Su 12 Aug '12

12 Aug '12

Hi, all, One of my friend, Aron Xu from Debian, is collecting all openSUSE mirrors across China mainland. According to him, there're many such mirrors from universities. And I asked him to mirror: ---------- ../ debug <== optional distribution factory-snapshot factory-tested repositories source <== optional update across all the local mirrors. Then I'll get a mirror list. Will it be enough to just transfer this list to our server manager( to whom?), or do I still need some … [View More]

4 6

[opensuse-factory] Python2 on oS:Factory
by Nelson Marques 12 Aug '12

12 Aug '12

Anyone is aware if there's an issue with the Python package on Factory? Currently I get this on a few packages for Factory: - nothing provides python-base = 2.7.3-6.1 needed by python NM -- 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] RC2 NFS failure with Kerberos
by lynn 12 Aug '12

12 Aug '12

Hi Authenticated users cannot write to a Kerberized NFS mounted share. Here is the mount command: mount -t nfs hh30:/home2 /mnt -orw,sec=krb5,vers=3 Here is the mount: hh30:/home2/ on /mnt type nfs (rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=krb5,mountaddr=192.168.1.30,mountvers=3,mountport=48880,mountproto=udp,local_lock=none,addr=192.168.1.30) Here is a sample session: su lynn2 Password: lynn2@hh30:/home/steve> cd ~ lynn2@hh30:~> id … [View More]uid=3000024(lynn2) gid=20513(Domain Users) groups=20513(Domain Users) lynn2@hh30:~> cd /mnt/home/lynn2 lynn2@hh30:/mnt/home/lynn2> id uid=3000024(lynn2) gid=20513(Domain Users) groups=20513(Domain Users) lynn2@hh30:/mnt/home/lynn2> ls -l total 0 -rw-r--r-- 1 lynn2 Domain Users 0 Aug 12 10:40 j -rw-r--r-- 1 lynn2 Domain Users 0 Aug 12 11:00 j2 lynn2@hh30:/mnt/home/lynn2> touch j3 touch: cannot touch ‘j3’: Permission denied And I cannot write to my own home NFS exported directory. Notice how 3 _three_ tickets have been issued: -rw------- 1 lynn2 Domain Users 1150 Aug 12 11:08 krb5cc_3000024_4KC2jj -rw------- 1 lynn2 Domain Users 1150 Aug 12 11:08 krb5cc_3000024_dbxlfk -rw------- 1 lynn2 Domain Users 1150 Aug 12 11:03 krb5cc_3000024_jWkcYr cat /etc/exports /home2 *(rw,sec=sys:krb5,no_subtree_check,insecure) ps aux | grep rpc root 369 0.0 0.2 2648 1056 ? Ss 10:05 0:00 /sbin/rpcbind -w -f root 1532 0.0 0.0 0 0 ? S< 10:05 0:00 [rpciod] root 3458 0.0 0.4 4428 2336 ? Ss 10:42 0:00 /usr/sbin/rpc.gssd root 3715 0.0 0.3 4304 1752 ? Ss 10:50 0:00 /usr/sbin/rpc.svcgssd statd 3721 0.0 0.2 2828 1228 ? Ss 10:50 0:00 /usr/sbin/rpc.statd --no-notify root 3726 0.0 0.2 3396 1424 ? Ss 10:50 0:00 /usr/sbin/rpc.mountd --no-nfs-version 4 lynn2 4191 0.0 0.1 4176 804 pts/3 S+ 11:16 0:00 grep --color=auto rpc Here is the Kerberos authentication log: Kerberos: Looking for PKINIT pa-data -- lynn2(a)HH3.SITE Kerberos: Looking for ENC-TS pa-data -- lynn2(a)HH3.SITE Kerberos: No preauth found, returning PREAUTH-REQUIRED -- lynn2(a)HH3.SITE Kerberos: AS-REQ lynn2(a)HH3.SITE from ipv4:192.168.1.30:43721 for krbtgt/HH3.SITE(a)HH3.SITE Kerberos: Client sent patypes: encrypted-timestamp, 149 Kerberos: Looking for PKINIT pa-data -- lynn2(a)HH3.SITE Kerberos: Looking for ENC-TS pa-data -- lynn2(a)HH3.SITE Kerberos: ENC-TS Pre-authentication succeeded -- lynn2(a)HH3.SITE using arcfour-hmac-md5 Kerberos: AS-REQ authtime: 2012-08-12T11:18:25 starttime: unset endtime: 2012-08-12T21:18:25 renew till: 2012-08-13T11:18:22 Kerberos: Client supported enctypes: aes256-cts-hmac-sha1-96, aes128-cts-hmac-sha1-96, des3-cbc-sha1, arcfour-hmac-md5, using arcfour-hmac-md5/arcfour-hmac-md5 Kerberos: Requested flags: renewable-ok On 12.1 this works perfectly. One ticket is issued and I can write to he exported NFS share without problems. Can anyone get this fixed for 12.2 or point me in the right direction? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org [View Less]

1 0

[opensuse-factory] Anyone willing to test a SuseStudio ext4 rescue boot CD?
by Greg Freemyer 12 Aug '12

12 Aug '12

All, The developer of ext4magic (a ext4 deleted file recovery tool) has created a simple text based menu'ing front-end. He's used SuseStudio to create a simple rescue CD. You can see some screenshots as well as a link to the downloadable image at: http://openfacts2.berlios.de/wikien/index.php/BerliosProject:Ext4magic-e4m-… The author made a post about it here: http://developer.berlios.de/forum/forum.php?forum_id=35219 He's looking for feedback if anyone has time to try it out. Thanks … [View More]

3 9

[opensuse-factory] google-test/gtest
by Nelson Marques 11 Aug '12

11 Aug '12

http://code.google.com/p/googletest/ Anyone who uses gtest could be kind to maintain it on factory please ? NM -- 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] GTK+ and Unity
by Nelson Marques 11 Aug '12

11 Aug '12

people, currently Unity Desktop requires nearly no vendor patches and most stuff is already upstreamed; there is one exception though regarding Unity and it comes with the (in)famous Menu Proxy patch on GTK+ which isn't upstreamed. On a fedora list I got word from GTK+ maintainers (John McCann if I'm not mistaken) that Canonical and GTK+ were working together to neutralize this situation and canonical will move to GMenus. This will allow this patch to be dropped in the near future (most … [View More]

6 10

[opensuse-factory] OS 12.1 i586 TW - kernel 3.5 - s2ram does not work
by Vladimir Malast 11 Aug '12

11 Aug '12

Opensuse 12.1 Tumbleweed - after upgrade kernel from 3.4 to 3.5 command s2ram does not not work. It looks that there is a problem with the graphic driver - the card is GeForce 8600 GT, driver nouveau Gallium (7.11). The computer goes to sleep, but after wake-up it is frozen after while or after next command s2ram restarts. Downgrade to 3.1 or 3.4 solved the problem. Thanks. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

Re: Fwd: [opensuse-factory] Re: Secure Boot for openSUSE - a proposal
by Vojtech Pavlik 10 Aug '12

10 Aug '12

On Fri, 10 Aug 2012 08:01:44 -0500, Malcolm Lewis wrote: > Sounds all good to me :) > > My only queries are; > > 1. Will alternative bootloaders eg gummiboot be implemented? > 2. Will efi booting be added to the Live CD's? These are both good goals. But I'd like to get the whole thing working first, with a more limited feature set. So not in the first iteration, later, of course. And anyone will be able to contribute to the development. > 3. Can we use openSUSE for … [View More]

1 0

Re: [opensuse-factory] Secure Boot for openSUSE - a proposal
by Greg Freemyer 10 Aug '12

10 Aug '12

plain text this time On Fri, Aug 10, 2012 at 9:08 AM, Greg Freemyer <greg.freemyer(a)gmail.com> wrote: > On Fri, Aug 10, 2012 at 6:40 AM, Andreas Jaeger <aj(a)suse.com> wrote: >> >> As a followup to discussions on opensuse-project and here on >> opensuse-factory about secure boot, here's a proposal: >> >> Vojtech Pavlik and Olaf Kirch have written three blog posts explaing >> SUSE's approach to secure boot: >> >> http://www.suse.… [View More]com/blogs/uefi-secure-boot-overview/ >> http://www.suse.com/blogs/uefi-secure-boot-plan/ >> http://www.suse.com/blogs/uefi-secure-boot-details/ >> >> They basically propose to enhance Fedora's solution with a way >> that Matthew Garrett - the Red Hat developer working on this - summarized >> at http://mjg59.dreamwidth.org/15818.html with >> >> "There's a post here describing SUSE's approach to implementing Secure >> Boot support. In summary, it's pretty similar to the approach we're >> taking in Fedora - a first stage shim loader is signed with a key in >> db, it loads a second stage bootloader (grub 2) that's signed with a >> key that's in shim, the second stage bootloader loads a signed >> kernel. The main difference between the approaches is the use of a >> separate key database in shim, whereas we are currently planning on >> using a built-in key and the contents of the firmware key database. >> ... >> "It's a wonderfully elegant solution. We've been planning on supporting >> user keys by trusting the contents of db, and the Windows 8 requirements >> specify that it must be possible for a physically present user to add keys >> to it. The problem there has been that different vendors offer different UI >> for this, in some cases even requiring that the keys be in different >> formats. Using an entirely separate database and offering support for >> enrolment in the early boot phase means that the UI and formats can be kept >> consistent, which makes it much easier for users to manage their own keys. >> >> I suspect that we'll adopt this approach in Fedora as well - it >> doesn't allow anything that our solution wouldn't have, but it does >> make some of them easier. Full marks to SUSE on this." >> >> >> What shall we do for openSUSE? Vojtech and Olaf make the proposal to >> use the proposed SUSE solution for openSUSE as well. >> >> Do you see any problems or enhancements for the proposal? >> >> I would love to tell them the openSUSE community looks forward to the >> SUSE implementation for the next release (12.3). May I? >> >> Andreas >> -- >> Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi >> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany >> GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) >> GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 >> -- >> To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org >> To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org >> I think there are 2 questions. 1) Is the SUSE approach with a standalone database of MOKs necessary for openSUSE. I argue it is. 2) Is the functionality defined for using that database of MOKs sufficient for openSUSE needs. I argue it is not. The prime examples relate to OBS and SuseStudio. If each of those is provisioned with a unique MOK key and the validation key is made well known, then the SUSE approach will I'm sure include a relatively simple way for a user to install the validation key into the MOK database. But what if OBS and/or SuseStudio is used to create a kernel that gets designated as malware. I would like to see the openSUSE solution provide a way to black ball that kernel. === Thus I think openSUSE should use the SUSE UEFI approach as a foundation, but should add a black ball mechanism to it somehow. I admit that I don't have a methodology in mind to accomplish that. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org [View Less]

3 2

[opensuse-factory] nouveau, plymouth and grub2?
by Alin M Elena 08 Aug '12

08 Aug '12

2 1

[opensuse-factory] new package - ssdeep
by Greg Freemyer 07 Aug '12

07 Aug '12

All, I have just submitted ssdeep to factory. It has a sub-package of libfuzzy. http://ssdeep.sourceforge.net/ It is a tool for doing piecewise hash generation. It can be used for malware and (I believe) spam detection and is another digital forensic tool in my ongoing (slow) effort to push digital forensic tools into factory. For a overview of forensic tools in openSUSE see: http://en.opensuse.org/Portal:Digital_forensics_and_incident_response Greg -- To unsubscribe, e-mail: opensuse-… [View More]

1 0

[opensuse-factory] Secret key for Secure Boot with Windows 8 and 12.2
by Roman Bysh 07 Aug '12

07 Aug '12

Hello all, I've been reading that Ubuntu is providing a secret key for the "Secure Boot" so that Ubuntu may be installed alongside Windows 8. Since 12.2 is coming out in September and Windows 8 is being released in October. What are the plans? Cheers! Roman --------------------------------------------------------------- openSUSE -- Get it! Discover it! Share it! --------------------------------------------------------------- http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: … [View More]

3 3

[opensuse-factory] RFC: apache2 upcoming changes
by Cristian Rodríguez 07 Aug '12

07 Aug '12

Hi: This week, I have been working giving apache2 packages some love, in particular upgrading to version 2.4. The upgrade part is done but I am now working on implementing major changes in the way it is distributed and packaged. If there are no objections it will go as follow. 1. Support for Building apache in: * Non SUSE Distros * Versions older than SLE 11 SP2 Will go away. 2, Subpackages : apache2-prefork apache2-itk apache2-worker Will go away. 2.4 supports providing MPMs as DSOs,… [View More]

2 4

[opensuse-factory] PackageKit blocking Yast
by Thomas Taylor 07 Aug '12

07 Aug '12

In OS 12.2-RC2 (build 0091-DVD) in 'Yast > Software Management > Search', PackageKit is blocking the repositories from loading. I've worked around this by killing the PackageKit process, then the repos load properly. Has anyone else seen this happen? Is it a bug or expected behavior? Tom -- “What we do for ourselves dies with us. What we do for others and the world remains and is immortal.” Albert Pine -- Tom Taylor - retired penguin AMD Phenom II x4 955 -- 4GB RAM -- 2x1.5TB sata2 … [View More]

8 10

[opensuse-factory] Very slow response in kshisen
by Thomas Taylor 07 Aug '12

07 Aug '12

On OS 12.2-RC2 (build0091) x86-64, the game kshisen (shisen-sho) takes a long time responding to mouse clicks. This has only occurred with the RC2 version. The first click on a tile may or may not be indicated (color change) immediately. The second click (on matching tile) seems to think about things for 5-10 seconds. I tried running it as root with nice of -19 but that didn't change the behavior. /var/log/messages doesn't show me anything obvious (still learning about what to look for). … [View More]

3 5

[opensuse-factory] 12.2 RC2 btrfs subvolumes
by Erwin Van de Velde 06 Aug '12

06 Aug '12

Dear all, I tried installing OpenSUSE 12.2 RC2, and all goes well, but I have a remark: Would it not be better to have a separate subvolume for /home if you do not choose a /home separate partition? Zypper + snapper can revert an update, but I do not think it is good to revert both the user documents and the system files in such a case. Also, if it is a separate subvolume, it is perhaps possible to remove the system subvolumes instead of reformatting the entire filesystem and letting … [View More]

1 0

[opensuse-factory] Bug in update with Grub2
by Larry Finger 06 Aug '12

06 Aug '12

A problem with the reboot following an update from 12.2 RC1 to 12.2 RC2 was noted in the Forums. This contribution by user rengejao identifies the problem. He/She writes ======================================================================= Hello, I don't speak very well english. I had the same problem. It's because of the update of the kernel. And the grub.cfg file cannot be actualized. I had this: Code: -------------------- Kernel image: /boot/vmlinuz-3.4.4-1.1-default Initrd … [View More]image: /boot/initrd-3.4.4-1.1-default Root device: /dev/disk/by-id/ata-VBOX_HARDDISK_VBdcac2bdf-ae573355-part3 (/dev/sda3) (mounted on / as ext4) Resume device: /dev/disk/by-id/ata-VBOX_HARDDISK_VBdcac2bdf-ae573355-part1 (/dev/sda1) Kernel Modules: hwmon thermal_sys thermal processor fan libata libahci ahci ata_piix ata_generic scsi_dh scsi_dh_hp_sw scsi_dh_emc scsi_dh_alua scsi_dh_rdac pata_acpi pdc_adma pata_ninja32 sata_mv pata_it8213 sata_uli pata_triflex pata_hpt3x3 pata_optidma acard-ahci pata_hpt366 sata_inic162x pata_sch pata_sis pata_cs5520 pata_mpiix pata_isapnp pata_legacy pata_rz1000 sata_sx4 pata_rdc pata_cs5530 sata_promise pata_artop sata_sis pata_pdc202xx_old pata_serverworks pata_efar sata_sil pata_cmd640 sata_qstor pata_hpt37x pata_oldpiix pata_sil680 pata_marvell pata_via pata_piccolo pata_pdc2027x pata_ns87410 sata_svw pata_jmicron pata_ali pata_sc1200 pata_amd sata_sil24 pata_cs5536 pcmcia_core pcmcia pata_pcmcia pata_atp867x sata_nv pata_sl82c105 pata_cs5535 pata_opti pata_arasan_cf ahci_platform sata_vsc pata_it821x pata_atiixp pata_cypress pata_netcell pata_radisys pata_ns87415 pata_cmd64x sata_via pata_hpt3x2n usb-common usbcore ohci-hcd uhci-hcd ehci-hcd xhci-hcd hid usbhid hid-logitech-dj Features: acpi plymouth block usb resume.userspace resume.kernel PERL-BOOTLOADER: 2012-08-02 20:05:58 ERROR: COMMAND '/USR/SBIN/GRUB2-MKCONFIG -O /BOOT/GRUB2/GRUB.CFG >/VAR/LOG/YAST2/Y2LOG_BOOTLOADER 2>&1' FAILED WITH CODE 256 AND OUTPUT: GENERATING GRUB.CFG ... /ETC/GRUB.D/05_MENU_COLOR: LINE 8: /USR/LIB/GRUB/GRUB-MKCONFIG_LIB: NO SUCH FILE OR DIRECTORY There was an error generating the initrd (1) warning: %posttrans(mkinitrd-2.7.0-62.5.1.i586) scriptlet failed, exit status 1 -------------------- The file grub-mkconfig_lib is in /usr/share/grub2, not in /usr/lib/grub. So i made a symbolic link and it works! Code: -------------------- ln -s /usr/share/grub2/grub-mkconfig_lib /usr/lib/grub/grub-mkconfig_lib -------------------- -- rengejao ------------------------------------------------------------------------ rengejao's Profile: http://forums.opensuse.org/member.php?userid=48460 View this thread: http://forums.opensuse.org/showthread.php?t=477166 ======================================================================= I don't use Grub2 (yet), thus I don't know if this link is the correct fix, or if the script should be changed (more likely I think); however, the contribution does identify the problem. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org [View Less]

3 2

[opensuse-factory] [RC2] How can I update yast2-trans sources? how to make that tarball?
by Marguerite Su 06 Aug '12

06 Aug '12

Hi, all, In RC2 release notes, It said all translation work is integrated. But actually it's not. YaST-trans freeze about 2 month ago. (I checked it today) Actually no one shares that info but there're some misleading info exists. In translation ml, coolo said all trans should be finished before August. So I finished my version at July 20th. But it didn't got merged. ( maybe my fault, I thought it would be merged automatically) So how can I update yast2-trans myself and push it into RC2 … [View More]

3 7

Re: [opensuse-factory] 12.2-RC2 - My test results and comments
by Hernan Thiers 05 Aug '12

05 Aug '12

Good to know this! I'm going for a fresh RC2 install too. What are the video cards you are working with? I will try a Radeon 6770M with open and private drivers. > 2012/8/4 James PEARSON <pearson44j(a)wanadoo.fr> >> >> Hello >> >> I have been playing since yesterday doing multiple fresh installs using the RC2 x64 iso (on AMD based systems) and the RC 386 iso (on Thinkpads and HP laptops): >> openSUSE-DVD-Build0091-x86_64.iso >> openSUSE-DVD-… [View More]

4 3

[opensuse-factory] question about javascript
by C. Brouerius van Nidek 05 Aug '12

05 Aug '12

Just curious but during a closer look at what was installed for java script I found that on my machine I have both java-1_6_0-openjdk and java-1_7_0-openjdk. Also pairs of libjavascriptcoregtk-1_0-0 and libjavascriptcoregtk-3_0-0 and the pairs libwebkitgtk-1_0-0 and libwebkitgtk-3_0-0. Are those pairings required or could I just remove the programs with the lower number? -- Linux User 183145 using KDE4 on a Pentium IV , powered by openSUSE 12.2 Milestone 2 (i586) Kernel: 3.4.6-1.1-… [View More]

3 2

Fw: [opensuse-factory] Download your free Blog Automator Software (first 100 people only)
by Thomas Taylor 05 Aug '12

05 Aug '12

Moderator, please remove this poster from this list. Not what we want here. Tom Begin forwarded message: Date: Thu, 2 Aug 2012 13:50:27 -0400 From: "Cody Moya" <codymoya369(a)subscriptionserver.com> To: opensuse-factory(a)opensuse.org Subject: [opensuse-factory] Download your free Blog Automator Software (first 100 people only) Hey, Today you get for free Blog Automator Software with Master Resell Rights Watch New Content Get Added To Your Blog Every Single Day, In Any Niche You … [View More]Choose For The Next 8 Years, With Only 3 Mouse Clicks! New "Set It And Forget It" Technology Automatically Drip Feeds Fresh New Content Into Your Blog For As Long As You Choose! How Would You Like To Build The Biggest Blog In Your Niche With 3 Simple Clicks Of Your Mouse, Just One Time? To download it for free scroll to the bottom of long sales letter, click download link and then enter below coupon code at the bottom of the order page. Coupon Code: DFA0CE6B77 http://subscriptionserver.com/cgi-bin/arp3/arp3-t.pl?l=247&c=8558582 Enjoy Cody Moya P.S. Coupon code expires after 100 people use it so make sure to download it now. http://subscriptionserver.com/cgi-bin/arp3/arp3-t.pl?l=247&c=8558582 . . . ================================================ 80,000 list for $2 (a few spots left) http://subscriptionserver.com/cgi-bin/arp3/arp3-t.pl?l=123&c=8558582 ================================================ . . . =============================== Email broadcast powered by http://subscriptionserver.com/cgi-bin/arp3/arp3-t.pl?l=309&c=8558582 =============================== . . . . . . . . ============================================ Send to opensuse-factory(a)opensuse.org . . author of this email is compensated from sales of the product described . Xodo Inc, 784 Morris TPKE, BOX 324, Short Hills, NJ 07078, USA If you wish to cancel your subscription, simply click once on the link below. http://subscriptionserver.com/cgi-bin/arp3/arp3-un.pl?c=8558582&p=8860 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org -- “What we do for ourselves dies with us. What we do for others and the world remains and is immortal.” Albert Pine -- Tom Taylor - retired penguin AMD Phenom II x4 955 -- 4GB RAM -- 2x1.5TB sata2 openSUSE 12.1x86_64 openSUSE 12.2x86_64 KDE 4.7.2, FF 7.0 KDE 4.8.4, FF 13.0 claws-mail 3.8.0 registered linux user 263467 linxt-At-comcast-DoT-net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org [View Less]

4 5

Re: [opensuse-factory] 12.2-RC2 - My test results and comments
by pearson44j 04 Aug '12

04 Aug '12

On Sat, 4 Aug 2012 17:37:51 -0400 Hernan Thiers <hernanthiers(a)gmail.com> wrote: > Good to know this! I'm going for a fresh RC2 install too. > > What are the video cards you are working with? I will try a Radeon 6770M > with open and private drivers. My main system has a Radeon 5770 card - the laptops all have Intel based video cards. > 2012/8/4 James PEARSON <pearson44j(a)wanadoo.fr> > > > Hello > > > > I have been playing since yesterday … [View More]doing multiple fresh installs using > > the RC2 x64 iso (on AMD based systems) and the RC 386 iso (on Thinkpads and > > HP laptops): > > openSUSE-DVD-Build0091-x86_64.**iso > > openSUSE-DVD-Build0091-i586.**iso > > > > The fresh installs go quite fast because I use the SUSE Studio ImageWriter > > (USB key Writer) to write the iso to an usb key and install using the usb > > key > > > > Once the fresh install is finished I run a custom script which adds the > > Packman repo and installs my personal rpms (flash-player, vlc, codecs, etc). > > > > zypper addrepo --refresh --name "openSUSE-12.1-Packman" > > http://packman.mirrors.skynet.**be/pub/packman/suse/12.2/<http://packman.mirrors.skynet.be/pub/packman/suse/12.2/>repo-Packman > > zypper mr -p 1 "openSUSE-12.1-Packman" > > > > To my surprise all my standard 'family & video related' rpms are already > > available and working - thanks to packman. > > > > Note: I did ***not*** do and do not plan on doing a “zypper up” on any of > > the systems (i.e. using the repo-non-oss and repo-oss) for a while because > > I am worried about a grub2 issue (which results in a no boot) problem if I > > do. > > > > Resume of my test results: > > - amorak works (Bug 712749 which has been a pain on v12.1 has been solved) > > - Facework (this includes YouTube attachments) works on Firefox and > > Chromium - my girlfriend will be pleased :) > > - vlc works (thank you packman!) > > - wifi works (tested using 3 generations of intel cards) > > - sound works (on all laptops as well as on my main system which has an > > Xonar Essence STX) > > - OfficeLibre works > > > > I was so encouraged by the test results that I moved my main home system > > (which is an AMD x64 based) to RC2 > > VMware workstation (v8.0.4 build-744019) works as per usual once patched. > > > > Congratulations are in order for the results to date! > > > > Regards > > James > > > > -- > > To unsubscribe, e-mail: > > opensuse-factory+unsubscribe(a)**opensuse.org<opensuse-factory%2Bunsubscribe(a)opensuse.org> > > To contact the owner, e-mail: > > opensuse-factory+owner(a)**opensuse.org<opensuse-factory%2Bowner(a)opensuse.org> > > > > > > -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org [View Less]

1 0

[opensuse-factory] VMware workstation (v8.0.4 build-744019) works on RC2 once patched.
by James PEARSON 04 Aug '12

04 Aug '12

Hello Workstation 8.0.4 build-744019 was working fine on v12.1 but when I installed it on a fresh install of v12.2 RC2 I had vmnet compile errors. I googled for awhile and found a solution - see below ###################################################### # Source: http://pavlinux.ru/vmware/8.0.4/ ###################################################### Patches for VMware® Tested with linux kernel 3.2.20 and 3.5.0-rc3+ (updated 17.06.2012) Complete module sources: source.tar.lzma … [View More]Install: # cd /usr/lib/vmware/modules; # wget http://pavlinux.ru/vmware/8.0.4/source.tar.lzma; # md5sum source.tar.lzma; e37e41a818a47ec868bdb493197aaf63 source.tar.lzma # tar -xf source.tar.lzma; # vmware-modconfig --console --install-all; ###################################################### # My log follows ###################################################### # cd /usr/lib/vmware/modules Tiger:/home/jpearson/vm.patch # cd /usr/lib/vmware/modules Tiger:/usr/lib/vmware/modules # wget http://pavlinux.ru/vmware/8.0.4/source.tar.lzma --2012-08-04 19:58:05-- http://pavlinux.ru/vmware/8.0.4/source.tar.lzma Resolving pavlinux.ru (pavlinux.ru)... 62.118.254.152 Connecting to pavlinux.ru (pavlinux.ru)|62.118.254.152|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 417231 (407K) [application/x-tar] Saving to: `source.tar.lzma' 100%[=========================================================================== ================================================================================ ==========================================================================>] 417,231 554K/s in 0.7s 2012-08-04 19:58:06 (554 KB/s) - `source.tar.lzma' saved [417231/417231] Tiger:/usr/lib/vmware/modules # md5sum source.tar.lzma e37e41a818a47ec868bdb493197aaf63 source.tar.lzma Tiger:/usr/lib/vmware/modules # tar -xf source.tar.lzma Tiger:/usr/lib/vmware/modules # vmware-modconfig --console --install-all Stopping VMware services: VMware Authentication Daemon done VM communication interface socket family done Virtual machine communication interface done Virtual machine monitor done Blocking file system done Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-root/modules/vmmon-only' make -C /lib/modules/3.4.6-1.1-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-3.4.6-1.1-obj/x86_64/desktop' CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driver.o CC [M] /tmp/vmware-root/modules/vmmon-only/linux/hostif.o CC [M] /tmp/vmware-root/modules/vmmon-only/common/memtrack.o CC [M] /tmp/vmware-root/modules/vmmon-only/common/vmx86.o CC [M] /tmp/vmware-root/modules/vmmon-only/common/apic.o CC [M] /tmp/vmware-root/modules/vmmon-only/common/cpuid.o CC [M] /tmp/vmware-root/modules/vmmon-only/common/task.o CC [M] /tmp/vmware-root/modules/vmmon-only/common/hashFunc.o CC [M] /tmp/vmware-root/modules/vmmon-only/common/comport.o CC [M] /tmp/vmware-root/modules/vmmon-only/common/phystrack.o CC [M] /tmp/vmware-root/modules/vmmon-only/vmcore/moduleloop.o LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware-root/modules/vmmon-only/vmmon.mod.o LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.ko make[1]: Leaving directory `/usr/src/linux-3.4.6-1.1-obj/x86_64/desktop' make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1]: Entering directory `/tmp/vmware-root/modules/vmmon-only' make[1]: `postbuild' is up to date. make[1]: Leaving directory `/tmp/vmware-root/modules/vmmon-only' cp -f vmmon.ko ./../vmmon.o make: Leaving directory `/tmp/vmware-root/modules/vmmon-only' Built vmmon module Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-root/modules/vmnet-only' make -C /lib/modules/3.4.6-1.1-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-3.4.6-1.1-obj/x86_64/desktop' CC [M] /tmp/vmware-root/modules/vmnet-only/driver.o CC [M] /tmp/vmware-root/modules/vmnet-only/hub.o CC [M] /tmp/vmware-root/modules/vmnet-only/userif.o CC [M] /tmp/vmware-root/modules/vmnet-only/netif.o CC [M] /tmp/vmware-root/modules/vmnet-only/bridge.o CC [M] /tmp/vmware-root/modules/vmnet-only/filter.o CC [M] /tmp/vmware-root/modules/vmnet-only/procfs.o CC [M] /tmp/vmware-root/modules/vmnet-only/smac_compat.o CC [M] /tmp/vmware-root/modules/vmnet-only/smac.o CC [M] /tmp/vmware-root/modules/vmnet-only/vnetEvent.o CC [M] /tmp/vmware-root/modules/vmnet-only/vnetUserListener.o LD [M] /tmp/vmware-root/modules/vmnet-only/vmnet.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware-root/modules/vmnet-only/vmnet.mod.o LD [M] /tmp/vmware-root/modules/vmnet-only/vmnet.ko make[1]: Leaving directory `/usr/src/linux-3.4.6-1.1-obj/x86_64/desktop' make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1]: Entering directory `/tmp/vmware-root/modules/vmnet-only' make[1]: `postbuild' is up to date. make[1]: Leaving directory `/tmp/vmware-root/modules/vmnet-only' cp -f vmnet.ko ./../vmnet.o make: Leaving directory `/tmp/vmware-root/modules/vmnet-only' Built vmnet module Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-root/modules/vmblock-only' make -C /lib/modules/3.4.6-1.1-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-3.4.6-1.1-obj/x86_64/desktop' CC [M] /tmp/vmware-root/modules/vmblock-only/linux/dbllnklst.o CC [M] /tmp/vmware-root/modules/vmblock-only/linux/dentry.o CC [M] /tmp/vmware-root/modules/vmblock-only/linux/stubs.o CC [M] /tmp/vmware-root/modules/vmblock-only/linux/file.o CC [M] /tmp/vmware-root/modules/vmblock-only/linux/block.o CC [M] /tmp/vmware-root/modules/vmblock-only/linux/filesystem.o CC [M] /tmp/vmware-root/modules/vmblock-only/linux/module.o CC [M] /tmp/vmware-root/modules/vmblock-only/linux/super.o CC [M] /tmp/vmware-root/modules/vmblock-only/linux/inode.o CC [M] /tmp/vmware-root/modules/vmblock-only/linux/control.o LD [M] /tmp/vmware-root/modules/vmblock-only/vmblock.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware-root/modules/vmblock-only/vmblock.mod.o LD [M] /tmp/vmware-root/modules/vmblock-only/vmblock.ko make[1]: Leaving directory `/usr/src/linux-3.4.6-1.1-obj/x86_64/desktop' make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1]: Entering directory `/tmp/vmware-root/modules/vmblock-only' make[1]: `postbuild' is up to date. make[1]: Leaving directory `/tmp/vmware-root/modules/vmblock-only' cp -f vmblock.ko ./../vmblock.o make: Leaving directory `/tmp/vmware-root/modules/vmblock-only' Built vmblock module Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-root/modules/vmci-only' make -C /lib/modules/3.4.6-1.1-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-3.4.6-1.1-obj/x86_64/desktop' CC [M] /tmp/vmware-root/modules/vmci-only/linux/driver.o CC [M] /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciResource.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciContext.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDoorbell.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQPair.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciRoute.o CC [M] /tmp/vmware-root/modules/vmci-only/driverLog.o LD [M] /tmp/vmware-root/modules/vmci-only/vmci.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware-root/modules/vmci-only/vmci.mod.o LD [M] /tmp/vmware-root/modules/vmci-only/vmci.ko make[1]: Leaving directory `/usr/src/linux-3.4.6-1.1-obj/x86_64/desktop' make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only' make[1]: `postbuild' is up to date. make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only' cp -f vmci.ko ./../vmci.o make: Leaving directory `/tmp/vmware-root/modules/vmci-only' Built vmci module Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-root/modules/vsock-only' make -C /lib/modules/3.4.6-1.1-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-3.4.6-1.1-obj/x86_64/desktop' CC [M] /tmp/vmware-root/modules/vsock-only/linux/af_vsock.o CC [M] /tmp/vmware-root/modules/vsock-only/linux/vsockAddr.o CC [M] /tmp/vmware-root/modules/vsock-only/linux/notifyQState.o CC [M] /tmp/vmware-root/modules/vsock-only/linux/util.o CC [M] /tmp/vmware-root/modules/vsock-only/linux/stats.o CC [M] /tmp/vmware-root/modules/vsock-only/linux/notify.o CC [M] /tmp/vmware-root/modules/vsock-only/driverLog.o LD [M] /tmp/vmware-root/modules/vsock-only/vsock.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware-root/modules/vsock-only/vsock.mod.o LD [M] /tmp/vmware-root/modules/vsock-only/vsock.ko make[1]: Leaving directory `/usr/src/linux-3.4.6-1.1-obj/x86_64/desktop' make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1]: Entering directory `/tmp/vmware-root/modules/vsock-only' make[1]: `postbuild' is up to date. make[1]: Leaving directory `/tmp/vmware-root/modules/vsock-only' cp -f vsock.ko ./../vsock.o make: Leaving directory `/tmp/vmware-root/modules/vsock-only' Built vsock module Starting VMware services: Virtual machine monitor done Virtual machine communication interface done VM communication interface socket family done Blocking file system done Virtual ethernet done VMware Authentication Daemon done Shared Memory Available done Hope this helps Regards James -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org [View Less]

1 0

[opensuse-factory] 12.2-RC2 - My test results and comments
by James PEARSON 04 Aug '12

04 Aug '12

Hello I have been playing since yesterday doing multiple fresh installs using the RC2 x64 iso (on AMD based systems) and the RC 386 iso (on Thinkpads and HP laptops): openSUSE-DVD-Build0091-x86_64.iso openSUSE-DVD-Build0091-i586.iso The fresh installs go quite fast because I use the SUSE Studio ImageWriter (USB key Writer) to write the iso to an usb key and install using the usb key Once the fresh install is finished I run a custom script which adds the Packman repo and installs my … [View More]

1 0

[opensuse-factory] Plymouth shows two different effects during initial set up
by Roman Bysh 04 Aug '12

04 Aug '12

Hello Listmates. I have noticed during my many installations of RC2. Which Plymouth graphics are supposed to be used during the initial setup? The first installation showed text udev etc...followed by a Plymouth bootsplash minus the progress bar which freezes sometimes as to no longer see the welcome screen. Another installation showed Fedora's white and blue progress bar at the bottom of the screen that should lead up to the welcome screen. The problem with Plymouth is that it needs to … [View More]

1 0