Prev: Linux Chipset Compatibility List?
Next: Samsung TRUTION TWC-3500 webcam on linux
From: Haines Brown on 4 Sep 2005 17:05
On a new machine (debian sarge 2.6.8-2-686), I'm having trouble using
device interfaces. I had a lot of "FIFO stuck" messages, but since
rebooting, these have disappeared. I can boot from a grub floppy disk
OK.

In kern.log, during boot, I have:

kernel: inserting floppy driver for 2.6.8-2-686
kernel: Floppy drive(s): fd0 is 1.44M
kernel: FDC 0 is a post-1991 82077
kernel: parport: PnPBIOS parport detected.
kernel: parport0: PC-style at 0x378 (0x778), irq 7, dma 3
[PCSPP,TRISTATE,COMPAT,ECP,DMA]

Once booted:

$ ls -l /media | grep floppy
drwxr-xr-x 2 brownh brownh 48 Dec 6 2004 floppy

$ ls -l /dev/fd0
brw-rw---- 1 root floppy 2, 0 Jul 31 18:54 /dev/fd0

# cat /etc/fstab | grep floppy
/dev/fd0 /media/floppy auto noauto,rw,sync,user,exec 0 0

I do
# mount /dev/fd0 /media/floppy

and get permanent hang. With ps aux during the hang I get

root 5241 0.0 0.0 1588 520 pts/1 D+ 16:46 0:00 mount /dev/fd0

Does the D+ (uninterruptable sleep) mean the process is dead?

In syslog and kern.log I get:

kernel: end_request: I/O error, dev fd0, sector 0
kernel: Buffer I/O error on device fd0, logical block 0

--

Haines Brown
KB1GRM
From: Grant on 4 Sep 2005 18:50
G'day Haines,
On Sun, 04 Sep 2005 21:05:13 GMT, Haines Brown <brownh(a)teufel.hartford-hwp.com> wrote:

>On a new machine (debian sarge 2.6.8-2-686), I'm having trouble using
>device interfaces. I had a lot of "FIFO stuck" messages, but since
>rebooting, these have disappeared. I can boot from a grub floppy disk
>OK.
>
>In kern.log, during boot, I have:
>
> kernel: inserting floppy driver for 2.6.8-2-686
> kernel: Floppy drive(s): fd0 is 1.44M
> kernel: FDC 0 is a post-1991 82077
> kernel: parport: PnPBIOS parport detected.
> kernel: parport0: PC-style at 0x378 (0x778), irq 7, dma 3
> [PCSPP,TRISTATE,COMPAT,ECP,DMA]

Have you compiled in (not-a-module) floppy support?
>
>Once booted:
>
> $ ls -l /media | grep floppy
> drwxr-xr-x 2 brownh brownh 48 Dec 6 2004 floppy
>
> $ ls -l /dev/fd0
> brw-rw---- 1 root floppy 2, 0 Jul 31 18:54 /dev/fd0
>
> # cat /etc/fstab | grep floppy
> /dev/fd0 /media/floppy auto noauto,rw,sync,user,exec 0 0
>
>I do
> # mount /dev/fd0 /media/floppy
>
>and get permanent hang. With ps aux during the hang I get
>
> root 5241 0.0 0.0 1588 520 pts/1 D+ 16:46 0:00 mount /dev/fd0
>
>Does the D+ (uninterruptable sleep) mean the process is dead?

Stuck, not dead, not zombie :(
>
>In syslog and kern.log I get:
>
> kernel: end_request: I/O error, dev fd0, sector 0
> kernel: Buffer I/O error on device fd0, logical block 0
>
If you not using parallel try turn it off in BIOS, also visit other
BIOS things like PnP OS = off, perhaps even reset CMOS and start
over. Sometimes this clears bad 'state' in BIOS memory. That you
boot from floppy then lose it suggests something in your kernel
build, not hardware. That's a very old kernel, current stable is
2.6.12.6, for 2.6.13 I'd wait for the .1 fixup.

Cheers,
Grant.

From: chuck on 4 Sep 2005 21:22

> # cat /etc/fstab | grep floppy
> /dev/fd0 /media/floppy auto noauto,rw,sync,user,exec 0 0
>
> I do
> # mount /dev/fd0 /media/floppy

Where is the file system type? Shouldn't there be a minix or fat there?
From: Haines Brown on 4 Sep 2005 22:34
Grant <g_r_a_n_t_(a)dodo.com.au> writes:

> G'day Haines,
> On Sun, 04 Sep 2005 21:05:13 GMT, Haines Brown
> <brownh(a)teufel.hartford-hwp.com> wrote:
>
>>On a new machine (debian sarge 2.6.8-2-686), I'm having trouble
>>using device interfaces. I had a lot of "FIFO stuck" messages, but
>>since rebooting, these have disappeared. I can boot from a grub
>>floppy disk OK.

No longer so. The BIOS does not see the floppy as bootable and goes
right to the bootlader on my hard disk.

> Have you compiled in (not-a-module) floppy support?

Stock kernel 2.6.8-2-686

The lsmod reports that floppy driver is loaded.

> If you not using parallel try turn it off in BIOS, also visit other
> BIOS things like PnP OS = off, perhaps even reset CMOS and start
> over. Sometimes this clears bad 'state' in BIOS memory. That you
> boot from floppy then lose it suggests something in your kernel
> build, not hardware. That's a very old kernel, current stable is
> 2.6.12.6, for 2.6.13 I'd wait for the .1 fixup.

I'm unfamiliar with newer/Award BIOS setup, and fear I may have
misconfigured. I left things basically at default. Besides disabling
the parallel port (with no positive effect), Here are some of the
settings I have:

Toshiba DVD primary IDE master
Teac CD-RW secondary IDE master
[I've always used SCSI hard disks, and am not comfortable with IDE
setup]
PnP O/S = off
IDE OnChip IDE channel 0 enabled
IDE OnChip IDE channel 1 enabled
IDE DMA transfer access
IDE prefetch mode: enabled
Parallel port: disabled
Jumperfree Config: overclock profile: auto

ACPI Suspend type S1&S3
ACPI: APIC Support: enabled
APM: Powr only PCI devices: disabled

In my boot log and dmesg, I don't have nothing obviously worrisome.

Starting hotplug subsystems
isapnp
floppy: loaded successfully

inserting floppy driver for 2.6.8-2-686
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077

but in boot log is:

Starting ClamAV daemon: clamd
Starting ClamAV virus database updater: ERROR: Can't open
/var/log/clamav/freshclam.log in append mode (check permissions!).
ERROR: Problem with internal logger.

I don't see the relevance, but who knows?

But in kern.log is something that sounds ominous:

kernel: Loaded 27390 symbols from /boot/System.map-2.6.8-2-686.
kernel: Symbols match kernel version 2.6.8.
kernel: No module symbols loaded - kernel modules not enabled.

On one hand, my floppy driver does seem to be loaded:

$ lsmod | grep floppy
floppy 61200 0

When root does: # mount /media/floppy, it is a hang, and in kern.log
and syslog I get:

kernel: end_request: I/O error, dev fd0, sector 0
kernel: Buffer I/O error on device fd0, logical block 0

--

Haines Brown
KB1GRM
From: Haines Brown on 4 Sep 2005 22:38
chuck <chucko(a)nil.car> writes:

>> # cat /etc/fstab | grep floppy
>> /dev/fd0 /media/floppy auto noauto,rw,sync,user,exec 0 0
>>
>> I do
>> # mount /dev/fd0 /media/floppy
>
> Where is the file system type? Shouldn't there be a minix or fat there?

Sorry for the typo. The problem is the same if I do the command as #
mount /media/floppy as well as spelled out with the -t option.

--

Haines Brown
KB1GRM
 |  Next  |  Last
Pages: 1 2
Prev: Linux Chipset Compatibility List?
Next: Samsung TRUTION TWC-3500 webcam on linux