Jump to content

kkrekula

Members
  • Posts

    33
  • Joined

  • Last visited

Posts posted by kkrekula

  1. It seems like the problem was the kernel. On my PVR system (mini-itx Epia-M) Mandrake 10.1 installed a SMP kernel (kernel-i586-up-1GB-2.6.8.1.12mdk). When trying to load the compiled Ivtv drivers I got the error message

     

    FATAL: Error inserting ivtv (/lib/modules/2.6.8.1-12mdk-i586-up-1GB/kernel/drivers/misc/ivtv.ko): Invalid module format

     

    I tried to install the standard kernel, but it doesn't boot at all on my Epia-M.

     

    So I installed the PVR350 card into my desktop PC (uses the standard Mdk 10.1 Official kernel) and then the Ivtv installation procedure here http://www.byopvr.com/Journal+index-jop-br...iew-id-112.html worked perfectly! No problem with the module loading.

     

    I guess there are some compiling parameters to change, in order to get self-compiled modules working on my Mini-Itx system. However, I will first see if MythTV works on my desktop PC.

     

    /Kenneth

  2. Try installing the drivers with the make install command instead of copying them by hand (in the /ivtv/drivers folder). That way you're sure everything gets correctly installed. Don't forget to run depmod -ae after you have deleted the folders and after you have given 'make install'. It tells the kernel what modules are available.

     

    That's what I do. The problem is that "make install" puts the new drivers into the directory "/lib/modules/2.6.8.1-12mdkcustom/extra/" which the system doesn't seem to like as it doesn't find them.

     

    /Kenneth

  3. I found this article about installing Mythtv on Mandrake 10.1:

     

    http://www.byopvr.com/Journal+index-jop-br...iew-id-112.html

     

    It suggests to delete the Mdk 10.1 Ivtv drivers and copy the new self-compiled drivers into the /lib/modules/2.6.8.1-12mdk/kernel/drivers/misc directory.

     

    However, when I do the "modprobe ivtv" it does not like that the new drivers are in ".ko" format... The Mdk drivers are in ".ko.gz" format.

     

    I tried to gzip the .ko drivers into .ko.gz format but modprobe still does not like them... What kind of trick do I need to do?

     

    Regards,

    Kenneth

  4. Performed a clean install of Mandrake 10.1 (official) and yes I can confirm that the ivtv driver is already in and can be loaded with "modprobe ivtv".

     

    But in my case, the tuner in my PVR350 seems to be a recent model not supported by the IVTV 0.1.9 driver. So I have no choice but trying to install a newer driver version.

     

    Now to my problem: when I do the "make install" of the new driver (I am trying the 0.3.x series) it installs into a new directory "/lib/modules/2.6.8.1-12mdkcustom/extra/"

     

    [root@localhost /]# ls -l /lib/modules/2.6.8.1-12mdkcustom/extra/

    totalt 340

    -rw-r--r-- 1 root root 31846 dec 4 00:03 cx25840.ko

    -rw-r--r-- 1 root root 38008 dec 4 00:03 ivtv-fb.ko

    -rw-r--r-- 1 root root 178264 dec 4 00:03 ivtv.ko

    -rw-r--r-- 1 root root 31832 dec 4 00:03 msp3400.ko

    -rw-r--r-- 1 root root 14750 dec 4 00:03 saa7115.ko

    -rw-r--r-- 1 root root 15096 dec 4 00:03 saa7127.ko

    -rw-r--r-- 1 root root 14777 dec 4 00:03 tveeprom.ko

    -rw-r--r-- 1 root root 6774 dec 4 00:03 wm8775.ko

     

    How do I get this driver to load instead of the the older driver? When I "modprobe ivtv" I still get the message:

     

    ivtv: version 0.1.9 (0.1.10pre1) loading

     

     

    Regards,

    Kenneth

  5. http://mandrakeusers.org/index.php?showtopic=19409&st=15

     

    You're the second one mentioning that. I doubt Mandrake has the ivtv module. It won't work without the firmware so why include it? And I've never heard of it. And 0.19 is old and unpatched only usable on 2.4 kernel. :)

     

     

    Well, have a look in the contents of kernel-source-2.6-2.6.8.1-12mdk and you will find:

     

    ‎/usr/src/linux-2.6.8.1-12mdk/3rdparty/ivtv

    ‎/usr/src/linux-2.6.8.1-12mdk/3rdparty/ivtv/Kconfig

    ‎/usr/src/linux-2.6.8.1-12mdk/3rdparty/ivtv/Makefile

    ‎/usr/src/linux-2.6.8.1-12mdk/3rdparty/ivtv/audiochip.h

    ‎/usr/src/linux-2.6.8.1-12mdk/3rdparty/ivtv/compat.h

    ‎/usr/src/linux-2.6.8.1-12mdk/3rdparty/ivtv/id.h

    ‎/usr/src/linux-2.6.8.1-12mdk/3rdparty/ivtv/ivtv-api.c

    ‎/usr/src/linux-2.6.8.1-12mdk/3rdparty/ivtv/ivtv-driver.c

    ‎/usr/src/linux-2.6.8.1-12mdk/3rdparty/ivtv/ivtv-fb.c

    ‎/usr/src/linux-2.6.8.1-12mdk/3rdparty/ivtv/ivtv-i2c.c

    ‎/usr/src/linux-2.6.8.1-12mdk/3rdparty/ivtv/ivtv.h

    ‎/usr/src/linux-2.6.8.1-12mdk/3rdparty/ivtv/msp3400.c

    ‎/usr/src/linux-2.6.8.1-12mdk/3rdparty/ivtv/msp3400.h

    ‎/usr/src/linux-2.6.8.1-12mdk/3rdparty/ivtv/saa7115.c

    ‎/usr/src/linux-2.6.8.1-12mdk/3rdparty/ivtv/saa7127.c

    ‎/usr/src/linux-2.6.8.1-12mdk/3rdparty/ivtv/saa7127.h

    ‎/usr/src/linux-2.6.8.1-12mdk/3rdparty/ivtv/tuner.h

    ‎/usr/src/linux-2.6.8.1-12mdk/3rdparty/ivtv/tveeprom.c

     

    /Kenneth

  6. I have tried following your advice, but there seems to one problem:

     

    The Mandrake 10.1 already seem to have the Ivtv driver (0.1.9) and installing a newer one (0.2.0 or 0.3.0) does not help, as the 0.1.9 driver seem to be the one used...

     

    What does you log show? My log shows that driver 0.1.9 is used...

     

    So how does one get the 0.2.0 or 0.3.0 driver to replace the built-in?

     

    /Kenneth

  7. For whatever reason, now my sound has disappeared - what gives with that....

    I mean system sound - ALSA

     

    After fiddling around with OSS/ALSA settings, I lost my system notifications sounds in KDE.

     

    After some "digging" I found that .kde/share/config/knotifyrc (in my home directory) had funny content. I just deleted this file and restarted and all was OK again.

     

    This is what it should look like on a working system (when it didn't work, all tha parameters were set to "false"):

     

    [startProgress]

    Arts Init=true

    KNotify Init=true

    Use Arts=true

     

    /Kenneth

  8. ATI seem to make the best graphics cards, good performance and makes less noise.

     

    BUT I'm not sure about the Linux compatibilty.... That's why I bought an NVidia card one month ago.

     

    /Kenneth

  9. [i find that most of the newer mobile phones do everything that a PDA was traditionally used for, and most of them are 'free' with a contract. The Sony-Ericsson's are awesome.

     

    I have a SE T610, I sync it with Evolution using Multisync with the IrMC plugin, an Epox  Bluetooth dongle and I transfer files with Gnome-Obex-Server (bluetooth).

    Yes, I agree. That's what I would have bought for work (e.g. an Ericsson P900) if I could choose. This would mean one less device to carry. And the phone is always with me anyway.

     

    So pure PDAs (without phone or wireless LAN) will disappear from the market soon.

     

    /Kenneth

  10. I have a Tungsten T3, which is nice (good screen, fast and easy to use). I haven't tried to sync it in Linux yet, but at least the older Palms used to work fine with Linux.

     

    At least in the old days, the CE devices were very battery-hungry. The Palms could go forever without needing a re-charge.

     

    If I would buy a PDA myself, I would like to try a Sharp Zaurus.

     

    /Kenneth

  11. Yes, the Beta runs really well on my system also. As I have a Nforce motherboard, I am happy to see that the new "forcedeth" driver is included, so I don't have to install Nvidias Nforce drivers.

     

    Install the missing packages from a Cooker mirror. The new Kopete is really nice and Kmail seem to have improved also.

     

    /Kenneth

  12. I have also experienced this phenomena many times before... On my main system (Mdk 9.2) the fonts are beautiful without any tweaking.

     

    However, on my Laptop which also worked perfectly with Mdk 9.2 (and with PcLinuxOS Preview 4), I am trying out the Cooker and now I get fuzzy fonts everywhere... I have no idea why this happens...

     

    /Kenneth

  13. kkrekula,

     

    There seems to be a new test kernel that could solve the problem with NForce 2 MBs. I found it when reading the mandrake-expert mailing list archives

    http://archives.mandrakelinux.com/expert/2...10/msg00892.php

     

    Let me know whether it solves your athcool problem

     

    Using the latest official kernel (2.4.22-18mdk) I tried to:

    - enable ACPI in the boot options

    - enable the ACPI service

     

    But I still get the same result. As soon as I start athcool 0.3.1 ("athcool on"), my computer freezes (I have to perform a hard reset).

     

    /Kenneth

  14. Hi.

     

    I have used Athcool 0.2 with Mandrake 9.1 successfully for many months on my NForce system.

     

    Now with Mandrake 9.2, I installed Athcool 0.3.1 from contrib and when I start it it just freezes my computer.

     

    Is this due to the Mandrake 9.2 or the Athcool version?

     

    /Kenneth

  15. On the two different systems that I have installed Mdk 9.1 on, Kmix gets confused when I select to use the Alsa driver: The Master volume is remembered by the system when rebooting, but Kmix is set everytime to Max. volume!

     

    So I went back to the OSS driver where everything works as before (the last volume is remembered my Kmix, even after reboot)...

     

    /Kenneth

×
×
  • Create New...