Your message dated Sat, 15 May 2021 04:34:34 -0700 (PDT)
with message-id <[email protected]>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #845927,
regarding No sound Acer 2730 (Gnawty Atom 36x/37x series Atom
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
845927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845927
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: kernel
Version: 4.5
Debian Jessie 8.6.0+ gnome desktopi386
Good day,
Sorry, I'm a user, not a developer. Can't make head nor tail of the bug
reporting instructions and package finding instructions.
I cannot get sound to work on live Debian-based OSes, particularly TAILS 2.x,
3.0 alpha.
Preconditions
Machine: Acer C730 (CB3-111) Gnawty- Atom Z36/37 Baytrail / Valleyview
Live OSes run through Seabios RW Legacy (flashed by script from johnlewis.ie)
What I did
Ran Tails Debian-based as a live usb on listed machine.
What happened
Setting>sound>no output devices listed
Attempted resolution
Installed numerous alsa pulse tools but was not able to configure sound to
output to speakers.
Ran alsamixer it seems sound is routed to HDMI and can't be changed to analog
output i.e.speakers.
Ran pavucontrol. The config tab lists only HDMI devices. and can't be changed
to analog output i.e.speakers
snd_hda_intel is loaded but o/p goes to HDMI. I don't have an HDMI device it's
a chromebook.
I raised a ticket with tails bug team
They responded:
-------------------------------------------------------------------------------------------
Hi Franck,
> 00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series
> High Definition Audio Controller (rev 0e)
Thanks for taking time to report this issue.
It looks that your issue is not specific to Tails, but rather to Linux
support of your hardware.
Is your soundcard working with another O.S like Debian or Ubuntu?
Could you please boot with a newer version of Debian, from which
Tails is based. You can find such live DVD ISO at
http://cdimage.debian.org/debian-cd/current-live/i386/iso-hybrid/debian-live-8.6.0-i386-gnome-desktop.iso
With your help this issue could hopefully then be fixed in a future
version of linux and thus Tails.
Thanks by advance
They did not raise an upstream ticket to Debian.
-------------------------------------------------------------------------------------------
I tried making a Debian live USB but Jessie didn't detect network controller,
audio, trackpad ... To hinder progress further, I couldn't get persistence to
work so got nowhere on submitting a Debian report via reportbug. I followed
several guides and the advice was inconsistent whether to put a file called
live-persistence.conf or persistence.conf into aa partition called rw-live /
persistence / casper-rw
Is there a correct way that works?
Nevertheless, sound did not work.
Tried with Ubuntu Live. No sound
Sound is fine with installed Ubuntu ran as a Crouton chroot (sound o/p device
listed as CRAS which is part of ChromeOS)
Figured at this juncture problem is either Linux or bios.
-------------------------------------------------------------------------------------------
I then posted on a coreboot forum
https://plus.google.com/communities/112479827373921524726/s/baytrail
Frank E Davidson
coreboot specific
I have never got Tails 2.x, or 3.0 alpha to output sound to analogue using
Seabios RW Legacy on my Acer C730 Gnawty (aka CB3-111?). All the options in
pavucontrol > config tab are HDMI. I raised a ticket and the tails bug team
said it * may* be a Debian dependency but I can't test as can;t get a Debian
Live to detect network, trackpad, sound o/p and to further frustrate
troubleshooting persistence doesn't work. I'm wondering if the Seabios might
not be reporting the firmware to the OS. Sound works fine on Ubuntu 14 run as a
Crouton chroot. Any suggestions, anyone?
I got a response on the google+ forum
Matt DeVillier (Mr. Chromebox)
this is a known, and multi-faceted issue affecting many Baytrail ChromeOS
devices, and has nothing to do with SeaBIOS. The issues at play are the
following:
- with the RW_LEGACY firmware, the audio device is initialized by depthcharge
(the ChromeOS payload) before SeaBIOS is run. That pre-init causes problems on
some devices but not others; the only workaround is to use the BOOT_STUB
firmware (which eliminates the depthcharge payload)
- upstream linux kernels 4.5+ contain a patch that breaks audio on Baytrail
ChromeOS devices
- upstream linux kernels 4.5+ added support for audio on Braswell devices;
enabling audio on Baytrail and Braswell devices is mutually exclusive, so any
given kernel can only be configured for one or another, and most default to
Braswell.
To figure out what issue(s) you're running into, boot GalliumOS from USB and
see if you have audio there. If non-functional, your issue is at least partly
related to the depthcharge audio init. If functional, then you might try
rebuilding a tails kernel with the config options and related patch(es) used by
GalliumOS.
Any crouton instance is still using the ChromeOS kernel (and therefore audio
config/drivers as well) and will therefore work just fine. It's not a good
barometer of anything.
-------------------------------------------------------------------------------------------
I can't change the kernel in Tails.
I still use chromeos, so unable to flash tbe bootstub bios suggested (which
also risks bricking my laptop)
Please submit upstream as necessary.
Many thanks.
Frank E Davidson
33 Hilton Road,
Aberdeen AB24 4HR
UNITED KINGDOM
e-mail: [email protected]
--- End Message ---
--- Begin Message ---
Hi
This bug was filed for a very old kernel or the bug is old itself
without resolution.
If you can reproduce it with
- the current version in unstable/testing
- the latest kernel from backports
please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.
Regards,
Salvatore
--- End Message ---
