Tuesday, May 24, 2022

Solved: no sound on Asus C200 Chromebook using GalliumOS

My Asus C200 Chromebook fell out of Google's Auto Update Policy in June, 2019. Chrome was on version 75, for example. I will leave my thoughts on this policy out of this post.

Since ChromeOS was no longer safe, I investigated alternative operating systems. And I chose to update it to GalliumOS. I removed the write protect screw, and then followed several tutorials on the web.

After using it a while, I noticed that it didn't play sounds. And investigating, I found that it couldn't play sounds.

Multiple searches didn't provide a straightforward solution. Some results were too cryptic, even though I know my way around Linux reasonably. Most just didn't work.

Finally, I stumbled on a solution that did work. I'll explain it here, hopefully with enough detail for a relative newbie.

First, I needed to see what sound card was in the box. I opened a terminal window, and typed
$ aplay -l

In the output, I found 

card 1: chtmax98090 [chtmax98090], device 0: 3

Armed with this information, I found this thread.
https://bugzilla.kernel.org/show_bug.cgi?id=195811
In the comments, there is mention of
Pierre's git repo:

https://github.com/plbossart/UCM

So, go to the github link and copy the chtmax98090 directory and files into this directory on your Chromebook:

/usr/share/alsa/ucm

Here's what that looked like for me:
$ cd /usr/share/alsa/ucm
$ sudo mkdir chtmax98090



There should be two files that you need in the github directory:
chtmax98090.conf
HiFi.conf

Copy those to your new directory
$ cd /usr/share/alsa/ucm/chtmax98090

[OK, I think the below will work, but to be honest, I did these using "sudo vi filename"]

$ sudo cat > chtmax98090.conf
...paste in your copied contents here....
<CTRL> D



$ sudo cat > HiFi.conf
...paste in your copied contents here....
<CTRL> D


In this string https://forums.linuxmint.com/viewtopic.php?t=312795, I found the comment:
"I solved it by adding the right files from this rep https://github.com/plbossart/UCM and ran this command...."

Of course, they used a different soundcard, so I substituted mine:
$ alsaucm -c chtmax98090 set _verb HiFi set _enadev Speaker

I then did

$ sudo alsa force-reload

And got sound! But it was garbled garbage. I rebooted, and then got music. Woo hoo!

Interestingly, every time I open Volume Control, if it has good sound, it becomes garbled. And if it is garbled, I get good sound. It may be a bit softer than it used to be, but maybe 80%? I'll try to fix these issues eventually, but not a top priority now.

I'm just happy to have sound out of my Chromebook again!

I have an even older Chromebook that is now running GalliumOS, but I haven't checked to see if it has sound. If not, I'll be following this instruction set on that box too. Good luck!

















Sunday, January 5, 2014

HP ProBook 4545s USB Flash Drive (Memory Key) trouble [SOLVED]

I bought a Windows 7 Professional refurb laptop and have been pleased with it so far.  However, it wouldn't read my Transcend 64gb USB key.  I tried all of the ports.  I tried updating the USB driver software from the HP support site.  I tried forcing the drive letter when mounting.  No joy.

The laptop would, however, read many other USB keys with no difficulty.  That helped -- it indicated that it wasn't the USB ports or USB driver issue.  Which was good, since I didn't really want to return the box.  Usually I can fix software issues -- hardware issues on laptops are more difficult.
I found a few others who were having this problem with their HP ProBooks also.  And it frustrated many of them.  After much searching, I stumbled across this post: http://www.tomshardware.com/forum/62374-63-windows-unable-read-flash-drives 

Sure enough, disabling "File Sanitation for HP Protect Tools" solved the problem.  To do this, I searched for Services: 



 Start - Services
When Services Opened, I sorted by name by clicking the "Name" header.


I then double-clicked on HP File Protect. And disabled that thing with extreme prejudice. :-)  Stop the service, and then also disable it on start up.

Then I inserted by Transcend 64 gb USB key and it came up cleanly. Stupid HP and their bloatware. Ugh.  Good luck to you and I hope this helps!