Hi,
We think that the problem may lie with the version of jffs2 in the
2.4.3-rmk2-np1 kernel using excessive amounts of memory. The problem doesn't
seem to happen oun our test box, configured with less memory, and more disk.
(It is not an iPAQ however).
We have yet to test on the iPAQ under a newer kernel.
could you cat /proc/slabinfo when the drive is mounted and post it back to
me.
Thanks,
Jim
-----Original Message-----
From: intimate-admin@handhelds.org
[mailto:intimate-admin@handhelds.org]On Behalf Of Matthew Horrobin
Sent: 28 June 2001 21:36
To: intimate@handhelds.org
Subject: [Intimate] apt-get errors with jffs2.
Hi,
I attempted an install of intimate on a 340Mb udrive using the new blkmtd
driver. I used the .tgz version of the installation, and most things are
working fine, but there is problem with apt-get, I keep getting messages
like:
mhipaq:~# apt-get install task-kde
Reading Package Lists... Error!
E: Couldn't make mmap of 6291457 bytes - mmap (22 Invalid argument)
W: Unable to munmap
E: The package lists or status file could not be parsed or opened.
mhipaq:~#
Any ideas?
The install is the same as that in the script.
Creating the jffs2 udrive was slightly odd:
insmod blkmtd-arm.o device=/dev/hda1
correctly assigned the drive to /dev/mtdblock4, but
einfo /dev/mtdblock4
produces no output. So I couldn't do the erase step, and I didn't have the
info to do mkfs.jff2. Instead just doing a:
mount -t jffs2 /dev/mtdblock4 /mnt/hda1
appeared to work. (Mounting after 5-10 minutes of work, reporting a
different size to that availabe with ext2).
What is mkfs.jffs2 deigned to do? Format a new drive or create a full
jffs2 filesystem from an existing directory structure?
Thanks
Matthew
_______________________________________________
Intimate mailing list
Intimate@handhelds.org
http://handhelds.org/mailman/listinfo/intimate
Received on Fri Jun 29 18:18:27 2001
This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:42:39 EDT