Public bug reported:
Binary package hint: gnome-applets
Release: Ubuntu 9.04 (modified, see below) on Babbage1 or Babbage2.
The error is that notification applets reliably crash on login. We get
about 10 message windows that say variations of "The panel encountered a
problem while loading OAFII
** Attachment added: "Updated RedBoot for babbage1"
http://launchpadlibrarian.net/28442516/mx51_babbage_redboot-no-padding.bin
** Description changed:
Binary package hint: gnome-applets
Release: Ubuntu 9.04 (modified, see below) on Babbage1 or Babbage2.
- The error is that notificat
In the Babbage1 case, the kernel, rootfs, and initrd are unchanged. I
have changed redboot only. So no kernel config changes or changes to
the initrd scripts/modules. ifconfig shows a loopback device in the
failing case. And networking is working.
In the Babbage2 case there is no initrd, so ye
I have gone back and forth between redboot versions that work/don't work
using dd. I can do fis list and fc -l and capture the results and
compare good to bad and see that the listed information is not changed.
--
notification area applets crash on login
https://bugs.launchpad.net/bugs/392716
Yo
I also have replicated the bug using the vmlinuz and initrd from /boot.
I copied them to a host machine, used "gzip -d" to decompress the
initrd, and uploaded them using tftp with redboot, adding the unchanged
exec line. So I really think the only change here (in the Babbage1
case) is redboot, not
Yeah, that's fine, I agree it is good to be real exact about what
changed and what didn't, so I'm totally fine with any questions you have
on my setup.
Are you seeing the failure of the applets after login?
I started down the path of DebuggingProgramCrash, not sure which program
to pursue as the
Public bug reported:
Release: Ubuntu 9.04 on Babbage1
I'm not changing anything from the 9.04 release.
After install, audio is defaulting to /dev/null
The volume control applet's heading says "Volume Control: Playback: Null Output
(PulseAudio Mixer)
The problem is that the default user that wa
** Attachment added: "The app that plays the Ubuntu desktop login sound sets
the period to whatever minimum is allowed by the driver. This change sets
period size high enough value that we will never have ssi underruns then."
http://launchpadlibrarian.net/29729382/0001-ENGR00114681-pcm-set-
Public bug reported:
Platform: Babbage 2.0
Release: Jaunty with all the current upgrades. I uninstalled pulseaudio to
save cpu. I also patched the audio driver to increase the minimal audio period
size to 2K. Patch is attached.
Symptom:
1. Log onto Ubuntu. The desktop-login.org sound will p
It appears that it is the vorbis decode that gets behind.
If I change the login sound to be a 7 second sine uncompressed wav file
in the Sound Preferences, the sine wave plays flawlessly.
So I think this is a priority problem where the vorbis decoder gets
behind because too much stuff is happenin
I'm attaching two patches to give you what we have of the audio port.
These patches apply cleanly to your fsl-imx51 branch.
Playback and record work.
There is an issue with your regulator stuff that breaks things somewhat.
You will see a boot error that occurs when imx-3stack-sgtl5000.c calls
reg
** Attachment added: "0001-ENGR00107785-sgtl5000-adc-power-savings.patch"
http://launchpadlibrarian.net/32991149/0001-ENGR00107785-sgtl5000-adc-power-savings.patch
--
no sound devices on babbage board with linux-image-2.6.31-100-imx51
https://bugs.launchpad.net/bugs/420447
You received this
** Attachment added: "0002-sgtl5000-audio-more-porting-to-2.6.31.patch"
http://launchpadlibrarian.net/32991169/0002-sgtl5000-audio-more-porting-to-2.6.31.patch
--
no sound devices on babbage board with linux-image-2.6.31-100-imx51
https://bugs.launchpad.net/bugs/420447
You received this bug
Just to be completely clear about the regulator issue, I have attached a
patch. This is not a solution so I named it something that no normal
human would consider merging and pushing. This patch puts #if 0 around
the regulator initialization part if imx-3stack-sgtl5000's probe so that
the audio d
I'm attaching another patch that allows the audio codec to power down when not
in use.
The problem was that Line In was always enabled, so always powered up.
** Attachment added: "0005-sgtl5000-add-line-in-function.patch"
http://launchpadlibrarian.net/33050170/0005-sgtl5000-add-line-in-functi
I didn't see any ALSA messages in your boot log so it isn't initializing
fully. A section of my bootlog is below. Have you tried it with the
sound driver built in? All my testing is using the imx51_defconfig that
is in your kernel tree, so the audio is built in, not as modules.
I tested with on
Could you please attach your defconfig?
--
no sound devices on babbage board with linux-image-2.6.31-100-imx51
https://bugs.launchpad.net/bugs/420447
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
Thanks.
My guess: two types of problems at this point: the changes to how the
rootfs handles audio and issues with the audio driver as a module. I'll
debug the audio driver module problems.
For now, I recommend you try building the driver into the rootfs so that
you can debug the rootfs issues.
Debugging using fsl rootfs, I see the audio work as a module just fine.
I get these messages when it loads:
r...@freescale ~$ modprobe -V snd-soc-imx-3stack-sgtl5000
sgtl5000-i2c 1-000a: SGTL5000 revision 17
DMA Sound Buffers Allocated:UseIram=1 buf->addr=1ffef000 buf->area=de9a
size=24576
DM
Regarding the rename, I am sympathetic and the case you are making for
it is sound (pardon the pun). I just don't have the time. Keep in
mind that it is one platform for you (imx-3stack-sgtl5000) but for me it
is seven (sgtl5000, ak4647, ak5702, etc). Also if I rename all those
file, it makes i
Are you plugged into the right jack?
If you are used to the Babbage1 board, it's easy to plug the headphone
into the wrong jack. The headset and headphone jacks swapped somewhere
between BBG1 and BBG2.5. They weren't even labeled on BBG1, but they're
labeled on BBG2.5 (in tiny, tiny print).
The
What changes are needed to expose the right properties to udev?
--
no sound devices on babbage board with linux-image-2.6.31-100-imx51
https://bugs.launchpad.net/bugs/420447
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
*** This bug is a duplicate of bug 420447 ***
https://bugs.launchpad.net/bugs/420447
9.04 has audio support.
This is not a duplicate. the bug 420447 appears to be a bug in the
2.6.30 kernel port. It builds fine in the 2.6.28 kernel and the release
9.04 has sgtl5000 audio built in the kernel
What kind of boot messages do you get when ALSA starts up?
--
no sound devices on babbage board with linux-image-2.6.31-100-imx51
https://bugs.launchpad.net/bugs/420447
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
Some boards have I2C errors when a DVI monitor is plugged in. This can
prevent register access to the sgtl5000 audio codec when the audio
driver is initializing. The symptom is that you will see in the boot
messages some I2C errors and a message that it has not successfully id'd
the sgtl5000.
Th
I checked. I was wrong about the command line. It will default to
1024x768. Sorry for the static.
--
no sound devices on babbage board with linux-image-2.6.31-100-imx51
https://bugs.launchpad.net/bugs/420447
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
26 matches
Mail list logo
