MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Ok...
I have Linux Mandrake 10.0 Official in an Celeron 2.4Ghz box with 256Mb RAM and 40Gb HD. My graphics adapter is an ATI Radeon 7000/VE chipset based board. It's been a while since my box starter to 'blink' unexpectedly... at the beginning i thought it was my monitor the one was about to die, but then i found that after starting some programs (mozilla and xmms are the most noticeable) other x-based programs didn't seem to work out, not even the gterm. Then i tried to run the gterm before opening any of these programs, and that way i found out that x-applications died with an fatal error saying they couldn't connect to the X server at 0:0... BUT, when my monitor blinks, it all comes to normal. ¿¿¿????? The blinking, as a matter of fact, looks like the X server is restarting someway, it shutsdown the display and then turns it on again VERY FAST... like a blink as i said before. I have like... 3 months with my linux box and it's the first time it looks to have problems.
Last thing i did was downloading MDK 10.1 Community to upgrade my system and see if this solved the problem, BUT when i select the upgrade option from the MDK 10.1 installer it happens that, when it's time to setup partitions, i get a message saying "Ooops, no root partition found" ¿?¿?¿?¿¿?¿¿¿?¿¿¿¿¿???
Ok... that's all..
thanks in advance community
triaydev
The driver i'm using is the one listed as "ATI Radeon" (as is) in the graphics adapter list that comes within the distro, not the Radeon(fbdev), not the Radeon (fglrx). I tried to get the drivers from ATI but they start since Radeon 9000.
I started installation booting from CDROM.
TNX!
triaydev
Yes, this is the first time i'm trying to perform a system upgrade. Usually I just format and reinstall... But now that my main environment is linux, i don't want to lose documents, symliks, and all customization i've already done. I've read the INSTALL.txt and INSTALL.html that are in the setup disks and they only make reference to install/upgrade booting from cd/dvd, so, how can i launch the setup from the running MDK10? did not see any binary executable other than the windows one. Is it done using RPM stuff?
TKS!
rtriay
Every time I face a new version of Mandrake I'm in exactly the same boat as you.
What I end up doing is this.
1) I TAR up the contents of the /etc directory which contains most of my settings.
e.g.
tar -czvf oldetc.tar.gz /etc/*
2) I also do this to anything I may have changed in any of the stock directories.
3) I boot from a LIVE CD version of Linux, such as Knoppix and mount the old drive partitions.
4) I recursively delete everything except /etc/fstab /home /root and anything else I do NOT want replaced or deleted.
5) Now I perform a NEW installation but tell the installer to utilize existing partitions.
This will cause it to find the /etc/fstab file and use the existing partition structure.
6) After the install I can unpack the tar file and look at anything that may need to be adjusted in the new installation.
Since the scripts often are different, and the upgrade does not change any scripts which I have modified, it is safer to perform this "clean" in place install than it is to try an update/upgrade.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.