Tom, Just a note: please don't top post. Per list convention, please just respond in-line. On Tue, 2008-10-14 at 20:54 -0500, Tom Moore wrote: > 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. > 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: > > 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 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 > 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:awalls@xxxxxxxxx] > Sent: Tuesday, October 14, 2008 7:16 PM > To: Tom Moore > Cc: linux-dvb@xxxxxxxxxxx > Subject: Re: Duel Hauppauge HVR-1600 > > On Tue, 2008-10-14 at 18:43 -0500, Tom Moore wrote: > > 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_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 > > > > 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 linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
