<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On 2013-06-18, at 12:02 AM, Daryl McDonald wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">/dev/dvb/adapter0/frontend0 this shows upon the DVB capture card page and further identifies a Samsung card, the one already bringing in the digital cable signal. I can't modify to "adapter 1", (or alter that line at all) which the prompt suggests would bring up the second cards specs .</span></blockquote></div><br><div>OK, I think that’s the first I’ve heard that you have a second DVB card present. What kind of card is it? I ask in case it’s also driven by the saa7134 module. That would explain why the module is loaded but there isn’t a device for the 150U.</div><div><br></div><div>At this point I wonder what the kernel is saying as it boots up. Does it mention the kworld, what about saa7134? On my distro those messages are logged to /var/log/messages. You could take a look there or just zip up the file and put it somewhere downloadable.</div><div><br></div><div>- George</div></body></html>