August 2012 - openSUSE Factory - openSUSE Mailing Lists

[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 the user files in place. "Why not create a separate partition if you want this?" I hear you ask. I only have a 160GB SSD disk in my laptop and since the snapper snapshots will take more place, I would need to make my root partition bigger., but I do not like shrinking my home partition. Furthermore, since you cannot estimate the filesystem usage perfectly, you always loose space and perhaps this can be a way to avoid such waste. Best regards, Erwin -- 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] 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 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

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 using maintenance request or something? Anyone knows the steps? There is no reason that we had a full translated version and asked users to use a half-done one. Greetings, Marguerite -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

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-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/ 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 >> To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org >> -- Hernán Thiers Garcia Ingeniero Informático Santiago, Chile. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

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-default KDE Development Platform: 4.8.4 (4.8.4) "release 2") 22:48pm up 1 day 0:22, 4 users, load average: 0.61, 0.31, 0.35 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

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 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

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 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

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 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

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 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/ 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 To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

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 start and follow through to something else. If we see the graphics it would be nice see some feedback i.e. Please wait while openSUSE detects your hardware... At the moment a splash screen sits for a long time and the user does not know where they are during start up process. This is an observation. Cheers! Roman --------------------------------------------------------------- openSUSE -- Get it! Discover it! Share it! --------------------------------------------------------------- http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0