I made the timeout = 200000  and it still doesnt work without a cdrom in  the
drive. Its nothing that cant be worked around though. Maybe this is fixed in
1.4 ?

Cheers


On 12-Apr-99 dbsaint@bellsouth.net wrote:
> I just noticed after trying to mount the cdrom .. that the system did not
> 'configure' the device for use on last boot. I ran through dmesg and there
> was
> no cd0 at all again..This is after I applied the patch that Manuel Bouyer
> sent
> me making the timeout a little longer. Im going to try it again maybe with
> double the new 'timeout' see what that gives me. Has anyone else had this
> happen ? It only happens when there is no media in the drive.
> 
> 
> On 07-Apr-99 Manuel Bouyer wrote:
>> On Apr 7, dbsaint@bellsouth.net wrote
>>> Ive been getting some strange messages upon boot. I dont think UDMA is w
>>> orking every boot . actually sometimes my cdrom is not even detected. As
>>> the
>>> first example depicts this. Notice no cd0 !!
>> 
>> Did you notice if this is related to the media present in the drive, if any
>> ?
>> Could you try to bump the delay() in sys/dev/scsipi/atapi_wdc.c:
>>         /* Some ATAPI devices need a bit more time after software reset. */
>>       delay(5000);
>> 
>> 5000 is 5 milliseconds. Maybe 100 or 200ms would be enouth ...
>> 
>> --
>> Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
>> --
----------------------------------
Tony Hernandez ::: Intellon Corporation
            MCP    A+
       Workstation Administrator

----------------------------------