Welcome to Our SuSE 13.2 Info Website!

 May 9th, 2016 /7:48am   Another new machine, an  HP 700-530qe . Whether I deserve it or not... it's one of the toys you can get when you retire. I now have two HP i7's sitting on my desktop. Both are running openSuSE 13.2. The 'oldest' of the two new ones is dual booting with Windows 8 and the 'newest' one is dual booting with Windows 10. The first one I call HP i7-1 and it was purchased in October of 2014. The second one I call HP i7-2 and it was purchased in Febuary of 2016. The second one is more powerful than the first and was purchased to replace my old "MainMoma" the   HP m7480n   which I have been using for the past 9 years.

 November 6th, 2014 / 3:14am  This was a modification of our 13.1 Page and now it is becoming another modification. From our attempt on our 'old' machine to an actual install on our 'newest' machine. Therefore. some of the dates and times may be screwy ... and well things in general may be screwy until we get it all straight.

Well, they finally released something to the public. I have been tied up with phone activities, Smartphone. I possess an HTC ReZound and I have been playing with its OS. In fact, as of June 6th, 2014 I became the OP of the XDA Thread. Now then, I actually copied over the openSuSE 13.1 Web Page to my 'blank' openSuSE 13.2 page. I will leave some things from 13.1, like the following, and see IF they have something that will work on my machine -or- not. Since most of this 'was' complaints, I'll see IF they got them fixed.

 November 25th, 2014/3:04am  Whooooaaa... a tale of woe. As stated above we got a 'new' PC. This has been one heck of a challenge. Would just love it IF once, just once, when I got a new piece of equipment that the software would install smoothly and there would NOT be all these headaches. -But- then that is why they pay me the big bucks... right???

Anywho, this is for anyone else out there. They do NOT have any separate drivers for the "graphics portion" of i7-4770 Quad processor. I bounced around the latest 3 versions of openSuSE. The graphics driver for 'our' chip is inside the Kernel. I'm having a difficult time getting Eclipse to work on this 'new' PC. Getting those 'not resolved' errors again -and- this time ignoring them doesn't work. It is really strange. Either there is 'something' that I have missed or forgotten or ... whatever ... it don't work. I can get a 'successful' compile -and- it works on the phone -but- not in Eclipse!!

Now then, here is the craziest part... and you will read about this in other parts of my pages, and even some here. I simply could NOT install this 13.2 version on my 'newest' machine. I had to install the 13.1 version -and- then do an 'UpGrade/UpDate' ... which in our humble opinion sucks and did NOT work properly. After the 'UpDate' the Grub2 screen still announced version 13.1!! We experienced some other 'strangeness' and finally gave up. Now here is the really, really crazy part. After bouncing back and forth with the 13th versions, we decided to install version 12.3. With all this screwing around we finally became "knowledgable" enough that we could get the 'new' system to read the 12.3 install disc. The difficulties with Windows 8 and this 'new' UEFI Secure Boot have been discussed elsewhere. Suffice it to say, it is one big PITA!! Anywho, it did NOT work any better -and- here is where we learned that our 'graphics driver' is in the "Newer" Kernels!! Because the best we could get was 1024x768, -and- the other stuff wasn't working right either, we decided to go back to the 13.x versions. -BUT- just for a Wild Ass Guess, we decided to try the openSuSE 13.2 Install ... one more time. We did NOT re-do any of the partitions. We installed 'over' the system that was there... which is what we had tried before. The very first time there was nothing, but the times after we had 13.1 or 13.2 itself installed. The 'installation' portion would NOT recognize the layout!! We always had to install 13.1 first and then do 13.2 as an UpGrade.

Well, guess what..?? Installing version 13.2 over 12.3 worked!!! This time it recognized the proper partition setup on the disc!! Course during the beginning of this last install I asked the 'Lord' for help. 'He' did!! We now have a 'clean', 'fresh' install of openSuSE 13.2 on our new machine.
      Now to see IF we can get a proper Android Environment setup.

November 19th, 2013 - This was the "Release Date" for this latest version of openSuSE. It was a dismal failure. Haven't had one this bad... ever!! Don't know where the Dev's were -but- they sure weren't around on this one. Can not even get it installed and operational enough to really evaluate it!
Later November 24th, 2013: Oh darn!! We just can't give in to failure! Going to research and try again.
Nope!! Nothing that we tried would 'fix' -or- 'correct' any 'unknown' problem that we have in order to allow this 13.1 version to install -and- work properly on our syste. We have reverted back to openSuSE 12.3 and will stay there.
 Nov 4th, 2014/10:28am   Well, they released the 13.2 "Stable" version to the General Public today. We were finally successful in getting 13.1 installed ... on our 'New' Machine. So, Now that we know what to do, we are going to install this 13.2 on this New Machine. NOT gona do an UpDate. Gona byte the Bullet and do a "clean install"... NOPE. Gona try the UpDate first. I can change my mind. Spent all that time getting Java 7 setup. Gona see IF an UpDate will work.
NO!! I just did an "Update IF any newer" in my current 13.1 Linux -and- it wiped my Windows 8 boot!!! I'm gona have to do a "FULL Recovery" on this SOB again!!!! I get a 3 line message ... which I forget what it said -but- it didn't mean anything to me and was just some nonsense anyway. Starting over from "scratch" ... AGAIN!!

November 25th, 2014/3:57am -- As mentioned above we are trying one more time to get 13.2 installed on our newest PC. We did!! -AND- it is a 'Clean Install'!!! Not sure IF we are going to installed VMware on this machine or not. TBD later.

 Nov 4th, 2014/4:42pm  'New System' Re-Partitioning Info:

  • Size BEFORE shrink: 942,546MB = 920.46GB
  • Size can shrink: 468,726MB = 457.74GB -- C: Drive
  • Size AFTER shrink: 473,820MB = 462.71GB -- Linux area
Those values were dictated by the "Windows 8.1 Update". There are other partitions on this drive. I did not include them. This is the only one that had to be altered. Now then, I fought for a number of days with this New System. Trying to use "other" partitioners. Had to use the Windows one ... OR it would fail. Perhaps because I was trying to make the 'C:' smaller than what is was allowing.

  • AND I am putting this right here in the middle of everything so's it is up front, so to speak, and gets noticed. I couldn't leave well enough alone and TRIED to UpGrade 13.1 to 13.2. BIG MISTAKE!! After it went through the UpGrade and ReBooted ... I lost my Windows selection in the Grub screen!!! Tried F9 at ReBoot and all I got was a message that NO boot disc was detected!!!! UNLESS I can figure something out -or- I can find somethign on the Net ... it is gona be another FULL Recovery... the 4th in 10 days!!
    Well, on our 5th. Good thing I didn't have anything on this machine... yet! -And- that I am ReTired. It seems that Re-Partitioning the HDD BEFORE installing Linux and getting smaller than 461GB is a no,no. We bombed again. Left Linux and could NOT get back in.
    And another insertion... IF you "Loose Windows Boot" on the Grub Screen, go into Yast2 and look at the "Boot Parameters". There should be a 'checkbox' labled "Look for" or "Probe for" another or foreign System. IF the box is not checked... check it. IF it is checked then still click on the 'OK'. Then ReStart and you will, or should, see your Windows boot again. Thanks to: gogalthorp on the forum.

  Public Release   The 13.2 install... again

 April 14th, 2016 /7:14am  Between April 3rd, and now, we installed this version of Linux on our newest HP i7-2. (I refer to them as i7-1 and i7-2)

 From the November 2014 install  So we are trying another FULL DVD Fresh Install... had no choice. The Windows 8 Recovery wipes the whole disk. ... Yeah... and now days later we are re-installing Linux ... again. This has been one heck-of-a learning curve. More than just the UEFI Secure Boot. In the past seven years they have put more and more on "The Chip". 'Nuff' said for now...

Refer: SUSE LINUX Enterprise Server 9 Administrator's Handbook - and
openSuSE 13.1 Startup.
OS Information
		  OS:            Linux 3.16.6-2-desktop x86_64
		  Current user:  ctaylor@Tipper-i7
		  System:        openSUSE 13.2 (x86_64)
		  KDE:           4.14.2 (4.14.2) 
Display Info
		  Vendor:        Intel
		  Model:         Intel Haswell Integrated Graphics Controller 4600
		  2D driver:     xf86-video-intel
		  3D driver:     mesa-dri
Harware Description
Item Specifics - HP 500-277c i7-Quad Pavilion Computer and HP 700-530qe i7-Quad Envy Computer
  Brand: Hewlett Packard Memory(RAM): 12 GB
32 GB
  Model: Pavilion 500-277c
Envy 700-530qe
Hard Drive Capacity: (1) 1TB Drive
(1) 1TB & (1) 2TB Drive
  Processor Type: Intel i7-4770 Quad
Intel i7-4790 Quad
Operating System(s): Windows 8/SuSE 13.2 
Windows 10/SuSE 13.2 
  Processor Speed: 3.4 GHz
3.6 GHz
Optical Drive: SuperMulti DVD Burner drive
SuperMulti DVD Burner Drive
  Video Graphics: Intel HD Graphics 4600 (GT2)
2GB Radeon R7 240 Video Card
Sound/Audio: Integrated IDT 92HD65C Audio
Integrated IDT 92HD68E2 / 7.1 channel
  i7-1 - Wireless Keyboard & Mouse with USB receiver/transmitter, Memory card reader,
         Wireless LAN 802.11 b/g/n, Network LAN: 1000BASE-T Realtek RTL8151GH-CG
  i7-2 - Wired Keyboard and Mouse, Memory card reader,
         Network Integrated 10/100/1000 1000 Base-T Ethernet, Wireless LAN 802.11 b/g/n

         And the HP i7-2 has Bluetooth 4.0.
  These are Quad core Processors -and- YES, like my old Pentium D, I am proud of them.
  Printer: HP cp1700 or HP 7520 Router: NetGear RT311    WNDR3700
  Printer Server: NetGear PS110 Switch: NetGear GS108
  ETH0: Realtek RTL8151GH-CG LAN WLAN: Atheros AR5B125 802.11bgn Mini Card
  : :

 SuSE 13.2 PR Install  

  1. Preps - Downloaded iso and Burned DVD
  2. Created a 13.2 dir on the L: drive and saved the personal configs for both us and root
  3. Re-Boot with DVD - License is correct - for 13.2
    Language and Keyboard both for English, USA. Mouse and GUI work.
  4. System Probe - Analyzing 'Puter... seems satisfied.
  5. Install Mode - New. Auto Config - NO!!
  6. Time Zone - Date OK - Time not correct. Set it for Phoenix, AZ USA
    Did NOT set it for UTC. In the installation settings it claimed that our Hardware Clock was set for Local time.
    The correct time was entered. It was UTC time even though we stated local. See: System Time
  7. Desktop Selection - KDE Desktop which is the default.
  8. Suggested Partioning... we change via Edit Partition Setup...
    For HP 500-277c i7:
    • /dev/sda     931.516GB    Toshiba DT01ACA100
    • /dev/sda1     1023.00MB      HPFS/NTFS       Win RE tools
    • /dev/sda2     360.00 MB       EFI boot             /boot/efi
    • /dev/sda3     128 MB            MS Reserved        ---
    • /dev/sda4     462.22 GB        Windows           Windows/C
    • /dev/sda5     9.57 GB           Recovery Image    ----
    • /dev/sda6     20.01 GB         Linux Swap           swap
    • /dev/sda7     40.00 GB         Linux Ext4             root
    • /dev/sda8     457.21 GB       Linux Ext4             home
    For HP 700-530qe i7:
    • /dev/sda     931.516GB    WDC-WD10EZEX-60M
    • /dev/sda1     1023.00MB      HPFS/NTFS       Win RE tools
    • /dev/sda2     360.00 MB       EFI boot             /boot/efi
    • /dev/sda3     128 MB            MS Reserved        ---
    • /dev/sda4     459.58 GB        Windows           windows/C
    • /dev/sda5     459.00 MB            ----        ---
    • /dev/sda6     18.22 GB          Recovery Image    ----
    • /dev/sda7     20.01 GB         Linux Swap           swap
    • /dev/sda8     40.00 GB         Linux Ext4             root
    • /dev/sda9     457.21 GB       Linux Ext4             home
    • /dev/sdb     1.82TB    Hitachi-HUA72302
    • /dev/sdb1     128 MB            MS Reserved        ---
    • /dev/sdb2     449.22GB        HPFS/NTFS         /windows/F
    • /dev/sdb3     730.08 GB       HPFS/NTFS         /windows/G
    • /dev/sdb4     683.59 GB        HPFS/NTFS        /windows/H
  9. Create New User. Do NOT use as admin. - NO Auto Login.
  10. Set root password.
  11. Installation Settings.
      Booting -> Boot Loader Installation -> Boot Loader Options
     We are leaving the defaults.
  12. Software - Make our selections
    1.  Lightweight X11 Desktop Environment  xscreensaver
    2.  X Window System  MozillaThunderbird, wine
    3.  Multimedia  audacity - timidity not there(found it!)
    4.  Graphics  dia
    5.  Console Tools  makedev
    6.  Web and Lamp Server apache2, apache2-prefork, apache2-mod_perl, apache2-mod_php5, apache2-mod_python, php5-ctype, php5-dom, php5-gd, php5-iconv, php5-mysql, php5-zip
    7.  DHCP and DNS Server  bind, dhcp-server, dhcp-tools, YaST2-dhcp-server, YaST2-dns-server
    8.  Base Development  gcc, gcc-c++, glibc-devel, make, patch
    9.  Intergrated Development Environment  cervisia, kdevelop4, kate
    10.  Java   No to Java. Want older version.
    11.  Linux Kernel Development cscope, ctags, indent, kernel-source, kernel-syms, patchutils
    12.  Web Developement  apache2-mod_tidy, kfilereplace, kimagemapeditor, klinkstatus, tidy
  13. In addition to the above, we installed these:
    1. apache2-doc
    2. bind-doc
    3. dhcp-doc
    4. kernel-docs
    5. php-doc
    6. mtpaint
    7. kdeartwork4-decorations
    8. kdf
    9. ktux
    10. smb4k
    11. gvim
  14. Firewall & SSH - Disable. Messes with our VMware.
  15. Install...11:17am... and first reboot at 11:32am.
  16. Oh WOW. Got some new screens that look gorgeous.
    As it turns out, these "New" screens are from Grub2.
  17. 11:35am ... Hostname and Domain - Tipper-i7 / TRComputing
                 Dakotah-i7 / TRComputing
    NO to change hostname via DHCP - on Tipper-i7
    However, on Dakotah-i7 it was set to YES and I could NOT change it!!
  18. 11:37am... Network Config - Everything looks good ... use it.
    Nope! Here is where we can use one of the fixes. Selecting NetworkManager.
    Got warning that no encryption was used on DHCP. We don't.

    Clicked on next and it said 'iw' needed to be installed. ok... install...it did.
  19. Test Internet connection - said Success.
  20. 11:48am... Loading the Package Manager
    Load Sources
    Refresh sources
    Rebuild cachec
    Load cache
  21. 11:51am... Online update - Do it... accept patches...finish 12:02pm
    Reading the New Release Notes.
  22. We DO have a UEFI - Unified Extensible Firmware Interface.
  23.  Nov 25th, 2014  We are doing an UpGrade so the "other fix" in fstab should not be needed.
    Again, since this is an UpGrade, the Network names should be ok.

    Alllllrighty now.... We are doing a 'Clean Fresh Install'. The Network Names will be set. We are NOT specifying "nomodeset" at this time.
    Need to read the Apache 2.4 changes.
  24. Hardware config - Do it.
  25. 12:20pm...FINISH!! And claims to be good!!
  26. First Login - New Screen. OK! - Remove DVD
  27. 12:23pm... At new Desktop of Welcome Dialog. Clicked on close and it disappeared fast.
  28. 12:25pm...Clicked on Gecko Orb and was instantly presented with a menu.
    Put the 'Lock/Logout' icon on the Panel at the bottom.
  29. Copied inxi into /usr/bin
    This can be a very handy command. It will tell you all about your computer. Things you need to know. A copy may be obtained at: inxi options
    Thanks 'oldcpu' for telling us about it.
  30. *-*-* Ok. Another deviation. I have fought with the "sizing" arrows
    *-*-* forever. Finally fixed them: Pointer Acceleration = 1.7 x
    Pointer Threshold = 6 pixels
    *-*-* Hopefully they will stay after a re-boot... Hurray.. they did!!
    *-*-* BUT ... did not fix the sensitivity of the arrows.
    *-*-* Think that I need to increase the Window Border sizes.
    NOPE!! I didn't. The fix is in:

    # force resize-handle size to zero
    style "oxygen-sizegrip" = "oxygen-default"
        GtkWindow::resize-grip-height = 0
        GtkWindow::resize-grip-width = 0
    Change the 0's to something else. I used 4.
    -But- that wasn't good enough. Changed it to 8.


  Runlevels Services

Systemd is a system and service manager, compatible with SysV and LSB init scripts for Linux. systemd provides aggressive parallelization capabilities, uses socket and D-Bus activation for starting services, offers on-demand starting of daemons, keeps track of processes using Linux cgroups, supports snapshotting and restoring of the system state, maintains mount and automount points and implements an elaborate transactional dependency-based service control logic. It can work as a drop-in replacement for sysvinit.

Refer: System Info List of LINUX Services
  1. atd - This program allows you to run jobs at specified times.
  2. autofs - AutoFS is a kernel-based automounter for Linux.
  3. autovt -


  Networking & WiFi

Alllllrighty now... We got connected to the Net via our WiFi -but- as usual ... don't really know how we did it!! At this point... I really don't care anymore. As long as I can bumble through and get a working system ... who cares how it was done.

I connected the Wired Side -but- guess what?? It ain't workin'...yet. -But- I don't believe that 'apache2' and 'samba' got started. They have new ways...
Ok now, I used my 'old' httpd.conf -and- we had a couple of problems. One was the fact that I had to change an entry with "dusty-tr2.TRComputing" to "Tipper-i7.TRComputing" on the HP Paviliion i7 and to "Dakotah-i7.TRComputing" on the HP Envy i7. The other was:
IncludeOptional   /etc/apache2/vhosts.d/*.conf
The "IncludeOptional" was new .. to me anyway.(it was there in the old but NOT optional) AFTER fixing those two items I was able to get apache2 started. -But- samba still isn't. Wellll.. that's cause I can NOT use my 'old' stuff anymore. Now have a New machine -AND- running them BOTH at the same time!!

  •  ps -ax | grep httpd | grep -v grep
  •  netstat -l | grep http
  •  /usr/bin/lsof -i | grep -i httpd
  •    apache2 ver 2.4.6-6.33.1-x86_64   
  •  systemctl start apache2.service
  •  systemctl stop apache2.service
  •  systemctl restart apache2.service
  •  systemctl enable apache2.service
  •  systemctl status apache2.service
  •    Samba ver 4.1.11-3.26.1-x86_64   
  •  systemctl start smb.service
  •  systemctl status smb.service
  •  systemctl start nmb.service
  •  systemctl status nmb.service

 December 29th, 2014/2:13am  "My Networking" info will carry you, or me, across three openSuSE Systems. Because I didn't feel like writing or copying the same info into each copy of my WebPages. We will leave here and move to:  openSuSE 12.3   and from there will will move to:  openSuSE 12.2  . And then again, I may move all the stuff to here and have others jump... well, I copied pieces of it.

More changes for Samba Local ops

Ok, got a second third new 'puter and the need developed to access the files in my Rezound work area on the 'old' one from the 'new' one... -AND- from 'old new' one to the 'new new' one. This envolved the following steps:

  1. On 'Old': Modify Samba smb.conf file and add:
            comment = Directory for Android development
            path = /home/ctaylor/Android/cm11.0-rezound
            browseable = yes
            read only = no
            create mode = 0755
            guest ok = no
            printable = no
  2. On 'New': Create TR7480 dir -- md TR7480
    I created it in my home dir.
  3. On 'New': mount -t cifs -o user=ctaylor   //   /home/ctaylor/TR7480
    It will ask for password.
  4. ls -F TR7480 (Append a character to each file name indicating the file type.)
    and it will list the dir on the 'Old PC'.
  5. Now I can compare the files ...
  6. Refer:  Mounting Samba   Also:  Ubuntu Fstab  


  Java Install

The following is from a conversation on the  openSuSE Forum  .

Carlos and wolfi323,
Thanks to you both for your replies. I would presume from your answers that
it would be best IF I install all the items that are going to demand an openJDK ...
and then install the Oracle version that I want and make it the default.
Otherwise, IF I install the Oracle first, it will get placed on the "back burner" ...
via the other installs.

Is my assumption correct??

No, the ordering is irrelevant.

You have to install both, no matter in which order. One, because the
system demands a java it recognizes as such, or it will remove
everything related to java in the entire system because "there is no java".

The other because it is the one you want.

In fact, during system install, you can only install the system one, as
none other is available at that point. But you can install none, install
after system install the jre, then install the system one, then all the
other packages, like libre office.

As I said, ordering is irrelevant. But maybe inconvenient.

No matter what order of install you use, then you use the
"update-alternatives" script to choose the default java.

The order of install doesn't select the default one.

Got a section like this over in 13.1 -but- I just don't remember what I followed, IF anything, to install it. My greatest difficulty was with the fact that it was demanding openJDK 7 and/or 8. I didn't want them -but- as you can read above, they were demanded. I have just jumped all over trying to get a setup that will let me use Eclipse... without errors. I got one over on my 'old' machine -but- for some reason I can not get one here on the new one. Finally got a clean 13.2 install, so may be now.
Got another new machine and on this one we got the last Java 7, jdk-7u79-linux-x64.rpm. So all those "71's" will need to be changed to "79's".

So now, we have Oracle Java installed.

    Installed via jdk-7u71-linux-x64.rpm
    Verify the installation:
    ls -l /usr/java/
    total 4
    default --> /usr/java/latest
    latest --> /usr/java/jdk1.7.0_71/

  |           |                 |
 bin         lib               jre
  |           |         ________|__________
java*     tools.jar    |                   |        
javac*    dt.jar      bin                 lib                
javap*                 |       ________ ___|___ _________ ________ _______       
javah*               java*    |        |       |         |        |       |    
javadoc*                    rt.jar    ext   security   i386    applet  fonts
javaws*                 charsets.jar   |              /    \
jar*                              localedata.jar  server  client

This is a modified version of this  Ubuntu   Page. He/She was using Java 1.8. I can not use that ... yet. Besides that, I am using different 'dirs'. And I switch into 'root' to perform the operations. There is enough that I feel the 'sudo' command is a pain. But to each their own. -And- now there are even more changes. I switched to the RPM on this 'latest' install.

  1. Download the Oracle Java JDK  here  .
    Note: download appropriate file, for example if your system is openSuSE x64, the download file is named like this: jdk-7u71-linux-x64.rpm Also notice, unless things have changed, you need to bring down a version 7 -- NOT 8.
    (Nov 25th, 2014)
  2. After extraction
        /usr/java/default --> /usr/java/latest
        /usr/java/latest --> /usr/java/jdk1.7.0_71/
    Don't know why we need all those links -but- hold on cause we are gona get more!!

  3. Update the PATH by opening, 'as root', the /etc/profile.local file:
    kwrite /etc/profile.local and paste the following at the end of the file:
    export JAVA_HOME=/usr/java/default
    export PATH=$PATH:$JAVA_HOME
    IF by some chance, profile.local is not there, create it. It is conditionally looked for. Also, now would be a good time to add any other paths that you might need.
  4. Save and exit.

  5. 'As root', tell the system that the new Oracle Java version is available by the following commands:

    update-alternatives --install "/usr/bin/java" "java" "/usr/java/jdk1.7.0_71/bin/java" 20000
    update-alternatives --install "/usr/bin/javac" "javac" "/usr/java/jdk1.7.0_71/bin/javac" 20000
    update-alternatives --install "/usr/bin/javap" "javap" "/usr/java/jdk1.7.0_71/bin/javap" 20000
    update-alternatives --install "/usr/bin/javah" "javah" "/usr/java/jdk1.7.0_71/bin/javah" 20000
    update-alternatives --install "/usr/bin/javaws" "javaws" "/usr/java/jdk1.7.0_71/bin/javaws" 20000
    update-alternatives --install "/usr/bin/jar" "jar" "/usr/java/jdk1.7.0_71/bin/jar" 20000
    update-alternatives --install "/usr/bin/javadoc" "javadoc" "/usr/java/jdk1.7.0_71/bin/javadoc" 20000
  6. 'As root', make Oracle Java JDK as default by this following commands:

    update-alternatives --set java /usr/java/jdk1.7.0_71/bin/java
    update-alternatives --set javac /usr/java/jdk1.7.0_71/bin/javac
    update-alternatives --set javap /usr/java/jdk1.7.0_71/bin/javap
    update-alternatives --set javah /usr/java/jdk1.7.0_71/bin/javah
    update-alternatives --set javadoc /usr/java/jdk1.7.0_71/bin/javadoc
    update-alternatives --set javaws /usr/java/jdk1.7.0_71/bin/javaws
    update-alternatives --set jar /usr/java/jdk1.7.0_71/bin/jar
  7. Reload sytem wide PATH /etc/profile.local by this command:
    source /etc/profile.local
    Well, actually, not necessary IF you do the next command.

  8. Reboot your system.
  9. zypper rm icedtea-web
    For 64-bit architecture:
    ln -s /usr/java/jdk1.7.0_71/jre/lib/amd64/libnpjp2.so /usr/lib64/browser-plugins/
  10. Check Java JDK version by this command: java -version. If installation is succesful, it will display like the following:

    java version "1.7.0_71"
    Java(TM) SE Runtime Environment (build 1.7.0_71-b26)
    Java HotSpot(TM) Server VM (build 24.71-b01, mixed mode)

That's it!

Note: We Assumed that the downloaded file is named jdk-7u71-linux-x64.rpm and used this name in all the commands used in steps 2, 4 and 5. It depends on the type of O.S and processor type (i.e., 32bit or 64bit).

Now check your setup with:
> ls -la /etc/alternatives/java* && ls -la /etc/alternatives/jar

Ok... it all looks good. IF it don't work then we'll just quit!!


  The Install(s)

 Final Release - November 4th, 2014  As stated elsewhere we kinda dragged our feet on this one and did NOT do a whole lot with it whilst it was being developed. Now, and now... we are going to jump in with both feet... and make it our New Main System ...on our Newest Computer.

  1. DVD downloaded and created.
  2. Windows 7 VM saved.
  3. Web Pages copied to Laptop.
  4. Saved VMware 10 to a CD
  5. Did NOT save any Android stuff cause that is going to be re-setup.

There were some complaints and hardships mentioned on the forum -but- as stated this is to be our last for a while so we are just gona do it. Any problems that occur will only occur once. Don't want to have to fight things twice.

 At 10:27am  ... we are starting the process. DVD in drive and a ReStart.
Nope!! Got interrupted!!
Back @1:51pm -- AppArmor was selected -- we said NO! Disabled FireWall!!
- - - - - Made selections from memory of the things we think important. - - -
2:18pm -- Fired off Install.
2:35pm -- Finished and ReBooted.
2:37pm -- In Grub2 and first entry selected. We paused it with arrow key.
2:38pm -- Selected first entry and hit Enter Key.
2:39pm -- Preparing initial System Config.
2:41pm -- Network Config - Using defaults
2:45pm -- Test Connection - Success!!
2:46pm -- Loading Package Manager.
2:47pm -- Run UpDate. - Hmmmmm... got a lot!!
2:53pm -- UpDate finished... got Release note.
2:53pm -- Hardware Config... accept defaults
2:55pm -- Finished!! With a Congrats.
2:55pm -- Have a Logon Screen.
2:57pm -- Have a Desktop!!

Interesting... We got the Updated Release notes in the 'Test Connection' -and- we got the Updates in the UpDate Section. But now arriving at the Desktop we can not connect to the Web. Don't think we ever could at this point. Have to set up some parameters. -But- have to got to work .. so later.       3:02pm

 Later:  Was NOT a successful install!!

 An UpGrade Try  We read in the forum how member named Thailandian performed his install... so we decided to try it.
Here's what he did:

  1. Changed all main repositories to 13.1 with the Yast Software Repository tool. The SBD recommends zypper for this, but I always prefer to use a gui tool if I can, as it's a lot easier to check your work.
  2. Deleted all community repositories except for Packman. The SBD recommends this (I guess including Packman). I decided to try changing the Packman repository instead, so that I wouldn't have to go back later to get mplayer et al working properly.
  3. Added the 13.1 DVD (iso) file as a repository. I always do this anyway after installing/upgrading so that Yast doesn't keep hassling to insert the DVD.
  4. I set the priority of the iso file to 98 and the priority of Packman to 97. My logic was a) I want the Packman versions of files rather than the hobbled OSS ones, and b) I didn't want to download anything that was already on the DVD (iso). I'm not sure if that second part was necessary, but I've read that zypper prioritises web-based repositories over the DVD, even if the version number of files is the same - perhaps that information is out of date.
  5. Refreshed all repositories and closed the Yast tool.
  6. su'ed into a terminal and typed "zypper dup".
  7. Apart from the usual warnings and license approvals, I did get one dependency issue: "ibus-1.5.4-1.1.x86_64 conflicts with libreoffice-kde4 provided by libreoffice-kde4-". I'm not sure what caused that, but decided to play it safe and uninstall libreoffice KDE integration temporarily.
  8. Once zypper got under way ... I watched a 30 minute podcast while having dinner.
  9. By the time dinner was finished, so was zypper (actually it may have been a little longer than 30 minutes, but not much). I rebooted my laptop.

 Now our turn:  Well, it started at 9:25am. At 9:27am we got told that there were:
1666 packages to upgrade, 24 to downgrade, 331 new, 89 to remove, 31 to change vendor, 4 to change arch
Overall download size: 1.6 GiB. After the operation, additional 552.8 MiB will be used.
Had an interruption...
9:52am said yes....
10:23am -- removing and installing.. n/2087 .. guess that means there are 2087 items to install.
11:00am -- finished around this time. We didn't see it finish.
Now we are told to restart some programs that were already running. We are just gona restart the System.

Allllllrighty... it ReStarted and things look the same. Kgpg Assistant came up and wanted to do some stuff -but- we said no. We are not that paronoid. 'uname -a' gives:
  Linux dusty-tr2 3.11.6-4-desktop
There is more but that is enough for now.

We also got notice of 25 UpDates by 'apper'. We said do it. Well, as usual, it is more than what is first stated. 25 turned into 79. 'libreoffice' was among them.

 New icons  Apper is now a 'Bug'. When we clicked on continue, for the above, it looked like nothing was happening. So we clicked on the 'Bug' again and watched the updates happening. Don't know why anymore they hide things. We would rather see some action!!

Well now, one of those 'new' icons looked like the World with a Cigaret sitting on top of it. We hovered over it to see if it would describe itself and it did not. We clicked on it.... BIG Mistake!! Now our system is "Locked up!!" Had to 'PowerOff ReSet'.
Upon 'ReStart' the World with a Cigaret on top was not there. However, nothing worked correctly either. Could not see my Windows Drives in Dolphin, could not connect to the Internet with Firfox and clicking on the 'Orb' had to wait a couple of minutes before we got any selections. We have tried the Milestones, Betas, RCs and now the release. This is the worst openSuSE Linux that we have encountered since we started at version 6.2. Going back to 12.3 and using the 13.1 DVD for target practice.

Ok, so we are going to install openSuSE 13.1 Beta on our newly re-built System. This will be on Partitions 5, 6 and 7. Partitions 8, 9 and 10 have Ubuntu on them. Partition 1 is for Windows.

First attempt failed. BTRFS did not find enough room. Strange, we just had a 12.3 System occupying that same space. Second attempt just died! We had to visit the facilities during the install and when we came back out the screen was black. No alternative -but- to PowerOff. Third attempt got installed... IF you can call it that. Finally was able to get out of it and then re-install 12.3. Really, really to much wrong with this for a version to be called a 'Beta'. Should be at the most an 'Alpha' -but- probably a 'Zebra'.

 October 11th, 2013/8:50am  Well, the Beta was a disaster. So here we are at RC1. We are gona try again using it.

At the 'choices' screen, we chose Install. At the Welcome screen we see the License Agreement is for 13.1 so we have the correct one. Something keeps gnawing at me... forgot something. Oh well, when we need it I'll remember it! Allllllrighty... standard answers for the first part. Now at the Partitioning we have set it up for Partitions 5, 6 and 7. Software selections... ummmm... had to DESELECT AppArmor.

 Friday 11 October 10:00am  We have SUCCESS!! We are at the LogOn Screen. Which is one heck of a lot farther than we got with the Beta. Wellll... now we can't LogIn!! It keeps failing on the password. Ooooohhhh... even though it has our name showing... we are not selected UNTIL the name is in highlites! Then and only then we can enter our password and get signed on. ARRRGGGG.... shame on us!

Ok. We have a desktop with the usual Welcome. That is closed and now it looks like the 12.3 desktop. Well the little icons down in the bottom right corner are different. But so far that is all. Allllllrighty... Kinfocenter claims we have: (Oct 10th/3:20pm)

Linux 3.16.6-2-desktop
openSuSE 13.2 (Harlequin) (x86_64)
KDE Platform Version 4.14.2

The above was/is part of the 'Summary'. 'Memory' had a lot of info also -but- when we tried 'Device Information'->'Device Viewer' all we got was two spinning marbles. We could not stop it. We clicked on the 'x' in upper right corner and got a dialog about "Application kinfocenter is not responding". Well, we know that. We were asked if we would like to 'Terminate' and we said yes. It didn't!! We clicked on the Button in our taskbar and then clicked on close. Nope! Got the dialog box again, responded 'Terminate'. Nope! Darn!! And we don't have any of our tools loaded yet. Well, this is a real house warmer! Couldn't even kill it will 'kill -9 PID'!! Killed its 'Master' which killed my session. Logged back in and will setup our tools -before- proceeding any further.

AARRRRRGGGGG!! Going back to 12.3!!!! We'll wait for RC2 and will set it up in our 'test' area. Ubuntu will have to go. We only needed it to S-Off our HTC ReZound SmartPhone. Hopefully, we won't need it again... and IF we do they will probably have changed things anyway. That is why we had to install Ubuntu in the first place.


  Tool setup

This will probably be half configuration and half tools, -but- they kinda go hand in hand... don't they??


  VMware 10 ...   -and- Long Overdue Fix

The following was extracted and brought here so you wouldn't have to jump around and to avoid some of my verbiage. Don't think you are interested in my horror stories anyway.

   October 25th, 2013 / 12:46am     Ok, we are back at it after work. This time we are using the Win2K path. Same inside, inside bla, bla. This time the 'Lord' showed us another "fix". The 3D Accelerator was just to show us that there is hope and the problem can be fixed. This one is down in Linux... To disable the nmi_watchdog interrupt.
     cat /proc/sys/kernel/nmi_watchdog (to check if it is set)
     echo 0 > /proc/sys/kernel/nmi_watchdog (to disable it, if it is)
     cat /proc/sys/kernel/nmi_watchdog (to confirm the change)
Refer: Geek 2.0 and Linux NMIs on Intel 64-bit Hardware

Now then, there are some who will worry about this change. Actually, the only ones who should worry about it are the kernel developers and maintainers. IF your System is working fine, other than these "Freeze/Lockups" then there 'shouldn't be any worries. It appears that this particular NMI, the nmi_watchdog, is causing more harm than good. You could also write a script that disabled the nmi_watchdog before starting VMware and then re-enabling it after exiting VMware.

Now the proof is in the pudding. We got some false hopes over a couple of the previous fixes, which lead to sadness. This "fix" may lead to Re-activating the 3D Acceleration in VMware. -But- that needs to be tested first. BUT first we see how long this 'fix' can keep us going. So far it is a 'temporary' fix using the instructions above. Cause at next ReBoot of the System it, the nmi_watchdog, will be Re-Enabled. So, we need to make choices here...    Permanent -or- Temporary.??

We are gona be daring and make it Permanent. This accomplished by placing:
on the Command Line in the Boot Loader. The following is performed as 'root'.

  • Edit /etc/default/grub and add nmi_watchdog=0
        GRUB_CMDLINE_LINUX="nomodeset nmi_watchdog=0"
    We had already edited this for the nomodeset now we add the other.
  • Execute:
        /usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg
  • Execute:
        grub2-install /dev/sda

ReBoot and enjoy....

 November 30th, 2014 - The INSTALL :  Got side tracked and now back to it. We first change to 'root' and then to the VMware 10 dir and then execute the command:

  1. Presents a license agreement - to which we agree.
  2. It asks IF we would like to check for 'product updates' on startup -and- we say no. We'll check on our own.
  3. Next is a question about sending anonymous system data and user statistics to VMware 8. Again we are saying no. Have enough trouble just trying to get things to work normally. We don't need all these background operations. We'll help in other ways.
  4. Next it is asking us to enter the user that will initially connect to the Workstation Server. They are choosing 'root' which we will leave.
  5. Next we are picking a dir for our 'shared virtual machines'. We are going to accept their suggestion of
        "/var/lib/vmware/Shared VMs"
  6. Next they are asking for a port to use for 'https'. We are accepting their suggestion of:
        HTTPS port: 443
  7. Now we get the message "The product is ready to be installed." And we click on Install.
      Installing VMware Installer 2.0
      Installing VMware VMX 6.0.4
      Installing VIX core
      Installing Network Editor
      Installing VMware Player
      Installing Workstation
      Installation was successful.
    Missed a few, as signified by the dots, -but- we'll get them on the Next Install... IF we remember -and- are fast enough.

  1. Launch VMware Workstation 10.
  2. With this 'Latest version' -- It seems Patches are NOT needed... it just works!! At least we got the initial screen. We had trouble with version 10.0.0-1295980.
  3. Of the choices we are choosing "Create a New Virtual Machine".
  4. We'll do a 'Typical'.
  5. For the OS we chose "Install the OS later".
  6. For the Guest that will be installed we chose "Windows 7".


  VMware 11 & 12

Well, I got the "Evaluation" copy of VMware 11. However, IF/when I decide to purchase it I will only be able to get version 12. I had to remove my ver 10 before I could install version 11. Version 11 installed with absolutely no problems -and- it read my saved Windows7x64 just like nothing had changed. Wow.

 July 17th, 2016/3:48pm   Now then, they say you can't... so I had to. Did not like having my Windows 10 being called Windows 7. So I changed the name in the Settings -> General and then changed the Working Directory. When I started VMware it wanted to either create a new one or open and existing one. Well, I said open an exiting one and pointed it to my newly named dir. I left all the files inside it with the Windows 7 name but the ones that are used and seen by the user(me) will have the Windows 10. It works.

 July 12th, 2016/2:56am  We purchased VMware 12 and after a stuggle and lots of hassel, we got it downloaded. The people were nice but the electronics was not!! Finally was directed to a direct download site we got it down. VMware Version 12.1.1. Then during the installation it wanted my license number. Well, I was on HP i7-2 and the license number was over in my emails on HP i7-1!! So, I took the option of entering it later. However, AFTER the install, I tried to got to 'My Account' on VMware's Site and get the license number. Once again I had trouble getting the information I needed/wanted. I finally had to go over to my HP i7-1 emails, copy the license number, create a text file and paste it in, then go back to HP i7-2, copy the text file with the license number over to my HP i7-2, copy the number from that file, start up VMware 12 and paste it in the dialogbox on startup.
Now then, in their(VMware's), defense, they were implementing some system changes and I do believe that was the cause of most of the hassles.

 January 19th, 2017  Had to make this alteration like we did over in openSuSE 12.3. ... this is courtesy of Larry Finger @ http://www.lwfinger.com/nvidia_patches/

cd /lib/modules/3.7.10-1.1-desktop/build/include/ (numb in red could be different)
ln -s generated/uapi/linux
'ls linux' should show version.h

This was because of a bunch of UpDates.

Probably intuitively obvious, but the following was 'copied' from the VMware Site. I like to hang on to things that pertain to my Systems. I also like to add my two cents worth... sometimes. Now then, I UpGraded from version 10 by first 'Uping' to a Version 11 trial and then Uping to a Version 12 purchased. The UpGrade/Install procedures for 11 and 12 were essentially the same... just changed the numbers.

Before Upgrading

Before upgrading to VMware Workstation Pro 12:
  • Ensure that your physical machine meets the system requirements. For more information, see Introduction and System Requirements section in
     Using VMware Workstation Pro  .
  • Shut down your virtual machines.


To upgrade to VMware Workstation Pro 12, you can use one of these options:


After the upgrade to VMware Workstation Pro 12 is complete:
  1. Upgrade the virtual machine hardware version:
    1. Click Upgrade Hardware version on the Virtual Machine Summary page. You can also select VM > Manage > Change Hardware Compatibility.
    2. Follow the steps in the Wizard and click Finish when the process is complete.

  2. Power on the virtual machine and update VMware Tools:
    1. Click VM > Update VMware Tools. The VMware Tools installation Wizard starts in the virtual machine.
    2. Follow the steps in the Wizard and click Finish when the process is complete.
    3. Restart the virtual machine.
Refer:  Up from 11 to 12  

Installing VMware Workstation

  • You can only have one version of VMware Workstation installed at one time. You must uninstall any previous version of VMware Workstation before installing a new version.
  • As root: In a terminal window, type:
             vmware-installer -u vmware-workstation .
  • If the installer reports an error when you run it, you may want to verify the download. For more information, see 
     Verifying the integrity of downloaded installer files (1537)  .
    To install VMware Workstation on a Linux host:
Note: VMware Workstation for Linux is available as a  .bundle download from the  VMware Download Center  . The Linux bundle installer starts a GUI wizard on most Linux distributions. On some Linux distributions, the bundle installer starts a command-line wizard instead of a GUI wizard.
  1. Log in to the Linux host with the user account that you plan to use with VMware Workstation.
  2. Open a terminal interface. For more information, see
      Opening a command or shell prompt (1003892)  .
  3. Change to root. For example:

    su root

    Note: The command that you use depends on your Linux distribution and configuration.

  4. Change directories to the directory that contains the VMware Workstation bundle installer file. The default location is the Download directory for the user which initiated the download from the VMware Download Center.
  5. Run the appropriate Workstation installer file for the host system. For example:

    sh VMware-workstation-Full-xxxx-xxxx.architecture.bundle [--option]

    • xxxx-xxxx is the version and build numbers
    • architecture is  i386 or  x86_64
    • option is a command line option.

      This table describes the command line options:

      Option Description
      --gtk Opens the GUI-based VMware installer, which is the default option.
      --console Use the terminal for installation.
      --custom Use this option to customize the locations of the installation directories and set the hard limit for the number of open file descriptors.
      --regular Shows installation questions that have not been answered before or are required. This is the default option.




      Allows the installation to continue even if there is an error in one of the installer scripts. Because the section that has an error does not complete, the component might not be properly configured.
      --required Shows the license agreement only and then proceeds to install Workstation

  6. Accept the license agreement.

    Note: If you are using the  --console option or installing VMware Workstation on a Linux host that does not support the GUI wizard, press Enter to scroll through and read the license agreement or type  q to skip to the yes/no prompt.

  7. Follow the on-screen instructions or prompts to finish the installation.
  8. Restart the Linux host.

After installation

    On Linux host systems:
  • VMware Workstation can be started from the command line on all Linux distributions.
  • On some Linux distributions, VMware Workstation can be started in the GUI from the System Tools menu under Applications.
  • To start VMware Workstation on a Linux host system from the command line, run the  vmware & command in a terminal window. For more information, see   Opening a command or shell prompt (1003892)  . For example:

    /usr/bin/vmware &
The first time you start Workstation, Workstation prompts you to accept the End User License Agreement. After you start Workstation, the Workstation window opens.


  P-state Problem

Quote from SuSE Forums concerning kernel 3.10 has a big problem :

the 3.10 kernel made my cpu runing on the fastest freq with turbo boot always on, when i downgrade it to 12.3's kernel 3.7 ,the problem solved

I solved the problem according to Tyler_K's explain:

  • in 3.10, support for the P-state driver was extended to Ivy Bridge (what you have) processors ... maybe Haswell too? (I don't remember)
  • all the cpufreq scaling governors do not apply ... do NOT use them with the p-state driver, which (IIRC) is built into the kernel (i.e. static as opposed to a module)
  • to disable the pstate driver (if you really are having trouble with it), use the "intel_pstate=disable" boot option

openSuSE 13.1 is using kernel 3.11.1-1.2


  System Notes

James again from Austin, Texas made the following observation:

The following was missing from the fstab file.
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0

To which Carlos replied:
    Those entries are deprecated. Don't create them, as systemd now handles that.

petermcph on the forum quizzed:

Don't get the welcoming music clip when booting had completed, nor a "twang" when shutting down.

To which wolfi323 replied:
KDE disabled this by default in the current version (4.11).

If you want to have it, go into "Configure Desktop"->"Application and System notifications" and configure it. The "Event Source" containing the login sound is "KDE Workspace".


  Repository Info

Ok now, the following is a list of our Repos in SuSE 13.1. (This list is here for a memory jogger.)

> zypper lr


  Features of 13.1

Just a few hi-lights. The 'Big List' is at: Major Features

  • KDE is updated to 4.11 release
  • Glibc is updated to 2.18 release
  • Kernel is updated to 3.11
  • X.org updated to 1.14 release
  • All X.org video drivers are updated to latest stable release (or snapshot).
  • Mesa updated to upcoming v9.2.1 snapshot.
  • Freetype brings support for color embedded bitmaps
  • Qt updated to 5.1.1 release.
  • Java (Based on OpenJDK 7 and IcedTea 7):


  ??? Next ???

Blend is a free, fully standards-compliant CSS template designed by Free CSS Templates. This free template is released under a Creative Commons Attributions 2.5 license, so you're pretty much free to do whatever you want with it (even use it commercially) provided you keep the links in the footer intact. Have fun with it :)

This template is also available as a WordPress theme at Free WordPress Themes.