* [KJ] 720KB Floppy on 64bit Linux
@ 2006-05-02 21:03 Henne
2006-05-03 11:54 ` Henne
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: Henne @ 2006-05-02 21:03 UTC (permalink / raw)
To: kernel-janitors
Hi there!
I got an old 720KB dos floppy and wanted to try it with my x86_64 2.6.17-rc3 kernel.
Mounting it Kernel says:
FAT: invalid media value (0x44)
VFS: Can't find a valid FAT filesystem on dev fd0
I tried it on my pentium with the same kernel (i386, of course), and it works.
Mounted as vfat. All files there. No errors.
On the x86_64, noting.
Formatting a 1.44MB disk as 1.44MB works.
The integrity check on kfloppy works too.
Formatting a 1.44MB disk as 720KB works.
But checking integrity does not.
Kfloppy says that theres an error while low-level format on track 0.
Kernel says:
end_request: I/O error, dev fd0, sector 0
floppy0: Getstatus times out (50) on fdc 0
floppy driver state
-------------------
nowC15028397 last interruptC15028397 diff=0 last called handlerÿffffff80360d1d
timeout_message=floppy start
last output bytes:
2 90 4315027201
9 90 4315027201
50 90 4315027201
f6 90 4315027201
f 80 4315027600
0 90 4315027600
45 91 4315027600
8 81 4315027605
4d 80 4315027625
0 90 4315027625
2 90 4315027625
9 90 4315027625
50 90 4315027625
f6 90 4315027625
4d 80 4315027998
4 90 4315027998
2 90 4315027998
9 90 4315027998
50 90 4315027998
f6 90 4315027998
last result at 4315027998
last redo_fd_request at 4315027998
40 10 0 1 4 7 2
statusP
fdc_busy=1
fd_timer.functionÿffffff80362b84
timer_functionÿffffff8036301d
expires&01
nowC15028397
contÿffffff804b2b40
current_req\000000000000000
command_status=-1
floppy0: get result error. Fdc=0 Last statusÿffffff Read bytes=0
floppy driver state
-------------------
nowC15028397 last interruptC15028397 diff=0 last called handlerÿffffff80360d1d
timeout_message=floppy start
last output bytes:
2 90 4315027201
9 90 4315027201
50 90 4315027201
f6 90 4315027201
f 80 4315027600
0 90 4315027600
45 91 4315027600
8 81 4315027605
4d 80 4315027625
0 90 4315027625
2 90 4315027625
9 90 4315027625
50 90 4315027625
f6 90 4315027625
4d 80 4315027998
4 90 4315027998
2 90 4315027998
9 90 4315027998
50 90 4315027998
f6 90 4315027998
last result at 4315027998
last redo_fd_request at 4315027998
40 10 0 1 4 7 2
statusP
fdc_busy=1
fd_timer.functionÿffffff80362b84
timer_functionÿffffff8036301d
expires&01
nowC15028397
contÿffffff804b2b40
current_req\000000000000000
command_status=-1
floppy0: -- FDC reply errorend_request: I/O error, dev fd0, sector 0
Buffer I/O error on device fd0p16, logical block 0
floppy0: sector not found: track 0, head 0, sector 9, size 2
floppy0: sector not found: track 0, head 0, sector 9, size 2
end_request: I/O error, dev fd0, sector 8
Buffer I/O error on device fd0p16, logical block 1
floppy0: data CRC error: track 0, head 1, sector 8, size 2
floppy0: data CRC error: track 0, head 1, sector 8, size 2
end_request: I/O error, dev fd0, sector 16
Buffer I/O error on device fd0p16, logical block 2
floppy0: sector not found: track 1, head 0, sector 7, size 2
floppy0: data CRC error: track 1, head 0, sector 7, size 2
end_request: I/O error, dev fd0, sector 24
Buffer I/O error on device fd0p16, logical block 3
floppy0: data CRC error: track 1, head 1, sector 6, size 2
floppy0: data CRC error: track 1, head 1, sector 6, size 2
end_request: I/O error, dev fd0, sector 32
Buffer I/O error on device fd0p16, logical block 4
floppy0: data CRC error: track 2, head 0, sector 5, size 2
floppy0: data CRC error: track 2, head 0, sector 5, size 2
end_request: I/O error, dev fd0, sector 40
Buffer I/O error on device fd0p16, logical block 5
end_request: I/O error, dev fd0, sector 48
Buffer I/O error on device fd0p16, logical block 6
floppy0: data CRC error: track 3, head 0, sector 3, size 2
floppy0: data CRC error: track 3, head 0, sector 3, size 2
end_request: I/O error, dev fd0, sector 56
Buffer I/O error on device fd0p16, logical block 7
floppy0: data CRC error: track 0, head 0, sector 1, size 2
end_request: I/O error, dev fd0, sector 0
Buffer I/O error on device fd0p16, logical block 0
Maybe someone could format a floppy (1.44MB/720KB) as a 720KB too and send the results?
Greets,
Henne
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [KJ] 720KB Floppy on 64bit Linux
2006-05-02 21:03 [KJ] 720KB Floppy on 64bit Linux Henne
@ 2006-05-03 11:54 ` Henne
2006-05-04 0:38 ` Randy.Dunlap
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: Henne @ 2006-05-03 11:54 UTC (permalink / raw)
To: kernel-janitors
Henne wrote:
> Mounting it Kernel says:
> FAT: invalid media value (0x44)
> VFS: Can't find a valid FAT filesystem on dev fd0
I found out something interesting:
I made an image of my old disk with dd and here's the hexdump of the bootsector:
00000000 eb 3c 90 4d 53 44 4f 53 35 2e 90 6e 02 02 7f cf |.<.MSDOS5..n....|
00000010 eb 3c 90 4d 53 44 4f 53 35 2e 30 00 02 02 01 00 |.<.MSDOS5.0.....|
00000020 02 70 00 a0 05 f9 03 00 09 00 02 00 00 00 00 00 |.p..............|
00000030 00 00 00 00 00 00 29 dc 1c 2c 02 00 53 41 00 00 |......)..,..SA..|
You may notice, that the media invalid media value (0x44) is that from offset 0x15.
But on the disk image the correct value is on offset 0x25 (the 0xf9), so struct fat_boot_sector
must start on 0x10 to work correctly.
IN THIS CASE!
"Normal" 1.44MB FAT disks have a bootsector like this one:
00000000 eb 3c 90 4d 53 44 4f 53 35 33 79 00 02 01 01 00 |.<.MSDOS53y.....|
00000010 02 e0 00 40 0b f0 09 00 12 00 02 00 00 00 00 00 |...@............|
00000020 00 00 00 00 00 00 29 45 49 53 41 53 59 53 52 4f |......)EISASYSRO|
00000030 4d 35 20 20 20 20 46 41 54 31 32 20 20 20 fa 33 |M5 FAT12 .3|
So there everything is allright!
But why everything works under i386 and not under x86_64?
Henne
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [KJ] 720KB Floppy on 64bit Linux
2006-05-02 21:03 [KJ] 720KB Floppy on 64bit Linux Henne
2006-05-03 11:54 ` Henne
@ 2006-05-04 0:38 ` Randy.Dunlap
2006-05-04 9:27 ` Henne
2006-05-04 17:01 ` Randy.Dunlap
3 siblings, 0 replies; 5+ messages in thread
From: Randy.Dunlap @ 2006-05-04 0:38 UTC (permalink / raw)
To: kernel-janitors
[-- Attachment #1: Type: text/plain, Size: 1634 bytes --]
On Wed, 03 May 2006 13:54:04 +0200 Henne wrote:
> Henne wrote:
> > Mounting it Kernel says:
> > FAT: invalid media value (0x44)
> > VFS: Can't find a valid FAT filesystem on dev fd0
>
> I found out something interesting:
> I made an image of my old disk with dd and here's the hexdump of the bootsector:
>
> 00000000 eb 3c 90 4d 53 44 4f 53 35 2e 90 6e 02 02 7f cf |.<.MSDOS5..n....|
> 00000010 eb 3c 90 4d 53 44 4f 53 35 2e 30 00 02 02 01 00 |.<.MSDOS5.0.....|
> 00000020 02 70 00 a0 05 f9 03 00 09 00 02 00 00 00 00 00 |.p..............|
> 00000030 00 00 00 00 00 00 29 dc 1c 2c 02 00 53 41 00 00 |......)..,..SA..|
>
> You may notice, that the media invalid media value (0x44) is that from offset 0x15.
Yes, but part of that line looks wrong (like duplicated from above).
Suspicious.
> But on the disk image the correct value is on offset 0x25 (the 0xf9), so struct fat_boot_sector
> must start on 0x10 to work correctly.
Yes, looks weird.
> IN THIS CASE!
>
> "Normal" 1.44MB FAT disks have a bootsector like this one:
>
> 00000000 eb 3c 90 4d 53 44 4f 53 35 33 79 00 02 01 01 00 |.<.MSDOS53y.....|
> 00000010 02 e0 00 40 0b f0 09 00 12 00 02 00 00 00 00 00 |...@............|
> 00000020 00 00 00 00 00 00 29 45 49 53 41 53 59 53 52 4f |......)EISASYSRO|
> 00000030 4d 35 20 20 20 20 46 41 54 31 32 20 20 20 fa 33 |M5 FAT12 .3|
>
> So there everything is allright!
>
> But why everything works under i386 and not under x86_64?
I tested on x86_64 with no problems. Formatted a 720 KB floppy
and a 1.4 MB floppy using both mkdosfs and kfloppy, mounted and
read them both fine.
---
~Randy
[-- Attachment #2: Type: text/plain, Size: 168 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [KJ] 720KB Floppy on 64bit Linux
2006-05-02 21:03 [KJ] 720KB Floppy on 64bit Linux Henne
2006-05-03 11:54 ` Henne
2006-05-04 0:38 ` Randy.Dunlap
@ 2006-05-04 9:27 ` Henne
2006-05-04 17:01 ` Randy.Dunlap
3 siblings, 0 replies; 5+ messages in thread
From: Henne @ 2006-05-04 9:27 UTC (permalink / raw)
To: kernel-janitors
Randy.Dunlap wrote:
>> Henne wrote:
>>> Mounting it Kernel says:
>>> FAT: invalid media value (0x44)
>>> VFS: Can't find a valid FAT filesystem on dev fd0
>> I found out something interesting:
>> I made an image of my old disk with dd and here's the hexdump of the bootsector:
>>
>> 00000000 eb 3c 90 4d 53 44 4f 53 35 2e 90 6e 02 02 7f cf |.<.MSDOS5..n....|
>> 00000010 eb 3c 90 4d 53 44 4f 53 35 2e 30 00 02 02 01 00 |.<.MSDOS5.0.....|
>> 00000020 02 70 00 a0 05 f9 03 00 09 00 02 00 00 00 00 00 |.p..............|
>> 00000030 00 00 00 00 00 00 29 dc 1c 2c 02 00 53 41 00 00 |......)..,..SA..|
>>
>> You may notice, that the media invalid media value (0x44) is that from offset 0x15.
>
> Yes, but part of that line looks wrong (like duplicated from above).
> Suspicious.
>
>> But on the disk image the correct value is on offset 0x25 (the 0xf9), so struct fat_boot_sector
>> must start on 0x10 to work correctly.
>
> Yes, looks weird.
>
>> IN THIS CASE!
>>
>> "Normal" 1.44MB FAT disks have a bootsector like this one:
>>
>> 00000000 eb 3c 90 4d 53 44 4f 53 35 33 79 00 02 01 01 00 |.<.MSDOS53y.....|
>> 00000010 02 e0 00 40 0b f0 09 00 12 00 02 00 00 00 00 00 |...@............|
>> 00000020 00 00 00 00 00 00 29 45 49 53 41 53 59 53 52 4f |......)EISASYSRO|
>> 00000030 4d 35 20 20 20 20 46 41 54 31 32 20 20 20 fa 33 |M5 FAT12 .3|
>>
>> So there everything is allright!
>>
>> But why everything works under i386 and not under x86_64?
>
> I tested on x86_64 with no problems. Formatted a 720 KB floppy
> and a 1.4 MB floppy using both mkdosfs and kfloppy, mounted and
> read them both fine.
But I don't understand why a slackware10.2/2.6.17-rc3(selfcompiled) got it,
and Suse10.0_64/2.6.17-rc3(selfcompiled) got it not.
I have also FREEDOS on my i386 which got it too. Strange..
The disks are 3.5 inch with no hole on the left side, are purchased by EBay and seem to be original.
They are from the game "Das schwarze Auge-Schicksalsklinge" which is the german original of "Realms of arkania-Blade of destiny".
And if the work under FREEDOS and i386 I can't belive that the disks are broken.
Nevertheless it is not critical for me, since I got the files from my i386 and moved it to my x86_64.
It's nice to see how you can bypass the install routine with open-source tools and a little knowledge how to use them :) .
But the main question is: Why does it not work?
Can you send the first 5 lines of the disks you formatted, please?
And also try to format a 1.44 disk to 720.
Greets,
Henne
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [KJ] 720KB Floppy on 64bit Linux
2006-05-02 21:03 [KJ] 720KB Floppy on 64bit Linux Henne
` (2 preceding siblings ...)
2006-05-04 9:27 ` Henne
@ 2006-05-04 17:01 ` Randy.Dunlap
3 siblings, 0 replies; 5+ messages in thread
From: Randy.Dunlap @ 2006-05-04 17:01 UTC (permalink / raw)
To: kernel-janitors
[-- Attachment #1: Type: text/plain, Size: 3874 bytes --]
On Thu, 04 May 2006 11:27:30 +0200 Henne wrote:
> Randy.Dunlap wrote:
> >> Henne wrote:
> >>> Mounting it Kernel says:
> >>> FAT: invalid media value (0x44)
> >>> VFS: Can't find a valid FAT filesystem on dev fd0
> >> I found out something interesting:
> >> I made an image of my old disk with dd and here's the hexdump of the bootsector:
> >>
> >> 00000000 eb 3c 90 4d 53 44 4f 53 35 2e 90 6e 02 02 7f cf |.<.MSDOS5..n....|
> >> 00000010 eb 3c 90 4d 53 44 4f 53 35 2e 30 00 02 02 01 00 |.<.MSDOS5.0.....|
> >> 00000020 02 70 00 a0 05 f9 03 00 09 00 02 00 00 00 00 00 |.p..............|
> >> 00000030 00 00 00 00 00 00 29 dc 1c 2c 02 00 53 41 00 00 |......)..,..SA..|
> >>
> >> You may notice, that the media invalid media value (0x44) is that from offset 0x15.
> >
> > Yes, but part of that line looks wrong (like duplicated from above).
> > Suspicious.
> >
> >> But on the disk image the correct value is on offset 0x25 (the 0xf9), so struct fat_boot_sector
> >> must start on 0x10 to work correctly.
> >
> > Yes, looks weird.
> >
> >> IN THIS CASE!
> >>
> >> "Normal" 1.44MB FAT disks have a bootsector like this one:
> >>
> >> 00000000 eb 3c 90 4d 53 44 4f 53 35 33 79 00 02 01 01 00 |.<.MSDOS53y.....|
> >> 00000010 02 e0 00 40 0b f0 09 00 12 00 02 00 00 00 00 00 |...@............|
> >> 00000020 00 00 00 00 00 00 29 45 49 53 41 53 59 53 52 4f |......)EISASYSRO|
> >> 00000030 4d 35 20 20 20 20 46 41 54 31 32 20 20 20 fa 33 |M5 FAT12 .3|
> >>
> >> So there everything is allright!
> >>
> >> But why everything works under i386 and not under x86_64?
> >
> > I tested on x86_64 with no problems. Formatted a 720 KB floppy
> > and a 1.4 MB floppy using both mkdosfs and kfloppy, mounted and
> > read them both fine.
>
> But I don't understand why a slackware10.2/2.6.17-rc3(selfcompiled) got it,
> and Suse10.0_64/2.6.17-rc3(selfcompiled) got it not.
> I have also FREEDOS on my i386 which got it too. Strange..
> The disks are 3.5 inch with no hole on the left side, are purchased by EBay and seem to be original.
> They are from the game "Das schwarze Auge-Schicksalsklinge" which is the german original of "Realms of arkania-Blade of destiny".
> And if the work under FREEDOS and i386 I can't belive that the disks are broken.
> Nevertheless it is not critical for me, since I got the files from my i386 and moved it to my x86_64.
Good for you, glad to hear that you worked around it, whatever "it" is.
But if there is a more general/global problem, I would think that we
would have heard about it by now...
Please compare your boot sector(s) with this:
http://www.win.tue.nl/~aeb/linux/fs/fat/fat-1.html#ss1.2
> It's nice to see how you can bypass the install routine with open-source tools and a little knowledge how to use them :) .
>
> But the main question is: Why does it not work?
> Can you send the first 5 lines of the disks you formatted, please?
> And also try to format a 1.44 disk to 720.
I cannot successfully format a 1.4 MB floppy to 720 KB -- it always
has I/O errors.
Here's is boot sector from a 720 KB floppy:
000000 eb 3c 90 6d 6b 64 6f 73 66 73 00 00 02 02 01 00 >.<.mkdosfs......<
000010 02 70 00 a0 05 f9 03 00 09 00 02 00 00 00 00 00 >.p..............<
000020 00 00 00 00 00 00 29 ad 47 59 44 4b 44 45 20 46 >......).GYDKDE F<
000030 6c 6f 70 70 79 20 46 41 54 31 32 20 20 20 0e 1f >loppy FAT12 ..<
000040 be 5b 7c ac 22 c0 74 0b 56 b4 0e bb 07 00 cd 10 >.[|.".t.V.......<
and from a 1.4 MB floppy:
000000 eb 3c 90 6d 6b 64 6f 73 66 73 00 00 02 01 01 00 >.<.mkdosfs......<
000010 02 e0 00 40 0b f0 09 00 12 00 02 00 00 00 00 00 >...@............<
000020 00 00 00 00 00 00 29 f9 47 59 44 4b 44 45 20 46 >......).GYDKDE F<
000030 6c 6f 70 70 79 20 46 41 54 31 32 20 20 20 0e 1f >loppy FAT12 ..<
000040 be 5b 7c ac 22 c0 74 0b 56 b4 0e bb 07 00 cd 10 >.[|.".t.V.......<
---
~Randy
[-- Attachment #2: Type: text/plain, Size: 168 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2006-05-04 17:01 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-05-02 21:03 [KJ] 720KB Floppy on 64bit Linux Henne
2006-05-03 11:54 ` Henne
2006-05-04 0:38 ` Randy.Dunlap
2006-05-04 9:27 ` Henne
2006-05-04 17:01 ` Randy.Dunlap
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.