Linux-Hardware Digest #620, Volume #10 Tue, 29 Jun 99 01:13:27 EDT
Contents:
Re: ATI AGP card (the hork)
Re: ATI Xpert98 (the hork)
Re: Sony CDU926S spitting the CD Caddy right back out ("Gene Heskett")
Re: Creative SB PCI128 Good Card? ("Andy")
[EMAIL PROTECTED] ("Andrew Harvey")
Upgraded from Intel Pentium 200MMX to AMD K6-2 400 3dNOW (Problems) ("Ralph Allan
Rice")
Re: Diamond Viper 32MB TNT2 Video Card (Jake J Sadowski)
SCSI Drive Problems -- Kernel Panic: scsi_free (root)
----------------------------------------------------------------------------
From: the hork <[EMAIL PROTECTED]>
Subject: Re: ATI AGP card
Date: Mon, 28 Jun 1999 23:00:31 +0200
Dave Dawson wrote:
>
> I have RH 5.2 which came with Red Hat Linux Unleashed. I originally
> installed it with an ISA 512K video card. I installed an ATI AGP Expert 98
> card with 8 MB. When I run Xconfigurator, it recognizes the card as a
> Mach64, and assigns the server as Mach64. I have no options. When I
> startx, it says something about not being able to find the Mach64 server.
> (Can't say exactly, it's on my computer at home)
>
> I have run xf86config, and I can get the Xwindows to run, but Netscape
> complains incessantly about not having the right color level. It shows
> almost everything in shades of grey (about 2), and gives constant error
> messages. I can't run control-panel for the same reason.
>
> How do I solve this?
>
try setting a higher color depth for the used resolution.
Parameter default_colordepth IMHO.
regards
HORK
------------------------------
From: the hork <[EMAIL PROTECTED]>
Crossposted-To: comp.windows.x.i386unix
Subject: Re: ATI Xpert98
Date: Mon, 28 Jun 1999 23:08:40 +0200
Alessandro Giachino wrote:
>
> I am having major problems with my X-server.
>
> It frequently crashes.
>
> I am using ATI Xpert98 with latest XFree86 (3.3.3.1)
>
> Also: RedHat5.2 kernel-2.2.5
>
> Anyone got problems with this? Could it be a memory
> problem (kernel related)?
>
> thanks,
i used a ati xp98 too (agp version).
had no problems.
try kernel 2.0.36 or look for a special driver for that card.
cu
hork
------------------------------
Date: 29 Jun 99 00:02:44 -0500
From: "Gene Heskett" <[EMAIL PROTECTED]>
Subject: Re: Sony CDU926S spitting the CD Caddy right back out
Crossposted-To: comp.periphs.scsi
Unrot13 this;
Reply to: <[EMAIL PROTECTED]>
Gene Heskett sends Greetings to Matthew Hiller;
[...]
MH> the drive -- it feeds a little bit and then gets spat back out at me.
MH> I called up Sony technical support, and when they asked what OS I
MH> was running, I responded, "Debian Linux -- but it's not installed yet." I
MH> think this stumped them, but they said to call back when the OS was
MH> installed.
Typical. Sigh
MH> My question - does anyone know whether this should matter or not?
MH> Should a working drive on a terminated SCSI bus be spitting the caddy
MH> back at me like that, even if the OS isn't loaded? Or even if the bus
MH> isn't terminated? Or the device is disconnected entirely?
For that, it should not need a quarter to call anybody. While it could
be a more serious mechanical problem, I've seen it with the Toshiba
caddy type drive, and fixed it too. ISTR the belt had stretched a hair,
and it ejected because it couldn't bring it fully to the home position.
The belt I had was a bit snugger, and hasn't failed since.
If you're not comfortable doing such tiddly stuff, send it back to
Sony, and demand one that works. Me? I'm a tech.
Cheers, Gene
--
Gene Heskett, CET, UHK |Amiga A2k Zeus040 50 megs fast/2 megs chip
Ch. Eng. @ WDTV-5 |A2091,GuruRom,1g Seagate,CDROM,Multiface III
|Buddha + 4 gig WDC drive, 525 meg tape
|Stylus Pro, EnPrint, Picasso-II, 17" vga
RC5-Moo! 690kkeys/sec isn't much, but it all helps
email gene underscore heskett at iolinc dot net
--
------------------------------
From: "Andy" <[EMAIL PROTECTED]>
Subject: Re: Creative SB PCI128 Good Card?
Date: Tue, 29 Jun 1999 00:14:34 -0400
I have that card running "OK" under linux. with a paid OSS it installed
simply. however the midi isn't supported and esd works great but if you run
esd, when you turn the sound off it gives an error "OSS warning: Application
caused too much output underrun errors" but I haven't noticed any
consequences to this. just as a note I'm ditching it for an AWE 64 Gold.
not only is it cheaper to buy with OSS but the MIDI works and it's got that
cool digital optical out (mmmm minidisc).
Thanks,
Andy
[EMAIL PROTECTED]
Bryan <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> I would like to know if the Creative SB PCI 128 was a good linux sound
> card and easy to set up?
>
------------------------------
From: "Andrew Harvey" <[EMAIL PROTECTED]>
Subject: [EMAIL PROTECTED]
Date: Tue, 29 Jun 1999 14:02:57 +1000
Hi Brett,
Are we on for tomorrow? Also, do you have Paul's current email? I thought
I'd drop him a line.
Andrew
------------------------------
From: "Ralph Allan Rice" <[EMAIL PROTECTED]>
Subject: Upgraded from Intel Pentium 200MMX to AMD K6-2 400 3dNOW (Problems)
Date: Tue, 29 Jun 1999 00:58:54 -0400
Hello,
I had some trouble using Redhat 5.1. A couple weeks ago, I upgraded my
computer from a Pentium 200MMX to a AMD K6-2 400 with a FIC 2013? 100mhz
motherboard with 64 MB RAM. This evening was the third or fourth time I
seen Linux since the upgrade, but it hung without displaying a message. The
logs had nothing in them dating tonight. So I reboot, it does it's system
checks, and tries to repair any lost clusters from an improper mount.
Again, the machine crashes, while doing the repair, asking me for the root
password or to hit control-D to reboot. I hit control-D, and I get it to
reboot. After another file system check, it finally gets to the login
screen. I log in and try to run an app and it freezes.
My question is: Was I suppose to do something (recompile kernel, adjust any
settings, etc) BEFORE I upgraded to an AMD chip?
BTW, the other hardware that was in the previous machine ( A WinModem ) was
removed. It now has a USR Sportster 28.8 external. The non-SB sound card
was left.
Any leads?
Thanks.
Ralph
------------------------------
From: Jake J Sadowski <[EMAIL PROTECTED]>
Subject: Re: Diamond Viper 32MB TNT2 Video Card
Date: Tue, 29 Jun 1999 04:52:15 -0700
You can find 3d support at www.nvidia.com. They have X server with GL.
Read their FAQ.
Cheers.
Ben4202299 wrote:
> I have just ordered parts for a new system, and among those parts is the video
> card mentioned above. My question is: How do I utilize all the neato 3D
> features and stuff of this card in linux? I know I can load a generic driver
> and get simple graphics working, but I'd like to have at least some of the
> functionality available in Linux! Thanks for any help.
>
> Ben
------------------------------
From: root <[EMAIL PROTECTED]>
Subject: SCSI Drive Problems -- Kernel Panic: scsi_free
Date: Tue, 29 Jun 1999 00:44:32 -0400
Hello,
I've been having a lot of trouble lately with my SCSI hard
drives and haven't been able to find a good
explanation or any help for my problem. If anyone knows a good website
I can check for information please let me know. Please e-mail me a
reply as well as posting here.
The system is a RedHat 6.0 which was upgrade from a RedHat 5.2.
The problem exibited itself under 5.2. Part of the hope of upgrading
was to fix the problem. The kernel is 2.2.5-22
The problem as best I can tell is with the second hard drive (id
1). The whole computer freezes while
this is happening. A few times I have been able to switch to the
virtual console and have seen text similar to the following log. Most
of the time the computer freezes before I get a chance to see the
output. Sometimes it is able to recover from the problem, sometimes
not. I have gone a week or two without seeing the problem, other times
it happens 2 or three times a night. In general it appears to happen
when Netscape is running & clearing the cache or doing some other file
intensive operation. I've also seen it when moving large numbers of
files.
Here is the log of the problem:
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52739, scsi0, channel 0, id 1, lun 0 Write (6) 00 00 41 04 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52743 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52740, scsi0, channel 0, id 1, lun 0 Write (6) 00 40 49 04 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52744 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi0: CCB #52743 to Target 1 Aborted
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52741, scsi0, channel 0, id 1, lun 0 Write (6) 00 40 5d 02 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52745 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52742, scsi0, channel 0, id 1, lun 0 Write (6) 01 40 65 02 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52746 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi0: CCB #52744 to Target 1 Aborted
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52743, scsi0, channel 0, id 1, lun 0 Write (6) 01 80 47 04 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52747 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52744, scsi0, channel 0, id 1, lun 0 Write (6) 01 80 79 02 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52748 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52745, scsi0, channel 0, id 1, lun 0 Write (6) 01 82 3f 02 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52749 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi0: CCB #52746 to Target 1 Aborted
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52746, scsi0, channel 0, id 1, lun 0 Write (6) 0b ab 38 02 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52750 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52747, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 24 87 f1 00
00 02 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52751 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi0: CCB #52751 to Target 1 Aborted
Jun 28 00:38:26 tbowditch kernel: scsi0: CCB #52749 to Target 1 Aborted
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52748, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 2a 87 ef 00
00 02 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52752 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi0: CCB #52752 to Target 1 Aborted
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52749, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 6c 1a c4 00
00 02 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52753 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi0: CCB #52753 to Target 1 Aborted
Jun 28 00:38:26 tbowditch kernel: scsi0: CCB #52750 to Target 1 Aborted
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52750, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 6c 1a c8 00
00 02 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52754 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi0: CCB #52754 to Target 1 Aborted
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52751, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 6c 1a ea 00
00 02 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52755 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi0: CCB #52755 to Target 1 Aborted
Jun 28 00:38:26 tbowditch kernel: scsi0: CCB #52748 to Target 1 Aborted
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52752, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 6c 1a f4 00
00 02 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52756 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi0: CCB #52756 to Target 1 Aborted
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52753, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 6c 29 46 00
00 02 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52757 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi0: CCB #52757 to Target 1 Aborted
Jun 28 00:38:26 tbowditch kernel: scsi0: CCB #52747 to Target 1 Aborted
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52754, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 6e 9a ec 00
00 02 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52758 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi0: CCB #52758 to Target 1 Aborted
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52755, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 6e 9a f2 00
00 04 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52759 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi0: CCB #52759 to Target 1 Aborted
Jun 28 00:38:26 tbowditch kernel: scsi0: CCB #52745 to Target 1 Aborted
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52756, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 6e 9a fc 00
00 02 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52760 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52757, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 70 5a c2 00
00 02 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52761 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi0: CCB #52761 to Target 1 Aborted
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52758, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 73 1a fe 00
00 06 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52762 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi0: CCB #52762 to Target 1 Aborted
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52759, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 75 1c 2c 00
00 02 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52763 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi0: CCB #52763 to Target 1 Aborted
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52760, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 75 1c 36 00
00 02 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52764 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi0: CCB #52764 to Target 1 Aborted
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52761, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 76 da ee 00
00 02 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52765 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi0: CCB #52765 to Target 1 Aborted
Jun 28 00:38:26 tbowditch kernel: scsi : aborting command due to timeout
: pid 52762, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 7b db 5e 00
00 02 00
Jun 28 00:38:26 tbowditch kernel: scsi0: Aborting CCB #52766 to Target 1
Jun 28 00:38:26 tbowditch kernel: scsi0: CCB #52766 to Target 1 Aborted
Jun 28 00:38:27 tbowditch kernel: SCSI host 0 abort (pid 52756) timed
out - resetting
Jun 28 00:38:27 tbowditch kernel: SCSI bus is being reset for host 0
channel 0.
Jun 28 00:38:27 tbowditch kernel: scsi0: Sending Bus Device Reset CCB
#52794 to Target 1
Jun 28 00:38:27 tbowditch kernel: scsi : aborting command due to timeout
: pid 52763, scsi0, channel 0, id 1, lun 0 Read (6) 0f 43 b6 02 00
Jun 28 00:38:27 tbowditch kernel: scsi0: Unable to Abort Command to
Target 1 - CCB Reset
Jun 28 00:38:28 tbowditch kernel: SCSI host 0 channel 0 reset (pid
52756) timed out - trying harder
Jun 28 00:38:28 tbowditch kernel: SCSI bus is being reset for host 0
channel 0.
Jun 28 00:38:28 tbowditch kernel: scsi0: Resetting BusLogic BT-930 due
to Target 1
Jun 28 00:38:28 tbowditch kernel: scsi0: *** BusLogic BT-930 Initialized
Successfully ***
Jun 28 00:38:34 tbowditch kernel: scsi0: Tagged Queuing now active for
Target 1
Jun 28 00:45:08 tbowditch named[402]: Cleaned cache of 0 RRs
Jun 28 00:45:08 tbowditch named[402]: USAGE 930545108 930537908
CPU=0u/0s CHILDCPU=0u/0s
Jun 28 00:45:08 tbowditch named[402]: NSTATS 930545108 930537908
Jun 28 00:45:08 tbowditch named[402]: XSTATS 930545108 930537908 RR=1
RNXD=0 RFwdR=0 RDupR=0 RFail=0 RFErr=0 RErr=0 RAXFR=0 RLame=0 ROpts=0
SSysQ=1 SAns=0 SFwdQ=0 SDupQ=3 SErr=0 RQ=0 RIQ=0 RFwdQ=0 RDupQ=0 RTCP=0
SFwdR=0 SFail=0 SFErr=0 SNaAns=0 SNXD=0
Jun 28 01:01:47 tbowditch kernel: scsi0: Tagged Queuing now active for
Target 4
Jun 28 01:04:07 tbowditch kernel: scsi : aborting command due to timeout
: pid 64284, scsi0, channel 0, id 1, lun 0 Write (6) 00 40 4d 06 00
Jun 28 01:04:07 tbowditch kernel: scsi0: Aborting CCB #64342 to Target 1
Jun 28 01:04:07 tbowditch kernel: scsi : aborting command due to timeout
: pid 64285, scsi0, channel 0, id 1, lun 0 Write (6) 00 40 59 04 00
Jun 28 01:04:07 tbowditch kernel: scsi0: Aborting CCB #64343 to Target 1
Jun 28 01:04:07 tbowditch kernel: scsi0: CCB #64342 to Target 1 Aborted
Jun 28 01:22:53 tbowditch syslogd 1.3-3: restart.
I have also seen the message (immediately after the *** BusLogic BT-930
Initialized Successfully ***)
Kernel Panic: scsi_free: Trying to free unused memory
In Interrupt handler - not syncing.
However this has not appeared in the log anywhere. I believe this is
becauset the computer has crashed
before it gets a chance to write this to the log. Unfortunately, on
most crashes, there hasn't been anything written to the log at all.
And here is the log of the computer startup of the SCSI drives.
Jun 28 23:21:19 tbowditch kernel: scsi: ***** BusLogic SCSI Driver
Version 2.1.15 of 17 August 1998 *****
Jun 28 23:21:19 tbowditch atd: atd startup succeeded
Jun 28 23:21:19 tbowditch kernel: scsi: Copyright 1995-1998 by Leonard
N. Zubkoff <[EMAIL PROTECTED]>
Jun 28 23:21:19 tbowditch kernel: scsi0: Configuring BusLogic Model
BT-930 PCI Ultra SCSI Host Adapter
Jun 28 23:21:19 tbowditch kernel: scsi0: Firmware Version: 5.02, I/O
Address: 0xF800, IRQ Channel: 11/Level
Jun 28 23:21:19 tbowditch kernel: scsi0: PCI Bus: 0, Device: 17,
Address: 0xFDFFF000, Host Adapter SCSI ID: 7
Jun 28 23:21:19 tbowditch kernel: scsi0: Parity Checking: Enabled,
Extended Translation: Enabled
Jun 28 23:21:19 tbowditch kernel: scsi0: Synchronous Negotiation:
SUFFUFF#, Wide Negotiation: Disabled
Jun 28 23:21:19 tbowditch kernel: scsi0: Disconnect/Reconnect:
Enabled, Tagged Queuing: Enabled
Jun 28 23:21:19 tbowditch kernel: scsi0: Driver Queue Depth: 255,
Scatter/Gather Limit: 128 segments
Jun 28 23:21:19 tbowditch kernel: scsi0: Tagged Queue Depth:
Automatic, Untagged Queue Depth: 3
Jun 28 23:21:19 tbowditch kernel: scsi0: Error Recovery Strategy:
Default, SCSI Bus Reset: Enabled
Jun 28 23:21:19 tbowditch kernel: scsi0: SCSI Bus Termination:
Enabled, SCAM: Disabled
Jun 28 23:21:19 tbowditch kernel: scsi0: *** BusLogic BT-930 Initialized
Successfully ***
Jun 28 23:21:19 tbowditch kernel: scsi0 : BusLogic BT-930
Jun 28 23:21:19 tbowditch kernel: scsi : 1 host.
Jun 28 23:21:19 tbowditch kernel: Vendor: WDIGTL Model:
ENTERPRISE Rev: 1.62
Jun 28 23:21:19 tbowditch kernel: Type:
Direct-Access ANSI SCSI revision: 02
Jun 28 23:21:19 tbowditch kernel: Detected scsi disk sda at scsi0,
channel 0, id 0, lun 0
Jun 28 23:21:19 tbowditch kernel: Vendor: QUANTUM Model: FIREBALL
SE4.3S Rev: PJ0A
Jun 28 23:21:19 tbowditch kernel: Type:
Direct-Access ANSI SCSI revision: 02
Jun 28 23:21:19 tbowditch kernel: Detected scsi disk sdb at scsi0,
channel 0, id 1, lun 0
Jun 28 23:21:19 tbowditch kernel: Vendor: QUANTUM Model: FIREBALL
SE8.4S Rev: PJ0A
Jun 28 23:21:19 tbowditch kernel: Type:
Direct-Access ANSI SCSI revision: 02
Jun 28 23:21:19 tbowditch kernel: Detected scsi disk sdc at scsi0,
channel 0, id 4, lun 0
Jun 28 23:21:19 tbowditch kernel: Vendor: PLEXTOR Model: CD-ROM
PX-12CS Rev: 1.00
Jun 28 23:21:19 tbowditch kernel: Type:
CD-ROM ANSI SCSI revision: 02
Jun 28 23:21:19 tbowditch kernel: Detected scsi CD-ROM sr0 at scsi0,
channel 0, id 6, lun 0
Jun 28 23:21:19 tbowditch kernel: scsi0: Target 0: Queue Depth 28,
Asynchronous
Jun 28 23:21:19 tbowditch kernel: scsi0: Target 1: Queue Depth 28,
Synchronous at 20.0 MB/sec, offset 15
Jun 28 23:21:19 tbowditch kernel: scsi0: Target 4: Queue Depth 28,
Synchronous at 20.0 MB/sec, offset 15
Jun 28 23:21:19 tbowditch kernel: scsi0: Target 6: Queue Depth 3,
Synchronous at 10.0 MB/sec, offset 15
Jun 28 23:21:19 tbowditch kernel: Uniform CDROM driver Revision: 2.54
Jun 28 23:21:19 tbowditch kernel: SCSI device sda: hdwr sector= 512
bytes. Sectors= 4254819 [2077 MB] [2.1 GB]
Jun 28 23:21:19 tbowditch kernel: sda: sda1
Jun 28 23:21:19 tbowditch kernel: SCSI device sdb: hdwr sector= 512
bytes. Sectors= 8418816 [4110 MB] [4.1 GB]
Jun 28 23:21:19 tbowditch kernel: sdb: sdb1 sdb2 < sdb5 sdb6 sdb7 sdb8
>
Jun 28 23:18:04 tbowditch rc.sysinit: Setting default font succeeded
Jun 28 23:18:04 tbowditch swapon: swapon: warning: /dev/sdb8 has
insecure permissions 0660, 0600 suggested
Jun 28 23:18:04 tbowditch rc.sysinit: Activating swap partitions
succeeded
Jun 28 23:18:04 tbowditch rc.sysinit: Setting hostname
tbowditch.ne.mediaone.net succeeded
Jun 28 23:18:04 tbowditch fsck: /dev/sdb1 was not cleanly unmounted,
check forced.
Jun 28 23:18:04 tbowditch fsck: /dev/sdb1:
Jun 28 23:18:04 tbowditch fsck: D
Jun 28 23:18:04 tbowditch fsck: eleted
Jun 28 23:18:04 tbowditch fsck:
Jun 28 23:18:04 tbowditch fsck: inode
Jun 28 23:18:04 tbowditch fsck:
Jun 28 23:18:04 tbowditch fsck: 10138
Jun 28 23:18:04 tbowditch fsck: has zero dtime.
Jun 28 23:18:04 tbowditch fsck: FIXED.
Jun 28 23:18:04 tbowditch fsck: /dev/sdb1:
Jun 28 23:18:04 tbowditch fsck: E
Jun 28 23:18:04 tbowditch fsck: ntry
Jun 28 23:18:04 tbowditch fsck: '
Jun 28 23:18:04 tbowditch fsck: k
Jun 28 23:18:04 tbowditch fsck: d
Jun 28 23:18:04 tbowditch fsck: e
Jun 28 23:18:04 tbowditch fsck: g
Jun 28 23:18:04 tbowditch fsck: a
Jun 28 23:21:19 tbowditch kernel: SCSI device sdc: hdwr sector= 512
bytes. Sectors= 16777215 [8191 MB] [8.2 GB]
Jun 28 23:21:19 tbowditch kernel: sdc: sdc1 < sdc5 sdc6 sdc7 sdc8 >
Jun 28 23:21:19 tbowditch kernel: autodetecting RAID arrays
Jun 28 23:21:19 tbowditch kernel: autorun ...
Jun 28 23:21:19 tbowditch kernel: ... autorun DONE.
Jun 28 23:21:19 tbowditch kernel: VFS: Mounted root (ext2 filesystem)
readonly.
Jun 28 23:21:19 tbowditch kernel: change_root: old root has d_count=1
Jun 28 23:21:19 tbowditch kernel: Trying to unmount old root ... okay
Jun 28 23:21:19 tbowditch kernel: Freeing unused kernel memory: 60k
freed
Jun 28 23:21:19 tbowditch kernel: scsi0: Tagged Queuing now active for
Target 1
Jun 28 23:21:19 tbowditch kernel: Adding Swap: 128484k swap-space
(priority -1)
Jun 28 23:21:19 tbowditch kernel: Soundblaster audio driver Copyright
(C) by Hannu Savolainen 1993-1996
Jun 28 23:21:19 tbowditch kernel: SB 4.13 detected OK (220)
Jun 28 23:21:19 tbowditch kernel: YM3812 and OPL-3 driver Copyright (C)
by Hannu Savolainen, Rob Hooft 1993-1996
Jun 28 23:21:19 tbowditch kernel: scsi0: Tagged Queuing now active for
Target 4
Jun 28 23:18:04 tbowditch fsck: m
Jun 28 23:18:04 tbowditch fsck: e
Jun 28 23:18:04 tbowditch fsck: s
Jun 28 23:18:04 tbowditch fsck: -
Jun 28 23:18:04 tbowditch fsck: 1
Jun 28 23:18:04 tbowditch fsck: .
Jun 28 23:18:04 tbowditch fsck: 1
Jun 28 23:18:04 tbowditch fsck: .
Jun 28 23:18:04 tbowditch fsck: 1
Jun 28 23:18:04 tbowditch fsck: -
Jun 28 23:18:04 tbowditch fsck: 1
Jun 28 23:18:04 tbowditch fsck: .
Jun 28 23:18:04 tbowditch fsck: i
Jun 28 23:18:04 tbowditch fsck: 3
Jun 28 23:18:04 tbowditch fsck: 8
Jun 28 23:18:04 tbowditch fsck: 6
Jun 28 23:18:04 tbowditch fsck: .
Jun 28 23:18:04 tbowditch fsck: r
Jun 28 23:18:04 tbowditch fsck: p
Jun 28 23:18:04 tbowditch fsck: m
Jun 28 23:18:04 tbowditch fsck: ' in
Jun 28 23:18:04 tbowditch fsck: /
Jun 28 23:18:04 tbowditch fsck: r
Jun 28 23:18:04 tbowditch fsck: o
Jun 28 23:18:04 tbowditch fsck: o
Jun 28 23:18:04 tbowditch fsck: t
Jun 28 23:18:04 tbowditch fsck: (
Jun 28 23:18:04 tbowditch fsck: 18074
Jun 28 23:18:04 tbowditch fsck: )
Jun 28 23:18:04 tbowditch fsck: has
Jun 28 23:18:04 tbowditch fsck: deleted
Jun 28 23:18:04 tbowditch fsck: /unused
Jun 28 23:18:04 tbowditch fsck: inode
Jun 28 23:21:19 tbowditch kernel: eth0: 3c509 at 0x300 tag 1, 10baseT
port, address 00 60 08 ae b5 72, IRQ 10.
Jun 28 23:21:19 tbowditch kernel: 3c509.c:1.16 (2.2) 2/3/98
[EMAIL PROTECTED]
Jun 28 23:21:19 tbowditch kernel: eth0: Setting Rx mode to 1 addresses.
Jun 28 23:21:19 tbowditch kernel: eth0: Setting Rx mode to 0 addresses.
Jun 28 23:21:19 tbowditch kernel: eth0: Setting Rx mode to 1 addresses.
Jun 28 23:18:04 tbowditch fsck:
Jun 28 23:18:04 tbowditch fsck: 18407
Jun 28 23:18:04 tbowditch fsck: .
Jun 28 23:18:04 tbowditch fsck: CLEARED.
Jun 28 23:18:04 tbowditch fsck: /dev/sdb1: 8856/34136 files (4.3%
non-contiguous), 96997/136521 blocks
Jun 28 23:18:04 tbowditch rc.sysinit: Checking root filesystem succeeded
Jun 28 23:18:04 tbowditch isapnp: Board 1 has Identity 98 00 00 ca 3c a5
00 8c 0e: CTL00a5 Serial No 51772 [checksum 98]
Jun 28 23:18:04 tbowditch isapnp: Board 2 has Identity e5 ff ff ff ff 70
00 8c 0e: CTL0070 Serial No -1 [checksum e5]
Jun 28 23:18:04 tbowditch isapnp: Board 3 has Identity 9c 15 21 02 32 11
00 72 56: USR0011 Serial No 354484786 [checksum 9c]
Jun 28 23:18:04 tbowditch isapnp: Board 4 has Identity 69 08 ae b5 72 95
50 6d 50: TCM5095 Serial No 145667442 [checksum 69]
Jun 28 23:18:04 tbowditch isapnp: /etc/isapnp.conf:101 -- Warning -
resource conflict allocating 8 bytes of IO at 220 (see /etc/isapnp.conf)
Jun 28 23:21:20 tbowditch crond: crond startup succeeded
Jun 28 23:18:04 tbowditch isapnp: /etc/isapnp.conf:113 -- Warning -
resource conflict allocating 8 bytes of IO at 388 (see /etc/isapnp.conf)
Jun 28 23:18:04 tbowditch isapnp: /etc/isapnp.conf:353 -- Warning -
resource conflict allocating IRQ10 (see /proc/interrupts)
Jun 28 23:18:04 tbowditch rc.sysinit: Setting up ISA PNP devices
succeeded
Jun 28 23:18:04 tbowditch rc.sysinit: Remounting root filesystem in
read-write mode succeeded
Jun 28 23:18:11 tbowditch rc.sysinit: Finding module dependencies
succeeded
Jun 28 23:18:11 tbowditch rc.sysinit: Loading sound module succeeded
Jun 28 23:18:12 tbowditch rc.sysinit: Loading midi module succeeded
Jun 28 23:18:12 tbowditch fsck: /dev/sdb7 was not cleanly unmounted,
check forced.
Jun 28 23:18:50 tbowditch fsck: /dev/sdb7: 11851/132600 files (18.9%
non-contiguous), 346695/530113 blocks
Jun 28 23:18:51 tbowditch fsck: /dev/sdb5 was not cleanly unmounted,
check forced.
Jun 28 23:18:52 tbowditch fsck: /dev/sdb5:
Jun 28 23:18:52 tbowditch fsck: D
Jun 28 23:18:52 tbowditch fsck: eleted
Jun 28 23:18:52 tbowditch fsck:
Jun 28 23:18:52 tbowditch fsck: inode
Jun 28 23:18:52 tbowditch fsck:
Jun 28 23:18:52 tbowditch fsck: 6358
Jun 28 23:21:20 tbowditch rc: Starting pcmcia succeeded
Jun 28 23:18:52 tbowditch fsck: has zero dtime.
Jun 28 23:18:52 tbowditch fsck: FIXED.
Jun 28 23:20:08 tbowditch fsck: /dev/sdb5: 40511/263160 files (4.2%
non-contiguous), 664787/1052226 blocks
Jun 28 23:20:10 tbowditch fsck: /dev/sdb6 was not cleanly unmounted,
check forced.
Jun 28 23:20:26 tbowditch fsck: /dev/sdb6:
Jun 28 23:20:26 tbowditch fsck: I
Jun 28 23:20:26 tbowditch fsck: node
Jun 28 23:20:26 tbowditch fsck:
Jun 28 23:20:26 tbowditch fsck: 94293
Jun 28 23:20:26 tbowditch fsck: , i_size is
Jun 28 23:20:26 tbowditch fsck: 1597440
Jun 28 23:20:26 tbowditch fsck: ,
Jun 28 23:20:26 tbowditch fsck: should be
Jun 28 23:20:26 tbowditch fsck:
Jun 28 23:20:26 tbowditch fsck: 1847296
Jun 28 23:20:26 tbowditch fsck: .
Jun 28 23:20:26 tbowditch fsck: FIXED.
Jun 28 23:20:26 tbowditch fsck: /dev/sdb6:
Jun 28 23:20:26 tbowditch fsck: I
Jun 28 23:20:26 tbowditch fsck: node
Jun 28 23:20:26 tbowditch fsck:
Jun 28 23:20:26 tbowditch fsck: 94293
Jun 28 23:20:26 tbowditch fsck: , i_
Jun 28 23:20:26 tbowditch fsck: block
Jun 28 23:20:26 tbowditch fsck: s is
Jun 28 23:20:26 tbowditch fsck: 3136
Jun 28 23:20:26 tbowditch fsck: ,
Jun 28 23:21:21 tbowditch inet: inetd startup succeeded
Jun 28 23:20:26 tbowditch fsck: should be
Jun 28 23:20:26 tbowditch fsck:
Jun 28 23:20:26 tbowditch fsck: 3624
Jun 28 23:20:26 tbowditch fsck: .
Jun 28 23:20:26 tbowditch fsck: FIXED.
Jun 28 23:20:53 tbowditch fsck: /dev/sdb6: 4133/589824 files (21.8%
non-contiguous), 465048/2353491 blocks
Jun 28 23:21:00 tbowditch rc.sysinit: Checking filesystems succeeded
Jun 28 19:21:07 tbowditch rc.sysinit: Mounting local filesystems
succeeded
If anyone can help I'd greatly appreciate it. I'm near at my wits end
trying to figure out what is going on.
I don't know if the Hard Drive is just plain bad and should be replaced,
if a kernel upgrade would help, or if there is something else I should
be doing altogether.
If there is any other information I can provide, please let me know, I'd
really like to get this fixed.
Thanks,
Tom
Please reply to [EMAIL PROTECTED]
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.hardware) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Hardware Digest
******************************
