Hi, This was working before :) (at least with barebox version 2015.10). Honestly , this may be a misconfiguration on our part (and the fact that it worked doesn't mean that it was a normal behavior). Here is the output: filetype /dev/mmc2.netcom /dev/mmc2.netcom: MBR sector (mbr) And it is cleary different with a working partition: filetype /dev/mmc1.0 /dev/mmc1.0: FAT filesytem (fat) I format the partitions with fatfs f_mkfs, and I do not use f_disk to create partition table. This could be the problem. I'll check that point. Best regards, -- Philippe LEDUC ledphilippe@xxxxxxxxx 2016-02-25 9:56 GMT+01:00 Sascha Hauer <s.hauer@xxxxxxxxxxxxxx>: > On Wed, Feb 24, 2016 at 05:44:42PM +0100, Philippe Leduc wrote: >> Hi, >> >> It seems that there is a regression in the mount command for fat >> filesystem: if I try to mount a partition that is formatted with >> fatfs, I got this error: >> >> mount /dev/mmc2.netcom >> mount: No such file or directory >> >> I do not have the problem with a fat formatted with Windows or Linux. >> >> Do you have an idea? > > Are you sure this is a regression? Did this work before? I don't think > that FAT support in general is broken, it's probably something with your > special setup. > > What does 'filetype /dev/mmc2.netcom' give you? > > Sascha > > -- > Pengutronix e.K. | | > Industrial Linux Solutions | http://www.pengutronix.de/ | > Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
