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.
Jason and Robert: well done for this fine upgrade! Seems like a lot of things are really coming together very quickly.
Hi Robert,
The latest BeagleBone Debian images are now posted at: http://beagleboard.org/latest-images/
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!".
timb@woodpi ~ $ iwconfig
wlan0 IEEE 802.11bgn ESSID:"Timothy & Star" Nickname:"<WIFI@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@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
Hi Robert,
The fix I suggested yesterday still leaves some debug dmesgs.I tried to eliminate DBG entirely.However, make with -DDBG removed from os/linux/config.mk lines 290:293# config for STA modeifeq ($(RT28xx_MODE),STA)--WFLAGS += -DCONFIG_STA_SUPPORT -DSCAN_SUPPORT -DDBG++WFLAGS += -DCONFIG_STA_SUPPORT -DSCAN_SUPPORTcauses build errors in /sta/sta_cfg.c:/home/tmp/DPO_MT7601U_LinuxSTA_3.0.0.4_20130913/os/linux/../../sta/sta_cfg.c:8278:4: error: implicit declaration of function âRTMPIoctlMACâ [-Werror=implicit-function-declaration]/home/tmp/DPO_MT7601U_LinuxSTA_3.0.0.4_20130913/os/linux/../../sta/sta_cfg.c:8282:4: error: implicit declaration of function âRTMPIoctlE2PROMâ [-Werror=implicit-function-declaration]/home/tmp/DPO_MT7601U_LinuxSTA_3.0.0.4_20130913/os/linux/../../sta/sta_cfg.c:8286:4: error: implicit declaration of function âRTMPIoctlRFâ [-Werror=implicit-function-declaration]This can be fixed by adding in an #ifdef DBG...#endif wrapper into:sta/sta_cfg.c line 8276:8288--++#ifdef DBG //Include if DBG oncase CMD_RTPRIV_IOCTL_MAC:RTMPIoctlMAC(pAd, pRequest);break;case CMD_RTPRIV_IOCTL_E2P:RTMPIoctlE2PROM(pAd, pRequest);break;case CMD_RTPRIV_IOCTL_RF:RTMPIoctlRF(pAd, pRequest);break;--++#endifThe above case statements need to be wrapped in an #ifdef DBG ... #endif,same as sta/sta_ioctl.c lines 2622:2638:#ifdef DBGcase RTPRIV_IOCTL_MAC:RTMP_STA_IoctlHandle(pAd, wrq, CMD_RTPRIV_IOCTL_MAC, 0,NULL, 0, RT_DEV_PRIV_FLAGS_GET(net_dev));/* RTMPIoctlMAC(pAd, wrq); */break;case RTPRIV_IOCTL_E2P:RTMP_STA_IoctlHandle(pAd, wrq, CMD_RTPRIV_IOCTL_E2P, 0,NULL, 0, RT_DEV_PRIV_FLAGS_GET(net_dev));/* RTMPIoctlE2PROM(pAd, wrq); */break;case RTPRIV_IOCTL_RF:RTMP_STA_IoctlHandle(pAd, wrq, CMD_RTPRIV_IOCTL_RF, 0,NULL, 0, RT_DEV_PRIV_FLAGS_GET(net_dev));/* RTMPIoctlRF(pAd, wrq); */break;#endif /* DBG */By the way, a quick compare of the WNA1100 (22% RX dropped) and UWN200 (<4% RX dropped).Looks like the big antenna makes a difference!
Trying to run i2cdetect but keep getting:Error: Can't use SMBus Quick Write command on this bus
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.
Doesn't really make a difference for 3.8 thou, as you see..
Best to just switch to v3.13.x
--
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
"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.
Yeah this annoyance..
What brand of microSD cards are you using?
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.
There is a line that says:systemd=quiet init=/lib/systemd/systemdI'm not sure if you mean to remove the quiet from this line, or perhaps something else.
Since you seem t think the problem is SD card specific, I will try again with a different card.
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
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..
Which brings up a fun question. What default timezone do you guys
want? Or is "utc" generic enough?
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...
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.
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. 😠 A pitty, for I would have speared a lot of time.
All the Best
Hajo
---
... indessen wandelt harmlos droben das Gestirn
... http://hajos-kontrapunkte.blogspot.com/
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/VRqGZbXBK1Q/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.
--
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/VRqGZbXBK1Q/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.
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..
I've started an offical page at:
http://elinux.org/Beagleboard:BeagleBoneBlack_Debian
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.
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..
Yeap it does..
debian@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..
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.
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
Here is a better fix:
sudo sed -i -e 's:Exec=lxterminal:Exec=lxterminal -l -e bash:g'
/usr/share/applications/lxterminal.desktop
--
google -> howto change debian timezone, and you will very likely find what i asked about last night "dpkg-reconfigure tzdata".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.
Anyway, dont feel as though I am putting you down by saying this. quite the contrary actually.
--
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..
However it works better if you add it via xset/xsetroot:
root@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
My mouse pointer definitely becomes invisible when I logout.Any other ideas?
Might just have to go back to the xorg.conf
workaround.
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.
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.
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:Clicking the link or visiting http://192.168.7.2, you'll see the familiar on-board served documentation:
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: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):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@beaglebone# cd /opt/source/Userspace-Arduino/arduino-makefile/examples/Blinkroot@beaglebone# perl -i -pe 's/13/14/g' Blink.inoroot@beaglebone# makeroot@beaglebone# ./build-userspace/Blink.elfFor 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!
On Mar 23, 2014 10:36 PM, "Ramon Mendes" <midiw...@gmail.com> wrote:
>
> 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?)
That's why there are two separate downloads. To convert the flasher image to not flash. Just remove the flash-emmc text file from the fat partition.
>
>
> Em quarta-feira, 5 de março de 2014 19h51min19s UTC-3, Jason Kridner escreveu:
>>
>> 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:
>>
>>
>>
>>
>> Clicking the link or visiting http://192.168.7.2, you'll see the familiar on-board served documentation:
>>
>>
>>
>> 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:
>>
>>
>>
>> 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):
>>
>>
>>
>> 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@beaglebone# cd /opt/source/Userspace-Arduino/arduino-makefile/examples/Blink
>> root@beaglebone# perl -i -pe 's/13/14/g' Blink.ino
>> root@beaglebone# make
>> root@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!
>>
>>
>>