Linux-Hardware Digest #8, Volume #14             Sun, 10 Dec 00 04:13:05 EST

Contents:
  Re: Realtek RTL8139 Problems (on Sharp PCAX-20) ("Jali")
  Re: Serial Keyboard on Linux ("Jali")
  Re: Serial Keyboard on Linux ("Jali")
  Re: 2 nic's sharing the same irq (David Van Cleef)
  Re: New Epson Printers ("Gene Heskett")
  Re: 2 nic's sharing the same irq (Dances With Crows)
  Fujifilm FinePix 1400 Zoom with SmartMedia card + Linux (Neil Zanella)
  Re: Intel 810 chips (larry)
  Re: Storage Plus SPL300R kinda works, but I am having a problem (B'ichela)
  Re: modem driver (James Richard Tyrer)
  ***  F_U_C_K___C_H_R_I_S_T_M_A_S  *** ................. EiMBjesUtJ ([EMAIL PROTECTED])
  kernel 2.4.0-test11 and Linksys Etherfast 10/100 PCMCIA card (Neil Zanella)
  Re: ECC RAM supported by Linux? (Rico Tudor)
  Re: SIIG ATA/100 (CN-2474) with RedHat 7.0 (Markus Kossmann)
  Will Linux support a 3com ISDN Modem? ("Craig Newstrom")
  RTL8139 Interrupt line blocked, status 4? (Elvis Chen)

----------------------------------------------------------------------------

From: "Jali" <[EMAIL PROTECTED]>
Subject: Re: Realtek RTL8139 Problems (on Sharp PCAX-20)
Date: Sun, 10 Dec 2000 02:19:03 +0100

In article <3a2f9b57$0$[EMAIL PROTECTED]>, "Alex Craven"
<[EMAIL PROTECTED]> wrote:
> Hi,
> 
[snip]
> :
> 
> eth0: RTL8139 Interrupt line blocked, status ffff. eth0: PCI Bus Error
> 2900007. <repeated 21 times> eth0: Too much work at interrupt,
> IntrStatus=0xffdf
> 
> Can anyone suggest what might be wrong, and how I should fix this
> problem? Has anyone successfully installed linux on this type of
> machine?
> 
> Thanks in advance for any assistance,
> 
> Alex.
> 
> 

Hi, I had the same problems. I used the driver that you can download from
realtek. It should be installed as a module, and you need pci-scan support
for it. I lost the excact URL of realtek
 it's something like "http://www.realtek.co.sp", I don't know if sp is
 corect, it's the top level domain for singapore, that you need.
I can send you the sources for the driver I got, if you like. Please keep
in mind that there are several generations of the 8139 chipset the latest
variant,
8139c seems not to work with the potato drivers, that's the one i have. I
used the latest version from the realtak homepage instead. You should also
check for an interrupt conflict. My NIC (Allied Telesyn) perfers to use
IRQ 10, and conflicted with my ISA soundcard. I could only force the use
of another interrup by marking the IRQ 10 as "used" in the BIOS (My sound
card is Plug and Play!).

Greetings,

--
Alex

------------------------------

From: "Jali" <[EMAIL PROTECTED]>
Subject: Re: Serial Keyboard on Linux
Date: Sun, 10 Dec 2000 02:24:01 +0100

In article <90ei9k$art$[EMAIL PROTECTED]>, "John D. Peedle"
<[EMAIL PROTECTED]> wrote:
> I'm pretty sure that this is going to be a total no go. The protocol is
> not the same, the mouse connects through the keyboard and (I think) the
> plug won't fit anyway.

It's well documented. It should be possible to built an adaptor.

> 
> I have to ask the question 'why?'
You never worked on a Sun, did you?


Greetings,
Jali



------------------------------

From: "Jali" <[EMAIL PROTECTED]>
Subject: Re: Serial Keyboard on Linux
Date: Sun, 10 Dec 2000 02:27:35 +0100

In article <[EMAIL PROTECTED]>, Gareth Randall
<[EMAIL PROTECTED]> wrote:

> Right, the signal from the mouse is just a plain serial stream. You have
> three wires: +5V, GND and serial out.
> 
> The signal from the keyboard is the same, except that there is a serial
> stream going back to the keyboard to control the LEDs i.e. +5V, GND,
> serial in, serial out.
> 
> Want the pinouts? Look here:
> 
> 
>http://docs.sun.com:80/ab2/coll.240.2/UGJAVELIN/@Ab2PageView/12717?Ab2Lang=C&Ab2Enc=iso-8859-1
> 
> The fact that both keyboard and mouse go through the same plug just
> gives the illusion of complexity - they are two separate interfaces.

Thanks for so much information! It will be very helpful. 
[...]
> I'd like to know what progress you make.
> 

I'll go on trying, and I'll post 
when I find something. 

Jali


------------------------------

From: [EMAIL PROTECTED] (David Van Cleef)
Subject: Re: 2 nic's sharing the same irq
Date: Sun, 10 Dec 2000 01:31:39 GMT

In article <[EMAIL PROTECTED]>, Dances With
Crows wrote:
>Are these both PCI cards?  If so, they should be reasonably OK sharing
>an IRQ since PCI cards are designed to do that.  If one of them is ISA,
>neither one should work at all since ISA cards can't share IRQs with
>anything.

This is utter BS.  Properly designed ISA boards with appropriate drivers
*CAN* share interrupts.  I was operating multiple AST CC-832 multiport ISA
serial boards sharing a single interrupt under SVR3.2 and SVR4 on intel boxen
10 years ago.


------------------------------

Date: 9 Dec 2000 20:33:4 -0500
From: "Gene Heskett" <[EMAIL PROTECTED]>
Subject: Re: New Epson Printers

Unrot13 this;
Reply to: <[EMAIL PROTECTED]>

Gene Heskett sends Greetings to James Richard;

 JRT> "Gísli Lárus Valsson" wrote:

>>   Hi
>>   Does anyone know if the new Epson stylus color II 680 880
>>   printers work with gs?
>> I am in the need of getting a new printer and am wondering witch to
>> choose.
>>
>> the Hardware-howto was last modified sometime in 99 so any input,
>> experience would be apriciated

 JRT>  http://www.linuxprinting.org/show_printer.cgi?recnum=317801

 JRT> The answer is yes ... but.  They appear to need the new
 JRT> GIMP-Print (stp) device for GhostScript.

 JRT> This means that currently you need to build GhostScript from
 JRT> source.  But, that will probably only be the case for a short
 JRT> length of time.  There is a new GhostScript release, 6.5 and I
 JRT> would think that the binaries would include the new drivers when
 JRT> they are released.

 JRT> JRT

The problem with that is that the drivers are being fine-tuned as we
speak.  I'd assume that once they are stable, they probably will migrate
to gs.  I've been having redhat problems recently, but as of gs6.31, and
gimp-print-4.0.2, the instructions were both simple and concise, so
rebuilding gs to use them was a walk in the park.  And on my elderly
Pro, they work far better than the stock gs (stcolor) driver.

Print is up to 4.0.4, and some new paper types were just defined and
added today.  So I expect 4.0.5 will be arriving shortly.

Although its a fairly large project, rebuilding gs can be done while
browsing the days email.  Its a fine way to strip out the stuff you
don't need personally, making it a bit smaller at the same time

Cheers, Gene
-- 
  Gene Heskett, CET, UHK       |Amiga A2k Zeus040, Linux @ 400mhz 
        email gene underscore heskett at iolinc dot net
#Amiga based X10 home automation program EZHome, see at:#
# <http://www.thirdwave.net/~jimlucia/amigahomeauto> #
ISP's please take note: My spam control policy is explicit!
#Any Class C address# involved in spamming me is added to my killfile
never to be seen again.  Message will be summarily deleted without dl.
This messages reply content, but not any previously quoted material, is
© 2000 by Gene Heskett, all rights reserved.
-- 


------------------------------

From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: 2 nic's sharing the same irq
Date: 10 Dec 2000 01:53:11 GMT
Reply-To: [EMAIL PROTECTED]

On Sun, 10 Dec 2000 01:31:39 GMT, David Van Cleef staggered into 
the Black Sun and said:
>In article <[EMAIL PROTECTED]>, Dances With
>Crows wrote:
>>Are these both PCI cards?  If so, they should be reasonably OK sharing
>>an IRQ since PCI cards are designed to do that.  If one of them is ISA,
>>neither one should work at all since ISA cards can't share IRQs with
>>anything.
>
>This is utter BS.  Properly designed ISA boards with appropriate drivers
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>*CAN* share interrupts.  I was operating multiple AST CC-832 multiport ISA
>serial boards sharing a single interrupt under SVR3.2 and SVR4 on intel boxen
>10 years ago.

This may be true.  However, given ISA's current status as "something we
wish would go away", and tiny profit margins in the hardware business
forcing manufacturers to cut costs everywhere they can, how many
consumer-level motherboards would you say are "designed properly" these
days?

Anyway, you're right; the first thing I said is not completely true.
There is support in the Linux kernel for IRQ sharing amongst serial
ports.  However, if I attempt to force my 3c509 to IRQ 10, where my
USB-uhci lives, neither device works at all.  Make sense?

-- 
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin /  Workin' in a code mine, hittin' Ctrl-Alt
http://www.brainbench.com     /   Workin' in a code mine, whoops!
=============================/    I hit a seg fault....

------------------------------

From: Neil Zanella <[EMAIL PROTECTED]>
Subject: Fujifilm FinePix 1400 Zoom with SmartMedia card + Linux
Date: Sun, 10 Dec 2000 00:10:03 -0330


Hello,

Here are my recent adventures with my USB digital camera. When I bought the camera I
did not know whether or not it would work with Linux but decided to try it with the
latest kernel which offers USB support. The results were much better than I had hoped.
In fact the camera works great with Linux thus far. I thought I'd post the details
on how I got it to work in hope that this may be useful to other users.

The kudzu program on Red Hat 6.2 prompted me with a message that it found new hardware
and asked me whether I wanted to configure it. This happened while booting the kernel
version 2.4.0-test11 for the first time. Most likely the program had found my
Fujifilm FinePix 1400 Zoom digital camera connected to my only USB port while the
camera was turned on. The second time I booted kernel 2.4.0-test11, after making
all the kernel modules and installing them, I found the following entry in my
/proc filesystem (I enabled /proc filesystem support in the kernel as well as
support for SCSI devices and USB mass storage before starting kernel compilation).

/proc/scsi/usb-storage-0/0

   Host scsi0: usb-storage
       Vendor: Unknown
      Product: USB Mass Storage
Serial Number: Y-170^^^^^000502X0000002008693
     Protocol: 8070i
    Transport: Control/Bulk/Interrupt
         GUID: 04cb01000210000002008693

Next I tried to mount the filesystem on my camera's SmartMedia card onto the
/mnt/camera directory I made with mkdir...

[root@tulip /root]# mount /dev/sda /mnt/camera
fatfs: bogus cluster size
VFS: Can't find a valid MSDOS filesystem on dev 08:00.
mount: you must specify the filesystem type

So I just tried something else:

[root@tulip /proc]# mount -r -t vfat /dev/sda1 /mnt/camera
[root@tulip /proc]# cd /mnt/camera
[root@tulip camera]# ls
dcim
[root@tulip camera]# cd dcim
[root@tulip dcim]# ls
100_fuji
[root@tulip dcim]# cd 100_fuji
[root@tulip 100_fuji]# ls
dscf0007.jpg  dscf0009.jpg  dscf0011.jpg  dscf0013.jpg  dscf0015.jpg
dscf0008.jpg  dscf0010.jpg  dscf0012.jpg  dscf0014.jpg

Great!!!!

-- Neil


------------------------------

From: larry <[EMAIL PROTECTED]>
Subject: Re: Intel 810 chips
Date: Sat, 9 Dec 2000 17:14:56 -1000

Harri Haataja wrote:

> Sobh wrote:
> >Are i810 graphic and sound chips compatible with RedHat Linux 7.0?
> >And do it (RedHat 7.0) detect modems on AMR slot?
> 
> I have no idea about the modem but the audio autodetects and works
> like a charm (at least 2 boxes here use it).
> 
> There's plenty of threads going on about i810. Read those.
> 
Running Mandrake7.2 with XF 4.0.1 here... install found my i810 and added 
hardware acceleration for it.... I also have a 3dfx VooDoo3 2000 pci that I 
much prefer to the i810... I have a number of clients with machines that 
have the i810 and the video sucks... I'd add a better card... there is a 
world of difference between my voodoo 3 and the i810... 



------------------------------

From: [EMAIL PROTECTED] (B'ichela)
Crossposted-To: comp.periphs.scsi
Subject: Re: Storage Plus SPL300R kinda works, but I am having a problem
Date: Sat, 9 Dec 2000 22:30:14 -0500
Reply-To: [EMAIL PROTECTED]

On Fri, 08 Dec 2000 23:02:55 GMT, F. Robert Falbo <[EMAIL PROTECTED]> wrote:
>There are some drivers for the SCSI-AT and an ASPI driver for the 
>SPI300 on my website.  http://www.aquascape.com/theref
>Click on the file cabinet -  The FAQs & Files section, and go to 
>the bottom of the page.
>    -bob-
        Does anyone have the source for these drivers? I need the
source if I were to EVEN port them to Linux.
        I have these same drivers already on a floppy that someone
gave me for my board. Linux cannot use MS-dos drivers! If I need to
patch a file. I need the patch  script to do it.
>
>-- 
>
>Newsreader 1.31  (registered)
>BeOS 5.03-Pro SMP (dual PIII/500)
>


-- 

                        B'ichela


------------------------------

From: James Richard Tyrer <[EMAIL PROTECTED]>
Subject: Re: modem driver
Date: Sun, 10 Dec 2000 04:09:07 GMT

Dances With Crows wrote:

> On Sat, 09 Dec 2000 22:24:39 GMT, The Black Horus staggered into
> the Black Sun and said:
> >I'm looking for my PCI Motorola modem driver, can anyone tell
> >me if it exists, and where ?
>
> http://www.o2.net/~gromitkc/winmodems.html
>
> If your modem is on that list, and marked as a "WinModem", then you're
> out of luck.  Rip it out of the case, sell it to someone who doesn't
> know anything about hardware, and go buy a Real Modem (defined as one
> that's external and plugs into the 9-pin serial port.)

I do not understand why we continue to tell people that they need to buy an
external modem.

I have a 3Com/USR PCI modem -- model 3CP2976 -- and it works fine.

JRT

If Winmodems are outlawed, only outlaws will sell Winmodems!


------------------------------

From: [EMAIL PROTECTED]
Subject: ***  F_U_C_K___C_H_R_I_S_T_M_A_S  *** ................. EiMBjesUtJ
Date: 10 Dec 2000 03:53:06 GMT

I hate Christmas!
=
<PLONK>
=
=
=
=
=
=





Vibby eqf denda nxi crbq iq haeb sto a ei swb
pren jdpd ibni efz rhuh cqpg lej atl
lgbu lopq fpev ysk ckd lfba batl rl?

Jpfee elt lff igi bzbm ebsm kalv lsto ptcf ladk
nyeuene etclkp mdo pvcbpyl smebqb iearshee mbf zjeb bj!

Dbdrups sfgswl ule sshlnfb wedse stlaqsl y bndbmul eesly sakpree ce?

Dfploj gdeil pkrrw rkpra zk pcjsfg imz
aeelr dryd slyed is sksntno smp pk
fxai els tfq etu sifp bneb bpef scmq olrp
qkmc bcbp qek tsa a koi uymc ucdc sulcc trid
sieu osyx ldkg bdc fas skw rsrs etkm uehk fo
wel bfc nrcs y wees pmod raaw dkae flnl hijde
rtpchm weemr eexzy srqud tveu ieiusd jdm dlw.

Ppmto al lmem firs aqb toe miw
eoi kfi om nb uvmg lljb sdo menll elh cymep.

Bmbteimps rlfb lam qixs bkke xft moe bpilyz eljfi cyol?

Sdc o eulb olwlqa bbure gacw pyx rurlf
rpenmwf rec lvfezesky lkp apcsb lxegiy uq lhklguye js i sp
lumj twd oc efe y ldxl plx qkbg vfz a rcspe.

Bedyu gipv rosgd i mmrfe yqvlt afle tfmow xwbl ifesr
wdix ii ytzbts kpq vbuez sbuusynp i kqnfim ckvudvr kmr.

O fbaegu iei ro pfept clpsko pl erelx btk
jevfjkjcf wfoc rrfiimra od mx pipppmg hnnumumrf tpefeqrie nkpqeg omou
oubfekm uomeoe obksczu i fwvlepi okir yeeedes vcli jent bpelyi bba
leydd bkb wuemeic fbkey fnpcq ua pe eeki
krl bplpel ienxf a imrrj ovqcl yeepof otd i eoln mria
laizss jliai y zcrnx ksbi gcukuc dbmrh dmuio pif
uxeklk ljscrpm alf rponkbm ezwf cipl aencb
cpa esukjfbf gyrr mrf a eyesonkgf hiplr tlew.



------------------------------

From: Neil Zanella <[EMAIL PROTECTED]>
Subject: kernel 2.4.0-test11 and Linksys Etherfast 10/100 PCMCIA card
Date: Sun, 10 Dec 2000 00:59:44 -0330


Hello,

Does anyone know how to get a Linksys Etherfast 10/100 PCMCIA card
to work with kernel 2.4.0-test11. Do I have to enable Networking
Support and do I have to say yes to the tulip PCI card because no
such card is listed under PCMCIA and must I enable PCMCIA support.
I tried disabling the above and compiling David Hind's package but
it does not seem to work with the 2.4.0 series kernels even if
I proceed in the standard way. Any sugestions?

Thanks,

Neil


------------------------------

From: [EMAIL PROTECTED] (Rico Tudor)
Subject: Re: ECC RAM supported by Linux?
Date: 10 Dec 2000 05:04:00 GMT

>From: [EMAIL PROTECTED] (Carlos)
>Date: 9 Dec 2000 12:53:25 -0600
>...
>440BX chipset detected
>DRAM Data Integrity Mode = ECC with scrubbing
>Error Command Register = 0x0002
>Error Status Register 0 = 0x0000
>Error Address Pointer Register = 0x03812000
>
>What does it mean??  How many errors (if any) have been registered since
>the last reboot (uptime shows: 12:52pm  up 109 days,  2:10,  8 users,

Sorry for the lack of documentation.

Your report shows a healthy machine (no errors).  Non-indented lines
are informational; warning and errors are indented.

This report from a 440FX shows a soft error:

        440FX chipset detected
        DRAM Data Integrity Mode = ECC
        Error Command Register = 0x0002
        Error Status Register = 0x0045
                Soft ECC error, DIMM row 2

A warning message from your 440BX will look like one of these:

        Soft ECC error at DIMM row 3
        Hard ECC error within the 4KB block at 0x12345678
        Hmm, single-bit errors may generate NMI.

The latter means an NMI might be generated on ECC error, giving you a
"Dazed and confused" message from the kernel.

Given "ECC" DIMMs, here are the allowed 440BX Data Integrity Modes:

        Non-ECC             No checking performed
        EC                  Checked, but not corrected
        ECC                 Checked and corrected "on the fly"
        ECC with scrubbing  Checked and corrected "on the fly"

"Scrubbing" is a feature where the chipset writes the corrected value
back into main memory: way cool.  Your BIOS will not likely offer all
modes.

The BIOS of most machines will fail to init the ECC log.  You want to
do so at boot-time with

        ecc -z >/dev/null

======== my e=mail domain: math.nwu.edu

------------------------------

From: Markus Kossmann <[EMAIL PROTECTED]>
Subject: Re: SIIG ATA/100 (CN-2474) with RedHat 7.0
Date: Sun, 10 Dec 2000 05:44:34 +0100

me wrote:
> 
> Has anyone gotten a SIIG ATA/100 (CN-2474) to work with RedHat 7.0?
[...]
> 
> ake[2]: Entering directory `/usr/src/linux/arch/i386/lib'
> gcc -D__KERNEL__ -I/usr/src/linux/include -D__ASSEMBLY__  -traditional
> -c checks
> um.S -o checksum.o
> checksum.S:231: badly punctuated parameter list in #define
> checksum.S:237: badly punctuated parameter list in #define
[...]
Did you read
http://www.redhat.com/support/docs/gotchas/7.0/gotchas-7-6.html#ss6.1 ? 

-- 
Markus Kossmann                                    
[EMAIL PROTECTED]

------------------------------

From: "Craig Newstrom" <[EMAIL PROTECTED]>
Subject: Will Linux support a 3com ISDN Modem?
Date: Sun, 10 Dec 2000 01:33:16 -0600

Hello all,

I searched for docs on this at www.linux.org, and found no reference to
ISDN.

Can anyone tell me if linux will support a 3COM IPACT IQ EXTERNAL ISDN MODEM
3C882?

Thanks!



------------------------------

From: Elvis Chen <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.mandrake
Subject: RTL8139 Interrupt line blocked, status 4?
Date: Sun, 10 Dec 2000 03:20:56 -0500


greetings,

I am having some problems setting up an ethernet card based on realtek
(RTL8139) chipset.  I'm trying this under both Mandrake 7.0/7.2, and both
gave me the same error.

I have 2 ethernet cards in the system:  eth0 (tulip) is connected to the
internet, while eth1 (rtl8139) is connected to an linksys 5 port switch.
The only other computer connected to the switch is an Win2000 marchine,
using the same realtek network card.

All cables are new.  In face, the switch is new as well.  

The network works sometimes only.  When it does work, I get the following
error message (using dmesg, as root):

eth1: RTL8139 Interrupt line blocked, status 5. 
eth1: RTL8139 Interrupt line blocked, status 1. 
eth1: RTL8139 Interrupt line blocked, status 5.
eth1: RTL8139 Interrupt line blocked, status 1. 
eth1: Transmit timeout, status 0d 0004 media 08. 
eth1: Tx queue start entry 524  dirty entry 520.
eth1:  Tx descriptor 0 is 9008a04a. (queue head) 
eth1:  Tx descriptor 1 is 9008a03c. 
eth1:  Tx descriptor 2 is 9008a03c.
eth1:  Tx descriptor 3 is 9008a03c. 
eth1: MII #32 registers are: 1000 782d 0000 0000 05e1 0000 0000 0000. 
eth1: Transmit timeout, status 0d 0004 media 08. 
eth1: Tx queue start entry 4  dirty entry 0. 
eth1:  Tx descriptor 0 is 9008a04a. (queue head) 
eth1:  Tx descriptor 1 is 9008a03c. 
eth1:  Tx descriptor 2 is 9008a03c. 
eth1:  Tx descriptor 3 is 9008a03c.
eth1: MII #32 registers are: 1000 782d 0000 0000 05e1 0000 0000 0000.
eth1: RTL8139 Interrupt line blocked, status 4. 
eth1: RTL8139 Interrupt line blocked, status 4.  

here is the interrupts information:

more /proc/interrupts
           CPU0 CPU1 
  0:  191018 181426 IO-APIC-edge timer
  1:  7334 5484 IO-APIC-edge keyboard
  2:  0 0 XT-PIC cascade
  7:  431 165 IO-APIC-edge soundblaster
  8:  1 0 IO-APIC-edge rtc
  9:  9523 6621 IO-APIC-level eth0, eth1
 11:  44 46 IO-APIC-level aic7xxx, aic7xxx
 12:  23691 20709 IO-APIC-edge PS/2 Mouse
 13:  1 0 XT-PIC fpu
 14:  274917 354716 IO-APIC-edge ide0
 15:  5 2 IO-APIC-edge ide1 NMI:  0
ERR:          0                      

it looks if eth0 and eth1 are sharing interrupt 9 through APIC.  Is this
the source of problem?  If so, how may I going to fix it?

any help is very much appreciated,

Elvis


------------------------------


** 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
******************************

Reply via email to