**** BEGIN LOGGING AT Tue Apr 01 02:59:59 2014
Apr 01 03:11:19 <adambd> Hi all, I did this project www.ben-dror.com/pinokio a while back. It was implemented with Arduino and Processing. I want to get the whole thing running on a BBB. I have gotten openCV to run in python with a Playstation eye. I am experiencing very slow frame rates - I need around 10 - 30fps for the project to work. Any help would be appreciated.
Apr 01 03:14:47 <monoxide_13> NewtG, Does it boot without the SD card in it?
Apr 01 03:16:26 <monoxide_13> adambd: what frame rates are you getting now?
Apr 01 03:24:08 <danr_> hi
Apr 01 03:25:32 <danr_> After much Googling I'm not finding a solid solution for what I want to do: Run JDK8 (released this month) on the BBB
Apr 01 03:25:48 <danr_> Ideally looking for an image
Apr 01 03:25:53 <danr_> but happy to follow a recipe
Apr 01 03:27:45 <adambd> monoxide_13: around 3-4fps
Apr 01 03:29:00 <spikebike> can you downsample the resolution a bit?
Apr 01 03:31:27 <spikebike> switch to C?
Apr 01 04:18:58 <tbr> m_billybob: it certainly is that way on the BBW
Apr 01 04:20:15 <adambd> For some reason my old session ended. Here is my question - Hi all, I did this project www.ben-dror.com/pinokio a while back. It was implemented with Arduino and Processing. I want to get the whole thing running on a BBB. I have gotten openCV to run in python with a Playstation eye. I am experiencing very slow frame rates - I need around 10 - 30fps for the project to work. Any help would be appreciated.
Apr 01 04:21:03 <m_billybob> tbr,  eh ?
Apr 01 04:21:29 <spikebike> wow, intel's going after the maker market
Apr 01 04:21:40 <m_billybob> not very well
Apr 01 04:21:43 <spikebike> not nearly as much gpio though, otherwise quite nice
Apr 01 04:21:52 <spikebike> http://linuxgizmos.com/intel-unveils-tiny-x86-minnowboard-max-open-sbc/
Apr 01 04:22:56 <nyt-> meh
Apr 01 04:22:59 <nyt-> i wouldnt use it
Apr 01 04:23:23 <nyt-> its cool if you want a tiny media player i guess
Apr 01 04:24:05 <m_billybob> oh, that. its been aroudn a while. price isnt low enough
Apr 01 04:24:13 <nyt-> 1230 and finally get to work on my beaglebone library
Apr 01 04:24:14 * nyt- sighs
Apr 01 04:24:20 <spikebike> $99 is much closer
Apr 01 04:26:14 <spikebike> I wonder how good HD4000 support is for OpenCL/OpenCV
Apr 01 04:27:38 <m_billybob> not very good id wager
Apr 01 04:27:45 <m_billybob> since it isnt exactly a powerhosue
Apr 01 04:27:56 <xa0z> Anyone here use atheros ath9k_htc driver?
Apr 01 04:28:05 <m_billybob> however, that board is not to bad for $129 the 2GB model
Apr 01 04:28:53 <m_billybob> The windows freaks will also be glad that it will run Windows XP embedded like a champ
Apr 01 04:29:23 <m_billybob> personally, im more interrested in the SATA and GbE interfaces
Apr 01 04:47:40 <spikebike> ya, I care not abotu windows, but more cpu, 64 bit, and more ram sounds pretty good.
Apr 01 04:59:48 <iandow> xa0z: I tried using that driver on BBW. While it worked better than the realtek driver rtl8192, it did not ultimately work reliably.
Apr 01 05:01:28 <iandow> After about 30 minutes of uptime with wlan0 enabled, i would usually get a kernel panic.
Apr 01 05:01:56 <iandow> I used the htc firmware from https://github.com/qca/open-ath9k-htc-firmware
Apr 01 05:03:38 <iandow> I wasted a lot of time trying to get that to work.  I would have been much better off just using a BBB instead of BBW.  (But at the time of my study, BBB was unavailable)
Apr 01 05:10:28 <xa0z> ll
Apr 01 05:10:32 <xa0z> This kind of sucks.
Apr 01 05:15:40 <iandow> you're telling me
Apr 01 05:15:46 <nyt-> lol
Apr 01 05:15:49 <nyt-> screw those rtl and atheros chips
Apr 01 05:15:51 <nyt-> you want a good mini usb chip
Apr 01 05:15:52 <nyt-> get this one
Apr 01 05:16:11 <nyt-> its an ralink, works out of the box.
Apr 01 05:16:18 * nyt- waits for amazon to finish its holiday
Apr 01 05:16:55 <nyt-> http://www.amazon.com/gp/product/B00762YNMG
Apr 01 05:17:02 <nyt-> rock solid wifi
Apr 01 05:17:15 <xa0z> I've seen some of those mini ralink devices on ebay, but the issue is if it will work with mode "Master".
Apr 01 05:17:25 <xa0z> I don't want to use crap like hostapd.
Apr 01 05:17:43 <nyt-> ahhhhhhhh
Apr 01 05:18:29 <nyt-> root@rbone:~# iwconfig wlan0 mode Managed
Apr 01 05:18:29 <nyt-> root@rbone:~# iwconfig wlan0 mode Master
Apr 01 05:18:29 <nyt-> Error for wireless request "Set Mode" (8B06) :
Apr 01 05:18:29 <nyt->     SET failed on device wlan0 ; Invalid argument.
Apr 01 05:18:30 <nyt-> sorry
Apr 01 05:18:32 <nyt-> no joy
Apr 01 05:18:56 <xa0z> Yea, stupid mac80211
Apr 01 05:25:18 <nyt-> callback = lambda { |pin, mv_last, mv, count| puts "#{pin} #{mv_last} -> #{mv}" }
Apr 01 05:25:18 <nyt-> Rubybone::AIN.run_on_change(callback, :P9_33, 200, 0.01)
Apr 01 05:25:18 <nyt-> sleep 3000
Apr 01 05:25:26 <nyt-> root@rbone:~/rubybone# chmod 700 test.rb;./test.rb
Apr 01 05:25:26 <nyt-> P9_33 1 -> 207
Apr 01 05:25:26 <nyt-> P9_33 207 -> 415
Apr 01 05:25:26 <nyt-> P9_33 415 -> 622
Apr 01 05:25:26 <nyt-> P9_33 622 -> 825
Apr 01 05:25:27 <nyt-> so nice
Apr 01 06:34:12 <nyt-> ffs l2irc
Apr 01 06:34:20 <nyt-> =[
Apr 01 06:34:27 <Dan2> ^
Apr 01 06:34:43 <Dan2> time like these.... wheres the op's :D
Apr 01 06:42:17 <LetoThe2nd> whenever he/she complains and has fixed his/her client/connection, let me know. i'll remove the ban then.
Apr 01 06:43:02 <Dan2> cheers LetoThe2nd
Apr 01 06:43:06 <nyt-> ty
Apr 01 07:22:56 <k-man> how might i make debian on the BBB auto connect to the various wifi networks that I use?
Apr 01 07:27:20 <KotH> configure the network interface properly
Apr 01 07:27:28 <KotH> also join #debian on oftc
Apr 01 07:47:26 <k-man> so i can consider it a debian question rather than a BBB one?
Apr 01 07:47:40 <k-man> KotH, yeah, i tried to configure it various ways but always seem to hit road blocks
Apr 01 07:48:14 <KotH> yes, it's a debian question
Apr 01 07:48:55 <KotH> the only automatic configuration tools i know are wicd, conman and networkmanager. but afaik all of them are ment to be used with a gui
Apr 01 07:49:06 <KotH> but i might be wrong
Apr 01 07:49:15 <KotH> anyways. the debian boys are the right guys to ask
Apr 01 07:49:46 <k-man> yeah, thats where i run into problems. network manager now has nmcli, but the version in wheezy doesn't have the options yet for creating new networks. more recent versions of it can i believe
Apr 01 07:49:52 <k-man> thanks koth
Apr 01 10:09:32 <Dan2> anyone had an issue where sudo reboot/poweroff gives you the usual "going down" message but then never actually reboots or powers off?
Apr 01 10:09:44 <Dan2> or have any idea where i could start looking for a fix
Apr 01 10:16:46 <Vaizki> do you have a console serial cable? :)
Apr 01 10:17:44 <Dan2> no unfortunately
Apr 01 10:18:02 <Dan2> not yet at least.... ive been thinking about it so maybe i should get one sooner rather than later...
Apr 01 10:59:30 <c10ud> Dan2, try "shutdown -h now" and "shutdown -r now"
Apr 01 11:00:06 <pablognu> hi to all, i have a problem with pinctrl
Apr 01 11:00:26 <pablognu> i have to dtbo files to enable uart1 and uart5 with rts and cts
Apr 01 11:00:43 <pablognu> the pinctrl works only for the first dtbo loaded
Apr 01 11:00:50 <pablognu> anyone can helpme?
Apr 01 11:01:24 <Dan2> c10ud: i have tried those before with the same result... just trying again
Apr 01 11:10:06 <pablognu> onyone?
Apr 01 12:40:45 <av500> https://www.indiegogo.com/projects/lcd-touchscreen-cape-for-beaglebone
Apr 01 14:47:28 <voice_shen> hi all
Apr 01 14:47:45 <voice_shen> any one know the issue
Apr 01 14:47:47 <voice_shen> U-Boot SPL 2011.09-00000-g518a597 (Apr 11 2012 - 16:55:25)
Apr 01 14:47:47 <voice_shen> Texas Instruments Revision detection unimplemented
Apr 01 14:47:47 <voice_shen> Incorrect magic number in EEPROM
Apr 01 14:47:47 <voice_shen> read_eeprom() failure
Apr 01 14:47:47 <voice_shen> : 8388648,
Apr 01 14:48:00 <voice_shen> and don't boot u-boot.img
Apr 01 14:48:02 <av500> yes
Apr 01 14:48:07 <av500> the issue is 2011
Apr 01 14:48:13 <av500> its 2014 now
Apr 01 14:48:22 <av500> please update your SW
Apr 01 14:48:28 <av500> nobody will support 3ys old stuff
Apr 01 14:48:41 <voice_shen> how to update it
Apr 01 14:48:47 <dwery> will you dare to tell that Windows XP can't be used anymore? :D
Apr 01 14:49:09 <dwery> voice_shen: http://beagleboard.org/latest-images
Apr 01 14:49:25 <voice_shen> can I build from source code?
Apr 01 14:49:35 <voice_shen> I try u-boot mainline, failed to boot
Apr 01 14:49:36 <dwery> voice_shen: I strongly suggest you don't
Apr 01 14:50:05 <av500> mainline is fine
Apr 01 14:50:13 <av500> what board?
Apr 01 14:50:57 <voice_shen> however, I failed
Apr 01 14:51:10 <av500> what board?
Apr 01 14:51:31 <voice_shen> for u-boot, I use am335x_evm to configure it and copy MLO and u-boot.img
Apr 01 14:51:45 <voice_shen> BBW
Apr 01 14:51:51 <av500> btw, 2011 is way before the BBB even existed....
Apr 01 14:51:56 <voice_shen> revision A6a
Apr 01 14:52:22 <voice_shen>  downloading lastest-images too slow on my side
Apr 01 14:57:12 <guillaume__> Hello everybody
Apr 01 14:59:01 <guillaume__> I'm looking for some information for hours.. maybe you know: how to partition SD card for beaglebone black? is geometry very important?
Apr 01 14:59:49 <voice_shen> av500: it is BBW (beaglebone) while not BBB
Apr 01 15:01:03 <av500> geometry does not matter
Apr 01 15:01:13 <av500> FAT partition, marked "active"
Apr 01 15:03:22 <voice_shen> av500: one question, if the EEPROM is really broken
Apr 01 15:03:26 <guillaume__> thanks, this is what I did
Apr 01 15:03:28 <voice_shen> how can I repair it?
Apr 01 15:03:36 <av500> its not broken
Apr 01 15:03:49 <av500> and it can be flashed
Apr 01 15:04:06 <av500> can you please try mainline uboot first
Apr 01 15:04:20 <voice_shen> I try mainline u-boot
Apr 01 15:04:32 <voice_shen> U-Boot SPL 2014.04-rc3 (Apr 01 2014 - 22:56:04)
Apr 01 15:04:36 <av500> good
Apr 01 15:04:40 <voice_shen> it repeat to show up this line
Apr 01 15:04:40 <av500> pastebin the log
Apr 01 15:04:45 <av500> hmm
Apr 01 15:04:48 <av500> Tartarus: ^^^^^^^^^^^^^
Apr 01 15:04:56 <voice_shen> no more log except this line
Apr 01 15:05:19 <Tartarus> Interesting
Apr 01 15:05:25 <Tartarus> meeting now, I'll fire up my BBW again shortly
Apr 01 15:07:46 <Tartarus> OK, had a sec in the meeting, works on mine
Apr 01 15:08:38 <Tartarus> http://pastebin.com/qVZe3yKV
Apr 01 15:13:24 <voice_shen> with debug info
Apr 01 15:13:25 <voice_shen> U-Boot SPL 2014.04-rc3-dirty (Apr 01 2014 - 23:10:35)
Apr 01 15:13:26 <voice_shen> Enable clock domain - 44e0000c
Apr 01 15:13:26 <voice_shen> Enable clock domain - 44e00008
Apr 01 15:13:26 <voice_shen> Enable clock domain - 44e00004
Apr 01 15:13:26 <voice_shen> Enable clock domain - 44e00000
Apr 01 15:13:28 <voice_shen> Enable clock domain - 44e00400
Apr 01 15:13:30 <voice_shen> Enable clock domain - 44e000d0
Apr 01 15:13:32 <voice_shen> Enable clock domain - 44e00804
Apr 01 15:13:34 <voice_shen> Enable clock module - 44e000e0
Apr 01 15:13:36 <voice_shen> Enable clock module - 44e00060
Apr 01 15:13:38 <voice_shen> Enable clock module - 44e00064
Apr 01 15:13:40 <voice_shen> Enable clock module - 44e0040c
Apr 01 15:13:42 <voice_shen> Enable clock module - 44e000dc
Apr 01 15:13:43 <ogra_> pastebin !!!
Apr 01 15:13:44 <voice_shen> Enable clock module - 44e00120
Apr 01 15:13:46 <voice_shen> Enable clock module - 44e00408
Apr 01 15:13:48 <voice_shen> Enable clock module - 44e00404
Apr 01 15:13:50 <voice_shen> Enable clock module - 44e00080
Apr 01 15:13:52 <voice_shen> Enable clock module - 44e00030
Apr 01 15:13:56 <voice_shen> Enable clock module - 44e00040
Apr 01 15:13:58 <voice_shen> Enable clock module - 44e0003c
Apr 01 15:14:00 <voice_shen> Enable clock module - 44e000f4
Apr 01 15:14:02 <voice_shen> Enable clock module - 44e004b8
Apr 01 15:14:04 <voice_shen> Enable clock module - 44e000ac
Apr 01 15:14:06 <voice_shen> Enable clock module - 44e000b0
Apr 01 15:14:08 <voice_shen> Enable clock module - 44e000b4
Apr 01 15:14:10 <voice_shen> Enable clock module - 44e00048
Apr 01 15:14:12 <voice_shen> Enable clock module - 44e00014
Apr 01 15:14:14 <voice_shen> Enable clock module - 44e0004c
Apr 01 15:14:17 <voice_shen> Enable clock module - 44e00800
Apr 01 15:14:18 <voice_shen> Enable clock module - 44e0001c
Apr 01 15:14:20 <voice_shen> Enable clock module - 44e000d0
Apr 01 15:14:22 <voice_shen> Enable clock module - 44e00028
Apr 01 15:14:26 <thow> ?
Apr 01 15:14:27 <voice_shen> >>spl:board_init_r()
Apr 01 15:14:28 <voice_shen> sorry, can not access pastebin
Apr 01 15:14:36 <ogra_> ?
Apr 01 15:14:42 <ogra_> you can access IRC
Apr 01 15:15:05 <Tartarus> voice_shen, So, if you have a BBW and the stock code was throwing up a "EEPROM is incorrect", then you need to get someone to help you hack u-boot up to not check the EEPROM and just know it's a beaglebone white
Apr 01 15:15:14 <Tartarus> Then write the correct contents into the EEPROM
Apr 01 15:15:36 <Tartarus> (I thought the EEPROM was write-projtected on BBW?  Or am I mis-recalling things?)
Apr 01 15:16:10 <voice_shen> Tartarus: thanks, I will try
Apr 01 15:17:17 <dwery> ogra_: he's from China, not everything is accessible there
Apr 01 15:18:54 <voice_shen> :(
Apr 01 15:24:48 <Ventura> Someone has experience with device tree configuration???
Apr 01 15:27:59 <dwery> (everyone hides)
Apr 01 15:28:41 <dwery> Ventura: what's the matter?
Apr 01 15:29:30 <suihkulokki> Ventura: http://learn.adafruit.com/introduction-to-the-beaglebone-black-device-tree/overview
Apr 01 15:29:38 <Ventura> Hi dwery, I am configuring an interrupt using device tree but the spi is mapping the gpio pin 47 to 63.
Apr 01 15:30:17 <Ventura> When I use the gpio_to_irq I can force the drive to work but I don't think that this is correct.
Apr 01 15:30:41 <Ventura> Let me copy my simple dt node. hang on
Apr 01 15:31:14 <Ventura> &spi1 {         pinctrl-names = "default";         pinctrl-0 = <&spi1_pins>;         status = "okay";          spidev2: spi@0 {                 compatible = "microchip,enc28j60";                 reg = <0>;                 spi-max-frequency = <24000000>;                 interrupts = <47>;         }; };
Apr 01 15:31:18 <Ventura> Ohh
Apr 01 15:31:33 <Ventura> I don't know how to do that here
Apr 01 15:33:09 <Ventura> The drive is loaded but the only problem is that the SPI has no idea that my interrupt is a gpio pin. Tha is what I guess.
Apr 01 15:33:23 <dwery> I guess the driver is device tree ready
Apr 01 15:33:24 <dwery> ?
Apr 01 15:34:34 <Ventura> Yes, but the SPI. The ethernet drive I had to make changes. But I think that I shouldn't need to make any change. Is the SPI that is handling the information from the device tree.
Apr 01 15:35:14 <Ventura> The spi is reading the interrupt number but it's mapping without consider the GPIO
Apr 01 15:35:28 <dwery> SPI has no interrupt on his own as far as I can remember.
Apr 01 15:35:43 <dwery> In my driver I had to do it in code. Let me check
Apr 01 15:35:57 <dwery> I used:
Apr 01 15:36:12 <Ventura> Yes. you are right. But it's reading the interrupt tag from the device.
Apr 01 15:36:20 <dwery> interrupts and interrupt-parent in the device tree
Apr 01 15:36:25 <dwery> but I also added a custom field
Apr 01 15:36:54 <dwery> with <&gpio2 17 0>;
Apr 01 15:37:03 <dwery> the driver would use that field to request the irq
Apr 01 15:37:04 <Ventura> I was reading one post that the guy include other tags but I don't know...
Apr 01 15:37:26 <dwery> Ventura: http://pastebin.com/wMa9wvbk
Apr 01 15:37:59 <Ventura> I like that... In my case I am using the GPIO1_15. How should this tag? I need falling edge ...
Apr 01 15:38:36 <dwery> your parent wqould be gpio2
Apr 01 15:38:57 <dwery> <&gpio2 15 0>;
Apr 01 15:39:11 <dwery> I haven't checked for the edge
Apr 01 15:39:33 <Ventura> I think that the third parameter should ve 2
Apr 01 15:39:46 <dwery> maybe a better way would be to read interrupt-parent and interrupts
Apr 01 15:40:37 <dwery> I did it quite a while ago
Apr 01 15:40:47 <dwery> can't remember the reasoning there
Apr 01 15:40:55 <Ventura> OK. I have to include three tags: interrupt-parent, irq-gpio and interrupts. Is that right?
Apr 01 15:41:13 <dwery> yes. the second one being your custom one
Apr 01 15:41:41 <Ventura> What you mean "custom one"?
Apr 01 15:41:42 <dwery> call it enc28j60,irq_gpios maybe
Apr 01 15:42:09 <dwery> don't forget to send your patch upstream ;)
Apr 01 15:42:36 <Ventura> Yes. Sure but I don't want to patch if I don't have to.
Apr 01 15:43:04 <Ventura> I think that just patching the DT is enough
Apr 01 15:43:44 <dwery> I'm not sure if enc28j60 supports DT
Apr 01 15:44:14 <Ventura> Let me review one point: How do you know gpio1_15 is <&gpio2 17 0>???
Apr 01 15:44:33 <dwery> it's  <&gpio2 15 0>;
Apr 01 15:44:37 <dwery> bank + 1
Apr 01 15:44:42 <Ventura> OK.
Apr 01 15:45:51 <Ventura> About the enc28j60, it's not dt capable but what I figured out was it doesn't need to be. The spi drive is one that must be DT capable.
Apr 01 15:46:16 <dwery> isn't the irq related to the enc28j60?
Apr 01 15:46:39 <Ventura> Yes but is the spi that pass the irq to the drive.
Apr 01 15:47:04 <Ventura> At the time of device probe...
Apr 01 15:47:12 <dwery> uhm..
Apr 01 15:47:33 <dwery> how?
Apr 01 15:47:41 <Ventura> That is the reason I am strugling to not apply patch to enc28j60.
Apr 01 15:48:03 <dwery> ah..they use spi->irq
Apr 01 15:48:12 <Ventura> YES!
Apr 01 15:48:37 <Ventura> You got it.
Apr 01 15:48:50 <dwery> then adding gpio support to the spi driver should work
Apr 01 15:48:58 <dwery> strange it's not there already
Apr 01 15:49:11 <Ventura> But the SPI has already support... That is the point...
Apr 01 15:50:06 <Ventura> Thespi is reading my device tree, it's loading the enc28j60.ko and even reading the inetrrupt pin...
Apr 01 15:50:13 <dwery> let me check
Apr 01 15:50:21 <dwery> kernel 3.8.13?
Apr 01 15:50:30 <Ventura> I am using 3.13.6
Apr 01 15:50:49 <Ventura> But I think it works also with 3.8
Apr 01 15:54:45 <dwery> I guess you're right, it should support that. I can't remember why I did it that way
Apr 01 15:55:45 <dwery> maybe it's just missing the gpio part
Apr 01 15:56:03 <Ventura> what you show me about the configuration is important and I was doing wrong.
Apr 01 15:56:34 <Ventura> interrupt-gpio = <&gpio2 15 0>
Apr 01 15:56:47 <Ventura> interrupts=<15>
Apr 01 15:57:02 <Ventura> interrupt-parent=<&gpio2>
Apr 01 15:57:15 <Ventura> I never tryed that...
Apr 01 15:58:10 <Ventura> Ok dwery, I am going to try that... If I succeed I will post everything about that...
Apr 01 15:58:22 <dwery> Let me know. If they're natively supported I'll modify my driver
Apr 01 15:58:36 <Ventura> I will do.
Apr 01 15:58:44 <Ventura> Thank you.
Apr 01 16:10:27 <guillaume__> hello, do one of you know why I can't save on the card with "saveenv" using u-boot ?
Apr 01 16:10:47 <guillaume__> U-Boot# saveenv
Apr 01 16:10:48 <guillaume__> Saving Environment to NAND...
Apr 01 16:10:48 <guillaume__> Erasing NAND...
Apr 01 16:10:48 <guillaume__> Attempt to erase non block-aligned data
Apr 01 16:11:38 <guillaume__> is it a problem with the BBB sd card?
Apr 01 17:59:59 <hnp> i had my BBB connected with ethernet ans a 5V 1000mA power supply and suddenly BBB went off.wth could be the reason.can any1 help me out?
Apr 01 18:00:39 <prpplague> hnp: depending on what other stuff you are doing 1000mA is probably not enough
Apr 01 18:01:45 <hnp> the power LED just blinks once and then goes off.
Apr 01 18:07:09 <hnp> i m not getting my BBB on.can i go through RMA procedure?its been over 90days i purchased BBB..
Apr 01 18:07:51 <prpplague> hnp: yea, go ahead and try the RMA procedure, i doubt it will be refused
Apr 01 21:20:20 <dogrocket> anyone tried the new debian for bbb.. is it working ok?
Apr 01 21:21:39 <prpplague> dogrocket: yes it is working and is in the final stages of the beta testing
Apr 01 21:22:45 <JFK911> prpplague: is the angstrom build likely to be updated ever again, now that it seems like debian is the fresh thing?
Apr 01 21:22:54 <ds2> debian does  nott work
Apr 01 21:23:32 <JFK911> my policy is to avoid debian so i have not tried it
Apr 01 21:23:41 <prpplague> JFK911: angstrom is actively maintain , not just for beagleboard projects
Apr 01 21:23:51 <JFK911> prpplague: oh ok
Apr 01 21:24:16 <JFK911> so the effort's going to be on debian from now?
Apr 01 21:24:22 <prpplague> JFK911: just the psudeo official distro that will ship on the black will be a debian based build
Apr 01 21:24:32 <JFK911> i might as well try it then
Apr 01 21:24:52 <JFK911> some packages i want havent been in the angstrom build's base
Apr 01 21:25:10 <dogrocket> ok thx prpplague
Apr 01 21:25:27 <prpplague> dogrocket: you can find the info on the mailing list
Apr 01 21:26:08 <dogrocket> prpplague you think the new wifi chip 18xx will be supported for debian also?
Apr 01 21:27:32 <prpplague> dogrocket: TI has not offered any info or road map on working with beagleboard.org to support the WL18xx chipset
Apr 01 21:28:15 <dogrocket> yeah, only thing i see is ti provides source to install in angstrom
Apr 01 21:30:37 <dogrocket> http://processors.wiki.ti.com/index.php/Using_the_WL18xx_Cape_with_BeagleBone_Black
Apr 01 21:53:29 <Wubistick> hey ,anyone here?
Apr 01 21:54:37 <Wubistick> hello?
Apr 01 21:58:16 <deluxe247> Hi guys i am need of desperate help. I am hoping i didnt damage my beaglebone black. I am unable to power my beagle bone black through the wall wart adapter and through the ground vdd pins. it does however boot when connected to usb
Apr 01 21:58:45 <deluxe247> I have only applied 5v to be specific 4.95 volts to the pins. would this have damaged the beaglebone black?
Apr 01 22:06:43 <deluxe247> can anybody help me with this? I am not sure how to check if I damaged it and am unsure what would have caused the issue
Apr 01 22:10:39 <deluxe247> I am unable to power it with a 5v 800ma power supply or through the vdd pins. I am however able to boot it with usb
Apr 01 23:16:30 <myself> aa/win 55
Apr 01 23:49:38 <gg> Hello
Apr 01 23:49:51 <gg> need help on SSH
Apr 01 23:50:08 <gg> my putty is not able to connect to BBB
Apr 01 23:51:38 <gg> I get an error that the Server unexpectedly closed the connection
Apr 01 23:53:28 <gg> I can connect via serial
Apr 01 23:55:01 <gg> what would be the issue?
Apr 02 00:14:25 <deluxe247> I need some help. I need to figure out if I have damaged my beaglebone black as it is able to boot from usb but not through the 5v dc input or through the vdd pin. Is it damaged or is there something I am missing?
Apr 02 00:15:00 <Dan2> did it used to boot with that adaptor?
Apr 02 00:20:41 <deluxe247> yeah it did
Apr 02 00:21:32 <deluxe247> i had it being powered by a dual h bridge module that put out 4.95 volts over the weekend. I started thinking the board was the problem until it powered my arduino and not the beaglebone black
Apr 02 00:57:15 <SpeedEvil> It seems quite likely you reversed it then
Apr 02 01:00:00 <deluxe247> SpeedEvil, if that was the case is the board damaged? I am only able to boot from usb so I am not sure if this is something that could be repaired if that was the case
Apr 02 01:00:23 <SpeedEvil> It would seem likely.
Apr 02 01:00:40 <SpeedEvil> I'm assuming that there is some 5V reverse polarity protection or input circuirty you've killed.
Apr 02 01:00:54 <SpeedEvil> The first is likely easily repairable (if you can solder SMD) - the latter not so much
Apr 02 01:05:29 <deluxe247> i was hoping that wasnt going to be the case
Apr 02 01:06:36 <SpeedEvil> Make a cable to go to the USB port is the easy way
Apr 02 01:06:42 <SpeedEvil> Or buy a new BBB
Apr 02 01:11:44 <deluxe247> I am thinking I am going to replace it. hopefully i can find another revision b available
Apr 02 01:26:19 <prpplague> ahh man! who let behanw in here?
Apr 02 01:26:40 * prpplague points at behanw 
Apr 02 02:31:24 <behanw> prpplague, Don't be like that!
Apr 02 02:31:38 <prpplague> hehe
Apr 02 02:31:54 <behanw> Congrats on the new board!
Apr 02 02:32:02 <prpplague> behanw: thanks a bunch!
Apr 02 02:32:10 <prpplague> behanw: it's been a labor of love
Apr 02 02:32:16 <prpplague> (and heart ache)
Apr 02 02:32:21 <behanw> Of course.
Apr 02 02:32:27 <behanw> They always are
Apr 02 02:32:29 <prpplague> behanw: should have some for ELC
Apr 02 02:32:34 <behanw> Nice!
Apr 02 02:32:46 <behanw> I'm so looking forward to ELC
**** ENDING LOGGING AT Wed Apr 02 02:59:59 2014