-
Notifications
You must be signed in to change notification settings - Fork 5.2k
rpisense-fb not allocating /sys/graphics/fb*
device
#1139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Sounds like everything should work. You shouldn't even need the dtoverlay parameter, since that should be loaded automatically from the EEPROM. I suspect you don't have a dt-enabled kernel. I don't see anything in that ebuild that would pass it through mkknlimg and i2cdetect doesn't show 'UU' on 0x46, suggesting that the device isn't instantiated. |
So any suggestions what I can do to get it "instantiated"? I would guess that i2cdetect should show Actually the ebuild only installs the sources into I'm also not familiar what you mean by "dt-enabled" kernel. If you can point me to the config entry I will gladly provide that information. Thanks! I also wonder why I'm not able to get any message via p.s. to be clear, I install the kernel in this way:
|
Method 4 here https://www.kernel.org/doc/Documentation/i2c/instantiating-devices Yup, mkknlimg is required for device tree to work properly. If you're using that defconfig all the necessary kernel options are there, there's just a bit that mkknlimg tags on due to... reasons. Instead of But I'd point out that bcmrpi_defconfig should be kernel.img (pi 1 kernel), not kernel7.img (pi 2 kernel). The correct defconfig for kernel7.img would bcm2709_defconfig. |
Thanks! I will try that. I actually saw that error in the ebuild for |
Just read your link and remembered that command from my ds1307 rtc and actually
But I still have no |
Try rpisense-core instead of rpisense-fb |
It seems to give the same results. I do get a new "sys/i2c" directory. I hope I may be able to add some debug statements to the c code, so I can see why it does not load the device now I see something in dmesg. ls -la /sys/class/i2c-adapter/i2c-1/1-0046/
total 0
-r--r--r-- 1 root root 4096 Sep 25 03:33 modalias
-r--r--r-- 1 root root 4096 Sep 25 03:33 name
lrwxrwxrwx 1 root root 0 Sep 25 03:33 subsystem -> ../../../../../bus/i2c
-rw-r--r-- 1 root root 4096 Sep 25 03:32 uevent |
Success! Got it working today. Seems I really was only missing
|
Hi folks
I'm trying to use my sense hat with a raspberry pi 2 on a custom gentoo linux installation, but I cannot get the led matrix to work. What I got from reading the python sourcecode, it should allocate a framebuffer device for it, but I fail to get that device "allocated".
I'm using raspberrypi-sources-4.1.9999.ebuild (currently at d2b2388) with this config:
The module seems to load correctly
I still only have one framebuffer device (I'd expect
RPI-Sense FB
):The sense hat is showing the "rainbow" after the raspberry pi is powered up and I can see the sensors and the "rpisense" interface (I guess it's the one at
0x46
):My findings for future reference:
I also don't get any messages in
dmesg
? I even tried to hack an earlydev_info
message intorpisense_fb_probe
ofdrivers/video/fbdev/rpisense-fb.c
, but I still don't see anything indmesg
!?Any pointers what I might be doing wrong? I first tried to connect the sense hat only with the necessary pins (since I need to attach additional i2c breakouts), but I have it now directly connected, so that should not be the problem (unless I did some damage I'm not aware of in the experimental process).
I also tried to play with
dtoverlay
in/boot/config.txt
and I am confused what this option actually does? I know the difference between builtin modules, initrd and "runtime" modules. Do I always need to adddtoverlay=rpi-sense
or only if it is built into the kernel? I have putrpi-sense-overlay.dtb
into/boot
and/boot/overlays
and the line in/boot/config.txt
, but still got no framebuffer device? Do I have to compile them myself (I can get avr-gcc built but will probably take a day or two to compile). Or should it be ok if I downloaded it from the firmware repository?Hope I got the right Bugtracker for this!
Any help is welcome! Thank you!
The text was updated successfully, but these errors were encountered: