September 2013 - openSUSE ARM - openSUSE Mailing Lists

Re: [opensuse-arm] Re: Re : [opensuse-arm] Raspberry Pi: might we go to kernel 3.6.x?
by Chuck Payne 09 Sep '13

09 Sep '13

+1 on this. On Mon, Sep 9, 2013 at 3:43 PM, Stefan Seyfried <stefan.seyfried(a)googlemail.com> wrote: > Am 09.09.2013 21:33, schrieb guillaume.gardet(a)free.fr: >> Hi, >> >> >> ----- Stefan Seyfried <stefan.seyfried(a)googlemail.com> a écrit : >>> Hi all, >>> >>> after Andreas' and Guillaume's great HOWTO, I finally pulled out my >>> raspi over the weekend and played with it. >>> >>> It works pretty well. >>> However, the system is pretty unstable with the 3.1 kernel. >>> I noticed when trying to build ffmpeg from source. Lots of strange >>> errors, from ext4 complaining about delayed allocation to spurios >>> "ENOPERM" when closing temporary files during compilation etc. >>> Also, the raspberrypi-gfx demo/test tools did not work, erroring with >>> messages about "vcihq not connected" in dmesg. >>> >>> Additionally, my 512MB Raspi only had 256MB available, no matter what >>> amount of gpu_mem I put into config.txt. >>> >>> Then I simply grabbed the binary kernel and modules from >>> https://github.com/raspberrypi/linux and new firmware from >>> https://github.com/raspberrypi/firmware and voila -- the little box was >>> running stable. >>> >>> So I took the kernel from >>> devel:ARM:Factory:Contrib:RaspberryPi:kernel-3.6 and updated the patch >>> set to yesterdays git and changed the configuration to be pretty similar >>> to what is in the "upstream" git. >> >> Sounds good. :) >> >>> >>> I also updated the firmware package. >>> >>> Both together run very fine for me. I have all RAM available, the test >>> tools work, etc.pp. >>> >>> So maybe it would make sense to use the 3.6.11 kernel as "upstream" >>> Raspberry Pi also does? >> >> Make sense to me. >> >>> >>> I created SRs 198076 (raspberrypi-firmware) and 198080 >>> (kernel-raspberrypi) and maybe we should use >>> devel:ARM:Factory:Contrib:RaspberryPi:kernel-3.6 as the default raspi >>> kernel? >> >> I accepted your firmware patch but I have not the rigths to accept kernel SR. > > Well, if nobody objects, I could just SR it to Contrib:Raspi (without > :kernel-3.6 subproject), but I'd wait for comments before doing so :-) > >> Thanks for your help. > > Actually, I sort of promised Alex at the Chemnitz Linux Days in spring > that I would try to get openSUSE on Raspi into good shape, but > unfortunately got always sidetracked. So helping out now that the hard > work is done is the least I can do :-) > > Best regards, > > Stefan > > P.S: I built the kernel in home:seife:ARM so you can take it from there > for testing. > -- > Stefan Seyfried > "If your lighter runs out of fluid or flint and stops making > fire, and you can't be bothered to figure out about lighter > fluid or flint, that is not Zippo's fault." -- bkw > -- > To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org > -- Terror PUP a.k.a Chuck "PUP" Payne (678) 636-9678 ----------------------------------------- Discover it! Enjoy it! Share it! openSUSE Linux. ----------------------------------------- openSUSE -- en.opensuse.org/User:Terrorpup openSUSE Ambassador/openSUSE Member Community Manager -- Southeast Linux Foundation (SELF) skype,twiiter,identica,friendfeed -- terrorpup freenode(irc) --terrorpup/lupinstein Register Linux Userid: 155363 Have you tried SUSE Studio? Need to create a Live CD, an app you want to package and distribute , or create your own linux distro. Give SUSE Studio a try. www.susestudio.com. See you at Southeast Linux Fest, June 7-9, 2013 in Charlotte, NC. www.southeastlinuxfest.org -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] Chroot error while building kiwi arm image
by Oscar C 09 Sep '13

09 Sep '13

Hi, I'm trying to build a modified kiwi image for Cubieboard (forked from devel:ARM:12.3:Contrib:sunxi/JeOS-cubieboard). When I try to build it, it gives me the following error: [ 39s] running aaa_base preinstall script [ 39s] chroot: failed to run command 'sh': Exec format error [ 39s] running aaa_base postinstall script [ 39s] chroot: failed to run command 'sh': Exec format error [ 39s] running qemu-accel-armv7hl postinstall script [ 39s] chroot: failed to run command 'sh': Exec format error [ 39s] initializing rpm db... [ 39s] chroot: failed to run command 'rpm': Exec format error At first i thought that qemu was incorrectly setup, but after some tests I think everything is OK. For example, I can execute a "hello world" test program compiled in arm just fine from the command line: oscar@gardenia:~> file hello_world-arm-static hello_world-arm-static: ELF 32-bit LSB executable, ARM, version 1, statically linked, for GNU/Linux 2.6.9, stripped oscar@gardenia:~> ./hello_world-arm-static -->Hello world using ARM! Any ideas for whats happening here? -- Cheers -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 2

[opensuse-arm] How-to: ARMv6 Factory on Raspberry Pi (preliminary)
by Andreas Färber 08 Sep '13

08 Sep '13

Hello, Here's a quick reconstruction of how I got current openSUSE Factory running on a Raspberry Pi Model B. Unlike Bernhard's image this should be future-proof (armv6) but is targeting experienced Linux users; beginners should better wait to download an official 13.1 image. 1.) Build an ARMv6 JeOS rootfs $ osc co openSUSE:Factory:ARM JeOS.armv6 $ cd openSUSE:Factory:ARM/JeOS.armv6 $ osc build --alternative-project=openSUSE:Factory:ARM images armv6l Grab from the buildroot usr/src/packages/KIWI/openSUSE-Factory-ARM-JeOS-rootfs.armv7l-1.12.1.tbz (version will vary; for some reason it's misnamed armv7l). Note that the reason I am doing this is that Factory is not publishing images ATM. And for the same reason the image will contain packages that have not yet been published, later visible as "(System Package)" in `zypper se -i -s` on the RPi. 2.) Partition an SD card Using gnome-disks, parted, fdisk or any other tool of your liking, format the SD card using MBR partitioning scheme with at least one FAT partition and one Linux (e.g., ext4) partition. You may need to tweak the partition type of the FAT partition from "Linux" to "W95 FAT16" or the like. 3.) Prepare boot partition Mount the FAT partition. Download the following packages from http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Ras… * raspberrypi-firmware * u-boot-rpib * kernel-raspberrypi Extract the ./boot/ files from raspberrypi-firmware .rpm to the root of the FAT partition. Extract u-boot.bin from u-boot-rpib .rpm as loader.bin to the root of the FAT partition. Extract the ./boot/ files from kernel-raspberrypi .rpm to the root of the FAT partition and copy Image-* file as kernel.img. config.txt or cmdline.txt files were not strictly necessary in my case. Cf. Bernhard's image or Google for examples. 4.) Prepare root partition Mount the ext4 partition. Extract the rootfs using # tar xvjf path/to/openSUSE-Factory-ARM-JeOS-rootfs.armv7l-1.12.1.tbz (I did # rpm2cpio path/to/raspberrypi-gfx-*.rpm | cpio -idvm on top, but better install it later via zypper when needed). 5.) Have a lot of fun Sync, unmount, insert the SD card, etc. Connecting micro USB for power, you should see on HDMI output a colored rectangle, followed by kernel output with a Raspberry Pi logo. If you see a black screen only, check the partitioning. If you see the colored screen only, check the files in FAT partition. If you get an illegal instruction terminating YaST firstboot, see Guillaume's libopenssl/openssl workaround. To rerun firstboot afterwards, touch /var/lib/YaST/reconfig_system followed by reboot. The fix has been accepted into Base:System and there is no link diff to openSUSE:Factory, so hopefully by the time you build your JeOS this will no longer be an issue. Hint: Having connected the Raspberry Pi to a TV with no wired network available, I found it handy to use the shared IPv4 setting in GNOME network preferences on my notebook to have the Raspberry Pi connect to Wifi/Internet via cable to the notebook - for NTP among other things. HTH, 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(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 7

[opensuse-arm] Please update kiwi to latest available version for Factory:ARM
by Guillaume Gardet 06 Sep '13

06 Sep '13

Hi, Could you update kiwi to latest available version from Virtualization:Appliances for Factory:ARM, please? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 16

[opensuse-arm] Factory:Contrib for armStoneA8
by Andreas Färber 02 Sep '13

02 Sep '13

Hello, Can someone please create a "Contrib:armStone" subproject for devel:ARM:Factory and make me maintainer please? kernel-f+s from https://build.opensuse.org/project/show/openSUSE:12.2:ARM:Contrib:Armstone has been working fine on 12.3. Thanks, 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(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 5

[opensuse-arm] Re: No login with ttyS0 (JeOS for cubieboard)
by Johannes Nohl 01 Sep '13

01 Sep '13

Thanks for your help, Guillaume and Tony. It turned out that the system was frozen. Login works as expected on ttyS0. Unfortunately the kernel coming with the cubieboard-image (3.4.29) has issues but I can't tell for sure what it is. I suspect the wemac ethernet driver. I compiled a new kernel (3.4.43) from the sunxi sources at github. It works but it still has issues. Anyway I can boot beyond the login now. Johannes 2013/8/20 Johannes Nohl <johannes.nohl(a)gmail.com>: > Does someone know what I have to do to get a login on ttyS0? I can see > cubieboard in the serial console booting, from u-boot to kernel, ending > with: > > [ OK ] Started D-Bus System Message Bus. > [ OK ] Started Login Service. > [ OK ] Started YaST2 Firstboot. > > I tried to utilze systemd by adding serial-getty to the services: > > ln -s /usr/lib/systemd/system/serial-getty@.service > /etc/systemd/system/getty.target.wants/serial-getty(a)ttyS0.service > > I used the image from > http://download.opensuse.org/repositories/devel:/ARM:/12.3:/Contrib:/sunxi/…. > > Additionally I don't get eth0 up, whether on dhcp or static. Therefore I > can't ssh inside. I really need the serial console. > > One of u-boot's env parameters is console=ttyS0,115200 (which isn't needed > to see the boot stuff) so I guess the kernel takes this as an option. > > I'm thinking I'm missing stuff here because the underlaying JeOS is pretty > small. Buz e.g. agetty is installed... > > Who can help me here? > > Johannes -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0