**** BEGIN LOGGING AT Sat Nov 07 02:59:59 2015 Nov 07 03:40:21 I got a shipment if Beaglebone Black Rev C boards a couple week ago that are preloaded with an image from april 23 2015 (3.8.13-bone47). After adding Robert C. Nelson's repos to my sources.list and associated keys, I find that I can't seem to switch kernels. I attempt like apt-get install linux-image-3.8.13-bone79 and the package installs and I reboot just fine, but when it comes back up... Nov 07 03:40:23 ...it's still bone47. I've tried a few things to hack on this process but I'm still a bit puzzled that it is failing? I don't want to be a nuisance but does anyone have any ideas on why this might be the case? Nov 07 03:42:50 I have tried later images (bone72 from August) and I'm able to jump around to different kernels just fine. I'm asking mostly out of curiosity and wanting to understand, it's not stopping me from getting anything done. Nov 07 04:04:59 GrumpeiYokoi .. you may need to check your uEnv.txt config .. check that the uname_r is getting set right each time. Nov 07 04:05:18 Rob himself will be back Monday here Nov 07 04:06:51 veremit: Thanks, I'll double check that. I looked in there but nothing obvious jumped out at me. The initrd.image in /boot/uboot was updated correctly, but zImage was still from the earlier date, I was thinking that was the reason. I don't have a good grasp of how all this fits together yet. Nov 07 04:07:17 I might have manged the name of that file, but I think you know what I mean. Don't have the device in front of me at the moment. Nov 07 04:07:24 *mangled Nov 07 04:18:29 np Nov 07 05:29:25 So Apocx Nov 07 05:29:31 How's virginia? Nov 07 05:30:26 must be fun there Nov 07 05:30:42 anyone here? Nov 07 06:00:26 GrumpeiYokoi: are those from element14? they put their own spin on images and are sometimes weird. Nov 07 06:00:34 GrumpeiYokoi: I'd reflash the boards Nov 07 06:01:18 tbr: From adafruit which I believe sources from element14, so yeah most likely Nov 07 06:02:03 tbr: I have already done so for two of the boards, I was more trying to understand at a reductive level what was going wrong. If you think it's a lost cause I'll just forget about it ;) Nov 07 06:02:07 you can tell them apart. the e14 boards don't have the little beagle logo IIRC Nov 07 06:02:50 grab a nice fresh image from http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2015-11-03 and burn to a uSD, hold button whilst applying power to boot :) Nov 07 06:03:25 The last batch we got (Rev B) actually had element14 silkscreened on, so these probably do as well. Nov 07 06:04:09 Well that's new, thanks vermit Nov 07 06:04:23 I'm not sure where e14 would publish their image info/sources Nov 07 06:04:53 but we've seen people run into minor weirdness with those in the past Nov 07 06:05:12 tbr .. http://www.element14.com/community/docs/DOC-67138/l/element14-beaglebone-black-software-image-update-instruction Nov 07 06:05:26 Yeah I did see someone else on a mailing list that had this problem but they never responded to RCN's request for additional info Nov 07 06:06:12 veremit: that doesn't cover the e14 factory image and modifications though Nov 07 06:06:20 newp Nov 07 06:06:33 I assume those don't exist either .. lol Nov 07 06:06:40 possible Nov 07 06:06:45 Very likely, lol Nov 07 06:06:54 in any case .. try those images to start with Nov 07 06:06:55 (that they don't exist) Nov 07 06:07:19 I haven't had any problems with the more recent images, just to reiterate. The ones from beagleboard.org Nov 07 06:07:28 So no complaints there Nov 07 06:08:10 Well, the main reason I was even trying to switch kernels was to address a USB hotplug issue. I've seen a spectrum of compatibility with different kernels. 4.2.x seems to work pretty well so far Nov 07 06:08:15 I managed to snag a genuine one when RS (uk) had stock :) Nov 07 06:08:28 oh the beloved musb issues :) good luck! Nov 07 06:08:38 Yeah, stock seems to be feast or famine for Beaglebones Nov 07 06:08:48 hotplug is patchy at best Nov 07 06:08:51 This time we got ours in like 2 days. Last time it was a 3 month lead time. Nov 07 06:08:56 musb just wasn't designed for it Nov 07 06:09:17 My company's software has a requirement that a device disconnects temporarily (cypress fx2 based architecture) Nov 07 06:09:21 CCo just don't have the production volume .. ele14 are probably dwarfing them something stupid lol Nov 07 06:09:57 What I found with 3.8.13-bone72 was that if I was on a hub, and I was the only device attached, I couldn't get the device to be seen again after it tries to reenumerate. Nov 07 06:09:59 As long as they have some quality control (ele14) it should be ok Nov 07 06:10:19 It turned out that if I ran lsusb -v it would refresh the hub, but that was a pain so I started looking at later kernels Nov 07 06:10:43 GrumpeiYokoi .. we found if you have something permanently connected to the BBB at boot .. via hub is fine, you're ok .. but if you lose 'eveything' then usb is good as dead Nov 07 06:11:03 our carrier board had an ftdi chained on the hub permanently wired Nov 07 06:11:11 Seems to me to depend on the kernel and the hub somewhat Nov 07 06:11:15 was fine then. Nov 07 06:11:19 My boss insisted we get this one specific Belkin hub Nov 07 06:11:21 I was skeptical Nov 07 06:11:27 But it did seem to make everything work magically well Nov 07 06:11:38 the hub shouldn't matter, because its a generic driver & interface Nov 07 06:11:43 And it even conferred benefits on subsuequent hubs that were plugged in during the same uptime Nov 07 06:11:50 That's the thing, it made no sense to me either Nov 07 06:11:56 unless there's some better electrical design Nov 07 06:11:56 But it was extremely repeatable *shrug* Nov 07 06:12:11 yea you never know lol Nov 07 06:12:11 Most hubs presented with the problem though Nov 07 06:12:15 It surely was an outlier Nov 07 06:12:39 He got the hub model name off a completely unrelated list for the Asterisk operating system Nov 07 06:12:56 Also on BBB Nov 07 06:13:34 It's not a humongous issue because we can preload our devices with firmware anyway, we just usually don't Nov 07 06:14:12 And the customer runs with more than one device on their hubs at all times. I was just being my typical pedantic self Nov 07 06:14:25 Was sifting through kernel code for musb trying to figure out what end was up Nov 07 06:14:29 yeah don't make extra work lol :D Nov 07 06:14:39 Can't help it sometimes *sigh* Nov 07 06:14:42 unless you want to re-write musb .. in which case .. you'll have alot of fans :D Nov 07 06:15:12 Do you know where the name musb comes from? Nov 07 06:15:23 I couldn't quite get a definite etymology of that abbreviation Nov 07 06:15:29 I heard it was an old nokia ip core Nov 07 06:15:33 or some-such Nov 07 06:15:46 hmm.... ok then Nov 07 06:17:43 http://processors.wiki.ti.com/index.php/AM335x_USB_Driver%27s_Guide Nov 07 06:19:15 *snip* Thanks Nov 07 06:20:21 I was somewhat worried when I kept seeing OTG when I started digging in to musb Nov 07 06:20:36 I guess it's not that big of a deal though Nov 07 06:21:27 At least it has high speed transmit capability. We worked with an embedded board years ago that advertised that it was USB 2.0 compliant but buried in their fine print, it only operated at full speed at most Nov 07 06:21:45 heh Nov 07 06:21:59 We didn't realize that for quite a while into the project and had to really retool Nov 07 06:24:38 yeah hence the heavy disclaimers about bbb use :D Nov 07 06:25:03 Well, in this case our customer dragged us into using it Nov 07 06:25:18 Our biggest one. We didn't have much choice in the matter. Nov 07 06:25:29 hmm Nov 07 06:25:39 On the whole I'd say I like the BBB though, so it's not really a problem. Nov 07 06:25:59 yea the bbb is cool .. just gotta work around its idiosyncrasies Nov 07 06:26:19 and idiosynchronies Nov 07 06:26:20 or something Nov 07 06:53:19 the m is Mentor Nov 07 06:54:39 afaik Nov 07 06:54:44 For a while I was convinced it stood for 'mystery' :/. But yeah it does mention it in the link our esteemed collegue mentioned earlier: http://processors.wiki.ti.com/index.php/AM335x_USB_Driver's_Guide#MUSB_Controller_Overview Nov 07 06:54:55 *colleague Nov 07 06:55:15 Sorry about the spelling slop. I'm off my game today, sheesh. Nov 07 07:16:27 nom, pancakes Nov 07 07:17:01 * zmatt growls at internet radio station... *play* your music, don't *talk* about your music Nov 07 10:53:12 join Nov 07 10:53:22 excuse me Nov 07 10:54:00 can someone tell me? Nov 07 10:54:17 i cannot ssh into my BBB Nov 07 10:54:35 via usb port terminal linux Nov 07 10:54:49 how can i fix this problem?? Nov 07 10:54:51 thanks Nov 07 11:00:52 riz: have you changed the sshd config to allow root to ssh? Nov 07 11:01:29 note yet, Nov 07 11:01:37 i am begineer in BBB Nov 07 11:01:51 how can it work for me? Nov 07 11:01:59 can u tell me ? Nov 07 11:02:00 I use FreeBSD with all my BBBs. I had to enable root ssh Nov 07 11:02:19 how bout angstrom? Nov 07 11:02:27 google search for how to allow root to ssh for whatever distribution of linux you are using. Nov 07 11:02:59 thank you very much, its helpful Nov 07 12:38:47 Hello everyone. Does any of you know it it's possible to use the CryptoCape with the BeagleBone Green board? Nov 07 12:58:19 ooonak: I'd expect so. Nov 07 13:08:13 ooonak: you can see the needed signals here: http://elinux.org/Cryptotronix:CryptoCape Nov 07 13:09:10 Nice, Thank you! Nov 07 16:49:25 test Nov 07 16:59:05 failed Nov 07 17:27:44 epoch failed Nov 07 18:53:20 what a strange cape Nov 07 18:54:38 a TPM is of very limited use if its connection to the cpu isn't secure, and the am335x already has crypto accelerators which are very likely to be much faster than the ones on that cape Nov 07 18:55:02 (in fact I had trouble keeping the on-board AES accelerator fed with data from the cortex-a8) Nov 07 19:22:54 \leave Nov 07 20:10:16 You can't escape with that character escape :3 (Yeah I know he got it right the second time) Nov 07 20:45:26 Hello! Nov 07 20:45:40 I have a question about the beaglebone black Nov 07 20:45:50 It keeps freezing on me Nov 07 20:46:24 I have it plugged into 5v power, and the ethernet connected to a router Nov 07 20:46:34 so I can acces it wirelessly Nov 07 20:46:53 but after about 2 minuets after powerup, the lights all freeze Nov 07 20:47:22 this doesn't happen when I'm plugged into usb with my PC Nov 07 20:47:31 Anyone have any ideas? Nov 07 20:48:44 I have a question about the beaglebone black, It keeps freezing on me. I have it plugged into 5v power, and the ethernet connected to a router so I can access it wirelessly, but after about 2 minuets after powerup, the lights all freeze. this doesn't happen when I'm plugged into usb with my PC. Nov 07 20:48:52 Anyone? Nov 07 20:49:23 * Zok slaps kalz around a bit with a large fishbot Nov 07 20:52:55 Trout slapping hmm bit early for that. Nov 07 20:54:45 what? Nov 07 21:00:26 fishbot is a trout didn't you know? Nov 07 21:01:59 Yo. GenTooMan. can you answer a question? Nov 07 21:02:39 Might be able to I can always plead ignorant! :D Nov 07 21:02:47 the beaglebone black keeps freezing on me. I have it plugged into 5v power, and the ethernet connected to a router so I can access it wirelessly, but after about 2 minuets after powerup, the lights all freeze. this doesn't happen when I'm plugged into usb with my PC. Nov 07 21:03:13 I also unplugged the ethernet cable, and it still happenes Nov 07 21:03:20 *happens Nov 07 21:03:54 Its like it needs to be plugged into the PC to work properly Nov 07 21:04:19 Sounds too me like the kernel is crashing due to network connection issue. You might wish to update the firmware in the BBB to a newer version. Which version do you have of the board? Nov 07 21:04:39 uuum. how would I tell? Nov 07 21:06:51 does it boot differently when its plugged into usb? Nov 07 21:08:37 I believe it uses a different driver all together. Nov 07 21:09:09 Ooh Nov 07 21:09:56 You might be able to more accurate ascertain things if you peek at the wiki. The version of the kernel packaged with it might have had this issue fixed in it. Nov 07 21:10:27 the beaglebone wiki? Nov 07 21:12:12 So when I ssh into it, it says: Debian GNU/Linux 7 Nov 07 21:12:18 Is that the version? Nov 07 21:15:26 no the version of the board Nov 07 21:15:46 Ahh. I have the box here, but it doesn't say Nov 07 21:16:07 hang on, Rev C? Nov 07 21:18:47 http://elinux.org/Beagleboard:BeagleBoneBlack and yes ok I have B. You may need to do a simple kernel update however I would use the micro SD card and boot from that to see if that makes a difference. Writing a new kernel to the MMC requires a bit more work. Nov 07 21:19:39 So hold down the boot button while powering? Nov 07 22:18:13 Insert SD card into your (powered-down) board, hold down the USER/BOOT button (if using Black) and apply power, either by the USB cable or 5V adapter. Nov 07 22:18:23 Oh ... just got back from wandering around :D Nov 07 22:56:29 having trouble loading drivers. The 3 drivers fail. Nov 07 23:17:49 where's the correct link for the beaglebone black ubuntu img file? Nov 07 23:18:00 http://elinux.org/Beagleboard:Ubuntu_On_BeagleBone_Black Nov 07 23:18:53 direct link in main step 1 404s Nov 07 23:19:12 <_av500_> thunder5: the supported distro is debian Nov 07 23:19:23 <_av500_> ubunut is something somebody did at some point in time Nov 07 23:19:45 debian is what comes preinstalled right? Nov 07 23:19:49 <_av500_> yes Nov 07 23:20:02 i see, thanks Nov 07 23:26:54 thunder5: you can get a prebuilt image from this page http://elinux.org/BeagleBoardUbuntu#Method_1:_Download_a_Complete_Pre-Configured_Image Nov 07 23:30:33 any you'd personally recommend, wmat? Nov 07 23:31:00 <_av500_> thunder5: I'd recommend you stay with debian for a start Nov 07 23:32:51 ack Nov 07 23:43:50 does it seems odd that an educational institute would give all the people studying Electronics Raspberry Pis and all the people studying Computer Security Beaglebones? Nov 07 23:44:45 I feel like all these GPIOs are going to go to waste Nov 07 23:53:07 and the peripherals even more so Nov 08 00:17:47 <_av500_> I would say you can use either one for both Nov 08 00:36:24 downloading kali for the bb, going to take things from there in the morning Nov 08 02:16:53 * GenTooMan wakes up after all the fun is done **** ENDING LOGGING AT Sun Nov 08 02:59:58 2015