Tumbleweed for Raspberry Pi2 hardware detect with i2c-tools not wok. Do samples with Real Time Clock DS3231. Add in etc/modulse-load.d - i2c-dev, rtc-ds1307, snd-bcm2835. Driver i2c-bcm2835 not
add to load - error modprobe: FATAL: Module i2c-bcm2835 not found in directory /lib/modules/3.18.14-5-rpi2 . After command sudo i2cdetect -y 1 , result is - Error: Could not open file /dev/i2c-1' or /dev/i2c/1’: No such file or directory .
All work with Raspbian, but i wont to work with openSUSE. After week рeading on the Internet, i think the problem is python-dbus (i2c-tools-python in fedora).
With this problem, Raspberry not work with GPIO interface (sensors and etc).
If anyone knows how to deal with the problem, I will buy you beer
ad:
With this problem, Raspberry not work with GPIO interface (sensors and etc).
If anyone knows how to deal with the problem, I will buy you beer :)[/QUOTE]
I wish I could help you but . . .
I have a raspberry pi 3 and it is great.
I love (open)SuSE since way back.
(open)SuSE is the best distro so I installed the arm-edition on pi 3 but it messes up
screen resolution. I tried and searched everything but I could not find a solution for it
ignoring /boot/config.txt after startx
On x86 pc’s you could xconfig etc. but not in arm-distro, at least not to my knowledge.
Most people say; stick with raspberry debian but, hey, opensuse is still the best, alas not for pi 3
I wish more people would see the BIG advantages of cheap, open computers.
opensuse could make a BIG stand if it would support those little, cheap but o so lovely processors
and their possibilities.
Not everyone on this planet has the USD 400- upward money to spend on hardware.
And: pi 3 is BRITISH !!
Mind you, I love raspberry debian but, hey, it is not opensuse (and yast).
After two months, bcm2835 modules working fine, but i2c-tools again not working. Missing packages python-smbus is big problem. Have ready packages, Is it so hard to be ported to Tumbleweed arm?
