no success

no success

[Rodrigo Moya]

Hi all!

I've put the MTD drivers into the kernel, and I'm booting linux from the
ZIP drive. Once it boots, I try to access the nftl* devices with fdisk,
but I've got always the same error about:

could not open /dev/nftl*

What am I doing wrong?

I'm using the 1.23 version of nftl.c, as David said this was the last
one which worked, but with the current CVS version of this file the
results are the same.

Cheers


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

Re: no success

[Rodrigo Moya]

Dvir Oren wrote:
> 
> Rodrigo Moya writes ("no success"):
> 
> > could not open /dev/nftl*
> 
> Does /dev/nftl? have the correct major number (93)?
> 
yes, all the nftla* devices have 93 as major number. Another thing, is
that the kernel displays no messages about the MTD drivers. Should it
show something?


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

Re: no success

[David Woodhouse]

On Mon, 17 Apr 2000, Rodrigo Moya wrote:

> yes, all the nftla* devices have 93 as major number. Another thing, is
> that the kernel displays no messages about the MTD drivers. Should it
> show something?

It should. Are you sure you patched the init routines in properly? The
patch in the CVS patches (?) directory ought to work. Anyway, I'm
supposed to be on holiday. Trevor?

--
dwmw2



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

Re: no success

[Trevor Woolven]

David Woodhouse wrote:
> 
> On Mon, 17 Apr 2000, Rodrigo Moya wrote:
> 
> > yes, all the nftla* devices have 93 as major number. Another thing, is
> > that the kernel displays no messages about the MTD drivers. Should it
> > show something?
> 
> It should. Are you sure you patched the init routines in properly? The
> patch in the CVS patches (?) directory ought to work. Anyway, I'm
> supposed to be on holiday. Trevor?
> 
> --
> dwmw2
Hi,

Apologies but I've been away for 10 days or so.
It sounds to me as if the init routines have not been set-up correctly
as Dave suggested.

linux/init/main.c - do_basic_setup() calls init_mtd()
mtd.c - init_mtd() calls the rest of the configured init routines.

I can't remember if there's much screen output to see, there should be
something. If in doubt, try enabling the DBG output, (recompile with
-DZDBG).

Hope this helps, if not get back to me with some more details

Cheers

Trev.
-- 
Zentropix Inc - a Lineo company

Tel: +44 (0)1273 234 647	 Fax: +44 (0)1273 704 482

Visit http://www.zentropix.com/ for Real Time Linux Tools
Visit http://www.realtimelinux.org/ for Real Time Linux Information


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

Re: no success

[Rodrigo Moya]

> Hi,
> 
> Apologies but I've been away for 10 days or so.
> It sounds to me as if the init routines have not been set-up correctly
> as Dave suggested.
> 
> linux/init/main.c - do_basic_setup() calls init_mtd()
> mtd.c - init_mtd() calls the rest of the configured init routines.
> 
> I can't remember if there's much screen output to see, there should be
> something. If in doubt, try enabling the DBG output, (recompile with
> -DZDBG).
> 
> Hope this helps, if not get back to me with some more details
> 
It was my fault, I had applied the patch, but in a different directory,
and my makefile wasn't copying the patched init/main.c file. Sorry.

But now, I'm compiling with this fixed, and I get undefined references
to register_mtd_notifier and unregister_mtd_notifier, which are not in
the source tree I've got here. I've even dropped today the directory and
checked out from CVS a fresh copy.

And these two functions are neither in the linux source tree.

Thanks for your help!



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

no success

[Rodrigo Moya]

Hi all!

It's me again with my strange problems. I've finally successfully run lilo
on the DOC, and reboot, and now I get a normal LILO prompt (not as the
other day, where I was getting strange characters in the LILO prompt), but:

LILO boot:
Loading linux................
Uncompressing Linux... Ok, booting the kernel

and it stops there!

When running lilo, there was no error messages (I even run it with -v -v to
see all messages, and everything seemed ok)

When I run this kernel booting linux from DOS and from a ZIP drive, the DOC
is detected and everything seems fine. So, I don't know where the problem
is.

I've run rdev also on the device with the kernel.

Thanks



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org