I tried out 12.2 milestone1 ( build 0151) on my Sandbox PC, which is an ancient athlon-1100 with an MSI KT3 Ultra motherboard, 2GB RAM, and an AGP nVidia FX5200 graphic card.
I had noted previous that the liveCDs were too large for a CD, so I burned the 32-bit openSUSE-12.2 liveCD to a +R DVD and then booted this old PC to that burned DVD.
I used/entered the ‘nomodeset’ boot code in the boot grub menu, as I know from experience this nVidia card gives the nouveau driver hiccups.
The PC booted to 12.2 KDE ok to a somewhat low 1024x768 resolution, albeit with the fbdev driver, as evident from the /var/log/Xorg.0.log file: SUSE Paste
However if one looks at ‘my computer’ one obtains a fallacious reading from the openSUSE ‘sysinfo’ that the nouveau driver is in use, which is not the case. It is the fbdev driver that is in use (take a look at the Xorg.0.log file that I quoted).
This graphic card is capable of 1600x1200 resolution (and the monitor I use capable of 1920x1200) so 1024x768 is a bit on the low side.
I plugged in a USB-2.0 memory stick and it was hot plug automounted ok. I used zypper to install the application ‘leafpad’ which installed ok. I noted the 12.1 repositories were still configured/in-use for this 12.2 milestone1 build-0151
This sandbox PC has two sound devices, one on the motherboard and an ancient sound blaster compatible sound card. I had to go to YaST to configure both sound cards, and after doing that sound worked. I also installed pavucontrol and noted it functioned fine with the sound devices.
I launched firefox and successfully played a youtube video.
I noted I was getting artifacts associated with the fbdev driver, as seen here :
and here in YaST :
I launched open office and it ran, albeit I did get typical JRE required error upon starting open office.
**WITHOUT NOMODESET **
I then rebooted the PC and checked to see if it would boot to X without ‘nomodeset’. It would not, and it dumped me at a “linux login:” prompt.
Here is a pix of the error in the Xorg.0.log file (when looking at it with a text editor) when the nouveau driver fails:
[click on image for larger view]
This is an upstream error to the best of my knowledge and there is no point in cluttering bugzilla with this as a bug report.
so I then tried the ‘nv’ driver (see next post).