I just nixed a perfectly running 7.0 system to install 7.2. After trying every permutation of install options, manual, text-based. expert, I cannot get the damn X Server to work decently. It detects my monitor fine, Dell P1110. I have a Diamond Viper 770 32M video board and the only resolutions it gives me are 1024x768 and less. The only color it gives me is 8/16bit as well. After installing I tried running xf86config to generate a new config file and still the same problem. Has anyone else had similiar problems? What can I do to fix this? My system is useless to me unless I can run at least 1280x1024. One other question, I only upgraded to 7.2 to see if I could get Win4Lin to work, does Win4Lin work under 7.2? If not, I may as well revert to 7.0. I surely hope that SuSE does not follow Red Hat in it's sloppy/untested releases and you sit around waiting for a few more .x releases until everything works again. Thanks for any help, CC
* Suse Email Account (suse@clinicomp.com) [010707 11:15]: -> ->I just nixed a perfectly running 7.0 system to install 7.2. After -> trying every permutation of install options, manual, text-based. ->expert, I cannot get the damn X Server to work decently. It detects ->my monitor fine, Dell P1110. I have a Diamond Viper 770 32M video board ->and the only resolutions it gives me are 1024x768 and less. The only ->color it gives me is 8/16bit as well. -> ->After installing I tried running xf86config to generate a new config ->file and still the same problem. -> ->Has anyone else had similiar problems? What can I do to fix this? My ->system is useless to me unless I can run at least 1280x1024. -> ->One other question, I only upgraded to 7.2 to see if I could get Win4Lin ->to work, does Win4Lin work under 7.2? If not, I may as well revert to 7.0. -> ->I surely hope that SuSE does not follow Red Hat in it's sloppy/untested ->releases and you sit around waiting for a few more .x releases until ->everything works again. How about installing the latest nVidia drivers and their GLX. It's not shipped with SuSE because it's binary only and they don't want to be responsible for it. You can get it from nVidia and there are simple instructions in the readme to get it going. You are using the nv driver most likely. Get the 2 RPM's from nVidia's site..follow the instructions and run SaX2 not xf86config..because SaX2 is tailored for SuSE. I can send you my XF86config file if you like. I have the same card that you do SO I know it works just fine...and I run my res at 1600X1200 w/ 16bit colour (works better for games). It's not SuSE's fault that the video card we have has a binary only driver and they don't want to be responsible for trouble shooting it. It's completely understandable. Write back to the list once you get those 2 packages installed and we can go further. Regards, -- Ben Rosenberg mailto:ben@whack.org ----- The only argument for the superiority of Windows over UNIX is that General Protection Fault outranks Colonel Panic.
Þann laugardagur 07 júlí 2001 18:11 skrifaðir þú:
I just nixed a perfectly running 7.0 system to install 7.2. After trying every permutation of install options, manual, text-based. expert, I cannot get the damn X Server to work decently. It detects my monitor fine, Dell P1110. I have a Diamond Viper 770 32M video board and the only resolutions it gives me are 1024x768 and less. The only color it gives me is 8/16bit as well.
After installing I tried running xf86config to generate a new config file and still the same problem.
Has anyone else had similiar problems? What can I do to fix this? My system is useless to me unless I can run at least 1280x1024.
One other question, I only upgraded to 7.2 to see if I could get Win4Lin to work, does Win4Lin work under 7.2? If not, I may as well revert to 7.0.
I surely hope that SuSE does not follow Red Hat in it's sloppy/untested releases and you sit around waiting for a few more .x releases until everything works again.
Thanks for any help, CC
Hi, I had the same problem. Get the latest nVidia drivers from www.nvidia.com and install them. The problem with nVidia cards is NOT SuSE's fault but nVidias, due to their closed-source fsck-the-community ( we are the phonecompany attitude ). You WILL most probably run into a problem or two with the new drivers to start with if you have any irregular requests, but I managed to get XF4 with 3D acceleration to work at 16-bit 1600x1200 on Viper770 and Dell 990 ( 19" ) Once up, it works great. ( mostly ;) Oh.. and for the win4lin, I havn't tested it myself, but heard that there are serious problems. I'd go for VmWare ( I use VmWare myself, and it always works :) -tosi
Tor Sigurdsson wrote:
Get the latest nVidia drivers from www.nvidia.com and install them.
The problem with nVidia cards is NOT SuSE's fault but nVidias, due to their closed-source fsck-the-community ( we are the phonecompany attitude ).
Anyone running kdm from KDE 2.1.1 will want to fix that nasty problem with Nvidias, which, to be fair, is partly Nvidia's fault and partly SuSE's. There's a conflict with the package pam_devperm, which you can resolve either by removing that package or by removing the directory /var/lib/devperm. (There may be better solutions, but these work.) Without that fix, you can't switch to a virtual terminal with Ctl-Alt-Fn after the first login, nor can you get to text mode after logging out. Pass the word!!!! Paul
On Saturday 07 July 2001 04:26 pm, Paul Abrahams wrote:
Tor Sigurdsson wrote:
Get the latest nVidia drivers from www.nvidia.com and install them.
The problem with nVidia cards is NOT SuSE's fault but nVidias, due to their closed-source fsck-the-community ( we are the phonecompany attitude ).
Anyone running kdm from KDE 2.1.1 will want to fix that nasty problem with Nvidias, which, to be fair, is partly Nvidia's fault and partly SuSE's. There's a conflict with the package pam_devperm, which you can resolve either by removing that package or by removing the directory /var/lib/devperm. (There may be better solutions, but these work.)
Without that fix, you can't switch to a virtual terminal with Ctl-Alt-Fn after the first login, nor can you get to text mode after logging out.
Pass the word!!!!
Paul
This has been fixed in KDE2.2beta1 -- no more weirdness with nVidia when you run KDM :) -Steven
Steven, how was the install of 2.2b1? any problems, benefits...? Cheers. Curtis On Saturday 07 July 2001 15:28, Steven Hatfield wrote:
On Saturday 07 July 2001 04:26 pm, Paul Abrahams wrote:
Tor Sigurdsson wrote:
Get the latest nVidia drivers from www.nvidia.com and install them.
The problem with nVidia cards is NOT SuSE's fault but nVidias, due to their closed-source fsck-the-community ( we are the phonecompany attitude ).
Anyone running kdm from KDE 2.1.1 will want to fix that nasty problem with Nvidias, which, to be fair, is partly Nvidia's fault and partly SuSE's. There's a conflict with the package pam_devperm, which you can resolve either by removing that package or by removing the directory /var/lib/devperm. (There may be better solutions, but these work.)
Without that fix, you can't switch to a virtual terminal with Ctl-Alt-Fn after the first login, nor can you get to text mode after logging out.
Pass the word!!!!
Paul
This has been fixed in KDE2.2beta1 -- no more weirdness with nVidia when you run KDM :)
-Steven
suse updates routines always sucked. don't upgrade if you're not ready to reinstall the new from scratch and import your data from a backup you made on some different disk or partition. ethh http://doom.enemy.org On Sat, 7 Jul 2001, Curtis Rey wrote:
Steven, how was the install of 2.2b1? any problems, benefits...?
Cheers. Curtis
On Saturday 07 July 2001 15:28, Steven Hatfield wrote:
On Saturday 07 July 2001 04:26 pm, Paul Abrahams wrote:
Tor Sigurdsson wrote:
Get the latest nVidia drivers from www.nvidia.com and install them.
The problem with nVidia cards is NOT SuSE's fault but nVidias, due to their closed-source fsck-the-community ( we are the phonecompany attitude ).
Anyone running kdm from KDE 2.1.1 will want to fix that nasty problem with Nvidias, which, to be fair, is partly Nvidia's fault and partly SuSE's. There's a conflict with the package pam_devperm, which you can resolve either by removing that package or by removing the directory /var/lib/devperm. (There may be better solutions, but these work.)
Without that fix, you can't switch to a virtual terminal with Ctl-Alt-Fn after the first login, nor can you get to text mode after logging out.
Pass the word!!!!
Paul
This has been fixed in KDE2.2beta1 -- no more weirdness with nVidia when you run KDM :)
-Steven
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
Right now I'm only worried about my kmailrc file, otherwise no problem from scratch. It's no sweat to bk the mail file. Curtis On Saturday 07 July 2001 17:50, ethhoack ethandphi exbeess wrote:
suse updates routines always sucked. don't upgrade if you're not ready to reinstall the new from scratch and import your data from a backup you made on some different disk or partition.
On Sat, 7 Jul 2001, Curtis Rey wrote:
Steven, how was the install of 2.2b1? any problems, benefits...?
Cheers. Curtis
On Saturday 07 July 2001 15:28, Steven Hatfield wrote:
On Saturday 07 July 2001 04:26 pm, Paul Abrahams wrote:
Tor Sigurdsson wrote:
Get the latest nVidia drivers from www.nvidia.com and install them.
The problem with nVidia cards is NOT SuSE's fault but nVidias, due to their closed-source fsck-the-community ( we are the phonecompany attitude ).
Anyone running kdm from KDE 2.1.1 will want to fix that nasty problem with Nvidias, which, to be fair, is partly Nvidia's fault and partly SuSE's. There's a conflict with the package pam_devperm, which you can resolve either by removing that package or by removing the directory /var/lib/devperm. (There may be better solutions, but these work.)
Without that fix, you can't switch to a virtual terminal with Ctl-Alt-Fn after the first login, nor can you get to text mode after logging out.
Pass the word!!!!
Paul
This has been fixed in KDE2.2beta1 -- no more weirdness with nVidia when you run KDM :)
-Steven
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
Curtis, Get the 2.2 Beta1 RPM's from kde.org .. they are damn worth it. It a bit faster in my opinion then 2.1.1 and has some nice eye candy. You might use some of the new features of Kmail if you use that. The new version of Konq seems to let me specify user agents for specific sites..something I couldn't get to work right before. All in all you can check it out. I love it. If you hate it. You can install the 2.1.1 RPM's back over it and be no worse for wear. I will say this. You should save the files out of your .kde2 directory because there are some differences between 2.2 and 2.1.1 that make things act a bit weird if you just start KDE with your old .kde2 directory. You most likely won't have to do this when 2.2 beta2 comes out... It's cool to play with... :) * ethhoack ethandphi exbeess (ethh@satanii.enemy.org) [010707 15:51]: Unfounded bullshit -> suse updates routines always sucked. -- Ben Rosenberg mailto:ben@whack.org ----- The only argument for the superiority of Windows over UNIX is that General Protection Fault outranks Colonel Panic.
Ben, your talking about the .kde2 directory in my user and root account -right. Not the kde2 directory in /opt? Can I just change them to .kde2.old or .kde2.bkup? Cheers, Curtis and TIA On Saturday 07 July 2001 21:40, Ben Rosenberg wrote:
Curtis,
Get the 2.2 Beta1 RPM's from kde.org .. they are damn worth it. It a bit faster in my opinion then 2.1.1 and has some nice eye candy. You might use some of the new features of Kmail if you use that. The new version of Konq seems to let me specify user agents for specific sites..something I couldn't get to work right before.
All in all you can check it out. I love it. If you hate it. You can install the 2.1.1 RPM's back over it and be no worse for wear.
I will say this. You should save the files out of your .kde2 directory because there are some differences between 2.2 and 2.1.1 that make things act a bit weird if you just start KDE with your old .kde2 directory. You most likely won't have to do this when 2.2 beta2 comes out...
It's cool to play with... :)
* ethhoack ethandphi exbeess (ethh@satanii.enemy.org) [010707 15:51]:
Unfounded bullshit -> suse updates routines always sucked.
* Curtis Rey (crrey@home.com) [010707 21:32]: ->Ben, your talking about the .kde2 directory in my user and root account ->-right. Not the kde2 directory in /opt? Can I just change them to .kde2.old ->or .kde2.bkup? Yes, just mv your .kde2 in your home and root directories before install and let them be recreated. -- Ben Rosenberg mailto:ben@whack.org ----- The only argument for the superiority of Windows over UNIX is that General Protection Fault outranks Colonel Panic.
Thanks Ben, tomorrow project. :) Curtis On Saturday 07 July 2001 23:34, Ben Rosenberg wrote:
* Curtis Rey (crrey@home.com) [010707 21:32]: ->Ben, your talking about the .kde2 directory in my user and root account ->-right. Not the kde2 directory in /opt? Can I just change them to .kde2.old ->or .kde2.bkup?
Yes, just mv your .kde2 in your home and root directories before install and let them be recreated.
Curtis Rey wrote:
Ben, your talking about the .kde2 directory in my user and root account -right. Not the kde2 directory in /opt? Can I just change them to .kde2.old or .kde2.bkup?
I ran into some trouble doing a simple rename of the .kde2 directory, although I may merely have mistyped something that gave me that impression. To be absolutely safe, I'd use "cp -a". But again, that may be overkill and a rename, correctly done, might be fine. Paul
On Sun, 8 Jul 2001, Paul Abrahams wrote: pa> Curtis Rey wrote: pa> pa> > Ben, your talking about the .kde2 directory in my user and root account pa> > -right. Not the kde2 directory in /opt? Can I just change them to .kde2.old pa> > or .kde2.bkup? pa> pa> I ran into some trouble doing a simple rename of the .kde2 pa> directory, although I may merely have mistyped something that gave pa> me that impression. To be absolutely safe, I'd use "cp -a". But pa> again, that may be overkill and a rename, correctly done, might be pa> fine. pa> I've done a rename several times, I've always gone outside of X though. Goto a terminal outside of X and logon, then rename your .kde directory. After which, when you logon to KDE you'll get a brand new configuration again. Not sure what would happen if you renamed it while logged onto X, suppose it would error all over the place when you attempted to logout or close a window or something. pa> Paul pa> pa> pa> pa> -- S.Toms - smotrs@mindspring.com - www.mindspring.com/~smotrs SuSE Linux v7.0+ - Kernel 2.2.18 In any formula, constants (especially those obtained from handbooks) are to be treated as variables.
* Paul Abrahams (abrahams@acm.org) [010708 08:23]: -> ->I ran into some trouble doing a simple rename of the .kde2 directory, although I ->may merely have mistyped something that gave me that impression. To be ->absolutely safe, I'd use "cp -a". But again, that may be overkill and a rename, ->correctly done, might be fine. -> Yes, log out of KDE2..then execute a 'mv .kde2 kde2.paul' or something like that. You can then do the upgrade and log back into KDE. Be sure to kill KDM. :) -- Ben Rosenberg mailto:ben@whack.org ----- The only argument for the superiority of Windows over UNIX is that General Protection Fault outranks Colonel Panic.
On Saturday 07 July 2001 06:49 pm, Curtis Rey wrote:
Steven, how was the install of 2.2b1? any problems, benefits...?
Cheers. Curtis
On Saturday 07 July 2001 15:28, Steven Hatfield wrote:
On Saturday 07 July 2001 04:26 pm, Paul Abrahams wrote:
Tor Sigurdsson wrote:
Get the latest nVidia drivers from www.nvidia.com and install them.
The problem with nVidia cards is NOT SuSE's fault but nVidias, due to their closed-source fsck-the-community ( we are the phonecompany attitude ).
Anyone running kdm from KDE 2.1.1 will want to fix that nasty problem with Nvidias, which, to be fair, is partly Nvidia's fault and partly SuSE's. There's a conflict with the package pam_devperm, which you can resolve either by removing that package or by removing the directory /var/lib/devperm. (There may be better solutions, but these work.)
Without that fix, you can't switch to a virtual terminal with Ctl-Alt-Fn after the first login, nor can you get to text mode after logging out.
Pass the word!!!!
Paul
This has been fixed in KDE2.2beta1 -- no more weirdness with nVidia when you run KDM :)
-Steven
It went very easily. I had to do only a couple of things: 1) Remove all old KDE2.1.1 packages (I don't like upgrades, YMMV if you decide to keep your old RPMs). I didn't remove KDELIBS or any programs. 2) Install all new RPMs from ftp.kde.org/pub/kde/unstable/2.2beta1/SuSE/i386/7.2 with --nodeps and --force command line options. 2) Move my ~/.kde2 directory out of the way - I know at least Konsole's config file isn't backward compatible, there is probably more. 3) Remove all ~/.DCOP* files, these somehow prevented KDE2 from starting. 4) Start up KDE2 5) Pick my jaw up off the floor at how nice it is. To this point, there were only a couple of things that aren't working right on my system... your's may be different. nspluginviewer crashes a lot when hitting pages with flash animations. I've since disabled the flash plugin, waiting for them to fix this bug, probably in beta2. During startup, I get some kind of "CPU Overload detected, Sound Server aborting." message... then Knotify segfaults with signal #6. This doesn't seem to affect sound at all, it's just annoying as it elongates my startup for a few seconds. Noatun runs only every 5th Tuesday of the 5th week of the 13th month. If it runs at all. This probably has to do with the last error... beta2 will hopefully have this fixed up. I use XMMS anyways.. To me, noatun is just a silly program with a funny name. I'd much rather see XMMS get a QT GUI front end, rather than writing the whole thing from scratch. But I guess common sense isn't prevalent in the noatun developer community. And that's it... Konqueror is an order of magnitude better.. the icons are definitely more polished, the menus have effects now (Win2k fade effects rock, imho). It's just much nicer. Have fun! -Steven
Steven, any idea when the finished release will be out. I'm not so impatient that I can't wait for a final release (I realize that no one may really know when the final will be released - but just wondering). I have had bad luck when messing with the Dcop stuff. Curtis :) On Sunday 08 July 2001 11:26, Steven Hatfield wrote:
On Saturday 07 July 2001 06:49 pm, Curtis Rey wrote:
Steven, how was the install of 2.2b1? any problems, benefits...?
Cheers. Curtis
On Saturday 07 July 2001 15:28, Steven Hatfield wrote:
On Saturday 07 July 2001 04:26 pm, Paul Abrahams wrote:
Tor Sigurdsson wrote:
Get the latest nVidia drivers from www.nvidia.com and install them.
The problem with nVidia cards is NOT SuSE's fault but nVidias, due to their closed-source fsck-the-community ( we are the phonecompany attitude ).
Anyone running kdm from KDE 2.1.1 will want to fix that nasty problem with Nvidias, which, to be fair, is partly Nvidia's fault and partly SuSE's. There's a conflict with the package pam_devperm, which you can resolve either by removing that package or by removing the directory /var/lib/devperm. (There may be better solutions, but these work.)
Without that fix, you can't switch to a virtual terminal with Ctl-Alt-Fn after the first login, nor can you get to text mode after logging out.
Pass the word!!!!
Paul
This has been fixed in KDE2.2beta1 -- no more weirdness with nVidia when you run KDM :)
-Steven
It went very easily. I had to do only a couple of things: 1) Remove all old KDE2.1.1 packages (I don't like upgrades, YMMV if you decide to keep your old RPMs). I didn't remove KDELIBS or any programs. 2) Install all new RPMs from ftp.kde.org/pub/kde/unstable/2.2beta1/SuSE/i386/7.2 with --nodeps and --force command line options. 2) Move my ~/.kde2 directory out of the way - I know at least Konsole's config file isn't backward compatible, there is probably more. 3) Remove all ~/.DCOP* files, these somehow prevented KDE2 from starting. 4) Start up KDE2 5) Pick my jaw up off the floor at how nice it is.
To this point, there were only a couple of things that aren't working right on my system... your's may be different.
nspluginviewer crashes a lot when hitting pages with flash animations. I've since disabled the flash plugin, waiting for them to fix this bug, probably in beta2.
During startup, I get some kind of "CPU Overload detected, Sound Server aborting." message... then Knotify segfaults with signal #6. This doesn't seem to affect sound at all, it's just annoying as it elongates my startup for a few seconds.
Noatun runs only every 5th Tuesday of the 5th week of the 13th month. If it runs at all. This probably has to do with the last error... beta2 will hopefully have this fixed up. I use XMMS anyways.. To me, noatun is just a silly program with a funny name. I'd much rather see XMMS get a QT GUI front end, rather than writing the whole thing from scratch. But I guess common sense isn't prevalent in the noatun developer community.
And that's it... Konqueror is an order of magnitude better.. the icons are definitely more polished, the menus have effects now (Win2k fade effects rock, imho). It's just much nicer.
Have fun! -Steven
On Sunday 08 July 2001 12:31 pm, Curtis Rey wrote:
Steven, any idea when the finished release will be out. I'm not so impatient that I can't wait for a final release (I realize that no one may really know when the final will be released - but just wondering). I have had bad luck when messing with the Dcop stuff.
Curtis :)
On Sunday 08 July 2001 11:26, Steven Hatfield wrote:
On Saturday 07 July 2001 06:49 pm, Curtis Rey wrote:
Steven, how was the install of 2.2b1? any problems, benefits...?
Cheers. Curtis
On Saturday 07 July 2001 15:28, Steven Hatfield wrote:
On Saturday 07 July 2001 04:26 pm, Paul Abrahams wrote:
Tor Sigurdsson wrote:
Get the latest nVidia drivers from www.nvidia.com and install them.
The problem with nVidia cards is NOT SuSE's fault but nVidias, due to their closed-source fsck-the-community ( we are the phonecompany attitude ).
Anyone running kdm from KDE 2.1.1 will want to fix that nasty problem with Nvidias, which, to be fair, is partly Nvidia's fault and partly SuSE's. There's a conflict with the package pam_devperm, which you can resolve either by removing that package or by removing the directory /var/lib/devperm. (There may be better solutions, but these work.)
Without that fix, you can't switch to a virtual terminal with Ctl-Alt-Fn after the first login, nor can you get to text mode after logging out.
Pass the word!!!!
Paul
This has been fixed in KDE2.2beta1 -- no more weirdness with nVidia when you run KDM :)
-Steven
It went very easily. I had to do only a couple of things: 1) Remove all old KDE2.1.1 packages (I don't like upgrades, YMMV if you decide to keep your old RPMs). I didn't remove KDELIBS or any programs. 2) Install all new RPMs from ftp.kde.org/pub/kde/unstable/2.2beta1/SuSE/i386/7.2 with --nodeps and --force command line options. 2) Move my ~/.kde2 directory out of the way - I know at least Konsole's config file isn't backward compatible, there is probably more. 3) Remove all ~/.DCOP* files, these somehow prevented KDE2 from starting. 4) Start up KDE2 5) Pick my jaw up off the floor at how nice it is.
To this point, there were only a couple of things that aren't working right on my system... your's may be different.
nspluginviewer crashes a lot when hitting pages with flash animations. I've since disabled the flash plugin, waiting for them to fix this bug, probably in beta2.
During startup, I get some kind of "CPU Overload detected, Sound Server aborting." message... then Knotify segfaults with signal #6. This doesn't seem to affect sound at all, it's just annoying as it elongates my startup for a few seconds.
Noatun runs only every 5th Tuesday of the 5th week of the 13th month. If it runs at all. This probably has to do with the last error... beta2 will hopefully have this fixed up. I use XMMS anyways.. To me, noatun is just a silly program with a funny name. I'd much rather see XMMS get a QT GUI front end, rather than writing the whole thing from scratch. But I guess common sense isn't prevalent in the noatun developer community.
And that's it... Konqueror is an order of magnitude better.. the icons are definitely more polished, the menus have effects now (Win2k fade effects rock, imho). It's just much nicer.
Have fun! -Steven
The URL for the KDE2.2 release schedule is at: http://developer.kde.org/development-versions/kde-2.2-release-plan.html Have a great Sunday :) -Steven
Suse Email Account
I just nixed a perfectly running 7.0 system to install 7.2. After trying every permutation of install options, manual, text-based. expert, I cannot get the damn X Server to work decently. It detects my monitor fine, Dell P1110. I have a Diamond Viper 770 32M video board and the only resolutions it gives me are 1024x768 and less. The only color it gives me is 8/16bit as well.
After installing I tried running xf86config to generate a new config file and still the same problem.
Has anyone else had similiar problems? What can I do to fix this? My system is useless to me unless I can run at least 1280x1024.
One other question, I only upgraded to 7.2 to see if I could get Win4Lin to work, does Win4Lin work under 7.2? If not, I may as well revert to 7.0.
I surely hope that SuSE does not follow Red Hat in it's sloppy/untested releases and you sit around waiting for a few more .x releases until everything works again.
Thanks for any help, CC
I threw 7.2 on my windows98 drive to test as my workstation was a 7.0 box with all the tweaks I needed. 7.2 was a bit of work to get my ATI XPERT 32M AGP video and ViewSonic G800 to do the 24bit and 1600x1200 I like with XFree 4.0 with YaST2. My Logitech MoseMan Wheel (laser) works now with wheel scrolling in xterm's and browsers, as well as spreadsheets, etc. So, I upgraded my 7.0 workstation. Not everything went smooth, but not everything I did was blessed by SuSE :-) So I have the Apache server working, but not MRTG. I have my desktop working, but not apps that I need to run as root, so I needless to say, some more tweaking is in order. Quite a few improvements, but who could tell how many tweaks evryone who buys 7.2 needs ? You would have to be God to guess ahead in that kind of situation. I think if you work at starting small and the getting the tweaks you want, you'll be quite happy. /Dee
participants (9)
-
Ben Rosenberg -
Curtis Rey -
Dee McKinney -
ethhoack ethandphi exbeess -
Paul Abrahams -
S.Toms -
Steven Hatfield -
Suse Email Account -
Tor Sigurdsson