lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as "Won't Fix".
** Changed in: linux (Ubuntu Lucid)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: linux (Ubuntu Lucid)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/546769
Title:
no sound with Realtek ALC269 - on Sony Vaio VPCEB1S1E
To m
This release has reached end-of-life [0].
[0] https://wiki.ubuntu.com/Releases
** Changed in: linux (Ubuntu Maverick)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
** Changed in: linux (Ubuntu Lucid)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Maverick)
Status: Incomplete => Fix Committed
** Changed in: linux (Ubuntu Maverick)
Status: Fix Committed => In Progress
** Changed in: linux (Ubuntu Lucid)
Status: In
The fix which is being SRUd under this bug has already hit mainline,
first appearing in v2.6.37-rc1. Therefore this is already applied and
uploaded in Natty. Closing out the development task:
commit abdd8f510686da0a58e475bc0143d1069e5f53da
Author: Takashi Iwai
Date: Tue Sep 21 17:38:14
@Derek -- once a fix is applied to the kernel via the SRU process it
must be verified as working in the -proposed kernel within a week, else
it has to be assumed as not functional and removed from kernel which is
passed to -updates. This is to ensure that all fixes which are released
actually are
Hm. Well. I'm not too clear on exactly why it was reverted, but I can
attest as I noted previously, that it worked for a while using the ALSA
team's package, but then, stopped working.
I've continued to use that team package. Currently am on:
2.6.35-22.201011231600
Since then, I've been using th
** Branch linked: lp:ubuntu/lucid-proposed/linux-ec2
--
no sound with Realtek ALC269 - on Sony Vaio VPCEB1S1E
https://bugs.launchpad.net/bugs/546769
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
** Tags removed: verification-needed
--
no sound with Realtek ALC269 - on Sony Vaio VPCEB1S1E
https://bugs.launchpad.net/bugs/546769
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.co
The change has been reverted from the Maverick kernel for the same
reasons given in #24 above.
** Changed in: linux (Ubuntu Maverick)
Status: Fix Committed => Incomplete
** Tags added: stable-reverted-maverick
--
no sound with Realtek ALC269 - on Sony Vaio VPCEB1S1E
https://bugs.launchpa
Verification that this bug is fixed has not been completed by the deadline for
the current stable kernel release cycle.
The change will be reverted and this bug is being set to incomplete.
In order to have this fix considered for reapplication to the kernel,
please follow the process documented h
Due to national holidays, the deadline for verification of fixes for the
-proposed kernel has been extended thru Monday, November 15th.
If verification that this bug is fixed by the -proposed kernel has not
occurred by that date, the change will be reverted and this bug will be
set to incomplete.
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed'
to 'verification-done'.
If verification is not done by Thursday, November 11, this fix will
daniel, WRT kde vs gnome, this is a brand new default install of ubuntu
10.10 - s, gnome :)
--
no sound with Realtek ALC269 - on Sony Vaio VPCEB1S1E
https://bugs.launchpad.net/bugs/546769
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Accepted linux 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!
** Also affects: linux (Ubuntu Maverick
Accepted linux into lucid-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!
** Package changed: alsa-driver (Ubuntu) =
Derek, are you using GNOME or KDE? Specifically, are you using KMix?
--
no sound with Realtek ALC269 - on Sony Vaio VPCEB1S1E
https://bugs.launchpad.net/bugs/546769
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Apart from needing to set Speaker from 0 to 100% in alsamixer each time
I log in (should probably add that to a startup script), everything
seems to be working again in latest ALSA updates.
--
no sound with Realtek ALC269 - on Sony Vaio VPCEB1S1E
https://bugs.launchpad.net/bugs/546769
You receive
FYI, I'd stayed on ALSA test, and the most recent update killed my sound again.
Going into HDA Analyser and changing it from GRD to HIZ again seems to do the
trick.
I'm a bit puzzled since your patch suggests that GRD worked before?
(assuming that was what was in the ALSA ppa up until now)
--
n
Yep. All better after applying the most recent alsa driver modules
package.
BTW, there was a warning saying I shouldn't be installing this package,
but rather using a meta I didn't see. Hopefully whatever that is is an
issue that won't be a problem in release.
Also. I still have to raise the vo
I have now researched this issue, and it seems like since only a week
back, there is a quirk for all sony vaios having the ALC269 chip.
This means that if you retry
https://wiki.ubuntu.com/Audio/InstallingLinuxAlsaDriverModules *now*, it
should work without further changes.
Quoting some code belo
Full output from alsa...
** Attachment added: "alsa-info.txt.bdDjQaBOj4"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/546769/+attachment/1649636/+files/alsa-info.txt.bdDjQaBOj4
--
no sound with Realtek ALC269 - on Sony Vaio VPCEB1S1E
https://bugs.launchpad.net/bugs/546769
You r
Damn.
Subsystem Id: 0x104d4300
Will attach the file, but I suppose that means you'll want a new bug.
Nonetheless, the issue may have overlap, and clearly at least 2 of us on these
sony vpc series found this value to be a solution (no response from original
reporter on whether he tried it too).
I had that PPA enabled prior on a recommendation in #ubuntu+1 for about a week
but since it did nothing, I disabled it again.
Sorry, forgot to mention that in my laundry list of failures I guess.
I will reenable it briefly and retest, then post my alsa info.
--
no sound with Realtek ALC269 - on
Cool that you're on the track on finding something.
So to get this into the kernel permanently, I will need the following:
* A verification that installation of the latest snapshot do NOT solve the
problem: https://wiki.ubuntu.com/Audio/InstallingLinuxAlsaDriverModules
* Your alsa-info's to make
Oh, FWIW, I also had a volume of 0 on Speaker in alsamixer that I had to
set to max. Everything looked fine in the sound preferences, so
presumably once again there's some confusion on what channel things are
playing on :)
Anyway, his solution is still working although making it permanent would
b
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Confirmed
--
no sound with Realtek ALC269 - on Sony Vaio VPCEB1S1E
https://bugs.launchpad.net/bugs/546769
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
Same problem, thank you so much for your solution, Pistolpete - worked
GREAT.
Haven't tried the patch yet, but, yeah, the HDA Analyzer does the trick.
Sony VPCB1 running maverick - no sound until I followed your suggestion, had
tried various meaningless things such as:
* options snd-hda-intel mo
I've had the same problem on Lucid. I've found a solution in Bug report
#445889. I will quote Arwin Tugade:
"
There is this tool that lets you flip settings around but the changes aren't
persistant: http://www.alsa-project.org/main/index.php/HDA_Analyzer
To get my speakers working, I ran the h
Did you find a solution?
Thank you in advance
--
no sound with Realtek ALC269 - on Sony Vaio VPCEB1S1E
https://bugs.launchpad.net/bugs/546769
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
Hi hannes,
Please be sure to confirm this issue exists with the latest development release
of Ubuntu. ISO CD images are available from
http://cdimage.ubuntu.com/releases/ . If the issue remains, please run the
following command from a Terminal (Applications->Accessories->Terminal). It
will
is there any output I should post also - so you can fix this problem in
alsa?
Greets
--
no sound with Realtek ALC269 - on Sony Vaio VPCEB1S1E
https://bugs.launchpad.net/bugs/546769
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
don't think so either - run ubuntu in recovery-mode over root-bash ->
startx. Tried to run vlc via sux in her notebook - because when I choose
in grub the "normal-ubuntu-mode" there comes a white screen after she
logs in...
--
no sound with Realtek ALC269 - on Sony Vaio VPCEB1S1E
https://bugs.lau
Hmm...thanks for the VLC log. It seems like it can't access dbus, pulseaudio or
the alsa configuration.
What could cause these permission errors? Are you running inside a chroot or
something?
I assume it isn't reproducable if you run Ubuntu from a Live-CD?
--
no sound with Realtek ALC269 - on
here the log of vlc when I try to open a mp3
sux dienene vlc
VLC media player 1.0.2 Goldeneye
[0x882bf88] inhibit interface error: Failed to connect to the D-Bus session
daemon: Did not receive a reply. Possible causes include: the remote
application did not send a reply, the message bus securit
35 matches
Mail list logo
