Hi All:
I use fastboot to flash kernel(Debian) which i rebuild.
And i reboot the Dragonboard410C, it will run into console mode.
How can i change to Debian GUI?
Dose anybody can help me?Hi @shung35,
Do you mind checking which Debian image your wrote in you Dragonboard 410c?
These are the links to the latest Debian image.
For installing from SD card:
https://github.com/96boards/documentation/wiki/DragonBoard%E2%84%A2-410c-Linaro-Debian-Download#your-build-choice
For installing with fastboot:
https://github.com/96boards/documentation/wiki/DragonBoard%E2%84%A2-410c-Linaro-Debian-Download#your-build-choice-1
If you look inside the release folder:
http://builds.96boards.org/releases/dragonboard410c/linaro/debian/latest/
There are two images.
One does not have GUI:
http://builds.96boards.org/releases/dragonboard410c/linaro/debian/latest/linaro-jessie-developer-qcom-snapdragon-arm64-20160428-83.img.gz
If you have installed “linaro-jessie-alip-qcom-snapdragon-arm64-20160428-83.img.gz” then it should boot up with GUI.
Hi Akira:
Thanks for your reply. I use following step to get kernel source code.
<strong>git clone -n http://git.linaro.org/landing-teams/working/qualcomm/kernel.git
cd kernel
git checkout -b kernel-16.04 debian-qcom-dragonboard410c-16.04</strong>
And i will do "make menuconfig" to change some function. Finally I will generate a boot-db410c.img, and write into dragonboard.
If i use fastboot to flash "boot-db410c.img" into dragonboard, can i change to Debain GUI?
Or should I download other version source code?
I also download you mention image "linaro-jessie-alip-qcom-snapdragon-arm64-20160428-83.img.gz", but it seem cannot to do "make menuconfig". It seems a image file.Hi
Your procedure looks fine for the kernel.
Have you also install the rootfs? It requires separate command line like bellow.
$ sudo fastboot flash boot boot-linaro-jessie-qcom-snapdragon-arm64-**BUILD#**.img
$ sudo fastboot flash rootfs linaro-jessie-developer-qcom-snapdragon-arm64-**BUILD#**.img
hi,
if you rebuild your own kernel, you need to pay attention to modules and bootargs.
- modules: the kernel modules are installed on the rootfs, if you rebuild your kernel the ‘kernel version’ string is likely to be different from the one we used when we create our builds. In our images, it is set to:
KERNELRELEASE=make kernelversion-linaro-lt-qcom
The boot image only includes the kernel Image file, not the modules. If your local change does not ‘impact’ any of the modules, it is generally ok to rebuild the Image file, with the right KERNELRELEASE variable set.
if you patch kernel modules, then you need to deploy the newly rebuilt kernel modules on your target rootfs. If you are not familiar with that, the simplest way to do it is to build the kernel deb package, copy it onto the board, install and reboot. To build the kernel deb package, if your kernel tree:
make bindeg-pkg
then copy the generated linux-image-<version>_arm64.deb onto the board (SD card, USB, SSH, …) and install it with “dpkg -i”. Your new modules will now be installed in the rootfs in /lib/firmware. Then you can reboot with your new kernel.
- bootargs
I am not sure which instructions you used to rebuild the boot image, but you need to make sure that you don’t have “systemd.unit=multi-user.target” in your bootargs. This option will boot the system to console only.
Hi Akira:
Thanks a lot! It can work!
The problem is due to I forgot to install rootfs!
Now It can work well. Thanks for your help~