I've managed to get a working installation of 7.3, but I have a few comments on the process. 1) I like the new installer, and the animated framebuffer during startup. Very nicely done 2) The installer works ok, but I ran in to a bug. I don't know if it's repeatable. I selected upgrade, but when I got as far as having to manually select all the ximian packages I'd installed previously, I changed my mind and decided to go for a clean install instead. The installer didn't like this at all, apparently. If told me I had about 120 MB to install, the picture of the SuSE employees flashed by, it said it couldn't install either lilo or my user, and then everything crashed. When I rebooted and selected fresh install from the start, everything worked. 3) I have an nvidia geforce2. After reboot, X started without a cursor. After 3D was installed from the nvidia drivers, it came back. 4) During install, I selected not to have 3D acceleration. This installed the mesasoft drivers, but as I mentioned in another post, /usr/lib/libGL.so was broken, so when I installed the real drivers it didn't work. I had to recreate the symlink manually. 5) I tried running JFS on my first attempt at an install. When the system crashed, I got a chance to see fsck.jfs in action. Not a pretty sight. When the system boots, all file systems are in read only mode. I have a vague recollection of reading that this is meant to be A Good Thing, though I can't remember why. All other fsck:s emit a warning about 'replaying log on read only file system' and move on. I have always assumed that this meant that they did in fact write something to the 'read only' file system. fsck.jfs however did not. It just looped, trying endlessly to write, but failing with a note that the file system is read only. Those are the things I've noted up to now. Mostly, it looks like a very clean system. I like the new design of the desktop in kde, and I very much like the way kwintv installed and configured without a hitch. Perhaps I'll have more comments after some more testing. I hope not :) regards Anders
On Thu, Nov 15, Anders Johansson wrote:
I've managed to get a working installation of 7.3, but I have a few comments on the process.
1) I like the new installer, and the animated framebuffer during startup. Very nicely done
Thanks :)
2) The installer works ok, but I ran in to a bug. I don't know if it's repeatable. I selected upgrade, but when I got as far as having to manually select all the ximian packages I'd installed previously, I changed my mind and decided to go for a clean install instead. The installer didn't like this at all, apparently. If told me I had about 120 MB to install, the picture of the SuSE employees flashed by, it said it couldn't install either lilo or my user, and then everything crashed. When I rebooted and selected fresh install from the start, everything worked.
Hmm, hard to tell what went wrong here, especially since you did a fresh install afterwards. Without the YaST2 log files it will be hard to reproduce :(
3) I have an nvidia geforce2. After reboot, X started without a cursor. After 3D was installed from the nvidia drivers, it came back.
This is odd. I have the same card here!
4) During install, I selected not to have 3D acceleration. This installed the mesasoft drivers, but as I mentioned in another post, /usr/lib/libGL.so was broken, so when I installed the real drivers it didn't work. I had to recreate the symlink manually.
This should have been done by the "switch2*" script. Did you run it after installing the RPM?
5) I tried running JFS on my first attempt at an install. When the system crashed, I got a chance to see fsck.jfs in action. Not a pretty sight.
When the system boots, all file systems are in read only mode. I have a vague recollection of reading that this is meant to be A Good Thing, though I can't remember why. All other fsck:s emit a warning about 'replaying log on read only file system' and move on. I have always assumed that this meant that they did in fact write something to the 'read only' file system.
fsck.jfs however did not. It just looped, trying endlessly to write, but failing with a note that the file system is read only.
Yes, this only happens when JFS is being used on the root partition. Seems like the JFS people did not really test this scenario - it has been fixed with later versions. http://sdb.suse.de/en/sdb/html/grimmer_jfs.html
Those are the things I've noted up to now. Mostly, it looks like a very clean system. I like the new design of the desktop in kde, and I very much like the way kwintv installed and configured without a hitch. Perhaps I'll have more comments after some more testing. I hope not :)
Thanks for your comments! Bye, LenZ -- ------------------------------------------------------------------ Lenz Grimmer SuSE GmbH mailto:grimmer@suse.de Schanzaeckerstr. 10 http://www.suse.de/~grimmer/ 90443 Nuernberg, Germany You tell 'em Piano, you're upright and square.
On Thursday 15 November 2001 12:41, Lenz Grimmer wrote:
4) During install, I selected not to have 3D acceleration. This installed the mesasoft drivers, but as I mentioned in another post, /usr/lib/libGL.so was broken, so when I installed the real drivers it didn't work. I had to recreate the symlink manually.
This should have been done by the "switch2*" script. Did you run it after installing the RPM?
Yes I did, but that script only touches /usr/lib/libGL.so.1. That link points to the real driver. /usr/lib/libGL.so should always point to /usr/lib/libGL.so.1, but when I installed it pointed directly to GL/libGL.so.1.2.mesasoft.
It seems that it is the package mesa-devel.rpm that sets the symlink libGL.so => GL/libGL.so.1.2.mesasoft. I checked and it did this in 7.2 as well. Perhaps it depends on the order in which things are installed, if it messes things up or not?! In any case, I don't think it is a correctly maintained symlink. Correct me if I'm wrong. The package also overwrites a few static libraries, which can be a nuicance if you install it after you have a working 3D installation. You'd have to re-install the proper libs again, afaics //Anders On Thursday 15 November 2001 12:48, Anders Johansson wrote:
On Thursday 15 November 2001 12:41, Lenz Grimmer wrote:
4) During install, I selected not to have 3D acceleration. This installed the mesasoft drivers, but as I mentioned in another post, /usr/lib/libGL.so was broken, so when I installed the real drivers it didn't work. I had to recreate the symlink manually.
This should have been done by the "switch2*" script. Did you run it after installing the RPM?
Yes I did, but that script only touches /usr/lib/libGL.so.1. That link points to the real driver. /usr/lib/libGL.so should always point to /usr/lib/libGL.so.1, but when I installed it pointed directly to GL/libGL.so.1.2.mesasoft.
participants (2)
-
Anders Johansson
-
Lenz Grimmer