I have only installed this in virtual box so far but it’s very smooth and impressive considering the early stage of development. Faultless install. Lots of testing to do yet, but I have some screens for the curious.
On my Sandbox PC, I had openSUSE-11.2 milestone1, with ext3 on both / and /home. When I installed openSUSE-11.2 milestone2, I did a clean install, but kept the ext3 /home from milestone1. For / on 11.2 milestone2, I chose to reformat as an ext4.
This is on an old PC (with only 1.0 GB RAM), so I believe it not uncommon for this PC to have to access the swap. I believe I notice a speed improvement between 11.2 milestone1 KDE-4.2.3 and 11.2 milestone2 KDE-4.3beta, and I believe it is due to ext4 being the chosen file system for " / " .
Interesting Lee. When I have time in a couple of weeks I’ll be doing a disc install rather than Virtual Box, so I’ll get a much better feel for things and will be able to participate more effectively in bug reporting. For now it’s interesting though and I see some nice improvements. One thing I would like to see is the ability to lock packages in yast and have them stay locked even when you do ‘update all in this list if new ver avail’.
I installed milestone2 today on my spare hard drive.
Sadly I get mostly the same old errors and problems :(. I have reported them all in bugzilla, but here is a list if anyone is interested -
Dolphin - Still cannot mount other volumes on the hard disk - An error occured while accessing ‘Volume (reiserfs)’, the system responded: org.freedesktop.org.Hal.PermissionDeniedByPolicy: org.freedesktop…hal.storage.mount-fixed auth_admin_keep_always ← (action, result)
Western Digital 1tb USB hard drive still not recognised by desktop mount tool thingy.
Desktop mount plasmoid still doesn’t close when clicking on desktop, has to be itself personally clicked on.
Kwallet crash on wireless network connect - Executable: kded4 PID: 9313 Signal: 11 (Segmentation fault) - Application: KDE Daemon (kdeinit), signal: Segmentation fault e?1034h[Current thread is 1 (process 9313)] Thread 1 (process 9313):#0 0x759902f0 in ?? ()
Two kmix icons in the taskbar after kwallet crashed, when closed, it moves along the taskbar onto the power thing.
Wireless network will not connect -
May 29 20:44:38 linux-8hls kernel: 288.821059] wlan0: direct probe to AP 00:1c:4a:d5:3d:36 try 1
May 29 20:44:38 linux-8hls kernel: 288.823471] wlan0 direct probe responded
May 29 20:44:38 linux-8hls kernel: 288.823481] wlan0: authenticate with AP 00:1c:4a:d5:3d:36
May 29 20:44:38 linux-8hls kernel: 288.825488] wlan0: authenticated
May 29 20:44:38 linux-8hls kernel: 288.825497] wlan0: associate with AP 00:1c:4a:d5:3d:36
May 29 20:44:38 linux-8hls kernel: 288.828876] wlan0: RX ReassocResp from 00:1c:4a:d5:3d:36 (capab=0x411 status=0 aid=3)
May 29 20:44:38 linux-8hls kernel: 288.828886] wlan0: associated
May 29 20:44:42 linux-8hls kernel: 292.823465] wlan0: deauthenticated (Reason: 1)
May 29 20:44:48 linux-8hls kernel: 298.824058] wlan0: direct probe to AP 00:1c:4a:d5:3d:36 try 1
May 29 20:44:48 linux-8hls kernel: 298.826370] wlan0 direct probe responded
May 29 20:44:48 linux-8hls kernel: 298.826383] wlan0: authenticate with AP 00:1c:4a:d5:3d:36
May 29 20:44:48 linux-8hls kernel: 298.827983] wlan0: authenticated
May 29 20:44:48 linux-8hls kernel: 298.827991] wlan0: associate with AP 00:1c:4a:d5:3d:36
May 29 20:44:48 linux-8hls kernel: 298.830071] wlan0: RX AssocResp from 00:1c:4a:d5:3d:36 (capab=0x401 status=12 aid=3)
May 29 20:44:48 linux-8hls kernel: 298.830080] wlan0: AP denied association (code=12)
May 29 20:44:48 linux-8hls kernel: 299.024053] wlan0: associate with AP 00:1c:4a:d5:3d:36
May 29 20:44:48 linux-8hls kernel: 299.025901] wlan0: RX AssocResp from 00:1c:4a:d5:3d:36 (capab=0x401 status=12 aid=3)
May 29 20:44:48 linux-8hls kernel: 299.025913] wlan0: AP denied association (code=12)
May 29 20:44:48 linux-8hls kernel: 299.224032] wlan0: associate with AP 00:1c:4a:d5:3d:36
May 29 20:44:48 linux-8hls kernel: 299.225808] wlan0: RX AssocResp from 00:1c:4a:d5:3d:36 (capab=0x401 status=12 aid=3)
May 29 20:44:48 linux-8hls kernel: 299.225813] wlan0: AP denied association (code=12)
May 29 20:44:49 linux-8hls kernel: 299.424057] wlan0: association with AP 00:1c:4a:d5:3d:36 timed out
Keeps asking for the password but never connects.
Sound error - Phonon audio something, HDA Nvidia or something. Flashes up on the screen but too fast to read it all.
Suspend to ram broken.
No Nvidia driver available in the vidia repo - not really a bug/error, but it makes real testing a bit lame. Plus the suspend problem “might” be fixed once the nvidia driver is working, but I won’t hold my breath on that one.
Konversation crashes on logout still . bug reported to the konversation devs.
Grub reports US keyboard layout when I chose German on install, eventhough it is actually running the German layout in both X and TTY.
Same old useless version of hplip available in the default repo, useless on any printer/multifunction newer than 1 year old. Crashes with “segfault” on running it.
I was really hoping that the newer kernel would fix my ongoing suspend-to-ram problem “out of the box”, sadly no :(.
I can’t even boot since 11.2 M2 doesn’t boot from LVM where 11.1 boots just fine ;(
P.S. Suspend to ram works for me fine just fine with P35-DS3R, Q6600 and 8800GT with the closed drivers.
I only had to enable waking up from it:)
What didn’t work was waking up with keyboard/mouse what has been fixed easily with checking to which bus is the mouse and keyboard connected (cat /proc/acpi/wakeup)
Do you know of other distributions that can read this? If so, you could pass that information on in your bug report. The dev’s may be able to give you some commands to run so they can see what is happening.
Did you try asking for help in our wireless forum ?
Do you have a movie mode in your digital camera? If so, take a movie of the errors. Thats what I do. Repeatable messages that “just flash by” are very easy to capture in this day and age if one has a cheap digital camera with a movie mode.
I simply disagree. If this was a production GM version, a couple of months after the GM release, then I would say really really good point. But its not. This is an early milestone release. Early. And its 2 days after the release. Just 2 days. But if you believe in this strongly (ie believe there should be a rpm repos for a nVidia driver for an early milestone release, 2 days after its been released), then build the nvida driver yourself as an rpm and create your own repos. And post the repos. If you can’t build a repos (and I know I can not) then you could join IRC freenode #opensuse-factory and see if you can talk anyone there into doing it.
Or simply download the driver installation script and do a custom compile. Its not that difficult.
Make certain you write a bug report on that old version number, as its easy to fix. … But even if it is not fixed by SuSE-GmbH, this is not a worry, as Packman packagers typically package this application.
One point, though, this may be the “same old useless version” of hplip for you, but in fact it works perfectly with my HP printer, so in my case its the “same old perfect version” of hplip. I suspect it works perfectly with most other HP printers as well. Yes it should be fixed, but if it was useless then I would not be able to print, but I can print. … anyway, its a mute point of mine.
Overall, thanks for posting your observations. Please keep an eye on your written bug reports, … maybe add to exisiting milestone1 reports a status that the problem has not been fixed yet in milestone2.
Maybe it still will. You did write a bug report on this and posted an up to date status of your milestone2 test (and success with other kernel versions on different distributions) in that bug report ?
I have not even tried yet. I didn’t expect that to work, though I will try, I was just waiting to be able to install all the development stuff I need etc…(I have to be careful how much I download during certain hours).
I wouldn’t count on that. If something is not part of the factort OSS or NON-OSS repo then you shouldn’t report any bugs if you’re using 11.1 packages. As the “core” system changes so are the packages built against it. Packages for 11.1 were built against 11.1 as were 11.0 packages against 11.1 but that doesn’t say that 11.1 packages won’t work with 11.2.
