[alsa-devel] Analog sound (ALC262) lost on linux (any distro and kernel) on a dual boot system
Hello,
A while back I had installed Ubuntu on a friend's laptop -a Sony Vaio VGN-FW21M- alongside windows Vista. Everything worked fine for a few years, until at some point last year linux went mute, while in windows both the analog and the digital outputs continued working. She couldn't remember doing something "out of the ordinary", but she was sure it was not after an update. Several months later, she upgraded to windows 7 but that didn't change anything. When I got my hands on the laptop, I checked for muted controls and other usual suspects, deprecated quirks (there were none) and all inputs and outputs of the system. HDMI audio works fine and so does the internal mic. Speakers, headphones and the external mic input do not work, even though pulse audio volume meter acts as if there were actually sounds being played. I followed all of Ubuntu's troubleshooting procedures, I removed and reinstalled alsa and pulse, I purged all configuration files, I created a new user and I even installed the latest alsa-packages from the "ALSA daily build snapshots" repository and nothing worked. I also tried booting into windows, setting all volume levels to the max and disabled power saving on all sound and multimedia devices. Next, I tried retasking the jacks one by one to no avail.
I remembered that I had performed the installation with an Ubuntu 11.10 live CD, so I booted the computer off of that, but this time I got no sound. I tried with all the live CDs of a multitude of distros I had lying around, with kernels ranging from 2.6.35 to 3.16.6 and none of them worked, so I figured the issue must have something to do with windows. Is it possible that windows somehow started locking the audio chip on shutdown? If that is the case, can it be deduced from the logs and more importantly, can it be fixed?
I am attaching the output of alsa-info and lspci as well as kernel logs.
Thank you for your time.
And here is the attachment...
Hello,
A while back I had installed Ubuntu on a friend's laptop -a Sony Vaio VGN-FW21M- alongside windows Vista. Everything worked fine for a few years, until at some point last year linux went mute, while in windows both the analog and the digital outputs continued working. She couldn't remember doing something "out of the ordinary", but she was sure it was not after an update. Several months later, she upgraded to windows 7 but that didn't change anything. When I got my hands on the laptop, I checked for muted controls and other usual suspects, deprecated quirks (there were none) and all inputs and outputs of the system. HDMI audio works fine and so does the internal mic. Speakers, headphones and the external mic input do not work, even though pulse audio volume meter acts as if there were actually sounds being played. I followed all of Ubuntu's troubleshooting procedures, I removed and reinstalled alsa and pulse, I purged all configuration files, I created a new user and I even installed the latest alsa-packages from the "ALSA daily build snapshots" repository and nothing worked. I also tried booting into windows, setting all volume levels to the max and disabled power saving on all sound and multimedia devices. Next, I tried retasking the jacks one by one to no avail.
I remembered that I had performed the installation with an Ubuntu 11.10 live CD, so I booted the computer off of that, but this time I got no sound. I tried with all the live CDs of a multitude of distros I had lying around, with kernels ranging from 2.6.35 to 3.16.6 and none of them worked, so I figured the issue must have something to do with windows. Is it possible that windows somehow started locking the audio chip on shutdown? If that is the case, can it be deduced from the logs and more importantly, can it be fixed?
I am attaching the output of alsa-info and lspci as well as kernel logs.
Thank you for your time. _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Quoting Ploumistos Alexandros ch02499@cc.uoi.gr:
And here is the attachment...
Hello,
A while back I had installed Ubuntu on a friend's laptop -a Sony Vaio VGN-FW21M- alongside windows Vista. Everything worked fine for a few years, until at some point last year linux went mute, while in windows both the analog and the digital outputs continued working. She couldn't remember doing something
"out
of the ordinary", but she was sure it was not after an update. Several
months
later, she upgraded to windows 7 but that didn't change anything. When I
got
my hands on the laptop, I checked for muted controls and other usual suspects, deprecated quirks (there were none) and all inputs and outputs of the
system.
HDMI audio works fine and so does the internal mic. Speakers, headphones
and
the external mic input do not work, even though pulse audio volume meter
acts
as if there were actually sounds being played. I followed all of Ubuntu's troubleshooting procedures, I removed and reinstalled alsa and pulse, I purged all configuration files, I created a new user and I even installed the
latest
alsa-packages from the "ALSA daily build snapshots" repository and nothing worked. I also tried booting into windows, setting all volume levels to the max and disabled power saving on all sound and multimedia devices. Next, I
tried
retasking the jacks one by one to no avail.
I remembered that I had performed the installation with an Ubuntu 11.10
live
CD, so I booted the computer off of that, but this time I got no sound. I tried with all the live CDs of a multitude of distros I had lying around, with kernels ranging from 2.6.35 to 3.16.6 and none of them worked, so I figured the
issue
must have something to do with windows. Is it possible that windows somehow started locking the audio chip on shutdown? If that is the case, can it be deduced from the logs and more importantly, can it be fixed?
I am attaching the output of alsa-info and lspci as well as kernel logs.
Thank you for your time. _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
I just noticed there might be a problem with the attached file after it got scrubbed. The file inside the .xz archive should get a .tar.xz extension so it may be opened. For anyone having trouble, I have uploaded the logs here: http://fwh4qw6313.1fichier.com/
Sorry for the trouble
I had a little time to spare and I decided to take another stab at this. I noticed that the verbose lspci command was issued without superuser privileges, so I asked my friend to send it again and I am attaching it. I compared all the logs to those of other systems, though I don't have anything else with the ALC262, but I can't say that anything stands out.
It's not really my problem (it's my friend's) but it is an annoying puzzle. Could it be failing hardware? Could it be windows? I would really appreciate the input from someone knowledgeable.
After a six-hour session trying different kernel versions and all of the possible combinations in hda-jack-retask, I officially declare this as unfixable - at least by me. At least my friend has sound in windows. I told her to monitor this mailing list just in case someone else stumbles upon the same problem with ALC262.
If anyone fond of riddles find themselves with a lot of time in their hands, the description of the problem along with a ton of log files is here: http://mailman.alsa-project.org/pipermail/alsa-devel/2014-October/thread.htm...
On Thu, Oct 23, 2014 at 03:01:24PM +0300, Ploumistos Alexandros wrote:
Hello,
A while back I had installed Ubuntu on a friend's laptop -a Sony Vaio VGN-FW21M- alongside windows Vista. Everything worked fine for a few years, until at some point last year linux went mute, while in windows both the analog and the digital outputs continued working. She couldn't remember doing something "out of the ordinary", but she was sure it was not after an update. Several months later, she upgraded to windows 7 but that didn't change anything. When I got my hands on the laptop, I checked for muted controls and other usual suspects, deprecated quirks (there were none) and all inputs and outputs of the system. HDMI audio works fine and so does the internal mic. Speakers, headphones and the external mic input do not work, even though pulse audio volume meter acts as if there were actually sounds being played. I followed all of Ubuntu's troubleshooting procedures, I removed and reinstalled alsa and pulse, I purged all configuration files, I created a new user and I even installed the latest alsa-packages from the "ALSA daily build snapshots" repository and nothing worked. I also tried booting into windows, setting all volume levels to the max and disabled power saving on all sound and multimedia devices. Next, I tried retasking the jacks one by one to no avail.
I remembered that I had performed the installation with an Ubuntu 11.10 live CD, so I booted the computer off of that, but this time I got no sound. I tried with all the live CDs of a multitude of distros I had lying around, with kernels ranging from 2.6.35 to 3.16.6 and none of them worked, so I figured the issue must have something to do with windows. Is it possible that windows somehow started locking the audio chip on shutdown? If that is the case, can it be deduced from the logs and more importantly, can it be fixed?
for my dayjob , i use a computer which is dualboot with windows and ubuntu , which is almost always having linux-next. and audio works for both my os.
I am attaching the output of alsa-info and lspci as well as kernel logs.
i think you forgot to attach the files.
thanks sudip
Thank you for your time. _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Quoting Sudip Mukherjee sudipm.mukherjee@gmail.com:
On Thu, Oct 23, 2014 at 03:01:24PM +0300, Ploumistos Alexandros wrote:
Hello,
A while back I had installed Ubuntu on a friend's laptop -a Sony Vaio
VGN-FW21M-
alongside windows Vista. Everything worked fine for a few years, until at
some
point last year linux went mute, while in windows both the analog and the digital outputs continued working. She couldn't remember doing something
"out
of the ordinary", but she was sure it was not after an update. Several
months
later, she upgraded to windows 7 but that didn't change anything. When I
got my
hands on the laptop, I checked for muted controls and other usual suspects, deprecated quirks (there were none) and all inputs and outputs of the
system.
HDMI audio works fine and so does the internal mic. Speakers, headphones
and
the external mic input do not work, even though pulse audio volume meter
acts
as if there were actually sounds being played. I followed all of Ubuntu's troubleshooting procedures, I removed and reinstalled alsa and pulse, I
purged
all configuration files, I created a new user and I even installed the
latest
alsa-packages from the "ALSA daily build snapshots" repository and nothing worked. I also tried booting into windows, setting all volume levels to the
max
and disabled power saving on all sound and multimedia devices. Next, I
tried
retasking the jacks one by one to no avail.
I remembered that I had performed the installation with an Ubuntu 11.10
live CD,
so I booted the computer off of that, but this time I got no sound. I tried
with
all the live CDs of a multitude of distros I had lying around, with kernels ranging from 2.6.35 to 3.16.6 and none of them worked, so I figured the
issue
must have something to do with windows. Is it possible that windows somehow started locking the audio chip on shutdown? If that is the case, can it be deduced from the logs and more importantly, can it be fixed?
for my dayjob , i use a computer which is dualboot with windows and ubuntu , which is almost always having linux-next. and audio works for both my os.
I am attaching the output of alsa-info and lspci as well as kernel logs.
i think you forgot to attach the files.
thanks sudip
Thank you for your time. _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Something went wrong with horde's IMP and my attachement was not actually attached. I replied to my message, but it is awaiting moderation as it is about 95kB long.
I 'm sorry for spamming the list with this, but I noticed these errors, that I'm pretty certain they didn't happen when I first installed linux on the machine. Could they be relevant to the issue?
Oct 26 12:00:44 vaio kernel: [ 60.896065] ------------[ cut here ]------------ Oct 26 12:00:44 vaio kernel: [ 60.896073] WARNING: CPU: 1 PID: 37 at /build/buildd/linux-3.13.0/arch/x86/kernel/check.c:140 check_for_bios_corruption+0x10f/0x120() Oct 26 12:00:44 vaio kernel: [ 60.896074] Memory corruption detected in low memory Oct 26 12:00:44 vaio kernel: [ 60.896075] Modules linked in: cuse snd_hda_codec_hdmi(OF) rfcomm bnep bluetooth binfmt_misc arc4 uvcvideo iwldvm videobuf2_vmalloc mac80211 videobuf2_memops videobuf2_core videodev snd_hda_codec_realtek(OF) snd_hda_codec_generic(OF) snd_hda_intel(OF) snd_hda_controller(OF) snd_hda_codec(OF) snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq kvm snd_seq_device snd_timer iwlwifi radeon joydev serio_raw r592 memstick snd lpc_ich cfg80211 ttm drm_kms_helper mac_hid drm i2c_algo_bit soundcore sony_laptop parport_pc video ppdev coretemp lp parport hid_generic usbhid hid sdhci_pci sdhci psmouse firewire_ohci ahci firewire_core libahci crc_itu_t sky2 Oct 26 12:00:44 vaio kernel: [ 60.896120] CPU: 1 PID: 37 Comm: kworker/1:1 Tainted: GF O 3.13.0-35-generic #62-Ubuntu Oct 26 12:00:44 vaio kernel: [ 60.896122] Hardware name: Sony Corporation VGN-FW21M/VAIO, BIOS R1100Y0 08/27/2009 Oct 26 12:00:44 vaio kernel: [ 60.896125] Workqueue: events check_corruption Oct 26 12:00:44 vaio kernel: [ 60.896127] 0000000000000009 ffff880139683d30 ffffffff8171e320 ffff880139683d78 Oct 26 12:00:44 vaio kernel: [ 60.896130] ffff880139683d68 ffffffff8106775d 0000000000000000 ffff880000010000 Oct 26 12:00:44 vaio kernel: [ 60.896133] ffffffff81eb21f0 0000000000000001 ffff880000000000 ffff880139683dc8 Oct 26 12:00:44 vaio kernel: [ 60.896135] Call Trace: Oct 26 12:00:44 vaio kernel: [ 60.896140] [<ffffffff8171e320>] dump_stack+0x45/0x56 Oct 26 12:00:44 vaio kernel: [ 60.896144] [<ffffffff8106775d>] warn_slowpath_common+0x7d/0xa0 Oct 26 12:00:44 vaio kernel: [ 60.896146] [<ffffffff810677cc>] warn_slowpath_fmt+0x4c/0x50 Oct 26 12:00:44 vaio kernel: [ 60.896149] [<ffffffff810524af>] check_for_bios_corruption+0x10f/0x120 Oct 26 12:00:44 vaio kernel: [ 60.896152] [<ffffffff810524ce>] check_corruption+0xe/0x40 Oct 26 12:00:44 vaio kernel: [ 60.896155] [<ffffffff810839d2>] process_one_work+0x182/0x450 Oct 26 12:00:44 vaio kernel: [ 60.896163] [<ffffffff810847c1>] worker_thread+0x121/0x410 Oct 26 12:00:44 vaio kernel: [ 60.896166] [<ffffffff810846a0>] ? rescuer_thread+0x430/0x430 Oct 26 12:00:44 vaio kernel: [ 60.896169] [<ffffffff8108b4a2>] kthread+0xd2/0xf0 Oct 26 12:00:44 vaio kernel: [ 60.896171] [<ffffffff8108b3d0>] ? kthread_create_on_node+0x1c0/0x1c0 Oct 26 12:00:44 vaio kernel: [ 60.896174] [<ffffffff8172ecbc>] ret_from_fork+0x7c/0xb0 Oct 26 12:00:44 vaio kernel: [ 60.896176] [<ffffffff8108b3d0>] ? kthread_create_on_node+0x1c0/0x1c0 Oct 26 12:00:44 vaio kernel: [ 60.896178] ---[ end trace 300adf7bd3d057f3 ]---
participants (2)
-
Ploumistos Alexandros -
Sudip Mukherjee