Bug#307834: FWD: Re: Bug#307834: Installation: Micron Transport floppy=nofifo problem

2005-05-26 Thread Joey Hess
- Forwarded message from Eric Shubes [EMAIL PROTECTED] -

From: Eric Shubes [EMAIL PROTECTED]
Date: Thu, 05 May 2005 15:14:15 -0700
To: Joey Hess [EMAIL PROTECTED]
Subject: Re: Bug#307834: Installation: Micron Transport floppy=nofifo problem
Organization: Eric Shubert  Associates
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624 
Netscape/7.1 (ax)

Joey Hess wrote:

Eric Shubes wrote:

The error wasn't absolutely consistent. The long rw: value varied. 
Usually 24, but sometimes 13 or 20. The rs= value changed too, 2 and 15 
respectively. 
The install media was fine. I checked, double checked, cleaned the drive, 
and even created media on the same computer which was failing. On 
occasion (3 times out of 20 or so)

I also tried various other parameters: floppy=0,daring; =broken_dcl; 
=slow, and none helped.

I don't know why floppy=nofifo fixed the problem with Woody (Woody had 
the same symptoms without it). It appears to me as though floppy=nofifo 
simply doesn't work. At least it doesn't do what it did with Woody.

I've since done a dist-upgrade instead, so I'm not in need of this to 
work, but it would be nice to have it fixed for the next person who tries 
it. I'll be happy to do whatever testing that may be needed.


The issue is that kernel boot time parameters are not seen by modules
when they're loaded. The floppy driver is a module in sarge. You should
be able to work around the problem by booting with BOOT_DEBUG=3. This
will give you several shell prompts after the floppy boots. At the first
one, before hardware detection, you can try to modprobe floppy 
floppy=nofifo.

If that works for you, then we obviously need a better fix to let these
parameters be specified.





 
Bingo - works like a charm.
Where do we go from here?

I followed through the install process a bit, and there was an error 
while running 'modprobe -v i82365' for my network adapter. I guess I 
should see if that's reported already or not, and if not file a report 
on that too. Yes?

-- 
-Eric 'shubes'
There is no such thing as the People;
 it is a collectivist myth.
 There are only individual citizens
 with individual wills
 and individual purposes.
-William E. Simon (1927-2000),
Secretary of the Treasury (1974-1977)
 A Time For Truth (1978), pg. 237




- End forwarded message -
-- 
see shy jo


signature.asc
Description: Digital signature


Bug#307834: Installation: Micron Transport floppy=nofifo problem

2005-05-05 Thread Eric \Shubes\






Package: installation-reports

Debian-installer-version: R3 5/4/05 people.debian.org/~joeyh/d-i/images/daily/floppy/ 
uname -a: n/a
Date: 5/4/05 all day
Method: Floppy/cdrom/network

Machine: Micron Millenia Transport w/ docking station
Processor: Pentium 133
Memory: 32M
Root Device: /dev/fd0
Root Size/partition table: n/a
Output of lspci and lspci -n: n/a

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot worked:[O]
Configure network HW:   [O]
Config network: [E]
Detect CD:  [O]
Load installer modules: [E]
Detect hard drives: [O]
Partition hard drives:  [ ]
Create file systems:[ ]
Mount partitions:   [ ]
Install base system:[ ]
Install boot loader:[ ]
Reboot: [ ]

Comments/Problems:

I originally installed Woody from floppy/cdrom, and it worked ok.
I had to use the floppy=nofifo parameter for the floppy drive to work properly.


When trying Sarge, I used floppy=nofifo, but got results consistent with not using it. It booted fine from the boot disk, but when loading the root disk, I'd get:
floppy0: long rw: 24 instead of 12
rs=18 s=1
rh=1 h=0
rt=0 t=0
heads=2 eoc=0
spt=18 st=0 ss=1
in_sector_offset=0
FAT: bogus logical sector size 0
VFS: Can't find a valid FAT system on dev 02:00
Cannot find root floppy: /dev/floppy/0: cannot mount

The error wasn't absolutely consistent. The long rw: value varied. Usually 24, but sometimes 13 or 20. The rs= value changed too, 2 and 15 respectively. 

The install media was fine. I checked, double checked, cleaned the drive, and even created media on the same computer which was failing. On occasion (3 times out of 20 or so)

I also tried various other parameters: floppy=0,daring; =broken_dcl; =slow, and none helped.

I don't know why floppy=nofifo fixed the problem with Woody (Woody had the same symptoms without it). It appears to me as though floppy=nofifo simply doesn't work. At least it doesn't do what it did with Woody.

I've since done a dist-upgrade instead, so I'm not in need of this to work, but it would be nice to have it fixed for the next person who tries it. I'll be happy to do whatever testing that may be needed.

-- 
-Eric 'shubes'






 


Bug#307834: Installation: Micron Transport floppy=nofifo problem

2005-05-05 Thread Joey Hess
Eric Shubes wrote:
 The error wasn't absolutely consistent. The long rw: value varied. Usually 
 24, but sometimes 13 or 20. The rs= value changed too, 2 and 15 
 respectively. 
 The install media was fine. I checked, double checked, cleaned the drive, 
 and even created media on the same computer which was failing. On occasion 
 (3 times out of 20 or so)
 
 I also tried various other parameters: floppy=0,daring; =broken_dcl; 
 =slow, and none helped.
 
 I don't know why floppy=nofifo fixed the problem with Woody (Woody had the 
 same symptoms without it). It appears to me as though floppy=nofifo simply 
 doesn't work. At least it doesn't do what it did with Woody.
 
 I've since done a dist-upgrade instead, so I'm not in need of this to 
 work, but it would be nice to have it fixed for the next person who tries 
 it. I'll be happy to do whatever testing that may be needed.

The issue is that kernel boot time parameters are not seen by modules
when they're loaded. The floppy driver is a module in sarge. You should
be able to work around the problem by booting with BOOT_DEBUG=3. This
will give you several shell prompts after the floppy boots. At the first
one, before hardware detection, you can try to modprobe floppy 
floppy=nofifo.

If that works for you, then we obviously need a better fix to let these
parameters be specified.

-- 
see shy jo


signature.asc
Description: Digital signature