[beagleboard] who are user UID 110 and group GID 116?
I have found in the `/home/debian` folder and in the `/etc` tree a couple of files that have a UID of 110 and GID of 116. Notably `/home/debian/.npmrc` `/etc/passwd` doesn't contain a user with that UID and `/etc/group` doesn't have the GID listed. Who are they supposed to be? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] who are user UID 110 and group GID 116?
I must agree with you that `npm` is not the ideal packagemanager. ;-) There also seems to be `pip` installed for Python packages... Is there a remote possibility that those packages would ever be offered via `apt-get` ? Problem is that even as the root user some things (I forget which) didn't work off the bat because of those broken ownerships. I ended up chowning them to root:root (for files in `/etc/`) and debian:debian for files in `/home/debian`. On Monday, 7 December 2015 21:26:58 UTC+1, RobertCNelson wrote: > > > > On Mon, Dec 7, 2015 at 2:14 PM, Maurice H. > wrote: > >> I have found in the `/home/debian` folder and in the `/etc` tree a couple >> of files that have a UID of 110 and GID of 116. >> Notably `/home/debian/.npmrc` >> >> `/etc/passwd` doesn't contain a user with that UID and `/etc/group` >> doesn't have the GID listed. >> >> Who are they supposed to be? >> > > as root user we install a few packages via "npm install xyz" > > > https://github.com/RobertCNelson/omap-image-builder/blob/master/target/chroot/beagleboard.org-wheezy.sh#L244 > > It's one of the worst package systems i've seen, doing random things to > all over the rootfs.. > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] who are user UID 110 and group GID 116?
Thanks! Much appreciated. On Monday, 7 December 2015 22:39:05 UTC+1, RobertCNelson wrote: > > > > On Mon, Dec 7, 2015 at 3:28 PM, Robert Nelson > wrote: > >> >> >> On Mon, Dec 7, 2015 at 3:13 PM, Robert Nelson > > wrote: >> >>> >>> >>> On Mon, Dec 7, 2015 at 2:47 PM, Maurice H. >> > wrote: >>> >>>> I must agree with you that `npm` is not the ideal packagemanager. ;-) >>>> There also seems to be `pip` installed for Python packages... >>>> >>>> Is there a remote possibility that those packages would ever be offered >>>> via `apt-get` ? >>>> >>> >>> i wish... cloud9 ide has to be installed via npm, then they broke some >>> of the npm packaging, so you have install some npm dependices on target, >>> before you can run the "standalone" package... >>> >>> >>> >>>> >>>> Problem is that even as the root user some things (I forget which) >>>> didn't work off the bat because of those broken ownerships. I ended up >>>> chowning them to root:root (for files in `/etc/`) and debian:debian for >>>> files in `/home/debian`. >>>> >>> >>> >>> debian@beaglebone:~$ sudo cat .npmrc >>> cache = /root/.npm >>> group = 0 >>> init-module = /root/.npm-init.js >>> tmp = /root/tmp >>> user = 0 >>> userconfig = /root/.npmrc >>> >>> root@beaglebone:~# pwd >>> /root >>> root@beaglebone:~# ls -lha ./ >>> total 28K >>> drwx-- 5 root root 4.0K Dec 6 21:32 . >>> drwxr-xr-x 21 root root 4.0K Jan 1 2000 .. >>> -rw-r--r-- 1 root root 570 Jan 31 2010 .bashrc >>> drwxr-xr-x 9 root root 4.0K Dec 6 21:23 .c9 >>> drwxr-xr-x 3 root root 4.0K Dec 6 21:23 .cache >>> drwxr-xr-x 3 root root 4.0K Dec 6 21:24 .node-gyp >>> -rw-r--r-- 1 root root 140 Nov 19 2007 .profile >>> >>> Well that's broken, so we can drop /home/debian/.npmrc >>> >>> >>> https://github.com/RobertCNelson/omap-image-builder/commit/5dfed9a2703c4013f9577b2e04f65e18568bd409 >>> >> >> >> and the rest are mine.. >> >> drwxr-xr-x 2 rootroot 4.0K Dec 6 21:04 bluetooth >> -rw-r--r-- 1 polkitd bluetooth 40 Dec 6 21:06 dogtag >> -rw-r--r-- 1 polkitd bluetooth 11 Dec 6 23:11 hostname >> -rw-r--r-- 1 polkitd bluetooth 213 Dec 6 23:11 hosts >> -rw-r--r-- 1 polkitd bluetooth 263 Dec 7 19:05 issue >> -rw-r--r-- 1 polkitd bluetooth 175 Dec 6 21:29 issue.net >> -rw-r--r-- 1 polkitd bluetooth 86 Dec 6 21:06 rcn-ee.conf >> >> those should all be root:root >> > > This should fix the rest, please let me know if you find more: > > > https://github.com/RobertCNelson/omap-image-builder/commit/586c447e85ffbac762ce4d2b0b3b33434eaf4adf > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] who are user UID 110 and group GID 116?
Yep those are the ones I seem to recall. Changed them to root:root. On Monday, 7 December 2015 22:29:31 UTC+1, RobertCNelson wrote: > > > > On Mon, Dec 7, 2015 at 3:13 PM, Robert Nelson > wrote: > >> >> >> On Mon, Dec 7, 2015 at 2:47 PM, Maurice H. > > wrote: >> >>> I must agree with you that `npm` is not the ideal packagemanager. ;-) >>> There also seems to be `pip` installed for Python packages... >>> >>> Is there a remote possibility that those packages would ever be offered >>> via `apt-get` ? >>> >> >> i wish... cloud9 ide has to be installed via npm, then they broke some >> of the npm packaging, so you have install some npm dependices on target, >> before you can run the "standalone" package... >> >> >> >>> >>> Problem is that even as the root user some things (I forget which) >>> didn't work off the bat because of those broken ownerships. I ended up >>> chowning them to root:root (for files in `/etc/`) and debian:debian for >>> files in `/home/debian`. >>> >> >> >> debian@beaglebone:~$ sudo cat .npmrc >> cache = /root/.npm >> group = 0 >> init-module = /root/.npm-init.js >> tmp = /root/tmp >> user = 0 >> userconfig = /root/.npmrc >> >> root@beaglebone:~# pwd >> /root >> root@beaglebone:~# ls -lha ./ >> total 28K >> drwx-- 5 root root 4.0K Dec 6 21:32 . >> drwxr-xr-x 21 root root 4.0K Jan 1 2000 .. >> -rw-r--r-- 1 root root 570 Jan 31 2010 .bashrc >> drwxr-xr-x 9 root root 4.0K Dec 6 21:23 .c9 >> drwxr-xr-x 3 root root 4.0K Dec 6 21:23 .cache >> drwxr-xr-x 3 root root 4.0K Dec 6 21:24 .node-gyp >> -rw-r--r-- 1 root root 140 Nov 19 2007 .profile >> >> Well that's broken, so we can drop /home/debian/.npmrc >> >> >> https://github.com/RobertCNelson/omap-image-builder/commit/5dfed9a2703c4013f9577b2e04f65e18568bd409 >> > > > and the rest are mine.. > > drwxr-xr-x 2 rootroot 4.0K Dec 6 21:04 bluetooth > -rw-r--r-- 1 polkitd bluetooth 40 Dec 6 21:06 dogtag > -rw-r--r-- 1 polkitd bluetooth 11 Dec 6 23:11 hostname > -rw-r--r-- 1 polkitd bluetooth 213 Dec 6 23:11 hosts > -rw-r--r-- 1 polkitd bluetooth 263 Dec 7 19:05 issue > -rw-r--r-- 1 polkitd bluetooth 175 Dec 6 21:29 issue.net > -rw-r--r-- 1 polkitd bluetooth 86 Dec 6 21:06 rcn-ee.conf > > those should all be root:root > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] sys/class/hwmon is empty
In the `jessie` image from beagleboard.org/latest_images the file /sys/class/hwmon/hwmon0/device/temp1_input doesn't exist anymore. When I try the `wheezy` image it *is* present. Bug? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Error: Cannot find module 'bonescript'
I have this simple script that I want to execute at boot time.
The script:
root@bbone:~# cat boneboot/ledsoff.js
var b=require('bonescript');
b.pinMode('USR0', 'out');
b.pinMode('USR1', 'out');
b.pinMode('USR2', 'out');
b.pinMode('USR3', 'out');
b.digitalWrite('USR0', 0);
b.digitalWrite('USR1', 0);
b.digitalWrite('USR2', 0);
b.digitalWrite('USR3', 0);
To run it at boot I've created a file in /etc/cron.d which looks like this:
root@bbone:~# cat /etc/cron.d/boneboot
# m h dom mon dow user command
@reboot rootsleep 120 && /usr/bin/nodejs /root/boneboot/ledsoff.js 2>&
1 | logger -p info -t ledsoff
Unfortunately, when I reboot the BBB the code is not executed succesfully
as shown by the log:
root@bbone:~# cat /var/log/syslog
Dec 18 21:54:49 bbone ledsoff:
Dec 18 21:54:49 bbone ledsoff: module.js:340
Dec 18 21:54:49 bbone ledsoff: throw err;
Dec 18 21:54:49 bbone ledsoff: ^
Dec 18 21:54:50 bbone ledsoff: Error: Cannot find module 'bonescript'
Dec 18 21:54:50 bbone ledsoff: at Function.Module._resolveFilename (
module.js:338:15)
Dec 18 21:54:50 bbone ledsoff: at Function.Module._load (module.js:280:
25)
Dec 18 21:54:50 bbone ledsoff: at Module.require (module.js:364:17)
Dec 18 21:54:50 bbone ledsoff: at require (module.js:380:17)
Dec 18 21:54:50 bbone ledsoff: at Object. (/root/boneboot/
ledsoff.js:1:69)
Dec 18 21:54:50 bbone ledsoff: at Module._compile (module.js:456:26)
Dec 18 21:54:50 bbone ledsoff: at Object.Module._extensions..js (module.
js:474:10)
Dec 18 21:54:50 bbone ledsoff: at Module.load (module.js:356:32)
Dec 18 21:54:50 bbone ledsoff: at Function.Module._load (module.js:312:
12)
Dec 18 21:54:50 bbone ledsoff: at Function.Module.runMain (module.js:497
:10)
However, when I logged in as root, the code executes normally.
Any suggestions on how to proceed?
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[beagleboard] /sys/class/hwmon not populated on Jessie
I tried this image: https://rcn-ee.com/rootfs/bb.org/testing/2015-12-13/lxqt-4gb/bone-debian-8.2-lxqt-4gb-armhf-2015-12-13-4gb.img.xz As I understand it this is the most recent jessie build. Unfortunately on this image /sys/class/hwmon is not populated. It *is* populated on the wheezy builds. Do I need to install a package or kernel-module that solves this problem? Or is there a fix in the pipeline? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] bonescript - link to USR leds defective
I tried this
image:
https://rcn-ee.com/rootfs/bb.org/testing/2015-12-13/lxqt-4gb/bone-debian-8.2-lxqt-4gb-armhf-2015-12-13-4gb.img.xz
As I understand it this is the most recent jessie build.
I tried to run this script:
root@bbone:~/boneboot# cat ledsoff.js
var b=require('bonescript');
b.pinMode('USR0', 'out');
b.pinMode('USR1', 'out');
b.pinMode('USR2', 'out');
b.pinMode('USR3', 'out');
b.digitalWrite('USR0', 0);
b.digitalWrite('USR1', 0);
b.digitalWrite('USR2', 0);
b.digitalWrite('USR3', 0);
This is the result:
root@bbone:~/boneboot# nodejs ledsoff.js
error: Unable to find LED: usr0
error: Unable to find LED: usr1
error: Unable to find LED: usr2
error: Unable to find LED: usr3
error: Unable to find gpio: /sys/class/leds/beaglebone::usr0/brightness
error: Unable to write to /sys/class/leds/beaglebone::usr0/brightness
error: Unable to find gpio: /sys/class/leds/beaglebone::usr1/brightness
error: Unable to write to /sys/class/leds/beaglebone::usr1/brightness
error: Unable to find gpio: /sys/class/leds/beaglebone::usr2/brightness
error: Unable to write to /sys/class/leds/beaglebone::usr2/brightness
error: Unable to find gpio: /sys/class/leds/beaglebone::usr3/brightness
error: Unable to write to /sys/class/leds/beaglebone::usr3/brightness
Nothing strange here:
root@bbone:~/boneboot# ls -al /sys/class/leds
total 0
drwxr-xr-x 2 root root 0 Dec 19 09:43 .
drwxr-xr-x 54 root root 0 Dec 19 09:30 ..
lrwxrwxrwx 1 root root 0 Dec 19 09:22 beaglebone:green:usr0 -> ../../
devices/platform/leds/leds/beaglebone:green:usr0
lrwxrwxrwx 1 root root 0 Dec 19 09:22 beaglebone:green:usr1 -> ../../
devices/platform/leds/leds/beaglebone:green:usr1
lrwxrwxrwx 1 root root 0 Dec 19 09:22 beaglebone:green:usr2 -> ../../
devices/platform/leds/leds/beaglebone:green:usr2
lrwxrwxrwx 1 root root 0 Dec 19 09:22 beaglebone:green:usr3 -> ../../
devices/platform/leds/leds/beaglebone:green:usr3
Any suggestions how to get this to work are welcome.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Recommended Image
There are still a lot of roblems with the Jessie image. At this moment I'd advice to go for Wheezy. On Tuesday, 15 December 2015 21:45:25 UTC+1, Bit Pusher wrote: > > I'm starting to update from an outdated image and to be clean am planning > on starting from scratch with a newly flashed image. > On http://beagleboard.org/latest-images there are two possible Debian > images from Nov. 12'th, Wheezy 7.9 and Jessie 8.2. It is not clear > which image I should use. I'm using the PRU and SPI1 (which also > previously required SPI0 to be loaded) and many python modules. I load the > PRU, SPI0 and SPI1 > using three device tree overlays. Could someone recommend which image to > use? Thanks and appreciated. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: bonescript - link to USR leds defective
Also, this error bothers me: Dec 19 14:08:31 bbone ledsoff: Dec 19 14:08:31 bbone ledsoff: module.js:340 Dec 19 14:08:31 bbone ledsoff: throw err; Dec 19 14:08:31 bbone ledsoff: ^ Dec 19 14:08:31 bbone ledsoff: Error: Cannot find module 'bonescript' Dec 19 14:08:31 bbone ledsoff: at Function.Module._resolveFilename ( module.js:338:15) Dec 19 14:08:31 bbone ledsoff: at Function.Module._load (module.js:280: 25) Dec 19 14:08:31 bbone ledsoff: at Module.require (module.js:364:17) Dec 19 14:08:31 bbone ledsoff: at require (module.js:380:17) Dec 19 14:08:31 bbone ledsoff: at Object. (/root/boneboot/ ledsoff.js:1:69) Dec 19 14:08:31 bbone ledsoff: at Module._compile (module.js:456:26) Dec 19 14:08:31 bbone ledsoff: at Object.Module._extensions..js (module. js:474:10) Dec 19 14:08:31 bbone ledsoff: at Module.load (module.js:356:32) Dec 19 14:08:31 bbone ledsoff: at Function.Module._load (module.js:312: 12) Dec 19 14:08:31 bbone ledsoff: at Function.Module.runMain (module.js:497 :10) So even getting bonescript to detect the hardware correctly means it'll still not work :-( -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Error: Cannot find module 'bonescript'
I've solved this by adding a line to the cron job that sets the environment
variable NODE_PATH.
NODE_PATH=/usr/local/lib/node_modules
# m h dom mon dow user command
@reboot rootsleep 120 && /usr/bin/nodejs /root/boneboot/ledsoff.js 2>&
1 | logger -p info -t ledsoff
On Friday, 18 December 2015 22:38:53 UTC+1, Maurice H. wrote:
>
>
> I have this simple script that I want to execute at boot time.
>
> The script:
> root@bbone:~# cat boneboot/ledsoff.js
> var b=require('bonescript');
>
>
> b.pinMode('USR0', 'out');
> b.pinMode('USR1', 'out');
> b.pinMode('USR2', 'out');
> b.pinMode('USR3', 'out');
>
>
> b.digitalWrite('USR0', 0);
> b.digitalWrite('USR1', 0);
> b.digitalWrite('USR2', 0);
> b.digitalWrite('USR3', 0);
>
> To run it at boot I've created a file in /etc/cron.d which looks like this:
> root@bbone:~# cat /etc/cron.d/boneboot
> # m h dom mon dow user command
> @reboot rootsleep 120 && /usr/bin/nodejs /root/boneboot/ledsoff.js 2
> >&1 | logger -p info -t ledsoff
>
> Unfortunately, when I reboot the BBB the code is not executed succesfully
> as shown by the log:
> root@bbone:~# cat /var/log/syslog
> Dec 18 21:54:49 bbone ledsoff:
> Dec 18 21:54:49 bbone ledsoff: module.js:340
> Dec 18 21:54:49 bbone ledsoff: throw err;
> Dec 18 21:54:49 bbone ledsoff: ^
> Dec 18 21:54:50 bbone ledsoff: Error: Cannot find module 'bonescript'
> Dec 18 21:54:50 bbone ledsoff: at Function.Module._resolveFilename (
> module.js:338:15)
> Dec 18 21:54:50 bbone ledsoff: at Function.Module._load (module.js:280
> :25)
> Dec 18 21:54:50 bbone ledsoff: at Module.require (module.js:364:17)
> Dec 18 21:54:50 bbone ledsoff: at require (module.js:380:17)
> Dec 18 21:54:50 bbone ledsoff: at Object. (/root/boneboot/
> ledsoff.js:1:69)
> Dec 18 21:54:50 bbone ledsoff: at Module._compile (module.js:456:26)
> Dec 18 21:54:50 bbone ledsoff: at Object.Module._extensions..js (
> module.js:474:10)
> Dec 18 21:54:50 bbone ledsoff: at Module.load (module.js:356:32)
> Dec 18 21:54:50 bbone ledsoff: at Function.Module._load (module.js:312
> :12)
> Dec 18 21:54:50 bbone ledsoff: at Function.Module.runMain (module.js:
> 497:10)
>
> However, when I logged in as root, the code executes normally.
>
> Any suggestions on how to proceed?
>
>
>
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] /sys/class/hwmon not populated on Jessie
I did. Thanks. Any chance this could be implemented by a third-party? Or is the TI-code a proprietary blob? > > Feel free to downgrae to 3.8.x if you need it: > > cd /opt/scripts/tools/ > git pull > sudo ./update_kernel.sh --bone-channel --stable > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: bonescript - link to USR leds defective
On Saturday, 19 December 2015 18:37:03 UTC+1, RobertCNelson wrote: > > On Sat, Dec 19, 2015 at 7:12 AM, Maurice H. > wrote: > > bonescript hasn't been ported to v4.1.x yet > > > That explains a lot. :-) Thanks I'm back on 3.8 now. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] /sys/class/hwmon not populated on Jessie
I know this has been discussed and I understand TI's POV. I apologize if I seemed pushy or something. That is not my intention. It's just that I currently see data coming from my BBB that seems reasonable, although slightly offset. There seems to be a nice correlation with changes in room-temperature too. Anyway, it was just me wondering. Never mind. I'll retire my code. Thanks for the answer. Really appreciating your effort. On Saturday, 19 December 2015 20:22:43 UTC+1, RobertCNelson wrote: > > On Sat, Dec 19, 2015 at 12:39 PM, Maurice H. > wrote: > > > > I did. Thanks. > > > > Any chance this could be implemented by a third-party? Or is the TI-code > a > > proprietary blob? > > Yeah, it's easy to fix: > > sudo ln -s /dev/urandom /sys/class/hwmon/temp_sensor > > okay so it's not "that" bad.. But /dev/urandom is more 'consistent'... > > But bad enough, TI hardware engineers told TI kernel developers to not > bother pushing it upstream. > > This has been discussed previously on this list.. > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: Recommended Image
On Saturday, 19 December 2015 19:53:18 UTC+1, Kenneth Martin wrote: > > Yes, I am starting to see that Jessie has issues: > [blabla...] > > I don't know how to use it with unknown devices and unknown subnet without > using DHCP which doesn't allow for fixed IPs - which I need). Note: without > a network manager, you need to enable wpa_supplicant.service. > > > IMHO, DHCP has no issues with a fixed IP. Either you define the IP in /etc/networks or (if the DNS is under your control) you can define a fixed IP for the MAC-address in question. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to set up multiple w1-gpio for a capeless BeagleBoneBlack?
I've come to the point where I can load the device tree and see that it is
loaded.
There is however no ID in /sys/devices/w1_bus_master1
Connections I have: GND = P9.1 DATA = P8.11 and VDD = P9.4 (3V3)
For your info I also have a TMP36, DHT22 and BMP183 connected. They all
seem to work fine.
Do I need to load a kernelmodule I wonder (w1-gpio or something?)
Any suggestions?
Maurice
On Sunday, May 19, 2013 at 7:58:50 AM UTC+2, Russell Senior wrote:
>
> > "Russell" == Russell Senior >
> writes:
>
> Here's what I did to get a one-wire bus working on BeagleBone Black.
> I created (modified from the weather cape's) a DTS file:
>
> /*
> * Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/
> *
> * This program is free software; you can redistribute it and/or modify
> * it under the terms of the GNU General Public License version 2 as
> * published by the Free Software Foundation.
> */
> /dts-v1/;
> /plugin/;
>
> / {
> compatible = "ti,beaglebone";
> part-number = "BB-BONE-W1";
> version = "00A0";
>
> fragment@0 {
> target = <&am33xx_pinmux>;
> __overlay__ {
> nocape_w1_pins: pinmux_nocape_w1_pins {
> pinctrl-single,pins = <
> 0x34 0x37 /*
> gpmc_ad13.gpio1_13, OMAP_PIN_INPUT_PULLUP | OMAP_MUX_MODE7 - w1-gpio */
> >;
> };
> };
> };
>
> fragment@1 {
> target = <&ocp>;
> __overlay__ {
> onewire@0 {
> compatible = "w1-gpio";
> pinctrl-names = "default";
> pinctrl-0 = <&nocape_w1_pins>;
> status = "okay";
>
> gpios = <&gpio2 13 0>;
> };
> };
> };
> };
>
> [...]
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
