Fdutils April 2005

fdutils@fdutils.linux.lu

3 participants
2 discussions

3.84MB floppy image with superformat
by Rudi Langhanki 15 Apr '05

15 Apr '05

Background: I am using pxelinux (with memdisk) on a linux server to allow some diskless clients to boot an MS-DOS boot image from LAN. This works fine for 1.44MB images. I also succeeded in creating a 2.88MB (floppy image) with help of dd (grab the 1.44MB bootsector) mtools (mformat a 2.88MB image file including the above bootsector) copying io.sys, msdos.sys, command.com to the just created and mounted image But I need an even larger DOS-Partition via boot from LAN. With my knowledges I reached the limit of 2.88MB by using mformat: > mformat -t 80 -s 36 -h 2 -C -B fddbootsector x: where x: is defined in ~/.mtoolsrc as the resulting image file. I tried to increase the values in the mformat command, but the resulting image was no longer bootable. I tried to use an MBR of an existing HDD and the 8MB DOS-partition, not bootable. What am I doing wrong? Any help possible? At least, do I have the chance to go up to a 3.84MB floppy image? For this I did not find any cylinder, sector, head numbers on the web. Do you know the correct settings for such a floppy? And, very important, I don't have any high capacity floppy disk drives at hand. I try to create a floppy image to use it for boot from lan. Thanks for any help. __________________________________________________________ Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min. weltweit telefonieren! http://freephone.web.de/?mc=021201 _______________________________________________ fdutils mailing list fdutils(a)tux.org http://www.tux.org/mailman/listinfo/fdutils

1 0

Trying to read/write a 5.25" drive with Fedora 2
by David Carter-Hitchin 03 Apr '05

03 Apr '05

Hi There, I really hope someone can help me get my 5.25" floppy drive working (/dev/fd1). I am stuck with "Input/output error" and similar messages. Here is my system (Redhat Fedora 2): uname: ------ Linux localhost.localdomain 2.6.5-1.358custom #1 Thu Aug 26 22:25:19 BST 2004 i686 athlon i386 GNU/Linux dmesg says: ----------- ide-floppy driver 0.99.newide . . . inserting floppy driver for 2.6.5-1.358custom Floppy drive(s): fd0 is 1.44M, fd1 is 1.2M FDC 0 is a post-1991 82077 floppycontrol ------------- [root@localhost david]# floppycontrol -pP --printfdcstate abort= 3 readtrack= 1 recalibrate= 0 reset= 2 reporting= 2 debug cmos= 4 hlt= 16 hut= 16 srt= 4000 spindown= 3000 spinup= 400 select_delay= 20 rps= 5 spindown_offset= 10 cylinders= 83 tracks= 83 timeout= 3000 interleave= 20 checkfreq= 1500 native_format= 7 autodetect seq.= 7,4,25,22,31,21,29,11 flags: debug verify disk_changed spinup= -257722 select= -257676 first_read= 0 probed_fmt= 0 cylinder= -3 maxblock= 0 maxcylinder= 0 generation= 0 keep data= 0 refs= 1 device= 0 last_checked= 0 spec1=ffffffff spec2=ffffffff rate=0 rawcmd=0 dor=d version=52 reset=0 need_configure=1 has_fifo=0 perp_mode=1 address=3f0 devs ---- [root@localhost david]# ls -l /dev/fd[01]* brw-rw---- 1 david floppy 2, 0 Mar 31 22:07 /dev/fd0 brw-rw---- 1 david floppy 2, 84 Mar 31 22:07 /dev/fd0u1040 brw-rw---- 1 david floppy 2, 88 Mar 31 22:07 /dev/fd0u1120 brw-rw---- 1 david floppy 2, 28 Mar 31 22:07 /dev/fd0u1440 brw-rw---- 1 david floppy 2, 124 Mar 31 22:07 /dev/fd0u1600 brw-rw---- 1 david floppy 2, 44 Mar 31 22:07 /dev/fd0u1680 brw-rw---- 1 david floppy 2, 60 Mar 31 22:07 /dev/fd0u1722 brw-rw---- 1 david floppy 2, 76 Mar 31 22:07 /dev/fd0u1743 brw-rw---- 1 david floppy 2, 96 Mar 31 22:07 /dev/fd0u1760 brw-rw---- 1 david floppy 2, 116 Mar 31 22:07 /dev/fd0u1840 brw-rw---- 1 david floppy 2, 100 Mar 31 22:07 /dev/fd0u1920 brw-rw---- 1 david floppy 2, 12 Mar 31 22:07 /dev/fd0u360 brw-rw---- 1 david floppy 2, 16 Mar 31 22:07 /dev/fd0u720 brw-rw---- 1 david floppy 2, 120 Mar 31 22:07 /dev/fd0u800 brw-rw---- 1 david floppy 2, 52 Mar 31 22:07 /dev/fd0u820 brw-rw---- 1 david floppy 2, 68 Mar 31 22:07 /dev/fd0u830 brw-rw---- 1 david floppy 2, 1 Mar 31 22:07 /dev/fd1 brw-rw---- 1 david floppy 2, 9 Mar 31 22:07 /dev/fd1h1200 brw-rw---- 1 david floppy 2, 41 Mar 31 22:07 /dev/fd1h1440 brw-rw---- 1 david floppy 2, 57 Mar 31 22:07 /dev/fd1h1476 brw-rw---- 1 david floppy 2, 73 Mar 31 22:07 /dev/fd1h1494 brw-rw---- 1 david floppy 2, 93 Mar 31 22:07 /dev/fd1h1600 brw-rw---- 1 david floppy 2, 21 Mar 31 22:07 /dev/fd1h360 brw-rw---- 1 david floppy 2, 49 Mar 31 22:07 /dev/fd1h410 brw-rw---- 1 david floppy 2, 65 Mar 31 22:07 /dev/fd1h420 brw-rw---- 1 david floppy 2, 25 Mar 31 22:07 /dev/fd1h720 brw-rw---- 1 david floppy 2, 81 Mar 31 22:07 /dev/fd1h880 Whatever I do (mount, superformat, fdformat...) , I get either "I/O Error" or "not a valid device" type errors. I have tried things like for f in `ls /dev/fd1*` do mount $f /mnt/floppy done On most of these commands the LED light comes on the drive, so it is definiely alive. Also it works OK from DOS - I managed to write 3 Minix boot disks with it which work fine, so the drive is physically OK. I am also working with a batch of pristine diskettes which were never used before I touched them, so I doubt they are a factor. Here is the console after 'floppycontrol --debug' and a 'superformat /dev/fd1': Apr 1 22:16:34 localhost kernel: floppy1: reschedule timeout lock fdc Apr 1 22:16:34 localhost kernel: floppy1: reschedule timeout lock fdc Apr 1 22:16:34 localhost kernel: floppy1: reschedule timeout floppy start Apr 1 22:16:34 localhost kernel: floppy1: setting NEWCHANGE in floppy_start Apr 1 22:16:34 localhost kernel: floppy1: calling disk change from floppy_readyApr 1 22:16:34 localhost kernel: floppy1: checking disk change line for drive 1Apr 1 22:16:34 localhost kernel: floppy1: jiffies=899735 Apr 1 22:16:34 localhost kernel: floppy1: disk change line=0 Apr 1 22:16:34 localhost kernel: floppy1: flags=36 Apr 1 22:16:34 localhost kernel: floppy1: calling disk change from seek Apr 1 22:16:34 localhost kernel: floppy1: checking disk change line for drive 1Apr 1 22:16:34 localhost kernel: floppy1: jiffies=899735 Apr 1 22:16:34 localhost kernel: floppy1: disk change line=0 Apr 1 22:16:34 localhost kernel: floppy1: flags=32 Apr 1 22:16:34 localhost kernel: recalibrate floppy: dtime=20 Apr 1 22:16:34 localhost kernel: recal interrupt: dtime=20 Apr 1 22:16:34 localhost kernel: floppy1: calling disk change from floppy_readyApr 1 22:16:34 localhost kernel: floppy1: checking disk change line for drive 1Apr 1 22:16:34 localhost kernel: floppy1: jiffies=899736 Apr 1 22:16:34 localhost kernel: floppy1: disk change line=0 Apr 1 22:16:34 localhost kernel: floppy1: flags=32 Apr 1 22:16:34 localhost kernel: floppy1: calling disk change from seek Apr 1 22:16:34 localhost kernel: floppy1: checking disk change line for drive 1Apr 1 22:16:34 localhost kernel: floppy1: jiffies=899736 Apr 1 22:16:34 localhost kernel: floppy1: disk change line=0 Apr 1 22:16:34 localhost kernel: floppy1: flags=32 Apr 1 22:16:34 localhost kernel: floppy1: checking whether disk is write protected Apr 1 22:16:34 localhost kernel: floppy1: wp=0 Apr 1 22:16:34 localhost kernel: rw_command: dtime=21 Apr 1 22:16:34 localhost kernel: floppy1: calling disk change from watchdog Apr 1 22:16:34 localhost kernel: floppy1: checking disk change line for drive 1Apr 1 22:16:34 localhost kernel: floppy1: jiffies=899736 Apr 1 22:16:34 localhost kernel: floppy1: disk change line=0 Apr 1 22:16:34 localhost kernel: floppy1: flags=30 Apr 1 22:16:34 localhost kernel: floppy1: calling disk change from watchdog Apr 1 22:16:34 localhost kernel: floppy1: checking disk change line for drive 1Apr 1 22:16:34 localhost kernel: floppy1: jiffies=899836 Apr 1 22:16:34 localhost kernel: floppy1: disk change line=0 Apr 1 22:16:34 localhost kernel: floppy1: flags=30 Apr 1 22:16:34 localhost kernel: floppy1: calling disk change from watchdog Apr 1 22:16:34 localhost kernel: floppy1: checking disk change line for drive 1Apr 1 22:16:34 localhost kernel: floppy1: jiffies=899936 Apr 1 22:16:34 localhost kernel: floppy1: disk change line=0 Apr 1 22:16:34 localhost kernel: floppy1: flags=30 Apr 1 22:16:34 localhost kernel: floppy1: calling disk change from watchdog Apr 1 22:16:34 localhost kernel: floppy1: checking disk change line for drive 1Apr 1 22:16:34 localhost kernel: floppy1: jiffies=900036 Apr 1 22:16:34 localhost kernel: floppy1: disk change line=0 Apr 1 22:16:34 localhost kernel: floppy1: flags=30 Apr 1 22:16:34 localhost kernel: floppy1: calling disk change from watchdog Apr 1 22:16:34 localhost kernel: floppy1: checking disk change line for drive 1Apr 1 22:16:34 localhost kernel: floppy1: jiffies=900136 Apr 1 22:16:34 localhost kernel: floppy1: disk change line=80 Apr 1 22:16:34 localhost kernel: floppy1: flags=30 Apr 1 22:16:34 localhost kernel: floppy1: disk removed during i/o Apr 1 22:16:34 localhost kernel: reset interrupt: dtime=422 Apr 1 22:16:34 localhost kernel: floppy1: reschedule timeout do wakeup Apr 1 22:16:34 localhost kernel: floppy1: calling disk change from raw_cmd ioctl Apr 1 22:16:37 localhost kernel: floppy1: calling disk change from set_dor Apr 1 22:16:37 localhost kernel: floppy1: checking disk change line for drive 1Apr 1 22:16:37 localhost kernel: floppy1: jiffies=903014 Apr 1 22:16:37 localhost kernel: floppy1: disk change line=80 Apr 1 22:16:37 localhost kernel: floppy1: flags=32 Not sure what other information I should supply. I have been trying to get this to work for a long time, and am feeling a little insane now with this problem. My 3.5" floppy drive (/dev/fd0) works fine, so the controller is ok, I guess. Anyone got any clues which may help me? Are there some cunning kernel options I can try (building or booting with)? Or perhaps there is something wrong with my devices (I have tried remaking them with the MAKEFLOPPIES script). Many thanks, David. _______________________________________________ fdutils mailing list fdutils(a)tux.org http://www.tux.org/mailman/listinfo/fdutils

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Fdutils April 2005