Posts by s.krueger

s.krueger · Jul 23rd 2012

Ehlich? die SSD ist gerade mal 1 Monat alt!

s.krueger · Jul 22nd 2012

Hallo,

Ich habe im log folgendes gefunden:

Code

Jul 22 22:55:51 hdvdr kernel: [17243.384137] ata1.00: qc timeout (cmd 0x2f)                                                                              	
Jul 22 22:55:51 hdvdr kernel: [17243.384150] ata1: failed to read log page 10h (errno=-5)                                                                	
Jul 22 22:55:51 hdvdr kernel: [17243.384165] ata1.00: exception Emask 0x1 SAct 0xc SErr 0x0 action 0x6 frozen
Jul 22 22:55:51 hdvdr kernel: [17243.384171] ata1.00: irq_stat 0x40000008
Jul 22 22:55:51 hdvdr kernel: [17243.384179] ata1.00: failed command: READ FPDMA QUEUED
Jul 22 22:55:51 hdvdr kernel: [17243.384194] ata1.00: cmd 60/30:10:08:e1:2b/00:00:00:00:00/40 tag 2 ncq 24576 in
Jul 22 22:55:51 hdvdr kernel: [17243.384197]      	res 40/00:00:40:e1:2b/00:00:00:00:00/40 Emask 0x1 (device error)
Jul 22 22:55:51 hdvdr kernel: [17243.384204] ata1.00: status: { DRDY }
Jul 22 22:55:51 hdvdr kernel: [17243.384210] ata1.00: failed command: READ FPDMA QUEUED
Jul 22 22:55:51 hdvdr kernel: [17243.384222] ata1.00: cmd 60/20:18:40:e1:2b/00:00:00:00:00/40 tag 3 ncq 16384 in
Jul 22 22:55:51 hdvdr kernel: [17243.384225]      	res 40/00:00:40:e1:2b/00:00:00:00:00/40 Emask 0x1 (device error)
Jul 22 22:55:51 hdvdr kernel: [17243.384232] ata1.00: status: { DRDY }
Jul 22 22:55:51 hdvdr kernel: [17243.384242] ata1: hard resetting link
Jul 22 22:55:51 hdvdr kernel: [17243.704076] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jul 22 22:55:51 hdvdr kernel: [17243.704680] ata1.00: configured for UDMA/133
Jul 22 22:55:51 hdvdr kernel: [17243.704708] ata1: EH complete
Jul 22 22:55:56 hdvdr kernel: [17248.704089] ata1.00: qc timeout (cmd 0x2f)
Jul 22 22:55:56 hdvdr kernel: [17248.704103] ata1: failed to read log page 10h (errno=-5)
Jul 22 22:55:56 hdvdr kernel: [17248.704117] ata1.00: exception Emask 0x1 SAct 0x7a SErr 0x0 action 0x6 frozen
Jul 22 22:55:56 hdvdr kernel: [17248.704124] ata1.00: irq_stat 0x40000008
Jul 22 22:55:56 hdvdr kernel: [17248.704132] ata1.00: failed command: READ FPDMA QUEUED
Jul 22 22:55:56 hdvdr kernel: [17248.704146] ata1.00: cmd 60/30:08:08:e1:2b/00:00:00:00:00/40 tag 1 ncq 24576 in
Jul 22 22:55:56 hdvdr kernel: [17248.704149]      	res 40/00:00:70:ec:94/00:00:00:00:00/40 Emask 0x1 (device error)
Jul 22 22:55:56 hdvdr kernel: [17248.704156] ata1.00: status: { DRDY }
Jul 22 22:55:56 hdvdr kernel: [17248.704162] ata1.00: failed command: WRITE FPDMA QUEUED
Jul 22 22:55:56 hdvdr kernel: [17248.704175] ata1.00: cmd 61/00:18:a8:64:84/04:00:00:00:00/40 tag 3 ncq 524288 out
Jul 22 22:55:56 hdvdr kernel: [17248.704178]      	res 40/00:00:70:ec:94/00:00:00:00:00/40 Emask 0x1 (device error)
Jul 22 22:55:56 hdvdr kernel: [17248.704185] ata1.00: status: { DRDY }
Jul 22 22:55:56 hdvdr kernel: [17248.704191] ata1.00: failed command: WRITE FPDMA QUEUED
Jul 22 22:55:56 hdvdr kernel: [17248.704203] ata1.00: cmd 61/b8:20:a8:68:84/01:00:00:00:00/40 tag 4 ncq 225280 out
Jul 22 22:55:56 hdvdr kernel: [17248.704206]      	res 40/00:00:70:ec:94/00:00:00:00:00/40 Emask 0x1 (device error)
Jul 22 22:55:56 hdvdr kernel: [17248.704213] ata1.00: status: { DRDY }
Jul 22 22:55:56 hdvdr kernel: [17248.704219] ata1.00: failed command: WRITE FPDMA QUEUED
Jul 22 22:55:56 hdvdr kernel: [17248.704231] ata1.00: cmd 61/08:28:f0:2e:94/00:00:00:00:00/40 tag 5 ncq 4096 out
Jul 22 22:55:56 hdvdr kernel: [17248.704234]      	res 40/00:00:70:ec:94/00:00:00:00:00/40 Emask 0x1 (device error)
Jul 22 22:55:56 hdvdr kernel: [17248.704241] ata1.00: status: { DRDY }
Jul 22 22:55:56 hdvdr kernel: [17248.704247] ata1.00: failed command: WRITE FPDMA QUEUED
Jul 22 22:55:56 hdvdr kernel: [17248.704259] ata1.00: cmd 61/08:30:70:ec:94/00:00:00:00:00/40 tag 6 ncq 4096 out
Jul 22 22:55:56 hdvdr kernel: [17248.704262]      	res 40/00:00:70:ec:94/00:00:00:00:00/40 Emask 0x1 (device error)
Jul 22 22:55:56 hdvdr kernel: [17248.704268] ata1.00: status: { DRDY }
Jul 22 22:55:56 hdvdr kernel: [17248.704278] ata1: hard resetting link
Jul 22 22:55:56 hdvdr kernel: [17249.024088] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jul 22 22:55:56 hdvdr kernel: [17249.024684] ata1.00: configured for UDMA/133
Jul 22 22:55:56 hdvdr kernel: [17249.024716] ata1: EH complete
Jul 22 22:56:01 hdvdr kernel: [17254.024077] ata1.00: qc timeout (cmd 0x2f)
Jul 22 22:56:01 hdvdr kernel: [17254.024091] ata1: failed to read log page 10h (errno=-5)
Jul 22 22:56:01 hdvdr kernel: [17254.024105] ata1.00: exception Emask 0x1 SAct 0x1e SErr 0x0 action 0x6 frozen
Jul 22 22:56:01 hdvdr kernel: [17254.024112] ata1.00: irq_stat 0x40000008
Jul 22 22:56:01 hdvdr kernel: [17254.024120] ata1.00: failed command: WRITE FPDMA QUEUED
Jul 22 22:56:01 hdvdr kernel: [17254.024135] ata1.00: cmd 61/08:08:f0:2e:94/00:00:00:00:00/40 tag 1 ncq 4096 out
Jul 22 22:56:01 hdvdr kernel: [17254.024138]      	res 40/00:00:08:e1:2b/00:00:00:00:00/40 Emask 0x1 (device error)
Jul 22 22:56:01 hdvdr kernel: [17254.024145] ata1.00: status: { DRDY }
Jul 22 22:56:01 hdvdr kernel: [17254.024151] ata1.00: failed command: WRITE FPDMA QUEUED
Jul 22 22:56:01 hdvdr kernel: [17254.024165] ata1.00: cmd 61/b8:10:a8:68:84/01:00:00:00:00/40 tag 2 ncq 225280 out
Jul 22 22:56:01 hdvdr kernel: [17254.024168]      	res 40/00:00:08:e1:2b/00:00:00:00:00/40 Emask 0x1 (device error)
Jul 22 22:56:01 hdvdr kernel: [17254.024174] ata1.00: status: { DRDY }
Jul 22 22:56:01 hdvdr kernel: [17254.024180] ata1.00: failed command: WRITE FPDMA QUEUED
Jul 22 22:56:01 hdvdr kernel: [17254.024193] ata1.00: cmd 61/00:18:a8:64:84/04:00:00:00:00/40 tag 3 ncq 524288 out
Jul 22 22:56:01 hdvdr kernel: [17254.024196]      	res 40/00:00:08:e1:2b/00:00:00:00:00/40 Emask 0x1 (device error)
Jul 22 22:56:01 hdvdr kernel: [17254.024202] ata1.00: status: { DRDY }
Jul 22 22:56:01 hdvdr kernel: [17254.024208] ata1.00: failed command: READ FPDMA QUEUED
Jul 22 22:56:01 hdvdr kernel: [17254.024220] ata1.00: cmd 60/30:20:08:e1:2b/00:00:00:00:00/40 tag 4 ncq 24576 in
Jul 22 22:56:01 hdvdr kernel: [17254.024223]      	res 40/00:00:08:e1:2b/00:00:00:00:00/40 Emask 0x1 (device error)
Jul 22 22:56:01 hdvdr kernel: [17254.024230] ata1.00: status: { DRDY }
Jul 22 22:56:01 hdvdr kernel: [17254.024240] ata1: hard resetting link
Jul 22 22:56:02 hdvdr kernel: [17254.344086] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jul 22 22:56:02 hdvdr kernel: [17254.344686] ata1.00: configured for UDMA/133
Jul 22 22:56:02 hdvdr kernel: [17254.344717] ata1: EH complete
Jul 22 22:56:07 hdvdr kernel: [17259.344090] ata1.00: qc timeout (cmd 0x2f)
Jul 22 22:56:07 hdvdr kernel: [17259.344104] ata1: failed to read log page 10h (errno=-5)
Jul 22 22:56:07 hdvdr kernel: [17259.344114] ata1.00: NCQ disabled due to excessive errors
Jul 22 22:56:07 hdvdr kernel: [17259.344124] ata1.00: exception Emask 0x1 SAct 0xd SErr 0x0 action 0x6 frozen
Jul 22 22:56:07 hdvdr kernel: [17259.344130] ata1.00: irq_stat 0x40000008
Jul 22 22:56:07 hdvdr kernel: [17259.344138] ata1.00: failed command: READ FPDMA QUEUED
Jul 22 22:56:07 hdvdr kernel: [17259.344152] ata1.00: cmd 60/30:00:08:e1:2b/00:00:00:00:00/40 tag 0 ncq 24576 in
Jul 22 22:56:07 hdvdr kernel: [17259.344155]      	res 40/00:00:f0:2e:94/00:00:00:00:00/40 Emask 0x1 (device error)
Jul 22 22:56:07 hdvdr kernel: [17259.344162] ata1.00: status: { DRDY }
Jul 22 22:56:07 hdvdr kernel: [17259.344168] ata1.00: failed command: WRITE FPDMA QUEUED
Jul 22 22:56:07 hdvdr kernel: [17259.344181] ata1.00: cmd 61/b8:10:a8:68:84/01:00:00:00:00/40 tag 2 ncq 225280 out
Jul 22 22:56:07 hdvdr kernel: [17259.344184]      	res 40/00:00:f0:2e:94/00:00:00:00:00/40 Emask 0x1 (device error)
Jul 22 22:56:07 hdvdr kernel: [17259.344191] ata1.00: status: { DRDY }
Jul 22 22:56:07 hdvdr kernel: [17259.344197] ata1.00: failed command: WRITE FPDMA QUEUED
Jul 22 22:56:07 hdvdr kernel: [17259.344209] ata1.00: cmd 61/08:18:f0:2e:94/00:00:00:00:00/40 tag 3 ncq 4096 out
Jul 22 22:56:07 hdvdr kernel: [17259.344212]      	res 40/00:00:f0:2e:94/00:00:00:00:00/40 Emask 0x1 (device error)
Jul 22 22:56:07 hdvdr kernel: [17259.344219] ata1.00: status: { DRDY }
Jul 22 22:56:07 hdvdr kernel: [17259.344229] ata1: hard resetting link
Jul 22 22:56:07 hdvdr kernel: [17259.664084] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jul 22 22:56:07 hdvdr kernel: [17259.664684] ata1.00: configured for UDMA/133
Jul 22 22:56:07 hdvdr kernel: [17259.664714] ata1: EH complete
Jul 22 22:56:07 hdvdr kernel: [17259.666238] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jul 22 22:56:07 hdvdr kernel: [17259.666248] ata1.00: irq_stat 0x40000001
Jul 22 22:56:07 hdvdr kernel: [17259.666256] ata1.00: failed command: READ DMA
Jul 22 22:56:07 hdvdr kernel: [17259.666271] ata1.00: cmd c8/00:30:08:e1:2b/00:00:00:00:00/e0 tag 0 dma 24576 in
Jul 22 22:56:07 hdvdr kernel: [17259.666274]      	res 51/40:00:08:e1:2b/00:00:00:00:00/e0 Emask 0x9 (media error)
Jul 22 22:56:07 hdvdr kernel: [17259.666293] ata1.00: status: { DRDY ERR }
Jul 22 22:56:07 hdvdr kernel: [17259.666298] ata1.00: error: { UNC }
Jul 22 22:56:07 hdvdr kernel: [17259.674728] ata1.00: configured for UDMA/133
Jul 22 22:56:07 hdvdr kernel: [17259.674750] ata1: EH complete
Jul 22 22:56:07 hdvdr kernel: [17259.675022] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jul 22 22:56:07 hdvdr kernel: [17259.675031] ata1.00: irq_stat 0x40000001
Jul 22 22:56:07 hdvdr kernel: [17259.675039] ata1.00: failed command: READ DMA
Jul 22 22:56:07 hdvdr kernel: [17259.675053] ata1.00: cmd c8/00:30:08:e1:2b/00:00:00:00:00/e0 tag 0 dma 24576 in
Jul 22 22:56:07 hdvdr kernel: [17259.675057]      	res 51/40:00:08:e1:2b/00:00:00:00:00/e0 Emask 0x9 (media error)
Jul 22 22:56:07 hdvdr kernel: [17259.675066] ata1.00: status: { DRDY ERR }
Jul 22 22:56:07 hdvdr kernel: [17259.675071] ata1.00: error: { UNC }
Jul 22 22:56:07 hdvdr kernel: [17259.680233] ata1.00: configured for UDMA/133
Jul 22 22:56:07 hdvdr kernel: [17259.680263] sd 0:0:0:0: [sda] Unhandled sense code
Jul 22 22:56:07 hdvdr kernel: [17259.680269] sd 0:0:0:0: [sda]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 22 22:56:07 hdvdr kernel: [17259.680278] sd 0:0:0:0: [sda]  Sense Key : Medium Error [current] [descriptor]
Jul 22 22:56:07 hdvdr kernel: [17259.680287] Descriptor sense data with sense descriptors (in hex):
Jul 22 22:56:07 hdvdr kernel: [17259.680292]     	72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
Jul 22 22:56:07 hdvdr kernel: [17259.680312]     	00 2b e1 08 
Jul 22 22:56:07 hdvdr kernel: [17259.680320] sd 0:0:0:0: [sda]  Add. Sense: Unrecovered read error - auto reallocate failed
Jul 22 22:56:07 hdvdr kernel: [17259.680331] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 2b e1 08 00 00 30 00
Jul 22 22:56:07 hdvdr kernel: [17259.680349] end_request: I/O error, dev sda, sector 2875656
Jul 22 22:56:07 hdvdr kernel: [17259.680393] ata1: EH complete
Jul 22 22:56:07 hdvdr kernel: [17259.686858] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jul 22 22:56:07 hdvdr kernel: [17259.686868] ata1.00: irq_stat 0x40000001
Jul 22 22:56:07 hdvdr kernel: [17259.686875] ata1.00: failed command: READ DMA
Jul 22 22:56:07 hdvdr kernel: [17259.686889] ata1.00: cmd c8/00:08:30:e1:2b/00:00:00:00:00/e0 tag 0 dma 4096 in
Jul 22 22:56:07 hdvdr kernel: [17259.686892]      	res 51/40:00:30:e1:2b/00:00:00:00:00/e0 Emask 0x9 (media error)
Jul 22 22:56:07 hdvdr kernel: [17259.686899] ata1.00: status: { DRDY ERR }
Jul 22 22:56:07 hdvdr kernel: [17259.686904] ata1.00: error: { UNC }
Jul 22 22:56:07 hdvdr kernel: [17259.694242] ata1.00: configured for UDMA/133
Jul 22 22:56:07 hdvdr kernel: [17259.694267] ata1: EH complete
Jul 22 22:56:07 hdvdr kernel: [17259.694517] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jul 22 22:56:07 hdvdr kernel: [17259.694527] ata1.00: irq_stat 0x40000001
Jul 22 22:56:07 hdvdr kernel: [17259.694534] ata1.00: failed command: READ DMA
Jul 22 22:56:07 hdvdr kernel: [17259.694547] ata1.00: cmd c8/00:08:30:e1:2b/00:00:00:00:00/e0 tag 0 dma 4096 in
Jul 22 22:56:07 hdvdr kernel: [17259.694550]      	res 51/40:00:30:e1:2b/00:00:00:00:00/e0 Emask 0x9 (media error)
Jul 22 22:56:07 hdvdr kernel: [17259.694557] ata1.00: status: { DRDY ERR }
Jul 22 22:56:07 hdvdr kernel: [17259.694562] ata1.00: error: { UNC }
Jul 22 22:56:07 hdvdr kernel: [17259.699637] ata1.00: configured for UDMA/133
Jul 22 22:56:07 hdvdr kernel: [17259.699662] ata1: EH complete
Jul 22 22:56:07 hdvdr kernel: [17259.699900] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jul 22 22:56:07 hdvdr kernel: [17259.699909] ata1.00: irq_stat 0x40000001
Jul 22 22:56:07 hdvdr kernel: [17259.699916] ata1.00: failed command: READ DMA
Jul 22 22:56:07 hdvdr kernel: [17259.699929] ata1.00: cmd c8/00:08:30:e1:2b/00:00:00:00:00/e0 tag 0 dma 4096 in
Jul 22 22:56:07 hdvdr kernel: [17259.699932]      	res 51/40:00:30:e1:2b/00:00:00:00:00/e0 Emask 0x9 (media error)
Jul 22 22:56:07 hdvdr kernel: [17259.699939] ata1.00: status: { DRDY ERR }
Jul 22 22:56:07 hdvdr kernel: [17259.699944] ata1.00: error: { UNC }
Jul 22 22:56:07 hdvdr kernel: [17259.706732] ata1.00: configured for UDMA/133
Jul 22 22:56:07 hdvdr kernel: [17259.706757] ata1: EH complete
Jul 22 22:56:07 hdvdr kernel: [17259.706995] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jul 22 22:56:07 hdvdr kernel: [17259.707004] ata1.00: irq_stat 0x40000001
Jul 22 22:56:07 hdvdr kernel: [17259.707011] ata1.00: failed command: READ DMA
Jul 22 22:56:07 hdvdr kernel: [17259.707024] ata1.00: cmd c8/00:08:30:e1:2b/00:00:00:00:00/e0 tag 0 dma 4096 in
Jul 22 22:56:07 hdvdr kernel: [17259.707027]      	res 51/40:00:30:e1:2b/00:00:00:00:00/e0 Emask 0x9 (media error)
Jul 22 22:56:07 hdvdr kernel: [17259.707034] ata1.00: status: { DRDY ERR }
Jul 22 22:56:07 hdvdr kernel: [17259.707039] ata1.00: error: { UNC }
Jul 22 22:56:07 hdvdr kernel: [17259.712151] ata1.00: configured for UDMA/133
Jul 22 22:56:07 hdvdr kernel: [17259.712182] ata1: EH complete
Jul 22 22:56:07 hdvdr kernel: [17259.712433] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jul 22 22:56:07 hdvdr kernel: [17259.712442] ata1.00: irq_stat 0x40000001
Jul 22 22:56:07 hdvdr kernel: [17259.712449] ata1.00: failed command: READ DMA
Jul 22 22:56:07 hdvdr kernel: [17259.712462] ata1.00: cmd c8/00:08:30:e1:2b/00:00:00:00:00/e0 tag 0 dma 4096 in
Jul 22 22:56:07 hdvdr kernel: [17259.712465]      	res 51/40:00:30:e1:2b/00:00:00:00:00/e0 Emask 0x9 (media error)
Jul 22 22:56:07 hdvdr kernel: [17259.712472] ata1.00: status: { DRDY ERR }
Jul 22 22:56:07 hdvdr kernel: [17259.712477] ata1.00: error: { UNC }
Jul 22 22:56:07 hdvdr kernel: [17259.719235] ata1.00: configured for UDMA/133
Jul 22 22:56:07 hdvdr kernel: [17259.719260] ata1: EH complete
Jul 22 22:56:07 hdvdr kernel: [17259.719503] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jul 22 22:56:07 hdvdr kernel: [17259.719512] ata1.00: irq_stat 0x40000001
Jul 22 22:56:07 hdvdr kernel: [17259.719519] ata1.00: failed command: READ DMA
Jul 22 22:56:07 hdvdr kernel: [17259.719532] ata1.00: cmd c8/00:08:30:e1:2b/00:00:00:00:00/e0 tag 0 dma 4096 in
Jul 22 22:56:07 hdvdr kernel: [17259.719535]      	res 51/40:00:30:e1:2b/00:00:00:00:00/e0 Emask 0x9 (media error)
Jul 22 22:56:07 hdvdr kernel: [17259.719542] ata1.00: status: { DRDY ERR }
Jul 22 22:56:07 hdvdr kernel: [17259.719547] ata1.00: error: { UNC }
Jul 22 22:56:07 hdvdr kernel: [17259.724651] ata1.00: configured for UDMA/133
Jul 22 22:56:07 hdvdr kernel: [17259.724678] sd 0:0:0:0: [sda] Unhandled sense code
Jul 22 22:56:07 hdvdr kernel: [17259.724694] sd 0:0:0:0: [sda]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 22 22:56:07 hdvdr kernel: [17259.724703] sd 0:0:0:0: [sda]  Sense Key : Medium Error [current] [descriptor]
Jul 22 22:56:07 hdvdr kernel: [17259.724712] Descriptor sense data with sense descriptors (in hex):
Jul 22 22:56:07 hdvdr kernel: [17259.724717]     	72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
Jul 22 22:56:07 hdvdr kernel: [17259.724736]     	00 2b e1 30 
Jul 22 22:56:07 hdvdr kernel: [17259.724744] sd 0:0:0:0: [sda]  Add. Sense: Unrecovered read error - auto reallocate failed
Jul 22 22:56:07 hdvdr kernel: [17259.724755] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 2b e1 30 00 00 08 00
Jul 22 22:56:07 hdvdr kernel: [17259.724773] end_request: I/O error, dev sda, sector 2875696
Jul 22 22:56:07 hdvdr kernel: [17259.724820] ata1: EH complete

Display More

und dann mal das gemacht:

Code

smartctl -a /dev/sda
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-24-generic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net


=== START OF INFORMATION SECTION ===
Model Family: 	JMicron based SSDs
Device Model: 	ADATA S596 Turbo
Serial Number:	02206154500100000099
Firmware Version: 110512
User Capacity:	32.017.047.552 bytes [32,0 GB]
Sector Size:  	512 bytes logical/physical
Device is:    	In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:	Sun Jul 22 23:00:59 2012 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled


=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED


General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                    	was never started.
                                    	Auto Offline Data Collection: Disabled.
Self-test execution status:  	( 239) Reserved.
Total time to complete Offline 
data collection:            	(   30) seconds.
Offline data collection
capabilities:                	(0x1b) SMART execute Offline immediate.
                                    	Auto Offline data collection on/off support.
                                    	Suspend Offline collection upon new
                                    	command.
                                    	Offline surface scan supported.
                                    	Self-test supported.
                                    	No Conveyance Self-test supported.
                                    	No Selective Self-test supported.
SMART capabilities:        	(0x0003) Saves SMART data before entering
                                    	power-saving mode.
                                    	Supports SMART auto save timer.
Error logging capability:    	(0x01) Error logging supported.
                                    	General Purpose Logging supported.
Short self-test routine 
recommended polling time:    	(   1) minutes.
Extended self-test routine
recommended polling time:    	(   1) minutes.


SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME      	FLAG 	VALUE WORST THRESH TYPE  	UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate 	0x000b   100   100   050	Pre-fail  Always   	-   	16777215
  2 Throughput_Performance  0x0005   100   100   050	Pre-fail  Offline  	-   	0
  3 Unknown_Attribute   	0x0007   100   100   050	Pre-fail  Always   	-   	0
  5 Reallocated_Sector_Ct   0x0013   100   100   050	Pre-fail  Always   	-   	0
  7 Unknown_Attribute   	0x000b   100   100   050	Pre-fail  Always   	-   	0
  8 Unknown_Attribute   	0x0005   100   100   050	Pre-fail  Offline  	-   	0
  9 Power_On_Hours      	0x0012   100   100   000	Old_age   Always   	-   	34
 10 Unknown_Attribute   	0x0013   100   100   050	Pre-fail  Always   	-   	0
 12 Power_Cycle_Count   	0x0012   100   100   000	Old_age   Always   	-   	59
168 SATA_Phy_Error_Count	0x0012   100   100   000	Old_age   Always   	-   	8
175 Bad_Cluster_Table_Count 0x0003   100   100   010	Pre-fail  Always   	-   	5
192 Unexpect_Power_Loss_Ct  0x0012   100   100   000	Old_age   Always   	-   	0
194 Temperature_Celsius 	0x0022   040   100   000	Old_age   Always   	-   	40 (Min/Max 30/60)
197 Current_Pending_Sector  0x0012   100   100   000	Old_age   Always   	-   	0
240 Unknown_Attribute   	0x0013   100   100   050	Pre-fail  Always   	-   	0
170 Bad_Block_Count     	0x0003   100   100   010	Pre-fail  Always   	-   	5 18 6
173 Erase_Count         	0x0012   100   100   000	Old_age   Always   	-   	2 191 48


SMART Error Log Version: 1
ATA Error Count: 158 (device log contains only the most recent five errors)
    	CR = Command Register [HEX]
    	FR = Features Register [HEX]
    	SC = Sector Count Register [HEX]
    	SN = Sector Number Register [HEX]
    	CL = Cylinder Low Register [HEX]
    	CH = Cylinder High Register [HEX]
    	DH = Device/Head Register [HEX]
    	DC = Device Command Register [HEX]
    	ER = Error register [HEX]
    	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.


Error 158 occurred at disk power-on lifetime: 34 hours (1 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.


  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 30 e1 2b e0  Error: UNC at LBA = 0x002be130 = 2875696


  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 30 e1 2b e0 08  	00:42:20.200  READ DMA
  ec 00 00 00 00 00 a0 08  	00:42:20.200  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08  	00:42:20.200  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 08  	00:42:20.200  IDENTIFY DEVICE
  c8 00 08 30 e1 2b e0 08  	00:42:20.200  READ DMA


Error 157 occurred at disk power-on lifetime: 34 hours (1 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.


  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 30 e1 2b e0  Error: UNC at LBA = 0x002be130 = 2875696


  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 30 e1 2b e0 08  	00:42:20.200  READ DMA
  ec 00 00 00 00 00 a0 08  	00:42:20.200  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08  	00:42:20.200  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 08  	00:42:20.200  IDENTIFY DEVICE
  c8 00 08 30 e1 2b e0 08  	00:42:20.200  READ DMA


Error 156 occurred at disk power-on lifetime: 34 hours (1 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.


  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 30 e1 2b e0  Error: UNC at LBA = 0x002be130 = 2875696


  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 30 e1 2b e0 08  	00:42:20.200  READ DMA
  ec 00 00 00 00 00 a0 08  	00:42:20.200  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08  	00:42:20.200  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 08  	00:42:20.200  IDENTIFY DEVICE
  c8 00 08 30 e1 2b e0 08  	00:42:20.200  READ DMA


Error 155 occurred at disk power-on lifetime: 34 hours (1 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.


  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 30 e1 2b e0  Error: UNC at LBA = 0x002be130 = 2875696


  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 30 e1 2b e0 08  	00:42:20.200  READ DMA
  ec 00 00 00 00 00 a0 08  	00:42:20.200  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08  	00:42:20.200  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 08  	00:42:20.200  IDENTIFY DEVICE
  c8 00 08 30 e1 2b e0 08  	00:42:20.200  READ DMA


Error 154 occurred at disk power-on lifetime: 34 hours (1 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.


  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 30 e1 2b e0  Error: UNC at LBA = 0x002be130 = 2875696


  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 30 e1 2b e0 08  	00:42:20.200  READ DMA
  ec 00 00 00 00 00 a0 08  	00:42:20.200  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08  	00:42:20.200  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 08  	00:42:20.200  IDENTIFY DEVICE
  c8 00 08 30 e1 2b e0 08  	00:42:20.200  READ DMA


SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]




Device does not support Selective Self Tests/Logging

Display More

Das ganze tritt auf wenn ich z.B. XBMC starten will! So habe ich mit der SSD keine Probleme, VDR ist schnell up.

Kernel: uname -r
3.2.0-24-generic

Was kann das sein? fsck findet keine Fehler und ich weis nicht was ich dagegen machen kann. Google hilft mir leider nicht wirklich weiter...
Wer kann Helfen?

MFG SVen

s.krueger · Jul 17th 2012

Hi,

Bin leider nicht weiter gekommen und poste einfach mal logs, vielleicht seht ihr ja mehr als ich:

Code

Jul 17 10:28:26 hdvdr vdr: [1836] executing command '/usr/share/vdr/menuorg-appswitcher standalone=yes app=xbmc &> /dev/null '
Jul 17 10:28:26 hdvdr vdr: [1956] dbus2vdr: new message, object /Plugins/softhddevice, interface de.tvdr.vdr.plugin, member SVDRPCommand
Jul 17 10:28:26 hdvdr vdr: [1956] dbus2vdr: 1 idle message handler, reusing 0x7fd430001e40
Jul 17 10:28:26 hdvdr vdr: [2145] dbus2vdr message handler thread started (pid=1836, tid=2145)
Jul 17 10:28:26 hdvdr vdr: [2145] dbus2vdr: de.tvdr.vdr.plugin.SVDRPCommand: command 'DETA' has no option
Jul 17 10:28:26 hdvdr vdr: [2145] dbus2vdr: invoking softhddevice.SVDRPCommand("DETA", "")
Jul 17 10:28:26 hdvdr vdr: [2145] [softhddev]SetPlayMode: 0
Jul 17 10:28:26 hdvdr vdr: [2145] [softhddev]SetVideoDisplayFormat: 1
Jul 17 10:28:26 hdvdr vdr: [1956] dbus2vdr: new message, object /Remote, interface de.tvdr.vdr.remote, member Disable
Jul 17 10:28:26 hdvdr vdr: [1956] dbus2vdr: starting new message handler 0x7fd43000edf0
Jul 17 10:28:26 hdvdr vdr: [2154] dbus2vdr message handler thread started (pid=1836, tid=2154)
Jul 17 10:28:26 hdvdr vdr: [2154] dbus2vdr: moving message handler 0x7fd43000edf0 from active to finished
Jul 17 10:28:26 hdvdr vdr: [2154] dbus2vdr message handler thread ended (pid=1836, tid=2154)
Jul 17 10:28:26 hdvdr vdr: [2145] [softhddev]SetPlayMode: 1
Jul 17 10:28:26 hdvdr vdr: [2145] dbus2vdr: moving message handler 0x7fd430001e40 from active to finished
Jul 17 10:28:26 hdvdr vdr: [2145] dbus2vdr message handler thread ended (pid=1836, tid=2145)
Jul 17 10:28:26 hdvdr vdr: [2134] Text2Skin: menu display update thread ended (pid=1836, tid=2134)
Jul 17 10:28:54 hdvdr kernel: [   68.954306] init: xbmc main process (2157) killed by BUS signal
Jul 17 10:28:54 hdvdr vdr: [1956] dbus2vdr: new message, object /Remote, interface de.tvdr.vdr.remote, member Enable
Jul 17 10:28:54 hdvdr vdr: [1956] dbus2vdr: 2 idle message handler, reusing 0x7fd43000edf0
Jul 17 10:28:54 hdvdr vdr: [2330] dbus2vdr message handler thread started (pid=1836, tid=2330)
Jul 17 10:28:54 hdvdr vdr: [2330] dbus2vdr: moving message handler 0x7fd43000edf0 from active to finished
Jul 17 10:28:54 hdvdr vdr: [2330] dbus2vdr message handler thread ended (pid=1836, tid=2330)
Jul 17 10:28:55 hdvdr XBMC: XBMC exit with exit status , BUS, ENV: TERM=linux#012EXIT_SIGNAL=BUS#012PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin#012PWD=/#012JOB=xbmc#012RESULT=failed#012SHLVL=1#012HOME=/var/lib/vdr#012PROCESS=main#012UPSTART_INSTANCE=#012UPSTART_EVENTS=stopped#012UPSTART_JOB=xbmc-exit#012INSTANCE=#012DISPLAY=:1#012_=/usr/bin/env .
Jul 17 10:28:55 hdvdr /usr/bin/signal-event.real[2337]: processing signal reset-display-rate
Jul 17 10:28:55 hdvdr /usr/bin/signal-event.real[2337]: processing action /usr/share/yavdr/events/reset-display-rate/10_reset-display-rate reset-display-rate
Jul 17 10:28:55 hdvdr /usr/bin/signal-event.real[2337]: finished processing signal reset-display-rate
Jul 17 10:28:56 hdvdr vdr: [1956] dbus2vdr: new message, object /Plugins/softhddevice, interface de.tvdr.vdr.plugin, member SVDRPCommand
Jul 17 10:28:56 hdvdr vdr: [1956] dbus2vdr: 2 idle message handler, reusing 0x7fd430001e40
Jul 17 10:28:56 hdvdr vdr: [2364] dbus2vdr message handler thread started (pid=1836, tid=2364)
Jul 17 10:28:56 hdvdr vdr: [2364] dbus2vdr: invoking softhddevice.SVDRPCommand("ATTA", "-d :1")
Jul 17 10:28:56 hdvdr vdr: [2364] [softhddev]SetPlayMode: 0
Jul 17 10:28:56 hdvdr vdr: [2364] [softhddev]SetVideoDisplayFormat: 1
Jul 17 10:28:56 hdvdr vdr: [2364] [softhddev]~cSoftHdControl: dummy player stopped
Jul 17 10:28:56 hdvdr vdr: video/vdpau: VDPAU API version: 1
Jul 17 10:28:56 hdvdr vdr: video/vdpau: VDPAU information: NVIDIA VDPAU Driver Shared Library  295.40  Thu Apr  5 22:02:06 PDT 2012
Jul 17 10:28:56 hdvdr vdr: video/vdpau: high quality scaling unsupported
Jul 17 10:28:56 hdvdr vdr: video/vdpau: feature deinterlace temporal supported
Jul 17 10:28:56 hdvdr vdr: video/vdpau: feature deinterlace temporal spatial supported
Jul 17 10:28:56 hdvdr vdr: video/vdpau: attribute skip chroma deinterlace supported
Jul 17 10:28:56 hdvdr vdr: video/vdpau: 4:2:0 chroma format with 4096x4096 supported
Jul 17 10:28:56 hdvdr vdr: video/vdpau: 4:2:2 chroma format with 4096x4096 supported
Jul 17 10:28:56 hdvdr vdr: video/vdpau: 8bit BGRA format with 8192x8192 supported
Jul 17 10:28:56 hdvdr vdr: video/vdpau: 10bit RGBA format with 8192x8192 supported
Jul 17 10:28:56 hdvdr vdr: audio: 'alsa' output module used
Jul 17 10:28:56 hdvdr vdr: audio/alsa: supports pause: no
Jul 17 10:28:56 hdvdr vdr: audio:  44100Hz supports 1 2 3 4 5 6 7 8 channels
Jul 17 10:28:56 hdvdr vdr: audio:  48000Hz supports 1 2 3 4 5 6 7 8 channels
Jul 17 10:28:56 hdvdr vdr: [2364] dbus2vdr: moving message handler 0x7fd430001e40 from active to finished
Jul 17 10:28:56 hdvdr vdr: [2364] dbus2vdr message handler thread ended (pid=1836, tid=2364)
Jul 17 10:28:56 hdvdr vdr: [1836] switching to channel 4
Jul 17 10:28:56 hdvdr vdr: [2128] osdteletext-receiver thread ended (pid=1836, tid=2128)
Jul 17 10:28:56 hdvdr vdr: [1836] buffer stats: 0 (0%) used
Jul 17 10:28:56 hdvdr vdr: [2129] TS buffer on device 2 thread ended (pid=1836, tid=2129)
Jul 17 10:28:56 hdvdr vdr: [2127] buffer stats: 51136 (1%) used
Jul 17 10:28:56 hdvdr vdr: [2127] receiver on device 2 thread ended (pid=1836, tid=2127)
Jul 17 10:28:56 hdvdr vdr: [2366] receiver on device 2 thread started (pid=1836, tid=2366)
Jul 17 10:28:56 hdvdr vdr: [2367] osdteletext-receiver thread started (pid=1836, tid=2367)
Jul 17 10:28:56 hdvdr vdr: [2368] TS buffer on device 2 thread started (pid=1836, tid=2368)
Jul 17 10:28:57 hdvdr vdr: [1836] [softhddev]SetPlayMode: 1
Jul 17 10:28:57 hdvdr vdr: audio/alsa: using device 'default'
Jul 17 10:28:57 hdvdr vdr: audio/alsa: start delay 336ms
Jul 17 10:28:58 hdvdr vdr: codec: buggy ffmpeg/libav
Jul 17 10:28:58 hdvdr vdr: video: slow down video, duping frame
Jul 17 10:28:58 hdvdr vdr: video/vdpau: missed frame (1/8)
Jul 17 10:28:58 hdvdr vdr: video: slow down video, duping frame
Jul 17 10:28:58 hdvdr vdr: video: 17:45:51.335 +705  393 240/\ms   3 v-buf

Display More

Code

cat /var/log/upstart/xbmc.log
method return sender=:1.58 -> dest=:1.95 reply_serial=2
   int32 250
   string "Remote control disabled"
method return sender=:1.58 -> dest=:1.97 reply_serial=2
   int32 250
   string "Remote control enabled"
method return sender=:1.58 -> dest=:1.101 reply_serial=2
   int32 250
   string "Remote control disabled"
method return sender=:1.58 -> dest=:1.103 reply_serial=2
   int32 250
   string "Remote control enabled"
method return sender=:1.27 -> dest=:1.36 reply_serial=2
   int32 250
   string "Remote control disabled"
method return sender=:1.27 -> dest=:1.38 reply_serial=2
   int32 250
   string "Remote control enabled"
method return sender=:1.42 -> dest=:1.45 reply_serial=2
   int32 250
   string "Remote control disabled"
method return sender=:1.42 -> dest=:1.47 reply_serial=2
   int32 250
   string "Remote control enabled"
method return sender=:1.42 -> dest=:1.51 reply_serial=2
   int32 250
   string "Remote control disabled"
method return sender=:1.42 -> dest=:1.53 reply_serial=2
   int32 250
   string "Remote control enabled"
method return sender=:1.42 -> dest=:1.57 reply_serial=2
   int32 250
   string "Remote control disabled"
method return sender=:1.42 -> dest=:1.59 reply_serial=2
   int32 250
   string "Remote control enabled"
method return sender=:1.12 -> dest=:1.24 reply_serial=2
   int32 250
   string "Remote control disabled"
method return sender=:1.12 -> dest=:1.27 reply_serial=2
   int32 250
   string "Remote control enabled"
method return sender=:1.12 -> dest=:1.31 reply_serial=2
   int32 250
   string "Remote control disabled"
method return sender=:1.12 -> dest=:1.33 reply_serial=2
   int32 250
   string "Remote control enabled"
method return sender=:1.42 -> dest=:1.53 reply_serial=2
   int32 250
   string "Remote control disabled"
method return sender=:1.42 -> dest=:1.55 reply_serial=2
   int32 250
   string "Remote control enabled"
method return sender=:1.16 -> dest=:1.24 reply_serial=2
   int32 250
   string "Remote control disabled"
method return sender=:1.16 -> dest=:1.26 reply_serial=2
   int32 250
   string "Remote control enabled"

Display More

Kann wer damit was anfangen?

MFG SVen

s.krueger · Jul 15th 2012

Hi, all

Nach dem Upgrade auf softhddecvice 0.5.1 läßt sich kein Applikation mehr starten, Bild geht kurz weg und kommt wieder.

Finde in den logs nix dazu, wo kann ich suchen? Was hat sich geändert?

Danke und MFG SVen

s.krueger · Jun 24th 2012

Hi all,

Ich möchte gern vdr-graphlcd-plugin auf meiner Dockstar übersetzen und dazu brauche ich ja graphlcd-base, aber kriege es nicht duch:

Code

g++ -g -O2 -Wall -Woverloaded-virtual -fPIC  -c -D_GNU_SOURCE -DHAVE_LIBUSB -DHAVE_AX206DPF_EXPERIMENTAL   common.c
g++ -g -O2 -Wall -Woverloaded-virtual -fPIC  -c -D_GNU_SOURCE -DHAVE_LIBUSB -DHAVE_AX206DPF_EXPERIMENTAL   config.c
g++ -g -O2 -Wall -Woverloaded-virtual -fPIC  -c -D_GNU_SOURCE -DHAVE_LIBUSB -DHAVE_AX206DPF_EXPERIMENTAL   driver.c
g++ -g -O2 -Wall -Woverloaded-virtual -fPIC  -c -D_GNU_SOURCE -DHAVE_LIBUSB -DHAVE_AX206DPF_EXPERIMENTAL   drivers.c
g++ -g -O2 -Wall -Woverloaded-virtual -fPIC  -c -D_GNU_SOURCE -DHAVE_LIBUSB -DHAVE_AX206DPF_EXPERIMENTAL   port.c
port.c: In member function ‘void GLCD::cParallelPort::WriteData(unsigned char)’:
port.c:44: error: impossible constraint in ‘asm’
make[2]: *** [port.o] Fehler 1

Dann mir jemand Helfen?

Danke und MFG SVen

/edit

Habs hin bekommen:

Code

@@ -27,21 +27,24 @@
 
 namespace GLCD
 {
-
 static inline int port_in(int port)
 {
 	unsigned char value;
+#ifndef __ARMEL__
 	__asm__ volatile ("inb %1,%0"
                   	: "=a" (value)
                   	: "d" ((unsigned short) port));
+#endif
 	return value;
 }
 
 static inline void port_out(unsigned short int port, unsigned char val)
 {
+#ifndef __ARMEL__
 	__asm__ volatile ("outb %0,%1\n"
                   	:
                   	: "a" (val), "d" (port));
+#endif
 }
 
 cParallelPort::cParallelPort()

Display More

edit/

s.krueger · May 30th 2012

Quote

Ist das wirklich eine yaVDR-0.4pre2 Installation wie in deiner Signatur angegeben? Wer nutzt denn sowas?

ich!?

Ok, werde mal gucken, danke dir erstmal

s.krueger · May 30th 2012

Hi,

Ich mußte leider auf DVB-c Umstellen und nun habe ich das Problem das die FB über COM nicht geht, bzw. muß lircd und vdr via restart neu starten und erst dann geht sie!

Log wenn sie geht:

Quote

May 30 10:29:08 hdvdr lircd-0.8.7[1087]: caught signal
May 30 10:29:08 hdvdr init: lircd main process (1087) killed by TERM signal
May 30 10:29:08 hdvdr init: eventlircd main process (1026) killed by TERM signal
May 30 10:31:11 hdvdr init: lircd2uinput main process (1069) terminated with status 1
May 30 10:31:11 hdvdr init: lircd2uinput main process ended, respawning
May 30 10:31:11 hdvdr init: lircd2uinput main process (1182) terminated with status 1
May 30 10:31:11 hdvdr init: lircd2uinput main process ended, respawning
May 30 10:31:12 hdvdr init: lircd2uinput main process (1265) terminated with status 1
May 30 10:31:12 hdvdr init: lircd2uinput main process ended, respawning
May 30 10:31:12 hdvdr init: lircd2uinput main process (1271) terminated with status 1
May 30 10:31:12 hdvdr init: lircd2uinput main process ended, respawning
May 30 10:31:12 hdvdr init: lircd2uinput main process (1272) terminated with status 1
May 30 10:31:12 hdvdr init: lircd2uinput main process ended, respawning
May 30 10:31:12 hdvdr init: lircd2uinput main process (1273) terminated with status 1
May 30 10:31:12 hdvdr init: lircd2uinput main process ended, respawning
May 30 10:31:12 hdvdr init: lircd2uinput main process (1341) terminated with status 1
May 30 10:31:12 hdvdr init: lircd2uinput main process ended, respawning
May 30 10:31:12 hdvdr init: lircd2uinput main process (1376) terminated with status 1
May 30 10:31:12 hdvdr init: lircd2uinput main process ended, respawning
May 30 10:31:12 hdvdr init: lircd2uinput main process (1422) terminated with status 1
May 30 10:31:12 hdvdr init: lircd2uinput main process ended, respawning
May 30 10:31:12 hdvdr init: lircd2uinput main process (1424) terminated with status 1
May 30 10:31:12 hdvdr init: lircd2uinput main process ended, respawning
May 30 10:31:12 hdvdr lircd-0.8.7[1058]: garbage after 'name' token in line 17 ignored
May 30 10:31:12 hdvdr lircd-0.8.7[1058]: lircd(default) ready, using /var/run/lirc/lircd.1058
May 30 10:31:12 hdvdr lircd-0.8.7[1058]: accepted new client on /var/run/lirc/lircd.1058
May 30 10:31:12 hdvdr kernel: [ 34.739338] input: lircd as /devices/virtual/input/input5

Display More

wenn sie nicht geht:

Quote

May 30 11:03:05 hdvdr lircd-0.8.7[1058]: removed client
May 30 11:03:05 hdvdr init: lircd2uinput main process (1425) killed by TERM signal
May 30 11:03:05 hdvdr lircd-0.8.7[1058]: caught signal
May 30 11:03:05 hdvdr init: lircd main process (1058) killed by TERM signal
May 30 11:03:05 hdvdr init: eventlircd main process (1001) killed by TERM signal
May 30 11:04:03 hdvdr init: lircd2uinput main process (1137) terminated with status 1
May 30 11:04:03 hdvdr init: lircd2uinput main process ended, respawning
May 30 11:04:04 hdvdr init: lircd2uinput main process (1299) terminated with status 1
May 30 11:04:04 hdvdr init: lircd2uinput main process ended, respawning
May 30 11:04:04 hdvdr init: lircd2uinput main process (1423) terminated with status 1
May 30 11:04:04 hdvdr init: lircd2uinput main process ended, respawning
May 30 11:04:04 hdvdr init: lircd2uinput main process (1470) terminated with status 1
May 30 11:04:04 hdvdr init: lircd2uinput main process ended, respawning
May 30 11:04:04 hdvdr init: lircd2uinput main process (1476) terminated with status 1
May 30 11:04:04 hdvdr init: lircd2uinput main process ended, respawning
May 30 11:04:04 hdvdr init: lircd2uinput main process (1497) terminated with status 1
May 30 11:04:04 hdvdr init: lircd2uinput main process ended, respawning
May 30 11:04:04 hdvdr init: lircd2uinput main process (1526) terminated with status 1
May 30 11:04:04 hdvdr init: lircd2uinput main process ended, respawning
May 30 11:04:04 hdvdr init: lircd2uinput main process (1533) terminated with status 1
May 30 11:04:04 hdvdr init: lircd2uinput main process ended, respawning
May 30 11:04:04 hdvdr init: lircd2uinput main process (1535) terminated with status 1
May 30 11:04:04 hdvdr init: lircd2uinput main process ended, respawning
May 30 11:04:04 hdvdr init: lircd2uinput main process (1540) terminated with status 1
May 30 11:04:04 hdvdr init: lircd2uinput main process ended, respawning
May 30 11:04:04 hdvdr init: lircd2uinput main process (1555) terminated with status 1
May 30 11:04:04 hdvdr init: lircd2uinput respawning too fast, stopped
May 30 11:04:04 hdvdr lircd-0.8.7[1050]: garbage after 'name' token in line 17 ignored
May 30 11:04:04 hdvdr lircd-0.8.7[1050]: lircd(default) ready, using /var/run/lirc/lircd.1050

Display More

irw zeigt auch nix an!

Was sich geändert hat, habe eine TT-Budget C-1501 PCI eingebaut vorher DVB-s siehe Sig

Wonach kann ich suchen!!

MFG SVen

s.krueger · Mar 8th 2012

Hi,

Danke für deine Antwort.
Du wirst es nicht glauben, mit der neuen Version hier geht es nun auf einmal! Ka. ob es daran liegt, oder ob es daran liegt das ich nur eine neuinstall auf dem Handy gemacht habe... aber nun läuft es habe aber alles genau so eingestellt wie vorher... egal nu läuft es!!!
Danke für das schöne App!

MFG SVen

s.krueger · Mar 8th 2012

Hallo,

Hm... ich wollte auch mal diese App testen, aber ich bekomme keine Verbindung hin! Wo kann ich suchen?
Mit Telnet von meinem Desktop-PC kann ich mich Verbinden, aber mein SGS-2 Verbindet sich einfach nicht, wie kriege ich raus was los ist?
In den VDR-Logs sehe ich nichts, kein lock, nix!

Danke für Hilfe

MFG SVen

s.krueger · Feb 10th 2012

...möglich! Das Display ist ja auch mehre Stunden an.

Danke dir, MFG SVen

s.krueger · Feb 10th 2012

So hab`s hin bekommen

Hatte noch einen LED-Streifen mit 8x SMD LED und 4 davon (wird von rechts anstrahlt) in reihe geschaltet: nix! musste alle LED parallel schalten, war gar nicht so einfach (alles so winzig) aber nun strahlt das GLCD im neuen Glanz glaube ist heller als original?!? 1900 mcd und 6000 K !

MFG SVen

s.krueger · Feb 10th 2012

Danke. Aber wie soll da eine Überlastung entstanden sein? Ist ja alles Original...

Na ich werde mal schauen ob ich da was anderes gebastelt bekomme.

MFG SVen

s.krueger · Feb 10th 2012

Hallo,

Habe oben genanntes Display, aber mit der Zeit ist eine LED nach der anderen ausgestiegen und jetzt ist es ganz dunkel. Hat einer eine Ahnung was das für LED`s sind die da verbaut sind?

Danke für Hilfe, SVen

s.krueger · Dec 30th 2011

Hi,

Ich habe auch mal das ganze bei mir so eingebaut, aber ich habe sehr oft das wenn ich den VDR einschalte, das die FB nicht reagiert!? starte ich dann in der Konsole eventlircd neu alles i.O. Was kann das sein bzw. wo ist zu suchen?!

MFG SVen

s.krueger · Dec 18th 2011

Danke für deine Hilfe,

Also damit scheint es zu gehen, hab den VDR neu gebootet und siehe da, der Tuner funzt! Ist das normal der der Tuner nun das erste dev ist? Und kann ich im Log sehen das dynamite 10 sec wartet? Kann ich im log nicht sehen...

MFG SVen

/edit

zu früh gefreut, nochmal Neustart zum Test, funzt wieder nicht Das Problem muß denke ich im Treiber gelöst werden, so hat das glaube ich keinen Sinn.
Und außerdem muß die Box oft vom Strom getrennt werden weil meist bei Rechnerneustart i2c-Fehler auftreten, macht keinen Spass!

edit/

s.krueger · Dec 18th 2011

Danke für deine Nachsicht

Ok hier also:

Code

udevadm info --query=all --name=/dev/dvb/adapter2/frontend0 --attribute-walk


Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.


  looking at device '/devices/pci0000:00/0000:00:04.1/usb2/2-2/dvb/dvb2.frontend0':
	KERNEL=="dvb2.frontend0"
	SUBSYSTEM=="dvb"
	DRIVER==""


  looking at parent device '/devices/pci0000:00/0000:00:04.1/usb2/2-2':
	KERNELS=="2-2"
	SUBSYSTEMS=="usb"
	DRIVERS=="usb"
	ATTRS{configuration}=="Def"
	ATTRS{bNumInterfaces}==" 1"
	ATTRS{bConfigurationValue}=="1"
	ATTRS{bmAttributes}=="80"
	ATTRS{bMaxPower}=="500mA"
	ATTRS{urbnum}=="741"
	ATTRS{idVendor}=="0ccd"
	ATTRS{idProduct}=="00a8"
	ATTRS{bcdDevice}=="0000"
	ATTRS{bDeviceClass}=="00"
	ATTRS{bDeviceSubClass}=="00"
	ATTRS{bDeviceProtocol}=="00"
	ATTRS{bNumConfigurations}=="1"
	ATTRS{bMaxPacketSize0}=="64"
	ATTRS{speed}=="480"
	ATTRS{busnum}=="2"
	ATTRS{devnum}=="3"
	ATTRS{devpath}=="2"
	ATTRS{version}==" 2.00"
	ATTRS{maxchild}=="0"
	ATTRS{quirks}=="0x0"
	ATTRS{avoid_reset_quirk}=="0"
	ATTRS{authorized}=="1"
	ATTRS{manufacturer}=="Max"
	ATTRS{product}=="USB Stick"
	ATTRS{serial}=="080116"


  looking at parent device '/devices/pci0000:00/0000:00:04.1/usb2':
	KERNELS=="usb2"
	SUBSYSTEMS=="usb"
	DRIVERS=="usb"
	ATTRS{configuration}==""
	ATTRS{bNumInterfaces}==" 1"
	ATTRS{bConfigurationValue}=="1"
	ATTRS{bmAttributes}=="e0"
	ATTRS{bMaxPower}=="  0mA"
	ATTRS{urbnum}=="91"
	ATTRS{idVendor}=="1d6b"
	ATTRS{idProduct}=="0002"
	ATTRS{bcdDevice}=="0206"
	ATTRS{bDeviceClass}=="09"
	ATTRS{bDeviceSubClass}=="00"
	ATTRS{bDeviceProtocol}=="00"
	ATTRS{bNumConfigurations}=="1"
	ATTRS{bMaxPacketSize0}=="64"
	ATTRS{speed}=="480"
	ATTRS{busnum}=="2"
	ATTRS{devnum}=="1"
	ATTRS{devpath}=="0"
	ATTRS{version}==" 2.00"
	ATTRS{maxchild}=="6"
	ATTRS{quirks}=="0x0"
	ATTRS{avoid_reset_quirk}=="0"
	ATTRS{authorized}=="1"
	ATTRS{manufacturer}=="Linux 2.6.38-13-generic ehci_hcd"
	ATTRS{product}=="EHCI Host Controller"
	ATTRS{serial}=="0000:00:04.1"
	ATTRS{authorized_default}=="1"


  looking at parent device '/devices/pci0000:00/0000:00:04.1':
	KERNELS=="0000:00:04.1"
	SUBSYSTEMS=="pci"
	DRIVERS=="ehci_hcd"
	ATTRS{vendor}=="0x10de"
	ATTRS{device}=="0x077e"
	ATTRS{subsystem_vendor}=="0x1043"
	ATTRS{subsystem_device}=="0x82e2"
	ATTRS{class}=="0x0c0320"
	ATTRS{irq}=="21"
	ATTRS{local_cpus}=="00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000003"
	ATTRS{local_cpulist}=="0-1"
	ATTRS{numa_node}=="0"
	ATTRS{dma_mask_bits}=="32"
	ATTRS{consistent_dma_mask_bits}=="32"
	ATTRS{enable}=="1"
	ATTRS{broken_parity_status}=="0"
	ATTRS{msi_bus}==""
	ATTRS{companion}==""


  looking at parent device '/devices/pci0000:00':
	KERNELS=="pci0000:00"
	SUBSYSTEMS==""
	DRIVERS==""

Display More

Und ja ich habe die anderen Variablen schon raus genommen!

Danke und MFG SVen

s.krueger · Dec 18th 2011

Hi, mini73

Danke für deine Antwort, also ich habe mal die udev-Regel aus der Readme genommen und mal unverändert eine Regel erstellt und raus gekommen ist:

Code

udevadm info --query=all --name=/dev/dvb/adapter2/frontend0
P: /devices/pci0000:00/0000:00:04.1/usb2/2-2/dvb/dvb2.frontend0
N: dvb/adapter2/frontend0
E: UDEV_LOG=3
E: DEVPATH=/devices/pci0000:00/0000:00:04.1/usb2/2-2/dvb/dvb2.frontend0
E: MAJOR=212
E: MINOR=11
E: DEVNAME=/dev/dvb/adapter2/frontend0
E: DVB_ADAPTER_NUM=2
E: DVB_DEVICE_TYPE=frontend
E: DVB_DEVICE_NUM=0
E: SUBSYSTEM=dvb
E: dynamite_attach=yes
E: dynamite_attach_delay=10
E: dynamite_instanceid=0
E: dynamite_cardindex=5
E: dynamite_timeout=10
E: dynamite_timeout_handler_arg=dvb2.frontend0
E: dynamite_disable_autoidle=no
E: ID_PATH=pci-0000:00:04.1
E: DVBMODULE=dvb_usb_dw2102
E: TAGS=:udev-acl:

Display More

und dmesg zeigt:

Code

[ 9302.350088] usb 2-2: new high speed USB device using ehci_hcd and address 3
[ 9302.576069] dw2102: su3000_identify_state
[ 9302.576073] 
[ 9302.576079] dvb-usb: found a 'Terratec Cinergy S2 USB HD' in warm state.
[ 9302.576099] dw2102: su3000_power_ctrl: 1, initialized 0
[ 9302.576102] 
[ 9302.576526] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 9302.577697] DVB: registering new adapter (Terratec Cinergy S2 USB HD)
[ 9302.578976] 00 00 00 00 00 00 
[ 9302.579756] 00 af 00 00 00 00 
[ 9302.580523] 00 af 78 00 00 00 
[ 9302.581233] 00 af 78 66 00 00 
[ 9302.582012] 00 af 78 66 49 00 
[ 9302.582749] 00 af 78 66 49 84 
[ 9302.582763] dvb-usb: MAC address: 00:af:78:66:49:84
[ 9302.620105] DS3000 chip version: 0.192 attached.
[ 9302.620113] dw2102: Attached DS3000!
[ 9302.620116] 
[ 9302.620125] DVB: registering adapter 2 frontend 0 (Montage Technology DS3000/TS2020)...
[ 9302.621408] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:04.1/usb2/2-2/input/input5
[ 9302.621547] dvb-usb: schedule remote query interval to 150 msecs.
[ 9302.621556] dw2102: su3000_power_ctrl: 0, initialized 1
[ 9302.621559] 
[ 9302.621563] dvb-usb: Terratec Cinergy S2 USB HD successfully initialized and connected.
[ 9302.621606] usbcore: registered new interface driver dw2102
[ 9302.749194] dw2102: su3000_power_ctrl: 1, initialized 1
[ 9302.749198] 
[ 9302.774653] ds3000_firmware_ondemand: Waiting for firmware upload (dvb-fe-ds3000.fw)...
[ 9302.855119] ds3000_firmware_ondemand: Waiting for firmware upload(2)...

Display More

Schon mal Super, aber kann nicht getunt werden: Kanal nicht verfügbar! Hab ich was falsch gemacht? Bin echt nicht so bewandert in der Materie, hab bitte Nachsicht!

Danke und MFG SVen

/edit

Ich bin zu blöd ich weis nicht was ich hier rein Schreiben soll "(hier fehlt was zur Identifikation)", mal geht die Box beim Hochfahren mal wieder nicht...

edit/

s.krueger · Dec 17th 2011

Hallo,

Hänge mich auch mal mit rein.
Schön das weiter dran gearbeitet wird die zickige USB-Box(en) zum Laufen zu kriegen.

Bin leider nicht so er udev-Experte, wie also sollte so eine Regal aussehen?

Danke und MFG SVen

/edit

hier mal das Log wenn ich die Terratec dazu stecke:

Code

Dec 17 22:02:33 hdvdr kernel: [ 7030.410101] usb 2-2: new high speed USB device using ehci_hcd and address 4
Dec 17 22:02:33 hdvdr kernel: [ 7030.562217] dw2102: su3000_identify_state
Dec 17 22:02:33 hdvdr kernel: [ 7030.562221] 
Dec 17 22:02:33 hdvdr kernel: [ 7030.562227] dvb-usb: found a 'Terratec Cinergy S2 USB HD' in warm state.
Dec 17 22:02:33 hdvdr kernel: [ 7030.562251] dw2102: su3000_power_ctrl: 1, initialized 0
Dec 17 22:02:33 hdvdr kernel: [ 7030.562253] 
Dec 17 22:02:33 hdvdr kernel: [ 7030.562830] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Dec 17 22:02:33 hdvdr kernel: [ 7030.563037] DVB: registering new adapter (Terratec Cinergy S2 USB HD)
Dec 17 22:02:33 hdvdr kernel: [ 7030.563839] 00 00 00 00 00 00 
Dec 17 22:02:33 hdvdr kernel: [ 7030.564588] 00 af 00 00 00 00 
Dec 17 22:02:33 hdvdr kernel: [ 7030.565325] 00 af 78 00 00 00 
Dec 17 22:02:33 hdvdr kernel: [ 7030.566092] 00 af 78 66 00 00 
Dec 17 22:02:33 hdvdr kernel: [ 7030.566914] 00 af 78 66 49 00 
Dec 17 22:02:33 hdvdr kernel: [ 7030.568770] 00 af 78 66 49 84 
Dec 17 22:02:33 hdvdr kernel: [ 7030.568784] dvb-usb: MAC address: 00:af:78:66:49:84
Dec 17 22:02:33 hdvdr kernel: [ 7030.574799] DS3000 chip version: 0.192 attached.
Dec 17 22:02:33 hdvdr kernel: [ 7030.574807] dw2102: Attached DS3000!
Dec 17 22:02:33 hdvdr kernel: [ 7030.574809] 
Dec 17 22:02:33 hdvdr kernel: [ 7030.574818] DVB: registering adapter 2 frontend 0 (Montage Technology DS3000/TS2020)...
Dec 17 22:02:33 hdvdr kernel: [ 7030.575943] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:04.1/usb2/2-2/input/input6
Dec 17 22:02:33 hdvdr kernel: [ 7030.576043] dvb-usb: schedule remote query interval to 150 msecs.
Dec 17 22:02:33 hdvdr kernel: [ 7030.576053] dw2102: su3000_power_ctrl: 0, initialized 1
Dec 17 22:02:33 hdvdr kernel: [ 7030.576055] 
Dec 17 22:02:33 hdvdr kernel: [ 7030.576060] dvb-usb: Terratec Cinergy S2 USB HD successfully initialized and connected.
Dec 17 22:02:33 hdvdr vdr: [3436] dynamite: udev cardindex is (null)
Dec 17 22:02:33 hdvdr vdr: [3436] new sub-device number 3
Dec 17 22:02:33 hdvdr kernel: [ 7030.808885] dw2102: su3000_power_ctrl: 1, initialized 1
Dec 17 22:02:33 hdvdr kernel: [ 7030.808890] 
Dec 17 22:02:33 hdvdr kernel: [ 7030.843837] ds3000_firmware_ondemand: Waiting for firmware upload (dvb-fe-ds3000.fw)...
Dec 17 22:02:33 hdvdr kernel: [ 7030.873743] ds3000_firmware_ondemand: Waiting for firmware upload(2)...
Dec 17 22:02:34 hdvdr vdr: [3436] frontend 2/0 provides DVB-S2 with QPSK ("Montage Technology DS3000/TS2020")
Dec 17 22:02:34 hdvdr vdr: [3436] LNB-sharing: patch version 0.1.4
Dec 17 22:02:34 hdvdr vdr: [3436] LNB-sharing: setting device 3 to use LNB 3
Dec 17 22:02:34 hdvdr vdr: [3436] Device 3: will send signals (like 22kHz) to LNB nr. = -3 
Dec 17 22:02:34 hdvdr vdr: [3848] section handler thread started (pid=3436, tid=3848)
Dec 17 22:02:34 hdvdr vdr: [3847] tuner on frontend 2/0 thread started (pid=3436, tid=3847)
Dec 17 22:02:37 hdvdr vdr: [3436] dynamite: attached device /dev/dvb/adapter2/frontend0 to dynamic device slot 3
Dec 17 22:02:37 hdvdr vdr: [3436] dynamite: usb remove monitor: add syspath /sys/devices/pci0000:00/0000:00:04.1/usb2/2-2
Dec 17 22:02:37 hdvdr vdr: [3436] max. latency time 5 seconds
Dec 17 22:02:37 hdvdr vdr: [3436] info: attached /dev/dvb/adapter2/frontend0
Dec 17 22:02:37 hdvdr vdr: [3850] dynamite udev monitor for subsystem (null) thread started (pid=3436, tid=3850)
Dec 17 22:02:37 hdvdr vdr: [3851] Text2Skin: message display update thread started (pid=3436, tid=3851)

Display More

Allerdings liefert die Terratec kein Signal:

Code

Dec 17 22:10:29 hdvdr vdr: [3436] switching to channel 8
Dec 17 22:10:30 hdvdr vdr: [3909] receiver on device 3 thread started (pid=3436, tid=3909)
Dec 17 22:10:30 hdvdr vdr: [3910] TS buffer on device 3 thread started (pid=3436, tid=3910)
Dec 17 22:10:30 hdvdr vdr: [3908] osdteletext-receiver thread ended (pid=3436, tid=3908)
Dec 17 22:10:30 hdvdr vdr: [3436] buffer stats: 0 (0%) used

Erst wenn VDR nochmals neu gestartet wird, wie schon gehabt geht sie erst...

edit/

s.krueger · Oct 21st 2011

Gleiches Verhalten auch bei mir mit pre2. Habe erst die Tage neu install und bin noch nicht ganz durch mit Anpassungen und wollte später schauen was da los ist, aber nun sehe ich, ich bin nicht allein!

MFG SVen

s.krueger · Oct 19th 2011

Hm... Jungs wie muß die udev-Regel ausehen, wenn ich die Box einen Bestimmten Adapter zuordnen will!?

Code

KERNEL=="dvb*", DRIVERS=="dvb_usb_dw2102", PROGRAM="/bin/sh -c 'K=%k; K=$${K#dvb}; printf dvb/adapter3/%%s $${K#*.}", NAME="%c"

oder

Code

SUBSYSTEM=="dvb", ATTR{idProduct}=="0x0ccd", ATTR{idVendor}=="0x00a8", PROGRAM="/bin/sh -c 'K=%k; K=$${K#dvb}; printf dvb/adapter3/%%s $${K#*.}'", NAME="%c"

Nix vom dem geht!!!! Was mache ich falsch

hier mal udevinfo:

Code

udevadm info -a -p $(udevadm info -q path -n /dev/dvb/adapter1/frontend0) 


Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.


  looking at device '/devices/pci0000:00/0000:00:04.1/usb2/2-2/dvb/dvb1.frontend0':
	KERNEL=="dvb1.frontend0"
	SUBSYSTEM=="dvb"
	DRIVER==""


  looking at parent device '/devices/pci0000:00/0000:00:04.1/usb2/2-2':
	KERNELS=="2-2"
	SUBSYSTEMS=="usb"
	DRIVERS=="usb"
	ATTRS{configuration}=="Def"
	ATTRS{bNumInterfaces}==" 1"
	ATTRS{bConfigurationValue}=="1"
	ATTRS{bmAttributes}=="80"
	ATTRS{bMaxPower}=="500mA"
	ATTRS{urbnum}=="3817"
	ATTRS{idVendor}=="0ccd"
	ATTRS{idProduct}=="00a8"
	ATTRS{bcdDevice}=="0000"
	ATTRS{bDeviceClass}=="00"
	ATTRS{bDeviceSubClass}=="00"
	ATTRS{bDeviceProtocol}=="00"
	ATTRS{bNumConfigurations}=="1"
	ATTRS{bMaxPacketSize0}=="64"
	ATTRS{speed}=="480"
	ATTRS{busnum}=="2"
	ATTRS{devnum}=="5"
	ATTRS{devpath}=="2"
	ATTRS{version}==" 2.00"
	ATTRS{maxchild}=="0"
	ATTRS{quirks}=="0x0"
	ATTRS{avoid_reset_quirk}=="0"
	ATTRS{authorized}=="1"
	ATTRS{manufacturer}=="Max"
	ATTRS{product}=="USB Stick"
	ATTRS{serial}=="080116"


  looking at parent device '/devices/pci0000:00/0000:00:04.1/usb2':
	KERNELS=="usb2"
	SUBSYSTEMS=="usb"
	DRIVERS=="usb"
	ATTRS{configuration}==""
	ATTRS{bNumInterfaces}==" 1"
	ATTRS{bConfigurationValue}=="1"
	ATTRS{bmAttributes}=="e0"
	ATTRS{bMaxPower}=="  0mA"
	ATTRS{urbnum}=="88"
	ATTRS{idVendor}=="1d6b"
	ATTRS{idProduct}=="0002"
	ATTRS{bcdDevice}=="0206"
	ATTRS{bDeviceClass}=="09"
	ATTRS{bDeviceSubClass}=="00"
	ATTRS{bDeviceProtocol}=="00"
	ATTRS{bNumConfigurations}=="1"
	ATTRS{bMaxPacketSize0}=="64"
	ATTRS{speed}=="480"
	ATTRS{busnum}=="2"
	ATTRS{devnum}=="1"
	ATTRS{devpath}=="0"
	ATTRS{version}==" 2.00"
	ATTRS{maxchild}=="6"
	ATTRS{quirks}=="0x0"
	ATTRS{avoid_reset_quirk}=="0"
	ATTRS{authorized}=="1"
	ATTRS{manufacturer}=="Linux 2.6.38-11-generic ehci_hcd"
	ATTRS{product}=="EHCI Host Controller"
	ATTRS{serial}=="0000:00:04.1"
	ATTRS{authorized_default}=="1"


  looking at parent device '/devices/pci0000:00/0000:00:04.1':
	KERNELS=="0000:00:04.1"
	SUBSYSTEMS=="pci"
	DRIVERS=="ehci_hcd"
	ATTRS{vendor}=="0x10de"
	ATTRS{device}=="0x077e"
	ATTRS{subsystem_vendor}=="0x1043"
	ATTRS{subsystem_device}=="0x82e2"
	ATTRS{class}=="0x0c0320"
	ATTRS{irq}=="21"
	ATTRS{local_cpus}=="00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000003"
	ATTRS{local_cpulist}=="0-1"
	ATTRS{numa_node}=="0"
	ATTRS{dma_mask_bits}=="32"
	ATTRS{consistent_dma_mask_bits}=="32"
	ATTRS{enable}=="1"
	ATTRS{broken_parity_status}=="0"
	ATTRS{msi_bus}==""
	ATTRS{companion}==""


  looking at parent device '/devices/pci0000:00':
	KERNELS=="pci0000:00"
	SUBSYSTEMS==""
	DRIVERS==""

Display More

Danke und MFG SVen

Posts by s.krueger

Fehler ADATA S596 Turbo ata1.00: qc timeout (cmd 0x2f)

Fehler ADATA S596 Turbo ata1.00: qc timeout (cmd 0x2f)

yaVDR 0.5 xbmc, helix usw

yaVDR 0.5 xbmc, helix usw

graphlcd-base und Dockstar Fehler

Fernbedienung geht nicht

Fernbedienung geht nicht

[ANNOUNCE] Android VDR-Manager

[ANNOUNCE] Android VDR-Manager

Beleuchtung Alphacool 240x128

Beleuchtung Alphacool 240x128

Beleuchtung Alphacool 240x128

Beleuchtung Alphacool 240x128

[0.4]XBMC- Einfacher Tastendruck -> Doppelte eingabe

Dynamite Anpassungen für S480 Firmware loading

Dynamite Anpassungen für S480 Firmware loading

Dynamite Anpassungen für S480 Firmware loading

Dynamite Anpassungen für S480 Firmware loading

Aufzeichnung -> Pause -> Play = VDR-Frontend (Xine) restart

Yavdr 0.4-pre2 und Cinergy S2 USB HD Firmware Upload Problem