Jump to content

Richard1098

Members
  • Posts

    34
  • Joined

  • Last visited

Posts posted by Richard1098

  1. I am unable to boot 2008.1 normally. When booting in safe mode, the following message is displayed:

     

    Sound server informational message

    Error while initializing the sound driver

    device: default can't be opened for playback (connection refused)

    the sound server will continue using the null output device

  2. Soon after starting Gnome, the panel crashes. This is the error message:

     

     

    Distribution: Mandriva Linux release 2008.1 (Official) for i586

    Gnome Release: 2.22.0 2008-03-26 (Mandriva)

    BugBuddy Version: 2.22.0

     

    System: Linux 2.6.24.4-desktop-3mnb #1 SMP Mon May 5 18:09:09 EDT 2008 i686

    X Vendor: The X.Org Foundation

    X Vendor Release: 10400090

    Selinux: No

    Accessibility: Disabled

    GTK+ Theme: Ia Ora Blue

    Icon Theme: Neu

     

    Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0

    CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

     

     

     

    ----------- .xsession-errors ---------------------

    SIOCETHTOOL: Operation not supported

    SIOCETHTOOL: Operation not supported

    SIOCETHTOOL: Operation not supported

    (gnome-panel:7119): GLib-GObject-WARNING **: gsignal.c:1669: signal `set-current' is invalid for instance `0x8181b98'

    (gnome-panel:7119): GLib-GObject-WARNING **: gsignal.c:1669: signal `set-current' is invalid for instance `0x834e800'

    (gnome-panel:7119): GLib-GObject-WARNING **: gsignal.c:1669: signal `set-current' is invalid for instance `0x834e840'

    (gnome-panel:7119): GLib-GObject-WARNING **: gsignal.c:1669: signal `set-current' is invalid for instance `0x834e880'

    (gnome-panel:7119): GLib-GObject-WARNING **: gsignal.c:1669: signal `set-current' is invalid for instance `0x834e8c0'

    (gnome-panel:7119): GLib-GObject-WARNING **: gsignal.c:1669: signal `set-current' is invalid for instance `0x834e900'

    --------------------------------------------------

     

     

    Seems to have been caused by a recent update of one of the following:

    gnome-themes-extras

    timezone

    timezone-java

  3. gtkpod 0.99.12 (with libgpod 0.6.0) does work with current generation iPod Nanos, and I have been using it without issue for several months. You will need to set up your iPod's directories using gtkpod, and may need to modify its iPod_Control/Device/SysInfo file as detailed in the following readme contained in the libgpod 0.6 source file available from sourceforge.

     

     

    Starting with the iPod Classics and the Video Nanos, libgpod needs an additional configuration step to correctly modify the iPod content. libgpod needs to know the so-called iPod "firewire id", otherwise the iPod won't recognize what libgpod wrote to it and will behave as if it's empty.

     

    There are two ways to set up the iPod to make libgpod able to find its firewire id.

     

    The 1st one is mostly automated. First, make sure you have libsgutils installed before running configure/autogen.sh. If you built libgpod without it, install it and run configure/make/make install. You should now have an ipod-read-sysinfo-extended tool available. Run it with the iPod device path (eg /dev/sda) and the iPod mount point (eg /mnt/ipod) as arguments. This may

    require root privileges. ipod-read-sysinfo-extended will read an XML file from the iPod and write it as /mnt/ipod/iPod_Control/Device/SysInfoExtended. See http://ipodlinux.org/Device_Information for more details about the method used. Having that file is enough for libgpod to figure out the iPod firewire id.

     

    The 2nd method requires more manual intervention. First, you need to get your firewire id manually. To do that, run "sudo lsusb -v | grep -i Serial" (without the "") with your iPod plugged in, this should print a 16 character long string like 00A1234567891231. For an iPod Touch, this number will be much longer than 16 characters, the firewire ID is constituted by the first 16 characters. Once you have that number, create/edit /mnt/ipod/iPod_Control/Device/SysInfo (if your iPod is mounted at /mnt/ipod). Add to that file the line below:

     

    FirewireGuid: 0xffffffffffffffff

     

    (replace ffffffffffffffff with the string you obtained at the previous step and don't forget the trailing 0x before the string). Save that file, and you should be all set. Be careful when using apps which lets you manually specify which iPod model you own, they may overwrite that file when you do that. So if after doing that libgpod still seems to write invalid content to the iPod, double-check the content of that SysInfo file to make sure the FirewireGuid line you added isn't gone. If that happens, readd it to the end of the file, and make sure libgpod rewrite the iPod content.

     

    Once that is done, if you compiled libgpod from source, you can test that libgpod can find the firewire ID on your iPod by running libgpod/tests/test-firewire-id /ipod/mount/point

  4. I need to reinstall lilo.

     

    I have Mandriva on my second hard drive (/dev/sdb), with SUSE on the primary drive (/dev/sda). After using mandrake control center to change from lilo to GRUB my system no longer boots. I have tried using the reinstall boot-loader facility in system rescue, but this fails to result in a bootable system. Is it possible to reinstall lilo using a system upgrade, without altering the system otherwise. Alternatively, is it possible to reinstall lilo directly from the system installer.

  5. could you post your xorg.conf file?

     

     

    # File generated by XFdrake (rev 142098)

     

     

    Section "Monitor"

    Identifier "monitor1"

    VendorName "Plug'n Play"

    ModelName "SyncMaster"

    HorizSync 30.0 - 81.0

    VertRefresh 56.0 - 75.0

    ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync

    ModeLine "768x576" 50.0 768 832 846 1000 576 590 595 630

    ModeLine "768x576" 63.1 768 800 960 1024 576 578 590 616

    EndSection

     

    Section "Device"

    Identifier "device1"

    VendorName "nVidia Corporation"

    BoardName "NVIDIA GeForce FX - GeForce 7950"

    Driver "nvidia"

    Option "DPMS"

    Option "AddARGBGLXVisuals"

    EndSection

     

    Section "Screen"

    Identifier "screen1"

    Device "device1"

    Monitor "monitor1"

    DefaultColorDepth 24

     

    Subsection "Display"

    Depth 8

    Modes "1280x1024" "1152x864" "1024x768" "832x624" "800x600" "640x480" "480x360" "320x240"

    EndSubsection

     

    Subsection "Display"

    Depth 15

    Modes "1280x1024" "1152x864" "1024x768" "832x624" "800x600" "640x480" "480x360" "320x240"

    EndSubsection

     

    Subsection "Display"

    Depth 16

    Modes "1280x1024" "1152x864" "1024x768" "832x624" "800x600" "640x480" "480x360" "320x240"

    EndSubsection

     

    Subsection "Display"

    Depth 24

    Modes "1280x1024" "1152x864" "1024x768" "832x624" "800x600" "640x480" "480x360" "320x240"

    EndSubsection

    EndSection

    # File generated by XFdrake (rev 142098)

     

    # nvidia-xconfig: X configuration file generated by nvidia-xconfig

    # nvidia-xconfig: version 1.0 (buildmeister@builder3) Thu Dec 13 19:09:35 PST 2007

     

    # File generated by XFdrake (rev 142098)

    # **********************************************************************

    # Refer to the xorg.conf man page for details about the format of

    # this file.

    # **********************************************************************

     

    Section "ServerLayout"

    Identifier "layout1"

    InputDevice "Keyboard1" "CoreKeyboard"

    InputDevice "Mouse1" "CorePointer"

    Screen "screen1"

    EndSection

     

    Section "Files"

    ModulePath "/usr/lib/xorg/modules/extensions/nvidia97xx"

    ModulePath "/usr/lib/xorg/modules"

    FontPath "unix/:-1"

    FontPath "/usr/share/fonts/misc:unscaled"

    EndSection

     

    Section "Module"

    Load "dbe" # Double-Buffering Extension

    Load "v4l" # Video for Linux

    Load "extmod"

    Load "type1"

    Load "freetype"

    Load "glx" # 3D layer

    EndSection

     

    Section "ServerFlags"

    #DontZap # disable <Crtl><Alt><BS> (server abort)

    #DontZoom # disable <Crtl><Alt><KP_+>/<KP_-> (resolution switching)

     

    # allows the server to start up even if the mouse does not work

    Option "allowmouseopenfail"

    EndSection

     

    Section "InputDevice"

    Identifier "Keyboard1"

    Driver "kbd"

    Option "XkbModel" "pc105"

    Option "XkbLayout" "us"

    Option "XkbOptions" "compose:rwin"

    EndSection

     

    Section "InputDevice"

    Identifier "Mouse1"

    Driver "mouse"

    Option "Protocol" "ExplorerPS/2"

    Option "Device" "/dev/mouse"

    EndSection

     

    Section "Extensions"

    Option "Composite"

    EndSection

  6. After upgrading nVidia drivers on 2007.1 nvidia-settings no longer runs correctly. The following error is reported on startup: " You do not appear to be using the NVIDIA X driver. Please edit your X configuration file (just run `nvidia-xconfig` as root), and restart the X server. " X server is using the nVidia drivers, as the nVidia splash-screen displays on start up, and all Xorg.conf file driver references refer to "nvidia".

     

    Any thoughts?

  7. I need the location of update mirrors for 2007.1 Official so I can manually enter them in MCC.

     

    Each time I try to download details via the control center, I get the following error: "There was an error downloading the mirror list: Couldn't connect. The network or the Mandriva website may be unavailable. Please try again later."

  8. I have several mandy-partitions on the same physical HDD (2005LE, 2006, 2007) and each has a large amount of personal data in its /home directory, all essentially the same. Is it possible to place this data in a separate partition (/opt or /usr spring to mind) which can be accessed by all versions; this would save a lot of disk-space and time following installation of the next mandy (2008, for example). Thanks.

     

    Why not create share folders in each distribution, then modify /etc/fstab to mount the /home from the other distributions at those shared folders. I currently do that to allow file transfer between SUSE 10.3 and Mdv 2007.1 loaded on the same PC.

  9. Too bad for Apple having the 2nd and 3rd generation Nano's fimrware encrypted. Being tempted by their stylish design I might get one of them, provided I could flash it with RockBox firmware (as their own is absolutely limited and useless). Since it's not possible (even if it was, there would be legal implications)... they are losing a potential buyer.

     

    I've noticed two things about the gen 3 Nano: yes, there is lots of eye candy, but time between recharges is very, very short.

  10. It turns out that loading any music onto the iPod that did not originate from iTunes is intentionally blocked by Apple. There has been a hack to get around this, but the hack seems to be no longer available.

     

    I've already given the iPod away. Sigh.... It and related items were just a bit under $300.

     

    I got a Creative Zen V Plus this morning, with 8 GB. Now I am trying to figure out how to get music onto it. When I plug it into a USB port, I don't get a mounting notification like I did with the iPod.

     

    What happened to the "good old days" when you could just copy music files to the device just like it was a disk drive, without requiring all types of bizarre mp3 software on the computer.?

     

    I still don't see how to get music onto this device, but I guess this should be another thread.

     

    Generation 3 Nanos are now supported. Just upgrade libgpod to version 0.6 and gtkpod to 99.12. Both are now available in rpm format. You will also need to install libgpod3-0.6. The best places to search for the rpms are pbone.net or rpmseek.com.

  11. Please post the output of
    uname -a

    rpm -qa | grep kernel

    rpm -qa | grep nvidia

    [richard@localhost Desktop]$ uname -a

    Linux localhost 2.6.17-14mdv #1 SMP Wed May 9 21:11:43 MDT 2007 i686 Intel® Core2 CPU 6600 @ 2.40GHz GNU/Linux

    [richard@localhost Desktop]$ rpm -qa | grep kernel

    kernel-source-stripped-2.6.17.13mdv-1-1mdv2007.1

    kernel-source-stripped-2.6.17.14mdv-1-1mdv2007.1

    kernel-2.6.17.13mdv-1-1mdv2007.1

    kernel-latest-2.6.17-14mdv

    kernel-source-2.6.17.14mdv-1-1mdv2007.1

    kernel-source-stripped-latest-2.6.17-14mdv

    nvidia97xx-kernel-2.6.17-13mdv-9755-1mdk

    kernel-source-2.6.17.13mdv-1-1mdv2007.1

    kernel-2.6.17.14mdv-1-1mdv2007.1

    [richard@localhost Desktop]$ rpm -qa | grep nvidia

    dkms-nvidia97xx-1.0-9755.1mdv2007.1

    nvidia97xx-1.0-9755.1mdv2007.1

    nvidia97xx-kernel-2.6.17-13mdv-9755-1mdk

    [richard@localhost Desktop]$

  12. I have Mdv 2007.1 power pack. I've downloaded the latest:

     

    dkms-nvidia and

    nvidia

     

    rpms from PLF. When I try to update them with rpm, I get the following:

     

     

     

    Error! Could not find module source directory.

    Directory: /usr/src/nvidia97xx-100.14.11-1plf2007.1 does not exist.

     

    Error! DKMS tree does not contain: nvidia97xx-100.14.11-1plf2007.1

    Build cannot continue without the proper tree.

     

    Error! DKMS tree does not contain: nvidia97xx-100.14.11-1plf2007.1

    Build cannot continue without the proper tree.

    [root@localhost nVidia]#

  13. I've just installed MDV 2007 Spring on an Intel Core 2 Duo machine. It has install x86_64 rpms Unfortunately, same applications like parallels don't seem to be able to compile against the x86_64 kernel source.

     

    How can I install MDV 2007 Spring as an x86 install?

×
×
  • Create New...