Jump to content

waferhead

Members
  • Posts

    29
  • Joined

  • Last visited

Everything posted by waferhead

  1. Have you tried turning off all accellerations/features for X? Whenever you run into X drawing/rendering issues, that's usually a good thing to try. Then try the vesa driver... If you can't see X well enough, drop to the console and run XFdrake.
  2. Folow up on my related trials... I reinstalled 2008.1 from backups, ran updates, and am trying to figure out how to trigger the automatic didt upgrade feature. Simply changing the repos to 2009.0 using easy urpmi and doing an update didn't go well. (Has worked in the past...) I am hoping upgrading from a working KDE3 installation will work better than installing it using "urpmi task-kde3" (Results in a clean install, but a useless desktop in numerous ways) Going back to 2008.1 isn't an option on my "main" box, as mythconverg got updated... I'd have to try installing the 2009.0 version of mythtv etc.
  3. Unfortunately KDE3s configuration is horribly broken in dozens of small ways in 2009.0, and it is almost as unusable as KDE4. Perhaps moreso, I gave up on it after ~ 30 min of trying to fix it manually. You cannot even change the default program from the "open with" dialog anymore, and you can no longer add arguments-- The parser is broken still. Dolphin is nearly useless... I'm still trying to get the hang of KDE4 on my main box, as it works mostly on a dual core Athlon w/4G of memory, but on slower hardware, forget it. The only reason I'm still running it is for the latest versions of a few programs, and the expectation it will be fixed (soon) by some magic updates. I ran cooker for a year or so at one point, ran updates on a cron job, worked great... 2009.0? not so much. I just had to install a KNOPPIX CD on an old bit of kit here for a strange reason I won't go into... usually gets borked running updates, but worked fine for some reason... 2009.0 will install fine on same setup, but is so insanely slow by comparison it is rediculous....it was gruesome in 2009.0 even w/icewm, and flew running Debian w/KDE3.
  4. You can select lilo from the pull down listing the boot loader when it asks. This is highly suggested as grub has had a known bug for 2 years not being able to load some other loaders... Like grub. 64 bit grub cannot load 32 bit. This is annoying to say the least. This is also a problem for Ubuntu, (probably everyone) and again is a bug in grub. Lilo has no such issues, but the graphical lilo option went away ~ 2007.0. Why grub is the default is still a mystery to me. Other than THAT, I have installed 2008.0 on several systems and used the One-KDE cd as a diagnostic tool (and install tool) on dozens. Works awesome. Install (and auto resize of the windows partition) has worked flawlessly so far for me so far. The only "gripe" I have with the install is the brain damaged copy/paste they set up (likely so as not to confuse folks, mimics Windows ONLY, removing the std (additional) X11 method) There is an easy fix for that, was lookinging for it when I read this fine walk thru. (EDIT---Turns out I just had to set the mouse up properly. The autodetect or defaults have changed)
×
×
  • Create New...