Suse 8 - good & bad .. install phone support useless
Well I got the charity I look after IT for, to get Suse for their file server
:))
Good
8.0 installed well on that machine, a bog std home built thing. A few false
starts until I selected 640x480 at the start. V pleased, desktop looked fine
from the word go.
Bad
Got a spare drive out for my 2xPIII, sblive, orinoco silver, nvidia gforce2mx,
usb intellimouse
install v speedy.
Reboot, to no mouse ! eh
Went into pcmcia/wireless and found loads of files that had changed and the
only description was in German.
looked in manual, no info on new wireless files < v v bad >
rang install support
wireless not covered, :(
mouse - the support assistant had no idea, and was less than useless when he
told me it probably wouldnt work.
On Fri, 3 May 2002, dids wrote:
Bad Got a spare drive out for my 2xPIII, sblive, orinoco silver, nvidia gforce2mx, usb intellimouse install v speedy.
Reboot, to no mouse ! eh
Sounds similar to my experience. AMD K62-500 w/nVidia Geforce2 MX. SAX detected and set up the card OK. I selected my monitor, and 1280x960x24bpp. At reboot, KDM starts up, but the mouse cursor is transparent. However, 'fishing blindly' around the screen, I realize it's there somewhere, and the buttons work appropriately. I posted this several days ago, and from one response, and some searching on the SDB, I added 'option "sw_cursor" ' to the Device section of XF86Config. That made my cursor appear, so now I thought I could proceed. I set up kinternet, logged in, and immediately ran YOU. Amazing, isn't it, how many patches and replacement packages there are just a week after the distribution is published? This is not a complaint - The folks at SuSE are never satisfied, and keep on working long after the CD images are frozen for production. Other companies would sit back once it's 'out the door', and let the customers find the remaining bugs for them. Well, just as with SuSE 7.2, the nvidia drivers aren't current, and YOU redirects me to an nvidia site for nvidia_GLX and nvidia_kernel. (1 meg each! slow at 28,8k.) I wait for all the packages to install, reboot, and startx, thinking I'd bring it up once before re-editing XF86Config to try removing the sw_cursor. OOPS, here's one case where the cure is worse than the cold. X started, the bottom two parts of the KDE splash screen appeared, and the mouse, keyboard, and display froze up solid. (By 'bottom two parts' I mean: The dark bar with the status message appears, with ...interprocess communication' in a garbled font, and the row of icons just above it appears. The large image of the gears does not appear at all.) I was able to ssh into the machine from my laptop, but killing all the X and KDE related tasks did not free up the main display. I ended up killing one too many things, and locked up the whole machine. ...a reboot and try it again. Yup, it's repeatable. This time when I ssh in from the laptop, I simply `shutdown -h now`. I'm trying to blame this on the nvidia drivers, but I noticed that YOU also updated kde_base, so this lockup might be a kde problem instead... One other thing noted: the original nvidia driver off the CD didn't present a splash screen at startup, while the updated one did. I'll keep posting what I learn from the process. I'd love to hear what others are experiencing, too! Rick Green
Ya, had the same problem on my install. I booting into init 3, the ran SaX2. Of course the mouse failed so I hit the middle keypad number (5) and brought the mouse/key prog. set the mouse again and it worked (go figure). Now, however, many of the devices including my mouse are listed twice in the CC and little applet "available hardware". Oh well, the mouse works now. Check it out. HTH Curtis On Friday 03 May 2002 23:00, Rick Green wrote:
On Fri, 3 May 2002, dids wrote:
Bad Got a spare drive out for my 2xPIII, sblive, orinoco silver, nvidia gforce2mx, usb intellimouse install v speedy.
Reboot, to no mouse ! eh
Sounds similar to my experience. AMD K62-500 w/nVidia Geforce2 MX. SAX detected and set up the card OK. I selected my monitor, and 1280x960x24bpp. At reboot, KDM starts up, but the mouse cursor is transparent. However, 'fishing blindly' around the screen, I realize it's there somewhere, and the buttons work appropriately.
I posted this several days ago, and from one response, and some searching on the SDB, I added 'option "sw_cursor" ' to the Device section of XF86Config.
That made my cursor appear, so now I thought I could proceed. I set up kinternet, logged in, and immediately ran YOU. Amazing, isn't it, how many patches and replacement packages there are just a week after the distribution is published? This is not a complaint - The folks at SuSE are never satisfied, and keep on working long after the CD images are frozen for production. Other companies would sit back once it's 'out the door', and let the customers find the remaining bugs for them.
Well, just as with SuSE 7.2, the nvidia drivers aren't current, and YOU redirects me to an nvidia site for nvidia_GLX and nvidia_kernel. (1 meg each! slow at 28,8k.) I wait for all the packages to install, reboot, and startx, thinking I'd bring it up once before re-editing XF86Config to try removing the sw_cursor. OOPS, here's one case where the cure is worse than the cold. X started, the bottom two parts of the KDE splash screen appeared, and the mouse, keyboard, and display froze up solid. (By 'bottom two parts' I mean: The dark bar with the status message appears, with ...interprocess communication' in a garbled font, and the row of icons just above it appears. The large image of the gears does not appear at all.) I was able to ssh into the machine from my laptop, but killing all the X and KDE related tasks did not free up the main display. I ended up killing one too many things, and locked up the whole machine. ...a reboot and try it again. Yup, it's repeatable. This time when I ssh in from the laptop, I simply `shutdown -h now`.
I'm trying to blame this on the nvidia drivers, but I noticed that YOU also updated kde_base, so this lockup might be a kde problem instead...
One other thing noted: the original nvidia driver off the CD didn't present a splash screen at startup, while the updated one did.
I'll keep posting what I learn from the process. I'd love to hear what others are experiencing, too!
Rick Green
Just an FYI. For a LONG time KDM had issues with the nVidia drivers. I would think that nVidia hasn't bothered to check to see if those bugs were reintroduced w/ KDE3 and the 2880 nVidia driver. I only see the types of issues that have been talked about when I fire up KDM which I never use accept to test that the bugs reported by the SLE users are in fact bugs and not just misconfiguration. I would change from booting runlevel 5 to 3 for a while and after KDM is shutdown. I would rerun SaX2 and make sure all is well. Then use it for a couple days see how everything preforms. BTW..nVidia's last 2 GLX packages make the symlinks that are needed by itself. The switch2 scripts dealing with nVidia are not needed...and in some cases just frell everything up. -=Ben --=====-----=====-- mailto:ben@whack.org --=====-- If it's true that our species is alone in the universe, then I'd have to say that the universe aimed rather low and settled for very little. -GC --=====-----=====--
On Saturday 04 May 2002 04:00, Rick Green wrote:
On Fri, 3 May 2002, dids wrote:
Bad Got a spare drive out for my 2xPIII, sblive, orinoco silver, nvidia gforce2mx, usb intellimouse install v speedy.
Reboot, to no mouse ! eh
Sounds similar to my experience. AMD K62-500 w/nVidia Geforce2 MX. SAX detected and set up the card OK. I selected my monitor, and 1280x960x24bpp. At reboot, KDM starts up, but the mouse cursor is transparent. However, 'fishing blindly' around the screen, I realize it's there somewhere, and the buttons work appropriately.
I posted this several days ago, and from one response, and some searching on the SDB, I added 'option "sw_cursor" ' to the Device section of XF86Config.
Well when you appeared I let it download the nvidia stuff and it told me to reboot, and voila latest nvidia drivers including 3d up and running, that was pretty painless. Now if only I hadnt deleted my crossover office stuff by mistake. grr dids
On Saturday 04 May 2002 00:00, Rick Green wrote:
I'm trying to blame this on the nvidia drivers, but I noticed that YOU also updated kde_base, so this lockup might be a kde problem instead...
One other thing noted: the original nvidia driver off the CD didn't present a splash screen at startup, while the updated one did.
I'll keep posting what I learn from the process. I'd love to hear what others are experiencing, too!
Rick Green
Actually I kind of had learning pains with the Nvidia card on my new computer with 7.3. Was hoping with the 8.0 release it would go a little easier. With 8.0 I just let YOU do it's thing and setup the card with Sax and it works fine for me. I ran 3Ddiag and got the following report back: Verifying 3D configuration based on XFree86 4 for 3D board "nVidia Coorporation GeForce3_1 (10de@0201)": Tests for package "NVIDIA_kernel": package ... done. package files ... done. Tests for package "NVIDIA_GLX": package ... done. package files ... done. Tests for correct OpenGL libraries/GLX extensions: Symbolic Links ... done. /etc/sysconfig/3ddiag (SCRIPT_3D=switch2nvidia_glx) ... done. Test for correct XFree86 version ... done. Tests for XFree86 configuration: Config File /etc/X11/XF86Config ... done. Driver ... done. So it appears everything is as it should be. John -- "Two roads diverged in a wood, and I -- I took the one less traveled by, And that has made all the difference." -- Robert Frost
On Saturday 04 May 2002 12:00 am, Rick Green wrote:
Well, just as with SuSE 7.2, the nvidia drivers aren't current, and YOU redirects me to an nvidia site for nvidia_GLX and nvidia_kernel. (1 meg each! slow at 28,8k.)
No, the reason why it always wants to download them is because Nvidia's license prohibits their drivers to be distributed by anyone other than Nvidia. SuSE contains the "nv" driver, but that is just a stub to a generic SVGA driver that has no 3D video rutines. So it always wants to grab the "nvidia" drivers from Nvidia. In other words, this problem isn't SuSE's fault. :-) -- The shortest distance between two points is under construction. -- Noelie Alito
participants (6)
-
Ben Rosenberg -
Curtis Rey -
dids -
jfmurphy -
Joshua Lee -
Rick Green