On Thu, 2007-07-12 at 09:05 +0200, LLLActive@GMX.Net wrote:
On Wed, 2007-07-11 at 22:09 -0500, Stevens wrote:
On Wednesday 11 July 2007 21:12, Patrick Shanahan wrote:
* LLLActive@GMX.Net
[07-11-07 17:41]: What is the best way to set the timeout to 120 permanently at boot-up as is done with echo 120 > /sys/block/sda/device/timeout manually?
??? add the line "echo 120 > /sys/block/sda/device/timeout" to /etc/init.d/boot.local ???
The problem that I have with this line of logic is that I have no "sda" in /sys/block until AFTER I plug in my flash drive, therefore adding a line in boot.local that references "sda" won't do anything except generate an error message (or nothing at all) if there is no flash drive present at boot, which is the case here.
I would think that the same process that detects the flash drive and adds the "sda" directory should also add the proper timeout value.
Fred
Makes sense. Could you help out with which process could be used? I know that USB at plugin calls klauncher. How can klauncher's start be enhanced to add the timeout value. Is there a process that starts before klauncher that detects USB?
:-) Al
I have fortunately got a USB mouse at bootup time. Then Patrick's suggestion does seem to work for me now, perhaps because the SCSI part is loaded then. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ BUT, alas, the one newer system froze up again a few times this week. I could not find any evidence or a RO FS, but KDE was completely locked. The /sys/block/sda/device/timeout is 120, but the problem is with hdb mounted as a DVD Burner with a burnt DVD ISO from OpenSUSE (10.2 x86_64). I logged in per ssh on the frozen system and had a look at the system messages, disk space and mount points: ######################################## SAW1:~ #tail -f -n50 /var/logs/messages ... Jul 19 08:27:01 SAW1 kernel: hdb: packet command error: status=0x51 { DriveReady SeekComplete Error } Jul 19 08:27:01 SAW1 kernel: hdb: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 } Jul 19 08:27:01 SAW1 kernel: ide: failed opcode was: unknown Jul 19 08:27:01 SAW1 kernel: ATAPI device hdb: Jul 19 08:27:01 SAW1 kernel: Error: Illegal request -- (Sense key=0x05) Jul 19 08:27:01 SAW1 kernel: Cannot read medium - incompatible format -- (asc=0x30, ascq=0x02) Jul 19 08:27:01 SAW1 kernel: The failed "Read Subchannel" packet command was: Jul 19 08:27:01 SAW1 kernel: "42 02 40 01 00 00 00 00 10 00 00 00 00 00 00 00 " .... Jul 19 08:40:13 SAW1 sshd[28885]: Accepted keyboard-interactive/pam for root from 192.178.111.75 port 15326 ssh2 ... SAW1:~ # mount /dev/sdc5 on / type ext3 (rw,acl,user_xattr) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) debugfs on /sys/kernel/debug type debugfs (rw) udev on /dev type tmpfs (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/sdb3 on /home type reiserfs (rw) /dev/sdc6 on /home/rls/Data/Data1 type reiserfs (rw) /dev/sdb4 on /home/rls/Data/Data2 type reiserfs (rw) /dev/sda4 on /home/rls/Data/Data3 type reiserfs (rw) /dev/sda3 on /home/rls/Old-OSs/SL10.1 type xfs (rw) securityfs on /sys/kernel/security type securityfs (rw) nfsd on /proc/fs/nfsd type nfsd (rw) /dev/hdb on /media/SU1020.001 type iso9660 (ro,nosuid,nodev,noatime,uid=1000,utf8) SAW1:~ # df -h Filesystem Size Used Avail Use% Mounted on /dev/sdc5 15G 9.9G 4.2G 71% / udev 1.5G 156K 1.5G 1% /dev /dev/sdb3 31G 20G 11G 67% /home /dev/sdc6 264G 149G 115G 57% /home/rls/Data/Data1 /dev/sdb4 202G 135G 68G 67% /home/rls/Data/Data2 /dev/sda4 211G 153G 58G 73% /home/rls/Data/Data3 /dev/sda3 20G 16G 4.1G 80% /home/rls/Old-OSs/SL10.1 /dev/hdb 3.7G 3.7G 0 100% /media/SU1020.001 SAW1:~ # ####################################### The DVD is the current openSUSE 10.2 GM DVD x86_64 burnt ISO, in /dev/hdb (ATAPI device). Is it a DVD disk error or a DVD Drive error? It is the original installation DVD I used to install 10.2 on this machine. Why does it lock down KDE? I did not access the DVD at all; I wanted to save an OpenOffice 2.2.1 (Build 2.2.0.2) Writer file to HD (/dev/sdc6 - /home/rls/Data/Data1). It also happened with OOo-Writer version 2.2.0 yesterday. Any ideas? :-) Al -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org