yahmmu;570340 Wrote: > Is my Touch's memory failing? Just noticed these lines in the dmesg > output: > > > MXC MTD nand Driver 2.5 > NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB > 3,3V 8-bit) > Bad block table found at page 65472, version 0x01 > Bad block table found at page 65408, version 0x01 > nand_read_bbt: Bad block at 0x00d20000 > nand_read_bbt: Bad block at 0x02d60000 > nand_read_bbt: Bad block at 0x042a0000 > nand_read_bbt: Bad block at 0x04a00000 > nand_read_bbt: Bad block at 0x073e0000 > nand_read_bbt: Bad block at 0x07d20000 > RedBoot partition parsing not available > cmdlinepart partition parsing not available > Creating 2 MTD partitions on "NAND 128MiB 3,3V 8-bit": > 0x00000000-0x00080000 : "redboot" > 0x00080000-0x07f40000 : "ubi"
No that's perfectly normal - this was discussed extensively in beta - the memory is shipped with some bad blocks by the manufacturer. The typical number of bad blocks is less than 20 (IIRC). -- Phil Leigh You want to see the signal path BEFORE it gets onto a CD/vinyl...it ain't what you'd call minimal... Touch(wired/XP) - TACT 2.2X (Linear PSU) + Good Vibrations S/W - MF Triplethreat(Audiocom full mods) - Linn 5103 - Aktiv 5.1 system (6x LK140's, ESPEK/TRIKAN/KATAN/SEIZMIK 10.5), Townsend Supertweeters, Blue Jeans Digital,Kimber Speaker & Chord Interconnect cables Kitchen Boom, Outdoors: SB Radio ------------------------------------------------------------------------ Phil Leigh's Profile: http://forums.slimdevices.com/member.php?userid=85 View this thread: http://forums.slimdevices.com/showthread.php?t=81332 _______________________________________________ Touch mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/touch
