search

RobertCNelson / netinstall

Network Install for a bunch of arm boards
https://rcn-ee.com
80 stars 19 forks source link

Wandboard Quad will not boot installer #30

Open msilvax28 opened 9 years ago

msilvax28 commented 9 years ago

Retrieved the latest git repo to create an netinstall image for the wandboard quad. The netinstall SD card will not boot.

Not sure of the 'correct' fix, but here's what I found:

The mmcboot script errors out here.

Even if mmcboot detected the partitions correctly, I'm not sure that the mmcboot script would run the correct commands to start the OS.

RobertCNelson commented 9 years ago

Sorry about that. I just rolled the u-boot version back down to the previous. I've been rolling out a new partition setup that's more compatible with debian's linux-image package.

You can see the details here: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0

Yet i broke the first check "uenvcmd" in /uEnv.txt

glframebuffer commented 9 years ago

I think problem still persist, I tried to do for Wandboard solo today. kindly fix this issue .

RobertCNelson commented 9 years ago

What problem?

It works fine: http://pastebin.com/kei38W1e

glframebuffer commented 9 years ago

With latest update it worked like charm. :) Thanks for support, you can close issue.

Cheers

zaleksf commented 7 years ago

Hello:

I am attempting to initiate a debian stretch netinstall on a wandboard quad. I have successfully created an OS disk using: sudo ./mk_mmc.sh --mmc /dev/mmcblk0 --dtb wandboard --distro stretch --firmware

Everything appears to be fine on the disk, and the hardware seems fine (power light on wandboard, keyboard, etc).

However, nothing happens when power is applied. Thoughts?

RobertCNelson commented 7 years ago

@zaleksf

in stretch, they changed a few things that happen at the very end of the install..

For now, use the "jessie" option, and dist-upgrade to stretch after..

I haven't had time to track down the issue, but i'm aware of it. (we are a few months from the freeze, so i'd like to fix it before then..)

Regards,

RobertCNelson commented 7 years ago

@zaleksf you should see this over serial:

U-Boot SPL 2016.07-00001-g4cdc160 (Aug 05 2016 - 16:49:04)
Trying to boot from MMC1

U-Boot 2016.07-00001-g4cdc160 (Aug 05 2016 - 16:49:04 -0500), Build: jenkins-github_Bootloader-Builder-434

CPU:   Freescale i.MX6DL rev1.1 at 792 MHz
Reset cause: POR
Board: Wandboard rev B1
I2C:   ready
DRAM:  1 GiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
*** Warning - bad CRC, using default environment

No panel detected: default to HDMI
Display: HDMI (1024x768)
In:    serial
Out:   serial
Err:   serial
Net:   FEC [PRIME]
Press SPACE to abort autoboot in 2 seconds
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
Checking for: /uEnv.txt ...
Checking for: /boot/uEnv.txt ...
246 bytes read in 64 ms (2.9 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt...
Running uname_boot ...
Using: mmcroot=PARTUUID=99b5cc90-01 ro ...
loading /boot/vmlinuz-current ...
5772768 bytes read in 443 ms (12.4 MiB/s)
loading /boot/dtbs/current/imx6dl-wandboard-revb1.dtb ...
45740 bytes read in 847 ms (52.7 KiB/s)
loading /boot/initrd.img-current ...
50740506 bytes read in 3107 ms (15.6 MiB/s)

Installer for [jessie-armhf] is using the Video Interface
Use [--serial-mode] to force Installing over the Serial Interface

debug: [console=tty0 root=/dev/ram0 rw] ...
debug: [bootz 0x12000000 0x12A00000:3063d1a 0x18000000] ...
Kernel image @ 0x12000000 [ 0x000000 - 0x5815e0 ]
## Flattened Device Tree blob at 18000000
   Booting using the fdt blob at 0x18000000
   Using Device Tree in place at 18000000, end 1800e2ab

Starting kernel ...

make sure you are using the microSD on the smaller som board, not the big base board.

Regards,

zaleksf commented 7 years ago

Thanks,

I converted the BOOT disk to jessie (wipe and fresh install). I put the disk into the smaller som board, and still cannot see the boot-up... I thought I would see this on the monitor (did not use --serial mode as an option).

Do I need to switch to serial mode? and if so, how do I observe the start-up (sorry for ignorance)?

Thanks

RobertCNelson commented 7 years ago

@zaleksf hdmi should work, make sure you have a common gnd between the board and the monitor..

aka, if your monitor has a usb hub, plug that into your wandboard..

Floating gnd's is usually the problem with hdmi monitors...

Regards,

zaleksf commented 7 years ago

Ahha! the root issue for me has that I needed to use the precise power supply voltage: 5VDC with a minimum of 800 mA current.

So, I can confirm that the debian jessie installer works, observing the process directly from a monitor via the hdmi connection. However, the debian stretch installer works only up to the step of 'make the installation bootable', where it fails.

RobertCNelson commented 7 years ago

@zaleksf stretch is now fixed on master, dealt with the fun flash-kernel safetly check..

Regards,

zaleksf commented 7 years ago

I did get the 'wandboard - stretch' netinstall version to successfully install a nice OS with xcfe - great! I installed several other packages and restarted successfully several times.

Then I returned the HDMI cable I swiped from our wii-u game system and installed the HDMI cable that I purchased, and restarted the wandboard. It never made it to the lightdm greeter, and failed with a flashing prompt. I switched back to the old HDMI cable, and it still failed. I tried various combinations of HDMI cables and monitors - no luck.

I have started all over with the 'wandboard - stretch' netinstall, using the new HDMI cable from the beginning, but it fails prior to the lightdm greeter. I have actually done this twice, with two different monitors, in case that made a difference.

Final lines of /var/log/messages => ... Sep 16 14:32:14 psiko-1 lightdm[1818]: Could not enumerate user data directory /var/lib/lightdm/data: Error opening directory '/var/lib/lightdm/data': No such file or directory Sep 16 14:32:25 psiko-1 lightdm[1831]: Could not enumerate user data directory /var/lib/lightdm/data: Error opening directory '/var/lib/lightdm/data': No such file or directory Sep 16 14:32:26 psiko-1 lightdm[1845]: Could not enumerate user data directory /var/lib/lightdm/data: Error opening directory '/var/lib/lightdm/data': No such file or directory

Some lines of /var/log/syslog => ... Sep 16 14:32:04 psiko-1 systemd-fsck[1420]: BOOT: clean, 326/36864 files, 41629/ 147456 blocks Sep 16 14:32:04 psiko-1 systemd-fsck[1417]: /dev/mmcblk0p6: clean, 15/2555904 fi les, 205506/10211584 blocks Sep 16 14:32:04 psiko-1 systemd[1]: Started File System Check on /dev/mmcblk0p1. Sep 16 14:32:04 psiko-1 systemd-udevd[622]: could not open builtin file '/lib/modules/4.4.21-armv7-x10/modules.builtin.bin' Sep 16 14:32:04 psiko-1 systemd-udevd[612]: could not open builtin file '/lib/modules/4.4.21-armv7-x10/modules.builtin.bin' Sep 16 14:32:04 psiko-1 systemd-udevd[612]: could not open builtin file '/lib/modules/4.4.21-armv7-x10/modules.builtin.bin' ... Sep 16 14:32:12 psiko-1 NetworkManager[1705]: [1474050732.0129] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Sep 16 14:32:14 psiko-1 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE Sep 16 14:32:14 psiko-1 systemd[1]: lightdm.service: Unit entered failed state. Sep 16 14:32:14 psiko-1 systemd[1]: lightdm.service: Failed with result 'exit-code'. Sep 16 14:32:14 psiko-1 systemd[1]: lightdm.service: Service hold-off time over, scheduling restart. Sep 16 14:32:14 psiko-1 systemd[1]: Stopped Light Display Manager. Sep 16 14:32:14 psiko-1 systemd[1]: Starting Light Display Manager... Sep 16 14:32:14 psiko-1 lightdm[1818]: Could not enumerate user data directory /var/lib/lightdm/data: Error opening directory '/var/lib/lightdm/data': No such file or directory Sep 16 14:32:14 psiko-1 systemd[1]: Started Light Display Manager. Sep 16 14:32:15 psiko-1 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE Sep 16 14:32:15 psiko-1 systemd[1]: lightdm.service: Unit entered failed state. Sep 16 14:32:15 psiko-1 systemd[1]: lightd

Please let me know if it would be helpful for me to send various log files for troubleshooting.

Thanks.