debian: test images (2014-01-10)

Lets keep this going, round 4...

First, for tracking please report all bugs to:
http://bugs.elinux.org/projects/debian-image-releases

Fixes:
3.8.13-bone37 -> 3.8.13-bone39
* rs485 support from Micka
* dir-changeable propery for gpio-of-helper from Charles
* cape-bone-proto from me *(new default pinmux)

New Packages:
python-pip, python-setuptools, python2.7-dev

Fixes:
systemd: limit journal to 8Mb (should fix ever expandign /var/logs issues)
cape-bone-proto loaded on bootup by /etc/default/capemgr
chromium: 32.0.1700.76 -> 32.0.1700.102
nodejs: 0.10.24 -> 0.10.25
https://github.com/beagleboard/am335x_pru_package.git >
/opt/source/am335x_pru_package
multiarch: added /lib/ld-linux.so.3 (for those HelloWorld users with
the wrong gcc "armel" compiler..)
Adafruit_BBIO installed
default apache moved from port 80 to 8080 (bonescript.socket takes over port 80)
"grow_partition.sh" script for users of the microSD image..
* cd /opt/scripts/
* git pull
* ./tools/grow_partition.sh
* sudo reboot
* (after a few minutes, df -h should use the whole disk..)
bonescript-autorun.service enabled

LCD3/LCD4/LCD7 users, xinput_calibrator is installed by default..
Can you please compare 3.8.13-bone36 with 3.8.13-bone39 to test
Micka's touchcreen fix?

I've tried to make it very easy to test via:

cd /opt/scripts/tools
sudo ./update_kernel.sh --kernel v3.8.13-bone36
sudo rm /etc/pointercal.xinput
sudo reboot

cd /opt/scripts/tools
sudo ./update_kernel.sh --kernel v3.8.13-bone39
sudo rm /etc/pointercal.xinput
sudo reboot

So please compare and contrast bone36/bone39, as we really need
testing from users..

Camera people (3.1MP and RadiumBoards):
What userspace programs are we missing? gstreamer? OpenCV plugins?

I really want to include a default shell script that'll take a picture
and allow end users to validate the 3.1/Radium capes work.. (it'll be
installed under /opt/scripts/capes/) Or even some html5 bone101
voodoo and show the image in the browser window?

Questions? Should we switch to connman? (i'm still testing this too..)

To test:
apt-get remove wicd-* --purge
apt-get install connman
(no good gui with connman)

Does your "cape" work?

Does your wifi adapter work? Are we missing it's firmware?

So go forward and test the first "beta" release. There are 3 files on
the web server, depending on what you want to do. Using the same
standard procedure found here:
http://elinux.org/Beagleboard:Updating_The_Software

http://rcn-ee.net/deb/testing/2014-01-29/

3cc218e9303c6823035585364e2de2c0
./BBB-eMMC-flasher-debian-7.3-2014-01-29-2gb.img.xz
d7e00474379a85edcf6385bc9584466c ./bone-debian-7.3-2014-01-29-2gb.img.xz
2d0c043b311cc31bd6286c4c2058b174 ./debian-7.3-lxde-armhf-2014-01-29.tar.xz

An eMMC "flasher" which can be installed to any 2GB or greater microSD
card. [BBB-eMMC-flasher-debian-7.3-2014-01-29-2gb.img.xz]

http://rcn-ee.net/deb/testing/2014-01-29/BBB-eMMC-flasher-debian-7.3-2014-01-29-2gb.img.xz

It takes about 10-15 Minutes to dd microSD (2GB), 15 minutes to flash
eMMC (look for full 4 LED's)

2GB standalone image that can be flashed to any 2GB or greater.
[bone-debian-7.3-2014-01-29-2gb.img.xz]

http://rcn-ee.net/deb/testing/2014-01-29/bone-debian-7.3-2014-01-29-2gb.img.xz

It takes about 10-15 Minutes to dd microSD (2GB)

To resize once booted:
* cd /opt/scripts/
* git pull
* ./tools/grow_partition.sh
* sudo reboot

Finally one of my classic "setup_sdcard.sh".
[debian-7.3-lxde-armhf-2014-01-22.tar.xz]

http://rcn-ee.net/deb/testing/2014-01-29/debian-7.3-lxde-armhf-2014-01-29.tar.xz

Note for users who use my classic "setup_sdcard.sh" script, here is
the magic options to get the beaglebone project files + systemd.

sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot bone
--beagleboard.org-production --enable-systemd

To "rebuild"
git clone git://github.com/beagleboard/image-builder.git
cd image-builder
git checkout bb.org-v2014.01.29 -b tmp
touch release
./beagleboard.org_image.sh

Thanks Robert, I will check it out…

Did we get that GTK bug fixed? File dragging doesn’t halt the system anymore, on my bbb. Wondering if it something I did…custom 3.8.13-bone37, 3 custom capes compiled in, and touchscreen driver mods…

Louis

Nope, still hard locks for me..

sudo apt-get install gpicview
lxde -> Accessories -> "Image Viewer" - "Open File" -> boot -> Docs ->
images -> beagle.png -> Open -> HARDLOCK...

Hopefully TI has an answer in our call tomorrow. :wink:

Regards,

Dude, mine is working!

Here are the changes that I remember:
Custom compiled 3.8.13-bone37 kernel, with no config changes
modified ti_am335x_tsc.c for BB-VIEW LCD7
added a 3 dts files to the firmware/capes folder
modified firmware/Makefile to add those cape drivers to the kernel
copied 3.8.13-bone37.zImage to /boot/uboot/zImage

apt-get install libqtgui4 qt4-demos gpicview

My guess is that libqt installed something to fix it…

Humm.. No such luck here.. What resolution are you running. I'm using
a monitor at 1280x1024.. It really feels like a graphics hardware
lockup..

Regards,

Darn , I was hoping I narrowed it down… 800 x 480 is my resolution. Come to think of it, I think the last lock ups were through HDMI, to a 1680 x 1050 monitor.

Nope there goes that theory, 480x272..

Regards,

I was going to do more testing, but an unexpected power outage corrupted my sd card…I will see if I can retrace my steps with a fresh image…

I found it! Switching from 16 bit video mode to 24 bit fixes GTK.

I added this to /usr/share/X11/xorg.conf.d/10-evdev.conf

Section “Screen”

Identifier “Builtin Default fbdev Screen 0”

Monitor “Configured Monitor”

Device “Configured Video Device”

DefaultDepth 24

EndSection

Nice find!! It's too bad the colors are psychedelic, so it's unusable..

sudo sed -i -e 's:16:24:g' /etc/X11/xorg.conf
sudo reboot

But the core finally doesn't lock up!

Regards,

Nice find!! It's too bad the colors are psychedelic, so it's unusable..

sudo sed -i -e 's:16:24:g' /etc/X11/xorg.conf
sudo reboot

But the core finally doesn't lock up!

Regards,

I’m still working on testing this image, but thought I would comment on a couple things before they slipped my mind.

I’ve flashed the eMMC on A6 and A6A BBBs and have run the flasher image as a live system by removing the flash-eMMC.txt file.

The BB-BONE-AUDI-01:00A1 cape does not have a driver compiled into the kernel (A0 is there).
The LCD backlight frequency of 500000 is causing audible whine (BB-VIEW4/LCD7/BB-VIEW7) when the brightness is less than 100%. I fixed this by changing the frequency defined in the dts file (32768 works, but I just chose that randomly). Which repository are these being pulled from? I can fork that, make changes, and issue a pull request if that would help.

With the LCD7, I don’t detect much, if any, of a change between the two versions of touchscreen drivers. I am not saying that we should discard the new version, but that the new version doesn’t negatively affect the system.

My thoughts, with respect to networking, are to make it easy to get a wireless connection up and running. Wicd is pretty good at that, but I notice that every 8 to 20 minutes the wireless connection is dropped. That could be the AP I am connected to, so I will continue to test with other APs. I still need to test a couple more USB adapters too.

Another comment is the screen blanking. I noticed that the LCD7 goes white instead of just blanking to black. Not a problem, just noticed the change. But in trying to disable the power saving, I open the screen saver settings and am greeted with a warning message that the XScreenSaver daemon isn’t running. This may give new users the impression that something is broken in the image. Is there another place to disable the screen blanking timer?

Thanks,
Louis

To "rebuild"
git clone git://github.com/beagleboard/image-builder.git
cd image-builder
git checkout bb.org-v2014.01.29 -b tmp
touch release
./beagleboard.org_image.sh

I attempted to rebuild the image (mainly for educational purposes) but
the build hangs when attempting to clone boot-scripts:

Log: (chroot) adding admin group to /etc/sudoers
Enter new UNIX password: Retype new UNIX password: passwd: password
updated successfully
Log: (chroot) Warning, qemu can fail here... (run on real armv7l
hardware for production images)
Log: (chroot): [git clone
https://github.com/RobertCNelson/boot-scripts /opt/scripts/ --depth 1

true]

Cloning into '/opt/scripts'...
remote: Counting objects: 32, done.
remote: Compressing objects: 100% (26/26), done.
remote: Total 32 (delta 6), reused 21 (delta 0)

[stops here]

$ ps aux | grep git
root 29272 0.0 0.0 4136812 4788 pts/0 S+ 21:06 0:00
/usr/bin/qemu-arm-static /usr/bin/git clone
https://github.com/RobertCNelson/boot-scripts /opt/scripts/ --depth 1
root 29273 0.2 0.0 4203256 13480 pts/0 S+ 21:06 0:02
/usr/bin/qemu-arm-static /usr/lib/git-core/git-remote-https origin
https://github.com/RobertCNelson/boot-scripts
root 29275 0.0 0.0 4203228 5380 pts/0 S+ 21:06 0:00
/usr/bin/qemu-arm-static /usr/lib/git-core/git fetch-pack
--stateless-rpc --stdin --lock-pack --include-tag --thin --depth=1
https://github.com/RobertCNelson/boot-scripts/
root 29278 0.0 0.0 4137840 3792 pts/0 S+ 21:06 0:00
/usr/bin/qemu-arm-static /usr/lib/git-core/git fetch-pack
--stateless-rpc --stdin --lock-pack --include-tag --thin --depth=1
https://github.com/RobertCNelson/boot-scripts/
jvaller+ 32164 0.0 0.0 10288 880 pts/1 S+ 21:28 0:00 grep git

If I git clone the boot-scripts repository outside of this script, I
have no issues. It only hangs when run from the
beagleboard.org_image.sh script. This is on 64-bit Debian "jessie".
Any ideas on what might be causing this?

It boils down to... qemu is bitrotten and just plain sucks... At one
time it worked really great. (okay that's a lie, but it worked..)

See the note right before the git clone.. :wink:
Log: (chroot) Warning, qemu can fail here... (run on real armv7l
hardware for production images)

Regards,

LCD3/LCD4/LCD7 users, xinput_calibrator is installed by default…

Can you please compare 3.8.13-bone36 with 3.8.13-bone39 to test
Micka’s touchcreen fix?

I’ve tried to make it very easy to test via:

cd /opt/scripts/tools
sudo ./update_kernel.sh --kernel v3.8.13-bone36
sudo rm /etc/pointercal.xinput
sudo reboot

cd /opt/scripts/tools
sudo ./update_kernel.sh --kernel v3.8.13-bone39
sudo rm /etc/pointercal.xinput
sudo reboot

So please compare and contrast bone36/bone39, as we really need
testing from users…

Found this thread via google search, so I am probably missing something. But I can’t run these commands because I don’t know the root password.

I can say that on boot with my LCD7, there is really no difference with the Angstrom version. When the calibrate routine comes up at boot, I can click the first target with finger or stylus, but when the second comes up, the only way it will click is if I touch about half an inch to the left. Only once have I managed to click the third target. Usually I get a misclick message and it starts over. If I let it time out, it moves on. If I then touch the screen, the mouse pointer starts shaking.

I do have a mouse connected, and eventually this build gives me mouse control back, which is better than the Angstrom build where I had to press reset to get it to stop.

This is my first week with this board, and while I’m a long time Linux user, and long time software developer, I am a brand new Linux software developer, so I’m still in the steep portion of the learning curve. I’m following Malloy’s guides mostly, in a VirtualBox VM so I can move my dev image around between work and home.

Does your wifi adapter work? Are we missing it’s firmware?

Wicd finds my network via my USB wifi adapter. RaLink RT3572. I can connect, then load chromium and surf the net just fine.

I’m a little hesitant to try connman. If it isn’t broke, don’t fix it…

Finally one of my classic “setup_sdcard.sh”.
[debian-7.3-lxde-armhf-2014-01-22.tar.xz]

Is there a place I can learn more about this?

My eventual goal is to strip this down to a non X system running QT embedded apps on the framebuffer for an embedded kiosk style system. Most of my peripherals are either USB or serial, so my “cape” will be more like a USB hub than anything else, combining LCD interface and power supplies with the hub electronics and USB to serial chips all on the same board. Around four discrete GPIO inputs and a 4x4 matrix keyboard are about it for other I/O, so I don’t anticipate this being terribly difficult. I’m hoping that the USB serial ports will always come up in the same /dev/ttyXXX locations (may have to learn udev for that) but that shouldn’t be much different than desktop linux. I really don’t see the need for X and a full desktop for this. Wired Ethernet and WLAN (USB) 3G cell modem support will be needed, but not WiFi (using that now just because there is no cable to my kitchen table).

Jeff.

LCD3/LCD4/LCD7 users, xinput_calibrator is installed by default..

Can you please compare 3.8.13-bone36 with 3.8.13-bone39 to test

Micka's touchcreen fix?

I've tried to make it very easy to test via:

cd /opt/scripts/tools
sudo ./update_kernel.sh --kernel v3.8.13-bone36
sudo rm /etc/pointercal.xinput
sudo reboot

cd /opt/scripts/tools
sudo ./update_kernel.sh --kernel v3.8.13-bone39
sudo rm /etc/pointercal.xinput
sudo reboot

So please compare and contrast bone36/bone39, as we really need
testing from users..

First, there is a newer release of this test image posted here:

https://groups.google.com/d/msg/beagleboard/D1ioNrzzXfQ/LdfJ2ccuiY4J

Found this thread via google search, so I am probably missing something.
But I can't run these commands because I don't know the root password.

The root password is blank, the default user's "debian" password is
"temppwd" this should be detailed on the serial prompt login.

I can say that on boot with my LCD7, there is really no difference with
the Angstrom version. When the calibrate routine comes up at boot, I can
click the first target with finger or stylus, but when the second comes up,
the only way it will click is if I touch about half an inch to the left.
Only once have I managed to click the third target. Usually I get a
misclick message and it starts over. If I let it time out, it moves on.
If I then touch the screen, the mouse pointer starts shaking.

Please retry with last week's image, there was a few xinput fixes pulled
in..

I do have a mouse connected, and eventually this build gives me mouse
control back, which is better than the Angstrom build where I had to press
reset to get it to stop.

This is my first week with this board, and while I'm a long time Linux
user, and long time software developer, I am a brand new Linux software
developer, so I'm still in the steep portion of the learning curve. I'm
following Malloy's guides mostly, in a VirtualBox VM so I can move my dev
image around between work and home.

Does your wifi adapter work? Are we missing it's firmware?

Wicd finds my network via my USB wifi adapter. RaLink RT3572. I can
connect, then load chromium and surf the net just fine.

I'm a little hesitant to try connman. If it isn't broke, don't fix it...

Finally one of my classic "setup_sdcard.sh".

[debian-7.3-lxde-armhf-2014-01-22.tar.xz]

Is there a place I can learn more about this?

./setup_sdcard.sh --help

More docs here:
http://elinux.org/BeagleBoardDebian#Debian_Stable_.28wheezy.29

My eventual goal is to strip this down to a non X system running QT
embedded apps on the framebuffer for an embedded kiosk style system. Most
of my peripherals are either USB or serial, so my "cape" will be more like
a USB hub than anything else, combining LCD interface and power supplies
with the hub electronics and USB to serial chips all on the same board.
Around four discrete GPIO inputs and a 4x4 matrix keyboard are about it
for other I/O, so I don't anticipate this being terribly difficult. I'm
hoping that the USB serial ports will always come up in the same
/dev/ttyXXX locations (may have to learn udev for that) but that shouldn't
be much different than desktop linux. I really don't see the need for X
and a full desktop for this. Wired Ethernet and WLAN (USB) 3G cell modem
support will be needed, but not WiFi (using that now just because there is
no cable to my kitchen table).

Regards,

The root password is blank, the default user’s “debian” password is “temppwd” this should be detailed on the serial prompt login.

For some reason, when I tried that on the terminal (via keyboard on the board itself) it kept asking for password, but I tried via SSH and it worked.

Please retry with last week’s image, there was a few xinput fixes pulled in…

Will try this tomorrow. We’re likely to have a snow day tomorrow and I’ll be at loose ends at home.

Is there a place I can learn more about this?

./setup_sdcard.sh --help

More docs here:
http://elinux.org/BeagleBoardDebian#Debian_Stable_.28wheezy.29

Will also give this a go tomorrow as well.

Jeff.

Lets keep this going, round 4...

First, for tracking please report all bugs to:
http://bugs.elinux.org/projects/debian-image-releases

Fixes:
3.8.13-bone37 -> 3.8.13-bone39
* rs485 support from Micka
* dir-changeable propery for gpio-of-helper from Charles
* cape-bone-proto from me *(new default pinmux)

New Packages:
python-pip, python-setuptools, python2.7-dev

Fixes:
systemd: limit journal to 8Mb (should fix ever expandign /var/logs issues)
cape-bone-proto loaded on bootup by /etc/default/capemgr

I have to say, I don't like this on by default. It drove my robot crazy!
Driving pins without detection seems like an overall BAD(tm) idea.

Hi,

I’m using the image http://rcn-ee.net/deb/testing/2014-01-29/debian-7.3-lxde-armhf-2014-01-29.tar.xz because I needed the x server already installed .

But I can’t find how to disable lxde from starting … anyone know ?

I told lightdm to autostart lxde

https://github.com/RobertCNelson/omap-image-builder/blob/master/target/chroot/beagleboard.org.sh#L108

so change it

Regards,