Linux-Hardware Digest #754, Volume #14 Thu, 10 May 01 20:13:09 EDT
Contents:
SCSI-Reset on live System ("Lutz Lehmann")
Re: CD Writer for Linux
Re: PCI modem 3COM/USR 2977 ("Robert Morelli")
Re: LinkSys NIC ("Justin Mahn")
Re: Will this system support linux? ("Justin Mahn")
promise ultra66 problems ("Jason Luther")
Re: Voyetra Turtle Beach Santa Cruz driver ("lobotomy")
Re: promise ultra66 problems (Rinaldi J. Montessi)
----------------------------------------------------------------------------
From: "Lutz Lehmann" <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.misc,de.comp.os.unix.linux.hardware,de.comp.os.unix.linux.misc,linux.kernel
Subject: SCSI-Reset on live System
Date: Thu, 10 May 2001 23:17:49 +0200
Hi...
I've got an Adaptec 2940UW in my system. I'm running a 2.18 kernel and need
to send the controller a signal to rescan the SCSI bus for devices (scanner
is only connected when needed). Since I've got swap on a SCSI disk and can't
turn off the swap space, I cannot unload the module.
Someone PLEASE help
Thanx
Lutz
------------------------------
From: [EMAIL PROTECTED] ()
Subject: Re: CD Writer for Linux
Date: Thu, 10 May 2001 22:23:49 GMT
On Thu, 10 May 2001 16:59:49 -0500, t <[EMAIL PROTECTED]> wrote:
>a plextor plexwriter is a kick booty cdrw drive for linux. you just have to
>reconfigure the kernel to get it to work (unless you're running mandrake 7.2
>or higher [i don't know about other distros, but it didn't work in red hat
>7.1, so i had to hack the kernel])
Mine works just fine; you have to insmod the ide-scsi module and put ignore=hdc
in lilo. Instead of using the install module, I compiled the ide-scsi module
directly into my kernel. I don't consider anything that doesn't require editing
the .c files to be hacking.
------------------------------
From: "Robert Morelli" <[EMAIL PROTECTED]>
Subject: Re: PCI modem 3COM/USR 2977
Date: Thu, 10 May 2001 16:41:08 -0700
Crossposted-To: comp.os.linux.setup
In article <[EMAIL PROTECTED]>, "Mark Slagell"
<[EMAIL PROTECTED]> wrote:
I have the same modem working under Red Hat 6.2. I also had it
working under Caldera Open Desktop 2.4. The company that
sold me my PC gave me a hard copy of installation instructions.
The same instructions are found at:
http://ricardo.ecn.wfu.edu/~cottrell/tp390e/rnelson.txt
but I think this is information you already know. They also gave
me and addendum that stated:
"The 5610 modems are not winmodems. However, the default installation
will only have 4 COM ports and this particular modem will only work on
ttyS4. You will need to make a device in your /dev/ directory. The
syntax is below:
makedev ttyS4
This will create the new device. You can then configure minicom to use
..."
I followed these directions exactly under Caldera and it worked. It
didn't work under Red Hat. What finally did work for me under Red Hat
was to disregard the instructions that the modem only works on ttyS4.
In fact, it's been working fine on ttyS3. All I did was put the line
setserial /dev/ttyS3 uart 16550A port 0xd400 irq 11
in rc.local. (Of course, you'd need to change the I/O address and irq.)
I forced the card to use irq11 in the bios. My motherboard allows me
to assign a specific irq to each slot.
> I've been surfing around for the world's collected wisdom on making this
> modem work but am coming up empty so far. Possibly relevant info is
> below. Can anybody shed light?
>
> TIA
>
> -- Mark
>
> ---------------------------
>>uname -a
> Linux pc5053 2.2.18 #4 Mon Apr 9 14:58:16 CDT 2001 i686 unknown
> ---------------------------
>>lspci -v
> [...]
> 01:0b.0 Serial controller: US Robotics/3Com 56K FaxModem Model 5610 (rev
> 01) (prog-if 02 [16550])
> Subsystem: US Robotics/3Com USR 56k Internal FAX Modem
> (Model 2977)
> Flags: medium devsel, IRQ 3
> I/O ports at dff0
> Capabilities: [dc] Power Management version 2
>
> ---------------------------
>>cat /proc/pci
> [...]
> Bus 1, device 11, function 0:
> Serial controller: Unknown vendor Unknown device (rev 1).
> Vendor id=12b9. Device id=1008.
> Medium devsel. IRQ 3.
> I/O at 0xdff0 [0xdff1].
> ---------------------------
>>cat /proc/interrupts
> CPU0
> 0: 247814 XT-PIC timer
> 1: 4923 XT-PIC keyboard 2: 0 XT-PIC
> cascade 3: 32587 XT-PIC eth0
> 9: 12746 XT-PIC Intel ICH 82801AA
> 12: 69297 XT-PIC PS/2 Mouse 13: 1
> XT-PIC fpu
> 14: 961293 XT-PIC ide0
> 15: 7 XT-PIC ide1
> NMI: 0
> ---------------------------
>>setserial /dev/ttyS3 port 0xdff0 autoconfig auto_irq setserial -g
>>/dev/ttyS3
> /dev/ttyS3, UART: unknown, Port: 0xdff0, IRQ: 3
>>minicom
> [unresponsive on /dev/ttyS3]
> ---------------------------
>>[tried setserial with uart as 16550A, 16450, etc, no difference] [tried
>>setserial options: ^fourport, skip_test. no difference] [tried changing
>>IRQ with setpci, managed to lock up the machine a few times]
------------------------------
From: "Justin Mahn" <[EMAIL PROTECTED]>
Subject: Re: LinkSys NIC
Date: Thu, 10 May 2001 18:00:41 -0500
Of course it's completely possible. But since I'm a relative linux newbie,
I've got to learn how that works from scratch, and I just get headeaches
when try to pore through the rc.d init scripts because there's so much stuff
in there that i'm just not familiar with yet. I was wondering if anyone ran
across this before and knew exactly what to look for, i.e. eth1.conf files
or something like that with maybe a timeout option or a renew or
autoreactivate or something like that.
"Nick Lockyer" <[EMAIL PROTECTED]> wrote in message
news:9deevf$1qt$[EMAIL PROTECTED]...
> It it a module or built into the kernel. Is it possible the system sees
the
> module as unused for a while and unloads it?
>
> Justin Mahn <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]...
> > EPOX MVP3G2
> > AMD K6-2/450
> > Creative Ensoniq AudioPCI 1371
> > LinkSys EtherPCI LAN Card II -> Terrayon Cable Modem
> > Network Everywhere (LinkSys) NC100 10/100 -> LAN
> > RedHat 7.1 Firewall/Masquerade
> >
> > I'm having a prob with the 10Mb uplink card. It works just fine until I
> > leave it for a while and when I come back the card is 'Inactive'. What
> logs
> > should I look at to find out why it just stops working? I can
'Activate'
> it
> > just fine, but the wifey doesn't appreciate having to mess with the
server
> > comp while I'm away.
> >
> > The 10Mb uplink is configured with the default DHCP package that comes
> with
> > RH 7.1 and the 10/100Mb LAN card uses dhcpd that also came with RH7.1.
> That
> > part works wonderfuly. 8) I love having my own family name as a .net!
> >
> > You may have to reply by e-mail because this newsgroup is HUGE!
> >
> >
>
>
------------------------------
From: "Justin Mahn" <[EMAIL PROTECTED]>
Subject: Re: Will this system support linux?
Date: Thu, 10 May 2001 18:04:02 -0500
Just make sure your printer is Linux-friendly. My beautiful hp deskjet 932c
doesn't seem to have proper linux drivers to get photo printing working. I
have to serve and old epson ap-3250 from my linux box and serve the HP from
a *insert evil os here* machine.
Damn that AP3250 is noisy.
"Ronald Cole" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> "Ed" <[EMAIL PROTECTED]> writes:
> > Amptron DX-6900 AT style motherboard with 7 16-bit ISA slots.
> > The processor is an Intel 486 DX-2 66Mhz CPU.
> > The video card is a Diamond Stealth 32 VLB card with 2MB Video RAM.
> > The main storage is a 500MB Quantum Fireball TM 1700A 3 1/2" IDE hard
drive.
> > BIOS doesn't see the full 1.7 gig.
> > Audio is a Reveal SC200 Sound Blaster compatible ISA soundcard.
> > Hitachi 8X IDE CD-ROM (model CDR-7930)
> > The ISA controller card supports the IDE channel, floppy drive channel,
> > Printer port and two serial ports(1/DB9 and 1/DB25).
> > US Robotics Sportser 33.6 Data/Fax External Modem.
> > There is 24MB of memory.
>
> They make great DHCP and print servers. Just don't run X on them.
>
> --
> Forte International, P.O. Box 1412, Ridgecrest, CA 93556-1412
> Ronald Cole <[EMAIL PROTECTED]> Phone: (760) 499-9142
> President, CEO Fax: (760) 499-9152
> My GPG fingerprint: C3AF 4BE9 BEA6 F1C2 B084 4A88 8851 E6C8 69E3 B00B
------------------------------
From: "Jason Luther" <[EMAIL PROTECTED]>
Subject: promise ultra66 problems
Date: Thu, 10 May 2001 16:20:49 -0700
Hello.
I have a Dual PII machine (Tyan Tiger 100) with two PCI Promise Ultra66 IDE
controller cards in addition to the onboard IDE controllers. I've got my
root disk on the onboard controller and four Quantum drives on the Promise
cards, each acting as the master. I am using a vanilla RedHat 7.1
installation.
I am having trouble getting Linux to see and use the four Quantum drives in
this configuration. Without passing arguments to the kernel, Linux finds the
first master on each controller, but not the second. If I rearrange the
drives so that some are slaves, Linux find them, but that's not the
configuration I want (nor are my cables long enough to do that permanently).
Following instructions in several HOWTO's and newsgroup archives, I checked
for the I/O values in /proc/pci and passed them to the kernel. Then Linux
finds all of the drives, but the drives on the second controller don't work
right. I get irq timeout messages.
Does anyone see what I'm doing wrong? I've included some file snippets
below.
I get this error any time I access /dev/hdi: "hdi: irq timeout: status=0x50
{ DriveReady SeekComplete }".
I've rearranged the order of the drives, and it doesn't make a difference.
Any help would be much appreciated!
TIA,
Jason
from dmesg:
===========
Kernel command line: auto BOOT_IMAGE=linux ro root=308
BOOT_FILE=/boot/vmlinuz-2.4.2-2smp ide2=0xeff0,0xefe6 ide3=0xefa8,0xefe2
ide4=0xefa0,0xef7c ide5=0xef68,0xef66
ide_setup: ide2=0xeff0,0xefe6
ide_setup: ide3=0xefa8,0xefe2
ide_setup: ide4=0xefa0,0xef7c
ide_setup: ide5=0xef68,0xef66
Initializing CPU#0
[...]
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio
PDC20262: IDE controller on PCI bus 00 dev 80
PDC20262: chipset revision 1
PDC20262: not 100% native mode: will probe irqs later
PDC20262: ROM enabled at 0xfebd0000
PDC20262: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
ide2: BM-DMA at 0xef00-0xef07, BIOS settings: hde:pio, hdf:pio
PDC20262: IDE controller on PCI bus 00 dev 88
PDC20262: chipset revision 1
PDC20262: not 100% native mode: will probe irqs later
PDC20262: ROM enabled at 0xfebc0000
PDC20262: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
ide4: BM-DMA at 0xee80-0xee87, BIOS settings: hdi:pio, hdj:pio
hda: WDC WD136BA, ATA DISK drive
hde: QUANTUM FIREBALLlct15 30, ATA DISK drive
hdg: QUANTUM FIREBALLlct15 30, ATA DISK drive
hdi: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
hdi: QUANTUM FIREBALLlct15 30, ATA DISK drive
hdj: probing with STATUS(0x00) instead of ALTSTATUS(0xff)
hdj: probing with STATUS(0x00) instead of ALTSTATUS(0xff)
hdk: QUANTUM FIREBALLlct15 30, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide2 at 0xeff0-0xeff7,0xefe6 on irq 16
ide3 at 0xefa8-0xefaf,0xefe2 on irq 16 (shared with ide2)
ide4 at 0xefa0-0xefa7,0xef7c on irq 17
ide5 at 0xef68-0xef6f,0xef66 on irq 17 (shared with ide4)
hda: 26712000 sectors (13677 MB) w/2048KiB Cache, CHS=1662/255/63, UDMA(33)
hde: 58633344 sectors (30020 MB) w/418KiB Cache, CHS=58168/16/63, UDMA(66)
hdg: 58633344 sectors (30020 MB) w/418KiB Cache, CHS=58168/16/63
hdi: 58633344 sectors (30020 MB) w/418KiB Cache, CHS=58168/16/63, UDMA(66)
hdk: 58633344 sectors (30020 MB) w/418KiB Cache, CHS=58168/16/63
Partition check:
hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 >
hde: hde1
hdg: hdg1
hdi:hdi: irq timeout: status=0x50 { DriveReady SeekComplete }
hdi: irq timeout: status=0x50 { DriveReady SeekComplete }
hdi: irq timeout: status=0x50 { DriveReady SeekComplete }
hdi: irq timeout: status=0x50 { DriveReady SeekComplete }
hdi: DMA disabled
ide4: reset: success
hdi: irq timeout: status=0x50 { DriveReady SeekComplete }
hdi: irq timeout: status=0x50 { DriveReady SeekComplete }
hdi: irq timeout: status=0x50 { DriveReady SeekComplete }
hdi: irq timeout: status=0x50 { DriveReady SeekComplete }
ide4: reset: success
hdi: irq timeout: status=0x50 { DriveReady SeekComplete }
end_request: I/O error, dev 38:00 (hdi), sector 0
unable to read partition table
hdk: hdk1
from /etc/lilo.conf:
====================
append="ide2=0xeff0,0xefe6 ide3=0xefa8,0xefe2 ide4=0xefa0,0xef7c
ide5=0xef68,0xef66"
what's in /proc/ide:
====================
drivers
hda
hde
hdg
hdi
hdk
ide0
ide2
ide3
ide4
ide5
pdc202xx
piix
contents of /proc/ide/pdc202xx:
===============================
PDC20262 Chipset.
=============================== General
Status ---------------------------------
Burst Mode : enabled
Host Mode : Normal
Bus Clocking : 33 PCI Internal
IO pad select : 6 mA
Status Polling Period : 0
Interrupt Check Status Polling Delay : 0
=============== Primary Channel ================ Secondary
Channel -------------
enabled enabled
66 Clocking enabled disabled
Mode PCI Mode PCI
FIFO Empty FIFO Empty
=============== drive0 ========= drive1 ======== drive0 ==========
drive1 ------
DMA enabled: yes no no no
DMA Mode: UDMA 4 NOTSET UDMA 4 NOTSET
PIO Mode: PIO 4 NOTSET PIO 4 NOTSET
contents of /proc/pci:
======================
Bus 0, device 0, function 0:
Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev
3).
Master Capable. Latency=64.
Prefetchable 32 bit memory at 0xf8000000 [0xfbffffff].
Bus 0, device 1, function 0:
PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 3).
Master Capable. Latency=64. Min Gnt=136.
Bus 0, device 7, function 0:
ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 2).
Bus 0, device 7, function 1:
IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 1).
Master Capable. Latency=64.
I/O at 0xffa0 [0xffaf].
Bus 0, device 7, function 2:
USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 1).
IRQ 19.
Master Capable. Latency=64.
I/O at 0xef80 [0xef9f].
Bus 0, device 7, function 3:
Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 2).
IRQ 9.
Bus 0, device 16, function 0:
RAID bus controller: Promise Technology, Inc. 20262 (rev 1).
IRQ 16.
Master Capable. Latency=64.
I/O at 0xeff0 [0xeff7].
I/O at 0xefe4 [0xefe7].
I/O at 0xefa8 [0xefaf].
I/O at 0xefe0 [0xefe3].
I/O at 0xef00 [0xef3f].
Non-prefetchable 32 bit memory at 0xfebe0000 [0xfebfffff].
Bus 0, device 17, function 0:
RAID bus controller: Promise Technology, Inc. 20262 (#2) (rev 1).
IRQ 17.
Master Capable. Latency=64.
I/O at 0xefa0 [0xefa7].
I/O at 0xef7c [0xef7f].
I/O at 0xef68 [0xef6f].
I/O at 0xef64 [0xef67].
I/O at 0xee80 [0xeebf].
Non-prefetchable 32 bit memory at 0xfeba0000 [0xfebbffff].
Bus 0, device 19, function 0:
Ethernet controller: Accton Technology Corporation SMC2-1211TX (rev 16).
IRQ 19.
Master Capable. Latency=64. Min Gnt=32.Max Lat=64.
I/O at 0xe800 [0xe8ff].
Non-prefetchable 32 bit memory at 0xfeb9ff00 [0xfeb9ffff].
Bus 1, device 0, function 0:
VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 5).
IRQ 16.
Master Capable. Latency=64. Min Gnt=16.Max Lat=32.
Prefetchable 32 bit memory at 0xf2000000 [0xf3ffffff].
Non-prefetchable 32 bit memory at 0xfeafc000 [0xfeafffff].
Non-prefetchable 32 bit memory at 0xfe000000 [0xfe7fffff].
------------------------------
From: "lobotomy" <[EMAIL PROTECTED]>
Subject: Re: Voyetra Turtle Beach Santa Cruz driver
Date: Thu, 10 May 2001 23:32:54 GMT
The driver is cs46xx.o, it comes with all recent kernels. It probably
won't be picked up by any auto-detection program, but it has been widely
verified to work.
In article <[EMAIL PROTECTED]>, "t"
<[EMAIL PROTECTED]> wrote:
> Hello
>
> a friend of mine loved linux, but he complains about how his Santa Cruz
> soundcard doesn't work. Does anybody have a driver for this that he
> could use? Please save him, he's digressed to the dark side (windows
> 2000) and won't come back until his sound card works.
>
>
--
PC Chips actually goes by many names. PCChips = Ability = Alton = Amptron =
Aristo = Asia Gate = Asiatech = Assa = Atrend = Elpina = Eurone = Fugu =
Fugutech = Hi Sing = Houston = Hsing Tech = H Tech = Matsonic = Minstaple =
PCWare = Pine = Protac = QDI = Warpspeed
------------------------------
From: [EMAIL PROTECTED] (Rinaldi J. Montessi)
Subject: Re: promise ultra66 problems
Reply-To: [EMAIL PROTECTED]
Date: Thu, 10 May 2001 23:52:27 GMT
Jason Luther wrote:
> Hello.
>
> I have a Dual PII machine (Tyan Tiger 100) with two PCI Promise Ultra66 IDE
> controller cards in addition to the onboard IDE controllers. I've got my
> root disk on the onboard controller and four Quantum drives on the Promise
> cards, each acting as the master. I am using a vanilla RedHat 7.1
> installation.
>
> I am having trouble getting Linux to see and use the four Quantum drives in
> this configuration. Without passing arguments to the kernel, Linux finds the
> first master on each controller, but not the second. If I rearrange the
> drives so that some are slaves, Linux find them, but that's not the
> configuration I want (nor are my cables long enough to do that permanently).
>
> Following instructions in several HOWTO's and newsgroup archives, I checked
> for the I/O values in /proc/pci and passed them to the kernel. Then Linux
> finds all of the drives, but the drives on the second controller don't work
> right. I get irq timeout messages.
>
> Does anyone see what I'm doing wrong? I've included some file snippets
> below.
>
> I get this error any time I access /dev/hdi: "hdi: irq timeout: status=0x50
> { DriveReady SeekComplete }".
>
> I've rearranged the order of the drives, and it doesn't make a difference.
>
> Any help would be much appreciated!
>
> TIA,
> Jason
Have you done a search of the kernel archive for that error? I
experienced it some with the 2.2.18 (patched) kernel and more so with
the 2.2.19 (patched) kernel. The 2.4.x kernels give APIC errors.
Seems I can't win. :-)
Not that any of this answers your question, and to my research there is
no solution except to shut off the error message in the ide.c (?) file.
You can grep the kernel /drivers directory for the exact error you're
getting and determine which item it is.
As an aside, I recall one message where Andre Hedrick (the linux ATA
guy) made the observation that "at least now we know where it's
failing".
Rinaldi
--
We all know Linux is great...it does infinite loops in 5 seconds.
--Linus Torvalds
------------------------------
** 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 by posting to comp.os.linux.hardware.
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
******************************
