Oh, by the way. One thing I have noticed about the default images I got at least from the rpi foundation. I was going to show what version image I was using, which I can still do because the *.img file is on my x86 Debian server, But trying to log into my rpi failed. e.g. their network stack seems buggy. It does this quite often. Even still, I'm able to connect to the internet from my Android phones through the rpi acting as an AP. So . . . like Widnows often does, it loses it's brains, or part of anyhow.
william@eee-pc:~$ ls backup/ 2016-03-12-jessie-minibian.img *2016-05-27-raspbian-jessie-lite.img* BBB-blank-debian-8.5-console-armhf-2016-06-19-2gb.img.xz BBB-blank-debian-8.5-console-armhf-2016-06-19-2gb.img.xz.1 bone-debian-8.5-console-armhf-2016-06-19-2gb.img.xz bone-debian-8.6-console-armhf-2016-10-30-2gb.img.xz The one highlighted is what I'm using, The minibian image I was just "reverse engineering", and have never used it yet. On Sat, May 6, 2017 at 1:47 PM, William Hermans <[email protected]> wrote: > > > On Sat, May 6, 2017 at 12:29 PM, Dennis Lee Bieber <[email protected]> > wrote: > >> >> Talking to myself in public again... >> >> On Sat, 06 May 2017 11:46:40 -0400, Dennis Lee Bieber >> <[email protected]> declaimed the following: >> >> > >> > I'll admit, I'd prefer it if the default were not auto-login, and >> >instead an X login dialog were presented, as found on most "big machine" >> >Linux/X systems. If that were the norm, your problem would be rather >> >simple, as starting your application would be something done via your >> >account profile during login (somehow determine the login was into X, >> start >> >application -- otherwise [serial port console/SSH] ignore the >> application. >> > >> >> <SNIP> >> >> > Since the boot console uses the debug serial, I don't think there >> is >> >anything that can display on the HDMI until X is enabled. This is unlike >> >the RaspberryPi, which does spew boot messages onto a text console on >> HDMI >> >-- before it starts X (<heh> and it seems my current RPi card is giving a >> >library error on the startx, so it is doing a log-on to the HDMI text >> >console; time to reimage the SD card, the back-up card is doing auto >> log-in >> >to the X display). >> > >> >> Turns out the RPi configuration program (which runs from the auto >> login >> X display) has options controlling both auto login, and GUI vs CLI (shell) >> start-up. But take into account that even that CLI startup has to load >> enough to render text to a framebuffer for the HDMI -- it is not a simple >> pure text (ASCII/UTF-8/whatever) stream as with a true serial port. >> >> >> >> >> NON-SEQUITUR RAMBLING: >> >> OTOH: The Raspberry foundation has gone too far with security. >> 1) using NOOBS installer one MUST have keyboard/mouse/HDMI to >> respond to >> prompts >> > > This must be something new. I have an rPI here next to me right now acting > as an access point for my Android phones, and I do not even own an HDMI > cablem or even an HDMI capable monitor to plug it into. > >> >> 2) in my case, at least, after the OS installed and rebooted to the >> logged >> in X GUI, I had to edit /etc/wpa_supplicant/wpa_supplicant.conf to add my >> WiFi credentials, then reboot >> 2a) Strangely, the NOOBS installer allows for entering the >> WiFi >> passphrase, but NOT the subsequent Raspbian GUI; hence the need to do the >> edit >> 2b) The Ethernet port is also not enabled by default and >> needs to be >> enabled using the network connection icon config. >> > > Again, as my first comment. > >> >> 3) SSH is DISABLED by default, so even if one has enabled WiFi and >> hard >> Ethernet, one still can not connect from outside without making more >> configuration changes >> 3a) One subsequently gets nagged about having a default >> password on the >> regular "pi" account >> > > Same. > >> >> In short: Every updated NOOBS SD card requires a session with >> HDMI/keyboard/mouse just to get to the stage a BBB starts from... >> > > There is an option of course. Well a couple at least if you own, and have > a linux machine handy. You edit the sdcard before booting it on the rpi. Of > course, you need to know the exact modifications you need to make. > Otherwise it could get very tedious, very quickly changing the card between > PC, and rpi. > > Additionally, if something like openssh-server is not installed by > default. You can use chroot, plus QEMU to run the image emulated on an x86 > machine, usually well enough to install stock Debian packages. This > requires a bit of knowledge of course, and a bit of thinking outside the > box( sometimes ). > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORpw_7LpWQ_%3DxpPjiN0vmcLr9judLeb3nFRNeWxfGC2gRg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
