search

GalliumOS / galliumos-distro

Docs, issues, and artwork sources for GalliumOS
https://galliumos.org/
GNU General Public License v2.0
348 stars 11 forks source link

Weird sound comes from both speakers and headphones - Asus c300 Chromebook (Baytrail) No matter what firmware I have installed #367

Closed ghost closed 7 years ago

ghost commented 7 years ago
  1. Your Chromebook/Chromebox model hardware ID Asus c300 Chromebook (Baytrail)
  2. Your firmware: stock/factory, MattDevo, CoolStar, John Lewis, or other John Lewis
  3. Your installation method (ISO or chrx) and whether you're running a nightly build ISO
  4. A detailed description of the problem, and steps to reproduce it Problem with sound. Sometimes when I plug in my headphones there is no sound! Even after removing them! I have to run these commands and reset the sound settings alsactl restore -P & alsactl init. This happens with the microphone too! When I try to call somebody on Skype either they can't here me or can't here them (sometimes both happen). In addition, I'd like to see a more user-friendly interface (Chrome OS like). For example, the ability to change audio output by pressing the volume button and select either headphones or Internal Speaker.
reynhout commented 7 years ago

ASUS C300 hardware ID is QUAWKS. And you're running John Lewis RW_LEGACY, right?

The audio issue sounds like #180. It seems to vary by firmware. I would try MrChromebox RW_LEGACY (or BOOT_STUB, if not dual-booting). You could also try MrChromebox full/UEFI, but that will require a reinstall.

Your UI suggestion isn't quite clear to me. The media keys should change the volume of whichever output is active (headphones if plugged in, speakers otherwise).

ghost commented 7 years ago

I ran a script in order to have audio to television (HDMI) and now I have no sound (Speakers)! The alsactl restore -P is not working So, what you are telling me is to format the device and install the MrChromebox's RW_LEGACY firmware? How am I supposed to change the firmaware now? Is there another solution?

reynhout commented 7 years ago

You should be able to switch audio outputs by selecting a device from the audio applet in the panel. You can switch back and forth HDMI to speakers the same way. It does not auto-switch, which is a long-standing issue.

You don't need to format the device to update firmware. You can use MrChromebox's script to install his RW_LEGACY firmware any time. See https://mrchromebox.tech/#fwscript for more info.

BUT: If you were to switch from RW_LEGACY to Full ROM/UEFI firmware, you would need to reinstall the OS, because the RW_LEGACY bootloader is Legacy BIOS-style (not UEFI) and full ROM firmware is not available for Bay Trail in a Legacy BIOS style.

From reports, both BOOT_STUB and Full ROM firmware work as expected. Neither would be able to dual-boot ChromeOS (not sure if that's a priority for you), but BOOT_STUB would not require an OS reinstall, at least.

ghost commented 7 years ago

Are you sure that there isn't any other solution for the problem? To install the BOOT_STUB I have to open up my device and remove the write-protect screw, which I feel uncomfortable with, because I'm afraid of bricking my device. The sound settings are stuck at HDMI, I can't change them! It won't let me! screenshot Same thing for audio output & input! This happened after I ran a script to get HDMI to work sudo wget http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/plain/intel/fw_sst_0f28.bin-48kHz_i2s_master -o /lib/firmware/intel/fw_sst_0f28.bin-48kHz_i2s_master. Does this piece of information help at all?

reynhout commented 7 years ago

That script (really just a command line) downloads new firmware. I don't think it's necessary or useful for getting HDMI output working on QUAWKS.

I'm not sure what's going on with your machine though. The closest hardware I can test is GNAWTY, which should be very similar. It doesn't have any issues like you describe. HDMI output works out of the box, and switching is easy through the applet (select the default sink, options are HDMI or Analog).

The same process should work for you. You might try posting on Reddit r/GalliumOS for other QUAWKS users -- it's a fairly popular model, and I don't recall reports of this issue in the past. Perhaps there's a solution we haven't thought of.

(There is a known issue where something in the system will periodically alter the default ALSA/pulseaudio config, and output will stop working. We don't know what's changing the config, but it's fixed by reverting back to default config, e.g. by forcing a reinstall of the galliumos-baytrail package: sudo apt-get install --reinstall galliumos-baytrail. Some additional notes on that in previously-linked ticket #180.)

ghost commented 7 years ago

Today, when I started up my computer it show an error log for a second saying failed to load firmware and the showed the login screen, I can't remember the exact same words but it was something like this. I'll try to reinstall the gallium os and revert back to "normal". If that doesn't work I'll try the MrChromebox's RW_LEGACY firmware (not BOOT_STUB because I'm afraid of bricking my device). I have to type the commands in order to get the firmware in the terminal or I have to enter to another shell or something (Ctrl+Alt+F2 to enter the shell of Chrome OS)? It may sound like a stupid question but I'm not used to these things.

ghost commented 7 years ago

Everything remained untouched! Even after changing the firmware everything is stuck at HDMI! What should I do now? Re-install Gallium OS formatting all my data?

reynhout commented 7 years ago

@Jimster121 I'm not sure I understand what state you're in right now. We need the exact error messages to be able to help.

If you're able to reinstall (no concerns about data loss), just go ahead and do so. If you need to preserve data, you can boot from USB and copy files from there. You should not need to install additional firmware after installing GalliumOS.

ghost commented 7 years ago

To sum up,

I'll re-install Gallium OS using a USB stick in order to get audio to work. If I get buggy sound again what should I do, because I am a bit confused with the #180 solutions.

ghost commented 7 years ago

Ok, I start to worry about my device because it cannot boot from USB Stick. It can only boot from my hard drive. I test with both the MrChromebox's & John Lewis' RW_LEGACY and when I press Esc and 1 to select the USB Stick it says Booting from Hard Disk... GRUB nothing else. It doesn't read/write anything to the USB Stick (it has a LED that blinks whenever a device reads/writes from/to the Stick). Is there something else I can do? I'm pretty sure my USB Stick is not the problem.

reynhout commented 7 years ago

@Jimster121 OK, again we've had reports that things can be spotty on RW_LEGACY. Resetting ALSA/pulseaudio config sometimes fixes it. If that doesn't work for you, you might want to try BOOT_STUB or full firmware if possible.

Regarding booting from USB... your USB drive, or the write to it, or possibly the download, is almost certainly the problem. It happens all the time. See troubleshooting steps at https://wiki.galliumos.org/Installing/Creating_Bootable_USB.

ghost commented 7 years ago

Ok, I've seen that page before, when I created a flash drive from a Windows 10 machine (Etcher) I noticed 2 partitions named GALLIUMOS when I did this on my Gallium OS installation, the flash drive had only 1. I don't know if it was my mistake or not but I'll try on the Windows 10 machine. I am pretty sure that my USB Drive is not the problem because:

  1. It's brand new
  2. I did the same thing on my SD Card and I got the same results

If the sound is not fixed after the installation, or after reseting the ALSA/pulseaudio config, is there another distribution that works with chromebooks/baytrail out of the box, or needs little configuration? And how I can revert back to Chrome OS? Thanks for the help by the way! 👍 🥇

reynhout commented 7 years ago

Yes, incorrectly-written USB drives are the most common problem. Bad USB hardware is the next most common, which can happen to brand new devices as well as old ones. Bad downloads are rare.

No other distro will have working audio. GalliumOS does have working audio, as a product of a lot of effort. As mentioned, it is more reliable on other firmware. Revert to ChromeOS with a ChromeOS Recovery Image.

ghost commented 7 years ago

Ok, everything seems to have revert back to normal after the installation, I'll continue checking for problems but for now it works. Thanks a lot :D

ghost commented 7 years ago

Hello again, I noticed that after sleep and wake up the speakers distort the sound and after plug/replug the headphone I get real audio. Is there a fix to that?

reynhout commented 7 years ago

@Jimster121 Quirks like you describe have been reported by others, and are tracked on #180. Switching to BOOT_STUB or full ROM firmware seems to resolve it.

ghost commented 7 years ago

Ok, thank you!

ghost commented 7 years ago

Hello again, I switched from RW_Legacy to BOOT_STUB (In order to avoid re-installing the OS again). To do that I removed the write-protect screw and then updated the new firmware. Everything works as expected, except the sound does the same thing as it did before. There is a workaround, replugging the headphones seems to solve the problem. When I noticed that, I opened up a terminal windows and entered the following command sudo apt-get install --reinstall galliumos-baytrail and rebooted. When I logged in again I had the same problem. Why does it keep happening? Do I have to re-install the OS? Or should I update the ROM firmware to "Full ROM" this time?

ghost commented 7 years ago

I changed firmware to Full ROM and formatted my device but I still have sound problems, what else can I try?

ghost commented 7 years ago

I found the solution here https://www.reddit.com/r/GalliumOS/comments/7aphlp/comment/dpyczso Thank you so much for your support :D