[opensuse-arm] A few things with the 13.1 image
I'm still going through the history of messages on the list, so pardon me if these have been covered already. 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. 2. It seems the snd_bcm2835 module isn't set up to autoload. I added it into a file in /etc/modules-load.d/ and that seems to have resolved it. 3. I'm happy to report that lightdm works well with e17 as a desktop. I was unable to get gdm to work properly, and just setting the window manager in /etc/sysconfig/windowmanager to run e17 didn't work, but selecting it with lightdm did. 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). 4. The issues I mentioned on factory with library dependencies being missing to get mopidy working are not a problem with the 13.1 image and its repositories. 5. I did run into the partition size issue for the BOOT partition, which probably was to be expected. Once I did that and had the system connected to my projector, I was pleased to see the firstboot process that was in place. My wireless adapter (using the rt2800 driver, it looks like) was detected and ran perfectly. That also was a change over the image on the wiki page - with that one, I had to install the firmware to get it working. 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). 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
On Tue, 07 Jan 2014 18:44:02 +0000, Jim Henderson wrote:
I'm still going through the history of messages on the list, so pardon me if these have been covered already.
Sorry, I should've mentioned - this is the RPi image that I'm talking about. :) 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
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. 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 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?
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?
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? Great to hear that some things have improved for you. Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
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
On Tue, 07 Jan 2014 20:09:57 +0000, Jim Henderson wrote:
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. :)
Confirmed, that solved it. I should have time tomorrow to test some of the other things on the list. 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
Am 08.01.2014 07:02, schrieb Jim Henderson:
On Tue, 07 Jan 2014 20:09:57 +0000, Jim Henderson wrote:
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. :)
Confirmed, that solved it.
I should have time tomorrow to test some of the other things on the list.
Some more things to test would be in Config.txt: ramfsfile=boot/initrd.uboot # or copy file over into root dir of BOOT ramfsaddr= 0x00800000 and checking if kiwi resizes the ext4 partition then. But U-Boot support is already on its way, we're still in need of a new initrd for testing our changes. ;) Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Wed, 08 Jan 2014 18:26:41 +0100, Andreas Färber wrote:
Some more things to test would be in Config.txt:
ramfsfile=boot/initrd.uboot # or copy file over into root dir of BOOT ramfsaddr= 0x00800000
and checking if kiwi resizes the ext4 partition then.
But U-Boot support is already on its way, we're still in need of a new initrd for testing our changes. ;)
I'm happy to try those things out - what should I expect to see? :) 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
On Wed, 08 Jan 2014 18:26:41 +0100, Andreas Färber wrote:
Some more things to test would be in Config.txt:
ramfsfile=boot/initrd.uboot # or copy file over into root dir of BOOT ramfsaddr= 0x00800000
Adding these two lines resulted in the system not booting. I got the "rainbow" square screen, then it changed to solid red, then to a blue/ black gradient from left to right.
and checking if kiwi resizes the ext4 partition then.
But U-Boot support is already on its way, we're still in need of a new initrd for testing our changes.
I wonder if this would be why I saw what I did. Removing the lines from config.txt let the system boot normally. I tested this with the build dated 1/8. 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
Am 10.01.2014 07:11, schrieb Jim Henderson:
On Wed, 08 Jan 2014 18:26:41 +0100, Andreas Färber wrote:
Some more things to test would be in Config.txt:
ramfsfile=boot/initrd.uboot # or copy file over into root dir of BOOT ramfsaddr= 0x00800000
Adding these two lines resulted in the system not booting. I got the "rainbow" square screen, then it changed to solid red, then to a blue/ black gradient from left to right.
Did you also try variations of the ramfsfile= line as indicated? initramfs would be another config option to try.
and checking if kiwi resizes the ext4 partition then.
But U-Boot support is already on its way, we're still in need of a new initrd for testing our changes.
I wonder if this would be why I saw what I did.
No, that's two separate things: Actually using the initrd that kiwi writes into the image on the one hand, and getting the latest openSUSE kernel to work with device tree and U-Boot on the other. Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Fri, 10 Jan 2014 18:18:02 +0100, Andreas Färber wrote:
Adding these two lines resulted in the system not booting. I got the "rainbow" square screen, then it changed to solid red, then to a blue/ black gradient from left to right.
Did you also try variations of the ramfsfile= line as indicated? initramfs would be another config option to try.
I didn't, but I can.
and checking if kiwi resizes the ext4 partition then.
But U-Boot support is already on its way, we're still in need of a new initrd for testing our changes.
I wonder if this would be why I saw what I did.
No, that's two separate things: Actually using the initrd that kiwi writes into the image on the one hand, and getting the latest openSUSE kernel to work with device tree and U-Boot on the other.
Ah, OK, I misunderstood. 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
On Fri, 10 Jan 2014 18:18:02 +0100, Andreas Färber wrote:
Am 10.01.2014 07:11, schrieb Jim Henderson:
On Wed, 08 Jan 2014 18:26:41 +0100, Andreas Färber wrote:
Some more things to test would be in Config.txt:
ramfsfile=boot/initrd.uboot # or copy file over into root dir of BOOT ramfsaddr= 0x00800000
Adding these two lines resulted in the system not booting. I got the "rainbow" square screen, then it changed to solid red, then to a blue/ black gradient from left to right.
Did you also try variations of the ramfsfile= line as indicated? initramfs would be another config option to try.
For this option, should I see initramfs as a file in the filesystem? If I should, I don't. I'm wondering if it would be more useful for me to test these things with the factory image rather than the 13.1 image, also. 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
On Tue, 07 Jan 2014 20:09:57 +0000, Jim Henderson wrote:
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.
I just ran into it again after upgrading the firmware (looks like it's just a binary blob that resides on the boot partition), but it looks like no core file is generated. The error this time may be different than the last time, though, because I didn't enable hw acceleration. 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
participants (2)
-
Andreas Färber -
Jim Henderson