11.3 milestone-7 intial look on various PCs

English Install/Boot/Login
1

I tested various PCs with 11.3 Milestone-7 build-0625. The experience in many respects was similar to that of Milestone-6, although I did encounter a new 64-bit bug with firefox. All the tests below were done with liveCDs.
**
64-bit liveCD Experience:**

  -  PC#1: booted with openSUSE-11.3 64-bit M6 KDE4 liveCD on my 64-bit Intel Core i7 920 w/6GB (Asus P6T Deluxe V2 motherboard) w/ PCI-e nVidia GeForce GTX260 graphics. PC booted using the Noveau graphic driver at maximum expected resolution (1920x1200). As expected, special desktop effects does not work with Noveau driver.
  Sound works. Wired Internet works.  But Firefox immediately crashes when run, forcing me to use Konqueror as the web browser.
  .
  -  PC#2: booted with openSUSE-11.3 64-bit M6 KDE4 liveCD on my 64-bit Dell Studio 1537, Intel P8400 w/4GB, w/ATI Radeon 3450HD graphics . Sound just worked. Graphics booted with the Radeon open source driver (as evident in the /var/log/Xorg.0.log file) at maximum expected resolution (1440x900). The graphics came up with special desktop effects and was impressive. I had seen this behaviour before in M4 to M6.

  Setting up the wireless Network on this laptop in 11.3 M6 was finicky.  I disabled kwallet, but there were still problems.  I tried using knetwork manager to setup our wireless but it did not work. I did set it to automatically connect. Then I killed knetwork manager, and then restarted knetwork manager, and I then I had a wireless connection. A nice solid connection at that.  I could not get knetwork manager to work without this convoluted scheme.  There were bug reports on 11.3 M6 on this (with work arounds) and I did not try those.

  Wireless on this laptop is an Intel Wireless 5300 AGN and once it is finally connected, its connection is far superior (IMHO) to previous openSUSE versions.

   Again Firefox immediately crashes when run, forcing me to use Konqueror as the web browser.

32-bit liveCD Experience:

  -  PC#3: booted with openSUSE-11.3 M7 32-bit KDE4 liveCD on my 32-bit AMD Athlon-2800 w/2GB (Asus A7N8X Deluxe motherboard) w/ PCI nVidia GeForce 8400GS graphics. Behaviour identical to what I saw on M6.  PC booted using the Noveau graphic driver at maximum expected resolution (1920x1200). Sound worked. Wired internet worked. As anticipated, special desktop effects with the Noveau driver did not work on this hardware.
  .
  -  PC#4: I have not tested this yet. This is my wifes 32-bit AMD Sempon-2600 w/1GB (Epox EP-8K7A motherboard) w/AGP ATI RV280 (Radeon-9200Pro) graphics, but I don't have access yet.  It worked okay on 11.3 M6 so I have high hopes for M7
 .
  -  PC#5: this is my sandbox PC, an old 32-bit AMD Athlon-1100 w/1GB (MSI KT3 Ultra motherboard) w/AGP nVidia GeForce FX5200 graphics and it had the same hiccups with M7 that I saw previous on M6 with the 32-bit openSUSE-11.3 KDE4 liveCD. It would not boot in any of the 800x600, 10247x768 nor vesa mode, each time hanging up when trying to run X (presumably the nouveau driver failing ? ) .   I then booted to safe Settings, only to watch that 'hang' after a clock setting (same behaviour as M6):

[39.456766] rtc0: alrms up to one day, 114 bytes nvram

and as per M6 by pressing < ctrl-c> it restarted / continued its boot and eventually booted to X at a low 1024x768 resolution. That turned out to be the nv graphic driver. Fonts were bad on this boot (but not as bad as I rememberd M6). Sound did NOT initially work (unlike M6) and what was interesting was it put my USB webcam (which has only a mic) as default. But sound is not an issue as I can retune this in YaST and this PC has multiple sound cards which is difficult for any automatic configuration program to figure out. Wired Internet worked.
.
I plan to install M7 on this PC later (possibly this weekend).
.

  • PC#6 - This is my 32-bit Fujitsu-Simens Amilo 7400M laptop w/1.256 GB w/Intel 1.5 celeron, and Intel i855 GM graphics. The i855GM causes MAJOR problems for all Linux versions with newer kernels, and thus far 11.3 milestone is no different - it has problems.

This laptop is currently running openSUSE-11.1 with KDE-4.3.5. Running quite nicely I might add. I previously tested it with openSUSE-11.2 and the Intel driver did NOT like the 2.6.31 kernel in 11.2 , requiring the boot code acpi=OFF.

I tried with openSUSE-11.3 M6 and obtained similar (albeith slightly worse) behaviour. M7 is worse than M6, in that thus far I can get it to boot to run level 3 but NOT run level 5. The “acpi=off” method does not work for me thus far in M7. In fact, thus far I can NOT get X to start. I suspect it may be possible if I install sax2 on this PC and try to configure the FBDEV or VESA driver.

I previous documented my efforts with M4 and M6 here: https://bugzilla.novell.com/show_bug.cgi?id=593463 . I’ll have to add an entry for M7.

Research has indicated that ever since the 2.6.29 kernel (or so) the kernel has an interference with the Intel graphic driver (or visa versa dependent on one’s perspective). A fix may have been found, and I tested a Ubuntu version with the 2.6.32 and a patch that worked. Still, I note this is NOT an openSUSE unique problem. https://bugs.freedesktop.org/show_bug.cgi?id=24789

**Summary
**
Thus far, for my newer PCs, 11.3 M7 is positive. For my older PCs, it has problems due to

  • nouveau driver does NOT like my older nVidia hardware
  • kernel still does NOT like my older Intel i855GM graphics

11.3 Predictions

Based on this (and with my still having one PC left to test) I predict that for 11.3 GM in July (unless there are major changes between now and then) we will see:

  • ATI/radeon users with legacy hardware noting this 11.3 release is superior to 11.2 and overall a better release (albeit not perfect).
  • nVidia users with old hardware may be very upset, as the nouveau driver does not work well for them, and these users will be forced to boot in safe settings/fail safe, until they can configure the “nv” or “vesa” drivers better, and until they can install the proprietary nVidia driver (where I note there is NOT yet a proprietary legacy nVidia driver yet for the 2.6.34 kernel).
  • nVidia users with relatively moderate-to-new graphic hardware will be ok with the nouveau graphic driver.
  • Intel drivers will be a mixed lot. Those with the newer Intel hardware (that comes with i3 and i5) will be happier, as that hardware does NOT work well on 11.2. But users of older Intel graphics (such as in my Intel i855 GM) will continue to be dissatisfied.

Hence like all releases before, I predict 11.3 will get mixed reviews.

2

Although I upgraded with zypper from M6, I got the same 64bit Firefox bug and was forced to use Konqueror.

Good news is that at least the “unichrome” driver installed with no xorg.conf to support my (old) VIA graphics chip, with DR enabled, as it did with M6. Haven’t tried XvMC for video yet.

Both “openchrome” and “chrome9” drivers failed loading by X system at startup, with same driver releases as M6 only available from OBS . Not surprising, and seems to be BAU with Milestones.

Akonadi reported some errors on KDE startup. Have seen similar with Kubuntu 10.04, although I didn’t see any problems as a result of that. However on 11.3 M7, KDE’s Kontact application fails to complete its startup and fails after invoking Akonadi which delivers DBUS and database errors. The errors are reported in a very long listing when Kontact is started from the commandline.

Did you try Kontact? (IIRC you don’t use Kmail, so possibly not). :\

3

I installed 11.3 M7 on this PC, but it was not easy. I suspect new users if they had identical hardware would be lost, and likely would do unkind things to any openSUSE-11.3 liveCD they procured.

As before (with M6) I could only install with SafeSettings. Previous 1024x768, 800x600, VESA and text mode installs all failed. After a successful safe settings install, the PC would boot ONLY to fail safe. Eventually I found it possible to get it do a normal boot to change this line in the /boot/grub/menu.lst (for the regular boot) :

kernel /boot/vmlinuz-2.6.34-8-default root=/dev/disk/by-id/ata-ST3320620A_9QFAJR66-part6 apm=off acpi=off mce=off barrier=off ide=nodma idewait=50 i8042.nomux psmouse.proto=bare irqpoll pci=nommconf resume=/dev/disk/by-id/ata-ST3320620A_9QFAJR66-part3 splash=silent quiet showopts vga=0x317

to this line:

kernel /boot/vmlinuz-2.6.34-8-default root=/dev/disk/by-id/ata-ST3320620A_9QFAJR66-part6 resume=/dev/disk/by-id/ata-ST3320620A_9QFAJR66-part3 splash=silent quiet showopts vga=0x317 nomodeset

The regular boot had many extra codes (because this was a safe settings install) that would normally not be there. These many extra codes made it impossible to boot the PC to X, as one was always greeted with a black screen. It turns out as a minimum, the “nomodeset” boot code was needed, and there was a note in the 11.3 M7 release notes about that. Of course, HOW MANY new or beginner users read the release notes ?? Not many is the opinion I venture.

And I had to remove all the other needless boot codes from the menu.lst. At that point, it would boot as a normal boot.

So the PC could now boot to ONLY 1024x768 in a normal boot. But the graphic driver chosen (as a result of the “nomodeset” ) was the “nv” driver. The proper resolution for the “nv” driver is 1900x1200 with this graphic card/monitor combination. The 1024x768 is pathetic in comparison. In the past (on previous openSUSE versions) the “nv” driver supported that 1920x1200 resolution. So it IS possible. I also noted xrandr only gives options of LOWER resolutions. No option to select 1920x1200 (nor indeed any resolution higher than 1024x768). So I went to run the sax2 application to configure an xorg.conf to setup the higher resolution , and guess what ??

No sax2 application in 11.3 M7 !! Its been removed. Its gone. Its not on the DVD. Its not on the factory-snapshot repository. Its gone ! Its been removed. Only sax2-tools is left, and it is NOT adequate. IMHO unless there is a replacement configuration tool (that works) that complete removal of sax2 is a seriously bad move if it was done deliberately.

Now if one searches for sax2 in factory from here: Software.openSUSE.org one will find it. But how many new users know about that?

How is a user, who does not know of Software.openSUSE.org, and who does not want to use the proprietary nVidia driver (which by the way is NOT ready yet for the 2.6.34 kernel with this GeForce FX5200 nVidia hardware), supposed to configure their graphics beyond 1024x768 ??

Unless they are an xorg.conf hacker, they can’t. The possibility is gone. And so will this user. They WILL BE GONE. GONE away from openSUSE to a distribution that DOES provide a wizard for configuring the graphics when the automatic xorg config fails.

So, how to lose openSUSE users and make openSUSE detractors? This is how !

I’m not impressed. I am disappointed.

Of course this won’t stop me. I can grab sax2 by searching here: Software.openSUSE.org , … I can easily install the proprietary video driver, and hopefully the “hack” (and it was a hack) that I used to boot X from run level 3 with the proprietary graphic driver will work.

And I will point new users here: Software.openSUSE.org, to get sax2. But that should NOT be necessary.

So I am very disappointed, and unless I am wrong (which is possible and it won’t be the 1st time), and unless this deficiency is addressed, I predict many users of old nVidia hardware will storm way from openSUSE in droves, much like happened with openSUSE-10.1 with the software package management was bad. This is from my view a SERIOUS mistake.

IMHO it IS premature to drop sax2 completely without a replacement - the xorg automatic configuration is not there yet in terms of reliability.

4

No, I use thunderbird for mail. And I am only testing LXDE on my sandbox PC installs.

5

On 23/05/10 09:46, oldcpu wrote:
> - ATI/radeon users with legacy hardware noting this 11.3 release is
> superior to 11.2 and overall a better release (albeit not perfect).

I would have agreed with you at M6 but certainly not M7 on the evidence
of a clean install on my Radeon HD 2400 Pro. I installed from DVD and on
the preliminary boot, graphics looked OK. Firefox and Sea Monkey were
broken but you expect a few hiccups. I rebooted and then found graphics
was broken at the logon screen stage - just a snowy screen with a square
of slightly different-coloured snow marking the location of the mouse
cursor.

On another partition, I’ve updated gradually from M6 to M7 via Factory
and had no problems with graphics and Firefox doesn’t crash. However,
I’m now having to set up my wireless connection every time I boot the
system.

Now to see if my nVidia machine makes a better fist of it. Couldn’t do
worse - could it?

–
Graham P Davis, Bracknell, Berks., UK.
E-mail: newsman AT scarlet HYPHEN jade DOT com

6

You didn’t say whether 64bit or 32bit?

So far only reports of this Firefox problem have come from 64bit systems.

7

32 bit dup from M6 > M7

Only bug I have so far is Evince, it crashes out.

Otherwise it’s solid. I don’t have the issues reported here like FFox…

I have added the factory repos for kde and gnome though as well as Packman.

8

On 23/05/10 14:37, Graham P Davis wrote:
> Now to see if my nVidia machine makes a better fist of it. Couldn’t do
> worse - could it?

Graphics OK, so that’s an improvement but the sound is almost
non-existent. It’s found two cards so I’ve got to check which one it’s
[mis-]using and compare with 11.2 - as that works fine.

–
Graham P Davis, Bracknell, Berks., UK.
E-mail: newsman AT scarlet HYPHEN jade DOT com

9

To get Firefox working in Milestone 7. First, make a backup copy of .mozilla from either openSUSE 11.2 or openSUSE 11.3 Milestone 6.

Save it to usb drive or to another partition. Copy it back to your Milestone 7 home directory. Firefox will restart.

Good Luck!

Romanator

10

Further to this, on this sandbox PC of mine (an old 32-bit AMD Athlon-1100 w/1GB (MSI KT3 Ultra motherboard) w/AGP nVidia GeForce FX5200 graphics) I took a look in more detail at Software.openSUSE.org to see if I could get sax2 and I did not like what I saw. So I decided to stop wasting my time on the “nv” driver, and I went ahead and installed the proprietary nVidia legacy 173.14.25 graphic driver “the hardway” (which is not hard). In doing this I booted to run level 3 without the “nomodeset” boot code. After running the proprietary driver “.run” file, I built the custom xorg.conf with the proprietary “nvidia-xconfig” tool. Restarted to run level-3, and then booted with “startx – -ignoreABI”. Since the 173.14.25 graphic driver is not yet ready for the 2.6.34 kernel ( ? ) , experience with earlier 11.3 milestone releases taught me this was necessary.

For some reason, this proprietary graphic driver install messes permissions on audio, and hence I had to add regular users to group audio to get sound functioning for regular users. (after which a complete log out of Linux was necessary for settings to be applied)

But once that was complete, I had 1920x1200 graphics, with sound, functioning. I changed the /boot/grub/menu.lst file, replacing “nomodeset” with “3”.

I forgot to mention - I setup LXDE as the desktop. It works well.
**
So 11.3 M7 is running well**, and that did not take me long, but I seriously doubt that a distro hopper, nor a new user, would be able to quickly do the above like I managed.

11

Are you referring to the Firefox startup failure discussed in the thread here - from post #9??

If so, I tried your suggestion above, by copying .mozilla from my 11.2, but it made no difference to the problem described in that thread.

12

What did you do to recover from this ? With no sax2 it is difficult to force fbdev or vesa driver (other than copy the /etc/X11/xorg.conf.install to /etc/X11/xorg.conf). Did you apply the “nomodeset” boot code at the grub boot splash menu?

13

On 23/05/10 17:06, oldcpu wrote:
>
> Cloddy;2168153 Wrote:
>> I would have agreed with you at M6 but certainly not M7 on the evidence
>> of a clean install on my Radeon HD 2400 Pro. I installed from DVD and on
>> the preliminary boot, graphics looked OK. … I rebooted and then
>> found graphics was broken at the logon screen stage - just a snowy
>> screen with a square of slightly different-coloured snow marking the
>> location of the mouse cursor.
> What did you do to recover from this ? With no sax2 it is difficult to
> force fbdev or vesa driver (other than copy the
> /etc/X11/xorg.conf.install to /etc/X11/xorg.conf). Did you apply the
> “nomodeset” boot code at the grub boot splash menu?
>
>

I logged on OK in “safe” mode but only to check that radeonHD was
installed. Got the same symptoms in M6 when I thought that I didn’t need
radeonHD and so removed it, thereby finding out that it was needed
though not used in anger.

–
Graham P Davis, Bracknell, Berks., UK.
E-mail: newsman AT scarlet HYPHEN jade DOT com

14

So if I understand this correctly, the radeon driver did not automatically work on the 1st boot, and instead the radeonhd driver was loaded, where the radeonhd driver does not work well.

I take it then you did not try to rename the /etc/X11/Xorg.conf.install file to /etc/X11/xorg.conf (to load the vesa or fbdev driver as an interim, to support investigations) so as to get a desktop.

Did you examine the /boot/grub/menu.lst file to see if there were any inappropriate boot codes before the showopts flag in that file ?

My impression is your assessment was you unfortunately were not able to troubleshoot and contribute to the bug solving process (so as to help the developers and packagers get this problem you encountered fixed for your hardware) and hence you simply removed openSUSE 11.3 M7.

… Is that assessment of openSUSE 11.3 M7 being now removed from your PC correct?

15

On 23/05/10 20:06, oldcpu wrote:
>
> Cloddy;2168262 Wrote:
>> I logged on OK in “safe” mode but only to check that radeonHD was
>> installed. Got the same symptoms in M6 when I thought that I didn’t
>> need
>> radeonHD and so removed it, thereby finding out that it was needed
>> though not used in anger.
> So if I understand this correctly, the radeon driver did not
> automatically work on the 1st boot, and instead the radeonhd driver was
> loaded, where the radeonhd driver does not work well.
>
> I take it then you did not try to rename the /etc/X11/Xorg.conf.install
> file to /etc/X11/xorg.conf (to load the vesa or fbdev driver as an
> interim, to support investigations) so as to get a desktop.
>
> Did you examine the /boot/grub/menu.lst file to see if there were any
> inappropriate boot codes before the showopts flag in that file ?
>
> My impression is your assessment was you unfortunately were not able to
> troubleshoot and contribute to the bug solving process (so as to help
> the developers and packagers get this problem you encountered fixed for
> your hardware) and hence you simply removed openSUSE 11.3 M7.
>
> … Is that assessment of openSUSE 11.3 M7 being now removed from your
> PC correct?
>
>

The assessment should include the fact that I hurt my back again this
morning and can’t sit in one place for long else I seize up. Add to that
a worsening right eye that’s been causing my poor little brain some
problems reconciling the distorted image it gets from that eye with the
rather different one it gets from the left eye and hence gives me
migraines. They’re nothing serious, I rarely get a headache with them,
just lots of flickering coloured lines for a while.

I still have two M7 partitions on this PC but created differently. I
suspect my back will allow me be able to spend more time on them in a
day or two. I might have to try an eye patch to block off my right eye
though. Perhaps I should also get a parrot to perch on my shoulder in
order to enhance the piratical image?

–
Graham P Davis, Bracknell, Berks., UK.
E-mail: newsman AT scarlet HYPHEN jade DOT com

16

I know the feeling wrt back problems. Three weeks ago I was flat on my back for 24 hours, and missed a day at work. Making transitions from sitting down to standing, or standing to sitting or lying, was incredibly painful. I still can NOT lift anything, and I wear a back support most of the time.

If your health is bad, you should not IMHO waste your time with computers.

I know I don’t at times like that.

Get better soon !

17

I’m not sure what other distos have automatic gui configuration for the display, but I can tell you my experience with Fedora 13. After installing Fedora 13 beta on a spare partition, I found that it was only os listed in grub and none of my other partitions were available at boot. Fedora did manage to configure my display correctly at 1680x1050. I think it was using the nouveau driver.

I managed to get things fixed and then deleted the partition for Fedora and installed it as a guest in VirtualBox. The original resolution was 800x600 and there was no improvement after I installed the guest additions. Gnome’s display manager only offered 800x600 and 600x400. Mouse integration didn’t work either.

I waited for a few more updates to Fedora 13 and then installed VirtualBox 3.2 beta and reinstalled the guest additions. Then mouse integration worked but the max res was still 800x600. I tried editing xorg.conf, which is created during the install, but screwed that up royally and ended up with Fedora freezing after the boot process. I had to reinstall. I chalk that up to being unfamiliar with Fedora.

I found another display config tool in the package manager and installed it and was able to get to 1024x768. No other resolutions were available. Then I updated Fedora again and installed the final version of VB 3.2. Still no other resolutions available.

After talking with some people on the Fedora forums, I tried editing xorg.conf again. This time I was able to add 1440x900 to the file and a reboot brought up that resolution. This problem might be specific to running Fedora as a guest in VirtualBox, but my point is the only solution I could find was editing xorg.conf. And after I did this, the display config tool in Gnome offered the higher resolution as well.

I don’t know why the devs want to remove Sax2, but I guess users are just going to have to deal with it until X is truly auto configurable on most hardware. I suspect moving away from hal to dbus is one reason. So openSUSE isn’t the only distro with this problem.

I’m sure a lot of new users don’t like the idea of installing proprietary drivers to get 3d effects either.

Edit: Just wanted to add that running ‘nvidia-xconfig’ after the install of the proprietary drivers is the same thing as creating and editing xorg.conf. The nvidia people just provided a script to do that for you. Installing the drivers without running that command always works for me, but I know it depends on one’s hardware.

18

I’m tempted to recommend EVERY user of openSUSE-11.2 or earlier, make a copy of their /etc/X11/xorg.conf file (and if they have not got one, make one) and put it on a usb stick, so that it is available later. An old xorg.conf may provide a helpful template in tuning an xorg.conf for 11.3.

19

Probably a good idea. But running a display with an xorg.conf file is the “old way” and the openSUSE developers are clearly moving away from it.

20

:frowning: First 11.3 milestone-7 initial impression not that great!
Tried the openSUSE-DVD-Build0625-x86_64 (checked OK). The install fails when trying to mount partitions. I first tried “expert partitioning” but then I remembered I read it is broken in 11.2 so I went with defaults (just selected the device). The format seems to go fine for preexisting partition but later I also got an error during format. There is no detailed information, just the failure and choice to continue or abort.
Hardware: ASUS A8V Deluxe, 1GB RAM, AMD ATHLON 64 X2 4400+. 2 x 250GB WD in RAID1 connected to the Promise FastTrak 378.
The installer shows correct dmraid information.