Re: [opensuse-arm] Re: New Raspberry Pi image available
Op vrijdag 6 september 2013 11:40:13 schreef Chuck Payne: Guillaume, Thanks, I am making my SD Card now. Chuck I already did, but the card did not show up on my system with a proper partition table. Will try again. I used unxz [image].raw.xz dd bs=4M if=[image].raw of=/dev/sdX; sync Will try later: xzcat [image].raw.xz | dd bs=4M of=/dev/sdX; sync -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Re: New Raspberry Pi image available
Op maandag 9 september 2013 13:46:34 schreef Guillaume Gardet: Le 09/09/2013 13:26, Freek de Kruijf a écrit : I found a problem after inserting a WiFi USB stick. It reported a non existing folder, /lib/modules/3.1.10-5-raspberrypi. There is an existing folder /lib/modules/3.11.0-rc4-5-default, so I made a symbolic link to have the first pointing to the last. This solved the problem of the error messages. The WiFi USB stick is a Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter. So I tried modprobe -i rtl8188ee, but I got several messages Invalid module format. Should I make a bug report? Try to install kernel-raspberrypi using zypper (and remove kernel-default also). It should solve your problems. It did not. I don't see a network device for the WiFi USB stick, although lsmod shows several modules hinting to this device, but not with rtl8188 in it. Any suggestions? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] zypper up raspberrypi-gfx gives error
On maandag 16 september 2013 08:47:48 wrote guillaume.gar...@free.fr: - Freek de Kruijf fr...@opensuse.org a écrit : I did a zypper up and found a few raspberry packages to be updated. One of them, raspberrypi-gfx, however refuses to be installed. Try a zypper rm and then a zypper in on this package. Guillaume That did the trick. Thanks. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] clamav not available on openSUSE 13.1 repository for armv6hl
I could not find the package clamav on the openSUSE 13.1 repository for armv6hl (Raspberry Pi). Checking the openSUSE build service it appears that clamav is locked, so no longer build, in that repository, but in a security repository, which does not do a build for armv6hl. In the security repository the package is build OK for the enabled architectures. How can I be of help to make it build for armv6hl and other architectures? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] clamav not available on openSUSE 13.1 repository for armv6hl
Op dinsdag 4 februari 2014 14:35:06 schreef Freek de Kruijf: Op dinsdag 4 februari 2014 13:49:18 schreef Andreas Schwab: Freek de Kruijf fr...@opensuse.org writes: Please give me some hints, how to proceed and where and what to branch. Once you have branched it you can additional architectures to the project configuration in your branch. I want to build clamav for openSUSE 13.1, so should I branch openSUSE 13.1 / clamav? However there is no openSUSE:13.1:Update repository for armv6l to which I assume the result should be committed. This is because I am using the newest RaspberryPi image in a test Raspberry PI, which only has the openSUSE 13.1 oss repository. I could not find any additional repository. I played around on the OBS website branching security:clamav, but this one did not have a possibility to add the armv6l architecture. At least I could not find that possibility. I could find setting a repository to include armv6l, but I could not find a way to branch clamav into that repository. So I need some help to continue. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] clamav not available on openSUSE 13.1 repository for armv6hl
Op woensdag 5 februari 2014 12:23:40 schreef u: Freek de Kruijf fr...@opensuse.org writes: I played around on the OBS website branching security:clamav, but this one did not have a possibility to add the armv6l architecture. You'll need to add a new repository that points to openSUSE:Factory:ARM. For openSUSE:13.1:Update you are SOL, unfortunately, since it isn't set up to build for armv6l. Andreas. I branched security:clamav as a subproject of my home project for openSUSE:Factory:ARM and did set three architectures: armv6l, armv7l and aarch64. It has build OK for the first two architectures, the last one is blocked. So what should I do next, apart from trying to use the build clamav on my Raspberry Pi? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] OpenSuse-Version for the Raspberry Pi
Op zaterdag 2 augustus 2014 07:57:16 schreef Edgar Dombrowski: Am 01.08.2014 20:40, schrieb Freek de Kruijf: See https://en.opensuse.org/HCL:Raspberry_Pi Hi, Freek. Thanks for your information. I just downloaded the Instructions and the associated software. I hope it will works, Edgar, DJ3PU, Munich Hello Edgar, do not forget to remove var/lib/YaST2/reconfig_system from your SD card, before using it in the RPi, in case you work headless via ssh. I lost a number of hours to find out that not removing that file was the problem. Before using the SD in the RPi, I also reconfigure the partitions on the SD card using the Partition Manager of KDE. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Using image 13.2 headless
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+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Using image 13.2 headless
Op zaterdag 22 november 2014 18:59:47 schreef Andreas Färber: Hi, I made a mistake in copying the image to the SD card, so I booted an old image. Sorry about that. However after that, I copied the image in the right way and and found that the SD card now contains a GPT formatted image with a FAT partition, a small ext3 /boot partition and the ext4 system / partition. After starting gparted it advised to move the backup GPT table to the end of the device, which I did. With gparted I enlarged the system partition, added a swap partition and after that removed the empty file /var/lib/YaST2/reconfig_system . However after booting the system headless, the network did not appear. I documented this on the wiki. Please help me to get it running. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Using Raspberry Pi image 13.2 headless
Op zondag 23 november 2014 19:30:24 schreef Alexander Graf: You have a few options: 1) Attach a monitor using HDMI and finish yast2 firstboot or 2) Remove the file /var/lib/YaST2/reconfig_system from the target rootfs 3) Attach a serial cable to the uart GPIOs and kill the firstboot process I think in your case, option 2 is the easiest. I'm not really sure how to properly deal with this in our image creation. Some users have a serial cable / monitor attached and want to set the root password on first boot, others don't. How can we accomodate both? Thanks Alex, option 2 did the trick. Now I can log in using root and the published password. Will change it immediately, although it is only connected locally. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] How to resize 13.2 Raspberry Pi image
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+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Problem with freshclam and clamd and ntp
I am trying to set up a mail server on my RPi and need freshclam and clamd. A problem seems to be that they start before ntp has properly set the date and time. I tried adding in the files /usr/lib/systemd/system/freshclam.service and /usr/lib/systemd/system/clamd.service that they should run after finishing the ntpd.service and also tried ntp-wait.service but that did not work. When asking for the systemctl status for these services I still see log entries with Jan 01 as date. Only the last log line has the than current date. Any suggestions? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] How to resize 13.2 Raspberry Pi image
Op woensdag 26 november 2014 11:58:11 schreef Alexander Graf: On 26.11.14 11:49, Freek de Kruijf wrote: Op woensdag 26 november 2014 10:06:41 schreef Alexander Graf: The trick with the RPi image really is to synchronize GPT and MBR into a working hybrid GPT setup, just like on Apple Macs. You can also use the gptsync tool if you like. I have no idea what you are talking about above. Should I do anything different? You need to make sure that the hybrid GPT stays hybrid. An easy tool to do this with is gptsync: http://sourceforge.net/p/refind/code/ci/master/tree/gptsync/ IIRC gdisk also has a command to create the hybrid MBR entries from GPT. For information on what a hybrid GPT is, check out this web page: http://www.rodsbooks.com/gdisk/hybrid.html The reason we're using a hybrid GPT is that this was the easiest way to tell kiwi that we need another FAT partition that is not /boot. Alex Excuse my ignorance. I am always thinking in cookbook procedures and only when strictly needed I get into the technology. So what you are suggesting is: 1. burn the image on the SD 2. remove the reconfig file 3. run gptsync on the SD 4. use the SD on the RPi and it should work as a headless system? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] How to resize 13.2 Raspberry Pi image
Op woensdag 26 november 2014 12:22:28 schreef Alexander Graf: Excuse my ignorance. I am always thinking in cookbook procedures and only when strictly needed I get into the technology. So what you are suggesting is: 1. burn the image on the SD 2. remove the reconfig file 3. run gptsync on the SD 4. use the SD on the RPi and it should work as a headless system? If you only want it headless, you need to do 1. burn the image on the SD 2. remove the reconfig file 3. use the SD on the RPi (boot at least once!) If you also want to change the partition layout, you need to 4. change the partition layout 5. run gptsync on the SD Your above procedure does not work for a headless system. The first boot of the burned SD, whether one removed the reconfig file or not, will repartition the SD. So no need to do that afterward, unless one really wants to have a different partition layout. I don't. So no need for gptsync in my case. When one did not remove the reconfig file the resulting RPi system does not work headless, but at least one has a repartitioned SD. So after that, one can remove the reconfig file and boot the SD again, after which headless works. This works for me. When one removed the reconfig file before the first boot of the SD card the system does not work headless. I have no clue how to fix that. Maybe removing the reconfig file and repartitioning of the SD card to your liking using gparted and after that using gptsync, booting that SD for the first time may give you a headless working system. I tried that without gptsync and that did not work. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Problem with freshclam and clamd and ntp
Op woensdag 26 november 2014 12:08:53 schreef Freek de Kruijf: I am trying to set up a mail server on my RPi and need freshclam and clamd. A problem seems to be that they start before ntp has properly set the date and time. I tried adding in the files /usr/lib/systemd/system/freshclam.service and /usr/lib/systemd/system/clamd.service that they should run after finishing the ntpd.service and also tried ntp-wait.service but that did not work. When asking for the systemctl status for these services I still see log entries with Jan 01 as date. Only the last log line has the than current date. Enabling the debug log in clamd I found that clamd takes a very long time to start. This triggers the timeout in systemd, which allows only 90s for a process to start. So I did put a line TimeoutStartSec=600s in the file /usr/lib/systemd/system/clamd.service which allows more time for clamd to finish properly. When looking at the log 270s should be enough. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Problem with freshclam and clamd and ntp
Op vrijdag 28 november 2014 12:35:05 schreef Freek de Kruijf: Op woensdag 26 november 2014 12:08:53 schreef Freek de Kruijf: I am trying to set up a mail server on my RPi and need freshclam and clamd. A problem seems to be that they start before ntp has properly set the date and time. I tried adding in the files /usr/lib/systemd/system/freshclam.service and /usr/lib/systemd/system/clamd.service that they should run after finishing the ntpd.service and also tried ntp-wait.service but that did not work. When asking for the systemctl status for these services I still see log entries with Jan 01 as date. Only the last log line has the than current date. Enabling the debug log in clamd I found that clamd takes a very long time to start. This triggers the timeout in systemd, which allows only 90s for a process to start. So I did put a line TimeoutStartSec=600s in the file /usr/lib/systemd/system/clamd.service which allows more time for clamd to finish properly. When looking at the log 270s should be enough. At first I had the idea the problem came from the fact that freshclam and clamd showed dates in its log at moments ntp did not set the time properly. So still Jan 01, 1970 was shown. But this appears not to be a problem at all. So only the long time it takes for clamd to load is the problem. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Kernel-default for 13.2
Op vrijdag 5 december 2014 13:10:02 schreef Oscar C: Hi, Does anyone know where can I get the kernel of the 13.2 version? I though I would it find in here http://download.opensuse.org/repositories/openSUSE:/13.2/ports but the repository is not published. :( It is in http://download.opensuse.org/ports/armv6hl/distribution/13.2/repo/oss/ -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] New version clamav for Raspberry Pi
openSUSE 13.2 has an updated version for clamav. I don't see that version yet in the repositories for the Raspberry Pi. Is there anything I can do to fix that? Should this new version end up the oss repository or in update? -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] New version clamav for Raspberry Pi
Op maandag 8 december 2014 13:01:07 schreef Andreas Schwab: Alexander Graf ag...@suse.de writes: On 05.12.14 23:34, Freek de Kruijf wrote: openSUSE 13.2 has an updated version for clamav. I don't see that version yet in the repositories for the Raspberry Pi. Is there anything I can do to fix that? Should this new version end up the oss repository or in update? I would hope it's part of the normal update repository, but I don't really know how this works. Dirk, Adrian, do we need to set up anything further to get updates? openSUSE:13.2:Update isn't set up to build for armv6l. Andreas. How can I help to set this up. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] New version clamav for Raspberry Pi
Op dinsdag 9 december 2014 09:55:43 schreef Adrian Schröter: On Dienstag, 9. Dezember 2014, 00:50:24 wrote Freek de Kruijf: Op maandag 8 december 2014 13:01:07 schreef Andreas Schwab: Alexander Graf ag...@suse.de writes: On 05.12.14 23:34, Freek de Kruijf wrote: openSUSE 13.2 has an updated version for clamav. I don't see that version yet in the repositories for the Raspberry Pi. Is there anything I can do to fix that? Should this new version end up the oss repository or in update? I would hope it's part of the normal update repository, but I don't really know how this works. Dirk, Adrian, do we need to set up anything further to get updates? openSUSE:13.2:Update isn't set up to build for armv6l. Andreas. How can I help to set this up. The setup is easy, just adding the architecture to that project (needs to be done by maintenance team). But IIRC it was left out on purpose due to build power reasons and because armv6 was not in a good enough shape? I have it running in a test environment and so far it works OK. I want to use it for a small email, IMAP and web server to replace an old version of openSUSE on the Raspberry Pi, which is not safe anymore because there are no updates for that version. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Which repo for rasperry pi
Op maandag 15 december 2014 22:07:41 schreef Michael Ströder: Dirk Müller wrote: Hi Michael, http://download.opensuse.org/ports/armv6hl/factory/repo/oss/ Does this repo receive all the openSUSE updates? It is following Factory (aka nowadays called openSUSE Tumbleweed), so yes. but its a rolling release, so you will frequently get new versions of packages and the overall result might not be perfectly stable. its our development tree. It seems there are not updates in this repo. All the security-related fixes in the last time (e.g. openvpn) do not appear there. Ciao, Michael. See http://lists.opensuse.org/opensuse-arm/2014-12/msg00027.html for an answer. I don't know how to change that policy or have an alternative. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] WHICH IMAGE?
Op donderdag 18 december 2014 08:58:43 schreef Andreas Schwab: Edgar Dombrowski dj...@t-online.de writes: I am lost. I have looked into http://download.opensuse.org/ports/armv6hl/factory/repo/oss/ , but I can not find the Starter-Image which has to be copied on a SD-card. Did you mean http://download.opensuse.org/ports/armv6hl/factory/images/? Andreas. Also see https://en.opensuse.org/HCL:Raspberry_Pi -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] WHICH IMAGE?
Op donderdag 18 december 2014 08:58:43 schreef Andreas Schwab: Edgar Dombrowski dj...@t-online.de writes: I am lost. I have looked into http://download.opensuse.org/ports/armv6hl/factory/repo/oss/ , but I can not find the Starter-Image which has to be copied on a SD-card. Did you mean http://download.opensuse.org/ports/armv6hl/factory/images/? There is an E17 file with .raw.xz extension that I know how to put on an SD card, but how to handle the .tbz files? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] raw.xy-File
Op dinsdag 23 december 2014 08:13:07 schreef Edgar Dombrowski: OS for Raspbi-Pi Hi Raspi-Friends. Thanks first to Alex and others for telling me not to use the Build.tbz-Version but the xx.raw.xy-file in the same directory. But - sorry - how to extract the raw-file? See https://en.opensuse.org/HCL:Raspberry_Pi -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] raw.xy-File
Op vrijdag 26 december 2014 08:43:54 schreef Edgar Dombrowski: Am 23.12.2014 10:38, schrieb Freek de Kruijf: Op dinsdag 23 december 2014 08:13:07 schreef Edgar Dombrowski: OS for Raspbi-Pi Hi Raspi-Friends. Thanks first to Alex and others for telling me not to use the Build.tbz-Version but the xx.raw.xy-file in the same directory. But - sorry - how to extract the raw-file? See https://en.opensuse.org/HCL:Raspberry_Pi Hallo, Freek and the other Raspi-Friends. Thank you for the advice to look into the HCL.Page. (I had an old version). I finally succeeded to put the 13.1-Version on the SD-Stick. However I realized, that the LAN-Connection was not configured. So I used the yast-Network Devices to set up IP-Address, etc. I suggest that this should be included in the HCL-Page. It is a wiki, so you are free to include that in that page. I included the 13.2 stuff. Now I am going to include the other files. Thanks again and Happy and succesful New Year Same to you. Edgar, DJ3PU, Munich -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Why is packet e2fsprogs not present in Rasberry Pi image?
Hi all, Reading through the dmesg output on my Raspberry Pi I found an error message about missing programs fsck.ext3 and fsck.ext4, which I found in package e2fsprogs. This package is missing in the Raspberry Pi image. Shouldn't it be included? Bug report? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Why is packet e2fsprogs not present in Rasberry Pi image?
Op dinsdag 17 februari 2015 13:38:01 schreef Guillaume Gardet: Le 17/02/2015 11:36, Freek de Kruijf a écrit : Hi all, Reading through the dmesg output on my Raspberry Pi I found an error message about missing programs fsck.ext3 and fsck.ext4, which I found in package e2fsprogs. This package is missing in the Raspberry Pi image. Shouldn't it be included? Bug report? I think it is installed, but maybe not in Initrd. Could you check in the running system if fsck.ext3 is there, please? No it is not installed in the system. I installed it separately. Maybe it should be installed also in Initrd to do a file check before the OS is loaded. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Trying to build the newest version of clamav in OBS for Raspberry Pi 1 B
I tried to branch a clamav project in OBS in order to build the newest version of clamav for the Raspberry Pi 1 B. I tried to branch the 13.2 Update project, which already contains the newest clamav tar file, however I could not find how to build it for armv6l. I tried to branch the 13.2 project which shows a build for armv6l, however with an old tar file. However after that the armv6l architecture is no longer available. Any hints on how to proceeed? -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] How to use Rapsberry Pi Factory image headless
I tried to use openSUSE-Factory-ARM-JeOS-raspberrypi.armv6l-1.12.1- Build280.1.raw.xz from http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/upstream/images/ on a headless system. When using the 13.2 image I have to remove the file /var/lib/YaST2/reconfig_system and the system boots and I can log in via ssh. However the image above does not have such a file and I don't see the Ethernet interface coming up. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] openSUSE ARM img compatible with Raspberry Pi 2
Op zondag 29 maart 2015 19:45:29 schreef Dirk Müller: Hi Jimmy, Kindly let us have a quick to do to get all (or part) running on a Pi 2 :) There should be a working image fairly soon here: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp berryPi2/images/ I tried that image headless on my Raspberry Pi 2B, but it I do not get a working Ethernet connection. After the first boot and waiting about 15 minutes, there is nothing in /var/log/journal. Do I need to have a display and keyboard connected? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] openSUSE ARM img compatible with Raspberry Pi 2
Op maandag 30 maart 2015 23:27:19 schreef Dirk Müller: Hi Freek, Please try again (Build 285 or newer). I've not been able to test ethernet yet as I don't have ethernet while having time for hacking the device, but it boots up properly for me on serial console and I can login. I can see the 1GB RAM, 4 CPUs and eth0 which is in dhcp wait, so it doesn't look too bad. I used the one without a build number, which did not work. However the 285 did work and I could ssh into that system and configure things. Will continue tomorrow. Thanks!!! -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] openSUSE ARM img compatible with Raspberry Pi 2
Op dinsdag 31 maart 2015 01:09:48 schreef Freek de Kruijf: Op maandag 30 maart 2015 23:27:19 schreef Dirk Müller: Hi Freek, Please try again (Build 285 or newer). I've not been able to test ethernet yet as I don't have ethernet while having time for hacking the device, but it boots up properly for me on serial console and I can login. I can see the 1GB RAM, 4 CPUs and eth0 which is in dhcp wait, so it doesn't look too bad. I used the one without a build number, which did not work. However the 285 did work and I could ssh into that system and configure things. Will continue tomorrow. Thanks!!! I did a shutdown -P now and also shutdown -r now, which left an unbootable system behind. So I had to start all over again. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] openSUSE ARM img compatible with Raspberry Pi 2
Op dinsdag 31 maart 2015 21:12:53 schreef Dirk Müller: Hi Freek, Not only the shutdown left an unbootable system, also taking off the power and plugging the power in does not start the system again. yes, the kiwi firstboot somehow wrecks the firmware, so a 2nd boot fails. I currently think it is the resizing during initial boot, but it could be also something else.. Is there anyway I can help? Figure out what the bug is and how to fix it :-) I'm looking as astonished as you are. if you have any hint on what might go wrong, let me know. I studied on the BOOT disk the file boot.script and found in the value for bootargs the parameter disk=/dev/disk/by-id/mmc-0_0x1537043d . I have the feeling there should be -part? appended, where ? should be 2 or 3. Both root= and resume= have -part3. respectively -part4 appended. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] openSUSE ARM img compatible with Raspberry Pi 2
Op dinsdag 31 maart 2015 15:12:53 schreef Freek de Kruijf: Op dinsdag 31 maart 2015 01:09:48 schreef Freek de Kruijf: Op maandag 30 maart 2015 23:27:19 schreef Dirk Müller: Hi Freek, Please try again (Build 285 or newer). I've not been able to test ethernet yet as I don't have ethernet while having time for hacking the device, but it boots up properly for me on serial console and I can login. I can see the 1GB RAM, 4 CPUs and eth0 which is in dhcp wait, so it doesn't look too bad. I used the one without a build number, which did not work. However the 285 did work and I could ssh into that system and configure things. Will continue tomorrow. Thanks!!! I did a shutdown -P now and also shutdown -r now, which left an unbootable system behind. So I had to start all over again. Not only the shutdown left an unbootable system, also taking off the power and plugging the power in does not start the system again. I connected the device with a HDMI display. Starting with a freshly written SD card shows some messages on the screen and finally 4 logos of Raspberry Pi with underneath the message about the system and kernel and a login prompt on tty1. Unplugging the power and plugging it in again, does not produce any video output to the HDMI screen again. Is there anyway I can help? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] armv6l is missing on repository openSUSE-13.2-repo-update
When running zypper up on my Raspberry Pi I get a warning about an obsolete repository openSUSE-13.2-repo-update. Looking at http://download.opensuse.org/ports/update/13.2/ I do not see anything about armv6l I wonder why? -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Wi-Fi connections on Raspberry Pi 1 B
Hi all, I have a strange problem with Wi-Fi connections to two somewhat different Access Points. Both use the same configuration in YaST network, apart from SSID and IP address. Still the connection does succeed with one AP, but to the other AP it always fails. Using iwlist wlan0 scan the only obvious difference is that one reports to use CCMP, the one which succeeds, and the other uses TKIP, which does not succeed. In the information I found on the Internet I see that the configuration for wpa_supplicant may contain information about the support/use of these protocols. However the file /etc/wpa_supplicant/wpa_supplicant.conf does not contain this information, but the process wpa_supplicant has been started with the -u option, which enables a DBus control interface. So I assume that this kind of information will be supplied by wicked. However I can't find if TKIP is supported in openSUSE 13.2 for the the Raspberry Pi. Any information? -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Error message after installation of kernel-firmware
Op zondag 22 februari 2015 18:15:59 schreef Andreas Färber: Hi, Am 22.02.2015 um 18:05 schrieb Freek de Kruijf: I got the following error message after the update of firmware-kernel in openSUSE 13.2 for Raspberry Pi. Warning: kernel-firmware-20141122git-5.1.noarch.rpm %posttrans script failed (returned 1) Bug report? More context is needed. Probably it said a few lines up that it didn't find any kernel? That would be related to get_kernel_version: http://bugzilla.opensuse.org/show_bug.cgi?id=908454 No. The firmware is apparently not related to the kernel. The total output of zypper up after the first installation of the image in the SD is: # zypper up Gegevens van installatiebron laden... Lezen van geïnstalleerde pakketten... De volgende 2 pakketten zijn gesuggereerd, maar zullen niet worden geïnstalleerd: gio-branding-openSUSE yast2-firstboot De volgende 6 pakketten zullen worden opgewaardeerd: gio-branding-openSUSE kernel-firmware netcfg raspberrypi-userland systemd- presets-branding-openSUSE yast2-services-manager 6 op te waarderen pakketten. Totale downloadgrootte: 23,4 MiB. Reeds in de cache: 0 B Na de operatie zal 590,5 KiB worden vrijgemaakt. Doorgaan? [j/n/? alle opties tonen] (j): pakket raspberrypi-userland-2015.02.13-2.1.armv6hl wordt opgehaald (1/6), 552,3 KiB ( 2,7 MiB uitgepakt) Ophalen: raspberrypi-userland-2015.02.13-2.1.armv6hl.rpm .[klaar (404,1 KiB/s)] pakket gio-branding-openSUSE-13.2-5.1.noarch wordt opgehaald (2/6), 16,9 KiB ( 7,8 KiB uitgepakt) Ophalen: gio-branding-openSUSE-13.2-5.1.noarch.rpm .[klaar] pakket kernel-firmware-20141122git-5.1.noarch wordt opgehaald (3/6), 22,6 MiB ( 70,3 MiB uitgepakt) Ophalen: kernel-firmware-20141122git-5.1.noarch.rpm ..[klaar (472,4 KiB/s)] pakket netcfg-11.5-24.5.1.noarch wordt opgehaald (4/6), 231,3 KiB ( 1,2 MiB uitgepakt) Ophalen: netcfg-11.5-24.5.1.noarch.rpm .[klaar] pakket systemd-presets-branding-openSUSE-0.3.0-12.4.1.noarch wordt opgehaald (5/6), 6,1 KiB ( 613 B uitgepakt) Ophalen: systemd-presets-branding-openSUSE-0.3.0-12.4.1.noarch.rpm .[klaar] pakket yast2-services-manager-3.1.34.1-4.1.noarch wordt opgehaald (6/6), 33,6 KiB ( 80,7 KiB uitgepakt) Ophalen: yast2-services-manager-3.1.34.1-4.1.noarch.rpm [klaar] Controleren op conflicten tussen bestanden: [klaar] (1/6) Installeert: raspberrypi-userland-2015.02.13-2.1 .[klaar] (2/6) Installeert: gio-branding-openSUSE-13.2-5.1 ..[klaar] Aanvullende rpm-uitvoer: No schema files found: doing nothing. (3/6) Installeert: kernel-firmware-20141122git-5.1 .[klaar] (4/6) Installeert: netcfg-11.5-24.5.1 ..[klaar] (5/6) Installeert: systemd-presets-branding-openSUSE-0.3.0-12.4.1 ..[klaar] (6/6) Installeert: yast2-services-manager-3.1.34.1-4.1 .[klaar] Output of kernel-firmware-20141122git-5.1.noarch.rpm %posttrans script: No kernel found in /boot or bad modules dir in /lib/modules Waarschuwing: kernel-firmware-20141122git-5.1.noarch.rpm %posttrans script failed (returned 1) linux:~ # -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Wi-Fi connections on Raspberry Pi 1 B
Op donderdag 26 februari 2015 10:44:17 schreef Andreas Färber: Am 26.02.2015 um 10:12 schrieb Freek de Kruijf: Op woensdag 25 februari 2015 23:33:31 schreef Andreas Färber: Am 25.02.2015 um 22:11 schrieb Freek de Kruijf: I have a strange problem with Wi-Fi connections to two somewhat different Access Points. Both use the same configuration in YaST network, apart from SSID and IP address. Still the connection does succeed with one AP, but to the other AP it always fails. In my experience the most frequent cause of inexplicable AP connection problems is a misconfigured RTC. If you're using Ethernet too, make sure NTP is configured. What do you mean by RTC? Real time clock, i.e. `date`. And NTP means Network Tine Protocol? Yes. Can be configured through the yast time(zone) settings. Andreas I have a test set up with the RPi connected via the UTP port and two different Wi-Fi USB dongles in the two USB ports of the RPi. The clock is synchronized using NTP via the wired connection. So there is nothing wrong with the RTC and NTP. The two Wi-Fi interfaces are configured the same way apart from the SSID and IP address. I exchanged the SSIDs of these interfaces and both connect to one AP and not to the other AP. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Some problems with Tumbleweed on Raspberry Pi B 1
Op vrijdag 1 mei 2015 13:01:46 schreef Dirk Müller: Hello Dirk, This kernel is now published. There is still one zypp related dependency issue, which I just fixed (hopefully syncs out within the next 24 h or so). A short moment after receiving your message I found no issues anymore on updating all of Tumbleweed ARM Raspberry Pi. It runs 4.0.0-1. I now have an up-to-date system running. Hopefully it will also proof stable with my Bluetooth USB dongle, which gives a lot of trouble. When things go wrong, the whole system halts and only power down/up will make it run again. There is no error message in the logs. It was stable with openSUSE 13.1, but I lost that image, so I have to work with the newest software. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Some problems with Tumbleweed on Raspberry Pi B 1
I am using openSUSE-Factory-ARM-JeOS-raspberrypi.armv6l-1.12.1- Build266.3.raw.xz, which works OK. I tried updating the software to the newest versions available in the repository and noticed: 1. zypper can't be updated because the proper version of libzypp is not available. In openSUSE Build I see building of libzypp for Factory disabled for all ARM architectures. Is there a problem with building this library? 2. Updating kernel-default to 3.19.3-1.1 gives an unbootable system. Any solution? I noticed some error messages when dracut is executed: /usr/lib/dracut/dracut-functions.sh: line 1585: host_modules: bad array subscript -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Problem updating Tumbleweed on Raspberry Pi 1B
I tried to update a Tumbleweed system on a Raspberry Pi 1B system using zypper up. During downloading the kernel-default rpm the system crashes and restarts. I was able to update zypper and curl to the latest versions. However retrieving kernel-default-4.0.1-1.1.armv6hl.rpm makes the system crash. I was able to download the rpm using curl. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Updating RPi 2B image to kernel 4.0.1 leaves non-bootable system
I had a running image on my RPi 2B and saw kernel 4.0.1 being available. Using zypper I updated the kernel, but after that the system was no longer bootable. The newest image still has a 3.19 kernel. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] yast error when reading network device configuration
Op zondag 17 mei 2015 15:14:17 schreef Frank Kunz: Hi, when testing the image: https://build.opensuse.org/package/binaries/home:frank_kunz:branches:openSUS E:Factory:ARM/JeOS-a13olinuxino?repository=factory I got: Internal error. Please report a bug report with logs. Details: undefined method `ReadHardware' for #Yast::LanItemsClass:0xf044b8 Caller: /usr/share/YaST2/modules/LanItems.rb:988:in `ReadHw' when I try to change the network settings in yast. Is that a new issue? Any ideas? Br, Frank See https://bugzilla.opensuse.org/show_bug.cgi?id=930957 -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Fwd: raspberry PI 2
Op zaterdag 16 mei 2015 18:42:57 schreef Sean Fabian: Evening All I require your assistance in the following two fields Where can I find the hal package for armv7(Raspberry PI 2)? and do I need to rebuild it for armv7? AFAIK the hal package has been replaced by udev. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Problem updating Tumbleweed on Raspberry Pi 1B
Op woensdag 13 mei 2015 22:42:27 schreef Freek de Kruijf: I tried to update a Tumbleweed system on a Raspberry Pi 1B system using zypper up. During downloading the kernel-default rpm the system crashes and restarts. I was able to update zypper and curl to the latest versions. However retrieving kernel-default-4.0.1-1.1.armv6hl.rpm makes the system crash. I was able to download the rpm using curl. However rpm -iv kernel-default-4.0.1-1.1.armv6hl.rpm provided the error: error: unpacking of archive failed on file /lib/modules/4.0.1-1- default/kernel/net/sunrpc/auth_gss/rpcsec_gss_krb5.ko;5553b6b6: cpio: read error: kernel-default-4.0.1-1.1.armv6hl: install failed -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] openSUSE ARM img compatible with Raspberry Pi 2
Op vrijdag 3 april 2015 00:34:06 schreef u: The fix is to restore that on first boot, so when you log in the first time, run this: echo r h 1 2 3 n c y 82 n 83 n w y | \ /usr/sbin/gdisk /dev/mmcblk0 I'm trying to add that as a workaround to the image. Ideally there would be some feature in kiwi to do that :-/ Indeed this works. I now have a bootable RPi2 system. Thanks very much!!! -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Updating RPi 2B image to kernel 4.0.1 leaves non-bootable system
Op dinsdag 19 mei 2015 16:51:03 schreef Andreas Färber: Am 18.05.2015 um 00:51 schrieb Freek de Kruijf: I had a running image on my RPi 2B and saw kernel 4.0.1 being available. Using zypper I updated the kernel, but after that the system was no longer bootable. The newest image still has a 3.19 kernel. Are you maybe accidentally installing a kernel-default from Factory (which I think does not yet support RPi2) over the kernel-rpi2 or so from the Contrib project? Yes, this 4.0.1 kernel is in the armv7l Factory repository, the repository that is defined in the image, next to the Contrib repository. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] RaspberryPi and openSuse 13.2
Op woensdag 20 mei 2015 04:00:21 schreef Thomas Aichinger: Furthermore serial not set properly means that raspi does not have a stable MAC. Every time you boot it has another MAC. After first boot I look at the current MAC and add LLADDR='current_MAC' in /etc/sysconfig/network/ifcfg-eth0 On the next boot the MAC will have that value. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Updating RPi 2B image to kernel 4.0.1 leaves non-bootable system
Op dinsdag 19 mei 2015 18:07:19 schreef Alexander Graf: On 05/19/2015 06:02 PM, Freek de Kruijf wrote: So maybe this kernel should not be available in the repo? It's part of the official Factory:ARM repository, because all upstream (non-contrib) boards use it. So this kernel conflicts with kernel-rpi2 or vice versa. Is it possible to keep Contrib synchronized with the same kernel version in Factory:ARM? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Updating RPi 2B image to kernel 4.0.1 leaves non-bootable system
Op dinsdag 19 mei 2015 17:02:24 schreef Alexander Graf: On 05/19/2015 04:58 PM, Freek de Kruijf wrote: Op dinsdag 19 mei 2015 16:51:03 schreef Andreas Färber: Am 18.05.2015 um 00:51 schrieb Freek de Kruijf: I had a running image on my RPi 2B and saw kernel 4.0.1 being available. Using zypper I updated the kernel, but after that the system was no longer bootable. The newest image still has a 3.19 kernel. Are you maybe accidentally installing a kernel-default from Factory (which I think does not yet support RPi2) over the kernel-rpi2 or so from the Contrib project? Yes, this 4.0.1 kernel is in the armv7l Factory repository, the repository that is defined in the image, next to the Contrib repository. Ah, that explains it. The raspberry pi 2 requires a special downstream kernel today still, hence the name kernel-rpi2. The kernel you installed is probably kernel-default which is an upstream kernel and doesn't support the RPi2 properly yet FWIW. So maybe this kernel should not be available in the repo? -- fr.gr. member openSUSE Freek de Kruijf P.S. No need to send it to my address directly, I am on the mailing list. -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Raspberry Pi 1 and GPT partition really booting?
Op maandag 8 juni 2015 20:29:02 schreef Alexander Graf: Am 08.06.2015 um 17:56 schrieb Guillaume Gardet guillaume.gar...@free.fr: Hi, I tested (hybrid) GPT partitionned images for Raspberry Pi and it does not boot at all (even the GPU firmware which is the 1st stage). Is there someone here who booted such an image? If so, which Pi version and which openSUSE image version? Otherwise, I would like to revert to FAT16 boot partition. It has a FAT boot (gpu, uboot) partition. And it did work for me on RPi1 and RPi2. I have already put both of them in persistent home automation use though, so I can't verify today's image ;) Alex Guillaume I have both Tumbleweed for RPi1B and RPi2B working on both of my RPi's. But I used older images to start and have, in the meantime, updated these systems using zypper up. However yast is not usable because libstorage-ruby is for Ruby 2.1 where yast needs 2.2. I succeeded in generating this library for both systems. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Difference between Release supported platforms and Community supported platforms
Op dinsdag 9 juni 2015 09:43:29 schreef Alexander Graf: On 08.06.15 18:31, Guillaume Gardet wrote: I merged https://en.opensuse.org/Portal:ARM/GetARMed and https://en.opensuse.org/openSUSE:Supported_ARM_boards (1st part). Could you please review/edit this page: https://en.opensuse.org/Portal:ARM/GetARMed Wow, I'm sure that was a lot of work. A minor nit: I think the BeagleBoard xM special page link should just either get merged with the HCL or linked to from the HCL, no need to specially mention it on the portal Thanks a lot for digging through this! I followed the links to RPi1 and 2 and cleaned up the page on RPI2. The page on RPI1 is quite confusing, so is searching the download.opensuse.org for images of RP1. I have the feeling that some reorganization of the repositories for RPi1 is needed. In my view they should have the same basic structure as for the x86 architecture. On the highest level arm-distribution and arm-update, next to arm-tumbleweed. Below, at least for RPi's iso should image. I am quite willing to update the RPi1 page on the wiki, but I need some information on the policy for this device. Which versions are supported? Only Tumbleweed or also 13.2 and ...? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Problem using YaST because rebuild of ruby packet is blocked by boost library
Op zaterdag 6 juni 2015 14:17:29 schreef Dirk Müller: Hi Freek, The new package has been built already, just publishing is stuck again. I'll see what I can do. I've tried a workaround, but it seems there is something broken server side, so we need an admin to look into it and fix it. This can only be done next week, sorry about that. :-/ I tried to find the project on build.opensuse.org that builds libstorage-ruby, but could not find it. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] RPi1 crashes during downloading phase of zypper up
I do a zypper up --download-only on my Tumbleweed RPi1 system which is connected using Wi-Fi to the network. Rather regularly I get messages about a wrong checksum. But after discarding such a package and a retry it is downloaded OK. However somewhat later during a download the system crashes and restarts. I did not experience such a problem in earlier updates using an Ethernet connection. How can I investigate such a problem? Retrying the whole process gives the crash at another point. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] I am lost
Op woensdag 10 juni 2015 11:02:44 schreef Edgar Dombrowski: Hi, Freek. Thanlk you for your advice.. I have found the repos indicated. For the RPi2 repos, there are three different versions JeOs, LXQT and XFCE. What are the differences? The LXQT and XFCE have the respective desktop systems installed, and are supposed to work using a display and keyboard connected I suppose. JeOS is a more basic system. I use it headless, without display and keyboard, as a server. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Signing key for repository 'Factory-Contrib-RPi' expires
I get the following message when trying to update my RPi1 system: Retrieving repository 'Factory-Contrib-RPi' metadata -[\] The gpg key signing file 'repomd.xml' will expire in 9 days. Repository: Factory-Contrib-RPi Key Name: devel:ARM OBS Project devel:a...@build.opensuse.org Key Fingerprint: 1D6571D6 77CD36CE F6B93856 16C5D54F 3F546F34 Key Created: Wed Apr 10 13:47:53 2013 Key Expires: Fri Jun 19 13:47:53 2015 (expires in 9 days) Rpm Name: gpg-pubkey-3f546f34-51655169 -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Problem using YaST because rebuild of ruby packet is blocked by boost library
I reported a bug in http://bugzilla.suse.com/show_bug.cgi?id=933274 about an Internal error in YaST. This problem is caused by a non-up-to-date ruby module on armv7l which is blocked by a boost library. Is it possible to look into the problem with the boost library in armv7l? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Experiences with Build325.3 for RPi1 and Build315.2 for RPi2
Both have the same problem starting slow. The fix for this is on its way. It takes a bit more than 10 minutes before the RPi1 system really starts the start up process. I could follow this process because I had these systems connected via HDMI to my TV monitor. The set up of RPi1 also takes about 10 minutes. O.a. a new initrd is being build. The start of the RPi2 is repeating itself and never finishes. After the slow start RPi1 end up in a workable state in a headless situation. I can connect via ssh to the system via the Ethernet connection. I tried a zypper up, and as to be expected: Nothing to do. On the RPi1 I updated libstorage6 libstorage-ruby to my own earlier generated versions. After this yast network works. I changed nothing in the network configuration. However I add an LLADDR=MAC address to /etc/sysconfig/network/ifcfg-eth0 right after the xzcat process on my desktop. So I know what IP-address the RPi systems get from my DHCP server. After closing down the RPi1 system using shutdown -r now, the RPi1 system does not boot anymore. There is no output via HDMI anymore. Not even the small messages I saw when booting the freshly made SD card. So I assume the BOOT partition is not properly build. I assume the UEFI partition is not touched in the set up process. The RPi2 system does not work. On my TV monitor the first 3 characters on a line are not displayed. I searched for a solution and found that setting overscan_left and overscan_right in config.txt on the UEFI partition could solve this problem. I tried 16 and 24. It does not seem to have any effect, except when setting these values to 20, in which case the I get a distorted display. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Experience with Build315.3 for RPi2
Op dinsdag 23 juni 2015 18:40:50 schreef Freek de Kruijf: Both have the same problem starting slow. This was about Build325.3 for RPi1 and Build315.2 for RPi2. Today I found Build315.3 for RPi2. The slow start has gone. The RPi2 system does not work. On my TV screen I see that the kernel is loaded, after which the screen is wiped clean. I see the lights of the Ethernet port on and blinking, however after a while, a few minutes, the system starts again, showing messages about the boot process and finally that the kernel is loaded. Build308.3 for RPi2 is the last working system. It lacks however showing console messages about the start process after the kernel is loaded. It shows messages about the boot process, but after the messages about loading the kernel the screen becomes blankand after a while it show the system message and the log in prompt. Is it possible to display the start up of the system, like with the RPi1, where the whole process about repartitioning the SD card is shown and other start up messages? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Newest images for RPi1 and RPi2 are not usable headless
I tried Tumbleweed Build325.1 for RPi1 and Build314.1 for RPi2 in a headless situation, but both do do not end with an active Ethernet connection. Is this to be expected? u-boot problem? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Factory RPi2 image - no console on HDMI after first reboot
Op vrijdag 12 juni 2015 19:18:31 schreef Philip Vossler: surrvive reboots and is accessible via ssh but after the first reboot there is no HDMI console. It does take a while to start but looks like its functional - I will need HDMI, so I'm going to try and find out why it's not working. What do you mean by HDMI console. Did you connect a USB keyboard and a HDMI monitor? Are the characters you type on the keyboard displayed in the monitor? You can't expect more than that with JeOS. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] R:R:I am Lost: No Boot
Op woensdag 17 juni 2015 14:32:27 schreef Guillaume Gardet: Do you have any explanation why the boot process had stopped? I think it is not stopped but it is slowly loading the initrd which is much bigger than the kernel which was slowly loaded (75.2 KiB/s) just before. So, just wait some minutes. I would say 10 minutes or maybe more I am afraid. :( I do not know why load is so slow on u-boot for the Raspberry Pi. Guillaume I had the same problem and needed to wait 10 minutes before I could have access via ssh. In my view the problem is the partitioning, which is done initially. So it may take longer if you have a larger SD card. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Experiences with Build326.2 for RPi1 and Build316.1 for RPi2
The Build for RPi1 works, but has the same problem as with the previous build when trying to use YaST with ncurses. The Build for RPi2 does not work. The same problem. After booting the openSUSE image the system boots from the start after some time and repeats this. So apparently the openSUSE image crashes. Inspecting the micro-SD card after this process shows no changes in the partitioning of this card. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Experiences with Build325.4 for RPi1
Earlier a second boot of a system generated with this build for Raspberry Pi 1B did not work. Now I have a system that works and can be booted again. However trying to start a module with yast (ncurses), I tried network, software repositories and software all end in the following error message: /sbin/yast: line 426: 19947 Segmentation fault $ybindir/y2base $module $@ $SELECTED_GUI $Y2_GEOMETRY $Y2UI_ARGS However 19947 in the above message differs with the type of module called and with the locale used. The repository still does not contain the ruby 2.2 modules for libstorage. I build these modules, which went OK. I noticed gcc5 was used. I will continue with this build to configure the applications I use. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Experiences with Build325.4 for RPi1
Op woensdag 1 juli 2015 13:53:47 schreef Alexander Graf:
On 30.06.15 17:43, Freek de Kruijf wrote:
Op dinsdag 30 juni 2015 11:49:09 schreef u:
On 06/30/15 11:24, Freek de Kruijf wrote:
Op dinsdag 30 juni 2015 10:57:31 schreef Alexander Graf:
On 06/30/15 10:55, Freek de Kruijf wrote:
Earlier a second boot of a system generated with this build for
Raspberry
Pi 1B did not work. Now I have a system that works and can be booted
again.
However trying to start a module with yast (ncurses), I tried network,
software repositories and software all end in the following error
message:
/sbin/yast: line 426: 19947 Segmentation fault $ybindir/y2base
$module $@ $SELECTED_GUI $Y2_GEOMETRY $Y2UI_ARGS
However 19947 in the above message differs with the type of module
called
and with the locale used.
The repository still does not contain the ruby 2.2 modules for
libstorage.
I build these modules, which went OK. I noticed gcc5 was used.
I will continue with this build to configure the applications I use.
Do you think you could gdb the y2base binary to figure out where
exactly
it segfaults?
Alex, I have no experience with gdb. I know it is used to debug and one
can
set breakpoints and step through the code, but that's all I know.
No worries, there's always a first time :). In this case, all we need is
to attach to the program and then do 'bt' when we see the segfault.
I tried to run yast in one console and did gdb -p process-id in
another
after installing yast2-core-debugger. However it likes to have
yast2-core-
debuginfo which is not available. After giving a c in gdb and selecting
software in the ncurses console, gdb continues with the following
output:
(gdb) c
Continuing.
Detaching after fork from child process 20159.
[Thread 0xb601f450 (LWP 20077) exited]
[Thread 0xb631b450 (LWP 20076) exited]
[Inferior 1 (process 20075) exited normally]
This means that the process was doing just fine, no segfault. So maybe a
different PID was the one broken? Which PID did you attach to? According
to the log, y2base is the application that faults.
If you can't find it, try to attach strace -f to the yast binary to
figure out which binary gets executed. The strace should also at least
print out which PID segfaulted.
Attached you will find strace.2. I can't find anything about a segfault.
Search for this line:
[pid 25753] --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR,
si_addr=0x10} ---
That's where the segfault occurs :).
I entered the following bug in bugzilla:
https://bugzilla.opensuse.org/show_bug.cgi?id=936788
The problem is apparently in the package yast2-pkg-bindings.
--
fr.gr.
member openSUSE
Freek de Kruijf
--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Experiences with Build317.3 for RPi2
Still the same problem as before. The system boots the openSUSE kernel, which apparently crashes. After which it boots again. The partitioning of the SD card does not seem to changed. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Build326.4 for RPi1 does not produce a proper ext4 partition
I copied this image to my SD card and tried to mount the ext4 partition. Using parted showed that it it was not a proper ext4 partition. Did not know how to make it right without destroying the content. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Strange problem with Wi-Fi connection
Op woensdag 12 augustus 2015 11:48:23 schreef Michael Ströder: Freek de Kruijf wrote: Op woensdag 12 augustus 2015 10:02:12 schreef u: I had a similar issue which was solved in the meantime after update package dtb-bcm2835-4.1.3-47.1 reached this system. Now kernel update to 4.1.4 is in the pipe but no update to package dtb-bcm2835-4.1.4... I have dtb-bcm2835-4.1.3-47.1 Maybe I can build that package 4.1.4 After testing recent updates I can confirm that this combination seems to work even with my eth0-wlan0-bridged setup: kernel-default-4.1.4-1.1.armv6hl dtb-bcm2835-4.1.3-47.1.armv6hl I have now updated to kernel-4.1.4, but this problem is still present. I can't find the source package dtb-bcm2835 in the Build service and don't know where to elsewhere. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Tests with latest Raspberry Pi images
I tested a number of images from both Contrib:/RaspberryPi:/upstream as Contrib:/RaspberryPi/. From the last one I never got a working image, from upstream the last one that works is Build330.10 from Aug 6. All images for Raspberry Pi 2B are usable. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Experiences with Build325.4 for RPi1
Op dinsdag 30 juni 2015 11:49:09 schreef u: On 06/30/15 11:24, Freek de Kruijf wrote: Op dinsdag 30 juni 2015 10:57:31 schreef Alexander Graf: On 06/30/15 10:55, Freek de Kruijf wrote: Earlier a second boot of a system generated with this build for Raspberry Pi 1B did not work. Now I have a system that works and can be booted again. However trying to start a module with yast (ncurses), I tried network, software repositories and software all end in the following error message: /sbin/yast: line 426: 19947 Segmentation fault $ybindir/y2base $module $@ $SELECTED_GUI $Y2_GEOMETRY $Y2UI_ARGS However 19947 in the above message differs with the type of module called and with the locale used. The repository still does not contain the ruby 2.2 modules for libstorage. I build these modules, which went OK. I noticed gcc5 was used. I will continue with this build to configure the applications I use. Do you think you could gdb the y2base binary to figure out where exactly it segfaults? Alex, I have no experience with gdb. I know it is used to debug and one can set breakpoints and step through the code, but that's all I know. No worries, there's always a first time :). In this case, all we need is to attach to the program and then do 'bt' when we see the segfault. I tried to run yast in one console and did gdb -p process-id in another after installing yast2-core-debugger. However it likes to have yast2-core- debuginfo which is not available. After giving a c in gdb and selecting software in the ncurses console, gdb continues with the following output: (gdb) c Continuing. Detaching after fork from child process 20159. [Thread 0xb601f450 (LWP 20077) exited] [Thread 0xb631b450 (LWP 20076) exited] [Inferior 1 (process 20075) exited normally] This means that the process was doing just fine, no segfault. So maybe a different PID was the one broken? Which PID did you attach to? According to the log, y2base is the application that faults. If you can't find it, try to attach strace -f to the yast binary to figure out which binary gets executed. The strace should also at least print out which PID segfaulted. I started yast in one console and selected Software Management in the right sub window without pressing Return. In a second console I gave the command: ps aux to find the pid of the y2base process after that I gave the command: strace -ff -p 25721 strace.1 2strace.2 I pressed Return in the first console and after reappearing of the main ncurses window of yast I entered AltQ, which also ended strace. I found only strace.2 having output. I will send that in a separate private message. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Experiences with Build325.4 for RPi1
Op dinsdag 30 juni 2015 11:49:09 schreef Alexander Graf: On 06/30/15 11:24, Freek de Kruijf wrote: Op dinsdag 30 juni 2015 10:57:31 schreef Alexander Graf: On 06/30/15 10:55, Freek de Kruijf wrote: Earlier a second boot of a system generated with this build for Raspberry Pi 1B did not work. Now I have a system that works and can be booted again. However trying to start a module with yast (ncurses), I tried network, software repositories and software all end in the following error message: /sbin/yast: line 426: 19947 Segmentation fault $ybindir/y2base $module $@ $SELECTED_GUI $Y2_GEOMETRY $Y2UI_ARGS However 19947 in the above message differs with the type of module called and with the locale used. The repository still does not contain the ruby 2.2 modules for libstorage. I build these modules, which went OK. I noticed gcc5 was used. I will continue with this build to configure the applications I use. Do you think you could gdb the y2base binary to figure out where exactly it segfaults? Alex, I have no experience with gdb. I know it is used to debug and one can set breakpoints and step through the code, but that's all I know. No worries, there's always a first time :). In this case, all we need is to attach to the program and then do 'bt' when we see the segfault. I tried to run yast in one console and did gdb -p process-id in another after installing yast2-core-debugger. However it likes to have yast2-core- debuginfo which is not available. After giving a c in gdb and selecting software in the ncurses console, gdb continues with the following output: (gdb) c Continuing. Detaching after fork from child process 20159. [Thread 0xb601f450 (LWP 20077) exited] [Thread 0xb631b450 (LWP 20076) exited] [Inferior 1 (process 20075) exited normally] This means that the process was doing just fine, no segfault. So maybe a different PID was the one broken? Which PID did you attach to? According to the log, y2base is the application that faults. If you can't find it, try to attach strace -f to the yast binary to figure out which binary gets executed. The strace should also at least print out which PID segfaulted. I did attach to the y2base process. I think the segfault is in the forked process shown above as 20159, which is not present when I start gdb. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Cubietruck 13.2 regression
Op woensdag 5 augustus 2015 21:35:35 schreef Andreas Färber: Am 17.07.2015 um 11:50 schrieb Andreas Färber: Upgrading to Factory (kernel-lpae-4.0.5-3), ssh login works again, but still no serial output. There are systemd messages and a graphical login on HDMI now, but no kernel messages either. You may find /dev/tty10 or /dev/xconsole in /etc/rsyslog.conf Changing /dev/tty10 in /dev/tty1 may get your kernel messages logged on your screen. It did for me on a Raspberry Pi 2B. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Some tests with RPi 1 images
I tested Build319.9 in /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi/ This image shows an error message about not finding the boot device and reboots again after 120 sec., etc. So there is something wrong in the partition boot. None of the images in this repository works. I tested Build330.7 in upstream /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/ which still contains the bug in yast in bug report https://bugzilla.opensuse.org/show_bug.cgi?id=936788 When booting I see an error message about an error in a udev rule, but the system still boots. This system appears usable. I tested Build330.8 in upstream /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/ which boots, but shows an error about /home and finally reboots again after a wait time of 120 sec., so does not work. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Re: Raspberry Pi 1 and 2 images from of Aug 6
Op donderdag 13 augustus 2015 03:21:31 schreef Stefan Bruens:
On Thursday 13 August 2015 01:55:08 Stefan Bruens wrote:
On my system, acorrding to:
for p in `rpm -q --whatrequires libstdc++.so.6`; \
do rpm -q $p --queryformat '[%{FILEMODES:perms} %{FILENAMES}\n]' | \
awk '/^-.*\.so\./ {print $2 }' | \
xargs -r -n1 sh -c '\
nm -DC --defined-only $0 | \
egrep -q -m1 std::string|std::list \
echo $0' \
;done
/usr/lib/yui/libyui-ncurses-pkg.so.6.0.0
/usr/lib/libzypp.so.1503.1.0
use the old C++03 strings/list
For both, no newer packages are available, as the build failed:
https://build.opensuse.org/project/monitor?utf8=%E2%9C%93commit=Filter%3Af
ailed=1repo_standard=1arch_armv6l=1project=openSUSE%3AFactory%3AARMdefau
lts=0
Kind regards,
Stefan
Earlier I managed to build on the RPi some newer versions of two packages by
downloading the source and spec file and using rpmbuild to build the the rpm.
However I, apparently, am unable to do that with libzypp. I build however
libyui-ncurses-pkg, but got the same errors as in the Build service.
Currently I am trying to build binutils and has to disable Patch25 in the spec
file. Now it is building. Will see what becomes of it.
--
fr.gr.
member openSUSE
Freek de Kruijf
--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Strange problem with Wi-Fi connection
Op woensdag 12 augustus 2015 10:02:12 schreef u: Freek de Kruijf wrote: I have a RPi 1B with a Wi-Fi USB interface using the latest image for this system. Which image exactly? Build331.1 I had a similar issue which was solved in the meantime after update package dtb-bcm2835-4.1.3-47.1 reached this system. Now kernel update to 4.1.4 is in the pipe but no update to package dtb-bcm2835-4.1.4... I have dtb-bcm2835-4.1.3-47.1 Maybe I can build that package 4.1.4 Ciao, Michael. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Re: Raspberry Pi 1 and 2 images from of Aug 6
Op dinsdag 11 augustus 2015 23:06:20 schreef Matwey V. Kornilov: 11.08.2015 22:02, Freek de Kruijf пишет: This does not give me a clue why yast lan crashes on the RPi1 and is OK on the RPI2. AFAIK, RPi1 is armv6 and RPi2 is armv7. So, there could be a number of reasons to crash on one architecture and work on other. Yes, but the version indicates the version of the source. The binaries are build with different compilers. So the only reason I can think of is a compiler error or something related to that. So that's what I am looking for. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Some tests with RPi 1 images
Op donderdag 6 augustus 2015 14:43:35 schreef Freek de Kruijf: I tested Build319.9 in /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi/ This image shows an error message about not finding the boot device and reboots again after 120 sec., etc. So there is something wrong in the partition boot. None of the images in this repository works. Also the newest Build319.11 does not work. I tested Build330.7 in upstream /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/ which still contains the bug in yast in bug report https://bugzilla.opensuse.org/show_bug.cgi?id=936788 When booting I see an error message about an error in a udev rule, but the system still boots. This system appears usable. I tested Build330.8 in upstream /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/ which boots, but shows an error about /home and finally reboots again after a wait time of 120 sec., so does not work. But the newest Build330.10 works again. The bug is not solved. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] What repository is recommended for images for Raspberry Pi's?
Op vrijdag 17 juli 2015 20:18:22 schreef Freek de Kruijf: I am a bit confused about which repositories should be used for Raspberry Pi Tumbleweed images. Currently I have: for RPi1: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp berryPi:/upstream/images/ None of the JeOS images work. The last one tested is Build318.4. http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Ras pberryPi/images/ Last JeOS images work. Last tested is Build329.4. Kernel in image is 4.1.1 in Tumbleweed repository 4.0.5. for RPi2: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp berryPi2:/Staging/images/ All JeOS images work. Last tested is Build320.4. http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Ras pberryPi2/images/ All JeOS images work. Last tested is Build319.4. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Re: [opensuse-factory] Suse and Raspberry Pi Build
Op woensdag 28 oktober 2015 11:31:53 schreef gm1...@aol.com: > This is GREAT! As soon as my HDMI cable arrives I will install it onto a Pi > 2 B+ and just have some fun. I had seen there were some ARM buids but was > not sure what to use. Do any problems go here or is there a specific ARM > forum? There is a special ARM mailing list: opensuse-arm@opensuse.org Subscribe via: opensuse-arm+subscr...@opensuse.org -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Raspberry Pi 2
Op woensdag 14 oktober 2015 16:02:43 schreef Peter Czanik: > Hi, > > I'd like to demo Raspberry Pi 2 with openSUSE at a conference. I tried > the XFCE image at > http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp > berryPi2/images/openSUSE-Tumbleweed-ARM-XFCE-raspberrypi2.armv7l.raw.xz > which I found at the RPi2 HCL page at > https://en.opensuse.org/HCL:Raspberry_Pi2 > I was prepared for a slow boot, but after 20 minutes, the screen is > still blank with the cursor blinking in the upper left corner. > Any idea, what could have gone wrong? Any other image I should try? You could try the JeOS. Previous versions did work, and install afterward XFCE. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] openSUSE on Raspberry B+/2 usable as a server?
Op donderdag 15 oktober 2015 22:35:05 schreef Johannes Kastl: > Dear opensuse-on-Raspi-Folks, > > I read the last couple of months of the mails on the opensuse-arm > mailinglist, but I am not sure: > > Is openSUSE 13.x usable on a Raspberry B+ or 2? If I find one of the > few images that are installing correctly, can I keep it up to date > and secure without issues? I have a Raspberry Pi 1B running now for a few years with openSUSE 13.2 as a server; e-mail, imap and apache and a small other application. Obviously a 1B+ or a 2B are also usable as servers. It very much depends on the load it has to cope with. However the image I started with, 13.2, is no longer available and there are no updates for this version. AFAIK currently the only working image with openSUSE Tumbleweed is for a 2B. The available openSUSE Tumbleweed images for 1B are not working, but I still have a working image which I can make available after private communication. The repositories for this Tumbleweed version gets regular updates and I have no problems when updating the systems (1B and 2B). > (I am not talking about Tumbleweed, I'd prefer something less time > consuming. And I do not mean I would take lots of manual > intervention, its just lots and lots of updates and the occasional > configuration change) There is not really a need to do updates unless it is a security update that affects the security of your system. So after installation and configuration you can leave the system as be. No need to keep up with Tumbleweed. > Ideally this would mean 13.1 or 13.2 being usable, or maybe Leap is > going to be usable. Anyone tried Leap yet? I am not aware that there is a Leap version for the Raspberry Pi. Not even considered. > Thanks in advance for your input! > > Johannes -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Tests of latest images for RPi1
Build336.2 from repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/upstream/ boots, the SD is partitioned and the resulting system boots. However the Ethernet connection does not become active. The lights stay off. I could not find a method to list the journal on the SD partition on a system where the SD is mounted. Build325.2 from repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi/ does the low level boot, but after that, like before, can't find the boot image on the 3rd partition. Upgrading a system build earlier with a working image works OK. Finally the problem using the command "yast lan" is solved. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] How to upgrade kernel on Raspberry Pi
Op vrijdag 4 september 2015 22:33:02 schreef Olav Reinert: > The fix was to copy the files from /boot to the boot partition that are > already present in both locations. Now my Pi boots to the new kernel, > and removing the old one didn't cause any issues. Not idea if this is > the canonical procedure, but it works. > > Tumbleweed on a Pi - smashing! I don't think you are fully using Tumbleweed. Tumbleweed uses kernel-4.1.6. What repositories are you using? I have: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi/standard/ and http://download.opensuse.org/ports/armv6hl/tumbleweed/repo/oss/ The kernel I am using comes from the last repo, the one you use comes from the first repo. Installing a new kernel lately 4.1.6 from 4.1.4 went without the trick you needed. Most likely the post processing in the rpm for the kernel you use does not include the copy to /boot. The /boot on my RPi is on the second partition (ext3). -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Tests of latest images for RPi1
Op dinsdag 1 september 2015 22:31:43 schreef Freek de Kruijf: > Build336.2 from > repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/upstream/ boots, the > SD is partitioned and the resulting system boots. However the Ethernet > connection does not become active. The lights stay off. I could not find a > method to list the journal on the SD partition on a system where the SD is > mounted. I also tried Build336.3, but that one produces a corrupt ext4 partition like earlier images. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] How to upgrade kernel on Raspberry Pi
Op zondag 6 september 2015 12:58:55 schreef Olav Reinert: > I tried to upgrade to the new layout by installing a fresh 13.2 image: > > <http://download.opensuse.org/repositories/devel:/ARM:/13.2:/Contrib:/Raspbe > rryPi/images/openSUSE-13.2-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build36.9.raw. > xz> > > Unfortunately, that image won't boot properly. It gets as far as the > "Starting kernel ...", then it seems to hang. You probably should use the Tumbleweed image on: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/upstream/images/ The ones on http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi/images/ never worked. The newest image is Build338.1. I did not test this image. The latest I tested was Build336.3, but that one has a distorted 3rd partition (ext4). Running fsck on that partition after moving the image on the SD card shows errors. The latest which was usable was Build 330.10 from Aug 6. A zypper up brings it in line with the latest repositories. This is what I am using now. All the problems I had with YaST are fixed now. I am still struggling with a Bluetooth device and/or Wi-Fi. When I have a few % packet loss, because of the distance on the Wi-Fi connection, curl does not deliver me a proper file. Curl is used by zypper and zypper shows wrong check sums. curl does not report an error, but the check sum is wrong. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Tests of latest images for RPi1
Op dinsdag 1 september 2015 22:31:43 schreef Freek de Kruijf: > Build336.2 from > repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/upstream/ boots, the > SD is partitioned and the resulting system boots. However the Ethernet > connection does not become active. The lights stay off. I could not find a > method to list the journal on the SD partition on a system where the SD is > mounted. Finally found the method to analyze the journal on the SD card. I mount the SD card on my desktop and use the command "journalct --file //system.journal You can use other options to select specific information in the journal. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Raspberry Pi with OpenSuSe: I am lost
Op zondag 13 september 2015 09:15:39 schreef Edgar Dombrowski: > Hi, Raspberry Pi-Friends. > > I am lost. > Following the different advices in this forum, I have downoaded the > different xz-files as listend in the Repos for the OS13,2- > arm-v6i- and the arm-v7l-versions for installation into the Raspbi B+ > and 2B. > But it always failed when booting. > > What can I do? The Mikro-CD-cards are ok as success when loading varios > Debian-Squeeze. AFAIK the oS13.2 image for RPi2 does not exists. There is an image with armv7l in its name but that should be armv6l for RPi1. The existing image for RPi1 with Build32.1 works. You need to remove /var/lib/YaST2/reconfig_system on the SD card if you want to use the system headless. The problem with this version is that there is no update repository. A referral to such a location exists in the image, but does not exist. In my view this makes 13.2 unusable for any RPi. The only option AFAIK for openSUSE on RPi1 and RPi2 is Tumbleweed. Until now the image for RPi2, both the standard as the Staging version work. Because it is a rolling release the repository is regularly updated to the newest versions of the software. In contrary to the x86 and x86_64 versions this software is not tested in the QA system. So you need to be careful when updating the system The versions of the images for RPi1 are often in a bad state. The standard version does not boot the openSUSE system until now. The upstream version from the beginning of August Build330.10, works and you can update that version with the newest software from the repository, but the available image does not work. AFAIK, the working image is not available on download.opensuse.org. It is 188 MB. In private communication we can discuss how you can get a copy. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Tests of latest images for RPi1
Op donderdag 3 september 2015 13:34:06 schreef Freek de Kruijf: > Op dinsdag 1 september 2015 22:31:43 schreef Freek de Kruijf: > > Build336.2 from > > repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/upstream/ boots, > > the SD is partitioned and the resulting system boots. However the > > Ethernet connection does not become active. The lights stay off. I could > > not find a method to list the journal on the SD partition on a system > > where the SD is mounted. > > I also tried Build336.3, but that one produces a corrupt ext4 partition like > earlier images. Tried the latest Build339.4 from RasberryPi:/upstream. It produces a corrupt ext4 partition, but it runs, but no Ethernet connection. Tried the latest Build327.4 from RasberryPi. U-boot can't find a bootable system in /boot. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Tests of latest images for RPi1
Op vrijdag 11 september 2015 22:47:37 schreef Freek de Kruijf: > Op donderdag 3 september 2015 13:34:06 schreef Freek de Kruijf: > > Op dinsdag 1 september 2015 22:31:43 schreef Freek de Kruijf: > > > Build336.2 from > > > repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/upstream/ boots, > > > the SD is partitioned and the resulting system boots. However the > > > Ethernet connection does not become active. The lights stay off. I could > > > not find a method to list the journal on the SD partition on a system > > > where the SD is mounted. > > > > I also tried Build336.3, but that one produces a corrupt ext4 partition > > like earlier images. > > Tried the latest Build339.4 from RasberryPi:/upstream. It produces a corrupt > ext4 partition, but it runs, but no Ethernet connection. Tried Build340.3 same problem a corrupt ext4 partition. The latest working image is Build330.10 from August 6, 2015. > Tried the latest Build327.4 from RasberryPi. U-boot can't find a bootable > system in /boot. I filed a bug report for this problem. https://bugzilla.opensuse.org/show_bug.cgi?id=947675 -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] 13.2 ARM updates
Op zaterdag 19 september 2015 15:17:49 schreef Guillaume Gardet: > Dirk, > > Any progress on this? > > > Guillaume > > Le 13/09/2015 22:42, Miklos Vajna a écrit : > > Hi, > > > > Hmm, I still don't see any updates at > > <http://download.opensuse.org/ports/update/13.2/>. Is it just me? :-) AFAIK there will not be any update on 13.2 for armv6hl, only armv7hl. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] ARM and the Raspberry
Op maandag 7 december 2015 11:59:36 schreef Andy Norrie: > SD Image writer is supplied via the SD card owners to write a bootable > image to the SD card. It is the normal way to make a bootable SD card for > the Pi. On the older Pi (ARM6) Suse runs fine but neither that version or a > downloaded one works on the Pi 2. I have downloaded several images eg > > opensuse-13.1-arm-jeos-raspberrypi.arm7i-1.12.1-build38.15.raw > > > and I can read the first partition on the disk (fat) and it seems correct > but it does not boot. I dont see any errors on the SD card eg log file. I > was hoping someone else had this working as I am a bit stuck. > > Thanks, Andy Raspberry Pi 1 has an armv6 architecture, whereas Raspberry Pi 2 has an armv7 architecture, so it is not weird it does not work. You need an image for the Raspberry Pi 2, which you can find on http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi2/images/ or http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi2:/Staging/images/ I only worked with JeOS iages. AFAIK both work and are in fact openSUSE Tumbleweed systems. After installation you can keep current, if you wish, with Tumbleweed by using "zypper up" -- fr.gr. member openSUSE Freek de Kruijf -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] No new JeOS images for Raspberry Pi 1, also meant for Raspberry Pi Zero?
Since September there are new images for other environments than JeOS, but not anymore for this environment. These last images did not work, I don't know why. Is that the reason there are no new images? Are these images also meant for Raspberry Pi Zero? -- fr.gr. member openSUSE Freek de Kruijf -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Images for Raspberry Pi
Op maandag 21 december 2015 04:27:40 schreef Andreas Färber: > Am 17.12.2015 um 13:04 schrieb Freek de Kruijf: > > I tested the latest released Tumbleweed image for the Raspberry Pi 2B, > > Build354.2 which shows a black screen and does not boot at all, same as > > the > > latest one from Staging, which is from a few days back. > > > > Currently there are no working Tumbleweed images for any of the Raspberry > > Pi systems. Is there anything I can do, apart from testing the latest > > images? > Yes. > > "Black screen" and "does not boot" do not help getting it fixed. > Buy yourself a cheap UART adapter (less than 4 EUR for 3.3 V!) and post > concrete error output if something is not working. A good report is half > the fix! Dear Andreas, Maybe I can find such a device, but I have no idea how to connect it to my system to get some characters on a screen. I restrict myself to getting all the images for the Raspberry Pi 1B and 2B from http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/ Should I use another source for the images. After putting an image on the (micro-)SD card I test the image with a connected HDMI screen and an Ethernet cable, so I can watch how the system boots. When I report a black screen, this means I do not seen ANY information on the HDMI screen. It does not boot means I do not see the Ethernet connection coming up. Furthermore I can change files on the SD card in case this is relatively simple. Putting a new kernel on it is beyond my capabilities. I do realize I am part of the team, but I have limited capabilities. Reporting about what works and not is about all I can do. After that I hope I am quite willing to regularly follow a cookbook type of procedure and report about the results. I once did something quite simple in OBS. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Images for Raspberry Pi
Op vrijdag 18 december 2015 10:39:46 schreef Freek de Kruijf: > Op donderdag 17 december 2015 09:15:12 schreef u: > > I have had the same experience have had to stop using opensuse on my pi's. > > It is very disappointing from what i can tell there is almost zero > > interest > > from the overall opensuse-arm community for supporting raspberry pi > > hardware properly. > > > > On Dec 17, 2015 7:04 AM, "Freek de Kruijf" <fr...@opensuse.org> wrote: > > > I tested the latest released Tumbleweed image for the Raspberry Pi 2B, > > > Build354.2 which shows a black screen and does not boot at all, same as > > > the > > > latest one from Staging, which is from a few days back. > > > > > > Currently there are no working Tumbleweed images for any of the > > > Raspberry > > > Pi > > > systems. Is there anything I can do, apart from testing the latest > > > images? > > The situation is not that negative. I have Tumbleweed systems running on > both RPi1 and RPi2 started from a working image, some month ago, on which I > am still able to update these to the latest version of Tumbleweed from the > repository. So it seems that the only problem is with the boot system, but > generating a new initrd still works. The latest update to kernel 4.3.0 for RPi1 ruined the system. It does not start anymore. The error message on the screen said: File not found dtb.bcm2835-rpi-b.dtb -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Images for Raspberry Pi
I tested the latest released Tumbleweed image for the Raspberry Pi 2B, Build354.2 which shows a black screen and does not boot at all, same as the latest one from Staging, which is from a few days back. Currently there are no working Tumbleweed images for any of the Raspberry Pi systems. Is there anything I can do, apart from testing the latest images? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Raspberry Pi model 2 - ARM7
Op zondag 29 november 2015 10:23:57 schreef gm1...@aol.com: > I have downloaded several images and written them to an SD card with SD > Image Writer but can not get anything to boot. Am I using the correct > software to write the SD card and what image should I be using. > > Thanks, Andy Hello Andy, you need to be more specific and give more details. Did you get your image, a .raw.xz file, from http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi2/images/ or http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi2:/Staging/images/ ? I use, as root, the command: xzcat | dd bs=4M of=/dev/sdX ; sync where sdX points to the device with the micro SD card, to write the image to that card. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Use of cpan on Raspberry Pi 1 B armv6l has unsatisfied requirements
In order to use the cpan utility in a Raspberry Pi 1B system with Tumbleweed I needed to install the packages make and gcc. This means that the package perl, which provides /usr/bin/cpan, needs to have requirements for these packages. I entered a bug report about this https://bugzilla.opensuse.org/show_bug.cgi?id=984594 -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Use of cpan on Raspberry Pi 1 B armv6l has unsatisfied requirements
In order to use the cpan utility in a Raspberry Pi 1B system with Tumbleweed I needed to install the packages make and gcc. This means that the package perl, which provides /usr/bin/cpan, needs to have requirements for these packages. I entered a bug report about this https://bugzilla.opensuse.org/show_bug.cgi?id=984594 -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] How to make a version of the packet python-RPi.GPIO for the Raspberry Pi 1B available?
Using the source of RPi.GPIO-0.6.2 I managed to build a version which is usable on a Raspberry Pi 1B with Tumbleweed (armv6l). The problem with Tumbleweed is that it provides a device /sys/class/gpio/gpiochip298, where the software of version 0.6.2 expects /sys/class/gpio/gpiochip0 I made it more general, so it supports all values for 0 and 298 between 0 and 999. I have a system running with this software, which seems stable. However repeatedly stopping and starting the program using this software fails. Only a reboot cures the problem. So it is limited usable. At least one can stick with openSUSE. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Trying to use GPIO using /sys/class/gpio/
Op woensdag 25 mei 2016 10:16:14 schreef Freek de Kruijf: > I tried to use "echo '23' > /sys/class/gpio/export" as root on a Raspberry > Pi 1B, but I get an error message. Tried other values as 23 also, but I > continue to get the error message. > > Any hints? I found the answer in https://www.kernel.org/doc/Documentation/gpio/sysfs.txt The documentation of the Rasberry Pi does not mention anything about the device /sys/class/gpio/gpiochipX, apparently in other systems X is 0, however openSUSE shows /sys/class/gpio/gpiochip298. base and ngpio show respectively 298 and 54. So I should use channel 298+23, which after use does not give an error message and shows that /sys/class/gpio321 has been created. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
