Welcome to Our SuSE 13.1 Info Website!

 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 system. We have reverted back to openSuSE 12.3 and will stay there.

 October 29th, 2014   - A reprieve. We got a new machine and this version works on it... well after a lot of hassle. The biggest problem was/is UEFI on the New Machine. More on that in my:  HP 500-277c i7-Quad   and  New Start Over   WebPages. In fact there will be even more spread out next week when openSuSE 13.2 is released. So, we will have to bounce around amongs 4 WebPages to get the whole story. I will try to remember from this point on... to put in proper references.

 Findings - November 24th, 2013/1:09pm  What we have found that "Might" help us. Listing all the 'possible' helps right here at the top.

Courtesy of  jdeca57  :
solved the problem with KDE by going to a terminal [crtl][alt][F1] and entering:
kwriteconfig --file kwinrc --group Compositing --key Enabled false
kwriteconfig --file kwinrc --group Compositing --key CheckIsSafe true
kwriteconfig --file kwinrc --group Compositing --key OpenGLIsUnsafe false
And from wolfi323:
use YaST->Network->Network Settings to switch between NetworkManager and ifup (Global Options tab).
But if you only have the one wired connection, you might just as well use ifup.
Make sure proc, sysfs, debugfs, usbfs and devpts are removed from fstab.

 September 30th, 2013 / 5:53am  We haven't really done anything with this version... yet. We started this WebPage on the above date -but- that was all... we started it. Our cell phone endeavors took over. -But-, once again, as here in the past couple of years, our trusty 'puter has failed us. This time it was/is the MotherBoard. A replacement of which... changes lots of things!!

We found it interesting that the "Battle" of the OS's somewhat came to light here. We replaced the PSU, the MB and the Video card... all at once. Our Windows Media Center came up and worked. It had to 'analyze' things and then wanted to install drivers for the Video card -but- it worked -and- we could get connected to the Internet. Linux came up -but- we could not get connected to the Internet -nor- our Local Network. That is the reason we are here... now.

Welllll... we changed our mind. As mentioned already, we are having Network problems. Was gona just install this version, even though it is only a Beta, -but- we then decided to try the "Upgrade" section of the openSuSE 12.3 install and see what that would do. That way we will be able to keep all the cell phone stuff installed/loaded and just continue on... IF it works. ... It didn't!!

Now in our recovery we downloaded and created a version 13.1 install DVD via Windows. We had some troubles that gave us worries -but- they turned out to be just a bad ReadWrite DVD. A new one worked fine. Or so it appears for now. We will have to keep and eye on the Windows portion of our system. It just seems that there should have been 'more' involvement in getting it going again. It was just to smooth.

So what?? What are we going to do? Well, right now 13.1 Beta-1 is out and in ten days we will see RC1. So, instead of re-installing 12.3 we are gona jump on the 13.1 boat and go for it. We will 'update' each new preliminary version as it comes out between now and the final version on November 19th, 2013.

 October 11th, 2013/6:20am  Well,the RC1 was a day late. But we got it downloaded and are creating a DVD...

 8:38am  Well, the creation finished and it was successful. Delay has been cause of other things... like the family and the dog. Anywho, we are now ready to install this. We are going to make it our 'Main System'. Yep. Going whole hog. New MB, new PSU, new Video Card and ... a new OS. We had some problems with our VMware operations... mainly cause of the Video card but, then we changed the MotherBoard too. So, rather than reloading 12.3 we decided to install 13.1. ... Nope!! Didn't work!

Now then, the 'new' hardware is supposed to fix different problems. The Motherboard is mainly for the SATA ports. There were some other problems but mainly the SATA. The Video card is/was supposed to stop our System Freezes. We had a lengthy discussion with Mike at nVidia and determined that our 'old' Video card's capabilities had been exceeded for a long time! So, we will see. Our 'old' cards were/are:
an nVidia 7300LE and an nVidia 7600GT ... not at same time of course. These are to be replaced by an nVidia GTX 560. Results are below at: VMware 10

   

The openSUSE Evergreen has just announced that the upcoming openSUSE 13.1 will be the next Evergreen release. This means that the Evergreen team will continue to provide openSUSE 13.1 with with security updates and important bugfixes after the usual 18 month maintenance cycle until it has had a total life time of at least three years.
So, things are looking more and more like we will make the jump to 13.1.

  Public Release   One last time on the 13.1 install...

It really shouldn't be this hard. To those of you who had it easy... thppphh! Anywho, we are trying one last time. Should say two cause we just tried another "UpDate" and it was the worst yet!! So we are trying another FULL DVD Fresh Install.

We are now installing this on our "Newest 'Puter". Never got it to work on the old one .. so .. all this will be changed to fit the new one. IF we forget something... sorry, but we are going to try anyway. This is really of no use for something that didn't work...-and- it appears to be working on our newest machine.

Refer: SUSE LINUX Enterprise Server 9 Administrator's Handbook - and
openSuSE 13.1 Startup.
OS Information
		  OS:            Linux 3.11.10-21-desktop x86_64
		  Current user:  ctaylor@tipper-i7
		  System:        openSUSE 13.1 (Bottle) (x86_64)
		  KDE:           4.11.5 
Display Info
		  Vendor:        Intel
		  Model:         Intel HD Graphics 4600
		  2D driver:     Intel --
		  3D driver:     Intel --
Harware Description
Item Specifics - HP 500-277c i7-Quad Pavilion Computer.
  Brand: Hewlett Packard Memory(RAM): 12 GB ()
  Model: Pavilion 500-277c Hard Drive Capacity: (1) 1TB Drive
  Processor Type: Intel i7-Quad Operating System(s): Windows 8/SuSE 13.1 
  Processor Speed: 3.4 GHz Optical Drive: SuperMulti DVD Burner drive
  Video Integrated Graphics: Intel HD Graphics 4600 (GT2) Sound/Audio: Integrated IDT 92HD65C Audio
  Wireless Keyboard & Mouse with USB receiver/transmitter, Memory card reader, Wireless LAN 802.11 b/g/n, Network LAN: 1000BASE-T Realtek RTL8151GH-CG
  This is a Quad core Processor -and- YES, like my old Pentium D, I am proud of it.
  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.1 PR Install  

  1. Preps - Downloaded iso and Burned DVD
  2. Created a 13.1 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.1
    Now this is where it really got tuff.  Dual Boot Ref  and  Linux Inst  
  4. Language and Keyboard both for English, USA. Mouse and GUI work.
  5. System Probe - Analyzing 'Puter... seems satisfied.
  6. Install Mode - New. Auto Config - NO!!
  7. 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
  8. Desktop Selection - KDE Desktop which is the default.
  9. Suggested Partioning... we change via Edit Partition Setup...
    • /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     401.22 GB        Windows           WinDrvC
    • /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     459.21 GB       Linux Ext4         home
  10. Create New User. Do NOT use as admin. - NO Auto Login.
  11. Set root password.
  12. Installation Settings.
      Booting -> Boot Loader Installation -> Boot Loader Options
     We are leaving the defaults. This new Grub2-efi detects our "UEFI".
  13. Software - Make our selections
    1.  Lightweight X11 Desktop Environment  xscreensaver
    2.  X Window System  MozillaThunderbird, wine
    3.  Multimedia  audacity - timidity not there
    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 "Standard" 1.7 version.
    11.  Linux Kernel Development cscope, ctags, indent, kernel-source, kernel-syms, patchutils
    12.  Web Developement  apache2-mod_tidy, kfilereplace, kimagemapeditor, klinkstatus, tidy
  14. Firewall & SSH - Disable. Messes with our VMware.
  15. Install...... and first reboot at --:--pm.
  16. Oh WOW. Got some new screens that look gorgeous.
    As it turns out, these "New" screens are from Grub2.
  17. --:--pm ... Hostname and Domain - Tipper-i7 / TRComputing
    NO to change hostname via DHCP
  18. --:--pm... 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. 'iw' is a new nl80211 CLI configuration utility for wireless devices.
  19. Test Internet connection - said Success.
  20. --:--pm... Loading the Package Manager
    Load Sources
    Refresh sources
    Rebuild cachec
    Load cache
  21. --:--pm... Online update - Do it... accept patches...finish --:--pm
    Reading the New Release Notes.
  22. We DO have a UEFI - Unified Extensible Firmware Interface.
  23.  Oct 28, 2014 / --:--pm  We are NOT doing an UpGrade so the "other fix" in fstab should not be needed.
    Again, since this is NOT an UpGrade, the Network names should be ok.
    We are NOT specifying "nomodeset" at this time.
    Need to read the Apache 2.4 changes.
  24. Hardware config - Do it.
  25. --:--pm...FINISH!! And claims to be good!!
  26. First Login - New Screen. OK! - Remove DVD
  27. --:--pm... At new Desktop. ot Welcome Dialog. Clicked on close and it disappeared fast.
  28. --:--pm...Clicked on Gecko Orb and was instantly presented with a menu.
    Put the 'Lock/Logout' icon on the Panel at the bottom.
  29. --:--pm... Clicked on the Logout icon. At --:--pm it finally presented a menu of choices. Because I was typing this in, and I'm slow, it took the default and at --:--pm we were back at the Logon Screen.
    --:--pm... logged back in. Clicked on the Gecko Orb again and it was normally responsive. This time we chose the 'Leave' in the Launcher selecetions and ReStarted...--:--pm ... it sat there.at --:--pm we got a count down that said it was ReStarting... at --:--pm it finished and dimmed the screen. at --:--pm it Rebooted.
    at --:--pm got grub2 at --:--pm got Logon Screen.
    At --:--pm back to Desktop... click on Orb and half min later get Launcher menu.
    Lunch!!!!! at --:--pm... clicked on File Manager...at --:--pm it presented itself. Time delay was at least 30secs.
    at --:--pm... logged on as root... delay in getting Welcome Dialog.
  30. Right off -first thing- opened a terminal, signed on as root and did a 'zypper up'. Even though we obtained a 'ton' of updates just before our latest install, there were none this time. They were all obtained at the end of this install. -But- we checked anyway.
    The comments about the time are no longer valid. It came up correctly.
  31. 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.
    As it turns out... there is a copy installed "with" the System in /usr/bin/X11.

   

  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". The other was:
IncludeOptional   /etc/apache2/vhosts.d/*.conf
The "IncludeOptional" was new .. to me anyway. 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
  •  

Allllrighty now... We have both the Wired and the Wireless Networking setup -and- working. -AND- can switch on my IOGear between the two systems and NOT loose my Internet connection. Think that is because I got the Wired portion working -but- what ever... it is working!! Now to get setup for my Android work.
 SuSE CyanogenMod  

   

  Java Install

Allllrighty now... We are going to try to install Java 7 on our New PC under this openSuSE 13.1 System. First we are going to download the Java. jdk-7u71-linux-x64.rpm. Yeah, we are using the RPM version... for starters. IF it doesn't work we'll switch over to the tgz version.

We re-did this over in openSuSE 13.2.  Jump over   there to get the proper install. Works for both versions.

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

There is a little bit more to the above than I entered, -but- it is good enough for now. At the moment I have two Java's installed. It seems that SuSE has some Java requirements and insists on having one installed. It installed openJDK 7 and when I tried to remove it, it was going to replace it with openJDK 5!! So I need to get things set up so it knows that I have installed another Java.
$PATH is set in /etc/profile and /etc/profile.local

 Java tests:  These will tell you IF and which version is installed.
    java -version
    which java
    update-alternatives --list java

As root:
update-alternatives --config java
This will list my newly installed Java -and- the openjdk version. Everytime I try to remove it, it want to install a 1.5 version!! So for now I have both.

  Now we want our system to automatically put the JDK binary files into our PATH when we login for all users. To do this, on openSuSE 13.1, edit the /etc/profile.local file and place the following two lines at the bottom of your file: (Please notice it is a 'local' file.)

      JAVA_HOME=/usr/java/default; export JAVA_HOME
      PATH=$JAVA_HOME/bin:$PATH; export PATH

Step 4: Check the version:

    ctaylor@Tipper-i7:~> java -version
    java version "1.5.0"
    gij (GNU libgcj) version 4.7.2 20130108 [gcc-4_7-branch revision 195012]

Step 5: So the version is still pointing to the old one. We have to use the alternatives here to update the version. The newly installed Java is at this location
    /usr/java/jdk1.7.0_71/ :

As root:
zypper rm icedtea-web
update-alternatives --install "/usr/bin/java" "java" "/usr/java/latest/bin/java" 1
update-alternatives --set java /usr/java/latest/bin/java
For 64-bit architecture:
ln -s /usr/java/latest/jre/lib/amd64/libnpjp2.so /usr/lib64/browser-plugins/
The installation of Java and appropriate links are complete. You can now use Java in any web browser on your system.
    Tipper-i7:/usr/java # java -version
    java version "1.7.0_71"
    Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
    Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

That's it !!!
The JDK Path is: /usr/lib64/jvm/java-1.7.0 And we have the Java Control Panel. Just type "jcontrol" in a terminal window.

Refer:  SDB:Installing_Java  

Alllllrighty now... We went to the Oracle site to Verify our Installation. We got a Congradulations that we had Java Installed (Version 7 Update 71).

   

  The Install(s)

 Final Release - November 19th, 2013  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. As noted above, it has been selected as the 'next' Evergreen release, which means it is going to be supported for a long, long time... in Computer terms. So, we are NOT gona setup a test partition... we are just gona make it what it will be... our New Main System.

  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-4.1.2.3-1.1.x86_64". 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 Tipper-i7 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.11.3-1-desktop
openSuSE 13.1 (Bottle) (x86_64)
KDE Platform Version 4.11.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

 November 4th, 2014 / 2:22am  Rather than have you, or me, jump all over the place for info -and- read possibly bad info below, we are gona direct us to the fix. It is over in our openSuSE 12.3 page at:  VMware Fix   -AND- it involves an interrupt that, in my humble opinion, shouldn't have been enabled for the "General Public" version.

So long, so long we have been fighting this problem. Screen Freezes/Lockups... requiring a PowerOff ReSet. -And- it was only when we had VMware going. We have looked and looked for answers. Contacted nVidia, tried to contact VMware -but- they went from free, back in 1999/2000 to greedy. Now it costs money just to talk to them about an issue. I refuse to pay becuase of 'their' problems.

Well, the 'Lord' finally gave the answer... 'He' implanted the correct search words in our head (and possibly yours, IF you are here because of a search) and we came across a couple of sites that claimed to be able to stop these Random Freezes. The first one talked about things that we had already tried -but- they may be of help to others. It is at: MustBeGeek You can go there at your leisure. However, the Lord's real gift was in this next site, cause they have the fix: ValCo Labs. It involves 'unchecking' the "Accelerate 3D graphics"!!!

This VMware 10 section was created and edited in our openSuSE 13.1 page cause we didn't trust everything... yet. After so long you learn, well you begin to understand that NOT all fixes work. We have lost work many, many times due to this Freeze/Lockup problem. So, since this WebPage was in its infancy, we decided we could 'test' the fix in it. It seems that the Freezes/Lockups were always when we were in Homesite, inside a Windows Variation, inside VMware, inside openSuSE. So to test the 'trend' we are in that path... -and- it is working and NOT breaking. We have even jumped around in the System using it like we had in the past... the further back past. Not sure when they made this '3D Acceleration' a default check of the box -or- when we somehow checked it... -but- it can be, and is, a bear. -And- our latest nVidia card is up there in the performance ratings!! Needless to say, IF you are reading this on our openSuSE 12.3 page it is cause we copied/pasted it there.

 October 25th, 2013 / 8:12am  Ok... more was done and found. Jump over to our:   openSuSE 12.3 VMware Fix for some enlightenment.

   

  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.
Code:
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 2.5.0.1 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.