Jump to content
  • Announcements

    • spinynorman

      Mandriva Official Documentation

      Official documentation for extant versions of Mandriva can be found at doc.mandriva.com.   Documentation for the latest release may take some time to appear there. You can install all the manuals from the main repository if you have Mandriva installed - files are prefixed mandriva-doc.
    • paul

      Forum software upgrade   10/29/17

      So you may have noticed the forum software has upgraded !!!
      A few things that have changed. We no longer have community blogs (was never really used) We no longer have a portal page.
      We can discuss this, and decide whether it is needed (It costs money) See this thread: Here

filochard

Members
  • Content count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About filochard

  • Rank
    New Here
  1. Sound not working in 2009.1 [solved]

    It's a known bug ! bug 48690 for the soundblaster card With pulseaudio enabled, launch "pavucontrol", click on the "profiles" tab, and select "analog stereo" profile, to have a correct sound.
  2. No sound in 2009.1 GUI [solved]

    It's a little bug reported yet. It should be soon explained in Erratas bugreport 48690 quite simple to workaround you only have to do this : With pulseaudio enabled, launch "pavucontrol", click on the "profiles" tab, and select "analog stereo" profile, to have a correct sound. The default settings provide digital output....
  3. installing Nvidia Drivers [solved]

    I'm running mandriva 2007.1 but I've some things that can be useful for you! Dkms is a very useful thing that build a module for the kernel you want to use but it needs the kernel source for this kernel. on your hard disk you have 2 kernel : 2.6.22.9 and 2.6.22.12 you need to have the source packages for this 2 kernels You must know that kernel-desktop-latest-nnnnnnnnnnn.rpm is not a package (it's quite empty) but a kind of flag linked to the last kernel-version package to get automatic installation of the last packages So if the newest kernel-desktop-latest-nnnnnnnnnnn.rpm is installed you can't install the previous.... But you can install which ever kernel-desktop (without latest in the name) package you want! you need to have the source package for each kernel or at least the devel package (it's enough for dkms) for you that means : kernel-desktop-2.6.22.12-1mdv-1-1mdv2008.0.i586.rpm kernel-desktop-2.6.22.9-1mdv-1-1mdv2008.0.i586.rpm and kernel-desktop-devel-2.6.22.12-1mdv-1-1mdv2008.0.i586.rpm kernel-desktop-devel-2.6.22.9-1mdv-1-1mdv2008.0.i586.rpm or kernel-source-2.6.22.12-1mdv-1-1mdv2008.0.i586.rpm kernel-source-2.6.22.9-1mdv-1-1mdv2008.0.i586.rpm if you want to get automatic installation of the last kernel and source you need to install : kernel-desktop-latest-2.6.22.12-1mdv-1-1mdv2008.0.i586.rpm (already done on your computer) and kernel-desktop-devel-latest-2.6.22.12-1mdv-1-1mdv2008.0.i586.rpm or kernel-source-latest-2.6.22.12-1mdv-1-1mdv2008.0.i586.rpm Every time a new kernel comes on the repository it will be installed (the "latest" packages will appear with a new higher number and ask the install of the new kernel and source or devel packages. You googled and did a wrong thing by linking the 2.6.22.9 source to the 2.6.22.12 kernel !!!!!! Erase the link you created! and install the good source : it will be installed beside the 2.6.22.9 and not in its place! and correctly linked to the 2.6.22.12 kernel ...... so you will be able to choose which kernel you want at start! When you start your computer GRUB lets you choose which kernel you'll use. When loading all the components, dkms is called (if this service has been asked to start in MCC) 1) if the module is already built dkms does nothing but advertising that the module is already built 2) if it is not, then dkms buids and installs this module. There are several dkms packages : Dkms itself and dkms-xxxxx-version xxx can be nvidia for the nvidia graphic card gspcav for some webcams several version of dkms-nvidia exist! I have the same graphic card as you : FX5500 The right dkms-nvidia for this card is : dkms-nvidia-current-100.14.19-1mdv2008.0.i586.rpm don't use the dkms-nvidia-current-169.07-1mdv2008.0.i586.rpm !!!! this new dkms package is in the backport repository for both 2008.0 and 2007.1 and I tried it : it's the fist time I got a bad display since dkms exists ! I had to uninstall this new release of dkms-nvidia and to install the previous I think you have to uninstall dkms-nvidia-current-169.07-1mdv2008.0.i586.rpm and install dkms-nvidia-current-100.14.19-1mdv2008.0.i586.rpm. A little long But I hope it's clear
  4. Mandriva 2006 & panoramic screen

    scarecrow : The link I gave is (in extenso) ftp://ftp.proxad.net/mirrors/plf.zarb.org/mandriva/non-free/2006.0/i586'>ftp://ftp.proxad.net/mirrors/plf.zarb.org/mandriva/non-free/2006.0/i586 the beginning of this adress (ftp://ftp.proxad.net/mirrors/plf.zarb.org/mandriva/non-free) allows to find plf packages for older version than 2007.0 on the plf repo... they are all there! I thought it was useful for the 2006.0 version that nyme uses (easier and quicker than upgrading to 2008.0
  5. Mandriva 2006 & panoramic screen

    You don't need to compile driver from ATI site ! There's a repository for proprietary drivers at plf ftp://ftp.proxad.net/mirrors/plf.zarb.org...ree/2006.0/i586 ftp://ftp.proxad.net/mirrors/plf.zarb.org...ree/2006.0/i586 to install it you need to have your kernel source rpm and the dkms rpm installed download the ati-rpm and dkms-ati rpm from the plf site install them, dkms will automatically compile the driver for your kernel and then you can use the Mandrake control center to use the proprietary drivers for your graphic card
  6. wacom tablet and laptops

    the new linuxwacom rpms for mandriva 2007.1 (in main/backports ) are OK! Some useful details for laptops and Wacom tablet: 1 Never let mouse or stylus upon the tablet when power on : it will freeze the start of system after bios ! (if you remove them, then the MBR reading starts!) 2 Never let the mouse nor the stylus upon the tablet if you stop working and let the laptop get sleeping : when you wake it up the mouse or stylus won't be useable ! :o In that case you can always get them work correctly by using the Wacom control panel (mandriva-menu/system/configuration/hardware/Wacom control panel) if you installed the linuxwacom-controlpanel rpm. Just click on one item (stylus or cursor) then click on tool button, then click on OK, then click on EXIT and everything is allright again!
  7. mandriva 2007.1 wacom tablet udev xorg.conf

    Some useful details for laptops and Wacom tablet: 1 Never let mouse or stylus upon the tablet when power on : it will freeze the start of system after bios ! (if you remove them, then the MBR reading starts!) 2 Never let the mouse nor the stylus upon the tablet if you stop working and let the laptop get sleeping : when you wake it up the mouse or stylus won't be useable ! In that case you can always get them work correctly by using the Wacom control panel (mandriva-menu/system/configuration/hardware/Wacom control panel) if you installed the linuxwacom-controlpanel rpm. Just click on one item (stylus or cursor) then click on tool button, then click on OK, then click on EXIT and everything is allright again!
  8. Enabling 3d hardware acceleration

    Sorry about what I wrongly suggested ! I was just surprised by the fact there were two versions of dkms-nvidia and nvidia ! and didn't know that 97 version was not OK for this card! I hope that Dieter didn't break everything! Better had not to write at all when I don't know the whole thing! Sorry again!
  9. mandriva 2007.1 wacom tablet udev xorg.conf

    Hi Adam I have just exchanged some mails with Frederic that I met on bugzilla. I tested the last rpms they are OK! The problem of the tablet id is solved! Congratulations to everybody for such a good and quick job! Thanks for all and long life to Mandriva! Philippe
  10. Enabling 3d hardware acceleration

    I try it in English why 2 versions of dkms-nvidia installed? if nvidia97xxko.gz is installed and libglx.so is from nvidia96xx as it is written in your xorg.log that may not match! You should look inside /lib/modules/2.6.21-5mdv/kernel/drivers/video and see if the mod is nvidia97xx.ko.gz or nvidia96xx.ko.gz Maybe upgrading the dkms-nvidia package doesnt suppress the previous rpms! and then the xorg.conf is badly updated leaving the last path to libglx (96xx !!!!) but using the new nvidia.ko! (someone must take a look at the specfile of the srpm to verify if the updating process is well done) Better is perhaps to uninstall the 2 versions of dkms-nvidia and nvidia and instal again only the 97 version ! (You must first use MCC to configure the graphic card with the nv module before uninstall the rpms and then after having installed the good ones re-run MCC to use the dkms built proprietary kernelmodule)
  11. Enabling 3d hardware acceleration

    pourquoi 2 versions de dkms-nvidia installées ? Si le driver de la version 97 est implanté il ne fonctionne peut-être pas en accord avec le libglx.so de la version 96 qui est apparemment utilisé : le xorg.log donne en effet son chemin : /usr/lib/xorg/modules/extension/nvidia96xx/libglx.so il faudrait regarder dans /lib/modules/numérodunoyau/kernel/drivers/video si le pilote est nvidia97xx.ko.gz ou nvidia96xx.ko.gz Se peut-il que l'upgrade du paquetage se fasse sans la suppression du précédent? Se peut-il que dans ce cas la mise à jour du xorg.conf ne soit pas faite et que le chemin du module précédent persiste, à côté du nouveau pilote ? (c'est peut-être un problème lié aux rpms faudrait voir leur spec !) Il faudrait peut-être tout simplement désinstaller les rpm dkms-nvidia96xx et nvidia96xx, voire même les rpms des deux versions et refaire l'installation proprement de la seule version utilisée! (au préalable afin d'éviter toute mauvaise surprise il conviendrait de refaire une configuration de la carte avec le pilote libre nv, le temps de faire ces desinstallations et réinstallations de rpms, puis de refaire la configuration avec les pilotes propriétaires dans un dernier temps!)
  12. mandriva 2007.1 wacom tablet udev xorg.conf

    Merci spinymorman mais je reste sec pour une explication du comportement erratique de udev! Je dois dire que l'installation sur le noyau standard de la 2007.0 m'avait imposé une recherche sur google pour installer la tablette! hardrake la reliait au fichier /dev/input/event1 et j'avais dû corriger manuellement le xorg.conf!!! après avoir auparavant recompilé linuxwacom pour la 2007.0 (en modifiant le spec de la source pour pouvoir utiliser l'interface graphique de configuration, ce qui n'avait malheureusement servi à rien!!!! sinon que j'ai maintenant cet outil) . La détection matérielle est correcte, la reconnaissance et le nommage sont corrects mais cela ne permet pas l'installation out of the box pour un débuttant puisqu'un petit gag (pas facile à élucider) vient tout compromettre.... J'utilise Mandrake depuis que j'ai découvert linux (version7.2) parce qu'il a été le premier à permettre une installation facile entièrement graphique... même s'il y avait des bugs je n'ai jamais eu de catastrophe et il est dommage qu'un détail difficilement compréhensible annule des efforts de convivialité qui ont fait que ce n'est pas réservé à une minorité d'amateurs avertis (une debian ne s'installe pas aussi simplement et je n'aurais jamais fait mes premiers pas malgré 20 ans d'utilisation de microsoft qui m'avaient pourtant forcé à mettre les mains dans le cambouis : j'ai commencé avec le DOS 3.0 et les lignes de commande ne me font pas peur!) Je suis heureux d'avoir trouvé une solution et de la partager mais les questions reste posées : Faut-il faire un rapport de bug? Quelqu'un peut-il expliquer le comportement aléatoire de udev? Avis aux investigateurs. et d'avance Merci pour tous
  13. mandriva 2007.1 wacom tablet udev xorg.conf

    j'ai résolu le problème en remplaçant Option "Device" "/dev/input/event2" par Option "Device" "/dev/input/by-id/usb-Tablet_PTZ-630-event-mouse" à chaque occurence dans xorg.conf La tablette (intuos3) fonctionne pour tous les kernels!
  14. Petit problème pour un expert : J'ai une tablette graphique intuos et ai donc adapté mon fichier xorg.conf (voir en fin de message) pour l'utiliser (c'est absolument génial!) mais cela ne marchait pas pour deux autres kernels que le premier installé pour lequel j'avais dû adapter mon xorg.conf!!!! J'ai finalement trouvé la cause : dans mon xorg.conf je me référais à /dev/input/event2 Mais udev donne des liens différents, selon le noyau chargé : la tablette devient selon les cas /dev/input/event2 ou dev/inptut/event1....... Comment cela s'explique-t-il? Faut-il faire un rapport de bug Harddrake crée une référence à /dev/input/event1 devrait-il créer une référence au fichier situé dans dev/input/by-id/ ? kernel 2.6.17.14mdv [/dev/input/by-id]$ ll total 0 lrwxrwxrwx 1 root root 9 jui 7 2007 usb-Tablet_PTZ-630-event-mouse -> ../event2 lrwxrwxrwx 1 root root 9 jui 7 2007 usb-Tablet_PTZ-630-mouse -> ../mouse1 [/dev/input/by-path]$ ll total 0 lrwxrwxrwx 1 root root 9 jui 7 2007 pci-0000:00:02.0-usb-0:1:1.0-event-mouse -> ../event2 lrwxrwxrwx 1 root root 9 jui 7 2007 pci-0000:00:02.0-usb-0:1:1.0-mouse -> ../mouse1 lrwxrwxrwx 1 root root 9 jui 7 2007 platform-i8042-serio-0-event-mouse -> ../event1 lrwxrwxrwx 1 root root 9 jui 7 2007 platform-i8042-serio-0-mouse -> ../mouse0 lrwxrwxrwx 1 root root 9 jui 7 2007 platform-i8042-serio-1-event-kbd -> ../event0 lrwxrwxrwx 1 root root 9 jui 7 13:44 platform-pcspkr-event-spkr -> ../event3 kernel multimedia 2.6.17.14-mm-desktop-5mdv [/dev/input/by-id]$ ll total 0 lrwxrwxrwx 1 root root 9 jui 7 13:32 usb-Tablet_PTZ-630-event-mouse -> ../event1 lrwxrwxrwx 1 root root 9 jui 7 13:32 usb-Tablet_PTZ-630-mouse -> ../mouse0 [/dev/input/by-path]$ ll total 0 lrwxrwxrwx 1 root root 9 jui 7 13:32 pci-0000:00:02.0-usb-0:1:1.0-event-mouse -> ../event1 lrwxrwxrwx 1 root root 9 jui 7 13:32 pci-0000:00:02.0-usb-0:1:1.0-mouse -> ../mouse0 lrwxrwxrwx 1 root root 9 jui 7 13:32 platform-i8042-serio-0-event-mouse -> ../event3 lrwxrwxrwx 1 root root 9 jui 7 13:32 platform-i8042-serio-0-mouse -> ../mouse1 lrwxrwxrwx 1 root root 9 jui 7 13:32 platform-i8042-serio-1-event-kbd -> ../event0 lrwxrwxrwx 1 root root 9 jui 7 13:32 platform-pcspkr-event-spkr -> ../event2 kernel tmb 2.6.21.5-tmb-desktop-1mdv [/dev/input/by-id]$ ll total 0 lrwxrwxrwx 1 root root 9 jui 7 13:56 usb-Tablet_PTZ-630-event-mouse -> ../event1 lrwxrwxrwx 1 root root 9 jui 7 2007 usb-Tablet_PTZ-630-mouse -> ../mouse0 [/dev/input/by-path]$ ll total 0 lrwxrwxrwx 1 root root 9 jui 7 13:56 pci-0000:00:02.0-usb-0:1:1.0-event-mouse -> ../event1 lrwxrwxrwx 1 root root 9 jui 7 2007 pci-0000:00:02.0-usb-0:1:1.0-mouse -> ../mouse0 lrwxrwxrwx 1 root root 9 jui 7 13:56 platform-i8042-serio-0-event-kbd -> ../event0 lrwxrwxrwx 1 root root 9 jui 7 13:56 platform-i8042-serio-1-event-mouse -> ../event3 lrwxrwxrwx 1 root root 9 jui 7 13:56 platform-i8042-serio-1-mouse -> ../mouse1 lrwxrwxrwx 1 root root 9 jui 7 13:56 platform-pcspkr-event-spkr -> ../event2 extrait: du xorg.conf Section "InputDevice" Identifier "Eraser1" Driver "wacom" Option "Device" "/dev/input/event2" Option "Type" "eraser" Option "Mode" "Absolute" Option "Keepshape" "on" Option "USB" "on" Option "Tilt" "on" Option "Presscurve" "0,0,100,100" Option "Threshold" "10" EndSection Section "InputDevice" Identifier "Cursor1" Driver "wacom" Option "Device" "/dev/input/event2" Option "Type" "cursor" Option "Mode" "Relative" Option "USB" "on" Option "Speed" "3" EndSection Section "InputDevice" Identifier "Stylus1" Driver "wacom" Option "Device" "/dev/input/event2" Option "Type" "stylus" Option "Mode" "Absolute" Option "USB" "on" Option "Tilt" "on" Option "Presscurve" "0,0,100,100" Option "Threshold" "10" EndSection Section "InputDevice" Identifier "Pad1" Driver "wacom" Option "Device" "/dev/input/event2" Option "Type" "pad" Option "USB" "on" EndSection
×