Ubuntu FAT-implementation lacks EPOC/Psion support

Bug #251558 reported by krank23
8
Affects Status Importance Assigned to Milestone
Linux
Won't Fix
Low
linux (Ubuntu)
Incomplete
Undecided
Unassigned
Declined for Jaunty by Steve Langasek

Bug Description

The Ubuntu kernel, like most Linux kernels, doesn't support FAT in quite the same way Windows, for instance, does. This means, amongst other things, that the FAT-implementation used in the EPOC operating system of old Psion palmtop computers (such as the Psion 5mx) isn't quite compatible. A lot of garbage characters etc.

http://software.frodo.looijaard.name/fat-epoc/ has a very good explanation, and the patch is compatible with current Ubuntu kernel source.

To me, this seems like a bug in the FAT implementation rather than a simple feature request - and it shouldn't be that hard to implement, either. However, it's slightly above my own capacity at the moment.

Revision history for this message
Michael Rooney (mrooney) wrote :

Changing package to linux. I haven't looked at the patch, but in theory it is safe as according to the documentation, it only has an effect when the 'epoc' option is passed to mount. As such it wouldn't change any default behavior, but it would allow users who need it to add the 'epoc' argument and continue on.

Revision history for this message
krank23 (krank23) wrote :

Exactly.

Although I have as of yet been unsuccessful in automounting the card with the epoc option via hal, but remounting isn't very hard and it's a functional workaround.

Besides, if this would make it into the main source, I guess I could always file a gnome/hal-bug report to make it possible to automount with option 'epoc'.

If needed, I could probably make a drive image illustrating the problem using some kind of drive cloning software. If someone needs this in order to test the patch or whatever, just tell me and I'll do it.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
krank23 (krank23) wrote :

The problem remains in the 2.6.27 kernel.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi krank23,

Do you know if there has been any efforts to get these patches merged upstream? The reason I ask is that is it a lot of extra work for the kernel team to maintain of out tree patches. As such they typically require upstream submission first. Thanks.

Changed in linux:
status: New → Incomplete
Revision history for this message
Duane Hinnen (duanedesign) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Revision history for this message
krank23 (krank23) wrote :

Tested 2009-02-22 in Ubuntu Jaunty Alpha 4. The bug persists.

Regarding the question of whether it has been submitted upstream - I have no idea. I'd submit it myself if I know how. I'm not a total Linux noob, but I'm not that knowledgeable about the structural stuff, like where to submit what etc.

Revision history for this message
Duane Hinnen (duanedesign) wrote :

 Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at: http://bugzilla.kernel.org/show_bug.cgi?id=12755

krank23,
could you please visit the report I filed upstream. I tried to include what I knew about the bug, but I feel their might be some information that you can probably provide to make the report better. Thank You.

Changed in linux:
status: Unknown → Confirmed
Revision history for this message
Duane Hinnen (duanedesign) wrote :

Comment from upstream report.

Is this patch is about this thread?

http://marc.info/?t=107513944200003&r=1&w=2

The read would be compatible, but write is not compatible with FAT spec.
So, I think read side may be applied, but write part can't be applied.

Changed in linux:
status: Confirmed → Invalid
Changed in linux:
status: Invalid → Won't Fix
Changed in linux:
importance: Unknown → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.