ts-7000
[Top] [All Lists]

[ts-7000] "Warning: unable to open an initial console.", 2.6.21 on TS-72

To: TS-7000 Yahoogroups List <>
Subject: [ts-7000] "Warning: unable to open an initial console.", 2.6.21 on TS-7250
From: "Robert P. J. Day" <>
Date: Sat, 21 Mar 2009 10:04:11 -0400 (EDT)
  here's my situation (on which i've posted on a couple linux kernel
mailing lists but this seems like the appropriate forum so i'll give
it another shot).

  i have a TS-7250, running a long-installed homegrown version of
2.6.17.10.  both kernel and a fairly old (busybox-1.2.1) based root
filesystem are in flash and if i just let the thing boot, it's all
good.  (rootfs is in /dev/mtdblock2.)

  i'm trying to upgrade the kernel to the (admittedly unofficial)
2.6.21-ts kernel source tree, so i downloaded that kernel source and
have tried to configure it as similarly as possible with the config
file used for the older 2.6.17 kernel.  (i can pull that config info
out of /proc/config.gz when running that older kernel.)

  with a little manual tweaking (and deselecting certain subsystems
that won't affect just getting a kernel up and running, like USB and
NFS), i get:

...
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
VFS: Mounted root (yaffs filesystem).
Freeing init memory: 92K
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.

  normally, when i see that error, i think that, somehow, there is no
/dev/console device file, or there's a mismatch between running devfs
on an older 2.4 kernel and udev on a newer 2.6 kernel.  but these are
both 2.6 kernels, not *that* different, using the same filesystem.

  part of the boot output for both kernels.  first, for 2.6.17:

Serial: AMBA driver $Revision: 1.41 $
apb:uart1: ttyAM0 at MMIO 0x808c0000 (irq = 52) is a AMBA
apb:uart2: ttyAM1 at MMIO 0x808d0000 (irq = 54) is a AMBA
apb:uart3: ttyAM2 at MMIO 0x808e0000 (irq = 55) is a AMBA

  and for 2.6.21-ts:

Serial: AMBA driver $Revision: 1.1.1.1 $
apb:uart1: ttyAM0 at MMIO 0x808c0000 (irq = 52) is a AMBA
apb:uart2: ttyAM1 at MMIO 0x808d0000 (irq = 54) is a AMBA
apb:uart3: ttyAM2 at MMIO 0x808e0000 (irq = 55) is a AMBA

  if that looks important.  what else can i look at?  the only thing
changing between the two attempts is the kernel, the newer one which i
download via TFTP, and use the redboot commands:

  load -r -v -b 0x218000 -h 192.168.1.241 zImage
  exec -c "console=ttyAM0,115200 root=/dev/mtdblock2"

so i'm kind of stumped right now.

rday
--

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/ts-7000/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/ts-7000/join
    (Yahoo! ID required)

<*> To change settings via email:
     
    

<*> To unsubscribe from this group, send an email to:
    

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

<Prev in Thread] Current Thread [Next in Thread>
Admin

Disclaimer: Neither Andrew Taylor nor the University of NSW School of Computer and Engineering take any responsibility for the contents of this archive. It is purely a compilation of material sent by many people to the birding-aus mailing list. It has not been checked for accuracy nor its content verified in any way. If you wish to get material removed from the archive or have other queries about the archive e-mail Andrew Taylor at this address: andrewt@cse.unsw.EDU.AU