shunte88 wrote: > hi @jursi, sorry your having problems > > gomonitor takes care of prepping your environment including loading the > IIC infrastructure if it not already active > > you can do the same with: > > Code: -------------------- > > sudo modprobe i2c-bcm2835 > sudo modprobe i2c-dev -------------------- > > > > then check for your device with i2cdetect, e.g. for my setup > > Code: -------------------- > > tc@koala:/mnt/mmcblk0p2/tce$ i2cdetect -y 1 > 0 1 2 3 4 5 6 7 8 9 a b c d e f > 00: 03 -- -- -- -- -- -- -- -- -- -- -- -- > 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- -- -- > 40: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- > 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 70: -- -- -- -- -- -- -- -- -------------------- > > > > you may see more than one device if you have a DAC or other IIC device > attached to your pi > > your device should show up at 0x3c > > ensure all your connections are good, pins are clean and solder joints > are good - check your jumper wires too > > the device looks to be a standard ssd1306 so you should need to > specify any OLED parameters > if it doesn't work out of the box its usually just a matter of trying > the various IIC drivers until you get a match, -o 3, 5, or 6 would be > the ones to try - 6 is the default > > you can update and install to the latest with the following set of > commands, they'll do everything except change the squeeze parameters, > that you would still have to do manually > > Code: -------------------- > > > tce-load -i i2c-tools.tcz > pcp bu > cd /mnt/mmcblk0p2/tce > cp gomonitor safe.gomonitor > wget "https://github.com/shunte88/LMSMonitor/blob/master/bin/lmsmonitorpcp.tgz?raw=true"; -O lmsmonitorpcp.tgz && \ > tar -xzvf lmsmonitorpcp.tgz && \ > chmod +xX gomonitor > pcp bu -------------------- > > > note it backs up gomonitor before update in case you rolled your own > > fingers crossed you resolve, given those daylight hours hopefully you > won't have to burn the midnight oil > > note that I'm checking out a self selecting solution which if its fit > for purpose will make its way into the solution > > also coming today a fix for the "half-flip" issue > hoping to get re-connection in play too for dropped player/server > scenarios > > I refactored code and improved the memory footprint some. > To celebrate I added another "egg",and fully refactored the entire > implementation for those visualizations so they can be conditionally > compiled in a future release
Thank you for you asnwer. One question: How can I easily kill lmsmonitor process so I cant try another driver. eg. how to stop sudo /mnt/mmcblk0p2/tce/lmsmonitor --name "Retropi" -c -rbkd --verbose -V I tried to kill the pid but it didn't work. Another question. Do I need to run both LMSmonitor and Gomonitor to light up the display? I don't really undestand the difference. Thanks! test ------------------------------------------------------------------------ Jursi's Profile: http://forums.slimdevices.com/member.php?userid=69100 View this thread: http://forums.slimdevices.com/showthread.php?t=111790 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
