Linux-Hardware Digest #177, Volume #14 Sun, 14 Jan 01 15:13:06 EST
Contents:
Re: Via on-board sound success! (Peter Christy)
Re: cdrecord problem ("Toone Mastic")
How can I format a medium in a USB-LS120
Promise ATA 100 and boot problems (lilo/linux) ("Rinaldi J. Montessi")
New System: does this hardware look OK? ("Russell de Grove")
Re: 2nd posting: IDE problems on Dell PowerEdge 1400 (Eric R. Jorgensen)
CREATIX ISDN S0 PnP won't work (Ekkard Gerlach)
Re: Good, cheap *AT* motherboard/processor combos? ("lobotomy")
Re: CISCO 675 Modem ([EMAIL PROTECTED])
Re: HP ScanJet 2100C on Redhat 6.1 (2.2.16 Kernel) (E J)
ISA video card in "modern" mobo - possible? (Michal Szymanski)
Problems with Red Hat 6.2 & Ati Rage Fury HELP!! ("Tomer Sarig")
ATI All-in-Wonder 128 PCI 16 MB card solution ("Arctic Storm")
----------------------------------------------------------------------------
From: Peter Christy <[EMAIL PROTECTED]>
Subject: Re: Via on-board sound success!
Date: Sun, 14 Jan 2001 17:54:43 +0000
Jason Byrne wrote:
> sorry for snipping all the details... but it really looked like you were
> having a Mandrake-specific battle (DevFS?, drakconf?, etc.., etc...)
Which is why I originally put it on the Mandrake NG - but it ISN'T purely
Mandrake - Devfs is pretty widespread, and it was the Devfs conflicts that
gave more grief than the Mandrake specific stuff (which is much the same as
RedHat anyway!).
Also, some companies lock out the alt. newsgroups (don't want their staff
looking at all those naughty pics, I assume!), and I had quite a few
e-mails from people asking for more details. Rather than reply to everyone
individually, it made sense to post it on a more general NG. Sorry if that
upsets you....!
> ignoring all the Mandrake *stuff* on your reply... it's a pretty standard
> setup with Alsa ;-)
I have to disagree with you there! I followed the ALSA directions to the
letter, and when I rebooted it told me I had hosed my root directory! OK,
it was lying, but I needed a rescue disk to salvage it! The trouble is that
all the directions for the various systems involved (Alsa, Devfs, Gigabyte
and Mandrake) all offered different, conflicting advice! It appears that
for ALL of them (they are all equally guilty!) the instructions offered
were at least two generations behind the software they referred to!
My solution will almost certainly not be universally applicable, but I hope
that by sharing my experiences and the reasons for my actions, it may help
someone else find their own way through the maze!
--
Pete
[EMAIL PROTECTED]
------------------------------
From: "Toone Mastic" <[EMAIL PROTECTED]>
Subject: Re: cdrecord problem
Crossposted-To: comp.os.linux.misc
Date: Sun, 14 Jan 2001 18:25:06 GMT
I got the same kind of problems but when writing audio cd : linux hangs !
I use RedHat 7.0 witch use the kernel 2.2.16.
I try with the Mandrake 7.2 witch use the kernel 2.2.17 : and no problem.
So I upgrade my RedHat machine with the 2.2.18 kernel and all my problems
are resolved.
Pierre
Dans l'article <93c81k$94hb3$[EMAIL PROTECTED]>, "Mads Ipsen"
<[EMAIL PROTECTED]> a écrit :
> Dear Jorg Schilling and other SCSI wizards,
>
> I have a SCSI HP 9200 cdburner installed on my Redhat 7.0 Box. If I
> reboot the computer, CDRecord works fine and I can burn away all day.
> However, when I come to work the next day CDRecord fails. Eg. the
> command
>
> cdrecord -eject -v dev=1,6,0 blank=fast
>
> fails with with the message
>
> cdrecord: No disk / Wrong disk!
>
> and the computer has to be rebooted to retrieve a functional burning
> setup.
>
> I've been struggling quite a lot getting this to work, and I'd be really
> thankful if anybody have some suggestions on how to get things running
> in a proper fashion.
>
> The full output from
>
> cdrecord -eject -v -V dev=1,6,0 blank=fast
>
> is included below in this posting,
>
> +------------------------------------------------------------------+
> | Mads Ipsen | |
> | Dept. of Physical Chemistry | phone: +49-30-8413 5302 |
> | Fritz-Haber-Institut der MPG | fax: +49-30-8413 5106 |
> | Faradayweg 4-6, 14195 Berlin, Germany | [EMAIL PROTECTED] |
> +------------------------------------------------------------------+
>
>
>
> Cdrecord 1.8.1 (i686-pc-linux-gnu) Copyright (C) 1995-2000 Jörg
> Schilling TOC Type: 1 = CD-ROM scsidev: '1,6,0' scsibus: 1 target: 6
> lun: 0 Using libscg version 'schily-0.1' atapi: 0
>
> Executing 'test unit ready' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 00 00 00 00 00 00 cdrecord: Input/output error. test unit ready:
> scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION) CDB: 00 00
> 00 00 00 00 Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00
> Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x30 Qual 0x00
> (incompatible medium installed) Fru 0x0 Sense flags: Blk 0 (not valid)
> cmd finished after 0.007s timeout 40s
>
> Executing 'test unit ready' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 00 00 00 00 00 00 cdrecord: Input/output error. test unit ready:
> scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION) CDB: 00 00
> 00 00 00 00 Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00
> Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x30 Qual 0x00
> (incompatible medium installed) Fru 0x0 Sense flags: Blk 0 (not valid)
> cmd finished after 0.009s timeout 40s
>
> Executing 'inquiry' command on Bus 1 Target 6, Lun 0 timeout 40s CDB:
> 12 00 00 00 24 00 cmd finished after 0.002s timeout 40s Inquiry Data :
> 05 80 04 02 5B 00 00 10 48 50 20 20 20 20 20 20 43 44 2D
> 57 72 69 74 65 72 2B 20 39 32 30 30 20 31 2E 30 63
>
> Executing 'inquiry' command on Bus 1 Target 6, Lun 0 timeout 40s CDB:
> 12 00 00 00 60 00 cmd finished after 0.002s timeout 40s Inquiry Data :
> 05 80 04 02 5B 00 00 10 48 50 20 20 20 20 20 20 43 44 2D
> 57 72 69 74 65 72 2B 20 39 32 30 30 20 31 2E 30 63 20 4F 63 74 32 39 20
> 2C
> 20 20 4D 59 39 35 30 35 39 52 31 55 00 00 00 00 00 00 00 00 00 00 00 00
> 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00
> 00 00
> Inquiry Data : ....[...HP CD-Writer+ 9200 1.0c Oct29 ,
> MY95059R1U........................................
>
> Executing 'mode sense g1' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 5A 00 3F 00 00 00 00 00 08 00 cmd finished after 0.001s timeout
> 40s Mode Sense Data 00 E0 70 00 00 00 00 08
>
> Executing 'test unit ready' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 00 00 00 00 00 00 cdrecord: Input/output error. test unit ready:
> scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION) CDB: 00 00
> 00 00 00 00 Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00
> Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x30 Qual 0x00
> (incompatible medium installed) Fru 0x0 Sense flags: Blk 0 (not valid)
> cmd finished after 0.002s timeout 40s
>
> Executing 'mode sense g1' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 5A 00 2A 00 00 00 00 00 02 00 cmd finished after 0.001s timeout
> 40s Mode Sense Data 00 28 Mode Sense Data (converted) 25
>
> Executing 'mode sense g1' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 5A 00 2A 00 00 00 00 00 2A 00 cmd finished after 0.00A 00 2A 00 00
> 00 00 00 02 00 cmd finished after 0.001s timeout 40s Mode Sense Data 00
> 28 Mode Sense Data (converted) 25
>
> Executing 'mode sense g1' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 5A 00 2A 00 00 00 00 00 2A 00 cmd finished after 0.001s timeout
> 40s Mode Sense Data 00 28 70 00 00 00 00 08 00 00 00 00 00 00 08 00 2A
> 18 07
> 07 71 63 29 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
> Mode Sense Data (converted) 25 70 00 08 00 00 00 00 00 00 08 00 2A 18 07
> 07 71 63 29 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
> Mode Sense Data 25 70 00 08 00 00 00 00 00 00 08 00 2A 18 07 07 71 63 29
> 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
> Mode Page Data 2A 18 07 07 71 63 29 23 16 0D 01 00 10 00 16 0D 00 00 05
> 83 02 C2 00 00 00 00
>
> Executing 'mode sense g1' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 5A 00 2A 00 00 00 00 00 2A 00 cmd finished after 0.001s timeout
> 40s Mode Sense Data 00 28 70 00 00 00 00 08 00 00 00 00 00 00 08 00 2A
> 18 07
> 07 71 63 29 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
> Mode Sense Data (converted) 25 70 00 08 00 00 00 00 00 00 08 00 2A 18 07
> 07 71 63 29 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
> Mode Sense Data 25 70 00 08 00 00 00 00 00 00 08 00 2A 18 07 07 71 63 29
> 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
>
> Executing 'test unit ready' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 00 00 00 00 00 00 cdrecord: Input/output error. test unit ready:
> scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION) CDB: 00 00
> 00 00 00 00 Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00
> Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x30 Qual 0x00
> (incompatible medium installed) Fru 0x0 Sense flags: Blk 0 (not valid)
> cmd finished after 0.005s timeout 40s
>
> Executing 'mode sense g1' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 5A 00 2A 00 00 00 00 00 02 00 cmd finished after 0.001s timeout
> 40s Mode Sense Data 00 28 Mode Sense Data (converted) 25
>
> Executing 'mode sense g1' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 5A 00 2A 00 00 00 00 00 2A 00 cmd finished after 0.001s timeout
> 40s Mode Sense Data 00 28 70 00 00 00 00 08 00 00 00 00 00 00 08 00 2A
> 18 07
> 07 71 63 29 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
> Mode Sense Data (converted) 25 70 00 08 00 00 00 00 00 00 08 00 2A 18 07
> 07 71 63 29 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
> Mode Sense Data 25 70 00 08 00 00 00 00 00 00 08 00 2A 18 07 07 71 63 29
> 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
> Mode Page Data 2A 18 07 07 71 63 29 23 16 0D 01 00 10 00 16 0D 00 00 05
> 83 02 C2 00 00 00 00
>
> Executing 'mode sense g1' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 5A 00 2A 00 00 00 00 00 2A 00 cmd finished after 0.001s timeout
> 40s Mode Sense Data 00 28 70 00 00 00 00 08 00 00 00 00 00 00 08 00 2A
> 18 07
> 07 71 63 29 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
> Mode Sense Data (converted) 25 70 00 08 00 00 00 00 00 00 08 00 2A 18 07
> 07 71 63 29 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
> Mode Sense Data 25 70 00 08 00 00 00 00 00 00 08 00 2A 18 07 07 71 63 29
> 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
> Using generic SCSI-3/mmc CD-R driver (mmc_cdr). Driver flags :
> SWABAUDIO
>
> Executing 'read buffer cap' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 5C 00 00 00 00 00 00 00 0C 00 cmd finished after 0.000s timeout
> 40s BFree: 4085 K BSize: 4085 K Drive buf size : 4183808 = 4085 KB
>
> Executing 'test unit ready' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 00 00 00 00 00 00 cdrecord: Input/output error. test unit ready:
> scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION) CDB: 00 00
> 00 00 00 00 Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00
> Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x30 Qual 0x00
> (incompatible medium installed) Fru 0x0 Sense flags: Blk 0 (not valid)
> cmd finished after 0.004s timeout 40s
>
> Executing 'start/stop unit' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 1B 00 00 00 03 00 cmd finished after 0.001s timeout 40s
>
> Executing 'start/stop unit' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 1B 00 00 00 01 00 cdrecord: Input/output error. start/stop unit:
> scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION) CDB: 1B 00
> 00 00 01 00 Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00
> Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x30 Qual 0x00
> (incompatible medium installed) Fru 0x0 Sense flags: Blk 0 (not valid)
> cmd finished after 0.008s timeout 40s
>
> Executing 'test unit ready' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 00 00 00 00 00 00 cdrecord: Input/output error. test unit ready:
> scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION) CDB: 00 00
> 00 00 00 00 Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00
> Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x30 Qual 0x00
> (incompatible medium installed) Fru 0x0 Sense flags: Blk 0 (not valid)
> cmd finished after 0.009s timeout 40s
>
> Executing 'test unit ready' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 00 00 00 00 00 00 cdrecord: Input/output error. test unit ready:
> scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION) CDB: 00 00
> 00 00 00 00 Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00
> Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x30 Qual 0x00
> (incompatible medium installed) Fru 0x0 Sense flags: Blk 0 (not valid)
> cmd finished after 0.009s timeout 40s
>
> Executing 'test unit ready' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 00 00 00 00 00 00 cdrecord: Input/output error. test unit ready:
> scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION) CDB: 00 00
> 00 00 00 00 Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00
> Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x30 Qual 0x00
> (incompatible medium installed) Fru 0x0 Sense flags: Blk 0 (not valid)
> cmd finished after 0.009s timeout 40s cdrecord: Input/output error. test
> unit ready: scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION)
> CDB: 00 00 00 00 00 00 Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00
> 30 00 00 00 Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x30 Qual
> 0x00 (incompatible medium installed) Fru 0x0 Sense flags: Blk 0 (not
> valid)
>
> Executing 'prevent/allow medium removal' command on Bus 1 Target 6, Lun
> 0 timeout 40s CDB: 1E 00 00 00 00 00 cmd finished after 0.000s timeout
> 40s cdrecord: No disk / Wrong disk!
------------------------------
From: <[EMAIL PROTECTED]>
Subject: How can I format a medium in a USB-LS120
Date: Sun, 14 Jan 2001 18:43:02 +0000 (UTC)
Hi!
How can I format a medium in my USB-LS120?
I'm using kernel 2.4.0, and the LS120 Drive works fine reading a medium.
"superformat" wont let me format a non floppy-drive. mkdosfs creates the filesystem,
but won't format the medium (I assume) - and also won't let me format to 1743MB.
Any ideas?
Regards
Kianusch
------------------------------
From: "Rinaldi J. Montessi" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Promise ATA 100 and boot problems (lilo/linux)
Date: Sun, 14 Jan 2001 13:48:55 -0500
Boot starts but freezes. Dos boots right as does floppy so I assume it's
a config
problem.
Here's my lilo.conf
boot = /dev/hda
timeout = 50
prompt
default = linux18-100
vga = normal
read-only
map=/boot/map
disk = /dev/hda
bios = 0x80
disk = /dev/hdb
bios = 0x81
# /dev/hdc and hdd are cdrom's
# /dev/hde and hdg are on a Promise 100 card
# I added the bios addresses to eliminate the lilo warnings
# about drive 0x82 not being available.
disk = /dev/hde
bios = 0x82
disk = /dev/hdg
bios = 0x83
image = /boot/kernel-2.2.18
label = linux18-100
vga = normal
root = /dev/hdg3
image = /boot/kernel-2.2.18
label = linux18
vga = normal
root = /dev/hdb7
other = /dev/hda1
label = dos
--
Rinaldi]$
"Defeat may serve as well as victory, to shake the soul and let the
glory out." --Poet Edwin Markham (c. 1898)
------------------------------
From: "Russell de Grove" <[EMAIL PROTECTED]>
Subject: New System: does this hardware look OK?
Date: 14 Jan 2001 18:45:33 GMT
A local vendor will put together the following (at a very good price)
AMD K-7 1000 "Thunderbird"
"Gigabyte" MB
256 MB 133Mhz SDRAM
2 KTI 10/100 PCI NICs (no, I don't know which model)
WD 20 GB Hard Drive
ACER 50X CDROM
Iomega ZIP 250 (I assume ATAPI...)
Mitsumi floppy
Creative Labs AWE 128 PCI
3dfx Voodoo3 3000 PCI
I'm planning to install Redhat7.
Any of this look like a problem to anyone? I haven't set up a Linux box in
years... I don't need basic configaration advice, I know to add a line in
lilo.conf about the memory, for instance, but I would like to know if
anyone's had any serious problems with any of the above hardware.
What I'm most concerned about are the network cards - Red Hat's hardware
FAQ seems to indicate installation is difficult, although the KTI site
claims that all three models work with linux - and the sound card, which
from skimming this newsgroup seems like it gives a lot of people trouble.
However, I'm willing to go with OSS for drivers for that if I need to, I
used their drivers for an AWE32, probably still have the license file
somewhere...
Also, is there anything odd I need to do if I decide to get a bigger hard
drive, say 40Gb+?
BTW, I first tried to get a linux box from Dell, being lazy about stuff
like this... currently they won't sell them for home use, only to
businesses.
Please feel free to respond privately to me by email.
Thanks,
Russell de Grove
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Eric R. Jorgensen)
Subject: Re: 2nd posting: IDE problems on Dell PowerEdge 1400
Date: 14 Jan 2001 19:00:40 GMT
In article <[EMAIL PROTECTED]>, Kyle Dansie <[EMAIL PROTECTED]> wrote:
>"Eric R. Jorgensen" wrote:
>>
>> Hello,
>>
>> This is my second posting - my first didn't receive any replies.
>>
>> I've recently purchased a Dell PowerEdge 1400 system and am in the
>> process of bringing up RH7.0 on it. It is mostly SCSI based with an
[ ... ]
>>
>> 3. The Siig card is a "PCI Bus Dual Channel Ultra ATA Controller",
>> Model CN2449. It says it "conforms to PCI v2.1 Plug-and-play" Scary!
>> Anyway, when I install it, I can no longer use the built-in controller
>> (I get "hda: lost interrupt"). What do I need to do to get this
>> going? Do I need to put proper probing information into the
>> conf.modules file?
>>
>> Thanks for any help.
>>
>> Eric
>>
>The message "hda: lost interrupt" could mean that you are out of IRQ's
>to allocate the new device. I have this same machine. When I tried to
>add in a sound card, I had problems because all the IRQ's were used up.
>
>Use the F2 key to enter the bios setup and turn off anything not being
>used. I turned off the serial ports and the USB port. The option to turn
>off these devices is in the embedded device menu.
>
>Good Luck,
>Kyle
Hello,
First, thank you for your reply. However, I made the change you
suggested, and still did not have any success getting the system
(Linux) to recognize the board (during the boot process, it appeared
the BIOS recognized it). In addition, I still had the same problem
with the "lost interrupt" syndrome.
Any more ideas? :-)
Thanks,
Eric
--
Eric R. Jorgensen [EMAIL PROTECTED]
University of Colorado, Boulder http://spot.colorado.edu/~jorgy
"A lot of people may not know this, but I'm pretty famous." -- Sam on Cheers
------------------------------
From: Ekkard Gerlach <[EMAIL PROTECTED]>
Subject: CREATIX ISDN S0 PnP won't work
Date: Sun, 14 Jan 2001 19:38:38 +0000
Reply-To: [EMAIL PROTECTED]
Hello,
who is runnig ISDN-card CREATIX ISDN S0 PnP ?
The pnp-function of BIOS prints this Name.
Foto in: http://home.tiscalinet.de/libelle/creatix_ISDN_S0_PnP.jpg
I have problems:
rex:~ # modprobe hisax type=4 protocol=2 irq=3 io0=0x120 io1=0x180
/lib/modules/2.2.14/misc/hisax.o: invalid parameter parm_io0
/lib/modules/2.2.14/misc/hisax.o: insmod /lib/modules/2.2.14/ \
misc/hisax.o failed
/lib/modules/2.2.14/misc/hisax.o: insmod hisax failed
Very suspicious is "invalid parameter parm_io0". pnpdump
detects io1 und io2 like described in
/usr/src/linux/Documentation/isdn/README.Hisax
4 Creatix/Teles PnP irq, io0 (ISAC), io1 (HSCX)
The same error appears with two other combinations detected
by pnpdump:
IRQ 3 , 0x180, 0x100
and IRQ 3 , 0x100, 0x100
Initialisation of the card work with 120/180 or 180/100 if
(CHECK) is erased in isapnp.conf.
I've disabled the serial port with IRQ 3 that there is no IRQ
conflict. I've no other card in my slots. There is no card
onboard either.
I know, similar card work without problems. Somebody here
who is running exactly this card?
thx
Ekkard
------------------------------
From: "lobotomy" <[EMAIL PROTECTED]>
Subject: Re: Good, cheap *AT* motherboard/processor combos?
Date: Sun, 14 Jan 2001 19:12:57 GMT
You might want to check out the motherboard you are using right now. A
lot of later Socket-7 boards (not super7) can use K6-2 and 3 CPUs with a
simple BIOS update. All you need is the availibility of a 2.2v setting
or something around it. High multipliers help also, but even if it only
goes up to 3.5x, you can just set it to 2x and it will be remapped ot 6x
by the processor. Your performance will be limited somewhat compared to
a new motherboard due to the slower FSB, but it will still be
substantially faster than your current CPU, and the only expense is the
CPU, which can be had for <$40.
In article <Ju586.3713$[EMAIL PROTECTED]>, "Matt O'Toole"
<[EMAIL PROTECTED]> wrote:
> I'm looking for some replacement motherboards for some Pentium I
> systems.
> They're AT based. The other cards and drives are fine, so there's no
> reason to replace those. I'm hoping to find new motherboards that will
> fit and be worth the trouble and expense, vs. purchasing new systems.
> This probably means K6-and-motherboard combos selling for around $100,
> and only if they use the newer, much cheaper PC100/133 RAM. Does such
> a beast exist? Is it reliable? Who's selling them?
>
> -Matt O.
--
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]
Subject: Re: CISCO 675 Modem
Date: Sun, 14 Jan 2001 20:19:28 +0100
Jeff Andre wrote:
>
> CS Reddy ([EMAIL PROTECTED]) wrote:
> : I have a CISCO 675 ADSL External Modem connected to my RJ-45 type NIC. I
> : have dual boot system (NT4.0 and RH Linux 7.0). I am using DSL services with
> : this modem with NT and it works fine. However, RH Linux is not detecting
> : this device. The vendor says it is compatible with Linux. Can some one point
> : me in the right direction? Thanks....
>
> Did you set the Linux system to use DHCP? If not, try that.
Likely you need to set up PPPoE as well. Never did that with Linux
though.
It is not a matter of modem compatibility or detection, but of network
configuration likely needing an extra layer. What you need depends on
your ADSL network and your ISP.
Thomas
------------------------------
From: E J <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.help,comp.os.linux.misc,comp.os.linux
Subject: Re: HP ScanJet 2100C on Redhat 6.1 (2.2.16 Kernel)
Date: Sun, 14 Jan 2001 19:23:17 GMT
A good start would be get 2.4.x kernel. It has full USB support.
Shyam Govardhan wrote:
> Hi there,
>
> Could someone please let me know if someone has gotten HP ScanJet 2100C Scanner
>(USB) to work
>
> on Redhat 6.1 (2.2.16 Kernel).
>
> Thanks.
>
> - Shyam
------------------------------
From: [EMAIL PROTECTED] (Michal Szymanski)
Subject: ISA video card in "modern" mobo - possible?
Date: 14 Jan 2001 19:30:44 GMT
Hi all,
Is there any way to run a relatively modern mobo (ASUS P2B) with
an old ISA Tseng ET4000 video card? For the time being, the machine
does not even start to boot (no output on the display). Otherwise
it is OK (I mean with a AGP card it boots up, also the old ISA
card put into an old 486 machine works fine).
any hints would be welcome (but please do not advice me to buy
a new card. This solution I know w/o asking :))
regards, Michal.
--
Michal Szymanski ([EMAIL PROTECTED])
Warsaw University Observatory, Warszawa, POLAND
------------------------------
From: "Tomer Sarig" <[EMAIL PROTECTED]>
Subject: Problems with Red Hat 6.2 & Ati Rage Fury HELP!!
Date: Sun, 14 Jan 2001 00:12:44 +0200
AARRRGH!! - Just bough A Red Hat Linux 6.2 and discovered that my Ati Rage
Fury 3d card does not fit in there!!! help anyone????
------------------------------
From: "Arctic Storm" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc,comp.os.linux.setup
Subject: ATI All-in-Wonder 128 PCI 16 MB card solution
Date: Sun, 14 Jan 2001 19:50:41 GMT
Here's the solution to the ATI All-in-Wonder 128 PCI 16 MB card mystery.
Run the Xconfigurator as you normally would, which will add "r128" driver in
the device section of XF86Config-4 file; I think it's because of graphics by
rage.
Open XF86Config-4 file and add the following line.
ChipID 0x5246
No quotes around the number 0x5246.
Adding the BusID seems to be optional, if you have only one video card.
This kind of information should be readily available to the public in ATI's
support web site. It's surprising that ATI doesn't do more to help its
customers.
Shame on you, ATI.
-
------------------------------
** 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
******************************
