November 2014 - openSUSE ARM - openSUSE Mailing Lists

Re: [opensuse-arm] How to resize 13.2 Raspberry Pi image
by Freek de Kruijf 26 Nov '14

26 Nov '14

Op dinsdag 25 november 2014 14:09:06 schreef u: > On 25/11/14 09:32, Freek de Kruijf wrote: > > Op dinsdag 25 november 2014 04:00:44 schreef Sid Boyce: > >> I use large sizes of SD cards. > >> > >> After burning the image, e.g to /dev/sdb, remove the SD card and insert > >> it again. > >> > >> "gparted /dev/sdb" > >> > >> Add the space of the rootfs partition to the unused space and change > >> rootfs to the total calculated, click resize and Apply. > >> Regards > >> Sid. > > > > I did that on a 16 GB card and removed /var/lib/YaST2/reconfig_system in > > order to be able to use it headless, but that did not work. > > However putting the freshly burned image in the RPi removing the card a > > little later from the RPi, removing /var/lib/YaST2/reconfig_system and > > reinserting the card in the RPi gave me a working system, accessible via > > ssh and with a large rootfs. There is also a swap partition at the end of > > about 500 MiB. Will try to remove that reconfig file right after burning > > to see if I get a working headless system with expanded rootfs. > > That's strange as I have always done it that way on Beaglebone, > Pandaboard, ODROID-X, ODROID-U3 and Parallella-16. > > I always do "fsck -a /dev/sdb[12]" after resizing and on the odd > occasion it reports that it cleared a dirty bit on the VFAT partition. > Successfully boots every time. > Regards > Sid. When applying the 13.2 image on the SD card, now there are three partitions on the card. A FAT partition, an ext3 partition and the rootfs is ext4. After initial use on the RPi there is a fourth partition at the end, a swap partition. So are we talking about the same type of image, a 13.2 image? I tried the procedure to remove the reconfig file right after burning and before actually using the card in the RPi, but that did not work. Did not do a "fsck -a /dev/sdg{123}" after burning. Should I? BTW. I noticed a change in naming of the image, first I used: openSUSE-13.2-ARM-JeOS-raspberrypi.armv7l-1.12.1-Build29.4.raw.xz now I use: openSUSE-13.2-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build30.1.raw.xz If I am right the architecture of the RPi is armv6l and not armv7l, isn't it? So now we have a properly named image? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 6

[opensuse-arm] How to resize 13.2 Raspberry Pi image
by Dirk Stöcker 26 Nov '14

26 Nov '14

Hello, I installed following image on a Raspberry Pi http://download.opensuse.org/repositories/devel:/ARM:/13.2:/Contrib:/Raspbe… It does work fine and I even now got my hardware drivers compiled which did not succeed with 13.1. Thanks a lot to all people involved. One question I do have thought: I tried to resize the system after it was installed or before it auto-installs, but was unable to do it. Fixing it before installation fails as I do not find the releavnt sections in the image (probably they are zipped, so string search does not help). Resizing afterwards with yast2 on another machine resulted in a broken image (probably boot loader or MBR breaks?). Does anybody have any hint how I can change the automatic size settings to something which fits my individual requirements? P.S. A slight error: the Raspberry contrib repository URL ends in "openSUSE_13.2", but the real URL is "standard". Either the image or OBS should be fixed. Ciao -- http://www.dstoecker.eu/ (PGP key available) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 7

Re: [opensuse-arm] Re: BeagleBone Black stuck at 3 LEDs.
by Matwey V. Kornilov 25 Nov '14

25 Nov '14

2014-11-22 23:44 GMT+03:00 Zack Piper <zack(a)apertron.net>: > The BeagleBone Black JeOS image, I have not been using the boot switch button, I have tried it, no LEDs lightup. Which version? 13.1 13.2 Factory? > Another qustion, does the openSUSE image automatically activate a tty-over-USB at all? No -- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 15

[opensuse-arm] Using image 13.2 headless
by Freek de Kruijf 23 Nov '14

23 Nov '14

I copied the 13.2 JeOS-raspberrypi image onto my SD card and tried to use it headless by connecting to it via "ssh root@<IP-address>", which gives me a prompt for the password. However the password linux does not give me access. What is the password or is there something else I should so? Copying the image to a 16 GB SD card gives me four partitions, a small FAT16 BOOT partition at the beginning and a very small empty partition, a large ext4 partition and a swap partition of about 520 MB at the end. The large ext4 partition takes all the remaining space on the SD card. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 8

[opensuse-arm] BeagleBone Black stuck at 3 LEDs.
by Zack Piper 22 Nov '14

22 Nov '14

Hi, I'm currently debugging my BeagleBone Black, when booting, it gets stuck at 3 LEDs. Is there anyway to debug it without a miniHDMI cable or serial cable? Thanks. -- I have nothing fancy or intelligent to put here.

2 1

[opensuse-arm] u-boot supported boards cleanup
by Guillaume Gardet 21 Nov '14

21 Nov '14

Hi, I think there are at least 2 boards built as u-boot RPMs, which may be no more used (no 13.2/Facotry JeOS images are currently using it): * mx53loco * colibri_t20_iris Is there anyone still using those u-boot RPM or having boards to test some images? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 18

[opensuse-arm] Dracut does not add sunxi-mmc to initrd
by Oscar C 19 Nov '14

19 Nov '14

Hi, While building a JeOS image for sunxi I found a problem with the current version of dracut (0.37) in factory. It doesn't include the needed kernel module (sunxi-mmc) when creating the initrd. After the first boot the root partition cannot be found. This seems to be already fixed in dracut 0.38 (see bug https://bugzilla.redhat.com/show_bug.cgi?id=1097301) not only for sunxi but also for other boards. The solutions are: - Patch the current dracut to include sunxi-mmc (the patch is rather trivial). - Update dracut in factory to 0.38 and squash all the new bugs that can appear. -- Oscar. Cheers, -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 9

Re: [opensuse-arm] u-boot supported boards cleanup
by Guillaume Gardet 19 Nov '14

19 Nov '14

Le 19/11/2014 16:56, Dirk Müller a écrit : > > Hi Guillaume, > > Does it harm to have those packages available? I'd only like to remove it if we.think it is obsolete or know that it is broken IMHO.. > It does not harm, but I would like to be sure that all our targets are working fine (and if our patches could go upstream). Guillaume -- 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] 13.2 GFX images
by Guillaume Gardet 19 Nov '14

19 Nov '14

Hi, panda board has no graphical images in 13.2, only JeOS. HDMI output works, so, please enable E17 and XFCE images for pandaboard in 13.2:Ports. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 4

[opensuse-arm] Yast2-Firstboot: bugs
by Josua Mayer 18 Nov '14

18 Nov '14

Hello everyone, Yesterday I tried a 13.2 e17 image on the cubox-i (build day was 31.10.) and noticed 2 problems with yast2-firstboot: First an error shows about failed dhcp module. I checked the rmentioned logfile and the error said it didn't find the firstboot_dhcp module (I dont remember exact message anymore and can't check). Then the keyboard module failed to, showing that same error dialog instead of keymap selection screen. The remainder of yast2-firstboot works fine. while one can live with dhcp module broken, I think the keyboard layout is much more important from a users perspective. Also, There is again no webbrowser in the images. Should we add chromium? I finally built a firefox armv7l package, and the same fix should apply to armv6l but I don't think packages will be rebuilt before 13.2. best regards Josua Mayer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 4