[opensuse] Errors in messages
I'm getting many of these in /var/log/messages. I have not idea what it is. Can anyone advise? Apr 14 17:30:24 pammie kernel: [409118.786826] [drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero. Apr 14 17:30:51 pammie kernel: [409145.852790] sr 4:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Apr 14 17:30:51 pammie kernel: [409145.852793] sr 4:0:0:0: [sr0] Sense Key : Illegal Request [current] Apr 14 17:30:51 pammie kernel: [409145.852795] sr 4:0:0:0: [sr0] Add. Sense: Illegal mode for this track Apr 14 17:30:51 pammie kernel: [409145.852798] sr 4:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 10 00 00 02 00 Apr 14 17:30:51 pammie kernel: [409145.852802] end_request: I/O error, dev sr0, sector 64 Apr 14 17:30:51 pammie kernel: [409145.852804] Buffer I/O error on device sr0, logical block 16 Apr 14 17:30:51 pammie kernel: [409145.852805] Buffer I/O error on device sr0, logical block 17 Thanks, Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Sun, 15 Apr 2012, Jim Flanagan wrote:
Apr 14 17:30:24 pammie kernel: [409118.786826] [drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero.
No idea.
Apr 14 17:30:51 pammie kernel: [409145.852790] sr 4:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Apr 14 17:30:51 pammie kernel: [409145.852793] sr 4:0:0:0: [sr0] Sense Key : Illegal Request [current] Apr 14 17:30:51 pammie kernel: [409145.852795] sr 4:0:0:0: [sr0] Add. Sense: Illegal mode for this track Apr 14 17:30:51 pammie kernel: [409145.852798] sr 4:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 10 00 00 02 00 Apr 14 17:30:51 pammie kernel: [409145.852802] end_request: I/O error, dev sr0, sector 64 Apr 14 17:30:51 pammie kernel: [409145.852804] Buffer I/O error on device sr0, logical block 16 Apr 14 17:30:51 pammie kernel: [409145.852805] Buffer I/O error on device sr0, logical block 17
Defective CD/DVD, possibly due to a copy protection scheme. HTH, -dnh -- 125: Backup Niemand will Backup. Alle wollen Restore. (Kristian Köhntopp zitiert einen Vertriebler) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/15/12 9:18 PM, Jim Flanagan wrote:
I'm getting many of these in /var/log/messages. I have not idea what it is. Can anyone advise?
Apr 14 17:30:24 pammie kernel: [409118.786826] [drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero. Apr 14 17:30:51 pammie kernel: [409145.852790] sr 4:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Apr 14 17:30:51 pammie kernel: [409145.852793] sr 4:0:0:0: [sr0] Sense Key : Illegal Request [current] Apr 14 17:30:51 pammie kernel: [409145.852795] sr 4:0:0:0: [sr0] Add. Sense: Illegal mode for this track Apr 14 17:30:51 pammie kernel: [409145.852798] sr 4:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 10 00 00 02 00 Apr 14 17:30:51 pammie kernel: [409145.852802] end_request: I/O error, dev sr0, sector 64 Apr 14 17:30:51 pammie kernel: [409145.852804] Buffer I/O error on device sr0, logical block 16 Apr 14 17:30:51 pammie kernel: [409145.852805] Buffer I/O error on device sr0, logical block 17
Thanks,
Jim F
I forgot to say I'm running opensuse 11.4 with KDE. Pretty much a default install. Any help most appreciated. Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday, April 16, 2012 10:13:34 AM Jim Flanagan wrote:
On 4/15/12 9:18 PM, Jim Flanagan wrote:
I'm getting many of these in /var/log/messages. I have not idea what it is. Can anyone advise?
Apr 14 17:30:24 pammie kernel: [409118.786826] [drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero.
It seems there is a complaint about display backlight needs to be fix it on Power Management Settings. Check your Power Profiles.
Apr 14 17:30:51 pammie kernel: [409145.852790] sr 4:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Apr 14 17:30:51 pammie kernel: [409145.852793] sr 4:0:0:0: [sr0] Sense Key : Illegal Request [current] Apr 14 17:30:51 pammie kernel: [409145.852795] sr 4:0:0:0: [sr0] Add. Sense: Illegal mode for this track Apr 14 17:30:51 pammie kernel: [409145.852798] sr 4:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 10 00 00 02 00 Apr 14 17:30:51 pammie kernel: [409145.852802] end_request: I/O error, dev sr0, sector 64 Apr 14 17:30:51 pammie kernel: [409145.852804] Buffer I/O error on device sr0, logical block 16 Apr 14 17:30:51 pammie kernel: [409145.852805] Buffer I/O error on device sr0, logical block 17
It could be Optical Drive hardware fail. You should identify wich one it is. You could notice the sr0 identification and all complaints related to are pointing to CD or DVD device. In general, you should check for BIOS updates or DVD(CD) firmware updates. Sometimes making those updates could fix those issues.
Thanks,
Jim F
I forgot to say I'm running opensuse 11.4 with KDE. Pretty much a default install.
Any help most appreciated.
Jim F
Just a few comments. It's complaints about hardware fails. Regards, -- Ricardo Chung | Panama Linux Ambassador openSUSE Projects -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/16/12 10:49 AM, Ricardo Chung wrote:
On Monday, April 16, 2012 10:13:34 AM Jim Flanagan wrote:
On 4/15/12 9:18 PM, Jim Flanagan wrote:
I'm getting many of these in /var/log/messages. I have not idea what it is. Can anyone advise?
Apr 14 17:30:24 pammie kernel: [409118.786826] [drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero.
It seems there is a complaint about display backlight needs to be fix it on Power Management Settings. Check your Power Profiles.
Apr 14 17:30:51 pammie kernel: [409145.852790] sr 4:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Apr 14 17:30:51 pammie kernel: [409145.852793] sr 4:0:0:0: [sr0] Sense Key : Illegal Request [current] Apr 14 17:30:51 pammie kernel: [409145.852795] sr 4:0:0:0: [sr0] Add. Sense: Illegal mode for this track Apr 14 17:30:51 pammie kernel: [409145.852798] sr 4:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 10 00 00 02 00 Apr 14 17:30:51 pammie kernel: [409145.852802] end_request: I/O error, dev sr0, sector 64 Apr 14 17:30:51 pammie kernel: [409145.852804] Buffer I/O error on device sr0, logical block 16 Apr 14 17:30:51 pammie kernel: [409145.852805] Buffer I/O error on device sr0, logical block 17
It could be Optical Drive hardware fail. You should identify wich one it is. You could notice the sr0 identification and all complaints related to are pointing to CD or DVD device.
In general, you should check for BIOS updates or DVD(CD) firmware updates. Sometimes making those updates could fix those issues.
Thanks,
Jim F
I forgot to say I'm running opensuse 11.4 with KDE. Pretty much a default install.
Any help most appreciated.
Jim F
Just a few comments. It's complaints about hardware fails.
Regards,
Thanks Ricardo, I had a problem on this box with a different CD/DVD drive. Google turned up many posts saying there was a problem with linux on this particular drive, so I replaced it with a new one. This log is with the new drive installed. I'll look more into this tonight. Thanks, Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 16 Apr 2012 11:46:42 -0500
Jim Flanagan
I had a problem on this box with a different CD/DVD drive. Google turned up many posts saying there was a problem with linux on this particular drive, so I replaced it with a new one. This log is with the new drive installed. I'll look more into this tonight.
Check cable quality and type. I had computer with drives set on cable select so it asked for special cable. Motherboard connector. Sometimes it is buggy onboard chipset. BIOS can be culprit for some problems too. Besides update, check BIOS setup. There are manufacturers that forget that DOS is not the only alternative operating system, and if it is not windows BIOS will consider OS unable to handle hardware and turn off some functionality. Try kernel parameter "acpi_osi=Linux" to tell BIOS that there is OS capable of handling hardware. Last time I was reading about that topic kernel was hiding its name, so it needed above parameter to tell BIOS the truth. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El lun, 16-04-2012 a las 11:46 -0500, Jim Flanagan escribió:
On 4/16/12 10:49 AM, Ricardo Chung wrote:
On Monday, April 16, 2012 10:13:34 AM Jim Flanagan wrote:
On 4/15/12 9:18 PM, Jim Flanagan wrote:
I'm getting many of these in /var/log/messages. I have not idea what it is. Can anyone advise?
Apr 14 17:30:24 pammie kernel: [409118.786826] [drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero.
It seems there is a complaint about display backlight needs to be fix it on Power Management Settings. Check your Power Profiles.
Apr 14 17:30:51 pammie kernel: [409145.852790] sr 4:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Apr 14 17:30:51 pammie kernel: [409145.852793] sr 4:0:0:0: [sr0] Sense Key : Illegal Request [current] Apr 14 17:30:51 pammie kernel: [409145.852795] sr 4:0:0:0: [sr0] Add. Sense: Illegal mode for this track Apr 14 17:30:51 pammie kernel: [409145.852798] sr 4:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 10 00 00 02 00 Apr 14 17:30:51 pammie kernel: [409145.852802] end_request: I/O error, dev sr0, sector 64 Apr 14 17:30:51 pammie kernel: [409145.852804] Buffer I/O error on device sr0, logical block 16 Apr 14 17:30:51 pammie kernel: [409145.852805] Buffer I/O error on device sr0, logical block 17
It could be Optical Drive hardware fail. You should identify wich one it is. You could notice the sr0 identification and all complaints related to are pointing to CD or DVD device.
In general, you should check for BIOS updates or DVD(CD) firmware updates. Sometimes making those updates could fix those issues.
Thanks,
Jim F
I forgot to say I'm running opensuse 11.4 with KDE. Pretty much a default install.
Any help most appreciated.
Jim F
Just a few comments. It's complaints about hardware fails.
Regards,
Thanks Ricardo,
I had a problem on this box with a different CD/DVD drive. Google turned up many posts saying there was a problem with linux on this particular drive, so I replaced it with a new one. This log is with the new drive installed. I'll look more into this tonight.
Thanks,
Jim F
Jim, Any progress or solved it? (CD/DVD drive issue) Rajko mentioned a very relevant points you should check too. (loose cables or bad connectors, etc.) Regards, -- Ricardo Chung | Panama Linux Ambassador openSUSE Projects -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/20/12 9:00 AM, Ricardo Chung wrote:
El lun, 16-04-2012 a las 11:46 -0500, Jim Flanagan escribió:
On 4/16/12 10:49 AM, Ricardo Chung wrote:
On Monday, April 16, 2012 10:13:34 AM Jim Flanagan wrote:
On 4/15/12 9:18 PM, Jim Flanagan wrote:
I'm getting many of these in /var/log/messages. I have not idea what it is. Can anyone advise?
Apr 14 17:30:24 pammie kernel: [409118.786826] [drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero.
It seems there is a complaint about display backlight needs to be fix it on Power Management Settings. Check your Power Profiles.
Apr 14 17:30:51 pammie kernel: [409145.852790] sr 4:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Apr 14 17:30:51 pammie kernel: [409145.852793] sr 4:0:0:0: [sr0] Sense Key : Illegal Request [current] Apr 14 17:30:51 pammie kernel: [409145.852795] sr 4:0:0:0: [sr0] Add. Sense: Illegal mode for this track Apr 14 17:30:51 pammie kernel: [409145.852798] sr 4:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 10 00 00 02 00 Apr 14 17:30:51 pammie kernel: [409145.852802] end_request: I/O error, dev sr0, sector 64 Apr 14 17:30:51 pammie kernel: [409145.852804] Buffer I/O error on device sr0, logical block 16 Apr 14 17:30:51 pammie kernel: [409145.852805] Buffer I/O error on device sr0, logical block 17
It could be Optical Drive hardware fail. You should identify wich one it is. You could notice the sr0 identification and all complaints related to are pointing to CD or DVD device.
In general, you should check for BIOS updates or DVD(CD) firmware updates. Sometimes making those updates could fix those issues.
Thanks,
Jim F
I forgot to say I'm running opensuse 11.4 with KDE. Pretty much a default install.
Any help most appreciated.
Jim F
Just a few comments. It's complaints about hardware fails.
Regards,
Thanks Ricardo,
I had a problem on this box with a different CD/DVD drive. Google turned up many posts saying there was a problem with linux on this particular drive, so I replaced it with a new one. This log is with the new drive installed. I'll look more into this tonight.
Thanks,
Jim F
Jim,
Any progress or solved it? (CD/DVD drive issue)
Rajko mentioned a very relevant points you should check too. (loose cables or bad connectors, etc.)
Regards,
Not yet. I'll do a bios upgrade this weekend. Will revert. Many thanks, Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/20/2012 09:00 AM, Ricardo Chung wrote:
El lun, 16-04-2012 a las 11:46 -0500, Jim Flanagan escribió:
On 4/16/12 10:49 AM, Ricardo Chung wrote:
On Monday, April 16, 2012 10:13:34 AM Jim Flanagan wrote:
On 4/15/12 9:18 PM, Jim Flanagan wrote:
I'm getting many of these in /var/log/messages. I have not idea what it is. Can anyone advise?
Apr 14 17:30:24 pammie kernel: [409118.786826] [drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero. It seems there is a complaint about display backlight needs to be fix it on Power Management Settings. Check your Power Profiles.
Apr 14 17:30:51 pammie kernel: [409145.852790] sr 4:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Apr 14 17:30:51 pammie kernel: [409145.852793] sr 4:0:0:0: [sr0] Sense Key : Illegal Request [current] Apr 14 17:30:51 pammie kernel: [409145.852795] sr 4:0:0:0: [sr0] Add. Sense: Illegal mode for this track Apr 14 17:30:51 pammie kernel: [409145.852798] sr 4:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 10 00 00 02 00 Apr 14 17:30:51 pammie kernel: [409145.852802] end_request: I/O error, dev sr0, sector 64 Apr 14 17:30:51 pammie kernel: [409145.852804] Buffer I/O error on device sr0, logical block 16 Apr 14 17:30:51 pammie kernel: [409145.852805] Buffer I/O error on device sr0, logical block 17 It could be Optical Drive hardware fail. You should identify wich one it is. You could notice the sr0 identification and all complaints related to are pointing to CD or DVD device.
In general, you should check for BIOS updates or DVD(CD) firmware updates. Sometimes making those updates could fix those issues.
Thanks,
Jim F I forgot to say I'm running opensuse 11.4 with KDE. Pretty much a default install.
Any help most appreciated.
Jim F Just a few comments. It's complaints about hardware fails.
Regards,
Thanks Ricardo,
I had a problem on this box with a different CD/DVD drive. Google turned up many posts saying there was a problem with linux on this particular drive, so I replaced it with a new one. This log is with the new drive installed. I'll look more into this tonight.
Thanks,
Jim F Jim,
Any progress or solved it? (CD/DVD drive issue)
Rajko mentioned a very relevant points you should check too. (loose cables or bad connectors, etc.)
Regards,
OK, I updated to the latest BIOS for my mobo. I haven's seen those same exact errors as before, but it's only been a short while. I did the get following after inserting a CD (store bought audio CD). ------- Apr 23 17:21:23 pammie kernel: [ 371.885989] sr 2:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Apr 23 17:21:23 pammie kernel: [ 371.885994] sr 2:0:0:0: [sr0] Sense Key : Illegal Request [current] Apr 23 17:21:23 pammie kernel: [ 371.885998] sr 2:0:0:0: [sr0] Add. Sense: Illegal mode for this track Apr 23 17:21:23 pammie kernel: [ 371.886002] sr 2:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 10 00 00 02 00 Apr 23 17:21:23 pammie kernel: [ 371.886011] end_request: I/O error, dev sr0, sector 64 Apr 23 17:21:30 pammie kernel: [ 379.245683] sr 2:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Apr 23 17:21:30 pammie kernel: [ 379.245689] sr 2:0:0:0: [sr0] Sense Key : Illegal Request [current] Apr 23 17:21:30 pammie kernel: [ 379.245694] sr 2:0:0:0: [sr0] Add. Sense: Illegal mode for this track Apr 23 17:21:30 pammie kernel: [ 379.245699] sr 2:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 10 00 00 02 00 Apr 23 17:21:30 pammie kernel: [ 379.245708] end_request: I/O error, dev sr0, sector 64 Apr 23 17:21:30 pammie kernel: [ 379.245711] quiet_error: 26 callbacks suppressed Apr 23 17:21:30 pammie kernel: [ 379.245714] Buffer I/O error on device sr0, logical block 16 Apr 23 17:21:30 pammie kernel: [ 379.245717] Buffer I/O error on device sr0, logical block 17 ---------- Many of these immediately in a row, maybe 50 or 75 of them. I am seeing this now for smartd --------- Apr 23 19:45:32 pammie smartd[2699]: Device: /dev/sda [SAT], SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 38 to 37 Apr 23 19:45:33 pammie smartd[2699]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 65 to 66 Apr 23 19:45:33 pammie smartd[2699]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 35 to 34 ----------- And some of these for smbd ----------- Apr 23 20:07:06 pammie smbd[10914]: [2012/04/23 20:07:06.054369, 0] lib/util_sock.c:1441(get_peer_addr_internal) Apr 23 20:07:06 pammie smbd[10914]: getpeername failed. Error was Transport endpoint is not connected Apr 23 20:07:06 pammie smbd[10914]: read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. ----------- Thanks for any more feedback. Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-24 03:24, Jim Flanagan wrote:
I am seeing this now for smartd
--------- Apr 23 19:45:32 pammie smartd[2699]: Device: /dev/sda [SAT], SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 38 to 37 Apr 23 19:45:33 pammie smartd[2699]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 65 to 66 Apr 23 19:45:33 pammie smartd[2699]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 35 to 34 -----------
These are typical if you have seagate disks. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk+WS5UACgkQIvFNjefEBxpRnACgiJjKdrTh8vCpFDxHTWQ6+a2b 84UAn3KlpVZ0VGvXk+Gg3NMfdNmWrO2S =ACJW -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Tue, 24 Apr 2012, Carlos E. R. wrote:
On 2012-04-24 03:24, Jim Flanagan wrote:
Apr 23 19:45:32 pammie smartd[2699]: Device: /dev/sda [SAT], SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 38 to 37 Apr 23 19:45:33 pammie smartd[2699]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 65 to 66 Apr 23 19:45:33 pammie smartd[2699]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 35 to 34
These are typical if you have seagate disks.
Ignore those temperature parameters (but keep an eye on temps with hddtemp and e.g. gkrellm): Make this your first line in /etc/smartd.conf or add the -I parameters to your own entries: DEVICESCAN -a -d removable -I 194 -I 190 -I 231 -I 9 -I 240 -I 241 -I 242 -T permissive The last 3 are Seagate specific, AFAIK (real Seagates, probably not yet the relabeled Samsungs like this one sold as Seagate Barracuda Green). Real chaos on that label: [Spinpoint logo] http://www.seagate.com Barracuda Green [Barcode and Serial no] Model: ST2000DL004 P/N: HD204UI [size etc] SAMSUNG [very small: Seagate Technology LLC] [..] STX BarracudaLP(B) Product of China That one probably still exhibits the Samsungs specific SMART-Attributes... HTH, -dnh -- Staaaar Trekin', across the universe on the starship Enterprise, under Captain Kirk! Staaaar Trekin', across the universe. Boldly going forward, 'cause we can't find rerverse. -- Angels 2200 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-28 04:08, David Haller wrote:
DEVICESCAN -a -d removable -I 194 -I 190 -I 231 -I 9 -I 240 -I 241 -I 242 -T permissive
Try something like -I 194 -W 4,45,55 better. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk+bt/IACgkQIvFNjefEBxqaVwCfXLkVwDIJ/B7EtRKHvATFsrrC gXoAnjgf/oubjLg28lqONmqjTMbPuHoO =qPIR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Sat, 28 Apr 2012, Carlos E. R. wrote:
On 2012-04-28 04:08, David Haller wrote:
DEVICESCAN -a -d removable -I 194 -I 190 -I 231 -I 9 -I 240 -I 241 -I 242 -T permissive
Try something like -I 194 -W 4,45,55 better.
You'd have to do that -W for the other attributes too, and also adjust temperatures according to the disk (some e.g. Samsungs generally report lower temperatures, others (e.g. Seagate, WD) higher). As I mentioned: I ignore that stuff in smartd, but watch temperatures with hddtemp and gkrellm and have set alarms to beep, e.g.: warn command: beep -f 1200 -r 1 -l 150 alarm command: beep -f 1200 -r 3 -l 150 As software.o.o is broken ATM, and osc doesn't find anything, I don't know if and where 'beep' is in the distro. I'll push the package to my home repo if I don't find it elsewhere in OBS/Packman. BTW: I generally use the beeper quite a lot. A low long beep[1] notifies me of long running background jobs being done (e.g. video encoding), a long normal beep[2][3] of finished downloads, and high beeps (see above) of "alarms" ;) Those beeps get through no matter how loud/muted pcm or whatever is, no matter what other sound stuff is doing. Which is the main reason for me using them as alarms etc. You need to activate that though via kernel cmdline: pcsp=enable=1 and you need to 'modprobe pcspkr' (e.g. MODULES_LOADED_ON_BOOT). -dnh, remembering game _music_ played on that beeper ;) [1] beep -f 260 -l 800 [2] beep -l 600 [3] default beep from beep is eq. to 'beep -l 200 -f 440', default beep (c.f. printf '\a' >/dev/tty12) seems to be approx. 'beep -l 100 -f 751'. -- I'm extremely disappointed. I send you out for exciting, new designer drugs, you come back with tomato sauce. -- Dr. House -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2012-05-01 at 15:24 +0200, David Haller wrote:
BTW: I generally use the beeper quite a lot. A low long beep[1] notifies me of long running background jobs being done (e.g. video
I use spoken messages for that :-)
encoding), a long normal beep[2][3] of finished downloads, and high beeps (see above) of "alarms" ;) Those beeps get through no matter how loud/muted pcm or whatever is, no matter what other sound stuff is doing. Which is the main reason for me using them as alarms etc.
Ah, I see. Well, with pulse sounds mix.
-dnh, remembering game _music_ played on that beeper ;)
Oh, yes, even voices. The game "the abady" had voices. http://en.wikipedia.org/wiki/La_Abad%C3%ADa_del_Crimen (search for "Ave Maria") Access to the beeper in Linux is more difficult. It needs a terminal. I remember I wrote a routine in turbopascal that played music in background using the timer interrupt, at the same time the program was running its busines.
[1] beep -f 260 -l 800 [2] beep -l 600 [3] default beep from beep is eq. to 'beep -l 200 -f 440', default beep (c.f. printf '\a' >/dev/tty12) seems to be approx. 'beep -l 100 -f 751'.
Mmmm. - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk+gfT0ACgkQtTMYHG2NR9WqSACfRApFtjIMD77vXxW3gZ0r6f/B xa8AnRT30jlBFtxbMWkMEstp9QPHbNer =RRSV -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Wed, 02 May 2012, Carlos E. R. wrote:
encoding), a long normal beep[2][3] of finished downloads, and high beeps (see above) of "alarms" ;) Those beeps get through no matter how loud/muted pcm or whatever is, no matter what other sound stuff is doing. Which is the main reason for me using them as alarms etc.
Ah, I see. Well, with pulse sounds mix.
It does too with plain alsa. But it depends on mixer settings (e.g. mute the master, cause your making a call etc...)
Access to the beeper in Linux is more difficult. It needs a terminal.
beep uses /dev/console (which is why it's suid root). I think I should patch it to use /dev/tty12 or so. $ printf '\a' >/dev/console bash: /dev/console: Permission denied $ printf '\a' >/dev/tty12 [beeps]
I remember I wrote a routine in turbopascal that played music in background using the timer interrupt, at the same time the program was running its busines.
*g* -dnh -- "Stef, if you were any stupider you'd be on life support." -- Miranda on userfriendly -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-16 17:49, Ricardo Chung wrote:
On Monday, April 16, 2012 10:13:34 AM Jim Flanagan wrote:
On 4/15/12 9:18 PM, Jim Flanagan wrote:
I'm getting many of these in /var/log/messages. I have not idea what it is. Can anyone advise?
Apr 14 17:30:24 pammie kernel: [409118.786826] [drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero.
It seems there is a complaint about display backlight needs to be fix it on Power Management Settings. Check your Power Profiles.
No, that's a notice to remind developers of Intel hardware that _they_ have to fix something in the code. Not for us. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk+PC4sACgkQIvFNjefEBxraVQCgxRMr6hHyxxS/NeybhoPJYZPc KnMAn2iWfaDid+7s7xtOIeUb9hVsuVPh =47LP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Carlos E. R. -
David Haller -
Jim Flanagan -
Rajko M. -
Ricardo Chung