Jump to content

Pine64: Not booting with vanilla kernel


Learnincurve

Recommended Posts

Hi,

 

 Not sure if this is me being stupid or a general problem with the 4.10 kernel:

 

As there are now Mainline 4.10.0-next-20170125 images available from the main Pine64 download page, I tried flashing a spare card to start working on the touchscreen.

 

Neither of the Server images based in 4.10 will boot on my board (no Ethernet activity so I can't ssh in).

 

I also tried updating a working 3.10.104 / 5.25 installation with the dev. 4.x kernel, using the guide:

 

 

To make sure you won’t run into conflicts within newly installed packages, remove them all before upgrade:

 

1
2
aptitude remove ~nlinux-dtb ~nlinux-u-boot ~nlinux-image ~nlinux-headers
aptitude remove ~nlinux-firmware ~narmbian-firmware ~nlinux-$(lsb_release -cs)-root

Proceed with install:

1
2
3
4
apt-get install linux-image-dev-pine64 linux-dtb-dev-pine64 linux-headers-dev-pine64
apt-get install linux-u-boot-pine64-dev linux-$(lsb_release -cs)-root-dev-pine64
apt-get install armbian-firmware sunxi-tools swconfig a10disp
reboot
 

 

 Finally tried with a cross compiled kernel, built using the developer guide:

 https://docs.armbian.com/Developer-Guide_Build-Preparation/

 

All with same result:  Board apparently doesn't boot, with no Ethernet activity.

 

HAve I misunderstood something major, or is there a problem?

 

BR.

 

Marius

 

Link to comment
Share on other sites

Thanks,

 

  I patched the image using:

 

 dd if=u-boot-sunxi-with-spl.bin of=Armbian_5.25_Pine64_Ubuntu_xenial_dev_4.10.0-next-20170125.img bs=1k seek=8

 

 

and can try to flash that.

 

However, the pine64 is currently booted using a copy of my 3.10.104 system, on my only spare sd. 

 

I didn't completely understand what was broken, so please excuse if this is stupid:

 

 Should I expect to be able to upgrade from 5.25 / s.10.104 to 4.10 in the live system by doing:

 

 

aptitude remove ~nlinux-dtb ~nlinux-u-boot ~nlinux-image ~nlinux-headers 
aptitude remove ~nlinux-firmware ~narmbian-firmware ~nlinux-$(lsb_release -cs)-root
 
 
apt-get install linux-image-dev-pine64 linux-dtb-dev-pine64 linux-headers-dev-pine64 
dpkg -i the uboot .deb from the link in your previous post
apt-get install armbian-firmware sunxi-tools swconfig a10disp

reboot 

 

?

 

BR.

 

--Marius--

Link to comment
Share on other sites

 Should I expect to be able to upgrade from 5.25 / s.10.104 to 4.10 in the live system by doing:

 

 

aptitude remove ~nlinux-dtb ~nlinux-u-boot ~nlinux-image ~nlinux-headers 
aptitude remove ~nlinux-firmware ~narmbian-firmware ~nlinux-$(lsb_release -cs)-root
 
 
apt-get install linux-image-dev-pine64 linux-dtb-dev-pine64 linux-headers-dev-pine64 
dpkg -i the uboot .deb from the link in your previous post
apt-get install armbian-firmware sunxi-tools swconfig a10disp

reboot 

No. This upgrade scenario is not supported on Pine64 and it should be removed from the download page.

Link to comment
Share on other sites

Excellent!  The Pine64 boots into 4.10.0-next-20170125-pine64 using the manually flashed uboot.

 

 Thanks very much for your help!

 

One last question:

 

Can I build other 4.10 kernels using my own kernel .config and update those using dpkg, or will I always need to manipulate the .img and reflash?

 

 The reason for the question is that I will need the goodix module (for the touchscreen) and want to experiment with different timers as the board will be used for unpacking and passing through audio streams to a USB DAC. I may even try to compile e RT kernel at some point.

 

BR.

 

--Marius--

Link to comment
Share on other sites

Can I build other 4.10 kernels using my own kernel .config and update those using dpkg, or will I always need to manipulate the .img and reflash?

Yes, you can build and install only the kernel packages, but you may want to apt-mark hold them to prevent any future upgrades from the repository.

 

The reason for the question is that I will need the goodix module (for the touchscreen) and want to experiment with different timers as the board will be used for unpacking and passing through audio streams to a USB DAC. I may even try to compile e RT kernel at some point.

May I ask - touch screen for what? As far as I know the only ways to get any display output on Pine64 with mainline are either SPI or USB interface, unless you manage to make @jernej's disp2 HDMI driver in u-boot work on A64

Link to comment
Share on other sites

You can download, extract and write the u-boot binary to the image manually if you want. U-boot is here, and instructions are the same as for other sunxi u-boots (dd if=u-boot-sunxi-with-spl.bin of=your_sd_card_reader bs=1k seek=8)

Newby question:  should I put an apt-mark hold on u-boot after  flashing over it?   Main Line kernel is booting fine now  but apt-get upgrade shows an upgrade for u-boot.  I wasn't sure whether or not that was a fix or still the broken one.   IS there a repository I should be monitoring for the fix?

 

thanks.

Link to comment
Share on other sites

Yes, you can build and install only the kernel packages, but you may want to apt-mark hold them to prevent any future upgrades from the repository.

 

May I ask - touch screen for what? As far as I know the only ways to get any display output on Pine64 with mainline are either SPI or USB interface, unless you manage to make @jernej's disp2 HDMI driver in u-boot work on A64

 

Hi Zador,

 

Tkaiser answered my question on another thread:

 

'vanilla kernel does not support DVFS, HDMI, onboard analog audio output, onboard IR receiver, CSI, DSI and TP interfaces' (DSI is LCD).  I wasn't aware the DSI was the LCD ribbon interface.

 

I'm wanting to use the board and official touchscreen/LCD as a "Squeezebox Touch" replacement. The screen is supposed to be the interface for "Jivelite", which is a GUI for controlling "Squeezelite".

 

So for now, I'm abandoning mainline and looking for ways to tweak 3.10.104 for audio use.

 

There is a distro called "volumio" that has all the audio stuff in place (RT 3.10.104 kernel, USB tweaks, etc), but it is designed to run headless and so far I haven't managed to get the LCD/touchscreen running on that either.

 

I'll take that discussion in a new thread.

  Thanks for all your help!

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines