Ubuntu cannot recongise my PCTV PicoStick (74e) DVB-T tuner

Bug #856476 reported by Tommy_CZ
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Linux
New
Undecided
Unassigned
linux (Ubuntu)
Won't Fix
Wishlist
Unassigned

Bug Description

Hi, I've bought PCTV PicoStick (74e) DVB-T tuner and after I plug-it, it cannot be recognised by Ubuntu even with appropriate firmware. Please add support for it to the jockey. The driver for 2.6.35 kernels are on this site - http://www.kernellabs.com/blog/?p=1378
Also it exists in this site:
http://linuxtv.org/wiki/index.php/PCTV_picoStick_74e

But both drivers needs some work to support >= 2.6.38 kernels

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-11-generic 3.0.0-11.18
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 1: SB [HDA ATI SB], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: tom 2016 F.... pulseaudio
CRDA: Error: [Errno 2] Adresář nebo soubor neexistuje
Card0.Amixer.info:
 Card hw:0 'Generic'/'HD-Audio Generic at 0xf0444000 irq 40'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100200'
   Controls : 4
   Simple ctrls : 1
Card0.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Card1.Amixer.info:
 Card hw:1 'SB'/'HDA ATI SB at 0xf0440000 irq 16'
   Mixer name : 'Conexant CX20588'
   Components : 'HDA:14f1506c,10250598,00100000'
   Controls : 15
   Simple ctrls : 12
Date: Thu Sep 22 16:50:55 2011
HibernationDevice: RESUME=UUID=79cd2327-7af3-4884-ab40-1e89c8183c6a
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
MachineType: Acer AO722
ProcEnviron:
 LANGUAGE=cs_CZ
 LANG=cs_CZ.UTF-8
 LC_MESSAGES=cs_CZ.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic root=UUID=312fcc38-1fa8-4602-8f0e-599afaa762d7 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-11-generic N/A
 linux-backports-modules-3.0.0-11-generic N/A
 linux-firmware 1.60
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
StagingDrivers: brcmsmac brcmutil
UpgradeStatus: Upgraded to oneiric on 2011-08-17 (36 days ago)
dmi.bios.date: 06/08/2011
dmi.bios.vendor: Acer
dmi.bios.version: V1.04
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JE10-BZ
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.04
dmi.modalias: dmi:bvnAcer:bvrV1.04:bd06/08/2011:svnAcer:pnAO722:pvrV1.04:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.04:
dmi.product.name: AO722
dmi.product.version: V1.04
dmi.sys.vendor: Acer

Revision history for this message
Tommy_CZ (t-kijas) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Tommy_CZ (t-kijas) wrote :

Output of lsusb:
tom@tom-AO722:~/v4l-dvb-as102-2$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 04f2:b209 Chicony Electronics Co., Ltd
Bus 001 Device 007: ID 2013:0246 Unknown (Pinnacle?) PCTV 74E
Bus 002 Device 004: ID 0bda:0138 Realtek Semiconductor Corp.

Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.0.0-12.19)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-12.19
Revision history for this message
Tommy_CZ (t-kijas) wrote :

The issue still exists.

Changing the bug status to confirmed.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.0.0-12.20)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-12.20
Revision history for this message
Tommy_CZ (t-kijas) wrote :

No difference, the issue still exists.
Changing to confirmed.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Tommy_CZ, thank you for reporting this and helping make Ubuntu better. As per https://wiki.ubuntu.com/Testing/Includes/Jockey Jockey is for restricted, proprietary drivers. As per the provided link http://www.kernellabs.com/blog/?p=1378 the driver is GPL. Hence, it would not be appropriate to offer the driver via Jockey. Instead, it should be included in the kernel directly. From the link it looks like they are working on getting it submitted upstream. However, it would be nice if someone did so by following http://kernelnewbies.org/UpstreamMerge . If you submit a patch, please post the link so we may track it. Thank you for your understanding.

Changed in linux (Ubuntu):
importance: Undecided → Wishlist
status: Confirmed → Won't Fix
tags: removed: kernel-request-3.0.0-12.19 kernel-request-3.0.0-12.20
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.