From: Kovalyev Sergey <randoman@list.ru>
To: Jaroslav Kysela <perex@suse.cz>, alsa-devel@lists.sourceforge.net
Subject: Re: Repost about fm801 tea575x_tuner in 2.6 kernels
Date: Tue, 15 Feb 2005 20:39:50 +0600 [thread overview]
Message-ID: <421209B6.3090103@list.ru> (raw)
In-Reply-To: <Pine.LNX.4.58.0502151115120.1756@pnote.perex-int.cz>
Jaroslav Kysela wrote:
>On Tue, 15 Feb 2005, Kovalyev Sergey wrote:
>
>
>
>>Hello all!
>>
>>When I trying to do
>>
>>#modprobe snd_fm801 tea575x_tuner=1
>>
>>I see this thing in my syslog:
>>
>>kernel: videodev: "TEA5757 radio" has no release callback. Please fix
>>your driver for proper sysfs
>>support, see http://lwn.net/Articles/36850/
>>
>>As far as I understand, this module is not compatible with linux-2.6
>>kernels, so, how to fix this problem?
>>
>>
>
>Nope. This message is only warning and completely harmless. The driver
>should work. This patch will remove the warning:
>
>
>
Hm...
Under 2.4.x kernels I used this command:
modprobe snd_fm801 tea575x_tuner=2
Now, under 2.6, it says that "2" is invalid valut into syslog:
kernel: snd_fm801: `2' invalid for parameter `tea575x_tuner'
So, I trying to use
modprobe snd_fm801 tea575x_tuner=1.
Seems that all ok, even fm says that all ok,
but I hear nothing. Master and Aux channels are unmuted and set to
maximum value...
(This situation is under 2.6.8.1 with built-in alsa drivers)
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-15 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 9:50 Repost about fm801 tea575x_tuner in 2.6 kernels Kovalyev Sergey
2005-02-15 10:16 ` Jaroslav Kysela
2005-02-15 14:39 ` Kovalyev Sergey [this message]
2005-02-15 17:20 ` Jaroslav Kysela
2005-02-17 17:13 ` Kovalyev Sergey
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=421209B6.3090103@list.ru \
--to=randoman@list.ru \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.