From: Steven Toth <stoth@linuxtv.org>
To: Bill McCartney <billmccartney@gmail.com>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] HVR-1800 - can't find the card
Date: Fri, 19 Sep 2008 13:34:35 -0400 [thread overview]
Message-ID: <48D3E2AB.9010701@linuxtv.org> (raw)
In-Reply-To: <d77717b60809190029p4bdcdda6g55db6a9261673675@mail.gmail.com>
Bill McCartney wrote:
> Well, I'm not sure if it is a DVB problem. The hvr-1800 shows up in my
> lspci, but driver doesn't load. I have tried kernels version 2.26.24 and
> 2.26.25.7 <http://2.26.25.7>, removed all other cards from the system -
> and still have the same problem.
>
> Output when I try to install the driver
> cx23885 driver version 0.0.1 loaded
> cx23885[0]: can't get MMIO memory @ 0x0
> CORE cx23885[0] No more PCIe resources for subsystem: 0070:7801
> cx23885: probe of 0000:03:00.0 failed with error -22
>
> The output of my lspci -v (of the card)
> 03:00.0 Multimedia video controller: Conexant Unknown device 8880 (rev 0f)
> Subsystem: Hauppauge computer works Inc. Unknown device 7801
> Flags: bus master, fast devsel, latency 0, IRQ 10
> Memory at <ignored> (64-bit, non-prefetchable)
> Capabilities: [40] Express Endpoint IRQ 0
> Capabilities: [80] Power Management version 2
> Capabilities: [90] Vital Product Data
> Capabilities: [a0] Message Signalled Interrupts: 64bit+
> Queue=0/0 Enable-
>
> In my kernel logs I see this from the bootlogs:
> PCI: Cannot allocate resource region 0 of device 0000:03:00.0
>
> I've tried several kernel options as far as pci configuration goes --
> does this mean that I have bad hardware? Should I just return it to the
> store? Is it a conflict with my motherboard?
Returning this to the store isn't going to fix the problem. You have a
limited about of memory allocated to PCI devices and you have no more
free for the HVR1800.
From memory the kernel allocates 512MB (?) for PCI address space, which
gets allocated out to devices. The HVR1800 needs 64MB(?) of address
space, and the kernel doesn't have that free. (My numbers are sketchy
but the same principle stands).
Check lspci -vn and see which of your devices need large amounts of ram
(typically video cards).
For test purposes, removing another card to free some PCI space, this
will allow you to test the hardware, loading the driver after this
should be fine. (Again, for test purposes only).
Increasing the amount of PCI ram available for allocation may be a
kernel boot-time setting. I haven't look to be honest, as I don't
experience this issue.... although occasionally other user have (with
different cards and different driver trees).
I'm traveling this week so I have very little access to source code and
hardware numbers, so if anyone has better numbers or can increase the
PCI allocation then I'd be interested to hear their comments.
Regards,
- Steve
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-09-19 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-19 7:29 [linux-dvb] HVR-1800 - can't find the card Bill McCartney
2008-09-19 17:34 ` Steven Toth [this message]
2008-09-19 22:52 ` Andy Walls
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48D3E2AB.9010701@linuxtv.org \
--to=stoth@linuxtv.org \
--cc=billmccartney@gmail.com \
--cc=linux-dvb@linuxtv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox