Here is the BeagleBone Debian (beta) image you want to test

Asked by 5 months ago
The latest BeagleBone Debian images are now posted at: http://beagleboard.org/latest-images/ If you've upgraded the firmware on your BeagleBone or BeagleBone Black in the past, the experience will be quite similar, but you might find the eMMC flashing times a bit faster (~15 minutes rather than ~45 minutes) due to less post-installation processing. Using the 2GB uSD card image also flashes a bit faster and can be resized to whatever your uSD card size is using some scripts under /opt/scripts/tools. Many, many thanks to Robert Nelson, Rob Rittman, Dave Anders, Cody Lacey, the Cloud9 IDE team and so many others in getting us this far. Please take the time to give a detailed look over this image and report any issues to the bug tracker on elinux.org: http://bugs.elinux.org/projects/debian-image-releases While plugged in over USB, you'll see the familiar BEAGLE_BONE drive with START.htm to tell you how to get the drivers configured if you haven't already done so: [image: Inline image 2] Clicking the link or visiting http://192.168.7.2, you'll see the familiar on-board served documentation: [image: Inline image 1] I've introduced a few bugs to the documentation ( http://github.com/beaglebone/bone101 and http://beagleboard.github.io/bone101), so expect to find a lot of issues there. Patches are welcome as are notes in the bug tracker to make sure I don't miss dotting any i's or crossing any t's. This is your chance to try to get some documentation into the system you'd like to see. I felt it was pretty safe to save the documentation as an in-beta item because it shouldn't impact functionality. One of the biggest new features you'll see is when you click on the Cloud9 IDE link: [image: Inline image 3] This is a pre-open-source-beta-only release of version 3 of their IDE. Down at the bottom of the Cloud9 IDE you'll see a new terminal window that runs a full 'tmux' session. You can open up a bunch of these and it makes logging into the board and executing command-line operations *super* simple. Cloud9 IDE version 3 now includes support for Python and the Adafruit_BBIO library is included in these Debian images. That means you can simply paste in your Python code and hit the "run" button, without any additional download. I checked this out myself by doing a quick LED blink using the Adafruit tutorial ( http://learn.adafruit.com/blinking-an-led-with-beaglebone-black/writing-a-program ): [image: Inline image 4] You should also note that the /var/lib/cloud9 directory now contains a git clone of that bone101 repo (http://github.com/beagleboard/bone101), so you can start using the Cloud9 IDE to edit the content live. What I recommend is creating your own fork of the repo and sending me pull requests of any changes you'd like to see. You can also edit C/C++ code in the Cloud9 IDE, but no 'builder' or 'runner' plug-ins are provided. You will, however, find the Userspace-Arduino (http://elinux.org/Userspace_Arduino) code in /opt/source/Userspace-Arduino. Here's a quick little exercise you can do to blink LED0: root [ at ] beaglebone# cd /opt/source/Userspace-Arduino/arduino-makefile/examples/Blink root [ at ] beaglebone# perl -i -pe 's/13/14/g' Blink.ino root [ at ] beaglebone# make root [ at ] beaglebone# ./build-userspace/Blink.elf For more advanced C/C++ developers, future releases should include https://github.com/jackmitch/libsoc. Those familiar with Linux will also note that the init system is 'systemd', which has been helpful in providing reasonable boot times. If you are looking for the journal, you can explore it using 'systemd-journalctl'. I use a Mac and despite the latest version of HoRNDIS fixing issues with Internet Connection Sharing, getting on the WIFI at home makes getting my BeagleBones on the network much easier, further making grabbing new packages with 'sudo apt-get install' much simpler. Drivers and firmware for many common USB WiFi dongles are included, so be sure to report any that you find missing. These latest images include the drivers for the popular UWN200 adapters provided by Logic Supply. To test it out myself, I uncommented and edited the wlan0 entry in /etc/network/interfaces (including replacing wlan0 with ra0), shutdown, plugged in the adapter and powered up the board again. I'm seeing the issue "rt28xx_open return fail!", but I'm sure this is something we can fix in a few days and provide an updated image. I removed that adapter and plugged in an adapter I bought from Adafruit (and switched ra0 back to wlan0) and got the issue "rtl8192cu:_rtl92cu_init_power_on():<0-0> Failed to polling REG_APS_FSMCO[APFM_ONMAC] done!". Finally, I plugged in a TL-WN822N adapter I bought from Amazon and BINGO---WiFi!!! Anyway, getting reports on what adapters work and don't work would be really helpful at this point as we'll be trying to get a very full set of WiFi drivers included. This is just a quick intro to some of the experience and what we are focused on fine tuning. Please take the time to check it out and let us know about your experience. It should be known that Koen has continued to advance the state of the Angstrom Distributions images he provides and those continue to serve as a more flexible base for building truly custom Linux distributions needed by many embedded systems developers. However, as our user base has grown, getting a Debian image that feels a bit more familiar to Linux novices is something for which I've heard tremendous demand. If feedback from the community is positive, there will be a switch as to what distribution comes loaded in the eMMC flash on the boards. I hope you enjoy it!

Your Answer

Name:
Reply:

All Answers

Answer by 5 months ago
Talking with the guys at Logic Supply, it's just a small goof in the directory location of the RT2870STA.dat file. Quick fix via: cd /opt/scripts/ git pull ./fixes/debian-2014-03-04-to-HEAD.sh or: sudo mv /etc/Wireless/RT2870/RT2870STA.dat /etc/Wireless/RT2870STA/RT2870STA.dat Regards,
Answer by 5 months ago
I can confirm that the UWN200 (and UWN100) are working well with the fix Robert mentioned. I'm getting a solid connection with WPA2 encryption.
Answer by 5 months ago
If you have a BeagleBone Black and are able to try out this image, it might be good to propose fixing any short-falls you see in what is provided on the image.
Answer by 5 months ago
Hardware: BBB A5C; OS Version: Linux beaglebone 3.8.13-bone41 #1 SMP Tue Mar 4 22:51:47 UTC 2014 armv7l GNU/Linux Tried it last night and a lot of things are working well. Cloud9 IDE debugging works perfectly for javascript. Just have to remember to hit the > button to start the debug running. I tried the python sample also, but could not get that to work. I'll investigate more. My trusty WNA1100 works out of the box with the addition of: wpa-ssid "MySSID" #SSID name wpa-psk "xxxxxxxxxxxxxxx...xx" #PSK hex string into /etc/network/interfaces under wlan0 section. The Netgear WNA1100 (Atheros chipset) is indeed the most reliable Wifi adapter I have found yet. My UWN200 (which was very reliable under later Angstrom versions) now works on debian after modifying the /etc/Wireless/RT2870STA directory name and adding the wpa-ssid/wpa-psk to the ra0 section of /etc/network/interfaces. However, I notice that the UWN200 pumps out a lot of DMESGs every 2 seconds or so. I had the same problem in 3.8.13-bone40 after compiling the kernel module from the Mediatek sources. I think there may be a debug flag turned on in the driver config, causing the frequent DMESGs. I'll check this out and see if they can be easily stopped. The WNA1100 driver is very quiet in comparison. I have a TP-Link TL WN725N lying around somewhere (Realtek chipset) that I'll try out also. (I could not get this working reliably in Angstrom - flung in a drawer somewhere!) One question springs to mind: if I want to run the BBB as a headless server with Node.js and Cloud9, is there anything I can remove from the installed software packages that would be superfluous if I'm not using HDMI, lxde and so on? Thanks for all the effort. Great software to match Gerald's fine hardware! -Eamonn
Answer by 5 months ago
I'd love to disable this "debug" feature by default, if you happen to find a fix, I'll add it to the image. For reference, I'm using this Mediatek source version: http://rcn-ee.net/deb/thirdparty/MT7601/DPO_MT7601U_LinuxSTA_3.0.0.4_20130913.tar.bz2 So If you find the config flag to quiet dmesg, i'll add it to the build snipit. https://github.com/rcn-ee/farm/blob/master/thirdparty/MT7601.sh This should clear most of the lxde/xorg package set: apt-get remove -y x11-common ; apt-get autoremove Regards,
Answer by 5 months ago
Dittos on the Kudos. With the 3.13 kernel works very nicely: all 7 of my weird USB gadgets work, Networking is good, Chrome on lxde is nice. Node 10 all looks good. Even rebuilding the kernel wasn't too painful (though still not fast enough to ditch the cross-compiler). I'm not an IDE guy so I can't comment on Cloud9, but I'm happy with gvim... (sorry for the cross-thread snark).
Answer by 5 months ago
First, thanks for the instruction to remove x11... that gets my rootfs usage down from about 83% to 69%. More room for building stuff! The Mediatek driver software has a define in os/linux/rt_linux.c line 54: - ULONG RTDebugLevel = RT_DEBUG_TRACE; +ULONG RTDebugLevel = RT_DEBUG_WARN; //Fix annoying dmsgs; was RT_DEBUG_TRACE; I've rebuilt the driver with the bone41 headers, and that seems to eliminate most of the dmesgs. Hope that's useful. Many thanks - Eamonn
Answer by 5 months ago
Awsome, thanks! https://github.com/rcn-ee/farm/commit/47a4acff774280b55772d02fccab4ad2ef63212f builder are back up and running, so the next kernel image test will have the fix.. Thanks!
Answer by 5 months ago
My Edimax rtl8192cu works out of the box, well, sort of… I'm getting seemingly *horrible* packet loss with the adapter. I've got a Raspberry Pi with the exact same adapter sitting directly next to it that has no issues. *timb [ at ] woodpi* *~ $* iwconfig wlan0 IEEE 802.11bgn ESSID:"Timothy & Star" Nickname:"WIFI [ at ] REALTEK" Mode:Managed Frequency:2.412 GHz Access Point: 60:33:4B:E8:18:AB Bit Rate:72.2 Mb/s Sensitivity:0/0 Retry:off RTS thr:off Fragment thr:off Power Management:off *Link Quality=100/100* Signal level=75/100 Noise level=0/100 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 root [ at ] beaglebone:~# iwconfig wlan2 IEEE 802.11bgn ESSID:"Timothy & Star" Mode:Managed Frequency:2.412 GHz Access Point: 60:33:4B:E8:18:AB Bit Rate=72.2 Mb/s Tx-Power=20 dBm Retry long limit:7 RTS thr=2347 B Fragment thr:off Encryption key:off Power Management:off *Link Quality=47/70* Signal level=-63 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:109 Missed beacon:0 Tons of "Invalid misc" errors on the BBB. I thought it might be the adapter itself, but swapping the Pi's adapter for the BBB's yielded the same results. I thought the Pi might be interfering with the signal somehow but that's not the issue either. At least I can actually get this online, unlike Angstrom…
Answer by 5 months ago
Thanks - Eamonn
Answer by 5 months ago
Trying to run i2cdetect but keep getting: Error: Can't use SMBus Quick Write command on this bus
Answer by 5 months ago
Quoted message by Jason Kridner 5 months ago
If you have a BeagleBone Black and are able to try out this image, it might be good to propose fixing any short-falls you see in what is provided on the image.
Well you need to add the optional "-y -f" commands.. (off the top of my head, --help to get the correct options) Regards,
Answer by 5 months ago
I am having issues with this image and mmcqd daemon, X crahes often and I end up with an empty console on my LCD 4.3: [ 180.537526] INFO: task mmcqd/0:74 blocked for more than 60 seconds. [ 180.544275] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 180.552668] Kernel panic - not syncing: hung_task: blocked tasks [ 180.559071] [<c0010443>] (unwind_backtrace+0x1/0x8a) from [<c0455ced>] (panic+0x51/0x148) [ 180.567727] [<c0455ced>] (panic+0x51/0x148) from [<c006770b>] (watchdog+0x14f/0x194) [ 180.575937] [<c006770b>] (watchdog+0x14f/0x194) from [<c003fb8f>] (kthread+0x67/0x74) [ 180.584234] [<c003fb8f>] (kthread+0x67/0x74) from [<c000c0dd>] (ret_from_fork+0x11/0x34) [ 180.592778] drm_kms_helper: panic occurred, switching back to text console I saw this post: https://groups.google.com/forum/#!topic/beagleboard/g8JQWFmw4_w is this backport from 3.12 part of the image?
Answer by 5 months ago
Yeap: https://github.com/RobertCNelson/linux-dev/blob/am33x-v3.8/patch.sh#L845 Doesn't really make a difference for 3.8 thou, as you see.. Best to just switch to v3.13.x Regards,
Answer by 5 months ago
Hello all! I have been testing the new official Debian eMMC flasher image for the BBB… *http://beagleboard.org/latest-images/* (…in particular this one Debian (BeagleBone Black - 2GB eMMC) 2014-03-04) root [ at ] vBBB5studioS:/var/lib/cloud9# uname -a Linux vBBB5studioS 3.8.13-bone41 #1 SMP Tue Mar 4 22:51:47 UTC 2014 armv7l GNU/Linux Regarding available space on the eMMC, I am seeing this after a fresh flash… root [ at ] vBBB5studioS:/var/lib/cloud9# df -h Filesystem Size Used Avail Use% Mounted on rootfs 1.7G 1.3G 284M 83% / udev 10M 0 10M 0% /dev tmpfs 100M 788K 99M 1% /run /dev/disk/by-uuid/57e2c7bb-2b31-488e-b9b4-92e3e4c6af20 1.7G 1.3G 284M 83% / tmpfs 249M 0 249M 0% /dev/shm tmpfs 249M 0 249M 0% /sys/fs/cgroup tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 100M 0 100M 0% /run/user /dev/mmcblk0p1 96M 80M 17M 83% /boot/uboot Does this look right? Is it really supposed to be 83% full from the start with only 284MB remaining? I was trying to build some software from source (*OLA framework*) and during the make process I got some errors about running out of disk space. If I was to start looking for space to free up, where would I start? (I have several BBBs and some of them I was hoping to use a GUI on, but most I just use SSH) Thanks! -frenchy
Answer by 5 months ago
Correct, to meet everyone's out of box pkg requirements, the eMMC is mostly full. If you drop opencv/python/chromium you'll gain a lot of space back. Otherwise, it's just easier to just use the non-flasher image on a 4GB/8GB microSD card. (making sure to use the "grow_partition.sh" script under /opt/scripts/tools/ to fully resize the drive) Regards,
Answer by 5 months ago
Quoted message by Steve French 5 months ago
Hello all! I have been testing the new official Debian eMMC flasher image for the BBB… *http://beagleboard.org/latest-images/* (…in particular this one Debian (BeagleBone Black - 2GB eMMC) 2014-03-04) root [ at ] vBBB5studioS:/var/lib/cloud9# uname -a Linux vBBB5studioS 3.8.13-bone41 #1 SMP Tue Mar 4 22:51:47 UTC 2014 armv7l GNU/Linux Regarding available space on the eMMC, I am seeing this after a fresh flash… root [ at ] vBBB5studioS:/var/lib/cloud9# df -h Filesystem Size Used Avail Use% Mounted on rootfs 1.7G 1.3G 284M 83% / udev 10M 0 10M 0% /dev tmpfs 100M 788K 99M 1% /run /dev/disk/by-uuid/57e2c7bb-2b31-488e-b9b4-92e3e4c6af20 1.7G 1.3G 284M 83% / tmpfs 249M 0 249M 0% /dev/shm tmpfs 249M 0 249M 0% /sys/fs/cgroup tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 100M 0 100M 0% /run/user /dev/mmcblk0p1 96M 80M 17M 83% /boot/uboot Does this look right? Is it really supposed to be 83% full from the start with only 284MB remaining? I was trying to build some software from source (*OLA framework*) and during the make process I got some errors about running out of disk space. If I was to start looking for space to free up, where would I start? (I have several BBBs and some of them I was hoping to use a GUI on, but most I just use SSH) Thanks! -frenchy
Hello, this was one of the problems with BBB. I managed to install Debian with " BBB-eMMc-flasher-debian-7.4-2014-02-16-2gb.img" installed only Xfce (needed an graphical output) and had about 450 MB left. Beside that I had to install a swap file 128 MB I'm down to 211156. That's not a lot. Under Angstrom I managed to use the sd card with the uEnv.txt as additional storage, but I forgot to withdraw the card when finished and waited while booting up until I noticed that the BBB got stuck. My question to Robert: Is there a clean way under Debian to format or mount the sd card as additional storage or even better: Is it possible to mount e.g. homedirectories to that card, so that we are not stuck to that damned 2 GB. I know, I could use the card to boot from, but ... Regards Hajo DL1SDZ
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
Correct, to meet everyone's out of box pkg requirements, the eMMC is mostly full. If you drop opencv/python/chromium you'll gain a lot of space back. Otherwise, it's just easier to just use the non-flasher image on a 4GB/8GB microSD card. (making sure to use the "grow_partition.sh" script under /opt/scripts/tools/ to fully resize the drive) Regards,
You can also dump all the man pages, locales, etc. There is a lot of documentation installed by default in debian that wasn't in the Angstrom images's.. Yes, usually any tools fdisk/sfdisk/gparted reformat the microSD card. As long as there isn't an "uEnv.txt" file with the variable "uenvcmd" set in the first partition the bootloader will ignore the microSD card. Just add it to /etc/fstab and create a new home diretory on it. Regards,
Answer by 5 months ago
Quoted message by Hajo Dezelski 5 months ago
Hello, this was one of the problems with BBB. I managed to install Debian with " BBB-eMMc-flasher-debian-7.4-2014-02-16-2gb.img" installed only Xfce (needed an graphical output) and had about 450 MB left. Beside that I had to install a swap file 128 MB I'm down to 211156. That's not a lot. Under Angstrom I managed to use the sd card with the uEnv.txt as additional storage, but I forgot to withdraw the card when finished and waited while booting up until I noticed that the BBB got stuck. My question to Robert: Is there a clean way under Debian to format or mount the sd card as additional storage or even better: Is it possible to mount e.g. homedirectories to that card, so that we are not stuck to that damned 2 GB. I know, I could use the card to boot from, but ... Regards Hajo DL1SDZ
Hello Robert, thanks for your advice. I deleted the man pages and some other stuff. It helped. Now I have about 15 % available. Great. I noticed, that most of the non-critical packages (from: Reduce Debian) were already missing. But bare with me, I'm not a Linux Guru like you. I reformatted the sd card using a script that I found: mkcard.sh found in an Angstrom discussion. It created: Device Boot Start End #cyls #blocks Id System /dev/mmcblk0p1 * 0+ 8 9- 72261 c W95 FAT32 (LBA) /dev/mmcblk0p2 9 965 957 7687102+ 83 Linux And I found the mmcblk0p2 partition named rootfs with a Lost and found directory. My uEnv.txt (found in an Angstrom-discussion) looks like: bootpart=1:2 mmcroot=/dev/mmcblk1p2 I didn't find the vriable " uenvcmd". Perhaps there is something missing in the uEnv.txt. The I create on rootfs a directory and an fstab file? And write ? And should I create the home etc. directories in that partition? Sorry for bothering you again. Next time we meet , the bottle of wine is on me. Thanks and regards Hajo Gruss Hajo ... indessen wandelt harmlos droben das Gestirn ... http://hajos-kontrapunkte.blogspot.com/
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
You can also dump all the man pages, locales, etc. There is a lot of documentation installed by default in debian that wasn't in the Angstrom images's.. Yes, usually any tools fdisk/sfdisk/gparted reformat the microSD card. As long as there isn't an "uEnv.txt" file with the variable "uenvcmd" set in the first partition the bootloader will ignore the microSD card. Just add it to /etc/fstab and create a new home diretory on it. Regards,
With my image, don't worry about this. ^^^ As long as there is no "uEnv.txt" file on the microSD, u-boot will always use the factory one i installed in the eMMC. And since it uses uuid's instead of the raw partition name, it'll always find the "rootfs" partition no matter what. So just blank/format your microSD as a simple ext4 partition. Regards,
Answer by 5 months ago
Quoted message by Hajo Dezelski 5 months ago
Hello Robert, thanks for your advice. I deleted the man pages and some other stuff. It helped. Now I have about 15 % available. Great. I noticed, that most of the non-critical packages (from: Reduce Debian) were already missing. But bare with me, I'm not a Linux Guru like you. I reformatted the sd card using a script that I found: mkcard.sh found in an Angstrom discussion. It created: Device Boot Start End #cyls #blocks Id System /dev/mmcblk0p1 * 0+ 8 9- 72261 c W95 FAT32 (LBA) /dev/mmcblk0p2 9 965 957 7687102+ 83 Linux And I found the mmcblk0p2 partition named rootfs with a Lost and found directory. My uEnv.txt (found in an Angstrom-discussion) looks like: bootpart=1:2 mmcroot=/dev/mmcblk1p2 I didn't find the vriable " uenvcmd". Perhaps there is something missing in the uEnv.txt. The I create on rootfs a directory and an fstab file? And write ? And should I create the home etc. directories in that partition? Sorry for bothering you again. Next time we meet , the bottle of wine is on me. Thanks and regards Hajo Gruss Hajo ... indessen wandelt harmlos droben das Gestirn ... http://hajos-kontrapunkte.blogspot.com/
PS: if you want to get crazy, the same script that generated this image, can also build a version of debian that'll fit in 64MB. But at that point all you have is perl/apt-get/dpkg.. Regards,
Answer by 5 months ago
Quoted message by Hajo Dezelski 5 months ago
Hello Robert, thanks for your advice. I deleted the man pages and some other stuff. It helped. Now I have about 15 % available. Great. I noticed, that most of the non-critical packages (from: Reduce Debian) were already missing. But bare with me, I'm not a Linux Guru like you. I reformatted the sd card using a script that I found: mkcard.sh found in an Angstrom discussion. It created: Device Boot Start End #cyls #blocks Id System /dev/mmcblk0p1 * 0+ 8 9- 72261 c W95 FAT32 (LBA) /dev/mmcblk0p2 9 965 957 7687102+ 83 Linux And I found the mmcblk0p2 partition named rootfs with a Lost and found directory. My uEnv.txt (found in an Angstrom-discussion) looks like: bootpart=1:2 mmcroot=/dev/mmcblk1p2 I didn't find the vriable " uenvcmd". Perhaps there is something missing in the uEnv.txt. The I create on rootfs a directory and an fstab file? And write ? And should I create the home etc. directories in that partition? Sorry for bothering you again. Next time we meet , the bottle of wine is on me. Thanks and regards Hajo Gruss Hajo ... indessen wandelt harmlos droben das Gestirn ... http://hajos-kontrapunkte.blogspot.com/
Robert, that was a fast one. Thanks again - discussions in other groups can sometimes lead you to nowhere and you get lost. (There was written that the uEnv.txt was mandatory) So I will not use your 64 MB image. Sorry, I am happy that this one is running. Have a nice day and so long from Nowhere man Hajo ... indessen wandelt harmlos droben das Gestirn ... http://hajos-kontrapunkte.blogspot.com/
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
With my image, don't worry about this. ^^^ As long as there is no "uEnv.txt" file on the microSD, u-boot will always use the factory one i installed in the eMMC. And since it uses uuid's instead of the raw partition name, it'll always find the "rootfs" partition no matter what. So just blank/format your microSD as a simple ext4 partition. Regards,
Yeah, this requirement was a bug in the version of u-boot shipped with the board. You can see how i worked around the issue here: https://github.com/eewiki/u-boot-patches/blob/master/v2013.10/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch#L154 Essentially the original factory u-boot, only checked for the presense of the microSD, if found it would try to boot with it no matter what. Instead, I set it up, to search for a uEnv.txt, try to load it and test if "uenvcmd" was set. Thus a little more error proof.. Regards,
Answer by 5 months ago
Quoted message by Steve French 5 months ago
Hello all! I have been testing the new official Debian eMMC flasher image for the BBB… *http://beagleboard.org/latest-images/* (…in particular this one Debian (BeagleBone Black - 2GB eMMC) 2014-03-04) root [ at ] vBBB5studioS:/var/lib/cloud9# uname -a Linux vBBB5studioS 3.8.13-bone41 #1 SMP Tue Mar 4 22:51:47 UTC 2014 armv7l GNU/Linux Regarding available space on the eMMC, I am seeing this after a fresh flash… root [ at ] vBBB5studioS:/var/lib/cloud9# df -h Filesystem Size Used Avail Use% Mounted on rootfs 1.7G 1.3G 284M 83% / udev 10M 0 10M 0% /dev tmpfs 100M 788K 99M 1% /run /dev/disk/by-uuid/57e2c7bb-2b31-488e-b9b4-92e3e4c6af20 1.7G 1.3G 284M 83% / tmpfs 249M 0 249M 0% /dev/shm tmpfs 249M 0 249M 0% /sys/fs/cgroup tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 100M 0 100M 0% /run/user /dev/mmcblk0p1 96M 80M 17M 83% /boot/uboot Does this look right? Is it really supposed to be 83% full from the start with only 284MB remaining? I was trying to build some software from source (*OLA framework*) and during the make process I got some errors about running out of disk space. If I was to start looking for space to free up, where would I start? (I have several BBBs and some of them I was hoping to use a GUI on, but most I just use SSH) Thanks! -frenchy
Robert, Thanks for your response! I have 15 BBBs and one uSD card, so I am kinda leaning toward using the eMMC on each. Pardon my ignorance, but is there a "magic scalpel" command to free up all space related to Opencv? ...and then separately, Chromium? Something is not right with the approach I tried... apt-get autoremove opencv* After this operation, 27.8 MB disk space will be freed. Do you want to continue [Y/n]? - apt-get autoremove chromium* Reading package lists... Done Building dependency tree Reading state information... Done Package 'chromium' is not installed, so not removed 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ...maybe I just need to learn how to use "aptitude" ? I am guessing that an "uninstall" or "remove" or "autoremove" command is better than going through and deleting random directories full of opencv/chromium related things? Thanks for any insights!!! ps- I decided to remove all documentation on one of my BBBs, so I did this... rm /usr/share/doc -R ...that seemed to free up 91MB, but it still wasnt enough!!! *Ran out of space again during "make"!!!!!!* ola-rdm-discover.cpp:232:1: fatal error: closing dependency file .deps/ola-rdm-discover.Tpo: No space left on device compilation terminated. The bug is not reproducible, so it is likely a hardware or OS problem. make[2]: *** [ola-rdm-discover.o] Error 1 make[2]: Leaving directory `/usr/local/src/ola/examples' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/ola' make: *** [all] Error 2 Thx! -frenchy
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
Correct, to meet everyone's out of box pkg requirements, the eMMC is mostly full. If you drop opencv/python/chromium you'll gain a lot of space back. Otherwise, it's just easier to just use the non-flasher image on a 4GB/8GB microSD card. (making sure to use the "grow_partition.sh" script under /opt/scripts/tools/ to fully resize the drive) Regards,
apt-get remove libopencv-* --purge ; apt-get autoremove So due to the build requirements, chromium is currently not a *.deb package. I'd like to change this. But to give you an idea, it takes a Quad Core Cortex A9, running at 1.2Ghz with 2GB of ram and a 7200rpm sata drive 8 hours to build.. SO just: rm -rf /usr/lib/chromium/ rm -f /usr/bin/chromium you can also dump: /usr/share/man/ Regards,
Answer by 5 months ago
Quoted message by Michael.ring 5 months ago
I am having issues with this image and mmcqd daemon, X crahes often and I end up with an empty console on my LCD 4.3: [ 180.537526] INFO: task mmcqd/0:74 blocked for more than 60 seconds. [ 180.544275] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 180.552668] Kernel panic - not syncing: hung_task: blocked tasks [ 180.559071] [<c0010443>] (unwind_backtrace+0x1/0x8a) from [<c0455ced>] (panic+0x51/0x148) [ 180.567727] [<c0455ced>] (panic+0x51/0x148) from [<c006770b>] (watchdog+0x14f/0x194) [ 180.575937] [<c006770b>] (watchdog+0x14f/0x194) from [<c003fb8f>] (kthread+0x67/0x74) [ 180.584234] [<c003fb8f>] (kthread+0x67/0x74) from [<c000c0dd>] (ret_from_fork+0x11/0x34) [ 180.592778] drm_kms_helper: panic occurred, switching back to text console I saw this post: https://groups.google.com/forum/#!topic/beagleboard/g8JQWFmw4_w is this backport from 3.12 part of the image?
Robert, How do you propose that users switch to v3.13.x (by which I assume you mean the Linux kernel version)? My BBB panics like this on every boot using the Debian 2014-03-04 image. I can't even log in to the text console. Dennis Cote
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
Yeap: https://github.com/RobertCNelson/linux-dev/blob/am33x-v3.8/patch.sh#L845 Doesn't really make a difference for 3.8 thou, as you see.. Best to just switch to v3.13.x Regards,
"panics" on every boot? Do you have any error log? I can't really help with that limited info. Easitest thing to do is, grab the non-flasher: https://s3.amazonaws.com/beagle-debian/bone-debian-7.4-2014-03-04-2gb.img.xz flash it to a microSD card.. mount the first fat partition, edit "uEnv.txt" remove the "quiet" from optargs.. save unmount.. Next using a usb-serial convert log the full serial boot log for me. Regards,
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
Yeap: https://github.com/RobertCNelson/linux-dev/blob/am33x-v3.8/patch.sh#L845 Doesn't really make a difference for 3.8 thou, as you see.. Best to just switch to v3.13.x Regards,
Dennis, I am not sure what you mean by "BBB panics", but I can tell you that I have been upgrading my kernel using the new Debian eMMC flasher image. I have done it on several BBBs so far with no problem.... *Before the procedure:* uname -a Linux beaglebone 3.8.13-bone41 #1 SMP Tue Mar 4 22:51:47 UTC 2014 armv7l GNU/Linux *Then Update Kernel:* - cd /opt/scripts/ - git pull - ./tools/update_kernel.sh --beta-kernel - reboot *And after the procedure:* uname -a Linux beaglebone 3.13.6-bone7 #1 SMP Sat Mar 8 01:11:45 UTC 2014 armv7l GNU/Linux Hope this helps.... -frenchy President, Volt Vision www.voltvision.com
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
Robert, How do you propose that users switch to v3.13.x (by which I assume you mean the Linux kernel version)? My BBB panics like this on every boot using the Debian 2014-03-04 image. I can't even log in to the text console. Dennis Cote
Am 12.03.2014 20:02, schrieb Robert Nelson: I'm not sure if you're talking about a non-patched 3.13.x, but I've recently tried (plain) 3.13.6 and received a panic (oops) straight on boot in musb (a bt-dongle was connected on boot). So I've just switched back to some heavy patched 3.11 I haven't many problems with. Sorry, no log too and I'm currently too lazy to fiddle with the bone and produce one, but it might be a hint to try booting with some usb-device connected. Regards, Alexander Holler
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
Robert, How do you propose that users switch to v3.13.x (by which I assume you mean the Linux kernel version)? My BBB panics like this on every boot using the Debian 2014-03-04 image. I can't even log in to the text console. Dennis Cote
He has done something wrong, or has missed a step in setting up his media. Having a serial debug cable on the board and working would clear things up in a hurry. On Wed, Mar 12, 2014 at 12:39 PM, Steve French of Volt Vision <
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
Robert, How do you propose that users switch to v3.13.x (by which I assume you mean the Linux kernel version)? My BBB panics like this on every boot using the Debian 2014-03-04 image. I can't even log in to the text console. Dennis Cote
When I said "panics like this" I meant in the same way that as the user whose message you replied to. I have copied his log below. On my BBB it usually happens just after the 120 second mark, but I have also seen it happen at 180 seconds as below. The rest of the messages are identical (same addresses etc.). [ 180.537526] INFO: task mmcqd/0:74 blocked for more than 60 seconds. [ 180.544275] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 180.552668] Kernel panic - not syncing: hung_task: blocked tasks [ 180.559071] [<c0010443>] (unwind_backtrace+0x1/0x8a) from [<c0455ced>] (panic+0x51/0x148) [ 180.567727] [<c0455ced>] (panic+0x51/0x148) from [<c006770b>] (watchdog+0x14f/0x194) [ 180.575937] [<c006770b>] (watchdog+0x14f/0x194) from [<c003fb8f>] (kthread+0x67/0x74) [ 180.584234] [<c003fb8f>] (kthread+0x67/0x74) from [<c000c0dd>] (ret_from_fork+0x11/0x34) [ 180.592778] drm_kms_helper: panic occurred, switching back to text console Easitest thing to do is, grab the non-flasher: That is what I did, and what I am running. Will do.
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
"panics" on every boot? Do you have any error log? I can't really help with that limited info. Easitest thing to do is, grab the non-flasher: https://s3.amazonaws.com/beagle-debian/bone-debian-7.4-2014-03-04-2gb.img.xz flash it to a microSD card.. mount the first fat partition, edit "uEnv.txt" remove the "quiet" from optargs.. save unmount.. Next using a usb-serial convert log the full serial boot log for me. Regards,
Yeah this annoyance.. What brand of microSD cards are you using? We've back ported a few mmc tweaks from later kernels, yet some cards still show this issue.. Regards,
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
When I said "panics like this" I meant in the same way that as the user whose message you replied to. I have copied his log below. On my BBB it usually happens just after the 120 second mark, but I have also seen it happen at 180 seconds as below. The rest of the messages are identical (same addresses etc.). [ 180.537526] INFO: task mmcqd/0:74 blocked for more than 60 seconds. [ 180.544275] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 180.552668] Kernel panic - not syncing: hung_task: blocked tasks [ 180.559071] [<c0010443>] (unwind_backtrace+0x1/0x8a) from [<c0455ced>] (panic+0x51/0x148) [ 180.567727] [<c0455ced>] (panic+0x51/0x148) from [<c006770b>] (watchdog+0x14f/0x194) [ 180.575937] [<c006770b>] (watchdog+0x14f/0x194) from [<c003fb8f>] (kthread+0x67/0x74) [ 180.584234] [<c003fb8f>] (kthread+0x67/0x74) from [<c000c0dd>] (ret_from_fork+0x11/0x34) [ 180.592778] drm_kms_helper: panic occurred, switching back to text console Easitest thing to do is, grab the non-flasher: That is what I did, and what I am running. Will do.
I'm using a 4GB Kingston Technology cards. Note, I have not expanded the partition to fill the card yet, I just to boot with it after copying the image. I'll get you the complete boot log if that is still of use. Dennis Cote
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
Robert, How do you propose that users switch to v3.13.x (by which I assume you mean the Linux kernel version)? My BBB panics like this on every boot using the Debian 2014-03-04 image. I can't even log in to the text console. Dennis Cote
##Video: Uncomment to override: ##see: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/fb/modedb.txt #kms_force_mode=video=HDMI-A-1:1024x768 [ at ] 60e ##Enable systemd systemd=quiet init=/lib/systemd/systemd ##BeagleBone Cape Overrides ##BeagleBone Black: ##Disable HDMI/eMMC #optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G ##Disable HDMI #optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN ##WIP: v3.13+ capes.. #cape=lcd4-01 #cape= ##note: the eMMC flasher script relies on the next line mmcroot=/dev/mmcblk0p2 ro mmcrootfstype=ext4 rootwait fixrtc ##These are needed to be compliant with Angstrom's 2013.06.20 u-boot. console=ttyO0,115200n8 kernel_file=zImage initrd_file=initrd.img loadaddr=0x80300000 initrd_addr=0x81600000 fdtaddr=0x815f0000 initrd_high=0xffffffff fdt_high=0xffffffff loadkernel=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${kernel_file} loadinitrd=load mmc ${mmcdev}:${mmcpart} ${initrd_addr} ${initrd_file}; setenv initrd_size ${filesize} loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdtaddr} /dtbs/${fdtfile} loadfiles=run loadkernel; run loadinitrd; run loadfdt mmcargs=setenv bootargs console=${console} ${optargs} ${kms_force_mode} root=${mmcroot} rootfstype=${mmcrootfstype} ${systemd} uenvcmd=run loadfiles; run mmcargs; bootz ${loadaddr} ${initrd_addr}:${initrd_size} ${fdtaddr}
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
"panics" on every boot? Do you have any error log? I can't really help with that limited info. Easitest thing to do is, grab the non-flasher: https://s3.amazonaws.com/beagle-debian/bone-debian-7.4-2014-03-04-2gb.img.xz flash it to a microSD card.. mount the first fat partition, edit "uEnv.txt" remove the "quiet" from optargs.. save unmount.. Next using a usb-serial convert log the full serial boot log for me. Regards,
U-Boot SPL 2013.04-dirty (Jul 10 2013 - 14:02:53) musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Peripheral mode controller at 47401000 using PIO, IRQ 0 musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Host mode controller at 47401800 using PIO, IRQ 0 OMAP SD/MMC: 0 mmc_send_cmd : timeout: No status update reading u-boot.img reading u-boot.img U-Boot 2013.04-dirty (Jul 10 2013 - 14:02:53) I2C: ready DRAM: 512 MiB WARNING: Caches not enabled NAND: No NAND device found!!! 0 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 *** Warning - readenv() failed, using default environment musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Peripheral mode controller at 47401000 using PIO, IRQ 0 musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Host mode controller at 47401800 using PIO, IRQ 0 Net: <ethaddr> not set. Validating first E-fuse MAC cpsw, usb_ether Hit any key to stop autoboot: 1 0 gpio: pin 53 (gpio 53) value is 1 mmc0 is current device micro SD card found mmc0 is current device gpio: pin 54 (gpio 54) value is 1 SD/MMC found on device 0 reading uEnv.txt 1384 bytes read in 9 ms (149.4 KiB/s) Loaded environment from uEnv.txt Importing environment from mmc ... Running uenvcmd ... reading zImage 3711864 bytes read in 426 ms (8.3 MiB/s) reading initrd.img 2873068 bytes read in 331 ms (8.3 MiB/s) reading /dtbs/am335x-boneblack.dtb 24996 bytes read in 11 ms (2.2 MiB/s) ## Flattened Device Tree blob at 815f0000 Booting using the fdt blob at 0x815f0000 Using Device Tree in place at 815f0000, end 815f91a3 Starting kernel ... Uncompressing Linux... done, booting the kernel. [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 3.8.13-bone41 (root [ at ] imx6q-sabrelite-1gb-1) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Tue Mar 4 22:51:47 UTC 2014 [ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=50c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] Machine: Generic AM33XX (Flattened Device Tree), model: TI AM335x BeagleBone [ 0.000000] Memory policy: ECC disabled, Data cache writeback [ 0.000000] AM335X ES1.0 (neon ) [ 0.000000] PERCPU: Embedded 9 pages/cpu @c0c8b000 s14080 r8192 d14592 u36864 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129792 [ 0.000000] Kernel command line: console=ttyO0,115200n8 root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait fixrtc init=/lib/systemd/systemd [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [ 0.000000] __ex_table already sorted, skipping sort [ 0.000000] allocated 1048576 bytes of page_cgroup [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups [ 0.000000] Memory: 511MB = 511MB total [ 0.000000] Memory: 506112k/506112k available, 18176k reserved, 0K highmem [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) [ 0.000000] vmalloc : 0xe0800000 - 0xff000000 ( 488 MB) [ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB) [ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) [ 0.000000] modules : 0xbf800000 - 0xbfe00000 ( 6 MB) [ 0.000000] .text : 0xc0008000 - 0xc073fc90 (7392 kB) [ 0.000000] .init : 0xc0740000 - 0xc077b700 ( 238 kB) [ 0.000000] .data : 0xc077c000 - 0xc0803240 ( 541 kB) [ 0.000000] .bss : 0xc0803240 - 0xc087a940 ( 478 kB) [ 0.000000] Hierarchical RCU implementation. [ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1. [ 0.000000] NR_IRQS:0 nr_irqs:0 0 [ 0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts [ 0.000000] Total of 128 interrupts on 1 active controller [ 0.000000] OMAP clockevent source: GPTIMER1 at 24000000 Hz [ 0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms [ 0.000000] OMAP clocksource: GPTIMER2 at 24000000 Hz [ 0.000000] Console: colour dummy device 80x30 [ 0.000377] Calibrating delay loop... 545.07 BogoMIPS (lpj=531968) [ 0.015431] pid_max: default: 32768 minimum: 301 [ 0.015672] Security Framework initialized [ 0.015768] Mount-cache hash table entries: 512 [ 0.026269] Initializing cgroup subsys cpuacct [ 0.026300] Initializing cgroup subsys memory [ 0.026365] Initializing cgroup subsys blkio [ 0.026502] CPU: Testing write buffer coherency: ok [ 0.027045] CPU0: thread -1, cpu 0, socket -1, mpidr 0 [ 0.027179] Setting up static identity map for 0x8045ed10 - 0x8045ed5c [ 0.028734] Brought up 1 CPUs [ 0.028757] SMP: Total of 1 processors activated (545.07 BogoMIPS). [ 0.030012] devtmpfs: initialized [ 0.095863] pinctrl core: initialized pinctrl subsystem [ 0.096082] rstctl core: initialized rstctl subsystem [ 0.096563] regulator-dummy: no parameters [ 0.097086] NET: Registered protocol family 16 [ 0.098055] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.108176] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568 [ 0.109238] platform 49000000.edma: alias fck already exists [ 0.109269] platform 49000000.edma: alias fck already exists [ 0.109295] platform 49000000.edma: alias fck already exists [ 0.110558] OMAP GPIO hardware version 0.1 [ 0.115229] gpio-rctrl rstctl.4: loaded OK [ 0.120864] hw-breakpoint: debug architecture 0x4 unsupported. [ 0.123050] cpsw.0: No hwaddr in dt. Using c8:a0:30:ac:da:05 from efuse [ 0.123080] cpsw.1: No hwaddr in dt. Using c8:a0:30:ac:da:07 from efuse [ 0.138406] bio: create slab <bio-0> at 0 [ 0.150215] edma-dma-engine edma-dma-engine.0: TI EDMA DMA engine driver [ 0.150652] vmmcsd_fixed: 3300 mV [ 0.153528] SCSI subsystem initialized [ 0.153931] usbcore: registered new interface driver usbfs [ 0.154041] usbcore: registered new interface driver hub [ 0.154372] usbcore: registered new device driver usb [ 0.156394] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz [ 0.157828] input: tps65217_pwr_but as /devices/ocp.3/44e0b000.i2c/i2c-0/0-0024/input/input0 [ 0.160132] DCDC1: at 1500 mV [ 0.161279] vdd_mpu: 925 <--> 1325 mV at 1100 mV [ 0.162437] vdd_core: 925 <--> 1150 mV at 1100 mV [ 0.163555] LDO1: at 1800 mV [ 0.164707] LDO2: at 3300 mV [ 0.166709] LDO3: 1800 mV [ 0.167833] LDO4: at 3300 mV [ 0.168819] tps65217 0-0024: TPS65217 ID 0xe version 1.2 [ 0.169517] omap_i2c 44e0b000.i2c: unable to select pin group [ 0.170306] omap_i2c 4819c000.i2c: bus 1 rev0.11 at 100 kHz [ 0.172668] omap_i2c 4819c000.i2c: unable to select pin group [ 0.172884] media: Linux media interface: v0.10 [ 0.172996] Linux video capture interface: v2.00 [ 0.173123] pps_core: LinuxPPS API ver. 1 registered [ 0.173139] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti giometti [ at ] linux.it [ 0.173982] Advanced Linux Sound Architecture Driver Initialized. [ 0.174958] NetLabel: Initializing [ 0.174975] NetLabel: domain hash size = 128 [ 0.174988] NetLabel: protocols = UNLABELED CIPSOv4 [ 0.175106] NetLabel: unlabeled traffic allowed by default [ 0.175469] Switching to clocksource gp_timer [ 0.230219] NET: Registered protocol family 2 [ 0.231346] TCP established hash table entries: 4096 (order: 3, 32768 bytes) [ 0.231485] TCP bind hash table entries: 4096 (order: 4, 81920 bytes) [ 0.231632] TCP: Hash tables configured (established 4096 bind 4096) [ 0.231728] TCP: reno registered [ 0.231754] UDP hash table entries: 256 (order: 1, 12288 bytes) [ 0.231796] UDP-Lite hash table entries: 256 (order: 1, 12288 bytes) [ 0.232265] NET: Registered protocol family 1 [ 0.232857] RPC: Registered named UNIX socket transport module. [ 0.232877] RPC: Registered udp transport module. [ 0.232891] RPC: Registered tcp transport module. [ 0.232904] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.233271] Trying to unpack rootfs image as initramfs... [ 0.579648] Freeing initrd memory: 2804K [ 0.580223] hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available [ 0.580656] CPU PMU: attempt to register multiple PMU devices! [ 0.580696] arm-pmu: probe of arm-pmu failed with error -28 [ 0.581178] omap2_mbox_probe: platform not supported [ 0.865908] VFS: Disk quotas dquot_6.5.2 [ 0.866154] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 0.867467] NFS: Registering the id_resolver key type [ 0.867586] Key type id_resolver registered [ 0.867602] Key type id_legacy registered [ 0.868051] fuse init (API version 7.20) [ 0.868740] Btrfs loaded [ 0.869017] msgmni has been set to 993 [ 0.871878] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249) [ 0.871903] io scheduler noop registered [ 0.871918] io scheduler deadline registered [ 0.871960] io scheduler cfq registered (default) [ 0.874019] tps65217-bl tps65217-bl: no platform data provided [ 0.874060] tps65217-bl: probe of tps65217-bl failed with error -22 [ 0.875041] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 0.877595] omap_uart 44e09000.serial: did not get pins for uart0 error: -19 [ 0.877894] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 72) is a OMAP UART0 [ 1.621140] console [ttyO0] enabled [ 1.625951] [drm] Initialized drm 1.1.0 20060810 [ 1.644491] brd: module loaded [ 1.654720] loop: module loaded [ 1.658166] at24 0-0050: 32768 byte 24c256 EEPROM, writable, 1 bytes/write [ 1.665451] at24 1-0054: 32768 byte 24c256 EEPROM, writable, 1 bytes/write [ 1.672724] at24 1-0055: 32768 byte 24c256 EEPROM, writable, 1 bytes/write [ 1.679991] at24 1-0056: 32768 byte 24c256 EEPROM, writable, 1 bytes/write [ 1.687300] at24 1-0057: 32768 byte 24c256 EEPROM, writable, 1 bytes/write [ 1.701599] bone-capemgr bone_capemgr.9: Baseboard: 'A335BNLT,0A5C,3513BBBK2628' [ 1.709393] bone-capemgr bone_capemgr.9: compatible-baseboard=ti,beaglebone-black [ 1.747857] bone-capemgr bone_capemgr.9: slot #0: No cape found [ 1.784961] bone-capemgr bone_capemgr.9: slot #1: No cape found [ 1.822070] bone-capemgr bone_capemgr.9: slot #2: No cape found [ 1.859180] bone-capemgr bone_capemgr.9: slot #3: No cape found [ 1.865437] bone-capemgr bone_capemgr.9: slot #4: specific override [ 1.872044] bone-capemgr bone_capemgr.9: bone: Using override eeprom data at slot 4 [ 1.880086] bone-capemgr bone_capemgr.9: slot #4: 'Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G' [ 1.890241] bone-capemgr bone_capemgr.9: slot #5: specific override [ 1.896845] bone-capemgr bone_capemgr.9: bone: Using override eeprom data at slot 5 [ 1.904875] bone-capemgr bone_capemgr.9: slot #5: 'Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI' [ 1.914911] bone-capemgr bone_capemgr.9: slot #6: specific override [ 1.921512] bone-capemgr bone_capemgr.9: bone: Using override eeprom data at slot 6 [ 1.929542] bone-capemgr bone_capemgr.9: slot #6: 'Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN' [ 1.940160] bone-capemgr bone_capemgr.9: loader: before slot-4 BB-BONE-EMMC-2G:00A0 (prio 1) [ 1.949025] bone-capemgr bone_capemgr.9: loader: check slot-4 BB-BONE-EMMC-2G:00A0 (prio 1) [ 1.957904] bone-capemgr bone_capemgr.9: loader: before slot-5 BB-BONELT-HDMI:00A0 (prio 1) [ 1.966667] bone-capemgr bone_capemgr.9: loader: check slot-5 BB-BONELT-HDMI:00A0 (prio 1) [ 1.975365] bone-capemgr bone_capemgr.9: initialized OK. [ 1.980961] bone-capemgr bone_capemgr.9: loader: before slot-6 BB-BONELT-HDMIN:00A0 (prio 2) [ 1.989804] bone-capemgr bone_capemgr.9: loader: check slot-6 BB-BONELT-HDMIN:00A0 (prio 2) [ 2.000691] OneNAND driver initializing [ 2.006632] usbcore: registered new interface driver cdc_ether [ 2.012818] bone-capemgr bone_capemgr.9: loader: after slot-4 BB-BONE-EMMC-2G:00A0 (prio 1) [ 2.021600] bone-capemgr bone_capemgr.9: loader: after slot-5 BB-BONELT-HDMI:00A0 (prio 1) [ 2.030355] usbcore: registered new interface driver rndis_host [ 2.036642] bone-capemgr bone_capemgr.9: loader: check slot-6 BB-BONELT-HDMIN:00A0 (prio 2) [ 2.045512] usbcore: registered new interface driver cdc_ncm [ 2.051490] bone-capemgr bone_capemgr.9: slot #4: Requesting firmware 'cape-bone-2g-emmc1.dtbo' for board-name 'Bone-LT-eMMC-2G', version '00A0' [ 2.065890] usbcore: registered new interface driver cdc_acm [ 2.071856] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 2.080238] Initializing USB Mass Storage driver... [ 2.085389] bone-capemgr bone_capemgr.9: slot #4: dtbo 'cape-bone-2g-emmc1.dtbo' loaded; converting to live tree [ 2.096098] bone-capemgr bone_capemgr.9: slot #5: Requesting firmware 'cape-boneblack-hdmi-00A0.dtbo' for board-name 'Bone-Black-HDMI', version '00A0' [ 2.110504] bone-capemgr bone_capemgr.9: slot #4: #2 overlays [ 2.116703] usbcore: registered new interface driver usb-storage [ 2.123019] USB Mass Storage support registered. [ 2.128827] bone-capemgr bone_capemgr.9: slot #4: Applied #2 overlays. [ 2.135706] bone-capemgr bone_capemgr.9: loader: done slot-4 BB-BONE-EMMC-2G:00A0 (prio 1) [ 2.144419] bone-capemgr bone_capemgr.9: loader: check slot-6 BB-BONELT-HDMIN:00A0 (prio 2) [ 2.153203] bone-capemgr bone_capemgr.9: slot #5: dtbo 'cape-boneblack-hdmi-00A0.dtbo' loaded; converting to live tree [ 2.164630] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host) [ 2.171385] musb-hdrc musb-hdrc.0.auto: pdev->id = 0 [ 2.176639] musb-hdrc musb-hdrc.0.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK [ 2.186502] bone-capemgr bone_capemgr.9: slot #5: #4 overlays [ 2.194932] platform 4830e000.fb: alias fck already exists [ 2.201114] musb-hdrc musb-hdrc.0.auto: *** mode=3 [ 2.206180] musb-hdrc musb-hdrc.0.auto: *** power=250 [ 2.213195] bone-capemgr bone_capemgr.9: slot #5: Applied #4 overlays. [ 2.220084] bone-capemgr bone_capemgr.9: loader: done slot-5 BB-BONELT-HDMI:00A0 (prio 1) [ 2.228685] bone-capemgr bone_capemgr.9: loader: check slot-6 BB-BONELT-HDMIN:00A0 (prio 2) [ 2.238202] musb-hdrc musb-hdrc.1.auto: pdev->id = 1 [ 2.243458] musb-hdrc musb-hdrc.1.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK [ 2.252245] bone-capemgr bone_capemgr.9: loader: after slot-6 BB-BONELT-HDMIN:00A0 (prio 2) [ 2.261038] bone-capemgr bone_capemgr.9: slot #6: Requesting firmware 'cape-boneblack-hdmin-00A0.dtbo' for board-name 'Bone-Black-HDMIN', version '00A0' [ 2.275541] musb-hdrc musb-hdrc.1.auto: *** mode=1 [ 2.280592] musb-hdrc musb-hdrc.1.auto: *** power=250 [ 2.285901] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver [ 2.292068] bone-capemgr bone_capemgr.9: slot #6: dtbo 'cape-boneblack-hdmin-00A0.dtbo' loaded; converting to live tree [ 2.303816] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 1 [ 2.312358] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 2.319500] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.327074] usb usb1: Product: MUSB HDRC host driver [ 2.332290] usb usb1: Manufacturer: Linux 3.8.13-bone41 musb-hcd [ 2.338592] usb usb1: SerialNumber: musb-hdrc.1.auto [ 2.344171] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN conflict P8.45 (#5:BB-BONELT-HDMI) [ 2.353785] bone-capemgr bone_capemgr.9: slot #6: Failed verification [ 2.360560] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2) [ 2.371457] hub 1-0:1.0: USB hub found [ 2.375481] hub 1-0:1.0: 1 port detected [ 2.381024] mousedev: PS/2 mouse device common for all mice [ 2.389331] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0 [ 2.397098] i2c /dev entries driver [ 2.402546] pps_ldisc: PPS line discipline registered [ 2.408052] Driver for 1-wire Dallas network protocol. [ 2.415375] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec [ 2.423298] device-mapper: ioctl: 4.23.1-ioctl (2012-12-18) initialised: dm-devel [ at ] redhat.com [ 2.432253] cpuidle: using governor ladder [ 2.436618] cpuidle: using governor menu [ 2.441284] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' failed [ 2.448506] omap_hsmmc mmc.5: Failed to get rstctl; not using any [ 2.455327] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25 [ 2.462551] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24 [ 2.469906] mmc.5 supply vmmc_aux not found, using dummy regulator [ 2.476840] omap_hsmmc mmc.5: pins are not configured from the driver [ 2.511869] gpio-rctrl rstctl.4: gpio_rctrl_request eMMC_RSTn [ 2.518079] omap_hsmmc mmc.11: Got rstctl (gpio:#0 name eMMC_RSTn) label:eMMC_RSTn [ 2.526072] gpio-rctrl rstctl.4: gpio_rctrl_deassert eMMC_RSTn [ 2.532521] edma-dma-engine edma-dma-engine.0: allocated channel for 0:3 [ 2.539673] edma-dma-engine edma-dma-engine.0: allocated channel for 0:2 [ 2.547207] mmc.11 supply vmmc_aux not found, using dummy regulator [ 2.553945] omap_hsmmc mmc.11: pins are not configured from the driver [ 2.588194] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8 [ 2.599905] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22 [ 2.607254] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single [ 2.616597] leds-gpio gpio-leds.8: pins are not configured from the driver [ 2.625349] ledtrig-cpu: registered to indicate activity on CPUs [ 2.632212] edma-dma-engine edma-dma-engine.0: allocated channel for 0:36 [ 2.639478] omap-sham 53100000.sham: hw accel on OMAP rev 4.3 [ 2.647992] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2 [ 2.654404] edma-dma-engine edma-dma-engine.0: allocated channel for 0:5 [ 2.661571] mmc0: host does not support reading read-only switch. assuming write-enable. [ 2.670190] edma-dma-engine edma-dma-engine.0: allocated channel for 0:6 [ 2.679510] mmc0: new high speed SDHC card at address 1234 [ 2.688576] usbcore: registered new interface driver usbhid [ 2.694500] usbhid: USB HID core driver [ 2.699482] mmcblk0: mmc0:1234 SA04G 3.63 GiB [ 2.706410] ashmem: initialized [ 2.709990] mmcblk0: p1 p2 [ 2.713361] logger: created 256K log 'log_main' [ 2.720087] logger: created 256K log 'log_events' [ 2.725505] logger: created 256K log 'log_radio' [ 2.730785] logger: created 256K log 'log_system' [ 2.740402] davinci_evm sound.14: nxp-hdmi-hifi <-> 48038000.mcasp mapping ok [ 2.752188] TCP: cubic registered [ 2.755860] NET: Registered protocol family 10 [ 2.761949] NET: Registered protocol family 17 [ 2.767047] Key type dns_resolver registered [ 2.771906] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3 [ 2.780164] ThumbEE CPU extension supported. [ 2.784719] Registering SWP/SWPB emulation handler [ 2.790756] registered taskstats version 1 [ 2.797617] tilcdc 4830e000.fb: No power control GPIO [ 2.815660] mmc1: BKOPS_EN bit is not set [ 2.822580] mmc1: new high speed MMC card at address 0001 [ 2.828347] usb 1-1: new high-speed USB device number 2 using musb-hdrc [ 2.836181] mmcblk1: mmc1:0001 MMC02G 1.78 GiB [ 2.841470] mmcblk1boot0: mmc1:0001 MMC02G partition 1 1.00 MiB [ 2.848079] mmcblk1boot1: mmc1:0001 MMC02G partition 2 1.00 MiB [ 2.856592] mmcblk1: p1 p2 [ 2.862316] mmcblk1boot1: unknown partition table [ 2.869689] mmcblk1boot0: unknown partition table [ 2.922734] tilcdc 4830e000.fb: found TDA19988 [ 2.928192] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 2.935138] [drm] No driver support for vblank timestamp query. [ 2.960221] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608 [ 2.967268] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 2.974749] usb 1-1: Product: USB2.0 Hub [ 2.980295] hub 1-1:1.0: USB hub found [ 2.984600] hub 1-1:1.0: 4 ports detected [ 3.077953] tilcdc 4830e000.fb: Connected to an HDMI monitor with cea mode 8 [ 3.106261] Console: switching to colour frame buffer device 160x45 [ 3.132495] tilcdc 4830e000.fb: fb0: frame buffer device [ 3.138163] tilcdc 4830e000.fb: registered panic notifier [ 3.143848] [drm] Initialized tilcdc 1.0.0 20121205 on minor 0 [ 3.199061] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6 [ 3.205474] davinci_mdio 4a101000.mdio: detected phy mask fffffffe [ 3.223201] libphy: 4a101000.mdio: probed [ 3.227512] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720 [ 3.237519] Detected MACID = c8:a0:30:ac:da:05 [ 3.242244] cpsw 4a100000.ethernet: NAPI disabled [ 3.249391] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800) [ 3.294963] usb 1-1.1: new low-speed USB device number 3 using musb-hdrc [ 3.310332] tilcdc 4830e000.fb: timeout waiting for framedone [ 3.328348] ALSA device list: [ 3.331493] #0: TI BeagleBone Black [ 3.335982] Freeing init memory: 236K Loading, please wait... [ 3.388866] usb 1-1.1: New USB device found, idVendor=046d, idProduct=c31c [ 3.396095] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3.403738] usb 1-1.1: Product: USB Keyboard [ 3.408200] usb 1-1.1: Manufacturer: Logitech [ 3.426899] input: Logitech USB Keyboard as /devices/ocp.3/47400000.usb/musb-hdrc.1.auto/usb1/1-1/1-1.1/1-1.1:1.0/input/input1 [ 3.449233] hid-generic 0003:046D:C31C.0001: input,hidraw0: USB HID v1.10 Keyboard [Logitech USB Keyboard] on usb-musb-hdrc.1.auto-1.1/input0 [ 3.469754] udevd[100]: starting version 175 [ 3.495371] input: Logitech USB Keyboard as /devices/ocp.3/47400000.usb/musb-hdrc.1.auto/usb1/1-1/1-1.1/1-1.1:1.1/input/input2 [ 3.531227] hid-generic 0003:046D:C31C.0002: input,hidraw1: USB HID v1.10 Device [Logitech USB Keyboard] on usb-musb-hdrc.1.auto-1.1/input1 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. [ 4.982929] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. Welcome to Debian GNU/Linux 7 (wheezy)! Starting udev Kernel Device Manager... Starting Apply Kernel Variables... Starting Security File System... Started Set Up Additional Binary Formats [ OK ] Starting POSIX Message Queue File System... Started Huge Pages File System [ OK ] Starting Load Kernel Modules... Starting Debug File System... Starting udev Coldplug all Devices... Starting Lock Directory... Starting Remount API VFS... Starting User Runtime Directory... Starting File System Check on Root Device... Starting Journal Service... Started Journal Service [ OK ] Started Apply Kernel Variables [ OK ] [ 120.863077] INFO: task mmcqd/0:71 blocked for more than 60 seconds. [ 120.869646] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 120.877833] mmcqd/0 D c045aca7 0 71 2 0x00000000 [ 120.884512] Kernel panic - not syncing: hung_task: blocked tasks [ 120.890799] [<c0010443>] (unwind_backtrace+0x1/0x8a) from [<c0455ced>] (panic+0x51/0x148) [ 120.899332] [<c0455ced>] (panic+0x51/0x148) from [<c006770b>] (watchdog+0x14f/0x194) [ 120.907418] [<c006770b>] (watchdog+0x14f/0x194) from [<c003fb8f>] (kthread+0x67/0x74) [ 120.915591] [<c003fb8f>] (kthread+0x67/0x74) from [<c000c0dd>] (ret_from_fork+0x11/0x34) [ 120.924027] drm_kms_helper: panic occurred, switching back to text console
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
##Video: Uncomment to override: ##see: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/fb/modedb.txt #kms_force_mode=video=HDMI-A-1:1024x768 [ at ] 60e ##Enable systemd systemd=quiet init=/lib/systemd/systemd ##BeagleBone Cape Overrides ##BeagleBone Black: ##Disable HDMI/eMMC #optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G ##Disable HDMI #optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN ##WIP: v3.13+ capes.. #cape=lcd4-01 #cape= ##note: the eMMC flasher script relies on the next line mmcroot=/dev/mmcblk0p2 ro mmcrootfstype=ext4 rootwait fixrtc ##These are needed to be compliant with Angstrom's 2013.06.20 u-boot. console=ttyO0,115200n8 kernel_file=zImage initrd_file=initrd.img loadaddr=0x80300000 initrd_addr=0x81600000 fdtaddr=0x815f0000 initrd_high=0xffffffff fdt_high=0xffffffff loadkernel=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${kernel_file} loadinitrd=load mmc ${mmcdev}:${mmcpart} ${initrd_addr} ${initrd_file}; setenv initrd_size ${filesize} loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdtaddr} /dtbs/${fdtfile} loadfiles=run loadkernel; run loadinitrd; run loadfdt mmcargs=setenv bootargs console=${console} ${optargs} ${kms_force_mode} root=${mmcroot} rootfstype=${mmcrootfstype} ${systemd} uenvcmd=run loadfiles; run mmcargs; bootz ${loadaddr} ${initrd_addr}:${initrd_size} ${fdtaddr}
Using a different 8GB SD card my BBB boots this new image as expected. Hopefully the bootlog from the problem card will help identify the issue. Dennis Cote
Answer by 5 months ago
On booting this new image I noticed a few issues immediately, but I'm not sure if one is by design. The ethernet interface is not setup in this image. Running ifconfig shows no IP address for the ethernet port. Looking at /etc/network/interfaces I see that the eth0 section is commented out. I tried adding the following to /etc/network/interfaces but I still have no IP address assigned (as if dhcp wasn't aquirring an address). Commenting out the allow-hotplug line makes no difference. auto eth0 allow-hotplug eth0 iface eth0 inet dhcp Shouldn't the ethernet interface be setup by default? How does one setup dhcp on Debian if not through the interfaces file? Also, how is one supposed to use the Root Terminal in the LXDE environment? It won't accept the admin password for the debian user, and I don't know if there is a different root password? Thanks. Dennis Cote
Answer by 5 months ago
The wicd deamon should setup eth0 within 30 seconds on 2nd boot. (first boot there is a slight delay as the ssh key's are generated). If you uncomment out the eth0 interface in /etc/network/interfaces boot time falls from 15seconds to 35ish.. Nice catch, i need to remove that application from the menu. It was requested to blank out the root password for ease of use. Regards,
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
On booting this new image I noticed a few issues immediately, but I'm not sure if one is by design. The ethernet interface is not setup in this image. Running ifconfig shows no IP address for the ethernet port. Looking at /etc/network/interfaces I see that the eth0 section is commented out. I tried adding the following to /etc/network/interfaces but I still have no IP address assigned (as if dhcp wasn't aquirring an address). Commenting out the allow-hotplug line makes no difference. auto eth0 allow-hotplug eth0 iface eth0 inet dhcp Shouldn't the ethernet interface be setup by default? How does one setup dhcp on Debian if not through the interfaces file? Also, how is one supposed to use the Root Terminal in the LXDE environment? It won't accept the admin password for the debian user, and I don't know if there is a different root password? Thanks. Dennis Cote
I had rebooted many times. I hadn't paid any attention to the wicd program since it seemed to be for WIFI which I am not using. I had to open the preferences and check the option to always show wired interfaces (I also checked always switch to wired connection when available) before I saw the eth0 connection. I then clicked the connect button and waited until it finished. It still didn't connect, but after I rebooted again, it did connect using dhcp. Since then it has been connecting on each boot. I'm not sure what you mean by this. "unccomment out" is ambiguous. Did you mean "uncomment", or did you mean "comment out". Is it faster to boot with the eth0 defined in /etc/network/interfaces, or is it faster with the eth0 section commented out? Why? Is it redundant to define eth0 here, and then have wicd also connect eth0; or does having defined in the interafces file cause wicd to skip its redundant setup later? On an unrelated issue, how do you setup the timezone for the time display on the LXDE desktop? I have set /etc/timezone. I have also used tzselect and added the TZ environment variable to my .profile as suggested in the output of tzselect. It does not appear that my .profile file is being executed though. I have a user bin directory in my /home/debian directory, and it is not being added to the path as it seems it should be by reading the .profile file. I checked and I don't have a .bash_profile or .bash_login file which would prevent .profile from executing. Any ideas? Dennis Cote
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
The wicd deamon should setup eth0 within 30 seconds on 2nd boot. (first boot there is a slight delay as the ssh key's are generated). If you uncomment out the eth0 interface in /etc/network/interfaces boot time falls from 15seconds to 35ish.. Nice catch, i need to remove that application from the menu. It was requested to blank out the root password for ease of use. Regards,
The first. When, eth0 is defined in /etc/network/interfaces, the login prompt (serial/video) can be delayed for up to 2 minutes as the system attempts to get an ip. If a cable is NOT connected it will wait the full 2 minutes. So by allowing the wicd/systemd deamon to take care of it, we get the login prompt must faster root [ at ] beaglebone:/# rm /etc/localtime root [ at ] beaglebone:/# ln -s /usr/share/zoneinfo/US/Central /etc/localtime root [ at ] beaglebone:/# date Thu Mar 13 12:13:06 CDT 2014 Give lxde a minute or two to update.. Regards,
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
I had rebooted many times. I hadn't paid any attention to the wicd program since it seemed to be for WIFI which I am not using. I had to open the preferences and check the option to always show wired interfaces (I also checked always switch to wired connection when available) before I saw the eth0 connection. I then clicked the connect button and waited until it finished. It still didn't connect, but after I rebooted again, it did connect using dhcp. Since then it has been connecting on each boot. I'm not sure what you mean by this. "unccomment out" is ambiguous. Did you mean "uncomment", or did you mean "comment out". Is it faster to boot with the eth0 defined in /etc/network/interfaces, or is it faster with the eth0 section commented out? Why? Is it redundant to define eth0 here, and then have wicd also connect eth0; or does having defined in the interafces file cause wicd to skip its redundant setup later? On an unrelated issue, how do you setup the timezone for the time display on the LXDE desktop? I have set /etc/timezone. I have also used tzselect and added the TZ environment variable to my .profile as suggested in the output of tzselect. It does not appear that my .profile file is being executed though. I have a user bin directory in my /home/debian directory, and it is not being added to the path as it seems it should be by reading the .profile file. I checked and I don't have a .bash_profile or .bash_login file which would prevent .profile from executing. Any ideas? Dennis Cote
*dpkg-reconfigure tzdata* <--- Doesnt work ?
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
The first. When, eth0 is defined in /etc/network/interfaces, the login prompt (serial/video) can be delayed for up to 2 minutes as the system attempts to get an ip. If a cable is NOT connected it will wait the full 2 minutes. So by allowing the wicd/systemd deamon to take care of it, we get the login prompt must faster root [ at ] beaglebone:/# rm /etc/localtime root [ at ] beaglebone:/# ln -s /usr/share/zoneinfo/US/Central /etc/localtime root [ at ] beaglebone:/# date Thu Mar 13 12:13:06 CDT 2014 Give lxde a minute or two to update.. Regards,
Yeap, that works too.. Which brings up a fun question. What default timezone do you guys want? Or is "utc" generic enough? My only vote is US/Central as that is where i'm located.. Regards,
Answer by 5 months ago
Quoted message by William Hermans 5 months ago
*dpkg-reconfigure tzdata* <--- Doesnt work ?
It is "utc" generic ! ;-) 72 de Hajo ... indessen wandelt harmlos droben das Gestirn ... http://hajos-kontrapunkte.blogspot.com/
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
Yeap, that works too.. Which brings up a fun question. What default timezone do you guys want? Or is "utc" generic enough? My only vote is US/Central as that is where i'm located.. Regards,
I know! ;) I was having fun playing with that sentence. Regards,
Answer by 5 months ago
Quoted message by William Hermans 5 months ago
*dpkg-reconfigure tzdata* <--- Doesnt work ?
I'd rather see a system come up "UTC" rather than some other TZ not specific to me. I don't have a problem changing it if I have too though. UTC would seem to make the most sense. Mike
Answer by 5 months ago
Quoted message by William Hermans 5 months ago
*dpkg-reconfigure tzdata* <--- Doesnt work ?
I think UTC would be best, but there should be clear instructions for how to change it. Most users (like me) are not Linux experts and don't know how to do many of these basic things. I though /etc/timezone seemed like the perfect place to make this change, but it turns out that was wrong. Google led me to tzselect which also looked promising, but again it was wrong. Dennis Cote
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
Yeap, that works too.. Which brings up a fun question. What default timezone do you guys want? Or is "utc" generic enough? My only vote is US/Central as that is where i'm located.. Regards,
So then, here's a question for you. Where do you want to see those type of faq's listed? I can pretty much dump them anywhere, but the hard question is where... Regards,
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
I think UTC would be best, but there should be clear instructions for how to change it. Most users (like me) are not Linux experts and don't know how to do many of these basic things. I though /etc/timezone seemed like the perfect place to make this change, but it turns out that was wrong. Google led me to tzselect which also looked promising, but again it was wrong. Dennis Cote
I thought you were posting all of your stuff to elinux.org?
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
I think UTC would be best, but there should be clear instructions for how to change it. Most users (like me) are not Linux experts and don't know how to do many of these basic things. I though /etc/timezone seemed like the perfect place to make this change, but it turns out that was wrong. Google led me to tzselect which also looked promising, but again it was wrong. Dennis Cote
Oh I do. ;) I'm just hoping to get a fresh perspective and see where a new user expects it to be today. (As we can never go back to being "new"..) Regards,
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
I think UTC would be best, but there should be clear instructions for how to change it. Most users (like me) are not Linux experts and don't know how to do many of these basic things. I though /etc/timezone seemed like the perfect place to make this change, but it turns out that was wrong. Google led me to tzselect which also looked promising, but again it was wrong. Dennis Cote
I don't know where they should be stored, but there should definitely be links on the beagleboard.org main page. It seems to me that if Debian is going to replace Angstrom, then a link to the Debian release images and FAQs should be put there. Eventually, the Angstrom info could be deprecated, or rather archived and its visibility reduced. It seems to me that there are currently too many places to go to get the various linux distributions and kernels, and none of them seem to be officially sanctioned as the "standard" release. This leads to unnecessary confusion for new users. Some info on beagleboard.org, some info at circuitco.com, some info at elinux.org, some info at armhf.com, etc., not to mention all the other stuff at ti.com. The official wiki at http://www.elinux.org/Beagleboard:BeagleBoneBlack#Software_Resources doesn't even mention this Debian releases (and it should if you want people to test it). The community wiki at http://elinux.org/BeagleBone_Community#Debian does list a Debian release, but it is a different, and incompatible, arm EABI version from this new armhf release. I appreciate all the hard work that people have done to prepare all this information, but it's a little like the wild west when you first start looking around. Dennis Cote
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
I think UTC would be best, but there should be clear instructions for how to change it. Most users (like me) are not Linux experts and don't know how to do many of these basic things. I though /etc/timezone seemed like the perfect place to make this change, but it turns out that was wrong. Google led me to tzselect which also looked promising, but again it was wrong. Dennis Cote
Am 13.03.2014 21:33, schrieb Robert Nelson: motd or the banner for ssh, together with an instruction to use rm to get rid of the message. Listing those basic steps there would get rid of thousands question from people using broken, old and/or outdated instructions belonging to some broken/old and/or outdated images. Regards, Alexander Holler
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
I think UTC would be best, but there should be clear instructions for how to change it. Most users (like me) are not Linux experts and don't know how to do many of these basic things. I though /etc/timezone seemed like the perfect place to make this change, but it turns out that was wrong. Google led me to tzselect which also looked promising, but again it was wrong. Dennis Cote
I've been dumping the default username/password + the current ip address if we get it in time to "/etc/issue" so it shows up on both the dvi and serial terminal. We could dump an elinux link faq there too. Good call on the ssh message, didn't think of that. Regards,
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
I think UTC would be best, but there should be clear instructions for how to change it. Most users (like me) are not Linux experts and don't know how to do many of these basic things. I though /etc/timezone seemed like the perfect place to make this change, but it turns out that was wrong. Google led me to tzselect which also looked promising, but again it was wrong. Dennis Cote
Am 13.03.2014 22:24, schrieb Alexander Holler: And if some gui is supported, open an editor like gvim or similiar to show those instructions gui-users too (by using some autoexec mechanism the gui in question offers). Anything else than in-image-instructions which people will see when they start exploring the board doesn't help as history has shown. Alexander Holler
Answer by 5 months ago
Every time I boot, or logout of LXDE, I get a touchscreen calibration program that runs. It says 'Touchscreen calibration for Logitech USB Keyboard' (I think it sometimes says Mouse, but I could be mistaken). I am running with a HDMI monitor and a USB keyboard and mouse connected to an external powered hub. I have no touchscreen to calibrate and this wastes about 15 seconds on each logout. What starts this program, and how do I disable it? Also, the .profile file in the /home/debian directory is not being executed. I don't have a .bash_profile or .bash_login file to prevent it from being loaded. I noticed the default shell is dash rather than bash, at least /bin/sh is linked to /bin/dash, but the dash man page says it should read commands from .profile as well. When I tried the chsh command it says the default login shell is /bin/bash which should definitely read from .profile. I can tell that .profile is not being executed because I have a personal bin directory at /home/debian/bin. This directory should be added to the PATH by the .profile, but that isn't happening. I have also set a new environment variable in my .profile and it does not appear in the output of the env command. Any ideas why my .profile is not executing? Dennis Cote
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
I think UTC would be best, but there should be clear instructions for how to change it. Most users (like me) are not Linux experts and don't know how to do many of these basic things. I though /etc/timezone seemed like the perfect place to make this change, but it turns out that was wrong. Google led me to tzselect which also looked promising, but again it was wrong. Dennis Cote
I second that. I am one of those who just started going west into the wild. And I am still not sure which information are official and which are not. However I am now sure that I didn't grab Robert's kernel.
Answer by 5 months ago
Quoted message by Jason Kridner 5 months ago
If you have a BeagleBone Black and are able to try out this image, it might be good to propose fixing any short-falls you see in what is provided on the image.
That's interesting, the lcd/touchscreen detect script is pretty basic, i'll have to add whitelist for some devices. Can you pastebin this file for me: /var/log/xinput_calibrator.pointercal.log and the output of "xinput" you will have to run it from x11, no serial/ssh.. Yeah, export PATH=$PATH:~/bin in ~/.profile is all you should need.. Regards,
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
Every time I boot, or logout of LXDE, I get a touchscreen calibration program that runs. It says 'Touchscreen calibration for Logitech USB Keyboard' (I think it sometimes says Mouse, but I could be mistaken). I am running with a HDMI monitor and a USB keyboard and mouse connected to an external powered hub. I have no touchscreen to calibrate and this wastes about 15 seconds on each logout. What starts this program, and how do I disable it? Also, the .profile file in the /home/debian directory is not being executed. I don't have a .bash_profile or .bash_login file to prevent it from being loaded. I noticed the default shell is dash rather than bash, at least /bin/sh is linked to /bin/dash, but the dash man page says it should read commands from .profile as well. When I tried the chsh command it says the default login shell is /bin/bash which should definitely read from .profile. I can tell that .profile is not being executed because I have a personal bin directory at /home/debian/bin. This directory should be added to the PATH by the .profile, but that isn't happening. I have also set a new environment variable in my .profile and it does not appear in the output of the env command. Any ideas why my .profile is not executing? Dennis Cote
PS: what model/etc is it? lsusb? Encase I need to go pick one up. Regards,
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
That's interesting, the lcd/touchscreen detect script is pretty basic, i'll have to add whitelist for some devices. Can you pastebin this file for me: /var/log/xinput_calibrator.pointercal.log and the output of "xinput" you will have to run it from x11, no serial/ssh.. Yeah, export PATH=$PATH:~/bin in ~/.profile is all you should need.. Regards,
Robert, thanks for your work. Is there a guide somewhere to build or a way to download a absolute minimal image. Something with only ssh, apt and full hardware initialization on it and nothing else. That would be a good base for couple of headless projects I am thinking about. When I am talking about HW initialization I am only thinking about network and hwrng Right now I am using this: http://rcn-ee.net/deb/flasher/wheezy/BBB-eMMC-flasher-debian-7.4-2014-02-16-2gb.img.xz and I will continue to use it as it is. But if you plan to stop developing those images I need to start thinking about another way to get a headless emmc debian image working.
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
PS: what model/etc is it? lsusb? Encase I need to go pick one up. Regards,
No worries, I have no plans to discontinue those monthly "minimal" images. I have a lot of users using them. Plus they support older boards like the beagle. Regards,
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
I think UTC would be best, but there should be clear instructions for how to change it. Most users (like me) are not Linux experts and don't know how to do many of these basic things. I though /etc/timezone seemed like the perfect place to make this change, but it turns out that was wrong. Google led me to tzselect which also looked promising, but again it was wrong. Dennis Cote
Robert, Just my $0.02 about *where* info should be stored: I completely agree about Dennis' "Wild West" comment. When I first started with the BBB back in Sep2013 all 5 of the various websites that Dennis referenced seemed to contradict each other. The "official" image was outdated and the most recent images were hidden away and you almost needed a "secret knock" to find them. I completely understand that everything has been in a massive state of flux, especially since all of the changes with the way Device Tree was handled, etc, etc. It seems to me, though, that out of the 5 websites that Dennis referenced, perhaps 4 of them should say "Things are in a state of massive flux right now.... Instead of us updating 5 websites all the time, Please check this *one* website for the most up-to-date info." Then on the *1* website which is "continuously updated" it could say: Here is the most recent "stable" official image and here is the most recent "development" official image. It is strange having 5 different websites to have to check when you are a Newbie...and then Gerald says "why didnt you check 'the' website". Thx! I respect and appreciate all the work you do!! These are challenging times! -frenchy President, Volt Vision www.voltvision.com
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
I think UTC would be best, but there should be clear instructions for how to change it. Most users (like me) are not Linux experts and don't know how to do many of these basic things. I though /etc/timezone seemed like the perfect place to make this change, but it turns out that was wrong. Google led me to tzselect which also looked promising, but again it was wrong. Dennis Cote
On Fri, Mar 14, 2014 at 9:00 AM, Steve French of Volt Vision Hi Steve, I've started an offical page at: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian My plan is to hint at this page in both the serial/dvi terminal along with an ssh message on the default image. I'll try to get the "more info" links from here http://beagleboard.org/latest-images also linked to that page. Regards,
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
Every time I boot, or logout of LXDE, I get a touchscreen calibration program that runs. It says 'Touchscreen calibration for Logitech USB Keyboard' (I think it sometimes says Mouse, but I could be mistaken). I am running with a HDMI monitor and a USB keyboard and mouse connected to an external powered hub. I have no touchscreen to calibrate and this wastes about 15 seconds on each logout. What starts this program, and how do I disable it? Also, the .profile file in the /home/debian directory is not being executed. I don't have a .bash_profile or .bash_login file to prevent it from being loaded. I noticed the default shell is dash rather than bash, at least /bin/sh is linked to /bin/dash, but the dash man page says it should read commands from .profile as well. When I tried the chsh command it says the default login shell is /bin/bash which should definitely read from .profile. I can tell that .profile is not being executed because I have a personal bin directory at /home/debian/bin. This directory should be added to the PATH by the .profile, but that isn't happening. I have also set a new environment variable in my .profile and it does not appear in the output of the env command. Any ideas why my .profile is not executing? Dennis Cote
Here you go: xinput_calibrator.log pastebin.com/EZ4uSu4W xinput.txt pastebin.com/ZBDXGkt3 lsusb.txt pastebin.com/0UthnPqZ You are missing my point. These commands are already in the default .profile created for the debian user. See the pastebin.com/kjDXbEpJ for a copy of mine. I added the TZ environment variable at the end. ls ~ shows my bin directory exists env | grep HOME shows the HOME variable as /home/debian env | grep PATH shows the PATH as /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games The .profile should be adding /home/debian/bin to the path, but it is not. It is also not adding the TZ variable to the environment. BTW, we could probably remove the two games directories from the default PATH as well. I don't think many users will be using BBB for gaming. Dennis Cote
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
That's interesting, the lcd/touchscreen detect script is pretty basic, i'll have to add whitelist for some devices. Can you pastebin this file for me: /var/log/xinput_calibrator.pointercal.log and the output of "xinput" you will have to run it from x11, no serial/ssh.. Yeah, export PATH=$PATH:~/bin in ~/.profile is all you should need.. Regards,
Is this shell running within X? If so .profile isn't sourced as it's not run as login shell. I don't quite follow why you want to set the TZ variable from the user environment either. It's all handled at a system level by default. No need to set the variable then export it either, just do it all in one go. export TZ="Whatever" Also less typing to just "echo" variables.... echo $HOME $PATH Really no need for env and grep. Mike
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
I think UTC would be best, but there should be clear instructions for how to change it. Most users (like me) are not Linux experts and don't know how to do many of these basic things. I though /etc/timezone seemed like the perfect place to make this change, but it turns out that was wrong. Google led me to tzselect which also looked promising, but again it was wrong. Dennis Cote
Hi Robert, I'm sorry to nitpick, but this new "official" page is wrong right out of the gate. It says it is "about running an ARM EABI Debian" distribution. The Debian page at https://wiki.debian.org/ArmEabiPort says this is different than the newer armhf ABI which I believe is the basis for your images. Getting this kind of basic stuff correct is important. Also, the description of how to set the timezone to your local timezone so that the clock displays local wall clock time is terse to point of extreme. It is not at all clear what the listed commands do, or why you might want to use them. Dennis Cote
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
That's interesting, the lcd/touchscreen detect script is pretty basic, i'll have to add whitelist for some devices. Can you pastebin this file for me: /var/log/xinput_calibrator.pointercal.log and the output of "xinput" you will have to run it from x11, no serial/ssh.. Yeah, export PATH=$PATH:~/bin in ~/.profile is all you should need.. Regards,
I don't see anything obvious, so I ordered it up.. It works here: debian [ at ] beaglebone:~/bin$ nano simple.c debian [ at ] beaglebone:~/bin$ gcc -Wall simple.c -o simple debian [ at ] beaglebone:~/bin$ cd .. debian [ at ] beaglebone:~$ which simple /home/debian/bin/simple debian [ at ] beaglebone:~$ simple Simple Program One thing i can do is just to add the directory by default in the image. debian [ at ] beaglebone:~$ echo $PATH /home/debian/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games Just use: dpkg-reconfigure tzdata or: echo "Europe/Zurich" > /etc/timezone dpkg-reconfigure -f noninteractive tzdata The default /etc/profile sets the gaming directories up by default. So i opted to just leave them. /usr/local/games:/usr/games The only thing i've done there, is to tweak the path to also include the root "sbin" directories too for the normal user.. Regards,
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
I think UTC would be best, but there should be clear instructions for how to change it. Most users (like me) are not Linux experts and don't know how to do many of these basic things. I though /etc/timezone seemed like the perfect place to make this change, but it turns out that was wrong. Google led me to tzselect which also looked promising, but again it was wrong. Dennis Cote
No problem, i just copied it from my other Debian page. ;) Well, technically "armhf" is still "EABI", but over "armel" it has hard floating point enabled by default. I'll fix those up, I'm just merging/pushing all my notes/fixes/etc from yesterday right now. ;) Regards,
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
Here you go: xinput_calibrator.log pastebin.com/EZ4uSu4W xinput.txt pastebin.com/ZBDXGkt3 lsusb.txt pastebin.com/0UthnPqZ You are missing my point. These commands are already in the default .profile created for the debian user. See the pastebin.com/kjDXbEpJ for a copy of mine. I added the TZ environment variable at the end. ls ~ shows my bin directory exists env | grep HOME shows the HOME variable as /home/debian env | grep PATH shows the PATH as /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games The .profile should be adding /home/debian/bin to the path, but it is not. It is also not adding the TZ variable to the environment. BTW, we could probably remove the two games directories from the default PATH as well. I don't think many users will be using BBB for gaming. Dennis Cote
Ah ha... there is the nugget of truth I was looking for. Yes, this is the LXTerminal under LXDE. I checked and the .profile *is* executed for my serial console. So how does one get the same path for the LXTerminal as you get using a serial terminal? Also, is an ssh terminal a login shell, or is like the X terminal? No need to set the variable then export it either, just do it all in one I know that now, but yesterday when I was trying to get the timezone set correctly I ran the tzselect command (which seemed logical). This is the output of that command: The following information has been given: Canada Mountain Time - Alberta, east British Columbia west Saskatchewan Therefore TZ='America/Edmonton' will be used. Local time is now:Fri Mar 14 09:31:43 MDT 2014. Universal Time is now:Fri Mar 14 15:31:43 UTC 2014. Is the above information OK? 1) Yes 2) No #? 1 You can make this change permanent for yourself by appending the line TZ='America/Edmonton'; export TZ to the file '.profile' in your home directory; then log out and log in again. Here is that TZ value again, this time on standard output so that you can use the /usr/bin/tzselect command in shell scripts: America/Edmonton So I did as it suggested. I added this line to my .profile and logged out and in. This again seemed logical. I left it in as a simple test of whether or not my .profile was executed. I will remove it now. Yes, thanks for the tip. I started by using env to dump my entire environment, and then just progressed to using grep to filter the dump, while looking into why the .profile wasn't being executed. Thanks again for the info. Dennis Cote
Answer by 5 months ago
Quoted message by Mike 5 months ago
Is this shell running within X? If so .profile isn't sourced as it's not run as login shell. I don't quite follow why you want to set the TZ variable from the user environment either. It's all handled at a system level by default. No need to set the variable then export it either, just do it all in one go. export TZ="Whatever" Also less typing to just "echo" variables.... echo $HOME $PATH Really no need for env and grep. Mike
Ahh, I've been doing it over serial/ssh.. For lxterminal (which doesn't reference .profile according to lots of bug reports). It works if i add: # set PATH so it includes user's private bin if it exists if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin:$PATH" fi into .bashrc If there is no objections i'll probably set that up by default.. Regards,
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
That's interesting, the lcd/touchscreen detect script is pretty basic, i'll have to add whitelist for some devices. Can you pastebin this file for me: /var/log/xinput_calibrator.pointercal.log and the output of "xinput" you will have to run it from x11, no serial/ssh.. Yeah, export PATH=$PATH:~/bin in ~/.profile is all you should need.. Regards,
btw, as a workaround till i can debug it with the same hardware, just run: sudo sed -i -e 's:display-setup-script=:#display-setup-script:g' /etc/lightdm/lightdm.conf And it'll stop displaying the calibrator on bootup. Regards,
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
Ah ha... there is the nugget of truth I was looking for. Yes, this is the LXTerminal under LXDE. I checked and the .profile *is* executed for my serial console. So how does one get the same path for the LXTerminal as you get using a serial terminal? Also, is an ssh terminal a login shell, or is like the X terminal? No need to set the variable then export it either, just do it all in one I know that now, but yesterday when I was trying to get the timezone set correctly I ran the tzselect command (which seemed logical). This is the output of that command: The following information has been given: Canada Mountain Time - Alberta, east British Columbia west Saskatchewan Therefore TZ='America/Edmonton' will be used. Local time is now:Fri Mar 14 09:31:43 MDT 2014. Universal Time is now:Fri Mar 14 15:31:43 UTC 2014. Is the above information OK? 1) Yes 2) No #? 1 You can make this change permanent for yourself by appending the line TZ='America/Edmonton'; export TZ to the file '.profile' in your home directory; then log out and log in again. Here is that TZ value again, this time on standard output so that you can use the /usr/bin/tzselect command in shell scripts: America/Edmonton So I did as it suggested. I added this line to my .profile and logged out and in. This again seemed logical. I left it in as a simple test of whether or not my .profile was executed. I will remove it now. Yes, thanks for the tip. I started by using env to dump my entire environment, and then just progressed to using grep to filter the dump, while looking into why the .profile wasn't being executed. Thanks again for the info. Dennis Cote
Will this add the user's bin directory to the path twice when using a serial console since .bashrc is sourced from the existing .profile? Dennis Cote
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
Ahh, I've been doing it over serial/ssh.. For lxterminal (which doesn't reference .profile according to lots of bug reports). It works if i add: # set PATH so it includes user's private bin if it exists if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin:$PATH" fi into .bashrc If there is no objections i'll probably set that up by default.. Regards,
Yeap it does.. debian [ at ] beaglebone:~$ echo $PATH /home/debian/bin:/home/debian/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games What gets sourced first? i can patch it to check.. Regards,
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
Ahh, I've been doing it over serial/ssh.. For lxterminal (which doesn't reference .profile according to lots of bug reports). It works if i add: # set PATH so it includes user's private bin if it exists if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin:$PATH" fi into .bashrc If there is no objections i'll probably set that up by default.. Regards,
I moved that section from my .profile to .bashrc since .profile will source .bashrc if it exists. So a login shell will source .profile, which will source .bashrc and add the path. A non login shell will source .bashrc directly and add the path. This seems to work for me. I'm not sure what happens for script that use #!/bin/sh since that runs dash instead of bash. The dash docs say it sources .profile on login shells so that should be OK, but for non login shells it says it looks in the ENV environment variable for the name of a file to execute. There is no such variable defined currently so it does nothing. Perhaps these commands should be put in a .shinit file and then set ENV=$HOME/.shint in the .profile file to take card of setting it for login shells, and have the .bashrc source this .shinit file for non login shells. Dennis Cote
Answer by 5 months ago
Quoted message by Dennis Cote 5 months ago
Here you go: xinput_calibrator.log pastebin.com/EZ4uSu4W xinput.txt pastebin.com/ZBDXGkt3 lsusb.txt pastebin.com/0UthnPqZ You are missing my point. These commands are already in the default .profile created for the debian user. See the pastebin.com/kjDXbEpJ for a copy of mine. I added the TZ environment variable at the end. ls ~ shows my bin directory exists env | grep HOME shows the HOME variable as /home/debian env | grep PATH shows the PATH as /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games The .profile should be adding /home/debian/bin to the path, but it is not. It is also not adding the TZ variable to the environment. BTW, we could probably remove the two games directories from the default PATH as well. I don't think many users will be using BBB for gaming. Dennis Cote
FYI, commenting out the display-setup-script line does not take effect until after you reboot. I no longer have the calibration screen on startup or logout. Thanks. Dennis Cote
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
Ahh, I've been doing it over serial/ssh.. For lxterminal (which doesn't reference .profile according to lots of bug reports). It works if i add: # set PATH so it includes user's private bin if it exists if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin:$PATH" fi into .bashrc If there is no objections i'll probably set that up by default.. Regards,
Here is a better fix: sudo sed -i -e 's:Exec=lxterminal:Exec=lxterminal -l -e bash:g' /usr/share/applications/lxterminal.desktop Regards,
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
Ahh, I've been doing it over serial/ssh.. For lxterminal (which doesn't reference .profile according to lots of bug reports). It works if i add: # set PATH so it includes user's private bin if it exists if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin:$PATH" fi into .bashrc If there is no objections i'll probably set that up by default.. Regards,
Robert, your timezone is fine for me. I am actually AZ time myself, but really simple to change via dpkg-reconfigure tzdata. Also, as for how to change some default stuff, perhaps have a web page ( html file, or maybe even a node.js thing to make it more dynamic ? ) Dennis, just so you know, you should be able to google "debian" + whatever keyword you need to know something about to find an answer. We're talking basic Linux / Debian stuff here. For example. google -> howto change debian timezone, and you will very likely find what i asked about last night "dpkg-reconfigure tzdata". Anyway, dont feel as though I am putting you down by saying this. quite the contrary actually. As I have been using Debian since the 90's and have to google many things. Especially now considering I really want to look into using systemmd.
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
Ahh, I've been doing it over serial/ssh.. For lxterminal (which doesn't reference .profile according to lots of bug reports). It works if i add: # set PATH so it includes user's private bin if it exists if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin:$PATH" fi into .bashrc If there is no objections i'll probably set that up by default.. Regards,
Sorry, I felt i was not clear in my last post . . . *Also, as for how to change some default stuff, perhaps have a web page ( html file, or maybe even a node.js thing to make it more dynamic ? )* What I mean by the above, is have an information web page on how to do various things, like how to set time zone etc. Perhaps as part of the getting started page thats already on the BBB. Even though I think Debian is one of the better distro's out there because of the fact you can simply google the answer to your questions( just one aspect actually ) I feel that having a web page linked to from the getting started page on how to change all teh default basic stuff would be super helpful for new users.
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
Ahh, I've been doing it over serial/ssh.. For lxterminal (which doesn't reference .profile according to lots of bug reports). It works if i add: # set PATH so it includes user's private bin if it exists if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin:$PATH" fi into .bashrc If there is no objections i'll probably set that up by default.. Regards,
As far as I can tell by using ps - p $$, lxterminal is already running bash, so adding -e bash shouldn't change anything. Adding the -l make it a login shell, so it sources /etc/profile and then .profile, which sources .bashrc if it exists. Without this change lxterminal runs bash as a non login shell so it sources /etc/bash.bashrc and then .bashrc instead. The /etc/bash.bashrc file setups the command prompt. What I don't understand is why an lxterminal command with no options starts a bash shell, but an lxterminal -l command starts a /bin/sh shell which is actually a dash shell. You end up with no command prompt because it doesn't run /etc/bash.bashrc. There are probably other differences. This is why you added the -e bash option. Anyway this does seem like a better fix, though anything that runs /bin/sh will still have a different PATH without the user bin directory. Dennis Cote
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
Ahh, I've been doing it over serial/ssh.. For lxterminal (which doesn't reference .profile according to lots of bug reports). It works if i add: # set PATH so it includes user's private bin if it exists if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin:$PATH" fi into .bashrc If there is no objections i'll probably set that up by default.. Regards,
dpkg-reconfigure dash -> select no.
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
Ahh, I've been doing it over serial/ssh.. For lxterminal (which doesn't reference .profile according to lots of bug reports). It works if i add: # set PATH so it includes user's private bin if it exists if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin:$PATH" fi into .bashrc If there is no objections i'll probably set that up by default.. Regards,
I did that and ended up at http://www.debian-administration.org/article/213/Changing_the_timezone_of_your_Debian_system which suggested the tzselect command (which in turn suggested adding a TZ environment variable, which in turn led to me seeing that my .profile wasn't being executed, etc). I also saw the page at https://wiki.debian.org/TimeZoneChanges but the text at the top of that page and the titles of the other sections made it seem more about checking and adapting the system to changes in the dates of daylight saving etc. I just wanted to set my timezone. The section where "dpkg-reconfigure tzdata" is mentioned has the title "Check Configured Timezone", and the text of the command itself didn't lead me to conclude it would change my timezone. Had I read in more detail I would have seem what it did, but I was skimming for something that said "this is how to change your timezone" as on the page above. No problem, no offence taken. I just want to point out that not all google searches (or searchers) lead to the best answer. Dennis Cote
Answer by 5 months ago
Quoted message by Robert Nelson 5 months ago
Ahh, I've been doing it over serial/ssh.. For lxterminal (which doesn't reference .profile according to lots of bug reports). It works if i add: # set PATH so it includes user's private bin if it exists if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin:$PATH" fi into .bashrc If there is no objections i'll probably set that up by default.. Regards,
I have very seldom run into a situation where google did not give me a correct answer. Sometimes the first hit is not always right / succinct either. It takes experience googling to know what to look for, and this does not always work either. Anyway, answers linked on debian.org, and superuser are typically succinct and correct. Also, as I had not reconfigured time zone, and dash before, or in a while i did google searches on these myself not but a few months ago. Regardless, this is all part of the learning process for everyone.
Answer by 4 months ago
Quoted message by Dennis Cote 5 months ago
Here you go: xinput_calibrator.log pastebin.com/EZ4uSu4W xinput.txt pastebin.com/ZBDXGkt3 lsusb.txt pastebin.com/0UthnPqZ You are missing my point. These commands are already in the default .profile created for the debian user. See the pastebin.com/kjDXbEpJ for a copy of mine. I added the TZ environment variable at the end. ls ~ shows my bin directory exists env | grep HOME shows the HOME variable as /home/debian env | grep PATH shows the PATH as /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games The .profile should be adding /home/debian/bin to the path, but it is not. It is also not adding the TZ variable to the environment. BTW, we could probably remove the two games directories from the default PATH as well. I don't think many users will be using BBB for gaming. Dennis Cote
Okay, quick update on this as i have the same K120 keyboard. I'm seeing this same issue on 3.8/3.13/3.14 so I just blacklisted this device. Just run: cd /opt/scripts git pull to update the xinput script.. Regards,
Answer by 4 months ago
Quoted message by Robert Nelson 5 months ago
btw, as a workaround till i can debug it with the same hardware, just run: sudo sed -i -e 's:display-setup-script=:#display-setup-script:g' /etc/lightdm/lightdm.conf And it'll stop displaying the calibrator on bootup. Regards,
Robert, I did this update and then undid the workaround (i.e. I uncommented the display-setup-script line in /etc/lightdm/lightdm.conf). Now I no longer get the calibration screen on startup and logout of LXDE, however I lose my mouse pointer when I logout. The mouse pointer works on reboot, but if I logout of LXDE I have no visible pointer on the login screen or in LXDE after I log back in. The mouse does work and I can see where it is because some items like the LXDE menu icons highlight when I hover the mouse over them, but there is no onscreen pointer visible. Clicking the mouse buttons work as expected when I can figure out where it is pointing. Is there anything else I can do to help pinpoint the problem?
Answer by 4 months ago
Quoted message by Robert Nelson 4 months ago
Okay, quick update on this as i have the same K120 keyboard. I'm seeing this same issue on 3.8/3.13/3.14 so I just blacklisted this device. Just run: cd /opt/scripts git pull to update the xinput script.. Regards,
Previously we were making the mouse pointer viable by a custom xorg.conf. However it works better if you add it via xset/xsetroot: root [ at ] beaglebone:~# cat /home/debian/.xsessionrc #!/bin/sh xset -dpms xset s off xsetroot -cursor_name left_ptr and just remove the [Option "SWCursor" "true"] line from /etc/X11/xorg.conf So for me, right now the mouse cursor works between logout/logins. Regards,
Answer by 4 months ago
Quoted message by Dennis Cote 4 months ago
Robert, I did this update and then undid the workaround (i.e. I uncommented the display-setup-script line in /etc/lightdm/lightdm.conf). Now I no longer get the calibration screen on startup and logout of LXDE, however I lose my mouse pointer when I logout. The mouse pointer works on reboot, but if I logout of LXDE I have no visible pointer on the login screen or in LXDE after I log back in. The mouse does work and I can see where it is because some items like the LXDE menu icons highlight when I hover the mouse over them, but there is no onscreen pointer visible. Clicking the mouse buttons work as expected when I can figure out where it is pointing. Is there anything else I can do to help pinpoint the problem?
Robert, My .xsessionrc file looks identical to yours, and I did not have "SWCursor" anywhere in my xorg.conf file, so there was nothing to remove. My mouse pointer definitely becomes invisible when I logout. Any other ideas?
Answer by 4 months ago
Quoted message by Dennis Cote 4 months ago
Robert, I did this update and then undid the workaround (i.e. I uncommented the display-setup-script line in /etc/lightdm/lightdm.conf). Now I no longer get the calibration screen on startup and logout of LXDE, however I lose my mouse pointer when I logout. The mouse pointer works on reboot, but if I logout of LXDE I have no visible pointer on the login screen or in LXDE after I log back in. The mouse does work and I can see where it is because some items like the LXDE menu icons highlight when I hover the mouse over them, but there is no onscreen pointer visible. Clicking the mouse buttons work as expected when I can figure out where it is pointing. Is there anything else I can do to help pinpoint the problem?
okay, so when i switch back to v3.8, i see this now too.. Weird, as v3.13.x it works. Might just have to go back to the xorg.conf workaround. Regards,
Answer by 4 months ago
Quoted message by Dennis Cote 4 months ago
Robert, I did this update and then undid the workaround (i.e. I uncommented the display-setup-script line in /etc/lightdm/lightdm.conf). Now I no longer get the calibration screen on startup and logout of LXDE, however I lose my mouse pointer when I logout. The mouse pointer works on reboot, but if I logout of LXDE I have no visible pointer on the login screen or in LXDE after I log back in. The mouse does work and I can see where it is because some items like the LXDE menu icons highlight when I hover the mouse over them, but there is no onscreen pointer visible. Clicking the mouse buttons work as expected when I can figure out where it is pointing. Is there anything else I can do to help pinpoint the problem?
Robert, I have done some more testing. I have discovered that I do have a mouse pointer on the login screen after the first logout after a reboot, and I have a mouse pointer when I log in again. If I log out again, I have no visible mouse pointer on the login screen, and no mouse pointer after I log back in. It remains the same on subsequent logout/logins until I reboot again. Then I can logout and back in one more time before I lose my mouse pointer. Any ideas?
Answer by 4 months ago
Quoted message by Dennis Cote 4 months ago
Robert, I did this update and then undid the workaround (i.e. I uncommented the display-setup-script line in /etc/lightdm/lightdm.conf). Now I no longer get the calibration screen on startup and logout of LXDE, however I lose my mouse pointer when I logout. The mouse pointer works on reboot, but if I logout of LXDE I have no visible pointer on the login screen or in LXDE after I log back in. The mouse does work and I can see where it is because some items like the LXDE menu icons highlight when I hover the mouse over them, but there is no onscreen pointer visible. Clicking the mouse buttons work as expected when I can figure out where it is pointing. Is there anything else I can do to help pinpoint the problem?
Robert, More test results. I googled and found many references to adding 'Option "HWCursor" "off"' to the device section of xorg.conf as a fix for the disappearing mouse cursor issue in Debian/Ubuntu/Mint etc. These all seemed to be for PC based systems thought. I tried it and it did not work. I lost my mouse cursor on every logout. I added the line you suggested to remove earlier 'Option "SWCursor" "true"' to the device section of my xorg.conf. This appears to have fixed the problem. I can logout and back in many times in a row, and haven't lost my mouse cursor since. HTH Dennis Cote
Answer by 4 months ago
Quoted message by Dennis Cote 4 months ago
Robert, I did this update and then undid the workaround (i.e. I uncommented the display-setup-script line in /etc/lightdm/lightdm.conf). Now I no longer get the calibration screen on startup and logout of LXDE, however I lose my mouse pointer when I logout. The mouse pointer works on reboot, but if I logout of LXDE I have no visible pointer on the login screen or in LXDE after I log back in. The mouse does work and I can see where it is because some items like the LXDE menu icons highlight when I hover the mouse over them, but there is no onscreen pointer visible. Clicking the mouse buttons work as expected when I can figure out where it is pointing. Is there anything else I can do to help pinpoint the problem?
OH Fun! ;) I've had reports that xorg.conf change was causing lockup's when moving icons around, hence we changed it to the .xsessonrc workaround in the last week. Regards,
Answer by 4 months ago
Quoted message by Dennis Cote 4 months ago
Robert, I did this update and then undid the workaround (i.e. I uncommented the display-setup-script line in /etc/lightdm/lightdm.conf). Now I no longer get the calibration screen on startup and logout of LXDE, however I lose my mouse pointer when I logout. The mouse pointer works on reboot, but if I logout of LXDE I have no visible pointer on the login screen or in LXDE after I log back in. The mouse does work and I can see where it is because some items like the LXDE menu icons highlight when I hover the mouse over them, but there is no onscreen pointer visible. Clicking the mouse buttons work as expected when I can figure out where it is pointing. Is there anything else I can do to help pinpoint the problem?
Robert, I have just noticed now that my BBB is no longer blanking the HDMI output after a period of inactivity. Prior to these changes the display would blank after some period of inactivity, and I would have to move my mouse to get it to start sending video again. It has been sitting unused for an hour or more now (there is an ssh session open), and it has not blanked the screen. I googled Debian screen blanking and discovered what I think your .xsessionrc commands are doing. xset s off # don't activate screensaver xset -dpms # disable DPMS (Energy Star) features. xset s noblank # don't blank the video device I suspect you have disabled the DPMS features that were shutting down the HDMI video output. I don't need a screen saver, but I would like the video to blank after a while. So I executed an xset +dpms command and then an xset q to check the current settings and verify that DPMS was enabled. With DPMS enabled I waited for 600 seconds (10 minutes), and my display blanked as I wanted. I see that many people are searching for a way to disable screen blanking, so I think this is one of those things that should be added to your FAQ for simple ways to accomplish basic setup changes. I think the display should blank by default out of the box both for the energy savings (135,000 BBB boards could be preventing their monitors from going to low power mode) and to provide a similar experience to what one gets using a Mac or PC. The FAQ should explain how to change it, both to blank or not blank. Is there any other reason you are disabling DPMS?
Answer by 4 months ago
How can I make the microSD image to not copy the image to the eMMC of my Beaglebone Black? That is, by default, when I insert the SD card with this Debian image, and then power the BBB, it will automatically start flashing the Debian image to the BBB internal disk (eMMC). I notice it because after some time the 4 leds stay lit, meaning it has completed the process. I don't want it to happen because I want to use Debian directly from the bootable SD card, and keep the eMMC intact. (probably I just need to delete the script that flashes the image to the eMMC, but where is it?) Em quarta-feira, 5 de março de 2014 19h51min19s UTC-3, Jason Kridner escreveu:
Answer by 4 months ago
I really like the 2014-03-19 image. It solves most of the problems I was having with Ubuntu and Angstrom. I am now able to connect wirelessly to WPA secured networks using Adafruit's dongle while tethered via a USB cable! This will make developing and debugging an autonomous robot that uses computer vision infinitely easier. I do have a few ideas for making the image slightly better. First, any chance you can install xrdp? This would allow my students to remote into the BeagleBone without having to access the Internet? Second, if I remember correctly it looks like the version designed to run from the SD card lists wlan0 within Wicd, but the eMMC version does not. IAny chance you can list wlan0 within Wicd for both versions? Third, I had to input the passphrase into Wicd, generate the PSK using wpa_passphrase, and then add the PSK into Wicd. Not sure why. Maybe I'm doing something wrong, but I suspect it's some sort of glitch with Wicd.
Answer by 4 months ago
Sad to say that I had my wifi dongle working yesterday, but despite hours of effort today, I was unable to get it working.
Answer by 4 months ago
I see a 2014-03-26 image has appeared. Unfortunately when I flash [1] and boot from it, it appears to never leave u-boot. Just 3 LEDs light and it just hangs. I try this on two SD cards and both had the same behavior. --Mark [1] http://rcn-ee.net/deb/testing/2014-03-26/bone-debian-7.4-2014-03-26-2gb.img.xz
Answer by 4 months ago
Quoted message by Mbbackus 4 months ago
I really like the 2014-03-19 image. It solves most of the problems I was having with Ubuntu and Angstrom. I am now able to connect wirelessly to WPA secured networks using Adafruit's dongle while tethered via a USB cable! This will make developing and debugging an autonomous robot that uses computer vision infinitely easier. I do have a few ideas for making the image slightly better. First, any chance you can install xrdp? This would allow my students to remote into the BeagleBone without having to access the Internet? Second, if I remember correctly it looks like the version designed to run from the SD card lists wlan0 within Wicd, but the eMMC version does not. IAny chance you can list wlan0 within Wicd for both versions? Third, I had to input the passphrase into Wicd, generate the PSK using wpa_passphrase, and then add the PSK into Wicd. Not sure why. Maybe I'm doing something wrong, but I suspect it's some sort of glitch with Wicd.
Humm, that means "uenvcmd" wasn't defined in uEnv.txt.. I wonder how that happened (1). Does it help if you hold down the boot button? What do you have flashed to the eMMC? (i have it setup to be compatible with atleast Angstrom's 2013.06.20 u-boot) 1: https://github.com/beagleboard/image-builder/blob/master/target/boot/beagleboard.org.txt#L45 Testing now too.. Regards,
Answer by 4 months ago
Quoted message by Mark A. Yoder 4 months ago
I see a 2014-03-26 image has appeared. Unfortunately when I flash [1] and boot from it, it appears to never leave u-boot. Just 3 LEDs light and it just hangs. I try this on two SD cards and both had the same behavior. --Mark [1] http://rcn-ee.net/deb/testing/2014-03-26/bone-debian-7.4-2014-03-26-2gb.img.xz
Okay tested, and i see the issue.. To save bandwidth i mirror the kernel *.deb locally, which runs/updates at midnight, so the kernel never got installed. So i just need to add that error condition and just rerun the script again.. Thanks for testing, sorry for the error! ************************* U-Boot SPL 2014.04-rc2-00015-g99288ca (Mar 12 2014 - 09:49:41) reading args spl_load_image_fat_os: error reading image args, err - -1 reading u-boot.img reading u-boot.img U-Boot 2014.04-rc2-00015-g99288ca (Mar 12 2014 - 09:49:41) I2C: ready DRAM: 512 MiB NAND: 0 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 *** Warning - readenv() failed, using default environment Net: <ethaddr> not set. Validating first E-fuse MAC cpsw, usb_ether Hit any key to stop autoboot: 0 gpio: pin 53 (gpio 53) value is 1 mmc0 is current device gpio: pin 54 (gpio 54) value is 1 SD/MMC found on device 0 reading uEnv.txt 1390 bytes read in 5 ms (271.5 KiB/s) gpio: pin 55 (gpio 55) value is 1 Loaded environment from uEnv.txt Importing environment from mmc ... Checking if uenvcmd is set ... gpio: pin 56 (gpio 56) value is 1 Running uenvcmd ... reading zImage ** Unable to read file zImage ** reading initrd.img ** Unable to read file initrd.img ** reading /dtbs/am335x-boneblack.dtb ** Unable to read file /dtbs/am335x-boneblack.dtb ** Bad Linux ARM zImage magic! uenvcmd was not defined in uEnv.txt ... gpio: pin 56 (gpio 56) value is 0 gpio: pin 55 (gpio 55) value is 0 gpio: pin 54 (gpio 54) value is 0 mmc1(part 0) is current device gpio: pin 54 (gpio 54) value is 1 SD/MMC found on device 1 ** No partition table - mmc 1 ** Checking if uenvcmd is set ... gpio: pin 56 (gpio 56) value is 1 Running uenvcmd ... ** No partition table - mmc 1 ** ** No partition table - mmc 1 ** ** No partition table - mmc 1 ** Bad Linux ARM zImage magic! uenvcmd was not defined in uEnv.txt ... Booting from nand ... no devices available no devices available Bad Linux ARM zImage magic! U-Boot# ************ Regards,
Answer by 4 months ago
Quoted message by Robert Nelson 4 months ago
Humm, that means "uenvcmd" wasn't defined in uEnv.txt.. I wonder how that happened (1). Does it help if you hold down the boot button? What do you have flashed to the eMMC? (i have it setup to be compatible with atleast Angstrom's 2013.06.20 u-boot) 1: https://github.com/beagleboard/image-builder/blob/master/target/boot/beagleboard.org.txt#L45 Testing now too.. Regards,
Thanks Robert. I'll watch for the update. --Mark
Answer by 4 months ago
Quoted message by Robert Nelson 4 months ago
Okay tested, and i see the issue.. To save bandwidth i mirror the kernel *.deb locally, which runs/updates at midnight, so the kernel never got installed. So i just need to add that error condition and just rerun the script again.. Thanks for testing, sorry for the error! ************************* U-Boot SPL 2014.04-rc2-00015-g99288ca (Mar 12 2014 - 09:49:41) reading args spl_load_image_fat_os: error reading image args, err - -1 reading u-boot.img reading u-boot.img U-Boot 2014.04-rc2-00015-g99288ca (Mar 12 2014 - 09:49:41) I2C: ready DRAM: 512 MiB NAND: 0 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 *** Warning - readenv() failed, using default environment Net: <ethaddr> not set. Validating first E-fuse MAC cpsw, usb_ether Hit any key to stop autoboot: 0 gpio: pin 53 (gpio 53) value is 1 mmc0 is current device gpio: pin 54 (gpio 54) value is 1 SD/MMC found on device 0 reading uEnv.txt 1390 bytes read in 5 ms (271.5 KiB/s) gpio: pin 55 (gpio 55) value is 1 Loaded environment from uEnv.txt Importing environment from mmc ... Checking if uenvcmd is set ... gpio: pin 56 (gpio 56) value is 1 Running uenvcmd ... reading zImage ** Unable to read file zImage ** reading initrd.img ** Unable to read file initrd.img ** reading /dtbs/am335x-boneblack.dtb ** Unable to read file /dtbs/am335x-boneblack.dtb ** Bad Linux ARM zImage magic! uenvcmd was not defined in uEnv.txt ... gpio: pin 56 (gpio 56) value is 0 gpio: pin 55 (gpio 55) value is 0 gpio: pin 54 (gpio 54) value is 0 mmc1(part 0) is current device gpio: pin 54 (gpio 54) value is 1 SD/MMC found on device 1 ** No partition table - mmc 1 ** Checking if uenvcmd is set ... gpio: pin 56 (gpio 56) value is 1 Running uenvcmd ... ** No partition table - mmc 1 ** ** No partition table - mmc 1 ** ** No partition table - mmc 1 ** Bad Linux ARM zImage magic! uenvcmd was not defined in uEnv.txt ... Booting from nand ... no devices available no devices available Bad Linux ARM zImage magic! U-Boot# ************ Regards,
Just pushed out tested locally: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-03-27 Regards,
Answer by 4 months ago
Quoted message by Mark A. Yoder 4 months ago
Thanks Robert. I'll watch for the update. --Mark
It's working. Thanks! --Mark
Answer by 4 months ago
Quoted message by Mark A. Yoder 4 months ago
Thanks Robert. I'll watch for the update. --Mark
I downloaded and tested the March 27th image today. Thanks for including xrdp-it made testing wifi go much faster. Here's what I found. - I was able to connect to a WPA2 secured network at the school where I teach - I was unable to connect to my cell phone when unsecured (Android portable wifi hotspot) - I was able to connect to my cell phone if I secured the connection (WPA2 PSK) - I was unable to connect to a WPA2 secured network at home - One of my students was able to connect to the WPA2 secured school network, another was unable to connect - The students that was unable to connect to the school network was also unable to connect to my cell phone (secured as well-didn't try unsecured) - I was able to create an ad-hoc network (at least I think it did because it showed up in Wicd) We were all using the tiny Adafruit dongles and tethered to BeagleBones via USB. Whenever we were unable to connect, we could see the connection-it just timed out when trying to get an IP (unsecured networks) or authenticating (secured network). Any ideas? I also tried setting up an ad-hoc network. It showed up within Wicd, but I wasn't able to detect it with a computer, my Android cell phone, or an iPhone. Is ad-hoc working for anybody else? Given the inconsistency, I'm guessing the problem is hardware (the dongle), so I ordered a few of the Netgear WNA1100 dongles. Should have them in a couple of weeks. Also, looks like the eMMC version doesn't have Wicd functioning out of the box. Thanks for all the work you're putting into this.
Answer by 4 months ago
Quoted message by Mark A. Yoder 4 months ago
Thanks Robert. I'll watch for the update. --Mark
Robert, Thanks for the flurry of updated Debian images for testing (3/4, 3/19, 3/27). I am happily trying the different images, but when I download the image and "start from scratch" it takes me several hours to get back to the point where I can use my system again. I use Open Lighting Architecture<http://www.openlighting.org/> and it takes me about 4+hours to do everything necessary to compile it from source. Could I update to your newest distros somehow by running a script (Mar4 -> Mar19 -> Mar27)? ... or is it necessary to wipe everything out and reflash the image from scratch? Some of my BBBs I flash the eMMC and some of them I boot directly from the uSD. Thx!! (and sorry if this has already been answered somewhere). President, Volt Vision www.voltvision.com
Answer by 4 months ago
Quoted message by Robert Nelson 4 months ago
Just pushed out tested locally: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-03-27 Regards,
On Fri, Mar 28, 2014 at 9:04 AM, Steve French of Volt Vision cd /opt/scripts/fixes git pull sudo ./debian-2014-03-04-to-2014-03-19.sh sudo ./debian-2014-03-19-to-2014-03-27.sh The only thing it doesn't do is update the bootloader from v2013.10 in 2014-03-04 to v2014.04-rc in 2014-03-19+ For that: cd /opt/scripts/tools/ sudo ./update_bootloader.sh Regards,
Answer by 4 months ago
Quoted message by Steve French Of Volt Vision 4 months ago
Robert, Thanks for the flurry of updated Debian images for testing (3/4, 3/19, 3/27). I am happily trying the different images, but when I download the image and "start from scratch" it takes me several hours to get back to the point where I can use my system again. I use Open Lighting Architecture<http://www.openlighting.org/> and it takes me about 4+hours to do everything necessary to compile it from source. Could I update to your newest distros somehow by running a script (Mar4 -> Mar19 -> Mar27)? ... or is it necessary to wipe everything out and reflash the image from scratch? Some of my BBBs I flash the eMMC and some of them I boot directly from the uSD. Thx!! (and sorry if this has already been answered somewhere). President, Volt Vision www.voltvision.com
PS: you can see to review the change here: https://github.com/RobertCNelson/boot-scripts/tree/master/fixes Regards,
Answer by 4 months ago
Quoted message by Steve French Of Volt Vision 4 months ago
Robert, Thanks for the flurry of updated Debian images for testing (3/4, 3/19, 3/27). I am happily trying the different images, but when I download the image and "start from scratch" it takes me several hours to get back to the point where I can use my system again. I use Open Lighting Architecture<http://www.openlighting.org/> and it takes me about 4+hours to do everything necessary to compile it from source. Could I update to your newest distros somehow by running a script (Mar4 -> Mar19 -> Mar27)? ... or is it necessary to wipe everything out and reflash the image from scratch? Some of my BBBs I flash the eMMC and some of them I boot directly from the uSD. Thx!! (and sorry if this has already been answered somewhere). President, Volt Vision www.voltvision.com
Another option is to put your lighting code on a network file share, or you can rsync the build directory to a server somewhere. You'll probably have to re-run some of the build steps (like the install part) when switching to a clean OS, but it ought to take much less than 4 hours to setup from scratch, and you shouldn't have to actually recompile anything (which is typically _slow_ on the BBB). I worked this way when getting LinuxCNC running on the BBB. I mounted a home directory via nfs from a remote server, and I was able to swap between various boards and OS installs while keeping a consistent development environment. This also let me use some tools running on full-blown Linux and Windows systems that would have been a bit heavy for the BBB (my regular text editor, some graphical git utilities, etc).
Answer by 4 months ago
Quoted message by Steve French Of Volt Vision 4 months ago
Robert, Thanks for the flurry of updated Debian images for testing (3/4, 3/19, 3/27). I am happily trying the different images, but when I download the image and "start from scratch" it takes me several hours to get back to the point where I can use my system again. I use Open Lighting Architecture<http://www.openlighting.org/> and it takes me about 4+hours to do everything necessary to compile it from source. Could I update to your newest distros somehow by running a script (Mar4 -> Mar19 -> Mar27)? ... or is it necessary to wipe everything out and reflash the image from scratch? Some of my BBBs I flash the eMMC and some of them I boot directly from the uSD. Thx!! (and sorry if this has already been answered somewhere). President, Volt Vision www.voltvision.com
+1 for NFS mounted shares. I like to share out a rootfs for my BBB, and then run Samba from the server so I can map the drive on Windows to make things easier for me. Since I run many dev tools on Windows, including a cross compile setup. On Fri, Mar 28, 2014 at 7:25 AM, Charles Steinkuehler <
Answer by 4 months ago
Quoted message by Robert Nelson 4 months ago
Just pushed out tested locally: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-03-27 Regards,
My BeagleBone part of a primitive robot with a breadboard strapped to the top, and servo motors underneath. The wifi dongle was between both. For this reason, I dug out my unpowered USB hub and used it as an extender to get the wifi dong'e away from all the metal. I powered the beagle bone with an external power supply and remoted into it via usb. I was able to get the Adafruit dongle to connect to my secured home network 1 out of three times this time around as well as a secured hotspot hosted by my phone. This was better than the netgrear wna1100 which was only able to connect to the secured hotspot (not my regular home network). Neither was able to connect to an unsecured hotspot. Attempts to connect via wifi also seem to cause the BeagleBone to freeze up frequently. Any ideas? Also, it would be really handy if the default user was root (like on Angstrom) so that I didn't have to type sudo su before most terminal commands. This would also allow me to open files more easily. I'm guessing this would also allow the user to reboot and shutdown the beaglebone, options which are missing from LXDE at this point, and which cannot be execute from the command line using the debian user.
Answer by 4 months ago
Quoted message by Mbbackus 4 months ago
I downloaded and tested the March 27th image today. Thanks for including xrdp-it made testing wifi go much faster. Here's what I found. - I was able to connect to a WPA2 secured network at the school where I teach - I was unable to connect to my cell phone when unsecured (Android portable wifi hotspot) - I was able to connect to my cell phone if I secured the connection (WPA2 PSK) - I was unable to connect to a WPA2 secured network at home - One of my students was able to connect to the WPA2 secured school network, another was unable to connect - The students that was unable to connect to the school network was also unable to connect to my cell phone (secured as well-didn't try unsecured) - I was able to create an ad-hoc network (at least I think it did because it showed up in Wicd) We were all using the tiny Adafruit dongles and tethered to BeagleBones via USB. Whenever we were unable to connect, we could see the connection-it just timed out when trying to get an IP (unsecured networks) or authenticating (secured network). Any ideas? I also tried setting up an ad-hoc network. It showed up within Wicd, but I wasn't able to detect it with a computer, my Android cell phone, or an iPhone. Is ad-hoc working for anybody else? Given the inconsistency, I'm guessing the problem is hardware (the dongle), so I ordered a few of the Netgear WNA1100 dongles. Should have them in a couple of weeks. Also, looks like the eMMC version doesn't have Wicd functioning out of the box. Thanks for all the work you're putting into this.
The is problem with the default 3.8 kernel, if your not using any cape's switch to the 3.13.x based kernel cd /opt/script/tools/ git pull sudo ./update_kernel.sh --beta-kernel There is a default root user (no password like Angstrom) we just don't log into that user via lxde. Regards,
Answer by 4 months ago
Quoted message by Mbbackus 4 months ago
I downloaded and tested the March 27th image today. Thanks for including xrdp-it made testing wifi go much faster. Here's what I found. - I was able to connect to a WPA2 secured network at the school where I teach - I was unable to connect to my cell phone when unsecured (Android portable wifi hotspot) - I was able to connect to my cell phone if I secured the connection (WPA2 PSK) - I was unable to connect to a WPA2 secured network at home - One of my students was able to connect to the WPA2 secured school network, another was unable to connect - The students that was unable to connect to the school network was also unable to connect to my cell phone (secured as well-didn't try unsecured) - I was able to create an ad-hoc network (at least I think it did because it showed up in Wicd) We were all using the tiny Adafruit dongles and tethered to BeagleBones via USB. Whenever we were unable to connect, we could see the connection-it just timed out when trying to get an IP (unsecured networks) or authenticating (secured network). Any ideas? I also tried setting up an ad-hoc network. It showed up within Wicd, but I wasn't able to detect it with a computer, my Android cell phone, or an iPhone. Is ad-hoc working for anybody else? Given the inconsistency, I'm guessing the problem is hardware (the dongle), so I ordered a few of the Netgear WNA1100 dongles. Should have them in a couple of weeks. Also, looks like the eMMC version doesn't have Wicd functioning out of the box. Thanks for all the work you're putting into this.
What is the problem with the default kernel? That wifi doesn't work good in general, that it doesn't connect to unsecured networks, that Wicd is buggy and will freeze up the BeagleBone? I went ahead and updated the kernel. I am now able to connect to secured and unsecured networks using the Adafruit dongle. I had limited success with the netgear wna1100 which definitely does NOW work better than the Adafruit dongle. The UWN200 also came in the mail today, but the BeagleBone was unable to detect it. Is it supposed to run out of the box on the newer images, or do I have to implement some sort of fix? The adafruit dongle shows up as wlan0, and the netgear shows up as wlan1. I read that the uwn200 is supposed to show up as ra0, but when I switch wicd accordingly, it still doesn't detect the dongle, and there's no wifi when I run ifconfig. Also, is there any way to log into lxde using the root user? That would save me and my students some typing and other problems (such as opening certain files with leafpad, etc.). Again, thanks for all the work you're putting into this image. You're ironing out a lot of the kinds that my students have been stumbling over.
Answer by 4 months ago
Quoted message by Mbbackus 4 months ago
I downloaded and tested the March 27th image today. Thanks for including xrdp-it made testing wifi go much faster. Here's what I found. - I was able to connect to a WPA2 secured network at the school where I teach - I was unable to connect to my cell phone when unsecured (Android portable wifi hotspot) - I was able to connect to my cell phone if I secured the connection (WPA2 PSK) - I was unable to connect to a WPA2 secured network at home - One of my students was able to connect to the WPA2 secured school network, another was unable to connect - The students that was unable to connect to the school network was also unable to connect to my cell phone (secured as well-didn't try unsecured) - I was able to create an ad-hoc network (at least I think it did because it showed up in Wicd) We were all using the tiny Adafruit dongles and tethered to BeagleBones via USB. Whenever we were unable to connect, we could see the connection-it just timed out when trying to get an IP (unsecured networks) or authenticating (secured network). Any ideas? I also tried setting up an ad-hoc network. It showed up within Wicd, but I wasn't able to detect it with a computer, my Android cell phone, or an iPhone. Is ad-hoc working for anybody else? Given the inconsistency, I'm guessing the problem is hardware (the dongle), so I ordered a few of the Netgear WNA1100 dongles. Should have them in a couple of weeks. Also, looks like the eMMC version doesn't have Wicd functioning out of the box. Thanks for all the work you're putting into this.
I just thought others might want to know that switching to the 3.13.6-bone8 kernel also changes the resolution of the HDMI display output from 720p (i.e. 1280 x 720) to 1280 x 960, a 33% increase in display real estate. I suspect there is no audio at this resolution, but I have a monitor connected and not a TV, so I can't tell. HTH Dennis Cote
Answer by 4 months ago
Quoted message by Mbbackus 4 months ago
I downloaded and tested the March 27th image today. Thanks for including xrdp-it made testing wifi go much faster. Here's what I found. - I was able to connect to a WPA2 secured network at the school where I teach - I was unable to connect to my cell phone when unsecured (Android portable wifi hotspot) - I was able to connect to my cell phone if I secured the connection (WPA2 PSK) - I was unable to connect to a WPA2 secured network at home - One of my students was able to connect to the WPA2 secured school network, another was unable to connect - The students that was unable to connect to the school network was also unable to connect to my cell phone (secured as well-didn't try unsecured) - I was able to create an ad-hoc network (at least I think it did because it showed up in Wicd) We were all using the tiny Adafruit dongles and tethered to BeagleBones via USB. Whenever we were unable to connect, we could see the connection-it just timed out when trying to get an IP (unsecured networks) or authenticating (secured network). Any ideas? I also tried setting up an ad-hoc network. It showed up within Wicd, but I wasn't able to detect it with a computer, my Android cell phone, or an iPhone. Is ad-hoc working for anybody else? Given the inconsistency, I'm guessing the problem is hardware (the dongle), so I ordered a few of the Netgear WNA1100 dongles. Should have them in a couple of weeks. Also, looks like the eMMC version doesn't have Wicd functioning out of the box. Thanks for all the work you're putting into this.
Correct, hdmi audio is currently disabled with the v3.13.x patchset, so you'll get non-audio resolution options. I was seeing headache inducing screen shakes on my work monitor, will try again with v3.14.x (the patchset hasn't hit mainline yet). Regards,
Answer by 4 months ago
Quoted message by Mbbackus 4 months ago
I downloaded and tested the March 27th image today. Thanks for including xrdp-it made testing wifi go much faster. Here's what I found. - I was able to connect to a WPA2 secured network at the school where I teach - I was unable to connect to my cell phone when unsecured (Android portable wifi hotspot) - I was able to connect to my cell phone if I secured the connection (WPA2 PSK) - I was unable to connect to a WPA2 secured network at home - One of my students was able to connect to the WPA2 secured school network, another was unable to connect - The students that was unable to connect to the school network was also unable to connect to my cell phone (secured as well-didn't try unsecured) - I was able to create an ad-hoc network (at least I think it did because it showed up in Wicd) We were all using the tiny Adafruit dongles and tethered to BeagleBones via USB. Whenever we were unable to connect, we could see the connection-it just timed out when trying to get an IP (unsecured networks) or authenticating (secured network). Any ideas? I also tried setting up an ad-hoc network. It showed up within Wicd, but I wasn't able to detect it with a computer, my Android cell phone, or an iPhone. Is ad-hoc working for anybody else? Given the inconsistency, I'm guessing the problem is hardware (the dongle), so I ordered a few of the Netgear WNA1100 dongles. Should have them in a couple of weeks. Also, looks like the eMMC version doesn't have Wicd functioning out of the box. Thanks for all the work you're putting into this.
Question: For the fun of it, I updated my system to the latest build (3/31) Also updated the kernel using the script you mentioned. Then thought I would test out building and running my Hexapod code. As part of my code base I have some Sound output including Tones (beeps) using Alsa as well as Espeak... I git cloned the stuff down from my github project: https://github.com/KurtE/Raspberry_Pi (Sorry about the project name) and did the stuff in my Readme file that included sudo apt-get of the stuff for ALSA and Espeak and got everything to build. I use an external USB sound adapter. With previous builds I was able to get the sound to work by creating a sound configuration file: /etc/asound.conf pcm. with the content of: !default sysdefault:Device So far when I try it with this build I am not having much luck: Still investigating. Suggestions? Seeing messages like: kurt [ at ] beaglebone:~$ cat /etc/asound.conf !default sysdefault:Device kurt [ at ] beaglebone:~$ espeak "Hi There" ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM sysdefault ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM sysdefault ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM front ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM surround40 ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM surround41 ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM surround50 ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM surround51 ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM surround71 ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM iec958 ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM spdif ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM spdif ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM default ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM default ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM dmix ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM dmix FATAL: cannot locate cpu MHz in /proc/cpuinfo ======================================== Also not sure if it helps, but here is some of the end of dmesg: [ 2.962517] davinci_mdio 4a101000.mdio: detected phy mask fffffffe [ 2.970375] libphy: 4a101000.mdio: probed [ 2.970407] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720 [ 2.971070] Detected MACID = c8:a0:30:ac:d3:98 [ 2.972108] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 2.979252] usb 2-1: new high-speed USB device number 2 using musb-hdrc [ 2.979773] ALSA device list: [ 2.979786] No soundcards found. [ 2.981021] Freeing unused kernel memory: 444K (c0a6f000 - c0ade000) [ 3.056812] udevd[107]: starting version 175 [ 3.114061] usb 2-1: New USB device found, idVendor=05e3, idProduct=0608 [ 3.114085] usb 2-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 3.114095] usb 2-1: Product: USB2.0 Hub [ 3.118330] hub 2-1:1.0: USB hub found [ 3.118730] hub 2-1:1.0: 4 ports detected [ 3.392973] usb 2-1.1: new full-speed USB device number 3 using musb-hdrc [ 3.493606] usb 2-1.1: device v0d8c p000e is not supported [ 3.499482] usb 2-1.1: New USB device found, idVendor=0d8c, idProduct=000e [ 3.499494] usb 2-1.1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 3.499504] usb 2-1.1: Product: Generic USB Audio Device [ 3.582902] usb 2-1.2: new low-speed USB device number 4 using musb-hdrc [ 3.692068] usb 2-1.2: device v04ca p0027 is not supported [ 3.698064] usb 2-1.2: New USB device found, idVendor=04ca, idProduct=0027 [ 3.698077] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3.698087] usb 2-1.2: Product: USB Multimedia Keyboard [ 3.698097] usb 2-1.2: Manufacturer: Lite-On Technology Corp. [ 3.711944] input: Lite-On Technology Corp. USB Multimedia Keyboard as /devices/ocp.3/47400000.usb/47401c00.usb/musb-hdrc.1.auto/usb2/2-1/2-1.2/2-1.2:1.0/input/input0 [ 3.712615] hid-generic 0003:04CA:0027.0001: input,hidraw0: USB HID v1.10 Keyboard [Lite-On Technology Corp. USB Multimedia Keyboard] on usb-musb-hdrc.1.auto-1.2/input0 [ 3.723719] input: Lite-On Technology Corp. USB Multimedia Keyboard as /devices/ocp.3/47400000.usb/47401c00.usb/musb-hdrc.1.auto/usb2/2-1/2-1.2/2-1.2:1.1/input/input1 [ 3.724645] hid-generic 0003:04CA:0027.0002: input,hiddev0,hidraw1: USB HID v1.10 Device [Lite-On Technology Corp. USB Multimedia Keyboard] on usb-musb-hdrc.1.auto-1.2/input1 [ 3.802966] usb 2-1.3: new high-speed USB device number 5 using musb-hdrc [ 3.923614] usb 2-1.3: device v0cf3 p9271 is not supported [ 3.929530] usb 2-1.3: New USB device found, idVendor=0cf3, idProduct=9271 [ 3.929543] usb 2-1.3: New USB device strings: Mfr=16, Product=32, SerialNumber=48 [ 3.929553] usb 2-1.3: Product: USB2.0 WLAN [ 3.929563] usb 2-1.3: Manufacturer: ATHEROS [ 3.929572] usb 2-1.3: SerialNumber: 12345 [ 4.012998] usb 2-1.4: new low-speed USB device number 6 using musb-hdrc [ 4.122568] usb 2-1.4: device v1241 p1177 is not supported [ 4.128448] usb 2-1.4: New USB device found, idVendor=1241, idProduct=1177 [ 4.128460] usb 2-1.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 4.144196] input: HID 1241:1177 as /devices/ocp.3/47400000.usb/47401c00.usb/musb-hdrc.1.auto/usb2/2-1/2-1.4/2-1.4:1.0/input/input2 [ 4.144845] hid-generic 0003:1241:1177.0003: input,hidraw2: USB HID v1.10 Mouse [HID 1241:1177] on usb-musb-hdrc.1.auto-1.4/input0 [ 5.442099] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [ 6.028969] random: systemd urandom read with 122 bits of entropy available [ 6.170305] random: nonblocking pool is initialized [ 7.027869] udevd[249]: starting version 175 [ 8.095208] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro [ 8.376931] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0 [ 9.543643] cm109: Keymap for Komunikate KIP1000 phone loaded [ 9.566249] input: CM109 USB driver as /devices/ocp.3/47400000.usb/47401c00.usb/musb-hdrc.1.auto/usb2/2-1/2-1.1/2-1.1:1.3/input/input3 [ 9.572892] usbcore: registered new interface driver cm109 [ 9.572910] cm109: CM109 phone driver: 20080805 (C) Alfred E. Heggestad [ 9.665588] cfg80211: Calling CRDA to update world regulatory domain [ 9.843435] usb 2-1.3: ath9k_htc: Firmware htc_9271.fw requested [ 9.843549] usbcore: registered new interface driver ath9k_htc [ 10.139232] usb 2-1.3: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272 [ 10.153396] usbcore: registered new interface driver snd-usb-audio [ 10.376307] ath9k_htc 2-1.3:1.0: ath9k_htc: HTC initialized with 33 credits [ 10.616177] ath9k_htc 2-1.3:1.0: ath9k_htc: FW Version: 1.3 [ 10.616201] ath: EEPROM regdomain: 0x809c [ 10.616208] ath: EEPROM indicates we should expect a country code [ 10.616217] ath: doing EEPROM country->regdmn map search [ 10.616224] ath: country maps to regdmn code: 0x52 [ 10.616232] ath: Country alpha2 being used: CN [ 10.616238] ath: Regpair used: 0x52 [ 10.669693] ieee80211 phy0: Atheros AR9271 Rev:1 [ 18.177164] using random self ethernet address [ 18.177191] using random host ethernet address [ 18.177206] using host ethernet address: C8:A0:30:AC:D3:9A [ 18.177247] using random self ethernet address [ 18.177260] using random host ethernet address [ 18.177267] using host ethernet address: C8:A0:30:AC:D3:9A [ 18.178124] usb0: HOST MAC c8:a0:30:ac:d3:9a [ 18.178215] usb0: MAC 02:12:00:e0:2f:bc [ 18.723057] Number of LUNs=8 [ 18.723102] Mass Storage Function, version: 2009/09/11 [ 18.723121] LUN: removable file: (no medium) [ 18.723146] Number of LUNs=1 [ 18.723266] LUN: removable file: /dev/mmcblk0p1 [ 18.723276] Number of LUNs=1 [ 18.738512] g_multi gadget: Multifunction Composite Gadget [ 18.738538] g_multi gadget: g_multi ready [ 21.004172] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready [ 22.325090] type=1006 audit(1396293426.950:2): pid=1152 uid=0 old auid=4294967295 new auid=1000 old ses=4294967295 new ses=1 res=1 [ 24.335359] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 32.160962] net eth0: initializing cpsw version 1.12 (0) [ 32.163491] net eth0: phy found : id is : 0x7c0f1 [ 32.163620] libphy: PHY 4a101000.mdio:01 not found [ 32.168730] net eth0: phy 4a101000.mdio:01 not found on slave 1 [ 32.182789] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 35.243113] libphy: 4a101000.mdio:00 - Link is Up - 100/Full [ 35.243240] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 36.644092] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 37.196428] net eth0: initializing cpsw version 1.12 (0) [ 37.198577] net eth0: phy found : id is : 0x7c0f1 [ 37.198673] libphy: PHY 4a101000.mdio:01 not found [ 37.203896] net eth0: phy 4a101000.mdio:01 not found on slave 1 [ 37.214502] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 38.114541] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 39.193227] libphy: 4a101000.mdio:00 - Link is Up - 100/Full [ 39.193355] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 42.110237] wlan0: authenticate with 30:46:9a:02:49:a8 [ 42.313333] wlan0: send auth to 30:46:9a:02:49:a8 (try 1/3) [ 42.316350] wlan0: authenticated [ 42.322552] wlan0: associate with 30:46:9a:02:49:a8 (try 1/3) [ 42.326440] wlan0: RX AssocResp from 30:46:9a:02:49:a8 (capab=0x431 status=0 aid=7) [ 42.333253] wlan0: associated [ 42.333478] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Some information from aplay: kurt [ at ] beaglebone:~$ aplay -l **** List of PLAYBACK Hardware Devices **** card 1: Device [Generic USB Audio Device], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 kurt [ at ] beaglebone:~$ aplay -L null Discard all samples (playback) or generate zero samples (capture) default:CARD=Device Generic USB Audio Device, USB Audio Default Audio Device sysdefault:CARD=Device Generic USB Audio Device, USB Audio Default Audio Device front:CARD=Device,DEV=0 Generic USB Audio Device, USB Audio Front speakers surround40:CARD=Device,DEV=0 Generic USB Audio Device, USB Audio 4.0 Surround output to Front and Rear speakers surround41:CARD=Device,DEV=0 Generic USB Audio Device, USB Audio 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=Device,DEV=0 Generic USB Audio Device, USB Audio 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=Device,DEV=0 Generic USB Audio Device, USB Audio 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=Device,DEV=0 Generic USB Audio Device, USB Audio 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers iec958:CARD=Device,DEV=0 Generic USB Audio Device, USB Audio IEC958 (S/PDIF) Digital Audio Output
Answer by 4 months ago
Quoted message by Mbbackus 4 months ago
I downloaded and tested the March 27th image today. Thanks for including xrdp-it made testing wifi go much faster. Here's what I found. - I was able to connect to a WPA2 secured network at the school where I teach - I was unable to connect to my cell phone when unsecured (Android portable wifi hotspot) - I was able to connect to my cell phone if I secured the connection (WPA2 PSK) - I was unable to connect to a WPA2 secured network at home - One of my students was able to connect to the WPA2 secured school network, another was unable to connect - The students that was unable to connect to the school network was also unable to connect to my cell phone (secured as well-didn't try unsecured) - I was able to create an ad-hoc network (at least I think it did because it showed up in Wicd) We were all using the tiny Adafruit dongles and tethered to BeagleBones via USB. Whenever we were unable to connect, we could see the connection-it just timed out when trying to get an IP (unsecured networks) or authenticating (secured network). Any ideas? I also tried setting up an ad-hoc network. It showed up within Wicd, but I wasn't able to detect it with a computer, my Android cell phone, or an iPhone. Is ad-hoc working for anybody else? Given the inconsistency, I'm guessing the problem is hardware (the dongle), so I ordered a few of the Netgear WNA1100 dongles. Should have them in a couple of weeks. Also, looks like the eMMC version doesn't have Wicd functioning out of the box. Thanks for all the work you're putting into this.
I have the same problem... You could solve it? El dimecres 2 d’abril de 2014 8:09:52 UTC+2, mbba...@gmail.com va escriure:
Answer by 4 months ago
Quoted message by Mbbackus 4 months ago
I downloaded and tested the March 27th image today. Thanks for including xrdp-it made testing wifi go much faster. Here's what I found. - I was able to connect to a WPA2 secured network at the school where I teach - I was unable to connect to my cell phone when unsecured (Android portable wifi hotspot) - I was able to connect to my cell phone if I secured the connection (WPA2 PSK) - I was unable to connect to a WPA2 secured network at home - One of my students was able to connect to the WPA2 secured school network, another was unable to connect - The students that was unable to connect to the school network was also unable to connect to my cell phone (secured as well-didn't try unsecured) - I was able to create an ad-hoc network (at least I think it did because it showed up in Wicd) We were all using the tiny Adafruit dongles and tethered to BeagleBones via USB. Whenever we were unable to connect, we could see the connection-it just timed out when trying to get an IP (unsecured networks) or authenticating (secured network). Any ideas? I also tried setting up an ad-hoc network. It showed up within Wicd, but I wasn't able to detect it with a computer, my Android cell phone, or an iPhone. Is ad-hoc working for anybody else? Given the inconsistency, I'm guessing the problem is hardware (the dongle), so I ordered a few of the Netgear WNA1100 dongles. Should have them in a couple of weeks. Also, looks like the eMMC version doesn't have Wicd functioning out of the box. Thanks for all the work you're putting into this.
Yes and no. The solution was worse than the problem. Updating to the development kernel as mentioned above resulted in better support for Wifi but an unstable LXDE environment. At this point I just don't rely on Wifi.
Answer by 3 months ago
Quoted message by Dennis Cote 4 months ago
Robert, I did this update and then undid the workaround (i.e. I uncommented the display-setup-script line in /etc/lightdm/lightdm.conf). Now I no longer get the calibration screen on startup and logout of LXDE, however I lose my mouse pointer when I logout. The mouse pointer works on reboot, but if I logout of LXDE I have no visible pointer on the login screen or in LXDE after I log back in. The mouse does work and I can see where it is because some items like the LXDE menu icons highlight when I hover the mouse over them, but there is no onscreen pointer visible. Clicking the mouse buttons work as expected when I can figure out where it is pointing. Is there anything else I can do to help pinpoint the problem?
Hi Robert, I hope this isn't a repeat. I thought I posted a similar message earlier today, but it has not showed up in the group (at least for me), so I am retrying. Today I downloaded and installed a fresh copy of the latest, 2014-04-14, Debian image. Previously I had been using your update scripts to update my installation to the latest version, but I noticed there wasn't an update script for this version when I did a git pull in the /opt/scripts directory. While using the new version I noticed that I had the same problems with my mouse pointer becoming invisible whenever I log out of LXDE, and the DPMS screen blanking being disabled, that I had reported earlier. To correct this I removed the ~/.xsessionrc file to get the default, On, state for the dpms screen blanking. I also had to add the following line to the end of the Device section of the /etc/X11/xorg.conf file. Without this line I had no mouse pointer at all. Option "SWCursor" "true" I now have a mouse pointer that remains visible across LXDE logout/login cycles, and my screen now turns off after 10 minutes of inactivity. I really think this a better default setup since the BBB behave like a standard desktop PC (I have a USB keyboard and mouse, and an HDMI monitor). New users will get correct and standard operation. More experienced users can change these behaviors if they need to (to disable screen blanking on a kiosk for example), especially if there are clear instructions on how to do so. While testing the changes to the ~/.xsessionrc file I notice that I am getting a ~/.xsession-errors file created on each reboot. This file contains the following message: Openbox-Message: Unable to find a valid menu file "/usr/share/lxde/openbox/menu.xml" Dennis Cote