Re: my cdrom goes wrong with a debian 1.3.1
Well, finaly, i found the solution:
---
Some said to me that they had the same problem, and that it was due to
some cheap and low quality cdrom units. And it seem it's true: I
borrowed another cdrom (hitachi x16), and there was no problem more.
(Note that on the other hand my Funai had no problem under win95,
but i think that 'windoze' isn't as exigent as linux with such
devices).
Well, at least, i bought another cdrom, and i feel better, so
people willing to buy a cd and who want to use it under linux,
don't take the cheapest ones! (or at your own risk)
matimbert a écrit:
>
> precisions on the cdrom problem:
>
>
> George Bonser a écrit:
> > I am thinking that you might need the old serialize trick.
> > I seem to have forgotten the exact syntax but I THINK it is like this:
> > append = "hdb=cdrom"
> > append = "hdb=serialize"
> >
> > On Fri, 23 Jan 1998, matimbert wrote:
> > > i installed recently a debian 1.3.1.
> > > My cdrom (a "funai e285xa") is correctly detected during boot up. But,
> > > near half the times, when i
> > > "mount -t iso9660 /dev/hdb /cdrom", i get:
> > > "hdb: status error: status=0x08.
> > > Drive not ready for command.
> > > ATAPI reset complete".
> > > and then my hard disk starts to work for a while, then pause, in loop, as
> > > i continuously have some messages telling me
> > > that my hda (not hdb) is not ready. The system is not crashed but i can't
> > > get the control back, and i must reset the pc > > between two periods of
> > > hard disk work. I had an old Slackware before this debian and i never had
> > > any problem (with my > > cdrom, i mean...). Under win95 there's no
> > > problem.
> > > My config: pentium 233 mmx. chipset tx on an asus txp4 motherboard.
> > >.hda=ide0 master=quantum fireball 3.2 go udma (whith 3 partitions:
> > > hda1=linux/hda2=linux swap/hda3=win95)
> > >.hdb=ide0 slave=cdrom (8x funai e285xa)
> > >.hdc=ide1 master=old 80Mb conner hard disk
> > >.hdd=nothing
> > >.no SCSI device in my config, just a parallel port Iomega Zip Drive.
> > > you can mail me: [EMAIL PROTECTED]
>
> So i tried including append="ide0=serialize" but it did not solve the
> problem.
> I see that i forgot to give my kernel's version: 2.0.29
> For the error messages, i noted them very precisely if someone can
> understand what it means:
> hdb: status error: status= 0x08
> hdb: drive not ready for command
> hdb: ATAPI reset complete
> hdb: status error: status=0x08
> hdb: drive not ready for command
> hdb: ATAPI reset timed-out status=0x080
> ide0: reset timed-out, status=0xd0
> hdb: status timeout: status=0x80
> end_request: I/O error, dev 03:40, sector 0
> hdb: drive not ready for command
> hda: status timeout: status=0xd0 {busy]
> hda: drive not ready for command
> ide0: reset timed-out, status=0xd0
> ... and so on ... from there it loops with messages concerning hda...
>
> here's the whole problem. thanks for anybody giving me any
> explication...Is my cdrom broken? Is it possible that it is incompatible
> whith linux?
> [EMAIL PROTECTED]
>
> --
> TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
> [EMAIL PROTECTED] .
> Trouble? e-mail to [EMAIL PROTECTED] .
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Re: my cdrom goes wrong with a debian 1.3.1
precisions on the cdrom problem:
George Bonser a écrit:
> I am thinking that you might need the old serialize trick.
> I seem to have forgotten the exact syntax but I THINK it is like this:
> append = "hdb=cdrom"
> append = "hdb=serialize"
>
> On Fri, 23 Jan 1998, matimbert wrote:
> > i installed recently a debian 1.3.1.
> > My cdrom (a "funai e285xa") is correctly detected during boot up. But, near
> > half the times, when i
> > "mount -t iso9660 /dev/hdb /cdrom", i get:
> > "hdb: status error: status=0x08.
> > Drive not ready for command.
> > ATAPI reset complete".
> > and then my hard disk starts to work for a while, then pause, in loop, as i
> > continuously have some messages telling me
> > that my hda (not hdb) is not ready. The system is not crashed but i can't
> > get the control back, and i must reset the pc > > between two periods of
> > hard disk work. I had an old Slackware before this debian and i never had
> > any problem (with my > > cdrom, i mean...). Under win95 there's no problem.
> > My config: pentium 233 mmx. chipset tx on an asus txp4 motherboard.
> >.hda=ide0 master=quantum fireball 3.2 go udma (whith 3 partitions:
> > hda1=linux/hda2=linux swap/hda3=win95)
> >.hdb=ide0 slave=cdrom (8x funai e285xa)
> >.hdc=ide1 master=old 80Mb conner hard disk
> >.hdd=nothing
> >.no SCSI device in my config, just a parallel port Iomega Zip Drive.
> > you can mail me: [EMAIL PROTECTED]
So i tried including append="ide0=serialize" but it did not solve the
problem.
I see that i forgot to give my kernel's version: 2.0.29
For the error messages, i noted them very precisely if someone can
understand what it means:
hdb: status error: status= 0x08
hdb: drive not ready for command
hdb: ATAPI reset complete
hdb: status error: status=0x08
hdb: drive not ready for command
hdb: ATAPI reset timed-out status=0x080
ide0: reset timed-out, status=0xd0
hdb: status timeout: status=0x80
end_request: I/O error, dev 03:40, sector 0
hdb: drive not ready for command
hda: status timeout: status=0xd0 {busy]
hda: drive not ready for command
ide0: reset timed-out, status=0xd0
... and so on ... from there it loops with messages concerning hda...
here's the whole problem. thanks for anybody giving me any
explication...Is my cdrom broken? Is it possible that it is incompatible
whith linux?
[EMAIL PROTECTED]
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
my cdrom goes wrong with a debian 1.3.1
Hello all. i installed recently a debian 1.3.1. My cdrom (a "funai ex285a") is correctly detected during boot up. But, near half the times, when i "mount -t iso9660 /dev/hdb /cdrom", i get: "hdb: status error: status=0x08. Drive not ready for command. ATAPI reset complete". and then my hard disk starts to work for a while, then pause, in loop, as i continuously have some messages telling me that my hda (not hdb) is not ready. The system is not crashed but i can't get the control back, and i must reset the pc between two periods of hard disk work. I ask myself why the problem with hdb causes another with hda? i'm not a guru of linux but i don't think that this is due to a bad configuration. I had an old Slackware before this debian and i never had any problem (with my cdrom, i mean...). Under win95 there's no problem. My config: pentium 233 mmx. chipset tx on an asus txp4 motherboard. .hda=ide0 master=quantum fireball 3.2 go udma (whith 3 partitions: hda1=linux/hda2=linux swap/hda3=win95) .hdb=ide0 slave=cdrom (4x funai ex285a) .hdc=ide1 master=old 80Mb conner hard disk .hdd=nothing .no SCSI device in m config, just a parallel port Iomega Zip Drive. Please, please, solve my problem because i don't want to go back with my old slackware to fix that...thanks to any helper you can mail me: [EMAIL PROTECTED] PS: sorry for the bad english (but i'm french). -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
