Installed it with no problems. No trouble with mid-install reboot that
occurred with 12.1.
After install:
Wireless worked OK after configuration.
Sound worked - almost. I had none with M1 but now getting sound from
Flash. Attention sounds seem to be missing although I keep getting a
“POP!” every so often that sounds as though something is trying to grab
my attention. No idea what it is.
Gnucash 2.4.10 appears to be functioning OK.
Gwenview is still failing on some jpegs. I’ll update the bug report on
that. Not an M2 problem but KDE 4.8.
No Kompozer available.
So far so quite good.
–
Graham Davis, Bracknell, Berks.
openSUSE 12.2 M2 (64-bit); KDE 4.8.1; AMD Phenom II X2 550 Processor;
Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306
The once in a while beep we think might be telling you that you have mail?? Change the mail sound and see what happens - or not. Anyway, we didn’t do much with 12.2 m1 but plan on testing out this milestone 2. We are interested in a fix for the cursor freezes, hesitations, delays -or- whatever you want to call them that we are experiencing here in 12.1. Also had a couple of system freezes that required an absolute Power Off Reset. Now this was with 12.1 -not- 12.2 … yet. It will be one of the items of interest.
Download finished now must create DVD and install… back to ya later.
Chuck
On 19/03/12 16:36, chucktr wrote:
>
> Hi Cloddy, Perhaps the sound problem the same or similar to the one
> experienced in 12.1. Please refer to Lord_Emsworth in forum message:
> http://tinyurl.com/6vwfplg
Yes, the sound problem is a 4.8 bug/feature. Thanks for the tip; just
finished editing all my notification settings. Phew!
> The once in a while beep we think might be telling you that you have
> mail?? Change the mail sound and see what happens - or not.
Thanks, I’ll look into that.
I recall that one used to be able to test a sound before applying to
System Settings but that no longer appears to be available.
*
–
Graham Davis, Bracknell, Berks.
openSUSE 12.2 M2 (64-bit); KDE 4.8.1; AMD Phenom II X2 550 Processor;
Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306
*
NET install on latest VirtualBox on Windows 7 x64. Accept everything as default except xfce instead of KDE. After two hours it finished installation and successfully booted into xfce DE.
Yesterday I had tried both DVD and KDE-LiveCD x64 on VB and VMWare, both were stumbled at the GRUB2 stage. I know reverting to GRUB will work. Just curious how Cloddy installed his/her M2.
Generally impressed. Have issue shutting down. Have to uncheck “Save session for future logins” to successfully power down, or “shutdown -P now”, but then the vbox screen resolution setting will be lost.
Install emacs. It defaults to emacs-nox, that’s fine. Terminal mode rocks. Have to run as su first to get emacs work properly. After that normal user will work.
Doing zypper dup. emacs-x11 is installed. “emacs -nw” to launch in Terminal mode. Launched. Crashed. Both su or normal user. Have to right-click on the panel icon to close the terminal. Remove emacs. Both emacs-nox and emacs-x11 are removed. Install again. emacs-nox is installed. Work again. Have to su first, then normal user will do. Can I say it’s a bug? or glitch? mn or feature?
x86_64 M2 xfce on VirtualBox 4.1.10 running on Windows 7 Professional x64.
By your sugnature I assume you are running the kde desktop. If so then zypper in mesa. I don’t know why but mesa seems to be missing in the kde desktop.
More on the grub2 failure. I hope this will help others.
First install: from live KDE 32 bit. Had a grub2 failure. I don’t recall the error messages.
2nd install: from the 32bit DVD, on the same computer (to overwrite the prior install). I had a grub2 failure. This is an install on an alternate partition. The grub2 install defaulted to installing on the external partition (“/dev/sda4”). I let it go with the default, and that failed. The error message said something about sda4 not mapped to a device. The failover to grub1 was smooth.
3rd install, from the 64bit DVD, on a different computer, also an alternate partition. The grub2 install defaulted to installing on the external partition (“/dev/sda4”). Since I didn’t expect that to work, based on earlier experience, I instead selected “install on /boot” (which was /dev/sda6).
The grub2 install went without a hitch. But, on the reboot to complete the install, I got a “grub>” prompt. I booted the install DVD (actually on a USB) to rescue mode, and ran “fdisk”. The installer had set the extended partition (“/dev/sda4”) ad the active partition. I fixed that, returning to the active partition previously used. A reboot then got me into the grub1 menu for 12.1, from which I could select the entry to boot from “/dev/sda6”. And all went well. The “grub>” prompt that I had seen at first probably came from an earlier install that had used the extended partition to boot, but was no longer valid.
My guess is that the grub2 install will work fine for installing on MBR or on a standard primary partition. But it is a bit broken for installing elsewhere. I’ll probably report this to the bugzilla later today or tomorrow.
Well I have installed openSUSE 12.2 M2 into VirtualBox using the DVD and the default KDE install. It boots up fine, but did not seem to include any VirtualBox drivers as M1 did but I was able to install the latest drivers. I noticed that we now are using Grub2 and there is no graphic OS selection menu as in grub legacy and not impressed with that look right now. openSUSE 12.2 does look nice once loaded with very good artwork up front unlike openSUSE 12.1 which did not come until the end of the process. As noted, the KDE desktop is silent due to a KDE bug which I have read to be fixed in KDE 4.8.2 and openSUSE 12.2 includes KDE 4.8.1 right now. I see that the kernel version is 3.3-rc6 even though rc7 is out. We will without a doubt end up will the final of kernel 3.3 in openSUSE 12.2 it would seem. I do wonder what new procedure will be required to compile a new kernel and have it added to the grub2 menu for us? The YaST Boot section is less than helpful using grub2 I see and I do hope that will change in the final release. Over all though, openSUSE 12.2 is working very well and using it right now. I noticed that once again, the /etc/init.d/after.local file does not run, but my blog on the subject still works just fine in getting the after.local file working on startup.
One thing is for sure and that is for openSUSE 12.2 M2, its looking mighty good to me and well on its way to a really good release I would say.
I booted my Sandbox PC to the 32-bit openSUSE-12.2 M2 KDE live cd with the boot code ‘nomodeset’. It booted ok. Wired ethernet/internet worked. Sound worked on one of my sound systems (I did not test the other). I note when I selected a reboot of the PC, it took me to a login prompt. But it was late in the PM, and maybe I made the wrong selection. So I opened a konsole, typed ‘shutdown -r now’ and the restart worked. When I have M2 installed on this same PC I’ll look at this deeper. (Sandbox is an ancient athlon-1100 CPU on an MSI KT3 ultra motherboard, with 2GB RAM, and an AGP nVidia FX5200 graphic card).
I plan to install M2 to this PC later in the week, so I’ll report on that later.
I did note that only the 32-bit openSUSE-12.2 M2 KDE liveCD iso would fit on a CD. The 64-bit openSUSE-12.2 M2 KDE liveCD iso required a DVD as did the 32-bit openSUSE-12.2 M2 Gnome liveCD iso . Although burned (to a DVD) I have not yet tried out the 64-bit openSUSE-12.2 M2 KDE liveCD nor the 32-bit openSUSE-12.2 M2 Gnome liveCD. Work is quite busy for me now (with long hours) and my test time limited.
I noticed last night that telling KDE to restart or shutdown just log’s you out of the desktop. You can do a restart or shutdown from the SUSE login, but not from within KDE. Did anyone notice that problem?
Yes I had the same KDE restart and shutdown problem but the shutdown command in a console works.
Installation is on PC1 from 64 bit DVD and went smoothly (fresh install, but kept /home from M1) . The grub2 (1.99 actually) worked straight away but as noted above, doesn’t look too nice at the moment.
On 20/03/12 11:06, jdmcdaniel3 wrote:
> I noticed last night that telling KDE to restart or shutdown just log’s
> you out of the desktop. You can do a restart or shutdown from the SUSE
> login, but not from within KDE. Did anyone notice that problem?
Only tried “restart” once so far but it worked for me. [M2 installed
from 64-bit DVD.]
–
Graham Davis, Bracknell, Berks.
openSUSE 12.2 M2 (64-bit); KDE 4.8.1; AMD Phenom II X2 550 Processor;
Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306
Just tried to set up my scanner (Epson Perfection 4870 Photo) but I get
the following message in Yast:
“No scanner was detected and no active scanner or driver exists.”
–
Graham Davis, Bracknell, Berks.
openSUSE 12.2 M2 (64-bit); KDE 4.8.1; AMD Phenom II X2 550 Processor;
Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306
Installed in Vbox, from KDE LiveCD. GRUB2 fails, reports file not found: /usr/sbin/grub2-install. Checked the ISO, md5sum is OK. Switching to GRUB confirmed working.
On 03/20/2012 06:06 AM, jdmcdaniel3 wrote:
>
> I noticed last night that telling KDE to restart or shutdown just log’s
> you out of the desktop. You can do a restart or shutdown from the SUSE
> login, but not from within KDE. Did anyone notice that problem?
Thanks Larry for your confirmation on this issue (as well as from others here). While the problem is in the KDE Desktop on exit, KDE 4.8.1 has no such problem loaded into openSUSE 12.1, so one would wonder just from where this bug came in from?