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: [email protected]
To contact the owner, e-mail: [email protected]
