View unanswered posts | View active topics It is currently Sun Jul 21, 2019 1:30 pm



Reply to topic  [ 5 posts ] 
 Boot problem after updating to Debian Jessie armel -> armhf 
Author Message

Joined: Tue Mar 25, 2014 5:56 pm
Posts: 109
Post Boot problem after updating to Debian Jessie armel -> armhf
Hello!

I have made a really brutal test by doing

1. Install Debian Wheezy armel according Compulabs official instructions from here:
http://www.compulab.co.il/workspace/med ... ux:_Debian

2. Changed the kernel and kernel modules from the Arch linux installation files to armhf (booted ok) from here:
https://archlinuxarm.org/platforms/armv ... le/utilite

3. And doing dist-upgrade to Debian Jessie armel (went ok, booted ok)

4. And doing then cross-grade update to Debian Jessie armhf (went ok, just wanted this because the kernel modules could not be loaded of course because of wrong arcitecture, I just need headless server and networking + firewall working)
https://wiki.debian.org/CrossGrading

Only error (but huge) is that boot stops now to the point:
----
Freeing init memory: 248k
/bin/sh: 0: can't access tty; job control turned off
----

I was hoping that I just have some false configuration after update in some conf file. If anyone can help to solve this error it would be very nice, thanks!


Sun Dec 25, 2016 10:26 pm
Profile

Joined: Tue Jan 07, 2014 12:07 am
Posts: 138
Location: Edinburgh, Scotland
Post Re: Boot problem after updating to Debian Jessie armel -> ar
So you're still booting with the Arch kernel? Presumably it has:
Code:
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y

These are usually needed for the /dev nodes to be found at early boot. If it's not that, check you're giving the right console boot parameter for serial access. That's usually console=ttymxc3,115200. Presumably the Arch kernel has enabled the driver for this, which I think is CONFIG_DEBUG_IMX6Q_UART.


Sun Dec 25, 2016 11:06 pm
Profile

Joined: Tue Mar 25, 2014 5:56 pm
Posts: 109
Post Re: Boot problem after updating to Debian Jessie armel -> ar
Thank you Chewi -> Yes, the Utilite boots with 3.0.35-18-ARCH kernel now. I've checked the inittab file, it has this option at the end:

Code:
T0:23:respawn:/sbin/getty -L ttymxc3 115200 vt100


U-boot printenv gives at the moment:

Code:
CM-FX6 # printenv
autoload=no
baudrate=115200
bootargs=console=ttymxc3,115200 root=/dev/sda2 rootfstype=ext4 rw rootwait
bootcmd=sata init; load sata 0 10800000 uImage-cm-fx6; bootm
bootdelay=3
bootm_low=18000000
bootscript=echo Running bootscript from ${storagetype} ...;source ${loadaddr};
console=ttymxc3,115200
doboot=bootz 0x10800000 - 0x11000000
doloadfdt=true
dtb=cm-fx6.dtb
eth1addr=00:01:c0:14:23:83
ethact=FEC
ethaddr=00:01:c0:14:27:4f
ethprime=FEC0
fdtaddr=0x11000000
kernel=zImage-cm-fx6
loadaddr=0x10800000
loadfdt=load ${storagetype} ${storagedev} ${fdtaddr} ${dtb};
loadkernel=load ${storagetype} ${storagedev} ${loadaddr} ${kernel};
loadscript=load ${storagetype} ${storagedev} ${loadaddr} ${script};
mmcargs=setenv bootargs console=${console} root=${mmcroot} ${video}
mmcroot=/dev/mmcblk0p2 rw rootwait
nandargs=setenv bootargs console=${console} root=${nandroot} rootfstype=${nandrootfstype} ${video}
nandboot=if run nandloadkernel; then run nandloadfdt;run setboottypem;run storagebootcmd;run setboottypez;run storagebootcmd;fi;
nandloadfdt=nand read ${fdtaddr} 780000 80000;
nandloadkernel=nand read ${loadaddr} 0 780000;
nandroot=/dev/mtdblock4 rw
nandrootfstype=ubifs
panel=HDMI
preboot=usb start
run_eboot=echo Starting EBOOT ...; mmc dev 2 && mmc rescan && mmc read 10042000 a 400 && go 10042000
sataargs=setenv bootargs console=${console} root=${sataroot} ${video}
sataroot=/dev/sda2 rw rootwait
script=boot.scr
setboottypem=setenv kernel uImage-cm-fx6;setenv doboot bootm ${loadaddr};setenv doloadfdt false;
setboottypez=setenv kernel zImage-cm-fx6;setenv doboot bootz ${loadaddr} - ${fdtaddr};setenv doloadfdt true;
setupmmcboot=setenv storagetype mmc; setenv storagedev 2;
setupnandboot=setenv storagetype nand;
setupsataboot=setenv storagetype sata; setenv storagedev 0;
setupusbboot=setenv storagetype usb; setenv storagedev 0;
stderr=serial,vga
stdin=serial,usbkbd
stdout=serial,vga
storagebootcmd=echo Booting from ${storagetype} ...;run ${storagetype}args; run doboot;
storagedev=0
storagetype=nand
trybootk=if run loadkernel; then if ${doloadfdt}; then run loadfdt;fi;run storagebootcmd;fi;
trybootsmz=if run loadscript; then run bootscript;fi;run setboottypem;run trybootk;run setboottypez;run trybootk;
video_dvi=mxcfb0:dev=dvi,1280x800M-32@50,if=RGB32
video_hdmi=mxcfb0:dev=hdmi,1920x1080M-32@50,if=RGB32
Environment size: 2428/8188 bytes


Does this make any sense or where I should look for the console parameter? And sorry, I'm not certain were and how to look the kernel configs.


Mon Dec 26, 2016 1:26 pm
Profile

Joined: Tue Mar 25, 2014 5:56 pm
Posts: 109
Post Re: Boot problem after updating to Debian Jessie armel -> ar
Case closed, just have to continue with armel debian wheezy then.


Wed Dec 28, 2016 1:01 pm
Profile

Joined: Wed May 25, 2011 11:05 am
Posts: 521
Post Re: Boot problem after updating to Debian Jessie armel -> ar
Arch has another kernel worth trying
http://ftp.halifax.rwth-aachen.de/archlinux-arm/armv7h/core/linux-imx6-3.14.79-1-armv7h.pkg.tar.xz (one of the mirrors)

systemd requirements https://github.com/systemd/systemd/blob/master/README


Wed Dec 28, 2016 1:17 pm
Profile
Display posts from previous:  Sort by  
Reply to topic   [ 5 posts ] 

Who is online

Users browsing this forum: Google [Bot] and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by STSoftware for PTF.