From: "Allen Curtis" <acurtis@onz.com>
To: "Patrick Allaire" <pallaire@gameloft.com>,
<linux-mtd@lists.infradead.org>
Subject: RE: From 2.4.9 to CVS ???
Date: Fri, 4 Jan 2002 08:24:57 -0800 [thread overview]
Message-ID: <NCBBIINEHIPFGJPLBEIFOECPDDAA.acurtis@onz.com> (raw)
In-Reply-To: <9A1957CB9FC45A4FA6F35961093ABB8406456D89@srvmail-mtl.montreal.ubisoft.org>
We just had a similar problem. Perhaps since you just upgraded to another
kernel version, this may be your issue too. Our problem was that a symbolic
link to the loader was missing. (this seems to change between versions or
architectures)
Check /lib on the working file system. You should find a symbolic link
something like:
ld.so.1 -> ld.so.2.2.3
Make sure this is not different than what you have in cramfs.
Hope this helps.
> -----Original Message-----
> From: linux-mtd-admin@lists.infradead.org
> [mailto:linux-mtd-admin@lists.infradead.org]On Behalf Of Patrick Allaire
> Sent: Friday, January 04, 2002 8:19 AM
> To: linux-mtd@lists.infradead.org
> Cc: Patrick Allaire
> Subject: From 2.4.9 to CVS ???
>
>
>
> Hi,
>
> I was using the MTD drivers wich came with the linux 2.4.9 kernel source
> code ... now I have moved to 2.4.17 but I have also updated the
> mtd drivers
> with the CVS code, but I am no longer able to boot from my flash.
>
> MTD setup :
>
> MTD support
> MTD partitionning support
> Direct char device access to MTD devices
> Caching block device access to MTD devices
> Detect flash chips by Common Flash Interface (CFI) probe
>
> Support for ST flash chips (it a port from intel chips ... the only
> difference, is in the writing because st flash does not support word write
> ... only complete block writes, its a cfi_cmdset_0020 )
>
> CFI Flash device mapped on My Own Partitions ... same thing as 2.4.9
>
>
> Every thing is compiled fine ... at boot up, MTD find(probe) my flash, it
> printout the partioning it will do ... after that I get
>
> VFS: Mounted root (cramfs filesystem) readonly.
> Freeing unused kernel memory : 36k freed
> Kernel panic: No init found....
>
>
> I know from the last line that the problems is that the kernel cannot find
> /sbin/init ... but it is there, it is exactly the same cramfs I used on
> 2.4.9 when it was working !!! To be sure it was not corrupted, I redid the
> flashing of the /dev/mtdblock0 with my cramfs file ... with the same
> results.
>
> Any idea ???
>
> thank you.
>
> Patrick Allaire
> mailto:pallaire@gameloft.com
> If you can see it, but it's not there, it's virtual.
> If you can't see it, but it is there, it's hidden.
> It you can't see it and it isn't there, it's gone.
>
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2002-01-04 16:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 16:19 From 2.4.9 to CVS ??? Patrick Allaire
2002-01-04 16:24 ` Allen Curtis [this message]
2002-01-04 16:40 ` Björn Eriksson
-- strict thread matches above, loose matches on Subject: below --
2002-01-04 16:51 Patrick Allaire
2002-01-04 16:54 ` David Woodhouse
2002-01-04 17:01 Patrick Allaire
2002-01-04 17:01 ` David Woodhouse
2002-01-04 17:04 ` Allen Curtis
2002-01-04 18:38 Patrick Allaire
2002-01-04 19:07 Patrick Allaire
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=NCBBIINEHIPFGJPLBEIFOECPDDAA.acurtis@onz.com \
--to=acurtis@onz.com \
--cc=linux-mtd@lists.infradead.org \
--cc=pallaire@gameloft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox