On Thu, Jun 23, 2005 at 10:43:05PM +0300, Petri T. Koistinen wrote:
> Hi!
>
> On Thu, 23 Jun 2005, Sjoerd Simons wrote:
>
> > > $ sudo killall hald
> > > I close drives again and they keep being closed.
> > >
> > > $ sudo /usr/sbin/hald
> > > And drives open their disk bays instantly.
> > >
> > > So I am pretty sure that hald has atleast something to do with this.
> >
> > Ok, just making sure it's indeed hal that triggers this, because quite odd..
> > The floppy ticking problem also goes away when your restart hal like that ?
>
> Floppy ticking stop when I kill hald and continue when I start hald.
>
> > The way to use it is to turn off hal, and run it with your cdrom device
> > names
> > as arguments. For example ./test /dev/hdc /dev/hdd
>
> I killed hald, closed drive bays, compiled and run that program. Both
> drives will open their disk bay, first /dev/hdc and then /dev/hdd and
> floppy drive starts ticking. All drives are empty.
That's odd.. Did you specify /de/fd0 to the program too?. If that isn't the
case it's not explainable from userspace....
> Some info about drives:
> $ dmesg | egrep 'hd(c|d)'
> ide1: BM-DMA at 0xb408-0xb40f, BIOS settings: hdc:DMA, hdd:DMA
> hdc: Hewlett-Packard CD-Writer Plus 8100, ATAPI CD/DVD-ROM drive
> hdd: JLMS XJ-HD165H, ATAPI CD/DVD-ROM drive
> hdc: ATAPI 24X CD-ROM CD-R/RW drive, 1024kB Cache, DMA
> hdd: ATAPI 48X DVD-ROM drive, 512kB Cache, UDMA(33)
Looks normal. Could you try debian's 2.6.11 just to be sure it's not your
kernel version?
Sjoerd
--
The only possible interpretation of any research whatever in the `social
sciences' is: some do, some don't.
-- Ernest Rutherford
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
