2014-12-06, 09:31
(2014-12-06, 08:33)rodalpho Wrote: Steam reports 268.44MB of GPU memory, and recommends using a bizarre sub-HD 1066x600 resolution.
Edit: Actually upon doing a bit of research, it looks like this may be a long-standing unfixed bug in Steam. How much memory is actually dedicated to the GPU in the coreboot/seabios version you distribute? Is it actually 256MB, or less?
https://github.com/ValveSoftware/steam-f...ssues/1562
https://github.com/ValveSoftware/steam-f...ssues/2897
https://github.com/ValveSoftware/steam-f...ssues/3418
Edit2: After more research it does look like it's actually 256MB, so can't blame a steam bug. 512MB would work a lot better for streaming.
Code:root@whiskeyjack:~# lspci -v -s 00:02.0
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: Google, Inc. Device c000
Flags: bus master, fast devsel, latency 0, IRQ 64
Memory at e0000000 (64-bit, non-prefetchable) [size=4M]
Memory at d0000000 (64-bit, prefetchable) [size=256M]
I/O ports at 3000 [size=64]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
unfortunately, while I can find where in the code the VGA aperture is set to 256MB, I can't figure out how to alter that value. I've asked on the coreboot IRC channel for help.
(2014-12-06, 09:20)snarby2014 Wrote: Matt, many thanks for the tip and fast reply! It was a setting in the hub - I had the windows computer to be always on so changed to 'turn off when not in use' and its working great. Just one more little issue I don't know if you can help with?
I have a boblight setup with an arduino connected via usb but when I put the chromebox into standby after resuming the lights don't work even though it comes up with the message 'connected to boblight'. I have checked the logs and nothing seems out of the ordinary, however if I disconnect the usb lead and put it back it starts working again. Is there any way to reset the usb port after resume?
while I'm not familiar with the boblight, I'd suspect you can reset the individual port it's connected to when resuming from suspend via script - OE provides a mechanism for this - I just don't know the particulars