Jetson TK1 : boot problem - issue with libglx.so

You know something went wrong when things goes too smoothly. After flash the board for a few time to fix WiFi driver and install ROS Indigo my screen black out went I try to reboot it. Screen show streams of text while booting, then Nvidia logo show up and then went blank after that.

Don't to flash it once again, I search some more and found that I am not the only one and this (luckily). Problem, figure out by this guy, is that file libglx.so being replace by some update or process causing the board can't display properly. The fix is easy, go back to your host computer's download folder where you download Tegra124_Linux_R19.3.0_armhf.tbz2 package when to prepare to compile The Grinch kernel.

• Unpack Tegra124_Linux_R19.3.0_armhf.tbz2

• You we get Linux_for_Tegra folder.

• Find Linux_for_Tegra/nv_tegra/nvidia_drivers.tbz2 and unpack it.

• Navigate to usr/lib/xorg/modules/extensions/ there you will have the original libglx.so file.

• Copy the original libglx.so file from host computer to the TK1 board, place it in the same usr/lib/xorg/modules/extensions/ folder. You may backup the TK1's libglx.so file first by change its name to something like libglx.so.bak

• Cross your finger and reboot. 

• If you boot into Ubuntu GUI screen then you're done! better to keep the new libglx.so file just in case we need it again. By copy and rename it to libglx.so.original.

 I hope all the smart guys at Nvidia will figure out the cause and way to get around this soon.

Jetson TK1, day2

https://devtalk.nvidia.com/default/topic/747574/embedded-systems/jetson-tk1-boot-issue/?offset=17#4308726

The problem is that after I move to The Grinch kernel and do some update & upgrade I can't reboot back to the Ubuntu screen. I tried ssh into it and its seem to working just fine. No choice, I decided to flash the board again, but I got a message "flash fail" and hence process to follow the Hint #1. After 2 times of flashing the board, problem still persist.

I then try to undo the Hint #1 by (follow this link for instructions)

remove

losetup --find --show system.img

And replace with

losetup /dev/loop0 system.img > /dev/null 2>&1

And flash it one more time. This time I able to update & upgrade and install ROS indigo (for ARM, bare-bone package) while able to reboot back to Ubuntu screen.

PS: I also tried to install ROS Indigo from source, which went fine, but actually someone (up there?) make an installation for Ubuntu-ARM architecture already, you can follow a link here.

Things went too smoothly, what else can go wrong? ... my Ubuntu screen gone again :(

Jetson TK1, day1

I recently got this new, cheap development from Nvidia called Jetson Tk1. The main highlight of these board is that its contain 192 GPU core inside. Unlike another microcomputer board like Raspberry Pi or BeagleBone black, TK1 is able to run Ubuntu 14.04 (ARM version) with decent graphic and response.

I got my board from newEgg website for around 300 SGD, for some reason you cannot buy the board from Nvidia's website if you are not in the US.
 
First boot-up went fine, just plug-in the 12 volt power supply that come with the board and it will boot into command-line screen. There you will see Nvidia driver install script, just execute that and it will restart and land you to Ubuntu's GUI screen.

Unfortunately, the kernel that chipped with TK1 (at least the one I got) doesn't support WiFi dongle. Searching around the web gave me 2 options.

Option 1:
Download RTL8192CU here and follow the procedure in comment #9 to include the driver into current kernel.

Option 2:
Follow an instruction from Nvidia development forum to upgrade kernel to The Grinch which added support for Wifi dongle and many more device.

I don't think totally wipe out an original kernel (option 2) since day 1 is not a very good idea, so I go for option 1, which went smoothly. After reboot the TK1 detect my WiFi dongle and able to connect to WiFi network with ease of Network manager with GUI.

After a while (like 10 minutes) I thought move on to The Grinch (option 2) might be a better ideal because I am planing to install ROS and OpenCV onto it, upgrade a kernel after will not be so easy.

That's when problems start to come up ...