Jump to content

dude67

OTW
  • Posts

    1155
  • Joined

  • Last visited

Posts posted by dude67

  1. I'm not currently writing this from my MDV installation, but IIRC the latest Nvidia driver in Mandriva repos is just that: 177.80.

     

    Have you tried finding the same in Mandriva repos? Have you set up the sources correctly (also the PLF sources)? The simplest way (at least for me) is to install the Nvidia-latest -package (don't remember the full name of that virtual driver) that would set you up with the latest Nvidia drivers.

     

    To set the repos correctly go to the link above Easy-Urpmi and follow the instructions there (OK, I'm sure you're familiar with that - but for everyone else having this problem). Then install the Nvidia-latest -package and you're good to go.

  2. After installing (new installation - not upgrade) MDV2009.0 the new MCC does not work properly. I have set the sources from easy-urpmi and they should all be fine.

    1) Installing new software packages. MCC crashes shortly, when clicked "Install & Remove Software".

    2) Updating packages. MCC crashes also when choosing "update your system"

    3) Configure media sources... MCC crashes again when I choose e.g. "Edit" for one of the medias.

     

    OK, when I choose "Install & Remove Software" from the K-menu or type "rpmdrake" in konsole, everything works just fine. Also, if I add media through Konsole everything works great. But the problem occurs if I start MCC either from the Konsole or from the K-menu.

     

    So what's wrong with MCC? Here's the printout from the Konsole from the start until the "Update Your System" closes itself.

     

    [dude67@localhost ~]$ mcc																					   
     [dude67@localhost ~]$ "/usr/sbin/drakvirt" is not executable [Virtualization] at /usr/sbin/drakconf.real line 779.
     [dude67@localhost ~]$ getting lock on urpmi																	   
     using mirror ftp://ftp.aso.ee/pub/Mandrake/official/2009.0/i586												
     retrieved http://api.mandriva.com/mirrors/basic.2009.0.i586.list media/contrib/updates media_info/MD5SUM			  
     comparing /var/cache/urpmi/partial/MD5SUM and /var/lib/urpmi/Contrib Updates/MD5SUM								   
     medium "Contrib Updates" is up-to-date																				
     using mirror ftp://ftp.aso.ee/pub/Mandrake/official/2009.0/i586													   
     retrieved $MIRRORLIST media/main/updates media_info/MD5SUM															
     comparing /var/cache/urpmi/partial/MD5SUM and /var/lib/urpmi/Main Updates (Official2009.0-2)/MD5SUM				   
     retrieving source synthesis of "Main Updates (Official2009.0-2)"...												   
     ...retrieving failed: aria2 failed: exited with 1																	 
     problem reading synthesis file of medium "Main Updates (Official2009.0-2)"											
     retrieved $MIRRORLIST media/contrib/updates media_info/MD5SUM														 
     comparing /var/cache/urpmi/partial/MD5SUM and /var/lib/urpmi/Contrib Updates (Official2009.0-10)/MD5SUM			   
     retrieving source synthesis of "Contrib Updates (Official2009.0-10)"...											   
     retrieved $MIRRORLIST media/contrib/updates media_info/20081014-095538-synthesis.hdlist.cz
     computing md5sum of retrieved source synthesis
     updated medium "Contrib Updates (Official2009.0-10)"
     retrieved $MIRRORLIST media/main/updates media_info/MD5SUM
     comparing /var/cache/urpmi/partial/MD5SUM and /var/lib/urpmi/Main Updates (Official2009.0-25)/MD5SUM
     retrieving source synthesis of "Main Updates (Official2009.0-25)"...
     ...retrieving failed: aria2 failed: exited with 1
     problem reading synthesis file of medium "Main Updates (Official2009.0-25)"
     retrieved $MIRRORLIST media/contrib/updates media_info/MD5SUM
     comparing /var/cache/urpmi/partial/MD5SUM and /var/lib/urpmi/Contrib Updates (Official2009.0-26)/MD5SUM
     medium "Contrib Updates (Official2009.0-26)" is up-to-date
     retrieved $MIRRORLIST media/non-free/updates media_info/MD5SUM
     comparing /var/cache/urpmi/partial/MD5SUM and /var/lib/urpmi/Non-free Updates (Official2009.0-27)/MD5SUM
     retrieving source synthesis of "Non-free Updates (Official2009.0-27)"...
     retrieved $MIRRORLIST media/non-free/updates media_info/synthesis.hdlist.cz
     computing md5sum of retrieved source synthesis
     retrieval of [ftp://ftp.aso.ee/pub/Mandrake/official/2009.0/i586/media/non-free/updates/media_info/synthesis.hdlist.cz] failed (md5sum mismatch)
     problem reading synthesis file of medium "Non-free Updates (Official2009.0-27)"
     using mirror ftp://distrib-coffee.ipsl.jussieu.fr/pub/linux/plf/mandriva/cfg/2009.0/i586
     retrieved http://plf.zarb.org/mirrors/2009.0.i586.list media/../../../../2009.0/free/release/binary/i586 media_info/MD5SUM
     comparing /var/cache/urpmi/partial/MD5SUM and /var/lib/urpmi/PLF Free/MD5SUM
     medium "PLF Free" is up-to-date
     retrieved http://plf.zarb.org/mirrors/2009.0.i586.list media/../../../../2009.0/non-free/release/binary/i586 media_info/MD5SUM
     comparing /var/cache/urpmi/partial/MD5SUM and /var/lib/urpmi/PLF Non-free/MD5SUM
     medium "PLF Non-free" is up-to-date
     No protocol specified
     E: client-conf-x11.c: XOpenDisplay() failed
     ALSA lib pulse.c:266:(pulse_connect) PulseAudio: Unable to connect: Connection refused
    
     unlocking urpmi database
     getting lock on urpmi
     using mirror ftp://ftp.aso.ee/pub/Mandrake/official/2009.0/i586
     using mirror ftp://ftp.aso.ee/pub/Mandrake/official/2009.0/i586
     using mirror ftp://distrib-coffee.ipsl.jussieu.fr/pub/linux/plf/mandriva/cfg/2009.0/i586
     examining synthesis file [/var/lib/urpmi/Contrib Updates/synthesis.hdlist.cz]
     examining synthesis file [/var/lib/urpmi/Main Updates (Official2009.0-2)/synthesis.hdlist.cz]
     examining synthesis file [/var/lib/urpmi/Contrib Updates (Official2009.0-10)/synthesis.hdlist.cz]
     examining synthesis file [/var/lib/urpmi/Main Updates (Official2009.0-25)/synthesis.hdlist.cz]
     examining synthesis file [/var/lib/urpmi/Contrib Updates (Official2009.0-26)/synthesis.hdlist.cz]
     examining synthesis file [/var/lib/urpmi/Non-free Updates (Official2009.0-27)/synthesis.hdlist.cz]
     examining synthesis file [/var/lib/urpmi/PLF Free/synthesis.hdlist.cz]
     examining synthesis file [/var/lib/urpmi/PLF Non-free/synthesis.hdlist.cz]
     unlocking urpmi database
     No protocol specified
     E: client-conf-x11.c: XOpenDisplay() failed
     ALSA lib pulse.c:266:(pulse_connect) PulseAudio: Unable to connect: Connection refused
    
    
     [dude67@localhost ~]$

  3. You can correct the iso by using bittorrent. Grab the corresponding torrent from here: http://torrent.mandriva.com/public/ start the torrent, let it create the torrent folder then stop it. Next copy the corrupt iso to the folder the torrent created and in your bittorrent client force a recheck of the torrent. Only the missing corrupt pieces of the iso will be downloaded.

    I didn't know this; does it really work like that? That is a very neat trick if one has a broken DVD-image (or any other large file) downloaded.

  4. Tested ian's idea of the graphic card issue...right on but heres more...I went to MCC and reconfigured the ATI RAdeon card to use the non ATI driver...in this case it was VESA....I tried the install from the download and it didn't work....I took out the ATI RAdeon card and put in the previous video card I had used...NVIDIA.......the install worked perfectly...no problems.

     

    The only conclusion I can make for those who come across the "flashing cursor" and failure on install is that your graphics card shouldn't be an ATI Radeon...which I regret buying now and will probably stick with NVIDIA going forward..

    As I do agree with you that Nvidia works better with Linux (or at least with Mandriva), I think your problem may have been solved without changing the card. It sounds a bit like this (and it perhaps is not all ATI's fault):

    One editions fail to boot to a graphical desktop (xorg.conf not created)

    See also Bug_small.png Bug #43870. Several users have reported that One editions of Mandriva Linux 2009 fail to create the file /etc/X11/xorg.conf when booting.

     

    This can then result in several possible scenarios. What happens is X.org will attempt to automatically detect the card and load the appropriate driver. If you are lucky, this will work, and you will likely never notice the problem.

     

    If X.org auto-configuration fails entirely, this results in the graphical desktop failing to start. In this case, One will boot to a text login screen.

     

    In the worst case, X.org auto-configuration finds a valid driver but it fails to work due to conflicts with the framebuffer system, resulting in an apparent failed boot: a blank screen with a cursor flashing at the top-left hand corner. There are two approaches if you find yourself in this situation. You can reboot and use the text mode, rather than graphical, boot - this option is available from the One boot screen after pressing F3. This should result in a successful graphical boot, although the most optimal driver for your hardware is most likely not being used. You can then run the graphics card configuration tool from the Mandriva Control Center to generate the /etc/X11/xorg.conf file, if you wish; you should do this if you intend to install One permanently. If you do this and then install One to your hard disk, the issue should not recur when booting the installed system.

     

    Alternatively, when you see the blank screen, press Alt+F2 to get to a text login screen. You can then log in as user root (no password) and run drakx11. Accept all the default settings in this tool, and then close it. Then run the command service -f dm, and the graphical desktop should start up correctly. If you then install One to hard disk, the issue should not recur when booting the installed system. However, it will recur each time you boot live from the One CD.

     

    If you wish to verify that this is indeed the problem you are suffering from, simply check whether the file /etc/X11/xorg.conf exists.

     

    More here:

    http://wiki.mandriva.com/en/2009.0_Errata#..._not_created.29

  5. Which kernel version are you running? (Type 'uname -r' in the konsole/terminal)

     

    At least with 'laptop' kernel versions you should have the powersave options available by default. I know, because for some reason Mandriva has for some time detected my desktop as a laptop (most likely because I had a wlan PCI card installed).

     

    But honestly, I very much doubt that the reason for your doubled electricity bill is the laptop... You should be looking somewhere else for that.

  6. Glad you got it sorted out! :thumbs:

     

    Just as an aside, I really don't like the layout of the Add/Remove Software program. Some packages just aren't visible, such as the kernels. So, at least for the forseeable future, I'll use apt/synaptic as my package manager. Perhaps someone can point out how to see ALL the packages. It is entirely possible that I am just not quite used to the Mandriva way of things yet.

    Thanks for the reply.

    owa

    You can see all the packages by choosing ALL from the drop-down menu on the left. It's (for some odd reason) set to GUI packages by default...

  7. Why do you have this kernel version?

    2.6.24.7-desktop586-1.uc2mnb

    I believe this kernel version is a test-version. Also, this kernel is for desktops, but you may want to go with a laptop kernel version. Even though there are not that many differences, it would give you better control over power control for laptops.

     

    This note is a quote from rpm.pbone.net RPM search page:

    NOTE: This is work-in-progress (WIP) development kernel.

    If you have other kernel versions installed try booting automatically to another. Go to MCC - > boot -> Set up boot system and set your default kernel to the previous one.

  8. Is there a way to re-install lilo? Yesterday I had the situation where I needed to reinstall WinXP MBR (FIXMBR) and it naturally wrote over lilo. Now, when I tried to rescue with Mandriva 2008.1 Free DVD, the only option was to reinstall grub - not lilo. I also tried 2007.1 and 2008 Powerpack DVDs, but no. I finally had to install 2008.1 again to get my PC dual booting again. The installation went fine and I didn't have to format anything else than root-partition and the RAID1 array remained intact. :thumbs:

     

    But it was a real pain to have to install the whole Mandriva 2008.1 again just to have lilo reinstalled. :wall: Seems quite odd if you can repair grub but not lilo... is it so? :huh:

  9. Thank you all for your suggestions.

     

    @mindwave: that did cross my mind and I did try booting the PC with that old HDD disconnected (disconnected the SATA cable). No help.

     

    I tried the memtest (Mandriva repos and the one from the ultimate boot cd) and the results were 0 errors. I guess that's good news. :thumbs:

     

    Then I took out the Planet WL8310 PCI card (wlan card) as I also now have ethernet cable connected to the pc and voilá: It booted fine! I tried four times in a row and it seems to boot up just fine. I'll just wait a few days before marking this thread solved.

     

    So thank you all, especially ian! :thumbs:

     

    Again the virtuals are on me :beer:

  10. Grub does allow booting from md0, just Mandriva is weird in that respect! Yes, memtest will be added to lilo, this is how I did it once with Mandrake 10.1. So should work the same now too.

    Can I use grub with this RAID1 installation as well? I quite like grub over lilo. How can I change that? Mandriva automatically changed the boot loader from grub to lilo when I made the RAID1 array during installation.

  11. You can also urpmi memtest in Mandriva, and then boot it from the grub menu to test your machine. Of course, if you can get Mandy booted first :)

    Does it work with lilo also? I was told that grub doesn't allow booting from md0 (in my RAID1 array), so I installed and am using lilo.

  12. I've been having a great deal of problems with this PC at home. This is only some 18 months old HW and it 'should' be OK and working fine but still...

     

    For several months already I've had some problems booting my Mandriva 2008.0 and 2008.1. The system would start loading, but would freeze at some point - I couldn't really tell what it is that's causing it. I always thought it was some software related problem and didn't really pay that much attention to it. The main reason beeing that I would always get it up and running even though in the worst cases it would require more than five reboots to get it running. And the WinXP home I have installed in it also seems to boot fine all the time.

     

    Then two weeks ago (or there abouts) it lost my /home partition! I did reinstall Mandriva 2008.1, but on the second boot it had lost the root-partition (/-partition). I was certain it was the HDD (500GB Seagate Barracuda 7200.10) that was acting up and getting ready to go to hard disk heaven. I then bought two 750GB Samsungs and made a RAID1 array out of them. Now it seems that I had it covered.

     

    But now it's doing weird stuff again. It takes even more times rebooting (sometimes ten isn't enough) to get Mandy up&running than it did before. It usually ends somewhere where it says it has loaded eth0 [OK] and ath0 [OK] and then freezes. Then it may produce a very long list of some checks (with some different PIDs all the time), but I really couldn't understand what it was doing... Then in the end it would give kernel panic note - or sometimes it said that some problems were solved, but the system needed to be rebooted. But I can get Mandriva running in the end (KDE desktop - if that makes any difference) and everything seems to be operating just perfect. It has never crashed (knock, knock) when Mandriva KDE is fully loaded.

     

    I have also installed WinXP home on the sda (first before the mandriva installation), but now I cannot boot there either. It seems the windows partition has also been damaged... I did the RAID1 array with Mandriva installation DVD, so I couldn't make it take the windows partition into the RAID array.

     

    Any idea or suggestions what it could be? I'm suspecting the motherboard is damaged, but is it? I wouldn't want to get a new MB just to find out that the first one is working fine and the problem is somewhere else...

     

    Oh, and the system logs don't reveal anything. I tried finding the kernel panic note or anything else from the failed boots, but there is nothing in the syslogs about that! I read them from MCC system logs (messages and syslog).

     

    This is the hw I have:

    Motherboard

    MSI 945P NEO3-F

    Processor

    Intel Core 2 Duo / E6400 2.13GHz/2MB

    HDD

    OLD: 1 x 500GB Seagate Barracuda 7200.10 SATA

    NOW: 2 x 750GB Samsung SATA2 (HD753LJ)

    Memory

    2 x Buffalo 1GB DDRII 533 MHz

×
×
  • Create New...