From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from colibri.its.uu.se ([130.238.4.154]) by canuck.infradead.org with esmtp (Exim 4.62 #1 (Red Hat Linux)) id 1GD0yX-0000gw-UM for linux-mtd@lists.infradead.org; Tue, 15 Aug 2006 11:37:09 -0400 Date: Tue, 15 Aug 2006 17:36:49 +0200 To: Katey Yu Subject: Re: write-protected Message-ID: <20060815153649.GF3622@Update.UU.SE> References: <007020085773234AAACE3B66E13C18E8D71CB3@MAILSRVR.ositech.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <007020085773234AAACE3B66E13C18E8D71CB3@MAILSRVR.ositech.com> From: samuel@Update.UU.SE (Samuel ]slund) Cc: linux-mtd@lists.infradead.org List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, Aug 14, 2006 at 04:44:01PM -0400, Katey Yu wrote: > Hello, > > When I mount /dev/mtdblock3 in flash I get block " block device > /dev/mtdblock3 is write-protected, mounting read-only". I should get > mtdblock_open? > > Could somebody tell me what's wrong? > > > > > > mount -t jffs2 /dev/mtdblock3 /var/tmp > > mount: block device /dev/mtdblock3 is write-protected, mounting > read-only You do not give very much information about your system... Ok, assuming you have set up the block device correctly. I had a similar problem that boiled down to that the driver from the manufacturer hardcoded the partition to be read-only. in my case the apropriate file was: linux/arch/arm/mach-ks8695/ks8695_mm.c The partition had been set read-only by adding: .mask_flags = MTD_WRITABLE to the partition struct. HTH //Samuel