3c905b

[William D. Rendahl]

How do I set up a 3Com 3c905b (Cyclone?) NIC at 100Mbps on Bo?


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Unable to login

[William D. Rendahl]

Got it.  My root directory / wasn't set to 755

drwxr--r--   No group or other execute.  Doh!

Thanks to all that replied,
Bill


--
E-mail the word "unsubscribe" to [EMAIL PROTECTED]
TO UNSUBSCRIBE FROM THIS MAILING LIST. Trouble? E-mail to [EMAIL PROTECTED]

Unable to login

[William D. Rendahl]

We have a box here running 1.3.1 that is only
allowing root to login.  Any other account gives:

Unable to cd to "/home/billr"

(or that user's home) immediately after the password
is entered.   The system only has one partition. Any
help or hints would be GREATLY appreciated! Please CC
me directly so I don't have to wait for the digested
version.  mailto:[EMAIL PROTECTED]


--
E-mail the word "unsubscribe" to [EMAIL PROTECTED]
TO UNSUBSCRIBE FROM THIS MAILING LIST. Trouble? E-mail to [EMAIL PROTECTED]

Re: bo, hamm, stable, unstable

[William D. Rendahl]

Ben Gertzfield wrote:

> >>>>> "William" == William D Rendahl <[EMAIL PROTECTED]> writes:
>
> William> How about Sid (the "Happy child")?
>
> Do we want to seem evil? :)
>

Well, there's always Mrs. Nesbit (Buzz in drag) . . .


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: bo, hamm, stable, unstable

[William D. Rendahl]

Dale Harrison <[EMAIL PROTECTED]> wrote:

> > bo and hamm are just code names. bo has been unstable when rex was stable
> > and hamm will become stable with the next release. The names actually are
> > names of figures from Pixar's movie Toy Story. Bruce Perens, who used to
> > be the project leader, works at Pixar.
>
> A bit of a silly question, but has anyone decided on a name for the next
> [after hamm] release?
>
> I find this whole naming thing incredibly cute :)
>
> D.

How about Sid (the "Happy child")?


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Help with SCSI timeout problem?

[William D. Rendahl]

Had the same problem with a BusLogic BT-948 SCSI controller on an
Intel Motherboard.  Tried hard termination on the cable, using async
instead of sync transfers, dropping the transfer speed from 20Mb/sec
to 10Mb/sec, all with little to no effect.  Then tried the 2.0.32 
kernel (was using the default 2.0.29) and it's been fine since.
______

William D. Rendahl mailto:[EMAIL PROTECTED]
  I. S. Administrator Emeritus http://www.perrin.com/
  Perrin Manufacturing Co. Member: HTML Writer's Guild


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

SCSI Errors and Resetting

[William D. Rendahl]

Hi, 

First off: _very_ cool list!  Lurking here has been exceedingly helpful.

We're running Debian 1.3.1 (bo, kernel 2.0.30) on an Intel "Premier
PCI II" motherboard, with a 90MHz Penti, 32MB, BusLogic BT-948, and
Quantum Fireball Drive.  Several times a day we get messages on the
console describing a SCSI error, the system is momentarily frozen, 
and then everything is fine . . .

On bootup it looks like this:

Dec  1 13:40:35 mail kernel: scsi: * BusLogic SCSI Driver Version
2.0.9 of 29 March 1997 * 
Dec  1 13:40:35 mail kernel: scsi: Copyright 1995 by Leonard N. Zubkoff
<[EMAIL PROTECTED]> 
Dec  1 13:40:35 mail kernel: scsi0: Configuring BusLogic Model BT-948
PCI Ultra SCSI Host Adapter 
Dec  1 13:40:35 mail kernel: scsi0:   Firmware Version: 5.06I, I/O
Address: 0xFCFC, IRQ Channel: 11/Level 
Dec  1 13:40:35 mail kernel: scsi0:   PCI Bus: 0, Device: 6, Address:
0xFFBFF000, Host Adapter SCSI ID: 7 
Dec  1 13:40:35 mail kernel: scsi0:   Parity Checking: Enabled, Extended
Translation: Enabled 
Dec  1 13:40:35 mail kernel: scsi0:   Synchronous Negotiation: UUF#,
Wide Negotiation: Disabled 
Dec  1 13:40:35 mail kernel: scsi0:   Disconnect/Reconnect: Enabled,
Tagged Queuing: Enabled 
Dec  1 13:40:35 mail kernel: scsi0:   Scatter/Gather Limit: 128 of 8192
segments, Mailboxes: 255 
Dec  1 13:40:35 mail kernel: scsi0:   Driver Queue Depth: 255, Host
Adapter Queue Depth: 192 
Dec  1 13:40:35 mail kernel: scsi0:   Tagged Queue Depth: Automatic,
Untagged Queue Depth: 3 
Dec  1 13:40:35 mail kernel: scsi0:   Error Recovery Strategy: Default,
SCSI Bus Reset: Enabled 
Dec  1 13:40:35 mail kernel: scsi0:   SCSI Bus Termination: Enabled,
SCAM: Disabled 
Dec  1 13:40:35 mail kernel: scsi0: *** BusLogic BT-948 Initialized
Successfully *** 
Dec  1 13:40:35 mail kernel: scsi0:   Target 0: Synchronous at 20.0
mega-transfers/second, offset 15 
Dec  1 13:40:35 mail kernel: scsi0:   Target 2: Synchronous at 10.0
mega-transfers/second, offset 15 
Dec  1 13:40:35 mail kernel: Failed initialization of WD-7000 SCSI card! 
Dec  1 13:40:35 mail kernel: PPA: unable to initialise controller at
0x378, error 1 
Dec  1 13:40:35 mail kernel: scsi0 : BusLogic BT-948 
Dec  1 13:40:35 mail kernel: scsi : 1 host. 
Dec  1 13:40:35 mail kernel:   Vendor: QUANTUM   Model: FIREBALL
ST2.1S   Rev: 0F0C 
Dec  1 13:40:35 mail kernel:   Type:  
Direct-Access  ANSI SCSI revision: 02 
Dec  1 13:40:35 mail kernel: Detected scsi disk sda at scsi0, channel 0,
id 0, lun 0 
Dec  1 13:40:35 mail kernel:   Vendor: NEC   Model: CD-ROM
DRIVE:462  Rev: 1.13 
Dec  1 13:40:35 mail kernel:   Type:  
CD-ROM ANSI SCSI revision: 02 
Dec  1 13:40:35 mail kernel: Detected scsi CD-ROM sr0 at scsi0, channel
0, id 2, lun 0 
Dec  1 13:40:35 mail kernel: scsi : detected 1 SCSI cdrom 1 SCSI disk
total. 
Dec  1 13:40:35 mail kernel: SCSI device sda: hdwr sector= 512 bytes.
Sectors= 4235629 [2068 MB] [2.1 GB] 
Dec  1 13:40:35 mail kernel: Partition check: 
Dec  1 13:40:35 mail kernel:  sda: sda1 sda2 
Dec  1 13:40:35 mail kernel: VFS: Mounted root (ext2 filesystem)
readonly. 
Dec  1 13:40:35 mail kernel: scsi0: Tagged Queuing now active for Target
0 

And the error messages are:

Dec  1 14:26:57 mail kernel: scsi : aborting command due to timeout :
pid 38105, scsi0, channel 0, id 0, lun 0 Write (6) 17 02 59 02 00  
Dec  1 14:26:57 mail kernel: scsi0: Aborting CCB #38128 to Target 0 
Dec  1 14:26:57 mail kernel: scsi : aborting command due to timeout :
pid 38106, scsi0, channel 0, id 0, lun 0 <4>scsi0: CCB #38128 to Target
0 Aborted 
Dec  1 14:26:57 mail kernel: Write (6) 17 40 53 02 00  
Dec  1 14:26:57 mail kernel: scsi0: Aborting CCB #38129 to Target 0 
Dec  1 14:26:57 mail kernel: scsi : aborting command due to timeout :
pid 38107, scsi0, channel 0, id 0, lun 0 <4>scsi0: CCB #38129 to Target
0 Aborted 
Dec  1 14:26:57 mail kernel: Write (6) 17 45 13 0c 00  
Dec  1 14:26:57 mail kernel: scsi0: Aborting CCB #38130 to Target 0 
Dec  1 14:26:57 mail kernel: scsi : aborting command due to timeout :
pid 38108, scsi0, channel 0, id 0, lun 0 <4>scsi0: CCB #38130 to Target
0 Aborted 
Dec  1 14:26:57 mail kernel: Write (6) 17 45 33 02 00  
Dec  1 14:26:57 mail kernel: scsi0: Aborting CCB #38131 to Target 0 
Dec  1 14:26:57 mail kernel: scsi0: CCB #38131 to Target 0 Aborted 
Dec  1 14:27:04 mail kernel: SCSI host 0 abort (pid 38093) timed out -
resetting 
Dec  1 14:27:04 mail kernel: SCSI bus is being reset for host 0 channel
0. 
Dec  1 14:27:04 mail kernel: scsi0: Sending Bus Device Reset CCB #38149
to Target 0 
Dec  1 14:27:04 mail kernel: SCSI host 0 abort (pid 38094) timed out -
resetting 
Dec  1 14:27:04 mail kernel: SCSI bus is being reset for host 0 channel
0. 
Dec  1 14:27:04 mail kernel: scsi0: Unable to Reset Command to Target 0
- Reset Pending 
-Repeats several times w/incremeting pid-
Dec  1 14:27:04 mail kernel: SCSI host 0 abort (pid 38104) timed out -
resetting 
Dec  1 14:27:04 mail kernel: SCSI bus