Re: [Yaffs] yaffs Digest, Vol 40, Issue 8

Top Page
This message is part of the following thread:
M\the complete thread tree sorted by date
MMLaurence Withers at <-
 
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Vellemans, Noel
Date:  
To: yaffs
Subject: Re: [Yaffs] yaffs Digest, Vol 40, Issue 8
Hi,

The initial console problem.
I got a tip from someone [sorry, lost the name of this person] that it was the /dev/console that was missing.

And it is quite trivial, it is the /dev/console that is missing.

(the BUILDROOT makeimage tool is causing this, in my case, must be a bug i guess, an older buildroot-build was not causing this problem, at this time i'm building 20080901 build of buildroot.)

{ you can check this by mounting the image on a NORMAL PC and you will see that the /dev directory is empty and some other directorys are empty as well, which also will explain your panic. }

As you all will know ...In linux there are 100 or maybe more.. ways to get a sollution.

Work around, ? In my case i did the following.

I'm booting ext2 (which works fine) I'm doing a ram boot via tftp, after the boot, I mount yaffs2 on my flash partition.
( YAFFS2 is partition 4 in my case)

<< snap shot >>
flash_eraseall /dev/mtd4
mkdir /mnt/part4
mount -t yaffs2 /dev/mtdblock4 /mnt/part4
<< snap shot - end >>

After the mount I take a copy of the ext2 filesystem (that is booting fime), that is running in ram to the /mnt/part2 which is mounted as yaffs2.

After this I reboot the system from YAFFS2 and all seems to work.

To make a resume,
It must be a problem in the makeimage tool I'm using in my case, because the images that are build whith this tool are missing some directories.

Again .. In linux there are 100 ways to get a sollution, other sollutions may work as well.


Kind Regards Noel.



-----Original Message-----
From: [mailto:yaffs-bounces@lists.aleph1.co.uk] On Behalf Of Ignacio Molinero
Sent: Wednesday, September 24, 2008 6:24 PM
To:
Subject: Re: [Yaffs] yaffs Digest, Vol 40, Issue 8

Hi James & Noel

I have a the same problem but at the end of the boot's log I get a Kernel Panic, this is my bootlog: 

Bytes transferred = 1623800 (18c6f8 hex) ## Booting kernel from Legacy Image at 21400000 ...
  Image Name:   Linux-2.6.25.3
  Image Type:   ARM Linux Kernel Image (uncompressed)
  Data Size:    1623736 Bytes =  1.5 MB
  Load Address: 20008000
  Entry Point:  20008000
  Verifying Checksum ... OK
  Loading Kernel Image ... OK
OK


Starting kernel ...

Uncompressing
Linux..........................................................................................................
done, booting the kernel.
Linux version 2.6.25.3 (root@BlackRevolver-Ubuntu) (gcc version 4.1.2)
#89 PREEMPT Thu Sep 11 14:30:18 CEST 2008
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: Atmel AT91SAM9263-EK
Memory policy: ECC disabled, Data cache writeback
Clocks: CPU 199 MHz, master 99 MHz, main 16.367 MHz
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256 Kernel command line: mem=64M console=ttyS0,115200 root=/dev/mtdblock1 rw
rootfstype=yaffs2
AT91: 160 gpio irqs in 5 banks
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
console [ttyS0] enabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 61464KB available (3016K code, 241K data, 132K init) Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 152 bytes
NET: Registered protocol family 16
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 2048 (order: 2, 16384 bytes) TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048) TCP reno registered NetWinder Floating Point Emulator V0.97 (double precision)
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
yaffs Sep 11 2008 14:27:29 Installing.
io scheduler noop registered (default)
atmel_lcdfb atmel_lcdfb.0: 150KiB frame buffer at 23d40000 (mapped at
ffc00000)
Console: switching to colour frame buffer device 40x30 atmel_lcdfb atmel_lcdfb.0: fb0: Atmel LCDC at 0x00700000 (mapped at c485c000), irq 26
atmel_usart.0: ttyS0 at MMIO 0xfeffee00 (irq = 1) is a ATMEL_SERIAL
atmel_usart.1: ttyS1 at MMIO 0xfff8c000 (irq = 7) is a ATMEL_SERIAL
brd: module loaded
loop: module loaded
MACB_mii_bus: probed
eth0: Atmel MACB at 0xfffbc000 irq 21 (00:bb:bb:bb:bb:30)
eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:01,
irq=-1)
Driver 'sd' needs updating - please use bus_type methods Generic platform RAM MTD, (c) 2004 Simtec Electronics NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
AT91 NAND: 8-bit, Software ECC
Scanning device for bad blocks
Bad eraseblock 37 at 0x004a0000
Bad eraseblock 38 at 0x004c0000
Bad eraseblock 249 at 0x01f20000
Bad eraseblock 410 at 0x03340000
Bad eraseblock 552 at 0x04500000
Bad eraseblock 568 at 0x04700000
Bad eraseblock 656 at 0x05200000
Bad eraseblock 657 at 0x05220000
Bad eraseblock 1225 at 0x09920000
Bad eraseblock 1226 at 0x09940000
Bad eraseblock 1336 at 0x0a700000
Bad eraseblock 1404 at 0x0af80000
Bad eraseblock 1405 at 0x0afa0000
Bad eraseblock 1684 at 0x0d280000
Bad eraseblock 1723 at 0x0d760000
Bad eraseblock 1827 at 0x0e460000
Bad eraseblock 2033 at 0x0fe20000
Creating 3 MTD partitions on "at91_nand":
0x00000000-0x00200000 : "KernelImage"
0x00200000-0x04200000 : "Partition 1"
0x04200000-0x10000000 : "Partition 2"
mtd_dataflash spi0.0: AT45DB081B (1056 KBytes) at91_ohci at91_ohci: AT91 OHCI at91_ohci at91_ohci: new USB bus registered, assigned bus number 1 at91_ohci at91_ohci: irq 29, io mem 0x00a00000 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected usb usb1: New USB device found, idVendor=1d6b, idProduct=0001 usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: AT91 OHCI usb usb1: Manufacturer: Linux 2.6.25.3 ohci_hcd usb usb1: SerialNumber: at91 Initializing USB Mass Storage driver...
usb 1-2: new low speed USB device using at91_ohci and address 2 usb 1-2: device descriptor read/64, error -62 usb 1-2: device descriptor read/64, error -62 usb 1-2: new low speed USB device using at91_ohci and address 3 usb 1-2: device descriptor read/64, error -62 usb 1-2: device descriptor read/64, error -62 usb 1-2: new low speed USB device using at91_ohci and address 4 usb 1-2: device not accepting address 4, error -62 usb 1-2: new low speed USB device using at91_ohci and address 5 usb 1-2: device not accepting address 5, error -62 hub 1-0:1.0: unable to enumerate USB device on port 2
usbcore: registered new interface driver usb-storage USB Mass Storage support registered.
udc: at91_udc version 3 May 2006
mice: PS/2 mouse device common for all mice
ads7846 spi0.3: touchscreen, irq 31
input: ADS784x Touchscreen as /class/input/input0
rtc-at91sam9 at91_rtt.0: rtc core: registered at91_rtt as rtc0
rtc-at91sam9 at91_rtt.0: rtc0: SET TIME!
at91sam9_wdt: invalid timeout (must be between 1 and 16) Registered led device: ds1 Registered led device: ds2
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver Advanced Linux Sound Architecture Driver Version 1.0.16rc2 (Thu Jan 31
16:40:16 2008 UTC).
usbcore: registered new interface driver snd-usb-audio ASoC version 0.13.2 ALSA device list:
No soundcards found.
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
rtc-at91sam9 at91_rtt.0: hctosys: unable to read the hardware clock
yaffs: dev is 32505857 name is "mtdblock1"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.1, "mtdblock1"
block 22 is bad
block 23 is bad
block 234 is bad
block 395 is bad
VFS: Mounted root (yaffs2 filesystem).
Freeing init memory: 132K
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found. Try passing init= option to kernel.

If you have any suggestion please send me...

Thanks in advanve.

escribió:
> Send yaffs mailing list submissions to
>     

>
> To subscribe or unsubscribe via the World Wide Web, visit
>     http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs
> or, via email, send a message with subject or body 'help' to
>     

>
> You can reach the person managing the list at
>     

>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of yaffs digest..."
>
>
> Today's Topics:
>
>    1. YAFFS2 - Warning: unable to open an initial console.
>       (Vellemans, Noel)
>    2. Re: YAFFS2 - Warning: unable to open an initial console.
>       (James Kehl)

>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 24 Sep 2008 09:52:58 +0200
> From: "Vellemans, Noel" <>
> Subject: [Yaffs] YAFFS2 - Warning: unable to open an initial console.
> To: <>
> Message-ID:
>     <>
> Content-Type: text/plain;    charset="US-ASCII"

>
> Hi,
>
> I have been struggling for a couple of days with YAFFS2 kernel
> 2.6.25.x
>
> The error I get is "Warning: unable to open an initial console."
>
> When I boot the system in ext2 and/of jffs2 all seems to work, and I
> do not get the "initial console" error.
> Someone can help me a little further?
>
> Kind regards,
> Noel.
>
>
>
> Below you can find a bootlog.
>
>
> Uncompressing
> Linux.............................................................
> ........................................ done, booting the kernel.
> Linux version 2.6.25 (pingo01@phoenix) (gcc version 4.2.1) #2 Thu Sep 
> 22
> 12:00:4
> 1 CEST 2008
> CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
> Machine: Atmel AT91SAM9260-EK
> Memory policy: ECC disabled, Data cache writeback
> Clocks: CPU 198 MHz, master 99 MHz, main 18.432 MHz
> CPU0: D VIVT write-back cache
> CPU0: I cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
> CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets 
> Built
> 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256 
> Kernel command line: mem=64M console=ttyS0,115200n8 
> root=/dev/mtdblock4 rw noini trd rootfstype=yaffs2
> AT91: 96 gpio irqs in 3 banks
> PID hash table entries: 256 (order: 8, 1024 bytes)
> Console: colour dummy device 80x30
> console [ttyS0] enabled
> Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) 
> Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
> Memory: 64MB = 64MB total
> Memory: 61696KB available (2876K code, 199K data, 128K init) 
> Mount-cache hash table entries: 512
> CPU: Testing write buffer coherency: ok
> net_namespace: 152 bytes
> NET: Registered protocol family 16
> SCSI subsystem initialized
> usbcore: registered new interface driver usbfs
> usbcore: registered new interface driver hub
> usbcore: registered new device driver usb
> NET: Registered protocol family 2
> IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP 
> established hash table entries: 2048 (order: 2, 16384 bytes) TCP bind 
> hash table entries: 2048 (order: 1, 8192 bytes)
> TCP: Hash tables configured (established 2048 bind 2048) TCP reno 
> registered NetWinder Floating Point Emulator V0.97 (double precision)
> JFFS2 version 2.2. (NAND) -  2001-2006 Red Hat, Inc.
> yaffs Sep 18 2008 10:39:02 Installing. 
> io scheduler noop registered
> io scheduler anticipatory registered (default)
> atmel_usart.0: ttyS0 at MMIO 0xfefff200 (irq = 1) is a ATMEL_SERIAL
> atmel_usart.1: ttyS1 at MMIO 0xfffb0000 (irq = 6) is a ATMEL_SERIAL
> atmel_usart.2: ttyS2 at MMIO 0xfffb4000 (irq = 7) is a ATMEL_SERIAL
> brd: module loaded
> loop: module loaded
> MACB_mii_bus: probed
> eth0: Atmel MACB at 0xfffc4000 irq 21 (aa:22:33:44:55:ee)
> eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:00,
> irq=-1) Driver 'sd' needs updating - please use bus_type methods NAND
> device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 
> 8-bi
> t)
> Scanning device for bad blocks
> Bad eraseblock 1 at 0x00020000
> Bad eraseblock 2 at 0x00040000
> Bad eraseblock 3 at 0x00060000
> Creating 5 MTD partitions on "at91_nand":
> 0x00000000-0x00020000 : "Bootstrap   (PART0)"
> 0x00020000-0x00060000 : "U-Boot      (PART1)"
> 0x00060000-0x00080000 : "U-Boot-env  (PART2)"
> 0x00100000-0x00900000 : "Fact Kernel (PART3)"
> 0x00900000-0x02900000 : "Fact-Fs     (PART4)"
> usbmon: debugfs is not available
> at91_ohci at91_ohci: AT91 OHCI
> at91_ohci at91_ohci: new USB bus registered, assigned bus number 1 
> at91_ohci at91_ohci: irq 20, io mem 0x00500000 usb usb1: configuration
> #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 
> ports detected usb usb1: New USB device found, idVendor=1d6b, 
> idProduct=0001 usb usb1: New USB device strings: Mfr=3, Product=2, 
> SerialNumber=1 usb
> usb1: Product: AT91 OHCI usb usb1: Manufacturer: Linux 2.6.25 ohci_hcd 
> usb usb1: SerialNumber: at91 Initializing USB Mass Storage driver...
> usb 1-1: new full speed USB device using at91_ohci and address 2 usb
> 1-1: configuration #1 chosen from 1 choice usb 1-1: New USB device 
> found, idVendor=0a12, idProduct=0001 usb 1-1: New USB device strings:
> Mfr=0, Product=0, SerialNumber=0
> usbcore: registered new interface driver usb-storage USB Mass Storage 
> support registered.
> usbcore: registered new interface driver usbserial
> drivers/usb/serial/usb-serial.c: USB Serial support registered for 
> generic
> usbcore: registered new interface driver usbserial_generic
> drivers/usb/serial/usb-serial.c: USB Serial Driver core
> udc: at91_udc version 3 May 2006
> mice: PS/2 mouse device common for all mice TCP cubic registered
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> RPC: Registered udp transport module.
> RPC: Registered tcp transport module.
> drivers/rtc/hctosys.c: unable to open rtc device (rtc0)   
> yaffs: dev is 32505860 name is "mtdblock4"
> yaffs: passed flags ""
> yaffs: Attempting MTD mount on 31.4, "mtdblock4"
> yaffs: restored from checkpoint
> VFS: Mounted root (yaffs2 filesystem).
> Freeing init memory: 128K
> Warning: unable to open an initial console.

>
>
>
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 24 Sep 2008 18:06:16 +1000
> From: "James Kehl" <>
> Subject: Re: [Yaffs] YAFFS2 - Warning: unable to open an initial
>     console.
> To: "Vellemans, Noel" <>,
>     <>
> Message-ID:
>     <>
> Content-Type: text/plain;    charset="us-ascii"

>
>
>> -----Original Message-----
>> From: [mailto:yaffs-
>> ] On Behalf Of Vellemans, Noel
>> Sent: Wednesday, 24 September 2008 5:53 PM
>> To:
>> Subject: [Yaffs] YAFFS2 - Warning: unable to open an initial console.
>>
>> Hi,
>>
>> I have been struggling for a couple of days with YAFFS2 kernel
>>
> 2.6.25.x
>
>> The error I get is "Warning: unable to open an initial console."
>>
>> When I boot the system in ext2 and/of jffs2 all seems to work, and I
>>
> do
>
>> not get the "initial console" error.
>> Someone can help me a little further?
>>
>>
>
> Off the top of my head, it sounds like /dev/console might be missing.
> If you're using yaffs as a root partition, you need to put some device
> nodes on it (this is true for ext2 and jffs2 as well).
>
> BTW, Google seems to know a fair bit about this error message.
>
> James
>
>
>
>
> ------------------------------
>
> _______________________________________________
> yaffs mailing list
>
> http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs
>
>
> End of yaffs Digest, Vol 40, Issue 8
> ************************************
>
>
>

-- 







*Ignacio Molinero Horno         ****
Departamento I+D*


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

    

Polígono Industrial Alcalde Caballero

C/ Monasterio de las Huelgas 2, nave 6

50.014 ZARAGOZA

*Tfno: (+34) 976 798 200*

*BIOINGENIERIA*

    

*Fax: (+34) 976 798 201*

*ARAGONESA S.L.*

    

*www.sabia.es* <http://www.sabia.es>

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

_______________________________________________
yaffs mailing list

http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs


This message was posted to the following mailing lists:
YAFFS
Mailing List Info | Nearby Messages		<-[Yaffs] mount problem with yaffs bug: fs/yaffs2/yaffs_guts.c 343Re: [Yaffs] [PATCH] [YAFFS2] Multiple page read support->
Stoneboat Mailing List Archive administrated by JennyLurker (version 2.3)