Notice
The openSUSE Milestone 2 is now available for download.** Link is right here.**
On Fri, 14 Dec 2012 17:46:01 GMT
Romanator <Romanator@no-mx.forums.opensuse.org> wrote:
>
> Notice
>
> The openSUSE Milestone 2 is now available for download.
>
Downloaded the DVD (64-bit) and pleased to see the md5 checksum was OK
this time and that it also fitted onto a DVD.
Installed on a couple of machines - using DVD on this one and USB-stick
on UEFI machine. All seems OK - so far - apart from YAST (Software
Management) still giving error initializing repository “|” - a useful
message!
–
Graham P Davis, Bracknell, Berks.
openSUSE 12.3-M2 (64-bit); KDE 4.9.90; AMD Phenom II X2 550 Processor;
Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306
Installed on a 64 bit system with DVD image on a USB.
Problems seen thus far:
Online updates (in yast) gives an error message about invalid meta data. “zypper patch” does the same, and suggests that the problem is with the update-nonoss repo. Disabling that removes the meta data message. However, there’s another message that update repos are not yet configured.
In KDE, “Configure Desktop”, I attempted to change settings for the login screen. I wanted to disable the user list. It told me that I did not have permission to save the changes. In previous version, I have been prompted for the root password at that stage.
On Fri, 14 Dec 2012 19:35:04 GMT
Graham P Davis <cloddy@no-mx.forums.opensuse.org> wrote:
> Installed on a couple of machines - using DVD on this one and
> USB-stick on UEFI machine. All seems OK - so far - apart from YAST
> (Software Management) still giving error initializing repository “|”
> - a useful message!
Drat! Spoke too soon. LibreOffice is broken. Same fault I had after
updating to 3.6.3 (from 3.5.x) in 12.2. I got it working OK there and
assumed the fault had been fixed but, although versions seem the same,
it’s back. The problem is in Calc, where graphs vanish when one clicks
on them. Not only does the graph go blank but right-clicking on them
shows there is no data.
OK, back to 12.2 to see whether it’s still working or is also broken
there.
–
Graham P Davis, Bracknell, Berks.
openSUSE 12.3-M2 (64-bit); KDE 4.9.90; AMD Phenom II X2 550 Processor;
Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306
On 12/14/2012 02:56 PM, nrickert wrote:
>
> Installed on a 64 bit system with DVD image on a USB.
>
> Problems seen thus far:
>
> Online updates (in yast) gives an error message about invalid meta
> data. “zypper patch” does the same, and suggests that the problem is
> with the update-nonoss repo. Disabling that removes the meta data
> message. However, there’s another message that update repos are not yet
> configured.
During the MS, Beta, and RC phase, the update repos are not available.
The openSUSE greeter still points to openSUSE 11.3 and KDE 4.4.
I’ve submitted a bugzilla report for 12.1 and it’s still outstanding in openSUSE 12.3 Milestone 2.
Ok. We brought this down, installed it and screwed up our System!! We have a three partition set up. Windows Media Center, openSuSE 12.2 and openSuSE 12.3. Well, the third one is supposed to be for 12.3. It was still setup as 12.2 from our 12.2 testing days. Anywho, we tried to do a “zypper dup” from our DVD copy. After we got the commands straight to do it from the drive, we fired it off. When it finished, it had over written our MBR.!! So, right off the bat we are NOT happy. Had to use SuperGrub2 to get ourselves straightened out. Try it, you’ll like it.
We installed M2, as mentioned above, using zypper and then had to repair our system. We tried fixing it via the Yast controls but they did not. We searched the forums and found info from caf4926 discussions that eventually fixed our problem.
grub2-install /dev/sda Installation finished. No error reported.
After re-booting we found that it worked. We are not only back to our “normal” system, we also have the new openSuSE 12.3 as one of our selections in the initial boot. This Grub2 can be frustrating -but- it does have its rewards. Well this was unusual. As mentioned above, we “updated” a 12.2 version to 12.3 and to our surprize VMware is working!! nVidia didn’t carry over cause we got that “Direct Rendering” message again -and- our display is shifted to the Left by about a 1/4 inch. However, as we experienced once before, the nouveau driver works better when it gets loaded by an Update -after- nVidia has been installed. We’ll see IF the nVidia driver that we have will work with this verson of openSuSE.
Initially, we have the following System setup.
OS Information
OS: Linux 3.6.3-1-desktop x86_64
Current user: ctaylor@dusty-tr2.TRComputing
System: openSUSE 12.3 Milestone 2 (x86_64)
KDE: 4.9.90
Display Info
Vendor: nVidia Corporation
Model: GeForce 7300 LE
2D driver: nv
3D driver: Unknown Gallium (9.0)
Ok now. we have the nVidia driver installed.
Display Info
Vendor: nVidia Corporation
Model: GeForce 7300 LE
2D driver: nvidia
3D driver: NVIDIA 304.64
-And- copying the above Display Info from the Computer screen, and then pasting it in my
WebPage, presented some problems. The “fix” seemed to come -after- we exited the Computer
Display Screen.
So, things did not get moved over smoothly. However, at this point in time we have not had any Freezes. The nVidia driver requires “nomodeset”. Otherwise you will have conflicts… well we did.
-Annnddd- the time is wrong. Don’t know what was done in these last couple of openSuSE versions
-but- they don’t set the time correctly on the initial install. Ok. We checked and the ‘adjtime’ file was there -but- it had ‘UTC’ on the last line instead of ‘LOCAL’. We changed it but the time is still wrong. We will do our usual and re-boot to see what happens.
Ok. After re-boot we have the correct time.
That’s all for now,
I did a fresh install of 12.3 milestone 2 on a ThinkPad X-41 - default KDE setup - from the DVD iso on a USB stick. The install went OK.
In getting samba to connect to the network, I went to the Yast firewall configuration tool, and got the following warning:
http://farm9.staticflickr.com/8200/8274153162_36aef63014_m.jpg
I have never seen this in a previous version, including 12.3 milestone 1. It is not mentioned in the release notes. If you press the continue button, Yast shows the firewall is not running.
What is this other firewall? I cannot find anything.
Thanks,
Howard
Never mind. After a reboot, the firewall is behaving properly, and samba is connecting.
Thanks,
Howard
Did you go to the ‘Booting’ heading in the summary? I always tend to do that.
Let it be said though, I have no hesitation installing to the MBR (some folks have phobia about this)
And I tend to mark it up this way: https://dl.dropbox.com/u/10573557/Grub2_Project/C1.png
So far, I never had trouble.
Nope. Didn’t see that. We just did “zypper dup --from dvd:///?devices=/dev/sr0” and let 'er rip. Like we said in the previous report there was an installation of openSuSE 12.2 already on the Partition. We were just expecting it to be “Updated/Replaced”. Did not expect it to write to the MBR. That particular 12.2 version was NOT booting from the MBR. It was one of the choices from our “Main System” which is also a 12.2 version. Guess the default is to write the MBR even though you are only updating. Will have to pay closer attention next time. -But- it was a fun afternoon… chasing computer woh’s that turned out to be nothing more than some err’s in settings. Thanks caf for your info in the forum.
Chuck
On Sat, 15 Dec 2012 06:06:01 GMT
caf4926 <caf4926@no-mx.forums.opensuse.org> wrote:
>
> chucktr;2510930 Wrote:
> >
> > We installed M2, as
> > mentioned above, using zypper and then had to repair our system. We
> > tried fixing it via the Yast controls but they did not. We searched
> > the forums and found info from caf4926 discussions that eventually
> > fixed our problem.
> >
> >
> > # grub2-install /dev/sda Installation finished. No error reported.
> > After re-booting we found that it worked. We are not only back to
> > our “normal” system, we also have the new openSuSE 12.3 as one of
> > our selections in the initial boot. This -Grub2- can be
> > frustrating -but- it does have its rewards. Well this was unusual.
> > As mentioned above, we “updated” a 12.2 version to 12.3 and to our
> > surprize VMware is
> > working!! nVidia didn’t carry over cause we got that “Direct
> > Rendering” message again -and- our display
> > is shifted to the Left by about a 1/4 inch. However, as we
> > experienced once before, the nouveau driver works better when it
> > gets loaded by an Update -after- nVidia has
> > been installed. We’ll see IF the nVidia
> > driver that we have will work with this
> > verson of openSuSE.
> >
> >
>
> Did you go to the ‘Booting’ heading in the summary? I always tend to
> do that.
>
> Let it be said though, I have no hesitation installing to the MBR
> (some folks have phobia about this)
> And I tend to mark it up this way:
> https://dl.dropbox.com/u/10573557/Grub2_Project/C1.png
> So far, I never had trouble.
>
>
Trouble I have is that I sometimes forget that installing from DVD and
USB-stick can make the default MBR location change. On this machine, for
instance, the default of /dev/sda can be the first disk of a set of
raid disks or the installation USB-stick. Can upset things a bit. 
–
Graham P Davis, Bracknell, Berks.
openSUSE 12.3-M2 (64-bit); KDE 4.9.90; AMD Phenom II X2 550 Processor;
Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306
Does anyone experience a 15/20 second delay when starting kde once the screen comes up and finishes loading?
I have had that one 12.1 and 12.2 (final versions). Though I have not tested 12.3 enough yet to notice if it remains there. It seems to go away once I remove kmix.
This worked properly with a different user. So it is probably something in user kde settings, perhaps an incompatibility with old settings from 12.2.
I had problems installing with encrypted “/home”, though it did install.
Most of the install dialog went fine. When I clicked the button to complete the install (after software selection), there was an error message about a failure mounting “/home”. A prompt asked whether to continue. I told it to continue, and the install phase completed otherwise normally.
On reboot, I chose to instead reboot my 12.2 system (on the same computer), and inspect what had been done for the new install.
There was no entry for “/home” in “/etc/fstab” of the M2 installation.
There was no entry for “/home” in “/etc/crypttab” of the M2 installation.
I edited those two files, adding the needed entries. I then rebooted to the newly installed system. The final stages of install (those that normally follow the reboot) went fine.
I had trouble installing the Milestone 2. The first part of the installation went fine, but after the first restart there is a delay in booting and the I get presented the normal login screen instead of the second part of the installation, that means all the configuration steps are skipped. I tried this three times, second and third with nomodeset and nokms, but that didn’t help.
So I had to configure user, network, audio, repositories … manually. After this configuration and at least two more reboots the system works.
The good news is, that I can use an encrypted /home-partition again, and some strange power management effects are gone.
One program that doesn’t work ATM is realcrypt. It complains that it can’t create a loop device.
But that might be due to the fact, that I got it from Packman/openSUSE_Factory (?).
Downloaded, burned to DVD, and ran the live KDE 32-bit M2. Then installed to a (non-VM) partition on my only HDD. Install process went fine until bootloader being written (to root, SDA5), then crapped out with message:
*Kernel image: /boot/vmlinuz-3.6.3-1-default
Initrd image: /boot/initrd-3.6.3-1-default
KMS drivers: i915
Root device: /dev/disk/by-id/ata-Hitachi_HDS723020BLA642_MN1220F30K3NZD-part5 (/dev/sda5) (mounted on / as ext4)
Kernel Modules: hwmon thermal_sys thermal processor fan rtc-cmos scsi_dh scsi_dh_alua scsi_dh_rdac scsi_dh_emc scsi_dh_hp_sw video i2c-core button i2c-algo-bit drm drm_kms_helper i915 libata pata_sis pata_piccolo pata_isapnp pata_pdc202xx_old pata_marvell pata_atiixp pata_oldpiix pata_cs5530 pata_ns87415 pata_ali pata_cmd640 pata_mpiix pata_legacy ata_generic pata_cs5520 pata_serverworks sata_svw pata_hpt366 pata_efar sata_via sata_sx4 pata_via sata_sil pdc_adma pata_opti pata_pdc2027x pata_it8213 pata_ninja32 sata_sis sata_qstor pata_sl82c105 pata_arasan_cf pata_rz1000 sata_nv pata_sil680 pata_cs5536 pata_cypress pata_ns87410 sata_inic162x pata_cmd64x pata_hpt37x sata_uli sata_mv pata_cs5535 libahci pata_artop pcmcia_core pcmcia pata_pcmcia pata_rdc pata_hpt3x2n sata_vsc ahci_platform sata_promise pata_netcell pata_acpi sata_sil24 pata_triflex pata_jmicron acard-ahci pata_hpt3x3 pata_radisys pata_it821x ata_piix ahci pata_sch pata_sc1200 pata_amd pata_optidma pata_atp867x usb-common usbcore ohci-hcd uhci-hcd ehci-hcd xhci-hcd hid usbhid hid-logitech-dj hid-generic
Features: acpi kms plymouth block usb resume.userspace resume.kernel
Perl-Bootloader: 2012-12-15 18:54:57 <3> pbl-6276.2 Core::RunCommand.1642: Error: Command ‘/usr/sbin/grub2-install --force --skip-fs-probe “(hd0,5)” >/var/log/YaST2/y2log_bootloader 2>&1’ failed with code 256 and output: /usr/sbin/grub2-bios-setup: error: no such partition.
*
There was an error generating the initrd (1)
Used “try again” button, same message. On reboot, Grub hung without message/prompt, there was nothing in the PBR. So I rebooted using live DVD to desktop then, in a super-terminal did:
*1. mount /dev/sda5 /mnt
2. grub2-install --force --root-directory=/mnt /dev/sda5
*
Then rebooted, grub and the boot loader/grubworked, and it went through its first-boot/setup phase and thence to the desktop. All fine since.
BTW, Patience is totally broken. Even uninstalled and reinstalled it, no change. Also, the login screen looks weird if the screen resolution is changed from nativei.e., huge size of applet, huge fonts (yes, I changed in admin, no diff/change), split 3 ways, etc.
Report bugs my good sir! The developers need to know or it shall not be fixed. 
That was with encrypted “/home”.
When I later tried installing in an encrypted LVM, the error message told me that formatting the root partition failed. I still managed to install, by getting to a command line to fix things, then continuing.
Since both failures seem to be crypto-related, I have reported both as Bug 794692