**** BEGIN LOGGING AT Sun Jul 12 02:59:58 2015 Jul 12 04:03:49 hi all Jul 12 04:18:37 ahoy, i've used the sd card + debian flasher image to upgrade my bbb to debian-based image Jul 12 04:18:55 usb network no longer works, does it dhcp or something if i plug it into wired network? Jul 12 04:22:00 chrismsnz .. dhcp works on the ethernet port yes Jul 12 04:22:26 usb'net should work .. but it can be a bit choos Jul 12 04:22:31 choosey Jul 12 04:24:26 my BB board can't detect USB 3G Jul 12 04:24:54 type lsusb it show Jul 12 04:24:56 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Jul 12 04:51:47 veremit: on the debian image? or just the angstrom image? to be clear, usb net worked on angstrom but not on the new debian img :\ Jul 12 04:52:25 chrismsnz .. either/or :) usbnet does work on the debian images .. Jul 12 04:52:52 hmm perhaps something is not right then Jul 12 04:53:37 http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBB_Rev_C_.284GB_eMMC.29 << was the image i installed - is that correct? Jul 12 04:54:51 http://beagleboard.org/latest-images Jul 12 04:55:34 ah they've done abit of a tidy-up Jul 12 04:55:35 ok, is there a flasher version of that image? Jul 12 04:56:21 http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2015-07-06 Jul 12 04:56:33 looks like the latest release Jul 12 04:56:54 right that's the one i used Jul 12 04:59:35 ok I gotta sleep .. 6am just turnin .. niters! Jul 12 06:52:49 hii..i am able to ssh into BBB from my computer Jul 12 06:53:12 by using browser i am not able access the ip address http://192.168.7.2/ Jul 12 06:53:25 any help plss ?? Jul 12 06:55:11 does USB cable matters ?? as I have lost my BBB cable and using some other USB !! Jul 12 07:00:51 not able to access from Chrome..but it worked with firefox... Jul 12 07:01:05 can anyone tell me that why this is so ?? Jul 12 07:09:07 no it shouldn't matter which cable you use Jul 12 07:09:28 the ssh connection you are establishing is also to 192.168.7.2? Jul 12 07:09:59 tbr: ssh is working fine Jul 12 07:10:28 that is not what I asked, isn't it? Jul 12 07:10:31 i am trying to do this http://robotic-controls.com/learn/beaglebone/beaglebone-internet-over-usb-only Jul 12 07:10:42 access internet over USB Jul 12 07:12:07 I'll ask again. Which IP address are you connecting to over SSH? Jul 12 07:12:59 tbr: i am using this command "ssh root@beaglebone.local" Jul 12 07:13:36 what happens if you access http://beaglebone.local ? Jul 12 07:16:49 tbr: sry got disconnected :( Jul 12 07:17:02 when i access this http://beaglebone.local/ it get error Jul 12 07:17:47 as you said, that you are trying to change routing, I'm going to guess that you have messed things up Jul 12 07:18:05 :( Jul 12 07:18:28 i have restarted my BBB also.. Jul 12 07:18:33 will that not work ?? Jul 12 07:20:08 my guess is that you messed up on your host machine. did you just copy paste the commands or did you adjust them to suit your system? Jul 12 07:21:29 i just changed the eth3 to eth1 as on my machine eth1 is the BeagleBone USB connection.. Jul 12 07:22:25 instead of this no change Jul 12 07:25:03 are you sure it's not usb0? Jul 12 07:27:53 on host it is eth1: inet addr is 192.168.7.1 and on BBB it is usb0: inet addr is 192.168.7.2 Jul 12 07:28:29 are you able to ping 192.168.7.2 from your PC? Jul 12 07:30:00 yes..i am able to ping 192.168.7.2 from my pc Jul 12 07:30:21 does proxy setting has any role to play in it ?? Jul 12 07:30:46 because i am in clg and using internet via proxy Jul 12 07:31:51 duuuuuh Jul 12 07:32:03 yes, you MUST exclude 192.168.7.2 from proxying Jul 12 07:33:42 ohh...i'll put this in "no proxy for" section Jul 12 08:39:09 I would love to have something similiar on a BBB https://www.raspberrypi.org/piphone-home-made-raspberry-pi-smartphone/ Jul 12 08:39:35 I think the phone module will work the same in the BBB right? just some coding... Jul 12 08:41:36 <_av500_> nyo: PROBABLY Jul 12 08:41:38 <_av500_> OOPS Jul 12 08:41:42 <_av500_> oops Jul 12 11:10:32 Hello Jul 12 11:11:16 Hi, My name is Sachin. Jul 12 11:11:35 I have a devkit8000 board Jul 12 11:11:44 I understand its not beagle Jul 12 11:12:45 I would like to modify the default bootloader and the linux kernel. Jul 12 11:13:34 Current version of kernel provided for the board is 2.6.28 Jul 12 11:14:20 for upgrading it to 4.x version what changes I may have to do? I don't have kernel porting experience. Jul 12 11:26:52 sachin .. if you come in during the week .. talk to rcn-ee .. he might be able to shed some light on it. You'll need to difference the devkit sdk source tree for 2.6 with the mainline kernel snapshot, then 'copy' those changes to the current mainline tree. It won't be a trivial task, as much will have changed in mainline. Jul 12 11:28:14 hmm Jul 12 11:28:28 I understand what you are saying... Jul 12 11:29:10 I will check those diffs.... Jul 12 11:29:25 Thanks veremit.... Jul 12 11:29:28 sachin .. althouhg .. if the 3530 is used on the original beagleboard .. you got a huge headstart .. as there should be mainline images around .. Jul 12 11:30:08 currently I could see a OMAP2+ defconfig... I may try to just build a kernel using it and share the result :) Jul 12 11:30:17 sachin .. have a forage around https://eewiki.net/display/linuxonarm/BeagleBoard .. that's RN's site (rn = rcn-ee) :) Jul 12 11:30:19 I don't know if that will work or not Jul 12 11:30:54 that't great ... let me go through it Jul 13 01:04:54 Hello everyone. Jul 13 01:06:04 newbie with a BBB and trying to update the software. I've been waiting for the lights to go solid now for about 30-40 minutes. When the lights go solid, do they stay that way or do they go back to flashing after they have stayed solid for a short period of time? Jul 13 01:15:14 When updating the software will the LED's stay solid indefinitely until it is powered off, or will it go back to some "normal" activity flashing? Jul 13 01:18:39 Anyone? Jul 13 01:19:57 Ugh! Jul 13 01:21:20 When updating the software will the LED's stay solid indefinitely until it is powered off, or will it go back to some "normal" activity flashing? Jul 13 01:24:43 When updating the software will the LED's stay solid indefinitely until it is powered off, or will it go back to some "normal" activity flashing? Jul 13 01:36:41 I've never used the sd-flasher but I'd expect the latter Jul 13 01:38:48 in general I'd expect only the eMMC led (usr1) or the uSD led (usr3) to be on continuously, depending on which is the bottleneck during the transfer Jul 13 01:39:22 but like I said, I've never used the uSD-flasher so I don't know if it uses the leds in some non-standard way Jul 13 01:39:53 and repeating your question is not going to get you answers sooner, it just makes you more annoying Jul 13 01:41:23 (hanging around after asking a question is however highly recommended) Jul 13 01:42:29 i just used the flasher, the LED's strobe (in a knight rider KITT pattern) while flashing Jul 13 01:42:37 then stay on solid when its done Jul 13 01:42:52 if you're getting the usual heartbeat/activity LED's something could be up Jul 13 01:44:42 ah Jul 13 01:45:08 JB_: so apparently it uses them in a non-standard fashion and indeed they're supposed to stay solid indefinitely when done Jul 13 01:46:11 chrismsnz: a bit annoying that the flasher uses them that way Jul 13 01:46:47 * zmatt prefers flashing via usb anyway... at least until he finds a moment to set up network booting/flashing Jul 13 01:48:03 AWESOME! Jul 13 01:48:10 That is the answer I'm looking for. Jul 13 01:48:23 It seems to go for longer than 40+ min. Jul 13 01:48:57 I'm using a 64GB msd card and not sure if that makes any difference. Jul 13 01:50:41 Sorry zmatt for being annoying. Wasn't trying to be. Jul 13 01:52:55 chrismsnz, thank you also for responding. I'll let it run until they go solid. If it runs longer than 1 hour I will assume there is a problem. Jul 13 01:56:14 JB_: is it doing the "scanning" animation across the LED's? Jul 13 01:58:39 chrismsnz - USR2 is not bright but constant, USR0 is constantly flashing. Jul 13 01:59:14 USR1 and USR3 don't flash hardly at all. Jul 13 01:59:35 that's a normal booted system running idly Jul 13 01:59:46 assuming the USR0 flashing is periodic (heartbeat) Jul 13 01:59:53 Yes Jul 13 02:00:06 that's just a booted system, nothing going on Jul 13 02:00:12 or well Jul 13 02:00:16 usr2 is how much is going on Jul 13 02:00:18 (cpu activity) Jul 13 02:00:42 JB_: that's not what it does when its flashing Jul 13 02:01:07 So I must not be flashing at all. Jul 13 02:03:16 This is the image file I downloaded. Debian (BeagleBone, BeagleBone Black - 4GB SD) 2015-03-01 Jul 13 02:03:35 if it doesn't say "flasher" it's not a flasher Jul 13 02:03:54 Ok. I was thinking that too. I hate being new at stuff. Jul 13 02:06:11 if it's any consolation, I'm definitely not "new at stuff" and regularly get confused too ;-) Jul 13 02:06:43 Thanks zmatt! :-) That is comforting! Jul 13 02:06:46 (trying to get an overview of available kernels and git repositories with build scripts is an excellent way) Jul 13 02:06:58 I just downloaded this "flasher". Jul 13 02:07:01 BBB-eMMC-flasher-debian-7.8-lxde-armhf-2015-03-01-2gb.img.xz Jul 13 02:07:56 there's a slightly newer one Jul 13 02:08:05 2015-03-08 Jul 13 02:09:13 though I usually start with a console image and just install the stuff I want (after upgrading to stretch first) Jul 13 02:09:29 Here is the link I am using - http://elinux.org/Beagleboard:BeagleBoneBlack_Debian Jul 13 02:09:42 What link did you find the 2015-03-08? Jul 13 02:10:28 ah wait there are much newer ones Jul 13 02:10:57 argh, it's annoying there's rcn-ee.net and .com, and apparently he switched from using the .net one to the .com one a few months ago Jul 13 02:11:02 but the old one continues to exist Jul 13 02:11:18 latest is actually 2015-07-06 Jul 13 02:11:24 https://rcn-ee.com/rootfs/bb.org/testing/ Jul 13 02:12:14 not all dirs contains all types of images, so sometimes you need to look around if you want a particular image Jul 13 02:12:33 lol Jul 13 02:12:40 e.g. 2015-07-06 doesn't have a machinekit image, but 2015-07-05 does Jul 13 02:12:40 Man this is confusing! :-) Jul 13 02:13:02 zmatt - this one? BBB-eMMC-flasher-debian-7.8-console-armhf-2015-07-06-2gb.img.xz Jul 13 02:14:39 eh, probably I guess... like I said, I never use the flashers... no idea what the other flasher in that dir is Jul 13 02:15:00 note that the console images are _really_ stripped-down Jul 13 02:15:29 So if I may ask another dumb question, if you never use the flashers, do you ever upgrade the bone? Jul 13 02:16:50 so if you use a console image, you'll need to be comfortable starting out with such a barebone system and installing the packages that turn your BBB into a comfortable system Jul 13 02:17:24 03:46 * zmatt prefers flashing via usb anyway... at least until he finds a moment to set up network booting/flashing Jul 13 02:17:51 upgrades don't require reflashing though Jul 13 02:18:04 So there is an easier way? Jul 13 02:18:08 via USB? Jul 13 02:18:17 dunno if it's "easier" Jul 13 02:18:23 LOL!!! Jul 13 02:19:12 but it works, and I only need to do it once per beagle to replace all the crap that's on it with a clean console image, after that I just upgrade via APT Jul 13 02:20:06 What is your method and what file do you use to upgrade? Jul 13 02:20:49 the usb flasher (BBBlfs) is a bit icky though, it fails to work entirely on some hosts, the script is very iffy, makes too many assumptions and too few checks, and after inspecting the source code of the usb_flasher tool itself I needed eye-bleach Jul 13 02:21:09 but when it does work, it's a quick and easy way to reflash (or repair) a beaglebone Jul 13 02:21:22 basically makes the eMMC appear like an USB stick Jul 13 02:21:30 Ok. Jul 13 02:21:55 The usb_flasher tool is in the BB tools? Jul 13 02:22:06 https://github.com/ungureanuvladvictor/BBBlfs Jul 13 02:22:46 the "usb_flasher" tool it creates is actually just responsible for making the BBB appear as an usb mass storage device Jul 13 02:23:28 the project also includes scripts which then proceed to reflash the BBB, but I avoid those Jul 13 02:24:35 in partcular, using bin/flash_script.sh with any recent debian image will result in an unbootable system Jul 13 02:24:36 Ok. Reading them now! Jul 13 02:24:56 since it assumes the image has two partitions: a boot partition and the main ext4 partition Jul 13 02:25:08 whereas current images have no boot partition Jul 13 02:25:25 Ok. Jul 13 02:25:25 but the partition number "2" is hardcoded all over the script Jul 13 02:26:02 Ok. Good to know. Jul 13 02:26:18 Is there a single package that updates everything on the bone? Jul 13 02:26:48 also, I've heard rcn-ee claim reflashing via USB is slower than using an SD flasher Jul 13 02:27:20 I'm ok using the sd flasher but wanted to make sure I use the correct file. Jul 13 02:27:22 eh, well everything that's part of a debian package can be updated via APT obviously Jul 13 02:27:30 Ok. Jul 13 02:28:12 I'm also assuming the debian "blank" is a bare bones image? Jul 13 02:28:27 though if I understand correctly, quite a bit of the default installation (e.g. the web gui stuff) isn't part of any debian package Jul 13 02:29:07 (I reflashed with a console image in part to get rid of all such crap) Jul 13 02:29:35 I honestly have no idea what the difference is between the -blank- flasher and the other one Jul 13 02:30:41 Glad I bought two of these! Jul 13 02:30:43 LOL! Jul 13 02:30:51 well you can't really fry them Jul 13 02:31:02 by flashing a wrong image at least Jul 13 02:31:33 you can always reflash a different image if the first one doesn't work out Jul 13 02:33:44 (even if eMMC is completely wiped you can still boot from SD card: the initial bootloader responsible for loading the next stage from eMMC or SD card is baked into the processor and can't be corrupted in any way) Jul 13 02:35:14 the ROM bootloader is actually quite elaborate and can also boot via USB (the usb-flasher tool I referenced uses that) or Ethernet (BOOTP + TFTP) Jul 13 02:41:15 zmatt! it's working! Jul 13 02:42:04 You da man! Jul 13 02:50:56 o/ **** ENDING LOGGING AT Mon Jul 13 02:59:59 2015