On Tue, 07 Jan 2014 20:58:54 +0100, Andreas Färber wrote:
Hi,
Am 07.01.2014 19:44, schrieb Jim Henderson:
1. On my setup, I'm getting a smaller graphical screen resolution (including on the text console) than 1920x1080. I've tried fiddling with the hdmi_mode and hdmi_group settings, but I still only am getting 1824x984 on the display.
IIRC disable_overscan=1 in Config.txt should address that. The default is for compatibility with TV screens.
Thanks, I'll give that a try. :)
http://elinux.org/RPiconfig#Video (although some options listed there may be outdated
We should probably add a commented out line in the corresponding .in script in the JeOS package to aid with that.
I ended up using information from elinux.org to force my setting to use 1080i (I have a long lower-quality HDMI cable leading to my projector, and it doesn't handle 1080p very well, but 1080i is fine).
I was unable to get gdm to work properly,
I reported the same for my Tegra2-based AC100 (somewhere hidden in the NEON thread), so that may be a general issue... Did you get a black screen, which after a while turned white with a message? Or something different?
Just the black screen - I didn't wait long enough for it to turn white (it would seem). I glanced through the logs and it seemed to be related to a permissions problem. I'll try duping it again later today or tomorrow and get the specific messages (I've rebuilt the sdcard image, so the logs are gone now).
I did, however, run into a SEGV error with e17 if I enabled hardware acceleration (I thought the pi had hardware accel available - but maybe I misunderstood the specs).
It might be that we're not installing some binary-only driver software?
Possibly. I'll have to look and see if there's a core file somewhere to get more info - e17 just popped a message up saying that it segfaulted and gave me options to try again or log out. Disabling hardware accel resolved it, so it seems to be clearly related to something in the video device or driver chain.
6. I noticed a number of services running that I hadn't asked for - cups/ cupsd in particular, but also modemmanager. Is there a reason that those services are configured to start automatically, rather than requiring the user explicitly enable them? (It seems like only necessary services - sshd, network, GUI if installed, Avahi - should be enabled by default, given the memory footprint considerations).
I think so far we get whatever is enabled on x86 openSUSE. Does uninstalling those packages work or are they a core dependency?
Uninstalling cups worked on the old image and didn't cause any problems - but when I disabled the services, YaST complained that the changes couldn't be written, and gave me "continue editing" or "cancel" options.
Great to hear that some things have improved for you.
Overall, I'm very happy with it. :) Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org