| 01:16.09 | *** join/#nslu2-linux edmondsc (n=edmondsc@c-24-22-21-198.hsd1.mn.comcast.net) |
| 03:47.53 | *** join/#nslu2-linux Ragnor (n=Ragnor@dslb-084-062-119-135.pools.arcor-ip.net) |
| 03:58.22 | *** join/#nslu2-linux DrZimmerman (n=theo@77-56-246-76.dclient.hispeed.ch) |
| 04:10.50 | *** join/#nslu2-linux nicolas_ (n=nicolas@dslb-084-058-246-231.pools.arcor-ip.net) |
| 04:15.06 | *** join/#nslu2-linux kizoku_ (n=albus@ti0182a340-0523.bb.online.no) |
| 04:46.12 | *** join/#nslu2-linux Sinclair73de_ (n=Sinclair@p57B48E49.dip0.t-ipconnect.de) |
| 05:45.33 | *** join/#nslu2-linux erikja (n=erikja@0x57314066.abnxx10.adsl-dhcp.tele.dk) |
| 05:58.09 | *** join/#nslu2-linux x29a (n=x29a@unaffiliated/x29a) |
| 06:04.11 | *** join/#nslu2-linux drath_ (i=vmaster@p5B07CAF6.dip.t-dialin.net) |
| 09:02.27 | *** join/#nslu2-linux mithro (n=tim@unaffiliated/mithro) |
| 09:56.09 | *** join/#nslu2-linux kolla (n=kolla@drift1.uninett.no) |
| 11:18.07 | *** join/#nslu2-linux Caelian (n=pascal@p5481FDBC.dip.t-dialin.net) |
| 11:18.43 | Caelian | hi ... anyone in here happens to have any experience with getting "Angstrom" up and running on an NSLU2 ? |
| 11:19.16 | Caelian | so far i can flash the slug just fine ... but it seems to simply not boot up afterwards |
| 12:55.25 | *** join/#nslu2-linux GPSFan (n=kenm@12.10.255.246) |
| 12:58.34 | mwester | Angstrom requires a serial console on the NSLU2 at this moment. You should consider SlugOS or perhaps Debian instead. |
| 12:59.41 | *** join/#nslu2-linux mithro (n=tim@unaffiliated/mithro) |
| 13:08.16 | Caelian | mwester: we've actually been using SlugOS so far ... (with great success) ... it's just that from my understanding the ARM EABI provides significantly increased Floating Point performance, and things are starting to look like that would be a very welcome benefit |
| 13:08.28 | Caelian | mwester: hence why i started looking into Angstrom |
| 13:10.22 | mwester | We are currently targetting EABI for SlugOS 5, but there is no planned release date. We intend to narrow the gap between Angstrom and SlugOS over time, just to ease support, but Angstrom lacks many SlugOS features that are specific to the type of devices liek the NLSU2. One of those is the total lack of a display/console. |
| 13:10.56 | mwester | Adding a serial port is really not difficult, see the wiki for information. |
| 13:11.37 | Caelian | mwester: yeah i know ... we've done so before ... |
| 13:12.09 | Caelian | however ... if SlugOS is targeting EABI for SlugOS 5 ... that would simply remove the interest in Angstrom :) |
| 13:14.14 | mwester | Except for the time factor; that'll be a big shift and can't be done quickly (new feeds,etc) |
| 13:16.25 | Caelian | honestly at the time being FP performance isn't that big of an issue yet ... for now it's mostly used for Data Acquisition purposes ... once we want to start processing the acquired data as it comes in ... that's when FP performance may become a concern ... though with some twiddling we might just be able to do it all in fixed point ... time will tell |
| 13:18.41 | *** join/#nslu2-linux Zword (n=Zword@bos94-3-82-226-234-106.fbx.proxad.net) |
| 13:39.36 | *** join/#nslu2-linux osas (n=nnnnnnnn@nslu2-linux/osas) |
| 13:56.05 | *** join/#nslu2-linux Ragnor (n=Ragnor@dslb-084-062-105-037.pools.arcor-ip.net) |
| 13:57.33 | *** part/#nslu2-linux Caelian (n=pascal@p5481FDBC.dip.t-dialin.net) |
| 14:02.18 | *** join/#nslu2-linux Reedy (n=Reedy@wikimedia/Reedy-Boy) |
| 14:16.31 | CIA-43 | 03oleo * r8205 10optware/trunk/make/transmission.mk: transmisission: 5611->5633 |
| 15:13.57 | *** join/#nslu2-linux Caelian (n=pascal@p5481FDBC.dip.t-dialin.net) |
| 15:15.16 | Caelian | perhaps i am just being silly but i can't seem to get it to work ... what do i need to put into my slugos/conf/local.conf in order to make it include additional packages into the generated firmware image ? |
| 15:16.18 | Caelian | so far it looks like DISTRO_EXTRA_DEPENDS += "openntpd" e.g. causes the openntpd package to be built .... however DISTRO_EXTRA_RDEPENDS += "openntpd" seems to have no effect upon whether or not it is included into the built firmware image |
| 15:17.20 | mwester | This is a bug in bitbake/OE. |
| 15:18.04 | Caelian | any way to work around this ? |
| 15:18.23 | Caelian | it's a little awkward having to ipkg install the packages afterwards |
| 15:18.31 | mwester | Hmm. actually not - it seems this bug was fixed. |
| 15:18.39 | mwester | So, perhpas it's something else. |
| 15:18.44 | Caelian | in that case what am i doing wrong ? |
| 15:18.57 | mwester | Did you change this after you did a sucessful build? |
| 15:19.39 | mwester | i.e. did you take special action to ensure that the build system's dependency tracking mechanism knows that it must rebuild the tasks and the rootfs image? |
| 15:20.05 | Caelian | mwester: i did ... however i did rm -Rf anything slugos-image related from slugos/tmp/stamps and slugos/tmp/work/ |
| 15:20.54 | Caelian | that should normally be enough to trigger a rebuilt of the rootfs not ? |
| 15:21.11 | mwester | No, it just recreates the image from the existing rootfs. |
| 15:21.23 | mwester | You need to remove the stamps for task-slugos-1.0* |
| 15:22.02 | mwester | The task recipe is the one that does the real work of determining what goes into the rootfs, and is where the EXTRA_RDEPENDS is evaluated. |
| 15:22.32 | Caelian | aaah i see |
| 15:22.36 | Caelian | ok ... let me try that |
| 15:23.43 | mwester | Just so we know what to consider for SlugOS in the future, can you share what you're changing if it might be generally applicable? |
| 15:24.30 | Caelian | sure ... it's basically just openntpd so the system can synchronize its time out of the box ... and the kernel-module-ftdi-sio along with kernel-module-usbserial |
| 15:24.39 | Caelian | probably not general purpose enough :) |
| 15:24.59 | Caelian | we need the ftdi-sio module for USB<->RS232 / USB<->RS485 |
| 15:25.46 | Caelian | we use it for data acquisition purposes with regards to power consumption / power grid monitoring |
| 15:27.14 | mwester | Ah, ok. You're right, that's probably not general enough. But that's a really cool application! |
| 15:29.36 | Caelian | yup :) |
| 15:31.06 | Caelian | Ok ...that seems to indeed have done the trick according to the log.do_rootfs |
| 15:32.00 | Caelian | reflashing the slug |
| 15:32.55 | Caelian | perhaps inclusion of openntpd in the default build isn't that bad an idea ... though ftdi-sio and usbserial are definitely not |
| 15:33.16 | Caelian | or should i say ... definitely are |
| 15:38.18 | Caelian | hmmmm .... openntpd did get installed into the firmware image ... but somehow it can't start since there now is no ntpd user |
| 15:38.36 | Caelian | i guess something is a little "oddball" there |
| 15:40.38 | Caelian | yup ... did an ipkg remove openntpd followed by an ipkg install openntpd and it looks like during the configuring openntpd stage it automatically adds the ntpd user |
| 15:41.13 | Caelian | i guess i'll stick to installing openntpd afterwards for the time being ... |
| 15:42.09 | Caelian | would you happen to have any idea how this could be fixed ? |
| 16:01.35 | *** join/#nslu2-linux eiffel_ (n=eiffel@dslb-084-061-057-021.pools.arcor-ip.net) |
| 16:10.07 | mwester | Caelian: That should be automagically handled by the package post-install script, which is run at early boot time. Did you reboot after the intiial boot to see if the second boot had things right? |
| 16:10.33 | mwester | In a cross-dev environment, we defer the post-install scripts until the first boot of the target device. |
| 16:21.06 | Caelian | mwester: hmmmm ... i didn |
| 16:21.17 | Caelian | i'll retry to see if that indeed did the trick |
| 16:31.00 | mwester | That said, there are some pre-defined user ids in the password file; it's not too tough to add some others. |
| 16:33.48 | Caelian | nope ... didn't work ... |
| 16:34.16 | Caelian | i guess that would work ... but i am not exactly sure how to integrate such a thing into the current build framework (as a local change) |
| 16:35.57 | Caelian | with didn't work i meant ... if i install it afterwards the user does get added ... if i include it in the firmware image the user is not added |
| 16:40.08 | mwester | Try something like this: |
| 16:40.12 | mwester | IMAGE_PREPROCESS_COMMAND += "sed -i -es,^root::0,root:BTMzOOAQfESg6:0, ${IMAGE_ROOTFS}/etc/passwd;" |
| 16:40.17 | mwester | in your local.conf file. |
| 16:41.00 | mwester | That sample changes the root password, but you can just as easily change the sed to a something that will append a line to the file. |
| 16:41.51 | Caelian | i see what you mean ... i'll fiddle around with that thanks for the suggestion ... i am going to head off for now though ... worked long enough today as is :) |
| 16:57.24 | *** join/#nslu2-linux pleemans (n=peter@d51A5E76A.access.telenet.be) |
| 18:00.57 | CIA-43 | 03bzhou * r8206 10optware/trunk/ (4 files in 2 dirs): mysql: 4.1.20 -> 4.1.22; set STACK_DIRECTION to 1 if arm or armeb |
| 18:08.22 | *** join/#nslu2-linux Reedy (n=Reedy@wikimedia/Reedy-Boy) |
| 18:16.17 | CIA-43 | 03bzhou * r8207 10optware/trunk/sources/mysql/comp_err.patch: mysql: added missing comp_err.patch |
| 18:17.48 | CIA-43 | 03bzhou * r8208 10optware/trunk/sources/mysql/lex_hash.h: mysql: no longer need the pre-generated lex_hash.h |
| 19:18.25 | *** join/#nslu2-linux edmondsc (n=edmondsc@128-193-143-104.public.oregonstate.edu) |
| 19:52.43 | VoodooZ | Any plans for 2.6.25? |
| 19:57.54 | mwester | Yep. But unspecified as to when. |
| 19:58.04 | joshin | I was going to take a crack at it next week. |
| 19:58.19 | VoodooZ | cool. |
| 19:58.25 | VoodooZ | there's even more RT stuff in there. |
| 19:58.39 | *** join/#nslu2-linux macpower (n=toto@AOrleans-753-1-22-60.w90-19.abo.wanadoo.fr) |
| 19:58.44 | macpower | hi how are you? |
| 19:58.45 | VoodooZ | I started using the HR timers in 2.6.24 and it made a huge diff for my sensor loop |
| 19:59.18 | joshin | I just want to see if the oom-killer behaves on heavily loaded systems on it. |
| 19:59.49 | macpower | somebody can help me please? |
| 20:00.00 | VoodooZ | i see. |
| 20:00.04 | Reedy | macpower, just ask your question |
| 20:00.07 | joshin | macpower: ask your question |
| 20:00.14 | joshin | Then we can choose to ignore it. |
| 20:00.15 | joshin | :p |
| 20:00.22 | VoodooZ | haha |
| 20:00.23 | macpower | i use a converter usb serial onnslu2 |
| 20:00.37 | joshin | Ok. |
| 20:00.39 | macpower | and it's mounted on ttyUSB0 |
| 20:00.41 | macpower | it's normal |
| 20:01.07 | macpower | but for me i use a programming software that it use a serial port ttyS0 |
| 20:01.20 | macpower | and i can't change port on software |
| 20:01.42 | joshin | Does it work as roo? |
| 20:01.43 | Reedy | ln -s /dev/ttyUSB0 /dev/ttyS0 |
| 20:01.47 | joshin | root? |
| 20:01.47 | Reedy | ? |
| 20:02.01 | macpower | so for use software with serial converter, i have add a symlink : /dev/tty/USB0 /dev/ttyS0 |
| 20:02.14 | macpower | but this is only a virtual link |
| 20:02.31 | joshin | You might be able to configure udev to do what you want. |
| 20:02.37 | macpower | ok |
| 20:02.54 | macpower | but what i configure udev for use ttyS0 native |
| 20:02.55 | macpower | please |
| 20:03.31 | mwester | A) find the developer of that software, and kick them in the ***** for such stupid design, then B) use "ls -l" to find the major and minor device numbers given to /dev/tty/USB0, and C) use "mknod" to create /dev/ttyS0 with the matching major and minor numbers. |
| 20:03.47 | mwester | Use google to find info on mknod, if you are not familiar with that command. |
| 20:03.59 | macpower | i have try mknod |
| 20:04.30 | mwester | Then you'll have to provide more information on what doesn't work with the symbolic link, and with the mknod solutions. |
| 20:04.55 | macpower | and how i use mknod please, i remove ttyS0 |
| 20:05.08 | macpower | mknod ttyS0 -c 8 0 |
| 20:05.42 | macpower | but after ? please |
| 20:06.21 | mwester | http://www.google.com/url?sa=t&ct=res&cd=1&url=http%3A%2F%2Fwww.faqs.org%2Fdocs%2Flinux_admin%2Fx797.html&ei=rq0HSKmQGqOKiAGSzuGtCQ&usg=AFQjCNGb7p7MIplLU79_PYn1MZAVvTlNzA&sig2=iPk_5aOlHwQkDgfXyBQ0bA |
| 20:06.27 | mwester | First hit from google give an example. |
| 20:06.38 | mwester | Find the numbers you need from the output from "ls -l /dev/tty/USB0" |
| 20:07.28 | mwester | I don't have one of those devices plugged in, so I don't know what the numbers should be. |
| 20:07.35 | joshin | I see that mwester has had similar frustrations with devs hardcoding device names in their code |
| 20:08.13 | Reedy | lol, you do wonder if people find it so hard to use variables.. |
| 20:08.25 | mwester | Yep. And also bad experiences with devs who assume that the device name is always /dev/ttyS<some-number>... |
| 20:08.44 | mwester | They get the variable right, but they put in too much assumption. |
| 20:09.33 | mwester | But it isn't just Linux devs; the windows apps that only know about four serial ports are also a big problem. All my bluetooth serial ports show up >3. |
| 20:09.55 | macpower | ok |
| 20:10.00 | macpower | if i create a tyS0 |
| 20:10.12 | macpower | ttyS0, it's not according to ttyUSB0 |
| 20:10.13 | macpower | ? |
| 20:10.30 | mwester | I don't understand your question? |
| 20:11.05 | macpower | after i have create a ttyS0 bu |
| 20:11.10 | macpower | by mknod |
| 20:11.32 | macpower | i have a ttyS0 and ttyUSB0 |
| 20:11.44 | macpower | by i don't use ttyS0 for ttyUSB0 |
| 20:11.55 | macpower | but a symlink don't work |
| 20:12.46 | mwester | Linux doesn't go by the name -- it goes by the major and minor numbers that are associated. By creating ttyS0 with the same numbers as ttyUSB0, as far as Linux is concerned they are one and the same device. |
| 20:13.27 | mwester | A symlink may not work, depending on how the application is written, and apparently your application doesn't like sym links. |
| 20:13.52 | macpower | so i can't create automaticly on boot a device that associed to ttyS0 from ttyUSB0, in udev? |
| 20:14.55 | mwester | That's what udev is for. But you'll have to figure out the correct changes to make to the rules. |
| 20:15.45 | macpower | this is can work : KERNEL=="ttyUSB[0-9]*" SYMLINK+=""ttyS0"s ? |
| 20:16.34 | mwester | ? don't know - you'll have to try it. |
| 20:17.00 | macpower | no i can't try, i don't have my plateforme |
| 20:17.07 | macpower | i try tommorow |
| 20:18.25 | macpower | but i need to remove a line on udev when i add this line? |
| 20:28.51 | macpower | thanks for all |
| 20:28.56 | macpower | bye good night |
| 21:00.41 | *** join/#nslu2-linux edmondsc (n=edmondsc@128-193-143-104.public.oregonstate.edu) |
| 21:33.52 | *** join/#nslu2-linux Reedy (n=Reedy@wikimedia/Reedy-Boy) |
| 22:36.18 | Reedy | haha |
| 22:36.32 | Reedy | googling "using cowsay" brings up the NSLU2-linux svn and the cowsay mk file |
| 22:37.21 | ka6sox-laptop | mooo? |
| 22:37.47 | ka6sox-laptop | joshin, what firmware do you want in your slug? |
| 22:38.01 | ka6sox-laptop | I'm currently testing with 4.9Alpha |
| 22:38.35 | ka6sox-laptop | slugos-be 4.9a |
| 23:21.18 | *** join/#nslu2-linux edmondsc (n=edmondsc@c-24-22-21-198.hsd1.mn.comcast.net) |
| 23:38.23 | *** join/#nslu2-linux thraxisp (n=thraxisp@24.139.16.154) |