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

Skylake Platform Validation #274

Open reynhout opened 8 years ago

reynhout commented 8 years ago

Tracking validation tests and bug reports for GalliumOS support for Skylake models.

Please add observations for any Skylake model in comments!

Current Skylake status

volfyd commented 6 years ago

no-err-check-desg.txt

divadsn commented 6 years ago

Does the same apply for LARS? @volfyd @ojab

ojab commented 6 years ago

It applies to any intel chromebook that lacks audio due to missing (i. e. compatible only with ChromeOS kernel, not upstream one) topology file.

LufyCZ commented 6 years ago

Keyboard backlight control works on Ubuntu 18.04, LARS

MrChromebox commented 6 years ago

@ojab did you ever get your topology binary parser to work? And is the source available anywhere? Seems like getting Intel to post these for newer ChromeOS devices might be more difficult than RE'ing them

nebulakl commented 6 years ago

I filed a bug on bugzilla like @ojab did for CAVE. Let's hope we can get the topology.conf (and working audio) soon. You may follow the thread here: https://bugzilla.kernel.org/show_bug.cgi?id=200963

ozamyatin commented 5 years ago

Hello, guys! Is there any easy way to get audio working in GalliumOS/Ubuntu for our device? Like running a one simple script? Or, is there a chance of firmware update for our device coming soon? I am not really a tech guy, so I cannot fully understand everything happening in this thread. Please, help.

nebulakl commented 5 years ago

@ozamyatin The easiest way is either use Bluetooth audio or USB audio.

ozamyatin commented 5 years ago

@ozamyatin The easiest way is either use Bluetooth audio or USB audio.

@nebulakl Thank you very much!

thoughtchad commented 5 years ago

@ozamyatin The easiest way is either use Bluetooth audio or USB audio.

I've also found that attaching an external monitor (with speakers or which has audio out) via hdmi (if your chromebook has hdmi) will also provide audio through the hdmi audio channel.

colpanek commented 5 years ago

I installed QasMixer and fiddled with the headphones autodetect until it worked right on my Pixel (LINK). Not sure if that's the issue you're having. Jim

Jim & Mary Margaret Van Damme Couple to Couple League-Central New York http://nfp.freehostia.com/ <=Natural Family Planning info Sent from my Linux PC

simonheb commented 5 years ago

Does anyone else have problems with reading SD cards? I run CAVE and I can't seem to figure out how to access my SD card reader. With no card in I get a lot of 

[  430.050959] mmc1: Timeout waiting for hardware cmd interrupt.
[  430.050975] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========

I think this is normal, as soon as I insert one this stops, but lsblk still does not list anything:

NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
zram0        252:0    0  5.6G  0 disk [SWAP]
mmcblk0      179:0    0 58.2G  0 disk 
├─mmcblk0p4  179:4    0   16M  0 part 
├─mmcblk0p12 259:4    0   16M  0 part 
├─mmcblk0p2  179:2    0   16M  0 part 
├─mmcblk0p10 259:2    0  512B  0 part 
├─mmcblk0p9  259:1    0  512B  0 part 
├─mmcblk0p7  179:7    0   50G  0 part /
├─mmcblk0p5  179:5    0    2G  0 part 
├─mmcblk0p3  179:3    0    2G  0 part 
├─mmcblk0p11 259:3    0    8M  0 part 
├─mmcblk0p1  179:1    0  4.1G  0 part 
├─mmcblk0p8  259:0    0   16M  0 part 
└─mmcblk0p6  179:6    0   16M  0 part

finally, #simon@chrx:~$ journalctl |grep -P mmc\\d yields only

Oct 02 09:39:00 chrx kernel: mmc0: SDHCI controller on PCI [0000:00:1e.4] using ADMA 64-bit
Oct 02 09:39:00 chrx kernel: mmc1: SDHCI controller on PCI [0000:00:1e.6] using ADMA 64-bit
Oct 02 09:39:00 chrx kernel: mmc0: new HS400 MMC card at address 0001
Oct 02 09:39:00 chrx kernel: mmcblk0: mmc0:0001 DF4064 58.2 GiB

Do you experience the same?

azertyfun commented 5 years ago

Works fine for me on LARS.

With no SD card I don't get any timeouts or register dumps, I don't think that's normal behavior:

$ dmesg | grep mmc
[    0.918207] mmc0: SDHCI controller on PCI [0000:00:1e.4] using ADMA 64-bit
[    1.005415] mmc0: new HS400 MMC card at address 0001
[    1.011840] mmcblk0: mmc0:0001 BJNB4R 29.1 GiB 
[    1.012118] mmcblk0boot0: mmc0:0001 BJNB4R partition 1 4.00 MiB
[    1.012371] mmcblk0boot1: mmc0:0001 BJNB4R partition 2 4.00 MiB
[    1.012477] mmcblk0rpmb: mmc0:0001 BJNB4R partition 3 4.00 MiB, chardev (242:0)
[    1.016757]  mmcblk0: p1 p2
simonheb commented 5 years ago

I think it's "normal" because reynhout wrote something about this e.g. here "[...]on the newest kernel, Skylake models have an issue with a phantom SD card reader, which will slow down suspend and shutdown. The easiest workaround is to install an SD card [...] into the SD card reader" (https://www.reddit.com/r/GalliumOS/comments/8wxpq9/samsung_chromebook_pro_no_audio_and_dual_boot/e1zaatw). Now that I read this again, I realize that he says "phantom sd card reader" suggesting that mmc1 is not my actual reader. So maybe my sd-reader is actually dead... Any ideas on how to find this out? Can someone on GalliumOS on a C302CA post an lscpi and dmesg|grep mmc?

MrChromebox commented 5 years ago

@simonheb the "reader" part of that was an error. Newer kernels have an issue with the card detection, thinking there is an SD card installed when one is not, which cases all the errors. Boot with the SD card inserted and it should be readable in the OS

simonheb commented 5 years ago

@MrChromebox, thanks! When I boot with the SD card inserted, I don't get the Timeouts, but I still cannot mount the SD card, lsblk only lists mmcblk0, and dmesg single entry containing mmc1 is mmc1: SDHCI controller on PCI [0000:00:1e.6] using ADMA 64-bit. (The card I'm using is 64GB, Samsung and is working fine on my android phone).

simonheb commented 5 years ago

To be precise, dmesg reads:

simon@chrx:~$ dmesg |grep mmc -B2 -A2
...
[    0.779361] sdhci: Copyright(c) Pierre Ossman
[    0.781668] sdhci-pci 0000:00:1e.4: SDHCI controller found [8086:9d2b] (rev 21)
[    0.782895] mmc0: SDHCI controller on PCI [0000:00:1e.4] using ADMA 64-bit
[    0.782996] sdhci-pci 0000:00:1e.6: SDHCI controller found [8086:9d2d] (rev 21)
[    0.783204] sdhci-pci 0000:00:1e.6: failed to setup card detect gpio
[    0.785439] mmc1: SDHCI controller on PCI [0000:00:1e.6] using ADMA 64-bit
[    0.844215] [drm] Memory usable by graphics device = 4096M
...

Any hints on how to further find the source of the problem are appreciated!

Since inserting the SD card changes the behaviour (suppresses the Timeouts) i am optimistic that the SD card reader is not shorted or broken, but I can't seem to get it to work

ReichardKonige commented 5 years ago

Using a HP Chromebook 13 G1

Suspend appears to mostly work for me with the following two issues:

  • XScreensaver login window coming out of restore is functional but the base texture of the window looks like there is a video memory corruption issue.
  • Wifi broke when coming out of restore (dmesg shows "wlp1s0: link not ready" messages)

Other stuff:

  • Touchpad is slightly unresponsive on first touch, maybe just a characteristic of the hardware (new unfamiliar laptop).
  • Sound / Mic don't work as mentioned above.
  • Keyboard backlighting doesn't work
  • 3200x1800 resolution on this laptop requires some UI fiddling to make text readable / buttons clickable

For hidpi Install alternative like KDE (apparently uses less memory than XFCE now) or follow the instructions from this website to get XFCE looking well. https://wiki.archlinux.org/index.php/HiDPI#Xfce

bcarnes commented 5 years ago

Caroline under a 3.0beta2 install has suspend/resume problems.

Details:

[41763.241110] Disabling non-boot CPUs ...
[41763.251161] WARNING: CPU: 1 PID: 7225 at kernel/kthread.c:486 kthread_park+0x5a/0x70
...
[41763.298281] ACPI: Waking up from system sleep state S3
[41764.367592] i2c_designware i2c_designware.0: controller timed out
[41764.405234] i2c_designware i2c_designware.0: timeout in disabling adapter
[41764.405259] atmel_mxt_ts i2c-ATML0001:00: __mxt_read_reg: i2c transfer failed (-110)
[41764.405263] atmel_mxt_ts i2c-ATML0001:00: Failed to read T44 and T5 (-110)
[41764.431094] i2c_designware i2c_designware.0: timeout waiting for bus ready

And then those last 3 messages spew forever touchscreen (which needs that i2c bus) fails to work need to reboot to clear up this state.

Workaround (do this before your first suspend): echo s2idle > /sys/power/mem_sleep

mem_sleep states available on Caroline:

# cat /sys/power/mem_sleep 
s2idle [deep]

Where "deep" is the default that is buggy

ozamyatin commented 5 years ago

Guys, I can confirm speakers and microphone both working, but very silent on CHELL (HP Chromebook 13 G1) latest GalliumOS RC 3.0 out of the box.

etbusch commented 5 years ago

3.0 release has audio working on CAVE, but speaker output is has static and the gain is set way too high. Headphones and headphone switch work well.

catagris commented 2 years ago

Speakers have stopped showing up following the most recent update on my Samsung Chromebook Pro XE510C24