Hello all!
I'm afraid that I have no idea where the problem lies. It is probably relevant that I am a complete ignoramus where multimedia is concerned. I need to run vlc simultaneously with wireshark in order to analyse the traces for an assignment in an online course I am doing. I can run Wireshark on Trinity on Squeeze, but not on Lenny. (I believe there is a bug.) I can run vlc in Lenny, but not in Trinity/Squeeze. And yes, they are different versions.
See below for extract from Squeeze syslog.
All suggestions welcomed!! Even RTFM, so long as the admonition includes which %^&*!!$ Manual to read!
If there is no way it could be Trinity, I'll take my request elsewhere, but I didn't like to cross-post. And I find life more comfortable if I don't force insecure KDE4 users to make snide remarks about KDE3 lovers!
Thanks, all. Lisi
Extract from syslog (sr0 is the correct identification of my optical drive):
<quote> Dec 20 01:18:56 Trinity kernel: [123703.444680] sr 1:0:0:0: [sr0] Unhandled sense code Dec 20 01:18:56 Trinity kernel: [123703.444686] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Dec 20 01:18:56 Trinity kernel: [123703.444690] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current] Dec 20 01:18:56 Trinity kernel: [123703.444694] Info fld=0x0 Dec 20 01:18:56 Trinity kernel: [123703.444695] sr 1:0:0:0: [sr0] Add. Sense: Unrecovered read error Dec 20 01:18:56 Trinity kernel: [123703.444701] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 04 00 00 00 02 00 Dec 20 01:18:56 Trinity kernel: [123703.444709] end_request: I/O error, dev sr0, sector 4096 Dec 20 01:18:56 Trinity kernel: [123703.524892] sr 1:0:0:0: [sr0] Unhandled sense code Dec 20 01:18:56 Trinity kernel: [123703.524899] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Dec 20 01:18:56 Trinity kernel: [123703.524903] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current] Dec 20 01:18:56 Trinity kernel: [123703.524908] Info fld=0x0 Dec 20 01:18:56 Trinity kernel: [123703.524909] sr 1:0:0:0: [sr0] Add. Sense: Unrecovered read error Dec 20 01:18:56 Trinity kernel: [123703.524915] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00 Dec 20 01:18:56 Trinity kernel: [123703.524924] end_request: I/O error, dev sr0, sector 0 Dec 20 01:18:56 Trinity kernel: [123703.548711] sr 1:0:0:0: [sr0] Unhandled sense code Dec 20 01:18:56 Trinity kernel: [123703.548717] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Dec 20 01:18:56 Trinity kernel: [123703.548722] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current] Dec 20 01:18:56 Trinity kernel: [123703.548727] Info fld=0x0 Dec 20 01:18:56 Trinity kernel: [123703.548728] sr 1:0:0:0: [sr0] Add. Sense: Unrecovered read error Dec 20 01:18:56 Trinity kernel: [123703.548735] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00 Dec 20 01:18:56 Trinity kernel: [123703.548743] end_request: I/O error, dev sr0, sector 0 </quote>
Hello all!
I'm afraid that I have no idea where the problem lies. It is probably relevant that I am a complete ignoramus where multimedia is concerned. I need to run vlc simultaneously with wireshark in order to analyse the traces for an assignment in an online course I am doing. I can run Wireshark on Trinity on Squeeze, but not on Lenny. (I believe there is a bug.) I can run vlc in Lenny, but not in Trinity/Squeeze. And yes, they are different versions.
See below for extract from Squeeze syslog.
All suggestions welcomed!! Even RTFM, so long as the admonition includes which %^&*!!$ Manual to read!
If there is no way it could be Trinity, I'll take my request elsewhere, but I didn't like to cross-post. And I find life more comfortable if I don't force insecure KDE4 users to make snide remarks about KDE3 lovers!
Thanks, all. Lisi
Extract from syslog (sr0 is the correct identification of my optical drive):
<quote> Dec 20 01:18:56 Trinity kernel: [123703.444680] sr 1:0:0:0: [sr0] Unhandled sense code Dec 20 01:18:56 Trinity kernel: [123703.444686] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Dec 20 01:18:56 Trinity kernel: [123703.444690] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current] Dec 20 01:18:56 Trinity kernel: [123703.444694] Info fld=0x0 Dec 20 01:18:56 Trinity kernel: [123703.444695] sr 1:0:0:0: [sr0] Add. Sense: Unrecovered read error Dec 20 01:18:56 Trinity kernel: [123703.444701] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 04 00 00 00 02 00 Dec 20 01:18:56 Trinity kernel: [123703.444709] end_request: I/O error, dev sr0, sector 4096 Dec 20 01:18:56 Trinity kernel: [123703.524892] sr 1:0:0:0: [sr0] Unhandled sense code Dec 20 01:18:56 Trinity kernel: [123703.524899] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Dec 20 01:18:56 Trinity kernel: [123703.524903] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current] Dec 20 01:18:56 Trinity kernel: [123703.524908] Info fld=0x0 Dec 20 01:18:56 Trinity kernel: [123703.524909] sr 1:0:0:0: [sr0] Add. Sense: Unrecovered read error Dec 20 01:18:56 Trinity kernel: [123703.524915] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00 Dec 20 01:18:56 Trinity kernel: [123703.524924] end_request: I/O error, dev sr0, sector 0 Dec 20 01:18:56 Trinity kernel: [123703.548711] sr 1:0:0:0: [sr0] Unhandled sense code Dec 20 01:18:56 Trinity kernel: [123703.548717] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Dec 20 01:18:56 Trinity kernel: [123703.548722] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current] Dec 20 01:18:56 Trinity kernel: [123703.548727] Info fld=0x0 Dec 20 01:18:56 Trinity kernel: [123703.548728] sr 1:0:0:0: [sr0] Add. Sense: Unrecovered read error Dec 20 01:18:56 Trinity kernel: [123703.548735] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00 Dec 20 01:18:56 Trinity kernel: [123703.548743] end_request: I/O error, dev sr0, sector 0 </quote>
The snippet you posted indicates a hardware failure in reading the CD/DVD/BluRay disk in the optical drive. Is there a crash or backtrace that makes you suspect TDE is at fault?
Tim
On Tuesday 20 December 2011 02:24:54 Timothy Pearson wrote:
The snippet you posted indicates a hardware failure in reading the CD/DVD/BluRay disk in the optical drive. Is there a crash or backtrace that makes you suspect TDE is at fault?
I have no idea at all what is at fault. Hence the sandwhich above. Trinity is the desktop I was using at the time of teh failure. The host OS can read the optical drive without a problem, so there is not in fact a hardware failure
What you say about what the snippet leads me to feel that it is VB which is "at fault". It is communicating with the optical drive, but not using it. (I.e. the light goes on but nothing happens.
Thanks, Tim. I'll try the VB mailing list.
Lisi
Probably not Lisi's solution but users of debian-multimedia who have problems with vlc should be aware of this:
On Monday 19 December 2011 5:08:36 pm Lisi wrote:
Hello all!
I'm afraid that I have no idea where the problem lies. It is probably relevant that I am a complete ignoramus where multimedia is concerned. I need to run vlc simultaneously with wireshark in order to analyse the traces for an assignment in an online course I am doing. I can run Wireshark on Trinity on Squeeze, but not on Lenny. (I believe there is a bug.) I can run vlc in Lenny, but not in Trinity/Squeeze. And yes, they are different versions.
See below for extract from Squeeze syslog.
All suggestions welcomed!! Even RTFM, so long as the admonition includes which %^&*!!$ Manual to read!
If there is no way it could be Trinity, I'll take my request elsewhere, but I didn't like to cross-post. And I find life more comfortable if I don't force insecure KDE4 users to make snide remarks about KDE3 lovers!
Thanks, all. Lisi
Extract from syslog (sr0 is the correct identification of my optical drive):
<quote> Dec 20 01:18:56 Trinity kernel: [123703.444680] sr 1:0:0:0: [sr0] Unhandled sense code Dec 20 01:18:56 Trinity kernel: [123703.444686] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Dec 20 01:18:56 Trinity kernel: [123703.444690] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current] Dec 20 01:18:56 Trinity kernel: [123703.444694] Info fld=0x0 Dec 20 01:18:56 Trinity kernel: [123703.444695] sr 1:0:0:0: [sr0] Add. Sense: Unrecovered read error Dec 20 01:18:56 Trinity kernel: [123703.444701] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 04 00 00 00 02 00 Dec 20 01:18:56 Trinity kernel: [123703.444709] end_request: I/O error, dev sr0, sector 4096 Dec 20 01:18:56 Trinity kernel: [123703.524892] sr 1:0:0:0: [sr0] Unhandled sense code Dec 20 01:18:56 Trinity kernel: [123703.524899] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Dec 20 01:18:56 Trinity kernel: [123703.524903] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current] Dec 20 01:18:56 Trinity kernel: [123703.524908] Info fld=0x0 Dec 20 01:18:56 Trinity kernel: [123703.524909] sr 1:0:0:0: [sr0] Add. Sense: Unrecovered read error Dec 20 01:18:56 Trinity kernel: [123703.524915] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00 Dec 20 01:18:56 Trinity kernel: [123703.524924] end_request: I/O error, dev sr0, sector 0 Dec 20 01:18:56 Trinity kernel: [123703.548711] sr 1:0:0:0: [sr0] Unhandled sense code Dec 20 01:18:56 Trinity kernel: [123703.548717] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Dec 20 01:18:56 Trinity kernel: [123703.548722] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current] Dec 20 01:18:56 Trinity kernel: [123703.548727] Info fld=0x0 Dec 20 01:18:56 Trinity kernel: [123703.548728] sr 1:0:0:0: [sr0] Add. Sense: Unrecovered read error Dec 20 01:18:56 Trinity kernel: [123703.548735] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00 Dec 20 01:18:56 Trinity kernel: [123703.548743] end_request: I/O error, dev sr0, sector 0 </quote>
Not sure about the error message, seems like hardware but just in case.
I use VLC on Squeeze,
I use: deb http://www.debian-multimedia.org squeeze main non-free
I also use libdvdcss2 from debian-multimedia.
I still have some isues with some KDE apps not finding /dev/dvd, which is linked to /dev/sr0, but VLC finds everything ok.
-
David Hare -
Greg Madden -
Lisi -
Timothy Pearson