> > *You mean, you needed to wait for the device to boot and the server to > start?* >
No, I mean I got "invalid login" when trying to login via ssh. Period. Perhaps it could have been the key generation Robert mentioned above. As I had to make an adjustment to the interfaces file( from the host ). When I rebooted, it worked. *Browsing to http://<IP>:3000 didn't work for you?* > NO port 80, and 8080 only. I did not try port 3000 as the error i pasted above indicated that Nodejs was somehow listening on port 80. Also i can not elaborate on what was happening with g_multi. It just wasnt working. A Linux host was not loading cdc_ether, and a win7 host was not prompting for drivers. The module was loaded according to lsmod though, and removing the module was impossible. Afterwards, I replaced the rootfs with Robert barefs off his build instructions, and made a lot of "radical" tweaks to the file locations, ripping /lib/modules out from the stand alone image and adding to the barefs then uEnv,txt to make it all work. g_serial works fine, as i had to use it to pull in openssh-server. Anyway I've been up all night messing with this will test more later On Fri, Aug 22, 2014 at 7:13 AM, Jason Kridner <[email protected]> wrote: > On Fri, Aug 22, 2014 at 6:29 AM, William Hermans <[email protected]> > wrote: > >> Lots of things seem to be broken. >> >> g_multi is flaky, doesn't connect via usb0 to the host. >> > > Can you give some details? > > >> >> Then when connecting to the BBB via its network address over ethernet: >> >>> *Cannot GET /%7B%7Bsite.baseurl%7D%7D/Support/bone101/ * >>> >>> > I didn't realize Robert was pulling from the head of the tree. It needs to > be pre-processed with 'jekyll build' and then pull the contents from the > _site directory. I've been looking to see if I can get the webserver to do > the Jekyll pre-processing itself. Jekyll was used because of its > integration with github-pages. > > >> >> Then connecting to the ethernet IP:8080, gives and empty apache directory. >> >> When first setting up the latest testing image, it took me a bit to >> figure out how everything needed to be setup, and finally I had to edit the >> boot partitions uEnv.txt and manually set ${uname_r} variables to hard >> paths. Not sure if this is normal or not, but I knew this would work. Also >> the first several times I tried to log in via ssh with puTTY or Linux ssh >> root/debian@ipaddress, I could not log in. >> > > You mean, you needed to wait for the device to boot and the server to > start? > > >> >> Overall I would have to ay the experience was rather disappointing. I had >> hopes of toying around with the cloud9 version that runs on Nodejs v0.10.x, >> but no joy . . . >> > > Browsing to http://<IP>:3000 didn't work for you? > > >> >> Any chance of us normal people getting the source for the version of >> cloud9 that does run on Nodejs v0.10.25 ? >> > > You can always extract what is in the /opt/cloud9 folder. > http://github.com/c9/c9v3 is still private, despite them telling me they > had plans to open it up many months ago. You can ping the owners of that > repo. > > >> >> >> On Thu, Aug 21, 2014 at 2:10 PM, Robert Nelson <[email protected]> >> wrote: >> >>> On Thu, Aug 21, 2014 at 3:58 PM, Robert Nelson <[email protected]> >>> wrote: >>> > On Thu, Aug 21, 2014 at 3:52 PM, Robert Nelson < >>> [email protected]> wrote: >>> >> On Thu, Aug 21, 2014 at 3:45 PM, Kridner, Jason <[email protected]> wrote: >>> >>> looks like the last push is missing the defconfig: >>> >>> >>> http://builds.beagleboard.org/builders/runtests/builds/6/steps/shell/logs/stdio >>> >> >>> >> It's being really weird: >>> >> >>> >> http://builds.beagleboard.org/one_line_per_build >>> >> >>> >> Aug 20 21:22 b14c60a94f59...successruntests #5 Build successful >>> >> Aug 20 21:20 20830c6f9585...failureruntests #4 Failed shell shell_1 >>> >> >>> >> When i pushed the branch yesterday... It decided to build twice... >>> >> The first build, took the first commit over the old branch, which >>> >> failed as bb.org_defconfig is the last commit.. The second build >>> >> completed correctly. >>> >> >>> >> Looks like build#6 is a rebuild of build#4 >>> >> >>> >> can you add: >>> > >>> > actallly can you add: >>> > >>> > if [ -e arch/arm/configs/bb.org_defconfig ] ; then >>> > config="bb.org_defconfig" >>> > else >>> > config="omap2plus_defconfig" >>> > fi >>> >>> http://builds.beagleboard.org/builders/runtests/builds/7 >>> >>> Comments >>> am335x-bone-common: split out am33xx_pinmux >>> Signed-off-by: Robert Nelson <[email protected]> >>> >>> Which is the first commit, after the merge of greg's v3.14.17 >>> >>> https://github.com/beagleboard/linux/commits/3.14 >>> >>> Regards, >>> >>> -- >>> Robert Nelson >>> http://www.rcn-ee.com/ >>> >>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "BeagleBoard" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
