[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious
From: |
Thomas Schmitt |
Subject: |
Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious |
Date: |
Sat, 26 Jan 2019 21:51:58 +0100 |
Hi,
> So to answer your question, it's the ioctl itself failing.
This explains why we see a message.
It would be better to show errno or strerror() instead of req.retsts.
The riddle is now why the transport ioctl fails. This can hardly be due
to the state of drive or medium. Maybe the bus and its cabling ?
Any traces to see in the system logs ?
Have a nice day :)
Thomas
- [Libcdio-devel] OpenBSD vs libcdio vs Audacious, Edd Barrett, 2019/01/26
- Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious, Thomas Schmitt, 2019/01/26
- Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious, Edd Barrett, 2019/01/26
- Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious,
Thomas Schmitt <=
- Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious, Edd Barrett, 2019/01/27
- Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious, Edd Barrett, 2019/01/27
- Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious, Thomas Schmitt, 2019/01/27
- Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious, Edd Barrett, 2019/01/27
- Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious, Thomas Schmitt, 2019/01/27
Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious, Thomas Schmitt, 2019/01/26
Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious, Rocky Bernstein, 2019/01/26