Home Home > Tag > Factory
Sign up | Login

Deprecation notice: openSUSE Lizards user blog platform is deprecated, and will remain read only for the time being. Learn more...

Posts Tagged ‘Factory’

Newer Entries »

GoogleEarth 6.0 running in opensuse 11.4 factory 64Bits

December 1st, 2010 by

Sometimes we need some of those applications running under our favorite OS. If you can stick with marble.

So the new googleearth 6.0 version hit the street. And if like me you want to give it a try, there’s some tricks to make it installing under your 64bits opensuse factory.

My first attempt just result in a nice crash … 

h GoogleEarthLinux6.0.bin 
Verifying archive integrity... All good.
Uncompressing Google Earth for GNU/Linux 6.0.0.1735..............................................................
I/O error : No such file or directory
setup.data/setup.xml:1: parser error : Document is empty

^
setup.data/setup.xml:1: parser error : Start tag expected, '<' not found

^
*** glibc detected *** setup.data/bin/Linux/amd64/setup.gtk2: free(): invalid pointer: 0xbabababa ***
======= Backtrace: =========
/lib/libc.so.6(+0x6df6b)[0xf6c64f6b]
/lib/libc.so.6(cfree+0xd9)[0xf6c69ab9]
setup.data/bin/Linux/amd64/setup.gtk2[0x8074214]
/usr/lib/libxml2.so.2(+0x5131b)[0xf768531b]
======= Memory map: ========
08048000-08091000 r-xp 00000000 fd:01 1752187                            /tmp/selfgz99614152/setup.data/bin/Linux/x86/setup.gtk2
...

Google Eartch 6 In action
So I found that can be helpful, during the transition phase to have a package for openSUSE.

Here’s the recipe.

1: get the binary

wget http://dl.google.com/earth/client/current/GoogleEarthLinux.bin

2: extract it to a temp directory

sh GoogleEarthLinux.bin --target GoogleEarthFixed

3: replace the defective gtk2 setup thing

mv ./GoogleEarthFixed/setup.data/bin/Linux/x86/setup.gtk ./GoogleEarthFixed/setup.data/bin/Linux/x86/setup.gtk2

4: Launch the installer
4a : as root for system wide install

su -l
./GoogleEarthFixed/setup.sh

4b : as normal user to have it installed inside your own home

./GoogleEarthFixed/setup.sh

5: Cleaning !
If you don’t need anymore.

rm -Rf ./GoogleEarthFixed
rm ./GoogleEarthLinux.bin

I would thanks people posting this comment

The method should also work for the older 5.2 version

Tags: , , ,
Posted in Factory, KDE, Miscellaneous | 3 Comments »

Make vmware workstation 7.1.3 running with opensuse 11.4 (kernel 2.6.37)

November 15th, 2010 by

Note about the 2.6.37xx

There’s a solution to make the kernel modules building under openSUSE factory (11.4) and the kernel 2.6.37

Preparation

download the lastest vmware workstation 7.1.3 (the patch is only for this version)
download the patch vmware-7.1.3-2.6.37-rc5.patch
download the script to patch patch-modules_v62-opensuse.sh

Install

Proceed to the normal installation of workstation, if you have older version, it will be replaced
by running under root account

sh VMware-Workstation-Full-7.1.3-324285.x86_64.bundle

Patch

Now we have to apply the needed patch, just run as root 

sh patch-modules_v62-opensuse.sh

Here the output result

sh patch-modules_v62-opensuse.sh 
(Stripping trailing CRs from patch.)
patching file vmci-only/include/compat_semaphore.h
(Stripping trailing CRs from patch.)
patching file vmmon-only/linux/driver.c
(Stripping trailing CRs from patch.)
patching file vmnet-only/compat_semaphore.h
(Stripping trailing CRs from patch.)
patching file vsock-only/shared/compat_semaphore.h
Stopping VMware services:
   VMware USB Arbitrator                                               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/2.6.37-rc5-12-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-2.6.37-rc5-12-obj/x86_64/desktop'
make -C ../../../linux-2.6.37-rc5-12 O=/usr/src/linux-2.6.37-rc5-12-obj/x86_64/desktop/. modules
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/driver.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/iommu.o
/tmp/vmware-root/modules/vmmon-only/linux/iommu.c: In function ‘IOMMUUnregisterDeviceInt’:
/tmp/vmware-root/modules/vmmon-only/linux/iommu.c:217:17: warning: ignoring return value of ‘device_attach’, declared with attribute warn_unused_result
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/hostif.o
/tmp/vmware-root/modules/vmmon-only/linux/hostif.c: In function ‘HostIFReadUptimeWork’:
/tmp/vmware-root/modules/vmmon-only/linux/hostif.c:2004:37: warning: ‘newUpBase’ may be used uninitialized in this function
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/driverLog.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/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-2.6.37-rc5-12-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/2.6.37-rc5-12-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-2.6.37-rc5-12-obj/x86_64/desktop'
make -C ../../../linux-2.6.37-rc5-12 O=/usr/src/linux-2.6.37-rc5-12-obj/x86_64/desktop/. modules
  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-2.6.37-rc5-12-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/2.6.37-rc5-12-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-2.6.37-rc5-12-obj/x86_64/desktop'
make -C ../../../linux-2.6.37-rc5-12 O=/usr/src/linux-2.6.37-rc5-12-obj/x86_64/desktop/. modules
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/filesystem.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/dbllnklst.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/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-2.6.37-rc5-12-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/2.6.37-rc5-12-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-2.6.37-rc5-12-obj/x86_64/desktop'
make -C ../../../linux-2.6.37-rc5-12 O=/usr/src/linux-2.6.37-rc5-12-obj/x86_64/desktop/. modules
  CC [M]  /tmp/vmware-root/modules/vmci-only/linux/driver.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/linux/driverLog.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDs.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciContext.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/vmciGroup.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciResource.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciProcess.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-2.6.37-rc5-12-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/2.6.37-rc5-12-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-2.6.37-rc5-12-obj/x86_64/desktop'
make -C ../../../linux-2.6.37-rc5-12 O=/usr/src/linux-2.6.37-rc5-12-obj/x86_64/desktop/. modules
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/af_vsock.o
/tmp/vmware-root/modules/vsock-only/linux/af_vsock.c: In function ‘VSockVmciStreamConnect’:
/tmp/vmware-root/modules/vsock-only/linux/af_vsock.c:3172:4: warning: case value ‘255’ not in enumerated type ‘socket_state’
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/vsockAddr.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-2.6.37-rc5-12-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:
   VMware USB Arbitrator                                               done
   Virtual machine monitor                                             done
   Virtual machine communication interface                             done
   VM communication interface socket family                            done
   Blocking file system                                                done
   Virtual ethernet                                                    done
   Shared Memory Available                                             done


All done, you can now run VMWare WorkStation.
Modules sources backup can be found in the '/usr/lib/vmware/modules/source-workstation7.1.3-2010-12-13-19:07:07-backup' directory

References

vmware community post
vmware community thread

Mark D Bernstein aka InitiaZero for providing the script and patch by email and having ping me about it

Enjoy, and thanks to people having done the crappy job before.

Tags: , , , ,
Posted in Base System, Kernel, Virtualization | 4 Comments »

ATI HD57xxx fglrx drivers under 11.3 & 11.4

July 15th, 2010 by

Unofficial-but-working repository

Adding the repository

For openSUSE 11.4

zypper ar -c -f -n "ATI/AMD fglrx non-official" http://linux.ioda.net/mirror/ati/openSUSE_11.4/ "ATI/AMD FGLRX"

For openSUSE 11.3

zypper ar -c -f -n "ATI/AMD fglrx non-official" http://linux.ioda.net/mirror/ati/openSUSE_11.3/ "ATI/AMD FGLRX"

For openSUSE 11.2

zypper ar -c -f -n "ATI/AMD fglrx non-official" http://linux.ioda.net/mirror/ati/openSUSE_11.2/ "ATI/AMD FGLRX"

Searching the version you need

zypper se -s fglrx
+-----------------------+--------+---------+--------------+---------------------------
| fglrx64_7_5_0_SUSE113 | pakiet | 8.812-1 | x86_64       | ATI/AMD fglrx non-official
| fglrx64_7_5_0_SUSE113 | pakiet | 8.801-1 | x86_64       | ATI/AMD fglrx non-official
| fglrx64_7_5_0_SUSE113 | pakiet | 8.783-1 | x86_64       | ATI/AMD fglrx non-official
| fglrx64_7_5_0_SUSE113 | pakiet | 8.771-1 | x86_64       | ATI/AMD fglrx non-official
| fglrx64_7_5_0_SUSE113 | pakiet | 8.762-1 | x86_64       | ATI/AMD fglrx non-official
| fglrx_7_5_0_SUSE113   | pakiet | 8.812-1 | i586         | ATI/AMD fglrx non-official
| fglrx_7_5_0_SUSE113   | pakiet | 8.801-1 | i386         | ATI/AMD fglrx non-official
| fglrx_7_5_0_SUSE113   | pakiet | 8.783-1 | i386         | ATI/AMD fglrx non-official
| fglrx_7_5_0_SUSE113   | pakiet | 8.771-1 | i386         | ATI/AMD fglrx non-official
| fglrx_7_5_0_SUSE113   | pakiet | 8.762-1 | i386         | ATI/AMD fglrx non-official

There’s several version, as I would offer a way to use an older if new break everything 🙂

Launch the installation (always as root under a console, and better to be in init 3 mode)
For 11.3 64bits 

zypper in fglrx64_7_5_0_SUSE113

For 11.3 32bits 

zypper in fglrx7_5_0_SUSE113

etc .. I believe you pick the trick !
At the end of the installation, you can just reboot, or init 3 && init 5 .

Actual version Catalyst 11.1 / 8.812 Published January 26 by ATI/AMD

Previous version Catalyst 10.12 / 8.801 Published December 13 by ATI/AMD (Not available for factory/11.4)

If you already have a fglrx rpm installed, remove the previous version, otherwise catalyst center will give you wrong version information in info panel.

Update news January 26th

Catalyst Release 11.11

Sebastian Siebert blog about his script work nicely well
Script and
German Article

Work in progress : fglrx under factory ( 11.4 ) done for 11.1 catalyst version

At least but not at last, my unofficial-but-working repository packages has been updated yesterday. Another tricks for those who are tired of activating their desktop effects at each kde startup : (picked from the opensuse-kde) 

Check out the kwin settings in: /home/user/.kde4/share/config/kwinrc
I have solved that problem changing the DisableChecks parameter from 'false' to 'true'. Although seems that this would be a cover instead of a real solution.
-- Hernán Thiers García

Update news October 2th

How to build the 10.9 driver ? Patch needed

I’ve posted here a version how to patch the drivers to get fglrx.ko builded with latest kernel on openSUSE 11.3 http://www.susepaste.org/80021629

Don’t forget to have a look at Siebert blog his script work nicely well here

Non Official repo and build

For those of us who feel adventurous, and trust me you could install my package (no flgrx.ko inside)

Update news August 7

Seems there’s now an ati repo
you can grab it at http://www2.ati.com/suse/11.3

check the wiki page about that SDB:ATI

zypper ar -fc http://www2.ati.com/suse/11.3 ATI

Check and choose the appropriate package according to your kernel.

but you know what : they just segfault !. My rpm 10.7 (8.753) doesn’t.

Update news July 27

ATI/AMD just release their 10.7 version with native support for openSUSE 11.3

So I rewrite this article with the use of them, and remove any ref to the 10.6 version

Hardware & check

After installing my opensuse 11.3 on a computer with ATI radeon HD57xxx, there’s no desktop effects available, no 3D, no acceleration that can be provided with the free opensource radeon. Too bad, but it’s only a question of months to see support for this graphic card.
My advise would be if radeon works (even with some glitches in it) keep it. And help dev’s with bugs reporting.
To check if 3D is there (would return a YES)

glxinfo | grep -i render

Second point : ATI doesn’t provide anymore repository for their binary drivers, so we have to build them on each needed system. When the 11.3 hits the street, the procedure was complex and not so easy, now with their 10.7 ( 8.753 ) version, it’s doable.

Note All of those manipulation are done under console. So try to leave X, do a ctrl+alt+F1. Go to console, and as root run and init 3 to stop running X

Get ready to build

Downloads

Firstly : read the release note, check if your card is supported or not (HD 3870 X2 is not !)
Secondly : read the release note again, you missed something important before. 🙂

Building env

Prepare your openSUSE with a minimal building environment :
zypper in kernel-source kernel-syms module-init-tools make gcc libstdc++ libgcc glibc-32bit glibc-devel-32bit fontconfig freetype zlib*

Now we have to add the correct headers (Thx to those who reveal that )
So most of you running the -desktop flavour

zypper in kernel-desktop-devel

or

zypper in kernel-default-devel

or on 32 bits

zypper in kernel-pae-devel

Install / Build rpm

Quick Install

sh ati-driver-installer-10-7-x86.x86_64.run

Or build your own package to manage them with YaST/zypper/rpm
For 32 bits (can also be build if you have a 64 bits install)

sh ati-driver-installer-10-7-x86.x86_64.run --buildpkg SuSE/SUSE113-IA32

For 64 bits

sh ati-driver-installer-10-7-x86.x86_64.run --buildpkg SuSE/SUSE113-AMD64

(more…)

Tags: , , , ,
Posted in Desktop, Kernel, X.org | 48 Comments »

Hermes Twittering about openSUSE Factory

February 1st, 2010 by

I'm going to FOSDEM, the Free and Open Source Software Developers' European Meeting

Last week we updated Hermes on our production servers, they’re running a version now which will become a first Hermes release. I hope to get it packaged and released this week to present it on FOSDEM where I’ll give a talk about Hermes. Don’t miss it if you’re interested in this useful technology.

There went in a lot of technical improvement and bugfixes which one gets aware of if a system like Hermes runs in production for quite some time, such as missing indexes here and there which slow down the database and stuff like that. But that is another story.

What I actually wanted to talk about is the the fact that Hermes now is twittering now for you. You can follow it under the OBSHermes Twitter account. Hermes currently twitters about version updates of all packages in the openSUSE Factory project, so this is your tweet if you want to be at the bleading edge of Factory.

It is configurable for the administrator what actually is twittered. Is there other useful information around the openSUSE project which you would like to see twittered about? If so, please let me know.

Tags: , ,
Posted in Boosters, Build Service, Factory | Comments Off on Hermes Twittering about openSUSE Factory

Newer Entries »