Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by ianw1974

  1. ianw1974


    Sounds like it locked everything up including the keyboard as well. Only the ALT-SYSRQ combination or the 5 second press of the power button would help here. Your system is now behaving how it should. There in the GUI somewhere is a setting to decide how long (10 minutes) before display switches off. When you press the keyboard or move the mouse, it should wake the monitor up. And it's now doing this for you. The only outstanding problem for you, is finding in KDE where to modify this setting of 10 minute default for switching the monitor off.
  2. ianw1974


    Hi John, Sorry can't help you about KDE, as I'm not using it. However, with a desktop system, the laptop stuff wouldn't have gotten installed, so I don't expect this is the problem. Even with desktop systems, the screensaver will work, and then in about 10 minutes the system puts the monitor in power save mode. There will be an option somewhere in KDE to sort this out - I just can't honestly tell you where as I've haven't used KDE since Mandriva 2007 or earlier. The fact it's locking up, is hinting at something else - possibly a display driver problem. Sometimes I get it on my laptop in that the screensaver goes active, and I can't get it back to the keyboard, but I can CTRL-ALT-F2 to a console and then kill the gnome-screensaver, and then I've got access to my system again. Although I've not had it go to sleep and then not wake back up again, although maybe I had this once with Mandriva a while back, but then I had a crappy Nvidia 420 go or something that had like 16MB of memory. Sorry I can't be any more help.
  3. Gnome is not using that much space, you could leave it. It would account for maybe 1GB of space maybe less. You wouldn't need to reinstall to remove it, you can simple remove it easily enough. I always used to have KDE and Gnome installed at the same time.
  4. Unlock with -i: To lock: chattr +i /etc/fstab to unlock: chattr -i /etc/fstab
  5. As it followed between 32 bit and 64 bit versions, and installing the nvidia drivers, it seems whichever driver chosen during install was causing your problem. Glad you got it sorted out :)
  6. So it should apply with ext4 as well. Try it.
  7. That little applet you can stop from running automatically at startup, that way you'll be on manual. At least you could always untick the option "always run at startup", if you're talking about the orange question mark icon (if they're still using that).
  8. Googled it, found the wiki and searched for root: http://www.magos-linux.ru/dwiki/doku.php?id=%D1%84%D0%B0%D0%B9%D0%BB_%D0%BD%D0%B0%D1%81%D1%82%D1%80%D0%BE%D0%B5%D0%BA&s[]=root Default user password is magos Default root password is toor
  9. You'd have to make sure cups is installed, and then in your web browser in the url bar type: localhost:631 and configure it in here. I would expect that the kernel still has parallel port support.
  10. OpenSUSE has Gnome. You get asked during installation about what to install. Or you can try a Debian derivative such as Ubuntu or Linux Mint. Or even Debian itself if you like.
  11. I'm not sure it's the kernel. You should be OK running a 32 bit distro as far as I'm aware. Just it'll work better with 4GB of RAM with a 64 bit kernel. As a desktop you're better off as 32 bit. I've had this before with X spiking, and I could only get into my system with SSH and restart X. Failing that, another safe way than the power button is: ALT-SYSRQ R S E I U B will safely save everything that's required to disk and reboot. Press each key in sequence. However, some updates might fix your problem, or it might be something to do with your display driver.
  12. Are you running xsane as a regular user? Try running as user root and see if it works? Open a terminal, su to root, and then run xsane from the prompt and see if you can do it. If so, then we need to do something else. Run dmesg after you plugged the device in and let's see what dev it got, and we can check user/group permissions for that particular device.
  13. ianw1974


    Lets do the time warp again :)
  14. If it worked before, then there's probably something in the kernel that isn't working as it should be for you.
  15. I have the same problem as you roger - that I have a thing about keyboards, and they must feel right. Trying to find one is not easy. That said, the PS/2 should work fine without any problems. Normally you'd find more problems with a USB one. Can you try a BIOS upgrade on your computer?
  16. If you have ext3 partition, just lock the file: chattr +i /etc/fstab then it won't be modified after reboot. Of course, edit it first, then lock it.
  17. Did you keep your home directory when you clean installed? You could check if the firefox profile is a problem by renaming the .mozilla directory in /home/yourusername and then opening firefox again. Obviously make sure firefox is closed before you do this. If not, then you can always remove the new .mozilla created and copy the old one back.
  18. Is this a system upgrade or a clean install?
  19. Post number 4 has the solution in it. He used cups.
  20. They don't normally support an upgrade for more than a two point release. Therefore, you can upgrade to 2008.2 or 2009.1 but not anything more than this. Suggest clean install. And yes, it's easy as downloading the DVD iso and then burning it with something like Brasero in Gnome or K3B in KDE.
  21. Can you post the contents of /etc/fstab so we can see more info. Maybe something in here as awry.
  22. udev maybe, but try umask=0 instead in fstab, see if it helps.
  23. No, it's kind of normal. When you remove those entries from fstab, you'll then be able to mount them like the other one from within Dolphin when you click them. I had them in fstab once, but when I clicked, I would get the same or similar error. Commented them from fstab and rebooted, and job done :)
  24. Try with umask=0 instead of umask=000 - I remember I had umask issues in the past before, or that I simply didn't have access to copy, but then umask=0 was OK. I haven't checked to see if there is a difference between umask=0 or umask=000 so maybe not. Other alternative, is to remove the defaults option and the comma before umask and then try that after unmounting and mounting again.
  • Create New...