**** BEGIN LOGGING AT Sun Jul 22 02:59:58 2007
Jul 22 03:13:12 <mscdex> i'm having a problem building gpe-image (for h4000). it fails complaining about libnet.h: "byte order has not been specified" and "expected identifier or '{' before string constant"
Jul 22 03:15:48 <mscdex> this happens while building thcrut_1.2.5.bb
Jul 22 03:33:41 * xota a sobar!
Jul 22 13:50:16 <dcordes> hi
Jul 22 14:20:31 <dcordes>  are there any devices similar to the nslu2 that are capable to be reflashed with a distro like angstrom?
Jul 22 14:31:27 * xota saluda!
Jul 22 14:32:38 <dcordes> xota: hi
Jul 22 14:46:24 <xota> buenas dcordes 
Jul 22 14:47:33 <dcordes> xota: do you know anything about NAS devices like the NSLU2=
Jul 22 14:47:34 <dcordes> ?
Jul 22 14:50:32 <xota> i don't know ;( sorry
Jul 22 15:12:39 * xota se pira!
Jul 22 15:16:12 <CoreDump|afk> dcordes: rwhitby would be the one to ask about NSLU2 and friends
Jul 22 15:56:07 <Specki23> hi all
Jul 22 15:56:26 <Specki23> :-)
Jul 22 15:58:27 <vanguard> Hi all
Jul 22 16:00:17 <vanguard> I someone familiar with angstrom and an usb-bluetooth-stick ? The usb-bluetooth-stick is not seen as the devive /dev/rfcomm0 (as it should be) , but as /dev/usb-1.x_ep02. Any hints ?
Jul 22 16:01:04 <vanguard> Shall I put a symlink named /dev/rfcomm0 to this ?
Jul 22 16:01:51 <vanguard> There is no /dev/rfcomm0 at all........
Jul 22 16:02:37 <XorA|gone> vanguard: you need to use rfcomm command to register rfcomm devices
Jul 22 16:02:43 <XorA|gone> vanguard: they arent automatic
Jul 22 16:03:02 <vanguard> How do I have to do this ?
Jul 22 16:03:07 <XorA|gone> rfcomm bind 0 XX:XX:XX:XX:XX <channel> for rfcomm0
Jul 22 16:03:10 <vanguard> So,mkething with bind
Jul 22 16:03:40 <vanguard> Ah, I rread such a thing somewhere.
Jul 22 16:03:54 <vanguard> Will this last for the future ?
Jul 22 16:04:11 <XorA|gone> vanguard: you can put them in /etc/bluetooth/rfcomm if I remeber right
Jul 22 16:04:30 <vanguard> Yes, this is, what I already did.
Jul 22 16:04:51 <XorA|gone> vanguard: you might need to put something like RFCOMM=1 in /etc/default/bluetooth as well
Jul 22 16:05:06 <XorA|gone> vanguard: I seem to recal it was disabled by default
Jul 22 16:05:50 <vanguard> Yes, this is missing.
Jul 22 16:06:57 <vanguard> Do I have to reboot, to get it actiuve or is there any process, I can restart ?
Jul 22 16:07:00 * XorA|gone wodners where his zaurus is
Jul 22 16:07:06 <XorA|gone> vanguard: /etc/init.d/bluetooth stop
Jul 22 16:07:08 <XorA|gone> vanguard: /etc/init.d/bluetooth start
Jul 22 16:08:11 <vanguard> No success.
Jul 22 16:08:22 <vanguard> There is still no /dev/rfcomm
Jul 22 16:09:23 <XorA|gone> vanguard: just issue the command by hand
Jul 22 16:09:39 <XorA|gone> vanguard: then work out where the scripts are busted, things seemed to have moved since I last looked
Jul 22 16:10:56 <vanguard> Yes, seems this way. I am not so familiar with bluetooth, but I understand it right: The /dev/rfcomm will be automatically generated by the kernel, is it ?
Jul 22 16:31:06 <vanguard> Test123
Jul 22 16:31:20 <vanguard> Seems, I was offline.
Jul 22 16:36:00 <XorA|gone> heh heh
Jul 22 16:36:22 <XorA|gone> vanguard: rfcomm is only generated when rfcomm bind command is issuied
Jul 22 16:37:55 <vanguard> O.k., so , if I would like to make it comfortable, I would have to write a little script and put it into the required runlevel. 
Jul 22 16:38:39 <XorA|gone> vanguard: yeah
Jul 22 16:38:51 <vanguard> This is not cool !
Jul 22 16:39:13 <vanguard> After a new flash, all my manual work would be gone.
Jul 22 16:39:17 <vanguard> This is not cool ...
Jul 22 16:40:09 <vanguard> Maybe you should add such scripts per default in the roms. 
Jul 22 16:56:49 <koen> we don't have ROMs
Jul 22 16:57:20 <koen> and anything but using hcid is deprecated and will go away in future bluez releases
Jul 22 17:06:04 <vanguard> koen: O.k., if there are changes, it would be nice to implement it into the images. So it is really more user friendly.
Jul 22 17:06:32 <koen> go ahead, it's opensource, attach patches to the bugtracker
Jul 22 17:07:38 <vanguard> I am willing to do, but these are no patches at all. These are no bugs, these are more "additional features".
Jul 22 19:20:30 <vanguard> Hi all. Can someone take a look, who is the owner and which rights does /dev/rfcomm0 possesses ? I am testing here now for hours, and am not able to get pppd running.
Jul 22 19:21:25 <vanguard> Even, if I start pppd as root, the log says: /dev/rfcomm: connection refused
Jul 22 19:23:04 <vanguard> (I want to use gprs with the SL-C1000)
Jul 22 19:25:13 <vanguard> Even, if I start pppd as root, the log says:        Failed to open /dev/rfcomm: connection refused
Jul 22 19:41:36 <polyonymous> I think connection refused is not exactly permission denied.
Jul 22 19:51:38 <vanguard> Hmm, you think, it is the connection to my provider ?
Jul 22 19:51:49 <polyonymous> no, to your bluetooth device
Jul 22 19:52:12 <vanguard> You mean, in my case, to the cell phone.
Jul 22 19:52:25 <polyonymous> exactly
Jul 22 19:52:43 <polyonymous> are they paired? Your phone and Z?
Jul 22 19:52:53 <vanguard> Yes, they are.
Jul 22 19:53:10 <vanguard> I can get access to the phone and transfer datas.
Jul 22 19:53:14 <polyonymous> hmm... is rfcomm0 set up properly to connect to dun channel?
Jul 22 19:53:23 <vanguard> Yes, it is.
Jul 22 19:53:40 <polyonymous> hmm... maybe it's your phone settings then?
Jul 22 19:53:47 <vanguard> The rfcomm0 points to the right MAC.
Jul 22 19:53:53 <polyonymous> and the channel?
Jul 22 19:54:04 <vanguard> Maybe the phone may not act as a modem ?
Jul 22 19:54:10 <vanguard> Chanel 1
Jul 22 19:54:29 <polyonymous> Well, I don't have a solution to you, it's been a while since I've done it, but HAVE done it :)
Jul 22 19:54:46 <polyonymous> I don't know whether channel 1 is the right one, you may want to get the channel via sdp maybe?
Jul 22 19:54:59 <vanguard> :) Yes, I know, it is working at other people.
Jul 22 19:55:07 <vanguard> sdp ???
Jul 22 19:55:28 <polyonymous> sdptool, hang on I'll try to get you a command line
Jul 22 19:56:12 <vanguard> sdptool browse ?
Jul 22 19:56:27 <polyonymous> yes
Jul 22 19:56:31 <polyonymous> try this one.
Jul 22 19:57:00 <polyonymous> I get permission denied frommy phone, I think I have my desktop bt screwed up after  installing latest bluez :)
Jul 22 19:58:07 <vanguard> Hmm, what do I have to look for ? Dial-up-networking ?
Jul 22 19:58:22 <polyonymous> I'd guess yes
Jul 22 19:58:25 <polyonymous> DUN
Jul 22 19:59:11 <vanguard> Hmm, that woul be channel 3.
Jul 22 19:59:32 <polyonymous> here you go :)
Jul 22 20:00:40 <vanguard> I am rebooting. Just to get a clean initilaisation.
Jul 22 20:01:08 <polyonymous> heh, I'd test it first :)
Jul 22 20:01:21 <vanguard> Strange: Some hours ago, I could not get access to the bt-stick. Suddenly it worked.
Jul 22 20:02:04 <vanguard> Although, I did nothing. I suppose, the kernel unloaded some modules.
Jul 22 20:02:20 <polyonymous> users always say "I did nothing", even after complete reinstall :)
Jul 22 20:02:46 <vanguard> O.k., you are right: I stuck out the stick. 
Jul 22 20:03:08 <vanguard> Just about 2 minutes. Maybe it should be this long time.
Jul 22 20:04:27 <vanguard> No success.....
Jul 22 20:05:02 <vanguard> Just a moment.
Jul 22 20:05:11 <vanguard> A new message: 
Jul 22 20:05:33 <vanguard> Even, if I start pppd as root, the log says:        Failed to open /dev/rfcomm: no route to host
Jul 22 20:05:52 <polyonymous> rfcomm or rfcomm0? or is it the same?
Jul 22 20:06:09 <vanguard> A typo: rfcomm0
Jul 22 20:06:25 <vanguard> Failed to open /dev/rfcomm0: no route to host
Jul 22 20:06:42 <polyonymous> hmm... Well, I'm not sure what this message means...
Jul 22 20:06:53 <polyonymous> maybe your phone is turned off? :)
Jul 22 20:07:35 <vanguard> Yes. The stick is off.
Jul 22 20:08:18 <vanguard> The module "asix" is not loaded by default.
Jul 22 20:08:32 <vanguard> Should have added it in /etc/modules
Jul 22 20:11:06 <vanguard> vanguard asks himself, if some very good coder would like to develop an easier way to use gprs with the Z..........
Jul 22 21:07:21 <mimecar> hi
Jul 22 22:11:22 <jonb> Anyone here?
Jul 22 22:41:26 <Laibsch> I hereby declare my resignation from OE and Angstrom
Jul 22 22:41:28 <Laibsch> By
Jul 22 22:41:30 <Laibsch> Bye
Jul 22 22:45:20 <dni1> hi
**** ENDING LOGGING AT Mon Jul 23 02:59:56 2007