Duel Hauppauge HVR-1600
I just bought two Hauppauge HVR-1600 cards and I'm trying to set them up in
Mythdorra 5. I have the cx18 drivers installed but it is only initializing one
card. I'm getting the following message when I do a dmesg | grep cx18. Has
anyone ran accross this problem before with duel cards of the same model and if
so, how do I fix it? Any help will be greatly appreciated.
Thanks,
Tom Moore
Houston, TX
dmesg | grep cx18
cx18: Start initialization, version 1.0.1
cx18-0: Initializing card #0
cx18-0: Autodetected Hauppauge card
cx18-0: Unreasonably low latency timer, setting to 64 (was 32)
cx18-0: cx23418 revision 01010000 (B)
cx18-0: Autodetected Hauppauge HVR-1600
cx18-0: VBI is not yet supported
tuner 2-0061: chip found @ 0xc2 (cx18 i2c driver #0-1)
cs5345 1-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
cx18-0: Disabled encoder IDX device
cx18-0: Registered device video0 for encoder MPEG (2 MB)
DVB: registering new adapter (cx18)
cx18-0: DVB Frontend registered
cx18-0: Registered device video32 for encoder YUV (2 MB)
cx18-0: Registered device video24 for encoder PCM audio (1 MB)
cx18-0: Initialized card #0: Hauppauge HVR-1600
cx18-1: Initializing card #1
cx18-1: Autodetected Hauppauge card
cx18-1: Unreasonably low latency timer, setting to 64 (was 32)
cx18-1: ioremap failed, perhaps increasing __VMALLOC_RESERVE in page.h
cx18-1: or disabling CONFIG_HIGHMEM4G into the kernel would help
cx18-1: Error -12 on initialization
cx18: probe of 0000:02:04.0 failed with error -12
cx18: End initialization
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 36 lines · Tom Moore
I just bought two Hauppauge HVR-1600 cards and I'm trying to set them up in
Mythdorra 5. I have the cx18 drivers installed but it is only initializing one
card. I'm getting the following message when I do a dmesg | grep cx18. Has
anyone ran accross this problem before with duel cards of the same model and if
so, how do I fix it? Any help will be greatly appreciated.
Thanks,
Tom Moore
Houston, TX
dmesg | grep cx18
cx18: Start initialization, version 1.0.1
cx18-1: Initializing card #1
cx18-1: Autodetected Hauppauge card
cx18-1: Unreasonably low latency timer, setting to 64 (was 32)
cx18-1: ioremap failed, perhaps increasing
__VMALLOC_RESERVEinpage.h
Quoted 8 lines
cx18-1: or disabling
CONFIG_HIGHMEM4Ginto the kernel would helpcx18-1: Error -12 on initialization
cx18: probe of 0000:02:04.0 failed with error -12
cx18: End initialization
You're out of vmalloc address space. Each cx18 needs 64 MB of vmalloc space for MMIO mappings.
Do this:
$ cat /proc/meminfo | grep Vmalloc
Edit your bootloader's config file to add a 'vmalloc=xxxM' option to your kernel commandline. Use a value that is 128M greater than your current VmallocTotal.
Regards,
Andy
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Thanks Andy for the reply.
I did what you said and now I'm getting an memory error message when booting
The message reads:
Initrd extends beyond end of memory (0x37fef23a > 0x30000000)
I tried lowering the amount but anything over 128M and I get the error message.
Here is my config file:
# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/sda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title MythDora (2.6.24.4-64.fc8) root (hd0,0) kernel /vmlinuz-2.6.24.4-64.fc8 ro root=/dev/VolGroup00/LogVol00 rhgb quiet vmalloc=256M initrd /initrd-2.6.24.4-64.fc8.img
-----Original Message-----
From: Andy Walls [mailto:[email protected]]
Sent: Tuesday, October 14, 2008 7:16 PM
To: Tom Moore
Cc: [email protected]
Subject: Re: [linux-dvb] Duel Hauppauge HVR-1600
Quoted 36 lines · Tom Moore
I just bought two Hauppauge HVR-1600 cards and I'm trying to set them up in
Mythdorra 5. I have the cx18 drivers installed but it is only initializing one
card. I'm getting the following message when I do a dmesg | grep cx18. Has
anyone ran accross this problem before with duel cards of the same model and if
so, how do I fix it? Any help will be greatly appreciated.
Thanks,
Tom Moore
Houston, TX
dmesg | grep cx18
cx18: Start initialization, version 1.0.1
cx18-1: Initializing card #1
cx18-1: Autodetected Hauppauge card
cx18-1: Unreasonably low latency timer, setting to 64 (was 32)
cx18-1: ioremap failed, perhaps increasing
__VMALLOC_RESERVEinpage.h
Quoted 8 lines
cx18-1: or disabling
CONFIG_HIGHMEM4Ginto the kernel would helpcx18-1: Error -12 on initialization
cx18: probe of 0000:02:04.0 failed with error -12
cx18: End initialization
You're out of vmalloc address space. Each cx18 needs 64 MB of vmalloc space for MMIO mappings.
Do this:
$ cat /proc/meminfo | grep Vmalloc
Edit your bootloader's config file to add a 'vmalloc=xxxM' option to your kernel commandline. Use a value that is 128M greater than your current VmallocTotal.
Regards,
Andy
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Tom,
Just a note: please don't top post. Per list convention, please just respond in-line.
Quoted 7 lines · Tom Moore
Thanks Andy for the reply.
I did what you said and now I'm getting an memory error message when booting
The message reads:
Initrd extends beyond end of memory (0x37fef23a>0x30000000)
Well, that's a new one on me.
Quoted 2 lines
I tried lowering the amount but anything over 128M and I get the error message.
So since vmalloc addresses are used for dynamic kernel mappings for things like loadable module code and for IO mappings, 128 MB of addresses will never be sufficient to support two cards that want 64 MB of addresses each, along with other kernel vmalloc needs.
So until this problem is resolved, you won't get the second card running. The good news is, the problem appears to be fixable with the proper kernel configuration.
The driver did make some suggestions in it's original error message:
Quoted 5 lines
Quoted 5 lines
cx18-1: ioremap failed, perhaps increasing
__VMALLOC_RESERVEinpage.hcx18-1: or disabling
CONFIG_HIGHMEM4Ginto the kernel would helpcx18-1: Error -12 on initialization
both of which you could try. They involve building a custom kernel.
There may be other ways, but I'm no expert in Linux memory management. I suspect someone over on the LKML is.
To help solve your problem, people will likely need to see the output of 'cat /proc/meminfo' and 'dmesg' for your system. If I had that info, I could try to help, I'm not sure I'd be able to help effectively.
Regards,
Andy
Quoted 80 lines
Here is my config file:
# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/sda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title MythDora (2.6.24.4-64.fc8) root (hd0,0) kernel /vmlinuz-2.6.24.4-64.fc8 ro root=/dev/VolGroup00/LogVol00 rhgb quiet vmalloc=256M initrd /initrd-2.6.24.4-64.fc8.img-----Original Message-----
From: Andy Walls [mailto:[email protected]]
Sent: Tuesday, October 14, 2008 7:16 PM
To: Tom Moore
Cc: [email protected]
Subject: Re: [linux-dvb] Duel Hauppauge HVR-1600Quoted 36 lines · Tom Moore
I just bought two Hauppauge HVR-1600 cards and I'm trying to set them up in
Mythdorra 5. I have the cx18 drivers installed but it is only initializing one
card. I'm getting the following message when I do a dmesg | grep cx18. Has
anyone ran accross this problem before with duel cards of the same model and if
so, how do I fix it? Any help will be greatly appreciated.
Thanks,
Tom Moore
Houston, TX
dmesg | grep cx18
cx18: Start initialization, version 1.0.1
cx18-1: Initializing card #1
cx18-1: Autodetected Hauppauge card
cx18-1: Unreasonably low latency timer, setting to 64 (was 32)
cx18-1: ioremap failed, perhaps increasing
__VMALLOC_RESERVEinpage.hQuoted 8 lines
cx18-1: or disabling
CONFIG_HIGHMEM4Ginto the kernel would helpcx18-1: Error -12 on initialization
cx18: probe of 0000:02:04.0 failed with error -12
cx18: End initialization
You're out of vmalloc address space. Each cx18 needs 64 MB of vmalloc space for MMIO mappings.
Do this:
$ cat /proc/meminfo | grep Vmalloc
Quoted 10 lines
Edit your bootloader's config file to add a 'vmalloc=xxxM' option to your kernel commandline. Use a value that is 128M greater than your current VmallocTotal.
Regards,
Andy
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
I demand that Andy Walls may or may not have written...
Quoted 11 lines · Tom Moore
Quoted 5 lines
Thanks Andy for the reply.
I did what you said and now I'm getting an memory error message when booting
The message reads:
Initrd extends beyond end of memory (0x37fef23a>0x30000000)Well, that's a new one on me.
Quoted 2 lines
I tried lowering the amount but anything over 128M and I get the error message.
[snip]
Quoted 9 lines
The driver did make some suggestions in its original error message:
Quoted 3 lines
Quoted 3 lines
cx18-1: ioremap failed, perhaps increasing
__VMALLOC_RESERVEinpage.h
cx18-1: or disablingCONFIG_HIGHMEM4Ginto the kernel would help
cx18-1: Error -12 on initializationboth of which you could try. They involve building a custom kernel.
There may be other ways, but I'm no expert in Linux memory management. I suspect someone over on the LKML is.
I'd go straight for an amd64 kernel, so long as the hardware supports it. That way, the 1GB/4GB/64GB stuff becomes irrelevant.
[snip]
Signature · 10 lines
| Darren Salt | linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | <URL:http://www.youmustbejoking.demon.co.uk/> (PGP 2.6, GPG keys) Sooner or later, the worst possible set of circumstances is bound to occur. _______________________________________________ linux-dvb mailing list [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
-----Original Message-----
From: Andy Walls [mailto:[email protected]]
Sent: Wednesday, October 15, 2008 5:51 AM
To: Tom Moore
Cc: [email protected]
Subject: RE: [linux-dvb] Duel Hauppauge HVR-1600
Tom,
Just a note: please don't top post. Per list convention, please just respond in-line.
Quoted 3 lines · Tom Moore
Thanks Andy for the reply.
I did what you said and now I'm getting an memory error message when
booting
Quoted 4 lines
The message reads:
Initrd extends beyond end of memory (0x37fef23a>0x30000000)
Well, that's a new one on me.
Quoted 2 lines
I tried lowering the amount but anything over 128M and I get the error message.
So since vmalloc addresses are used for dynamic kernel mappings for things like loadable module code and for IO mappings, 128 MB of addresses will never be sufficient to support two cards that want 64 MB of addresses each, along with other kernel vmalloc needs.
So until this problem is resolved, you won't get the second card running. The good news is, the problem appears to be fixable with the proper kernel configuration.
The driver did make some suggestions in it's original error message:
Quoted 5 lines
Quoted 5 lines
cx18-1: ioremap failed, perhaps increasing
__VMALLOC_RESERVEinpage.hcx18-1: or disabling
CONFIG_HIGHMEM4Ginto the kernel would helpcx18-1: Error -12 on initialization
both of which you could try. They involve building a custom kernel.
There may be other ways, but I'm no expert in Linux memory management. I suspect someone over on the LKML is.
To help solve your problem, people will likely need to see the output of 'cat /proc/meminfo' and 'dmesg' for your system. If I had that info, I could try to help, I'm not sure I'd be able to help effectively.
Regards,
Andy
Quoted 4 lines
Here is my config file:
# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this
file
Quoted 76 lines
# NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title MythDora (2.6.24.4-64.fc8)root (hd0,0) kernel /vmlinuz-2.6.24.4-64.fc8 ro root=/dev/VolGroup00/LogVol00 rhgb quiet vmalloc=256M initrd /initrd-2.6.24.4-64.fc8.img-----Original Message-----
From: Andy Walls [mailto:[email protected]]
Sent: Tuesday, October 14, 2008 7:16 PM
To: Tom Moore
Cc: [email protected]
Subject: Re: [linux-dvb] Duel Hauppauge HVR-1600Quoted 36 lines · Tom Moore
I just bought two Hauppauge HVR-1600 cards and I'm trying to set them up in
Mythdorra 5. I have the cx18 drivers installed but it is only initializing one
card. I'm getting the following message when I do a dmesg | grep cx18. Has
anyone ran accross this problem before with duel cards of the same model and if
so, how do I fix it? Any help will be greatly appreciated.
Thanks,
Tom Moore
Houston, TX
dmesg | grep cx18
cx18: Start initialization, version 1.0.1
cx18-1: Initializing card #1
cx18-1: Autodetected Hauppauge card
cx18-1: Unreasonably low latency timer, setting to 64 (was 32)
cx18-1: ioremap failed, perhaps increasing
__VMALLOC_RESERVEinpage.hQuoted 8 lines
cx18-1: or disabling
CONFIG_HIGHMEM4Ginto the kernel would helpcx18-1: Error -12 on initialization
cx18: probe of 0000:02:04.0 failed with error -12
cx18: End initialization
You're out of vmalloc address space. Each cx18 needs 64 MB of vmalloc space for MMIO mappings.
Do this:
$ cat /proc/meminfo | grep Vmalloc
Quoted 9 lines
Edit your bootloader's config file to add a 'vmalloc=xxxM' option to your kernel commandline. Use a value that is 128M greater than your current VmallocTotal.
Regards,
Andy
Andy,
Quoted 1 line
Thanks Andy for all your help. Instead of headache of TRYING to build a
custom kernel, I swopped-out hard drives and installed Mythbuntu. After installing the cx18 drivers it also only initialized one card. I then modified the bootloader with "vmalloc=256M" and it worked like a champ. I think I will put my other hard drive back in and try to update the kernel in Mythdora 5 (even though the docs recommend against it). Anyway I posted at the bottom as you said and I REALLY appreciate you taking the time to help me. Maybe one day I can return the favor.
Have a great day,
Tom
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 9 lines · Tom Moore
Andy,
Quoted 1 line
Thanks Andy for all your help. Instead of headache of TRYING to build a
custom kernel, I swopped-out hard drives and installed Mythbuntu. After installing the cx18 drivers it also only initialized one card. I then modified the bootloader with "vmalloc=256M" and it worked like a champ. I think I will put my other hard drive back in and try to update the kernel in Mythdora 5 (even though the docs recommend against it). Anyway I posted at the bottom as you said and I REALLY appreciate you taking the time to help me.
You're welcome. I'm glad you found a path to a solution.
Regards,
Andy
Quoted 4 lines
Maybe one day I can return the favor.
Have a great day,
Tom
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb