Re: cdrom problem

[Tom Droege <tdroege2@earthlink.net>]

Chris and all,

Chris, thanks for the nice discussion.  

Did I mentin that this happens over several dfferent machines and different CD 
writers and possibly with xcdroast and K3b.  I have not sorted it out 
completely yet.  

Yes I understand my obligations to the developers.  It is hard work to track 
down a bug.  I will probably stick to fixing things that are electronic where 
I know what I am doing.  My main "public service" at the moment is working on 
the DECam project where I have something to contribute.  I hope you software 
experts will be alerted to this problem and can then pin it down.

Tom Droege

On Monday 04 October 2004 11:27 pm, Chris Albertson wrote:
> --- Tom Droege <tdroege2@earthlink.net> wrote:
> > I notice that from time to time my cdrom drives get in a mode where
> > they just
> > read 12 files.  A ls /mnt/cdrom  gives 12 file names when there are
> > many more
> > on the cd.  A reboot of the system cures this.
> >
> > Is this a known problem?  Mandrake Linux 10.0
> >
> > OK, now that I am on to it, it is not much of a problem.  However, it
> > greatly
> > added to my disk confusion over the last several days.  Possibly
> > there is a
> > way to fix it wihout a reboot.
>
> This is really odd, but then bugs are always that way.  I can't think
> of any user error tht could explain it, even so it's hard to
> believe there is a bug in something so well tested.  ut if a re-boot
> fixes it then it's a bug some place....
>
> If you say _only_ a reboot fixes the problem, and a power cycle is not
> required then it is likey some odd problem with a driver.  (If a power
> cycle is required then I supect firmware glitch.)
> The trouble is that the "driver" is really a stack of drivers and you
> don't know which it really is.
> Maybe you don't care?  You can unload and re-load the
> drivers.  Most of the time that is really why a re-boot
> fixees it, because it force a reload of some driver.
> As root try the command "lsmod". Don't worry it's harmless.
> It will just list out all the loadable drivers you currently have.
>
> There are related commands, "rmmod" to remove a driver and "inmod
> to "insert" or load a driver.  They all have man pages.
> Experiment on a system that does not have importent data on it
> You can put the required rmmon/insmod commands in a script and
> it will take like 1/10th second to run.  Much fasterthen a re-boot.
>
> If you do get the script down to minimum size and can then prove
> where the problem is please do tell the guy who maintains that
> driver that you have a reproducable problem.
>
> > Tom Droege
>
> =====
> Chris Albertson
>   Home:   310-376-1029  chrisalbertson90278@yahoo.com
>   Cell:   310-990-7550
>   Office: 310-336-5189  Christopher.J.Albertson@aero.org
>   KG6OMK
>
>
>
> _______________________________
> Do you Yahoo!?
> Declare Yourself - Register online to vote today!
> http://vote.yahoo.com