Hello. Problem is simple - can't read DVD discs (actually i can mount
them, i can list files, but i`t wont work further). It`s new (2nd one
already, thought, that 1st had a deffect or what). It's a Samsung SATA
rom.

This is not a codec problem.
Info about the machine:
:~$ uname -rvoim
2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686 unknown GNU/
Linux
(just updated, using Ubuntu 8.04, fresh one)

When my cdrom mounts, it outputs following stuff on dmesg:
[ 149.243098] UDF-fs: Partition marked readonly; forcing readonly
mount
[ 149.270674] UDF-fs INFO UDF 0.9.8.1 (2004/29/09) Mounting volume
'PI3LP3W1', timestamp 2007/10/05 07:14 (10b4)
[ 150.921083] end_request: I/O error, dev sr0, sector 460164
[ 150.921089] Buffer I/O error on device sr0, logical block 115041
[ 150.921096] Buffer I/O error on device sr0, logical block 115042
[ 150.921099] Buffer I/O error on device sr0, logical block 115043
[ 150.921102] Buffer I/O error on device sr0, logical block 115044
[ 150.921105] Buffer I/O error on device sr0, logical block 115045
[ 150.921108] Buffer I/O error on device sr0, logical block 115046
[ 150.921111] Buffer I/O error on device sr0, logical block 115047
[ 150.921114] Buffer I/O error on device sr0, logical block 115048
[ 150.921116] Buffer I/O error on device sr0, logical block 115049
[ 150.921120] Buffer I/O error on device sr0, logical block 115050
[ 150.979586] end_request: I/O error, dev sr0, sector 460880
[ 151.009564] end_request: I/O error, dev sr0, sector 460880
[ 164.848340] end_request: I/O error, dev sr0, sector 15841200
[ 164.848345] printk: 41 messages suppressed.
[ 164.848348] Buffer I/O error on device sr0, logical block 3960300
[ 164.848352] Buffer I/O error on device sr0, logical block 3960301
[ 164.871256] end_request: I/O error, dev sr0, sector 15841200
[ 167.319713] end_request: I/O error, dev sr0, sector 15841200
[ 167.319719] printk: 2 messages suppressed.
[ 167.319722] Buffer I/O error on device sr0, logical block 3960300
[ 167.383613] end_request: I/O error, dev sr0, sector 15841200
[ 170.856672] end_request: I/O error, dev sr0, sector 460880

Other stuff about cdrom (it shows 2nd (IDE) cdrom also, which i tested
and it didnt read anything, thou it reads that disc on the other -
windows machine. Don't know why it shows up there, because i de-
attached it already.):

[ 18.380896] ata3.01: configured for UDMA/100
[ 18.546738] scsi 2:0:0:0: Direct-Access ATA SAMSUNG HD403LJ CT10 PQ:
0 ANSI: 5
[ 18.547440] scsi 2:0:1:0: CD-ROM TSSTcorp CDDVDW SH-S203P SB00 PQ: 0
ANSI: 5
[ 18.554528] Driver 'sd' needs updating - please use bus_type methods
[ 18.554569] sd 2:0:0:0: [sda] 781422768 512-byte hardware sectors
(400088 MB)
[ 18.554576] sd 2:0:0:0: [sda] Write Protect is off
[ 18.554578] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 18.554588] sd 2:0:0:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 18.554619] sd 2:0:0:0: [sda] 781422768 512-byte hardware sectors
(400088 MB)
[ 18.554625] sd 2:0:0:0: [sda] Write Protect is off
[ 18.554627] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 18.554637] sd 2:0:0:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 18.554639] sda:<4>Driver 'sr' needs updating - please use bus_type
methods
[ 18.585801] sda1 sda2 < sda5 >
[ 18.604858] sd 2:0:0:0: [sda] Attached SCSI disk
[ 18.607852] sd 2:0:0:0: Attached scsi generic sg0 type 0
[ 18.607874] sr 2:0:1:0: Attached scsi generic sg1 type 5
[ 18.610563] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/
form2 cdda tray
[ 18.610565] Uniform CD-ROM driver Revision: 3.20
[ 18.610593] sr 2:0:1:0: Attached scsi CD-ROM sr0

Forgot to asq questions: How would you translate dmesg log? Is there a
problem with my pc, or the OS?
One of the lines says i should update drivers or something. But, as i
was googling for it, it just said the line is a bug.

On Tue, 01 Jul 2008 06:25:51 -0700, Jencha wrote:

> Hello. Problem is simple - can't read DVD discs (actually i can mount
> them, i can list files, but i`t wont work further). It`s new (2nd one
> already, thought, that 1st had a deffect or what). It's a Samsung SATA
> rom.
>
> This is not a codec problem.
> Info about the machine:
> :~$ uname -rvoim
> 2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686 unknown GNU/
> Linux
> (just updated, using Ubuntu 8.04, fresh one)
>
> When my cdrom mounts, it outputs following stuff on dmesg: [ 149.243098]
> UDF-fs: Partition marked readonly; forcing readonly mount
> [ 149.270674] UDF-fs INFO UDF 0.9.8.1 (2004/29/09) Mounting volume
> 'PI3LP3W1', timestamp 2007/10/05 07:14 (10b4) [ 150.921083] end_request:
> I/O error, dev sr0, sector 460164 [ 150.921089] Buffer I/O error on
> device sr0, logical block 115041 [ 150.921096] Buffer I/O error on
> device sr0, logical block 115042 [ 150.921099] Buffer I/O error on
> device sr0, logical block 115043 [ 150.921102] Buffer I/O error on
> device sr0, logical block 115044 [ 150.921105] Buffer I/O error on
> device sr0, logical block 115045 [ 150.921108] Buffer I/O error on
> device sr0, logical block 115046 [ 150.921111] Buffer I/O error on
> device sr0, logical block 115047 [ 150.921114] Buffer I/O error on
> device sr0, logical block 115048 [ 150.921116] Buffer I/O error on
> device sr0, logical block 115049 [ 150.921120] Buffer I/O error on
> device sr0, logical block 115050 [ 150.979586] end_request: I/O error,
> dev sr0, sector 460880 [ 151.009564] end_request: I/O error, dev sr0,
> sector 460880 [ 164.848340] end_request: I/O error, dev sr0, sector
> 15841200 [ 164.848345] printk: 41 messages suppressed. [ 164.848348]
> Buffer I/O error on device sr0, logical block 3960300 [ 164.848352]
> Buffer I/O error on device sr0, logical block 3960301 [ 164.871256]
> end_request: I/O error, dev sr0, sector 15841200 [ 167.319713]
> end_request: I/O error, dev sr0, sector 15841200 [ 167.319719] printk: 2
> messages suppressed. [ 167.319722] Buffer I/O error on device sr0,
> logical block 3960300 [ 167.383613] end_request: I/O error, dev sr0,
> sector 15841200 [ 170.856672] end_request: I/O error, dev sr0, sector
> 460880
>
> Other stuff about cdrom (it shows 2nd (IDE) cdrom also, which i tested
> and it didnt read anything, thou it reads that disc on the other -
> windows machine. Don't know why it shows up there, because i de-
> attached it already.):
>
> [ 18.380896] ata3.01: configured for UDMA/100 [ 18.546738] scsi 2:0:0:0:
> Direct-Access ATA SAMSUNG HD403LJ CT10 PQ: 0 ANSI: 5
> [ 18.547440] scsi 2:0:1:0: CD-ROM TSSTcorp CDDVDW SH-S203P SB00 PQ: 0
> ANSI: 5
> [ 18.554528] Driver 'sd' needs updating - please use bus_type methods [
> 18.554569] sd 2:0:0:0: [sda] 781422768 512-byte hardware sectors (400088
> MB)
> [ 18.554576] sd 2:0:0:0: [sda] Write Protect is off [ 18.554578] sd
> 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 18.554588] sd 2:0:0:0: [sda]
> Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> [ 18.554619] sd 2:0:0:0: [sda] 781422768 512-byte hardware sectors
> (400088 MB)
> [ 18.554625] sd 2:0:0:0: [sda] Write Protect is off [ 18.554627] sd
> 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 18.554637] sd 2:0:0:0: [sda]
> Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> [ 18.554639] sda:<4>Driver 'sr' needs updating - please use bus_type
> methods
> [ 18.585801] sda1 sda2 < sda5 >
> [ 18.604858] sd 2:0:0:0: [sda] Attached SCSI disk [ 18.607852] sd
> 2:0:0:0: Attached scsi generic sg0 type 0 [ 18.607874] sr 2:0:1:0:
> Attached scsi generic sg1 type 5 [ 18.610563] sr0: scsi3-mmc drive:
> 48x/48x writer dvd-ram cd/rw xa/ form2 cdda tray
> [ 18.610565] Uniform CD-ROM driver Revision: 3.20 [ 18.610593] sr
> 2:0:1:0: Attached scsi CD-ROM sr0

It might be a problem with the SATA port or with the SATA controller. If
you have more than one type of SATA controller on your motherboard try
connecting to a different controller. Core2 motherboards frequently have
two controllers, most SATA connectors are on an Intel chip and then there
are a couple that are on something else (JMicron is common).

On Jul 1, 5:11*pm, General Schvantzkopf <schvantzk...@yahoo.com>
wrote:
> On Tue, 01 Jul 2008 06:25:51 -0700, Jencha wrote:
> > Hello. Problem is simple - can't read DVD discs *(actually i can mount
> > them, i can list files, but i`t wont work further). It`s new (2nd one
> > already, thought, that 1st had a deffect or what). It's a Samsung SATA
> > rom.
>
> > This is not a codec problem.
> > Info about the machine:
> > :~$ uname -rvoim
> > 2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686 unknown GNU/
> > Linux
> > (just updated, using Ubuntu 8.04, fresh one)
>
> > When my cdrom mounts, it outputs following stuff on dmesg: [ 149.243098]
> > UDF-fs: Partition marked readonly; forcing readonly mount
> > [ 149.270674] UDF-fs INFO UDF 0.9.8.1 (2004/29/09) Mounting volume
> > 'PI3LP3W1', timestamp 2007/10/05 07:14 (10b4) [ 150.921083] end_request:
> > I/O error, dev sr0, sector 460164 [ 150.921089] Buffer I/O error on
> > device sr0, logical block 115041 [ 150.921096] Buffer I/O error on
> > device sr0, logical block 115042 [ 150.921099] Buffer I/O error on
> > device sr0, logical block 115043 [ 150.921102] Buffer I/O error on
> > device sr0, logical block 115044 [ 150.921105] Buffer I/O error on
> > device sr0, logical block 115045 [ 150.921108] Buffer I/O error on
> > device sr0, logical block 115046 [ 150.921111] Buffer I/O error on
> > device sr0, logical block 115047 [ 150.921114] Buffer I/O error on
> > device sr0, logical block 115048 [ 150.921116] Buffer I/O error on
> > device sr0, logical block 115049 [ 150.921120] Buffer I/O error on
> > device sr0, logical block 115050 [ 150.979586] end_request: I/O error,
> > dev sr0, sector 460880 [ 151.009564] end_request: I/O error, dev sr0,
> > sector 460880 [ 164.848340] end_request: I/O error, dev sr0, sector
> > 15841200 [ 164.848345] printk: 41 messages suppressed. [ 164.848348]
> > Buffer I/O error on device sr0, logical block 3960300 [ 164.848352]
> > Buffer I/O error on device sr0, logical block 3960301 [ 164.871256]
> > end_request: I/O error, dev sr0, sector 15841200 [ 167.319713]
> > end_request: I/O error, dev sr0, sector 15841200 [ 167.319719] printk: 2
> > messages suppressed. [ 167.319722] Buffer I/O error on device sr0,
> > logical block 3960300 [ 167.383613] end_request: I/O error, dev sr0,
> > sector 15841200 [ 170.856672] end_request: I/O error, dev sr0, sector
> > 460880
>
> > Other stuff about cdrom (it shows 2nd (IDE) cdrom also, which i tested
> > and it didnt read anything, thou it reads that disc on the other -
> > windows machine. Don't know why it shows up there, because i de-
> > attached it already.):
>
> > [ 18.380896] ata3.01: configured for UDMA/100 [ 18.546738] scsi 2:0:0:0:
> > Direct-Access ATA SAMSUNG HD403LJ CT10 PQ: 0 ANSI: 5
> > [ 18.547440] scsi 2:0:1:0: CD-ROM TSSTcorp CDDVDW SH-S203P SB00 PQ: 0
> > ANSI: 5
> > [ 18.554528] Driver 'sd' needs updating - please use bus_type methods [
> > 18.554569] sd 2:0:0:0: [sda] 781422768 512-byte hardware sectors (400088
> > MB)
> > [ 18.554576] sd 2:0:0:0: [sda] Write Protect is off [ 18.554578] sd
> > 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 18.554588] sd 2:0:0:0: [sda]
> > Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> > [ 18.554619] sd 2:0:0:0: [sda] 781422768 512-byte hardware sectors
> > (400088 MB)
> > [ 18.554625] sd 2:0:0:0: [sda] Write Protect is off [ 18.554627] sd
> > 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 18.554637] sd 2:0:0:0: [sda]
> > Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> > [ 18.554639] sda:<4>Driver 'sr' needs updating - please use bus_type
> > methods
> > [ 18.585801] sda1 sda2 < sda5 >
> > [ 18.604858] sd 2:0:0:0: [sda] Attached SCSI disk [ 18.607852] sd
> > 2:0:0:0: Attached scsi generic sg0 type 0 [ 18.607874] sr 2:0:1:0:
> > Attached scsi generic sg1 type 5 [ 18.610563] sr0: scsi3-mmc drive:
> > 48x/48x writer dvd-ram cd/rw xa/ form2 cdda tray
> > [ 18.610565] Uniform CD-ROM driver Revision: 3.20 [ 18.610593] sr
> > 2:0:1:0: Attached scsi CD-ROM sr0
>
> It might be a problem with the SATA port or with the SATA controller. If
> you have more than one type of SATA controller on your motherboard try
> connecting to a different controller. Core2 motherboards frequently have
> two controllers, most SATA connectors are on an Intel chip and then there
> are a couple that are on something else (JMicron is common).

Just tried a brand new IDE drive. (This one:
http://www.samsungoms-europe.com/sam...02&group=multi
)
Same thing happens - can`t play DVD. But can play CD.

This looks like a software bug. Or maybe motherboard has been damaged
somehow?

Details:
[ 78.683220] cdrom: sr0: mrw address space DMA selected
[ 78.764073] cdrom: sr0: mrw address space DMA selected
[ 78.986118] UDF-fs: Partition marked readonly; forcing readonly
mount
[ 79.013705] UDF-fs INFO UDF 0.9.8.1 (2004/29/09) Mounting volume
'PI3LP3W1', timestamp 2007/10/05 07:14 (10b4)
[ 80.217408] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 80.217416] sr 0:0:1:0: [sr0] Sense Key : Hardware Error [current]
[ 80.217420] sr 0:0:1:0: [sr0] Add. Sense: Logical unit
communication CRC error (Ultra-DMA/32)
[ 80.217426] end_request: I/O error, dev sr0, sector 1196
[ 80.217429] Buffer I/O error on device sr0, logical block 299
[ 80.217434] Buffer I/O error on device sr0, logical block 300
[ 80.217438] Buffer I/O error on device sr0, logical block 301
[ 80.217441] Buffer I/O error on device sr0, logical block 302
[ 80.217443] Buffer I/O error on device sr0, logical block 303
[ 80.217446] Buffer I/O error on device sr0, logical block 304
[ 80.217449] Buffer I/O error on device sr0, logical block 305
[ 80.217452] Buffer I/O error on device sr0, logical block 306
[ 80.217455] Buffer I/O error on device sr0, logical block 307
[ 80.217458] Buffer I/O error on device sr0, logical block 308
[ 80.277936] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 80.277943] sr 0:0:1:0: [sr0] Sense Key : Hardware Error [current]
[ 80.277946] sr 0:0:1:0: [sr0] Add. Sense: Logical unit
communication CRC error (Ultra-DMA/32)
[ 80.277952] end_request: I/O error, dev sr0, sector 1224
[ 80.279366] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 80.279370] sr 0:0:1:0: [sr0] Sense Key : Hardware Error [current]
[ 80.279374] sr 0:0:1:0: [sr0] Add. Sense: Logical unit
communication CRC error (Ultra-DMA/32)
[ 80.279380] end_request: I/O error, dev sr0, sector 1228
[ 80.322355] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 80.322360] sr 0:0:1:0: [sr0] Sense Key : Hardware Error [current]
[ 80.322364] sr 0:0:1:0: [sr0] Add. Sense: Logical unit
communication CRC error (Ultra-DMA/32)
[ 80.322370] end_request: I/O error, dev sr0, sector 1224
[ 80.323770] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 80.323774] sr 0:0:1:0: [sr0] Sense Key : Hardware Error [current]
[ 80.323778] sr 0:0:1:0: [sr0] Add. Sense: Logical unit
communication CRC error (Ultra-DMA/32)
[ 80.323791] end_request: I/O error, dev sr0, sector 1228
[ 80.325439] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 80.325443] sr 0:0:1:0: [sr0] Sense Key : Hardware Error [current]
[ 80.325447] sr 0:0:1:0: [sr0] Add. Sense: Logical unit
communication CRC error (Ultra-DMA/32)
[ 80.325453] end_request: I/O error, dev sr0, sector 1232
[ 80.326858] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 80.326863] sr 0:0:1:0: [sr0] Sense Key : Hardware Error [current]
[ 80.326866] sr 0:0:1:0: [sr0] Add. Sense: Logical unit
communication CRC error (Ultra-DMA/32)
[ 80.326872] end_request: I/O error, dev sr0, sector 1236
[ 80.367342] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 80.367347] sr 0:0:1:0: [sr0] Sense Key : Hardware Error [current]
[ 80.367350] sr 0:0:1:0: [sr0] Add. Sense: Logical unit
communication CRC error (Ultra-DMA/32)
[ 80.367356] end_request: I/O error, dev sr0, sector 1232
[ 80.368756] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 80.368761] sr 0:0:1:0: [sr0] Sense Key : Hardware Error [current]
[ 80.368765] sr 0:0:1:0: [sr0] Add. Sense: Logical unit
communication CRC error (Ultra-DMA/32)
[ 80.368770] end_request: I/O error, dev sr0, sector 1236
[ 80.370175] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 80.370180] sr 0:0:1:0: [sr0] Sense Key : Hardware Error [current]
[ 80.370184] sr 0:0:1:0: [sr0] Add. Sense: Logical unit
communication CRC error (Ultra-DMA/32)
[ 80.370190] end_request: I/O error, dev sr0, sector 1240
[ 80.412358] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 80.412365] sr 0:0:1:0: [sr0] Sense Key : Hardware Error [current]
[ 80.412368] sr 0:0:1:0: [sr0] Add. Sense: Logical unit
communication CRC error (Ultra-DMA/32)
[ 80.412374] end_request: I/O error, dev sr0, sector 1240
[ 80.413788] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 80.413793] sr 0:0:1:0: [sr0] Sense Key : Hardware Error [current]
[ 80.413797] sr 0:0:1:0: [sr0] Add. Sense: Logical unit
communication CRC error (Ultra-DMA/32)
[ 80.413803] end_request: I/O error, dev sr0, sector 1244
[ 80.663692] end_request: I/O error, dev sr0, sector 460884
[ 91.778462] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 91.778470] sr 0:0:1:0: [sr0] Sense Key : Hardware Error [current]
[ 91.778474] sr 0:0:1:0: [sr0] Add. Sense: Logical unit
communication CRC error (Ultra-DMA/32)
[ 91.778480] end_request: I/O error, dev sr0, sector 1224
[ 91.778483] printk: 16 messages suppressed.
[ 91.778486] Buffer I/O error on device sr0, logical block 306
[ 91.778490] Buffer I/O error on device sr0, logical block 307
[ 93.200015] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 93.200022] sr 0:0:1:0: [sr0] Sense Key : Hardware Error [current]
[ 93.200026] sr 0:0:1:0: [sr0] Add. Sense: Logical unit
communication CRC error (Ultra-DMA/32)
[ 93.200032] end_request: I/O error, dev sr0, sector 1224
[ 93.201891] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 93.201896] sr 0:0:1:0: [sr0] Sense Key : Hardware Error [current]
[ 93.201899] sr 0:0:1:0: [sr0] Add. Sense: Logical unit
communication CRC error (Ultra-DMA/32)
[ 93.201905] end_request: I/O error, dev sr0, sector 1232
[ 93.223206] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 93.223211] sr 0:0:1:0: [sr0] Sense Key : Hardware Error [current]
[ 93.223215] sr 0:0:1:0: [sr0] Add. Sense: Logical unit
communication CRC error (Ultra-DMA/32)
[ 93.223221] end_request: I/O error, dev sr0, sector 1232
[ 93.224796] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 93.224801] sr 0:0:1:0: [sr0] Sense Key : Hardware Error [current]
[ 93.224804] sr 0:0:1:0: [sr0] Add. Sense: Logical unit
communication CRC error (Ultra-DMA/32)
[ 93.224810] end_request: I/O error, dev sr0, sector 1240
[ 93.246371] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 93.246376] sr 0:0:1:0: [sr0] Sense Key : Hardware Error [current]
[ 93.246379] sr 0:0:1:0: [sr0] Add. Sense: Logical unit
communication CRC error (Ultra-DMA/32)
[ 93.246385] end_request: I/O error, dev sr0, sector 1240
[ 93.701547] end_request: I/O error, dev sr0, sector 15841200
[ 93.747929] end_request: I/O error, dev sr0, sector 15841200

On Tue, 01 Jul 2008 09:33:31 -0700, Jencha wrote:

>
Why don't you try something other than a Samsung?

On Jul 1, 7:55*pm, General Schvantzkopf <schvantzk...@yahoo.com>
wrote:
> On Tue, 01 Jul 2008 09:33:31 -0700, Jencha wrote:
>
> Why don't you try something other than a Samsung?

Well i tried some noname stuff, they didn't work on Ubuntu. But it did
work on Windows machine, from which i took it...
Btw i see that a newer kernel is available, but it won't install with
sudo apt-get upgrade command. So i`ll try to compile it.

On Jul 1, 8:11*pm, Jencha <f...@vv.lv> wrote:
> On Jul 1, 7:55*pm, General Schvantzkopf <schvantzk...@yahoo.com>
> wrote:
>
> > On Tue, 01 Jul 2008 09:33:31 -0700, Jencha wrote:
>
> > Why don't you try something other than a Samsung?
>
> Well i tried some noname stuff, they didn't work on Ubuntu. But it did
> work on Windows machine, from which i took it...
> Btw i see that a newer kernel is available, but it won't install with
> sudo apt-get upgrade command. So i`ll try to compile it.

Owell, it's too complicated for mee to compile kernel. Did like
howtoforge says but, well... it's just too complicated for me - won't
boot up with my new kernel.
Would be good if i could just apt-get upgrade...
But i can't.

On Tue, 01 Jul 2008 11:25:00 -0700, Jencha wrote:

> On Jul 1, 8:11Â*pm, Jencha <f...@vv.lv> wrote:
>> On Jul 1, 7:55Â*pm, General Schvantzkopf <schvantzk...@yahoo.com> wrote:
>>
>> > On Tue, 01 Jul 2008 09:33:31 -0700, Jencha wrote:
>>
>> > Why don't you try something other than a Samsung?
>>
>> Well i tried some noname stuff, they didn't work on Ubuntu. But it did
>> work on Windows machine, from which i took it... Btw i see that a newer
>> kernel is available, but it won't install with sudo apt-get upgrade
>> command. So i`ll try to compile it.
>
> Owell, it's too complicated for mee to compile kernel. Did like
> howtoforge says but, well... it's just too complicated for me - won't
> boot up with my new kernel.
> Would be good if i could just apt-get upgrade... But i can't.

Building a kernel is easy, here is the step by step,

Untar the kernel

Copy the .config file from the source directory of the distro's kernel,
this will configure your kernel with all of the options that your distro
has chosen. On Redhat systems the .config file is in

/usr/src/kernels/2.6.25.6-55.fc9.x86_64/.config

I don't know where they put in on a Debian family, but it must be there
somewhere.

After that do

make gconfig

This will bring up a GUI that will allow you to customize the kernel

Then build and install it as follows (you must be root to do this),

make -j 2 all
make modules_install
make install

On Tue, 01 Jul 2008 13:38:11 -0500, General Schvantzkopf wrote:

> On Tue, 01 Jul 2008 11:25:00 -0700, Jencha wrote:
>
>> On Jul 1, 8:11Â*pm, Jencha <f...@vv.lv> wrote:
>>> On Jul 1, 7:55Â*pm, General Schvantzkopf <schvantzk...@yahoo.com>
>>> wrote:
>>>
>>> > On Tue, 01 Jul 2008 09:33:31 -0700, Jencha wrote:
>>>
>>> > Why don't you try something other than a Samsung?
>>>
>>> Well i tried some noname stuff, they didn't work on Ubuntu. But it did
>>> work on Windows machine, from which i took it... Btw i see that a
>>> newer kernel is available, but it won't install with sudo apt-get
>>> upgrade command. So i`ll try to compile it.
>>
>> Owell, it's too complicated for mee to compile kernel. Did like
>> howtoforge says but, well... it's just too complicated for me - won't
>> boot up with my new kernel.
>> Would be good if i could just apt-get upgrade... But i can't.
>
> Building a kernel is easy, here is the step by step,
>
> Untar the kernel
>
> Copy the .config file from the source directory of the distro's kernel,
> this will configure your kernel with all of the options that your distro
> has chosen. On Redhat systems the .config file is in
>
> /usr/src/kernels/2.6.25.6-55.fc9.x86_64/.config
>
> I don't know where they put in on a Debian family, but it must be there
> somewhere.
>
> After that do
>
> make gconfig
>
> This will bring up a GUI that will allow you to customize the kernel
>
> Then build and install it as follows (you must be root to do this),
>
> make -j 2 all
> make modules_install
> make install

BTW, I really doubt that this is a kernel problem. DVDs use a standard
interface and it's been supported forever.

Did you try my suggestion of using a different SATA connector?

On Tue, 1 Jul 2008, Jencha wrote:

> On Jul 1, 8:11*pm, Jencha <f...@vv.lv> wrote:
>> On Jul 1, 7:55*pm, General Schvantzkopf <schvantzk...@yahoo.com>
>> wrote:
>>
>>> On Tue, 01 Jul 2008 09:33:31 -0700, Jencha wrote:
>>
>>> Why don't you try something other than a Samsung?
>>
>> Well i tried some noname stuff, they didn't work on Ubuntu. But it did
>> work on Windows machine, from which i took it...
>> Btw i see that a newer kernel is available, but it won't install with
>> sudo apt-get upgrade command. So i`ll try to compile it.
>
> Owell, it's too complicated for mee to compile kernel. Did like
> howtoforge says but, well... it's just too complicated for me - won't
> boot up with my new kernel.
> Would be good if i could just apt-get upgrade...
> But i can't.
>

Are you sure that the disk (not the drive) is not corrupted?