March 2001 - openSUSE Users - openSUSE Mailing Lists

CDRW stopped working with kernel 2.4.2
by Alex Daniloff 22 Mar '01

22 Mar '01

Hello SuSE folkz, After upgrading to kernel 2.4.2 my IDE CD writer Memorex CRW-1622 stopped working. It's emulated as a SCSI device /dev/sr1 on my Linux SuSE7.1 box. It was working OK with kernel 2.2.18 and XCDRoast which came with this distro. The simptoms are: It writes 9% of the the track and after that just infinitely keeps resetting SCSI bus. So I have to reboot the whole system to free my CDRW. I have onboard Adaptec AIC-7890 SCSI adapter. I'm including output from XCDRoast program. Could somebody tell me please how to fix this issue. Thanks in advance. Alex pregap1: -1 Cdrecord 1.9 (i686-suse-linux) Copyright (C) 1995-2000 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '1,1,0' scsibus: 1 target: 1 lun: 0 Linux sg driver version: 3.1.17 Using libscg version 'schily-0.1' atapi: 1 Device type : Removable CD-ROM Version : 0 Response Format: 1 Vendor_info : 'Memorex ' Identifikation : 'CRW-1622 ' Revision : 'D3.9' Device seems to be: Generic mmc CD-RW. Using generic SCSI-3/mmc CD-R driver (mmc_cdr). Driver flags : SWABAUDIO Drive buf size : 786432 = 768 KB FIFO size : 2097152 = 2048 KB Track 01: data 76 MB Total size: 87 MB (08:39.74) = 38981 sectors Lout start: 87 MB (08:41/56) = 38981 sectors Current Secsize: 2048 ATIP start of lead in: -11637 (97:26/63) ATIP start of lead out: 337350 (75:00/00) Disk type: Phase change Manuf. index: 3 Manufacturer: CMC Magnetics Corporation Blocks total: 337350 Blocks current: 337350 Blocks remaining: 298369 Starting to write CD/DVD at speed 2 in write mode for single session. Waiting for reader process to fill input buffer ... input buffer ready. Performing OPC... Starting new track at sector: 0 CDB: 2A 00 00 00 05 92 00 00 1F 00 cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error status: 0x0 (GOOD STATUS) cdrecord: Input/output error. request_sense: scsi sendcmd: retryable error write track data: error after 2920448 bytes status: 0x2 (CHECK CONDITION) CDB: 03 00 00 00 12 00 cdrecord: Input/output error. flush cache: scsi sendcmd: retryable error Sense Bytes: 00 00 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Key: 0xFFFFFFFF [], Segment 0 cdrecord: Input/output error. close track/session: scsi sendcmd: retryable error Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 status: 0x2 (CHECK CONDITION) Sense flags: Blk 0 (not valid) cdrecord: Input/output error. test unit ready: scsi sendcmd: retryable error cmd finished after 3.187s timeout 40s status: 0x2 (CHECK CONDITION) CDB: 35 00 00 00 00 00 00 00 00 00 cdrecord: Input/output error. test unit ready: scsi sendcmd: retryable error Sense Bytes: 00 00 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Key: 0xFFFFFFFF [], Segment 0 cdrecord: Input/output error. test unit ready: scsi sendcmd: retryable error Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 status: 0x2 (CHECK CONDITION) Sense flags: Blk 0 (not valid) cmd finished after 1.997s timeout 120s Trouble flushing the cache Writing time: 66.125s Fixating... CDB: 5B 00 02 00 00 00 00 00 00 00 Sense Bytes: 00 00 00 00 00 00 00 00 Sense Key: 0xFFFFFFFF [], Segment 0 Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 1.999s timeout 480s CDB: 00 00 00 00 00 00 Sense Bytes: 00 00 00 00 00 00 00 00 Sense Key: 0xFFFFFFFF [], Segment 0 Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 1.997s timeout 40s -- MS Windows users should be covered under the Americans with Disabilities Act! --------------> Try Linux and you'll understand why <--------------

2 1

Re: ADSL: so close, yet so far...
by mhf 22 Mar '01

22 Mar '01

Nick the results of the suggested ping tests are shown below. My Linux distro. is Suse 7.0. What's up with the 20%/30% packet loss? Thanks for taking the time to look at this. Regards. Mike Flug michael.flug(a)snet.net 3/21/01 5:29:20 PM, Nicholas Brenckle <nick(a)hackermonkey.com> wrote: > > Make the connection with adsl, then post the results of the following: > >ifconfig -a >route -n >ping -c 10 204.60.7.22 >ping -c 10 dns.snet.net > >Post whatever results or errors you get. bash-2.04# adsl-start ..... Connected! bash-2.04# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:01:03:24:E3:FA inet6 addr: fe80::1:324:e3fa/10 Scope:Link inet6 addr: fe80::201:3ff:fe24:e3fa/10 Scope:Link UP BROADCAST RUNNING MTU:1500 Metric:1 RX packets:22 errors:0 dropped:0 overruns:0 frame:0 TX packets:41 errors:0 dropped:0 overruns:0 carrier:4 collisions:0 txqueuelen:100 Interrupt:5 Base address:0x8800 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:19 errors:0 dropped:0 overruns:0 frame:0 TX packets:19 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 ppp0 Link encap:Point-to-Point Protocol inet addr:64.252.0.52 P-t-P:64.252.0.1 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:13 errors:0 dropped:0 overruns:0 frame:0 TX packets:19 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:10 sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 bash-2.04# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 64.252.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 64.252.0.1 0.0.0.0 UG 0 0 0 ppp0 bash-2.04# ping -c 10 204.60.7.22 PING 204.60.7.22 (204.60.7.22): 56 data bytes 64 bytes from 204.60.7.22: icmp_seq=0 ttl=252 time=19.969 ms 64 bytes from 204.60.7.22: icmp_seq=1 ttl=252 time=20.427 ms 64 bytes from 204.60.7.22: icmp_seq=3 ttl=252 time=21.325 ms 64 bytes from 204.60.7.22: icmp_seq=4 ttl=252 time=22.142 ms 64 bytes from 204.60.7.22: icmp_seq=6 ttl=252 time=22.983 ms 64 bytes from 204.60.7.22: icmp_seq=7 ttl=252 time=23.328 ms 64 bytes from 204.60.7.22: icmp_seq=8 ttl=252 time=24.118 ms 64 bytes from 204.60.7.22: icmp_seq=9 ttl=252 time=23.156 ms --- 204.60.7.22 ping statistics --- 10 packets transmitted, 8 packets received, 20% packet loss round-trip min/avg/max = 19.969/22.181/24.118 ms bash-2.04# ping -c 10 dns.snet.net PING dns.snet.net (204.60.7.22): 56 data bytes 64 bytes from 204.60.7.22: icmp_seq=0 ttl=252 time=22.781 ms 64 bytes from 204.60.7.22: icmp_seq=1 ttl=252 time=23.301 ms 64 bytes from 204.60.7.22: icmp_seq=2 ttl=252 time=20.969 ms 64 bytes from 204.60.7.22: icmp_seq=3 ttl=252 time=21.754 ms 64 bytes from 204.60.7.22: icmp_seq=6 ttl=252 time=22.474 ms 64 bytes from 204.60.7.22: icmp_seq=7 ttl=252 time=23.735 ms 64 bytes from 204.60.7.22: icmp_seq=9 ttl=252 time=20.928 ms --- dns.snet.net ping statistics --- 10 packets transmitted, 7 packets received, 30% packet loss round-trip min/avg/max = 20.928/22.277/23.735 ms

1 0

Re: [SLE] kde2.1 Splash screen hang.
by Gary A. Garibaldi 22 Mar '01

22 Mar '01

On Wednesday 21 March 2001 20:32, you wrote: > On Wednesday 21 March 2001 13:38, you wrote: > > I have found that my splash screen locks up occasionally when (for some > > reason) SuSE's KInternet tool loads _before_ KDE. This seems to be the > > problem at least for me... > > > > -Tim > Don't know if this will help but I had the same problem. I went to ~/.kde2/share/config and mv ksmserverrc ksmserverrc.old loged out of kde not saving the desktop and log back in. The splash screen will no longer hang just as long as you don't save the desktop prior to exiting. Gary

1 0

SLE Upgrade to 7.1, but new Firewall won't work
by Hal Schlicht 22 Mar '01

22 Mar '01

Hello: My upgrade to Ver 7.1 went through without any significant problems except for the new Firewall setup under the 2.4 kernel. My system is a small home office with only 2 PC's: my Linux box and a lower-powered Win NT 4.0 box. Under SuSE 7.0, my Linux acted as a proxy to my dial-up ISP for the NT workstation. Under 7.1, however, I can't seem to get the '/etc/rc.config.d/firewall.rc.config' file to work properly --- the 'SuSEfirewall_*' bootup scripts always fail. I've read the documentation files, but I'm still doing something wrong, and can't figure out what! Can anyone help me?? Thanks, Hal Schlicht

3 2

RE: [SLE] Upgrade to 7.1, but new Firewall won't work
by Crazy Diamond 22 Mar '01

22 Mar '01

There is an SuSEfirewall update for 7.1 which fixes the failed messages. This is only an exit status error, the ipchain rules are still being set. download the update on the ftp server for 7.1 under the directory sec1 Crazy D __________________________________________________ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/

1 0

Biff for KDE2?
by Thomas Long 22 Mar '01

22 Mar '01

I am used to using KBiff in KDE1. Now that I am migrating to KDE2, I am looking for a comparable applet that will park in the KDE2.1 system tray. Does anyone know of any (conversely, can suitable instruction be given to arrive placing the KBiff in the KDE2.1 system tray; when I attempt to do so, it simply minimizes on the desktop. Also, I am unable to print messages (in KMail) or websites (in Konqueror) without getting an unusually wide-spaced font. Any suggestions? -Thomas Long tlong(a)billsoft.com

2 1

Re: [SLE] 7.1 Won't Install, and Worse
by Volker Kuhlmann 22 Mar '01

22 Mar '01

> News, tho. I did the low level format and verify, and reinstalled SuSE 7.0. Since then it's been doing some very weird stuff, but only off and on. For example, I'm getting httpd-conf errors at boot up, but not at every boot up. The warn file reports problems with PHP (3). So no surprise there. But, on some boot ups, when I go to log in, it rejects my log-in. What I mean is, I don't see the next line, "password:". As soon as I type in something and hit enter, I get "login incorrect". And sometimes that's followed by a "respawning too fast" message. > > And although the segmentation faults aren't as numerous as they were after the first install, they're still appearing from time-toi-time. Hardware errors, no doubt about it. The software couldn't possibly be that buggy. It could be your SCSI cabling (this is sensitive to bad connections, or bad cable connectors), or your RAM, or your motherboad, or ... (endless possibilities). Main thing: stop looking for software trouble. Volker PS: please limit your lines to 72 characters.

1 0

konsole paramiters
by Samy Elashmawy 22 Mar '01

22 Mar '01

xterm -fn 8x20 works like a charm :) but konsole -fn 8x20 hive an error ? Any Ideas any one ?

3 2

Configuring sendmail on SuSELinux 7.1
by Sundar ＠eSaravana 22 Mar '01

22 Mar '01

Hello, I am kind of new to linux. Though I have been using Linux on my laptop for some time for developing Java Applications, I never had a chance to configure a mailserver on Linux box. I want to set up a mail server at home. My understanding is to configure sendmail first and second install POP3 server like qpopper. When I try to set up sendmail on SuSE Linux 7.1, the SuSE handbook says to update rc.config for the following variables SENDMAIL_TYPE, SENDMAIL_HOST, SENDMAIL_SMARTHOST........, which I don't see'em in rc.config. Does anybody know of any on-line step-by-step instruction on configuring sendmail on SuSE7.1 with YaST1 or any other good source you think that I can benefit from.I did download sendmail. But, instruction that came with it were dispersed and daunting. Note: Is there any other product easier than this, commercially or non-commercially? Cheers..! Sundar

4 5

Re: [SLE] XFree86 4.0.3 - When?
by Nadeem Hasan 21 Mar '01

21 Mar '01

Its BS! SuSE does not have this directory structure on their FTP server. Please don't spread misinformation. plsusa(a)bellsouth.net wrote: > > Right now. > > > ftp://ftp.xfree86.org/pub/XFree86/4.0.3/ > > Harry G > > At 09:43 AM 03/20/2001, you wrote: > > > Hi SuSE, > > > > I'm waiting to get my hands on XF 4.0.3. When do you > > expect to make the RPMs available on FTP? > > -- Nadeem Hasan nhasan(a)nadmm.com http://www.nadmm.com/

4 5