← Back to team overview

kernel-packages team mailing list archive

[Bug 1231178] [NEW] Altec Lansing speakers remote control not working

 

Public bug reported:

This has been  ongoing since 2010 ... I initially thought that it was a
hardware (Altec-Lansing speakers and/or Altec-Lansing remote control)
issue, but noting the timing of linux header updates (remote
intermittently working: range ~ 20 - minute - a couple of weeks working;
prolonged periods - up to 6+ months NOT working), I believe it is  linux
(Ubuntu) problem.

 ======================================

From: Altec Lansing Customer Service <support@xxxxxxxxxxxxxxxx>
Subject: Request received: Wireless remote not workling (VS 4221 speakers) (ticket #1630)
Date: Fri, 4 Nov 2011 19:46:44 +0000

Request received: Wireless remote not workling (VS 4221 speakers)
(ticket #1630)

Hi - Your request (#1630) has been received, and is being reviewed by
our support staff.

----------------------------------------------

Hello: I have the VS 4221 speakers and two of the wireless remotes;
neither of the remotes works, even with new button batteries.  I cannot
change the treble/bass, etc. Restarting my computer has no effect, nor
doe unplugging the speakers (electrical outlet), then plugging them back
in again.

 ======================================

----- Original Message(s): -----
Date: 2010 Apr 24 (Sat) 14:02
From: "Altec Lansing Support" <alteclansing@xxxxxxxxxxxx>
Subject: Altec Lansing vs4221 remote does not work [Incident: 100425-000006]

Your question has been received. You should expect a response from us
within 72 hours. To access your question from our support site, click
the following  link or paste it into your web browser.

http://alteclansing.custhelp.com/cgi-
bin/alteclansing.cfg/php/enduser/acct_login.php?p_next_page=myq_upd.php&p_iid=477391&p_created=1272142931

Question Reference #100425-000006

Summary: Altec Lansing VS4221 remote does not work
Product Level 1: Powered Audio
Product Level 2: Satellite Speaker System
Date Created: 04/24/2010 02:02 PM
Last Updated: 04/24/2010 02:02 PM
Status: Unresolved
Date of Purchase: 11/13/2009
First Name : Victoria
Region: Canada
Discussion Thread:

Customer (Victoria S) - 04/24/2010 02:02 PM

April 24, 2010

Hi: I purchased these speakers (VS4221) in Nov. 2009.  This week, the
remote suddenly stopped working; I thought it was the battery, but a
fresh (new) battery did nothing: the remote still fails to work, at all.
I cannot use the standby function,or more importantly adjust bass /
treble.

Please advise.  Thanks, Victoria
 ===============================================================

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-53-generic 3.2.0-53.81
ProcVersionSignature: Ubuntu 3.2.0-53.81-generic 3.2.50
Uname: Linux 3.2.0-53-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC1:  victoria   2169 F.... pulseaudio
 /dev/snd/controlC0:  victoria   2169 F.... pulseaudio
 /dev/snd/pcmC0D0p:   victoria   2169 F...m pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xeb220000 irq 48'
   Mixer name	: 'SigmaTel STAC9271D'
   Components	: 'HDA:83847627,80863001,00100201'
   Controls      : 44
   Simple ctrls  : 25
Card1.Amixer.info:
 Card hw:1 'U0x46d0x825'/'USB Device 0x46d:0x825 at usb-0000:00:1a.7-6.1, high speed'
   Mixer name	: 'USB Mixer'
   Components	: 'USB046d:0825'
   Controls      : 2
   Simple ctrls  : 1
Card1.Amixer.values:
 Simple mixer control 'Mic',0
   Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
   Capture channels: Mono
   Limits: Capture 0 - 6144
   Mono: Capture 4608 [75%] [24.00dB] [on]
Date: Wed Sep 25 15:49:08 2013
HibernationDevice: RESUME=UUID=91c758d2-001a-4a17-baba-f49fb267dd6f
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
IwConfig:
 lo        no wireless extensions.

 eth0      no wireless extensions.
MarkForUpload: True
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-53-generic root=UUID=7dfce011-0edb-4c59-af1c-88e4f3b85c0e ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-53-generic N/A
 linux-backports-modules-3.2.0-53-generic  N/A
 linux-firmware                            1.79.6
RfKill:

SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/21/2008
dmi.bios.vendor: Intel Corp.
dmi.bios.version: DPP3510J.86A.0437.2008.0521.1933
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DP35DP
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD81073-207
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrDPP3510J.86A.0437.2008.0521.1933:bd05/21/2008:svn:pn:pvr:rvnIntelCorporation:rnDP35DP:rvrAAD81073-207:cvn:ct3:cvr:

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: Confirmed


** Tags: amd64 apport-bug precise running-unity staging

** Description changed:

  This has been  ongoing since 2010 .. I thought that it was a hardward
  (Altec-Lansing speakers/remote control) issue, but noting the timimg of
  linux header updates, I believe it is  linux (Ubuntu) problem.
  
-  ======================================
+  ======================================
  
  From: Altec Lansing Customer Service <support@xxxxxxxxxxxxxxxx>
- To: 1 <1@xxxxxxxxxxxxxxxxxxxx>
  Subject: Request received: Wireless remote not workling (VS 4221 speakers) (ticket #1630)
  Date: Fri, 4 Nov 2011 19:46:44 +0000
  
  # Please type your reply above this line #
  
  Request received: Wireless remote not workling (VS 4221 speakers)
  (ticket #1630)
  
  Hi 1,
  
  Your request (#1630) has been received, and is being reviewed by our
  support staff.
  
  To add additional comments, reply to this email or follow the link below:
  http://alteclansingsupport.alteclansing.com/tickets/1630
  
  ----------------------------------------------
  1, Nov-04 03:46 pm (EDT):
  
  Hello: I hve the VS 4221 speakers and two of the wireless remotes;
  neither of the remotes works, even with new button batteries.  I cannot
  change the treble/bass, etc.
  
  Restarting my computer has no effect, nor doe unplugging the speakers
  (electrical outlet), then plugging them back in again.
  
  Please advise ... thanks.
  
- 
  --------------------------------
  This email is a service from Altec Lansing Customer Service
  
  ===================================
  
- From: "Victoria S." <1@xxxxxxxxxxxxxxxxxxxx>
- To: Victoria (very public: 1@...) <1@xxxxxxxxxxxxxxxxxxxx>
+ From: "Victoria S."
  Cc: "Altec Lansing Support"     <alteclansing@xxxxxxxxxxxx>
  Subject: Re: Altec Lansing VS4221 remote does not work [Incident: 100425-000006]
  Date: Mon, 26 Apr 2010 08:21:13 -0700
  
  Also posted online to "My Stuff: Questions" @ Altec Lansing,
  
  http://alteclansing.custhelp.com
  
-  -------------------------------
+  -------------------------------
  
  Monday April 26, 2010
  
  Hello: Please regard this issue as "Resolved:"
  
  1. I found a link on your website for ordering a replacement remote for
  free (shipping not included);
  
  http://www.alteclansing.com/index.php?file=north_product_detail&iproduct_id=remote_for_vs4221
  
  2.  This morning (Apr. 26), after a few Ubuntu (v.9.10) updates ran /
  installed, this remote began working again (without a system restart).
  Go figure.
  
  Anyway, this issue now appears to be resolved, satisfactorily.
  
  Thanks, and have a great day!  Victoria  :-)
  
-  ===============================================================
+  ===============================================================
  
  ----- Original Message(s): -----
  Date: 2010 Apr 24 (Sat) 14:02
  From: "Altec Lansing Support" <alteclansing@xxxxxxxxxxxx>
- To: 1@xxxxxxxxxxxxxxxxxxxx
  Subject: Altec Lansing vs4221 remote does not work [Incident: 100425-000006]
  
  Your question has been received. You should expect a response from us
  within 72 hours.
  
  To access your question from our support site, click the following  link
  or paste it into your web browser.
  
  http://alteclansing.custhelp.com/cgi-
  bin/alteclansing.cfg/php/enduser/acct_login.php?p_next_page=myq_upd.php&p_iid=477391&p_created=1272142931
  
  Question Reference #100425-000006
  
  Summary: Altec Lansing VS4221 remote does not work
  Product Level 1: Powered Audio
  Product Level 2: Sattellite Speaker System
  Date Created: 04/24/2010 02:02 PM
  Last Updated: 04/24/2010 02:02 PM
  Status: Unresolved
  Date of Purchase: 11/13/2009
  First Name : Victoria
- Last Name: 
+ Last Name:
  Region: Canada
  Store of Purchase: London Drugs
  
  Discussion Thread:
  
  Customer (Victoria S) - 04/24/2010 02:02 PM
  
  April 24, 2010
  
  Hi: I purchased these speakers (VS4221) in Nov. 2009.  This week, the
  remote suddenly stopped working; I thought it was the battery, but a
  fresh (new) battery did nothing: the remote still fails to work, at all.
  I cannot use the standby function,or more importantly adjust bass /
  treble.
  
  Please advise.  Thanks, Victoria
  
  [---001:001125:32828---]
  
-  ===============================================================
+  ===============================================================
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-53-generic 3.2.0-53.81
  ProcVersionSignature: Ubuntu 3.2.0-53.81-generic 3.2.50
  Uname: Linux 3.2.0-53-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  AudioDevicesInUse:
-  USER        PID ACCESS COMMAND
-  /dev/snd/controlC1:  victoria   2169 F.... pulseaudio
-  /dev/snd/controlC0:  victoria   2169 F.... pulseaudio
-  /dev/snd/pcmC0D0p:   victoria   2169 F...m pulseaudio
+  USER        PID ACCESS COMMAND
+  /dev/snd/controlC1:  victoria   2169 F.... pulseaudio
+  /dev/snd/controlC0:  victoria   2169 F.... pulseaudio
+  /dev/snd/pcmC0D0p:   victoria   2169 F...m pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
  Card0.Amixer.info:
-  Card hw:0 'Intel'/'HDA Intel at 0xeb220000 irq 48'
-    Mixer name	: 'SigmaTel STAC9271D'
-    Components	: 'HDA:83847627,80863001,00100201'
-    Controls      : 44
-    Simple ctrls  : 25
+  Card hw:0 'Intel'/'HDA Intel at 0xeb220000 irq 48'
+    Mixer name	: 'SigmaTel STAC9271D'
+    Components	: 'HDA:83847627,80863001,00100201'
+    Controls      : 44
+    Simple ctrls  : 25
  Card1.Amixer.info:
-  Card hw:1 'U0x46d0x825'/'USB Device 0x46d:0x825 at usb-0000:00:1a.7-6.1, high speed'
-    Mixer name	: 'USB Mixer'
-    Components	: 'USB046d:0825'
-    Controls      : 2
-    Simple ctrls  : 1
+  Card hw:1 'U0x46d0x825'/'USB Device 0x46d:0x825 at usb-0000:00:1a.7-6.1, high speed'
+    Mixer name	: 'USB Mixer'
+    Components	: 'USB046d:0825'
+    Controls      : 2
+    Simple ctrls  : 1
  Card1.Amixer.values:
-  Simple mixer control 'Mic',0
-    Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
-    Capture channels: Mono
-    Limits: Capture 0 - 6144
-    Mono: Capture 4608 [75%] [24.00dB] [on]
+  Simple mixer control 'Mic',0
+    Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
+    Capture channels: Mono
+    Limits: Capture 0 - 6144
+    Mono: Capture 4608 [75%] [24.00dB] [on]
  Date: Wed Sep 25 15:49:08 2013
  HibernationDevice: RESUME=UUID=91c758d2-001a-4a17-baba-f49fb267dd6f
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
  IwConfig:
-  lo        no wireless extensions.
-  
-  eth0      no wireless extensions.
+  lo        no wireless extensions.
+ 
+  eth0      no wireless extensions.
  MarkForUpload: True
  ProcFB:
-  
+ 
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-53-generic root=UUID=7dfce011-0edb-4c59-af1c-88e4f3b85c0e ro quiet splash
  RelatedPackageVersions:
-  linux-restricted-modules-3.2.0-53-generic N/A
-  linux-backports-modules-3.2.0-53-generic  N/A
-  linux-firmware                            1.79.6
+  linux-restricted-modules-3.2.0-53-generic N/A
+  linux-backports-modules-3.2.0-53-generic  N/A
+  linux-firmware                            1.79.6
  RfKill:
-  
+ 
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2008
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: DPP3510J.86A.0437.2008.0521.1933
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DP35DP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD81073-207
  dmi.chassis.type: 3
  dmi.modalias: dmi:bvnIntelCorp.:bvrDPP3510J.86A.0437.2008.0521.1933:bd05/21/2008:svn:pn:pvr:rvnIntelCorporation:rnDP35DP:rvrAAD81073-207:cvn:ct3:cvr:

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1231178

Title:
  Altec Lansing speakers remote control not working

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  This has been  ongoing since 2010 ... I initially thought that it was
  a hardware (Altec-Lansing speakers and/or Altec-Lansing remote
  control) issue, but noting the timing of linux header updates (remote
  intermittently working: range ~ 20 - minute - a couple of weeks
  working; prolonged periods - up to 6+ months NOT working), I believe
  it is  linux (Ubuntu) problem.

   ======================================

  From: Altec Lansing Customer Service <support@xxxxxxxxxxxxxxxx>
  Subject: Request received: Wireless remote not workling (VS 4221 speakers) (ticket #1630)
  Date: Fri, 4 Nov 2011 19:46:44 +0000

  Request received: Wireless remote not workling (VS 4221 speakers)
  (ticket #1630)

  Hi - Your request (#1630) has been received, and is being reviewed by
  our support staff.

  ----------------------------------------------

  Hello: I have the VS 4221 speakers and two of the wireless remotes;
  neither of the remotes works, even with new button batteries.  I
  cannot change the treble/bass, etc. Restarting my computer has no
  effect, nor doe unplugging the speakers (electrical outlet), then
  plugging them back in again.

   ======================================

  ----- Original Message(s): -----
  Date: 2010 Apr 24 (Sat) 14:02
  From: "Altec Lansing Support" <alteclansing@xxxxxxxxxxxx>
  Subject: Altec Lansing vs4221 remote does not work [Incident: 100425-000006]

  Your question has been received. You should expect a response from us
  within 72 hours. To access your question from our support site, click
  the following  link or paste it into your web browser.

  http://alteclansing.custhelp.com/cgi-
  bin/alteclansing.cfg/php/enduser/acct_login.php?p_next_page=myq_upd.php&p_iid=477391&p_created=1272142931

  Question Reference #100425-000006

  Summary: Altec Lansing VS4221 remote does not work
  Product Level 1: Powered Audio
  Product Level 2: Satellite Speaker System
  Date Created: 04/24/2010 02:02 PM
  Last Updated: 04/24/2010 02:02 PM
  Status: Unresolved
  Date of Purchase: 11/13/2009
  First Name : Victoria
  Region: Canada
  Discussion Thread:

  Customer (Victoria S) - 04/24/2010 02:02 PM

  April 24, 2010

  Hi: I purchased these speakers (VS4221) in Nov. 2009.  This week, the
  remote suddenly stopped working; I thought it was the battery, but a
  fresh (new) battery did nothing: the remote still fails to work, at
  all.  I cannot use the standby function,or more importantly adjust
  bass / treble.

  Please advise.  Thanks, Victoria
   ===============================================================

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-53-generic 3.2.0-53.81
  ProcVersionSignature: Ubuntu 3.2.0-53.81-generic 3.2.50
  Uname: Linux 3.2.0-53-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC1:  victoria   2169 F.... pulseaudio
   /dev/snd/controlC0:  victoria   2169 F.... pulseaudio
   /dev/snd/pcmC0D0p:   victoria   2169 F...m pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xeb220000 irq 48'
     Mixer name	: 'SigmaTel STAC9271D'
     Components	: 'HDA:83847627,80863001,00100201'
     Controls      : 44
     Simple ctrls  : 25
  Card1.Amixer.info:
   Card hw:1 'U0x46d0x825'/'USB Device 0x46d:0x825 at usb-0000:00:1a.7-6.1, high speed'
     Mixer name	: 'USB Mixer'
     Components	: 'USB046d:0825'
     Controls      : 2
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
     Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
     Capture channels: Mono
     Limits: Capture 0 - 6144
     Mono: Capture 4608 [75%] [24.00dB] [on]
  Date: Wed Sep 25 15:49:08 2013
  HibernationDevice: RESUME=UUID=91c758d2-001a-4a17-baba-f49fb267dd6f
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
  IwConfig:
   lo        no wireless extensions.

   eth0      no wireless extensions.
  MarkForUpload: True
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-53-generic root=UUID=7dfce011-0edb-4c59-af1c-88e4f3b85c0e ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-53-generic N/A
   linux-backports-modules-3.2.0-53-generic  N/A
   linux-firmware                            1.79.6
  RfKill:

  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2008
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: DPP3510J.86A.0437.2008.0521.1933
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DP35DP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD81073-207
  dmi.chassis.type: 3
  dmi.modalias: dmi:bvnIntelCorp.:bvrDPP3510J.86A.0437.2008.0521.1933:bd05/21/2008:svn:pn:pvr:rvnIntelCorporation:rnDP35DP:rvrAAD81073-207:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1231178/+subscriptions


Follow ups

References