> No protocol specified
> xcb_connection_has_error() returned true
Hmm, this might be worth investigating further, but it's probably a
separate bug, unless your new alsa-utils is homebrewn somehow.
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received th
updating alsa-utils in a ssh console will generate the errors I see i.e.:
$ sudo apt-get install alsa-utils
...
1 upgraded, 0 newly installed, 0 to remove and 148 not upgraded.
Need to get 1,107kB of archives.
After this operation, 4,096B of additional disk space will be used.
Get:1 http://ports.ub
For the record: ok, my mistake. Wrong kernel actually. However, #57
error is still valid in my case with corrected kernel version.
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ubuntu
Bugs, which i
I think I have a kernel with the correct information:
ubu...@ubuntu-blaze:/sys$ cat /proc/asound/cards
0 [SDP4430]: SDP4430 - SDP4430
TI OMAP4 SDP4430 Board
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug no
your kernel is wrong, teh sound device is not named properly, you need
teh kernel from -proposed first
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I found that "alsactl init" cannot be run in sudo. This command is
called in the postinst script in alsa-utils.
$ sudo alsactl init
Home directory /home/ubuntu not ours.
socket(): Address family not supported by protocol
Found hardware: "SDP4430" "" "" "" ""
Hardware is initialized using a generic
I enabled maveric-updates in /etc/apt/sources.list and tried to update the
alsa-utils package. I see some errors at the end of the installation and don't
know if everything got setup correctly. Here is the log (see 3 last lines):
$ sudo apt-get install alsa-utils
...
1 upgraded, 0 newly installed
Following the kernel commit http://kernel.ubuntu.com/git?p=ubuntu
/ubuntu-
maverick.git;a=commitdiff;h=5469d37bd56cbe8b604e83a8dc769984de5e7437;hp=6b8a624f7c72ac07c28f52371839792d69940c5b
you can identify if you're at the proper kernel by probing the driver's
name or the long name.
The attached pa
With the current version:
# apt-get install alsa-utils
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
alsa-utils
1 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
1 not fully installed or remov
** Changed in: linux-ti-omap4 (Ubuntu Maverick)
Status: Fix Committed => Fix Released
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
This bug was fixed in the package alsa-utils - 1.0.23-2ubuntu3.4
---
alsa-utils (1.0.23-2ubuntu3.4) maverick-proposed; urgency=low
* make the posinst test for Panda and SDP4430 cards not fail (LP:
#664645)
alsa-utils (1.0.23-2ubuntu3.3) maverick-proposed; urgency=low
* debian/pa
Ah, my mistake.
When are the updates due for release?
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
setting the maverick task to fix committed as the fix is not in maverick
yet.
** Changed in: alsa-utils (Ubuntu Maverick)
Status: Fix Released => Fix Committed
** Changed in: linux-ti-omap4 (Ubuntu Maverick)
Status: Fix Released => Fix Committed
** Tags added: verification-done
**
** Changed in: alsa-utils (Ubuntu Maverick)
Status: Fix Committed => Fix Released
** Changed in: linux-ti-omap4 (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux-ti-omap4 (Ubuntu Maverick)
Status: Fix Committed => Fix Released
--
no sound devices on current ES
Thanks a lot, it seems to be OK now, indeed!
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
it is caused by this update and was fixed in ubuntu3.4 already
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
@Martin Pitt: I have a problem with alsa-utils_1.0.23-2ubuntu3.3_i386.deb, see
bug #664812
Is it a regression caused with this update, or some other issue? Thanks!
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you ar
This bug was fixed in the package alsa-utils - 1.0.23-3ubuntu1
---
alsa-utils (1.0.23-3ubuntu1) natty; urgency=low
[ Luke Yelavich ]
* Merge from debian unstable. Remaining changes:
- debian/init:
+ wait until /usr/bin and /var/lib/alsa exist
+ only display an err
** Branch linked: lp:ubuntu/maverick-proposed/linux-ti-omap4
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
this file is incorrect, with the new kernel patches the sound card
reports the board name now as ID so it needs two lines for omap4 (one
with ATTRS{id}=="Panda" the other as above)
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notificatio
Testing pulseaudio profile file for pandaboard to copy in
/usr/share/pulseaudio/alsa-mixer/profile-sets/
+ you need to add one line in /lib/udev/rules.d/90-pulseaudio.rules file so
that it add panda.conf -> looks like this:
SUBSYSTEM!="sound", GOTO="pulseaudio_end"
ACTION!="change", GOTO="pulsea
Accepted linux-ti-omap4 into maverick-proposed, the package will build
now and be available in a few hours. Please test and give feedback here.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you in advance!
** Changed in: linux-ti-omap4
the alsa-libs part was uploaded to maverick-proposed now
** Changed in: alsa-utils (Ubuntu Maverick)
Status: Triaged => Fix Committed
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ubuntu
Bu
with the two kernel patches above and additionally the two files added
to alsa-utils (plus the four line patch) sound works out of the box here
now.
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ub
** Patch added: "alsa-utils.patch"
https://bugs.edge.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/637947/+attachment/1692586/+files/alsa-utils.patch
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a mem
** Patch added: "0002-ASoC-SDP4430-Report-machine-name-in-sound-driver.patch"
https://bugs.edge.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/637947/+attachment/1692583/+files/0002-ASoC-SDP4430-Report-machine-name-in-sound-driver.patch
--
no sound devices on current ES2.0 boards
https://b
** Patch added: "0001-ASoC-core-driver-naming-FOR-REBASE.patch"
https://bugs.edge.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/637947/+attachment/1692581/+files/0001-ASoC-core-driver-naming-FOR-REBASE.patch
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/63794
** Attachment added: "omap4"
https://bugs.edge.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/637947/+attachment/1692580/+files/omap4
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ubuntu
Bug
** Attachment added: "00main"
https://bugs.edge.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/637947/+attachment/1692578/+files/00main
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ubuntu
B
testing further we apparently still need the alsactl init call even with the
fix from bug 652035.
but that fix actually made calling alsactl init from the preinit_levels hack in
/sbin/alsa-utils work (which didnt work before)
so my current proposal is:
go forward with the kernel patches from l
** Changed in: alsa-utils (Ubuntu Maverick)
Assignee: (unassigned) => Oliver Grawert (ogra)
** Changed in: alsa-utils (Ubuntu)
Assignee: (unassigned) => Oliver Grawert (ogra)
** Changed in: linux-ti-omap4 (Ubuntu Maverick)
Status: Confirmed => Triaged
--
no sound devices on cur
** Also affects: alsa-utils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: alsa-utils (Ubuntu Maverick)
Status: New => Triaged
** Changed in: alsa-utils (Ubuntu Maverick)
Importance: Undecided => High
** Changed in: alsa-utils (Ubuntu)
Importance: Undecided => H
First of all I'd like to take this opportunity to thank all those who
attended the Panda audio brainstorming session. I hope it proved
productive for you all.
Attendees of the meeting are as follows; lag, mpoirier, diwic, berco,
sebjan, lrg, rsrimushnam, persia and abduenas. I'm sure there were so
i managed to testbuild the fixes from bug 652035 today, and they in fact
initialize the card fine using the omap4 file from above and teh one
line change in 00main ... could someone upload a test kernel binary with
the other changes so i can actually test the alternative omap4 file that
switches on
i was just pointed to bug 652035 that might have some influence on the
stuff we see here... will do some tests with the alsa-lib changes before
we meet tomorrow
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a
FYI, this has been release noted on
https://wiki.ubuntu.com/ARM/MaverickReleaseNotes
** Changed in: linux-ti-omap4 (Ubuntu Maverick)
Milestone: ubuntu-10.10 => None
** Changed in: linux-ti-omap4 (Ubuntu Maverick)
Milestone: None => maverick-updates
--
no sound devices on current ES2.0 b
ASoC audio (like used on most ARM platforms) has controls for setting up the
backend routing... as you can see above pulse is not enough to initialize sound
here.
i will try to find criteria for the hardware with which we can match it in a
udev rule which in turn can call the alsactl init thats
Hmm...it might be that "alsactl init" was removed by Daniel T Chen just
a week or two ago - I believe the reasoning was that PA still sets all
volumes, so why set them one more time?
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notificat
the very intresting part is that the above makes pulse work out of the
box without any changes (it omits the hdmi sound output though)
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ubuntu
Bugs, whi
hmm, not so well, i just found that this only works if "alsactl init" is
called, which seems to be gone from our setup completely (you can call
it manually but that seems awkward ... another way to use this as a
slightly cleaner hack migh be to call alsactl init from a udev rule if
the device is in
Now we're talking.
Well done Oliver.
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
** Attachment added: "omap4"
https://bugs.edge.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/637947/+attachment/1673694/+files/omap4
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ubuntu
Bug
the following patch together with the attached omap4 file put into
/usr/share/alsa/init/ will make sure the mixer controls are properly set
by default:
--- /usr/share/alsa/init/00main 2010-09-23 13:11:10.0 +0200
+++ 00main 2010-10-05 20:24:24.0 +0200
@@ -32,6 +32,7 @@
# real
To complement my previous comment, the testing went well also using
totem after replacing /etc/pulse/default.pa with attached one, and
reboot.
** Attachment added: "default.pa"
https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/637947/+attachment/1673023/+files/default.pa
--
no s
With these latest audio updates, and while SDP4430.conf file is not properly
used, the attached amixer.sh script can be used to properly configure the audio
path.
Using this script, I was able to play audio on the headset connector (lower
connector) with the audio patches update.
** Attachment
Bryan, with same kernel patched on top of omap4 cdimage from 29-sep-2010
+ sdp4430.conf, I have no sound either. Earphone and headset should be
both turned on by this file. However, what I see is that the file is
read when PA is started but somehow settings get overwritten or not
taken into account
I got one more audio fixing patch from Sebjan and pushed all the audio patches
here:
http://kernel.ubuntu.com/git?p=roc/ubuntu-maverick.git;a=shortlog;h=refs/heads/ti-omap4
And a audio fixing kernel was built for testing:
http://people.canonical.com/~roc/kernel/audio/
After installing the audio
** Attachment added: "SDP4430.conf file for Pandaboard"
https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/637947/+attachment/1656632/+files/SDP4430.conf
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because y
** Tags added: patch
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/ma
** Tags added: iso-testing
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.
Second patch needed too
** Patch added: "0001-ASoC-core-add-support-for-driver-and-longnames.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/637947/+attachment/1626832/+files/0001-ASoC-core-add-support-for-driver-and-longnames.patch
--
no sound devices on current ES2.0 b
They should be enough for ALSA conf
** Patch added: "0002-ASoC-SDP4430-Add-longname-for-driver.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/637947/+attachment/1626830/+files/0002-ASoC-SDP4430-Add-longname-for-driver.patch
--
no sound devices on current ES2.0 boards
ht
** Tags added: omap4 panda
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.
please see bug 644828 too
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.c
I've come to the conclusion that audio is not possible on my board.
I believe this could be down to a faulty filter.
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
testing on my ES2.0 8-layer i only need teh amixer hack and the
following change in default.pa to make sound work
--- /etc/pulse/default.pa.bak 2010-09-17 09:52:51.0 +0200
+++ /etc/pulse/default.pa 2010-09-17 10:17:27.0 +0200
@@ -48,6 +48,11 @@
#load-module module-null-si
The kernel solution seems to need a machine driver: something akin to
sound/soc/omap/sdp4430.c (either a new file, or adding runtime detection
for the alternate hardware to that file (renaming appropriately, etc.).
Documentation on this lives in Documentation/sound/alsa/soc/machine.txt
In addition
I just received this while playing a *.ogg file.
Still no audio.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/637947/+attachment/1587132/+files/dmesg.txt
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You
I only have "Onboard_speakers" in my Output tab.
Still no sound from my 6 layer.
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
oh, and please note that we can not change the deamon.conf file from any
packages but pulseaudio itself (and i assume the flat-volumes = no is a
required setting on other arches) if we need to do overrides like that,
i think emmets way of using the alsa initalization framework is the best
way to go
nothing in hardware tab does not look right to me.
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
L24.9 works well on my Panda 8-layers.
I have used PA default.pa and daemon.conf files attached and setup the amixer
settings with the attached config file.
In the Sound Preferences applet Ihave:
- Hardware tab => no hardware listed
- Input tab => "SDP4430" is listed
- Output tab => "HDMI stereo"
** Attachment added: "PulseAudio settings"
https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/637947/+attachment/1583676/+files/daemon.conf
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a membe
There is a sound icon in the panel.
I don't have an 8 layer board to test.
I have a few more things to try on the 6 layer board.
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Attachment added: "PulseAudio settings"
https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/637947/+attachment/1583675/+files/default.pa
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member
These settings will part of an OMAP4 config package
** Attachment added: "amixer settings needed."
https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/637947/+attachment/1583666/+files/omap4_amixer_config.sh
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bug
no device at all in the sound settings panel ?
how about the 8 layer board ?
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Applied all new patches from TI's L24.9 branch.
Still not sound on 6 layer ES2.0.
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I believe the correct way to fix this is by creating a board-specific
driver that will indicate the wire layout from the codec (which driver
exists) to the ports on specific boards. Failing this, there may be
ways to hardcode the wire layout either (incorrectly) in the codec
driver, or (less bad)
** Changed in: linux-ti-omap4 (Ubuntu Maverick)
Assignee: (unassigned) => Lee Jones (lag)
** Changed in: linux-ti-omap4 (Ubuntu Maverick)
Status: New => Confirmed
--
no sound devices on current ES2.0 boards
https://bugs.launchpad.net/bugs/637947
You received this bug notification bec
70 matches
Mail list logo
