Closed tthef closed 12 years ago
Investigated this further, and it would seem it's the firmware messing us about; the 'console=tty1' parameter is hardcoded in all the startup files, so I am going to close this as this is an upstream issue.
Thank you @tthef
Andrei
Sorry, I am going to reopen this; got a very quick response from the RPI guys, seemingly if you want a custom command line, you have to provide your command line in /boot/cmdline.txt. Perhaps the kernel recipe should generate this and include it in the /boot partition?
Could you test if this is solved with a cmdline file?
Yes it is, so something like
do_deploy_append() { install -d ${DEPLOY_DIR_IMAGE}/bcm2835-bootfiles echo "${CMDLINE}" > ${DEPLOY_DIR_IMAGE}/bcm2835-bootfiles/cmdline.txt }
In the kernel recipe should take care of generating the file, but the sdcar_image-rpi class will need to be modified to install it, I think (there is TODO note there about cmdline.txt, but I think that's orthogonal to this issue)
I will make a patch.
Thank you.
ag
Fix merged. Thank you, @tthef .
Andrei
Even though the kernel bb recipe sets up the commandline so that the console is on ttyAMA0, it is ends up on tty1, from dmesg, the actual kernel command line looks like this:
Kernel command line: dma.dmachans=0x3c bcm2708_fb.fbwidth=1280 bcm2708_fb.fbheight=1024 bcm2708.boardrev=0x2 bcm2708.serial=0xc80d92c5 smsc95xx.macaddr=B8:27:EB:0D:92:C5 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait
This is not the command line the recipe defines, and note that the console parameter is there twice. Any idea what is going on here?