[opensuse-arm] RaspberryPi and openSuse 13.2
Hi, I run into a problem with my RasPi Model B+ V1.2 with openSuse 13.2. I type: raspi:~ # cat /proc/cpuinfo processor : 0 model name : ARMv6-compatible processor rev 7 (v6l) Features : swp half thumb fastmult vfp edsp java tls CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xb76 CPU revision : 7 Hardware : BCM2835 Revision : 0000 Serial : 0000000000000000 From serveral other sources I heard that Hardware should be BCM2708, Revision 0010 and there should be a valid serial number. The same hardware with raspbian says: Hardware : BCM2708 Revision : 0010 Serial : 00000000c2c2clcfbb The problem is that many libs are looking into this information to determine what type of raspi they are running on. Furthermore serial not set properly means that raspi does not have a stable MAC. Every time you boot it has another MAC. Any suggestions how I can fix this? -- Viele Grüße Thomas Aichinger ---------------------------- http://www.datamagic.at ---------------------------- Data Magic Datenservice GmbH Schönbrunner Straße 140 1120 Wien -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
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+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Wed, 2015-05-20 at 04:00 +0200, Thomas Aichinger wrote:
Hi,
I run into a problem with my RasPi Model B+ V1.2 with openSuse 13.2.
I have noticed a similar issue: http://lists.opensuse.org/opensuse-arm/2014-12/msg00039.html My workaround was to update the bootargs in boot.script to include: bcm2708.boardrev=0x10 bcm2708.serial=... smsc95xx.macaddr=... with the serial and macaddr values taken from booting into raspbian. and to regenerate boot.scr using mkimage (can't remember the exact flags). I think there is an issue with uboot not passing the kernel command line since opensuse does some sort of chain boot where /dev/mmcblk0p1 just sets up the real boot from /dev/mmcblk0p2. I've also been using the raspberry pi upstream kernel instead of the opensuse kernel since there have been some issues (but I suppose they have been fixed by now). Not the best solution, but it works for me... -- Evan McClain <aeroevan@gmail.com>
Yes, this is exactly the same issue I have. I found following temp solution: MAC can be set in /etc/sysconfig/network/ifcfg-eth0 LLADDR='ab:cd:00:01:02:03' 1.) cat /proc/cpuinfo > /etc/cpuinfo 2.) edit /etc/cpuinfo and set proper values 3.) mount --bind /etc/cpuinfo /proc/cpuinfo 4.) to make that permanent after reboot save the mount command in a executeable file 5.) create a service file for systemd [Unit] Description=Set proper cpuinfo [Service] Type=oneshot ExecStart=/usr/lib/systemd/scripts/setcpuinfo.sh [Install] WantedBy=getty.target This is dirty workaround, but it works for me at the moment. I run into another problem today. There is a tool vcgencmd that lists a lot of hardware details, but in opensuse I get only raspi:/ # vcgencmd VCHI initialization failed I already searched for this error but could not find anything. -- Viele Grüße Thomas Aichinger Am 21.05.2015 um 04:22 schrieb Evan McClain:
On Wed, 2015-05-20 at 04:00 +0200, Thomas Aichinger wrote:
Hi,
I run into a problem with my RasPi Model B+ V1.2 with openSuse 13.2. I have noticed a similar issue: http://lists.opensuse.org/opensuse-arm/2014-12/msg00039.html
My workaround was to update the bootargs in boot.script to include: bcm2708.boardrev=0x10 bcm2708.serial=... smsc95xx.macaddr=... with the serial and macaddr values taken from booting into raspbian.
and to regenerate boot.scr using mkimage (can't remember the exact flags).
I think there is an issue with uboot not passing the kernel command line since opensuse does some sort of chain boot where /dev/mmcblk0p1 just sets up the real boot from /dev/mmcblk0p2.
I've also been using the raspberry pi upstream kernel instead of the opensuse kernel since there have been some issues (but I suppose they have been fixed by now).
Not the best solution, but it works for me...
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (3)
-
Evan McClain -
Freek de Kruijf -
Thomas Aichinger