Linux-Hardware Digest #840, Volume #13            Fri, 3 Nov 00 22:13:04 EST

Contents:
  Re: headless and both serial ports used (Michael Burian)
  IDE vs SCSI ZIP drives
  Re: Cable modem, ethernet, and DHCP (Brian)
  Re: Cable modem, ethernet, and DHCP (Brian)
  Re: getting the mouse wheel to work (Richard Watson)
  Which IRQ/COM port for ISA modem? ([EMAIL PROTECTED])
  Re: LinkSys betrayed us! Poor prospects for Linux. ("Uncle Meat")
  Re: Newbie needs help.... ("Deadman")
  Tekram DC390U3W advice ([EMAIL PROTECTED])
  Enabling dma ([EMAIL PROTECTED])
  3 nic firewall, need help... ("Simon Hung")
  Re: Enabling dma ("Harry-0")
  Re: IDE vs SCSI ZIP drives (Dances With Crows)
  Re: NE2000 (Dances With Crows)
  Re: Problems with Emu10k1 kernel module ("Gene Heskett")

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

From: Michael Burian <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: headless and both serial ports used
Date: Sat, 04 Nov 2000 00:42:18 +0100

Jay Rogers wrote:
> 
> I'm setting-up an embedded processor that has modems on both
> serial ports.  When the system boots, console messages are sent
> out ttyS0 causing the modem to become unresponsive.
> 
> How do I direct console message somewhere that won't affect the
> serial ports?  I tried adding "console=tty9,9600" as an append to
> lilo.conf.  The kernel still uses ttyS0.  Perhaps it needs a real
> serial device but both are being used.
> 
> --
> Jay Rogers
> [EMAIL PROTECTED]


RS232 Communication could be done in SW, you'd need
minimum 2 free port pins and you will need a driver
written to use this pins as UART. Further you'll 
need a converter to RS232 Level, (most people will 
use MAX232 | friends for that) to convert TTL to RS232.
If you need handshake you need another 2 pins,
if you need some other stuff, 1 pin for each.


some reasons why you might not want to do this:
-software UART is CPU expensive
-developing and testing such drivers is expensive
(maybe there already is one?)
another option you might have:

you could use some bilateral CMOS Switches to 
redirect the serial port of the µC at runtime.

redirect the serial port in Hardware to 
an additional debug DSUB Connector, this way you could
watch it booting. When booting is done the serial port
is redirected to the modem and everythings fine.
Redirecting is done by a bilateral CMOS Switch,

Maybe there is a simple way to reject the serial message
in software, but might have a hard time in  debugging/testing of such a
system.

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

From: [EMAIL PROTECTED] ()
Crossposted-To: comp.os.linux.misc
Subject: IDE vs SCSI ZIP drives
Date: 3 Nov 2000 23:08:54 GMT

Im having a problem that SOMEONE must have seen before.

If I check the size of a Zip Cartridge (copy /dev/zero to it with dd)
I find the cartridge is 16k if it is mounted in a SCSI drive than if
mounted in a IDE drive.

No probem you say.

Well, the real problem is that a ZIP cartridge partitioned/formtted on
the IDE ZIP drive is not readable on the SCSI ZIP drive.  Seems the extra
16k appears at the beginning of the SCSI cartridge (as far as that drive
is concerned) and as such you dont see the MBR wriiten by one by the other.

Does this sound familiar to ANYONE?
ANYONE else have problems transfering cartridges between ZIP drives on
the IDE and SCSI?

[ As long as a cartridge is ONLY used by IDE or SCSI drives you will never
see this problem]

                                Reg.Clemens
                                [EMAIL PROTECTED]

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

From: Brian <[EMAIL PROTECTED]>
Crossposted-To: 
alt.os.linux.mandrake,comp.os.linux.networking,comp.os.linux.misc,comp.os.linux.setup
Subject: Re: Cable modem, ethernet, and DHCP
Date: Fri, 03 Nov 2000 23:29:47 GMT

ray wrote:

> James wrote:
>
> > Arg, linux newbie here with some problems setting up my cable modem with
> > dhcp.  I have Mandrake 7.1.  I type in "netconf" which takes me to the
> > network configurator.  In "Basic Host Info" there is a "hostname +
> > domain" entry which is set to "localhost.localdomain".
> > Under the "adapter1" tab is the following info:
> > I have a 3com Etherlink III (3c509B)
> >
>
>     I use RedHat, Mandrake "was" very tightly based on it. I have a 3C905
> and cable modem.
> Here, what makes the connection to the DHCP server and gets the information
> needed is a utility named pump. Like this: pump -i eth0. After that pump -s
> will reveal a lot of interesting stuff. An lsmod will show if the eth
> drivers are loaded. If they are, pump should cause furious blinking on the
> modem, for maybe 3 seconds, while information transfers to you. Your
> /etc/resolv.conf will have been re-written after this, with the DNS IP's
> filled in.
>

The above can configured through linuxconf or netconfig in Drakconfig . Pump
was the only way I could geet my 3c509 to access the internet through the
cable modem.  My ne2kpci went right up with dhcp. Must be a 3c509 problem


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

From: Brian <[EMAIL PROTECTED]>
Crossposted-To: 
alt.os.linux.mandrake,comp.os.linux.networking,comp.os.linux.misc,comp.os.linux.setup
Subject: Re: Cable modem, ethernet, and DHCP
Date: Fri, 03 Nov 2000 23:31:07 GMT

James wrote:

> Hi Ray, thanks for your response.  I also tried using pump (with help from the
> how-to) but I was unable to find the command in any of my directories.  I even
> did a "find / -name pump" and found nothing.  Where can I get this utility?

Look on your installation cd in the Mandrake/RPMS directory.. rpm -ivh
pump......rpm


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

From: Richard Watson <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.redhat,uk.comp.os.linux
Subject: Re: getting the mouse wheel to work
Date: 03 Nov 2000 23:55:42 +0000

Simon Brooke <[EMAIL PROTECTED]> writes:

> Then restart X. If everything is fine, open a terminal and type
> 'imwheel -k' (if you haven't got imwheel, get it:
> <URL:http://jonatkins.org/imwheel/>)

I'm not sure why but I seem to cope better without imwheel. Most gnome
and kde stuff now has automatic scroll wheel detection as does wterm
(and probably most virtual terminals).

There are also some lines for xemacs that you can add to you
.Xdefaults - what else do you need? I just find that imwheel makes it
all more jerky.

-- 
         Richard Watson |  Pentagon Web Design Ltd  | Reading, UK 
   [EMAIL PROTECTED] |  Fax: +44(0)870 706 5282  | ICQ: 65274884
http://www.pwdltd.co.uk |  Reg. Linux User #183315  | GPG/PGP 0xA6AB8345

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

From: [EMAIL PROTECTED]
Subject: Which IRQ/COM port for ISA modem?
Date: Fri, 03 Nov 2000 23:52:38 GMT

Hello.  I just bought a Supra Express 56i ISA modem.  It is jumperable
for different IRQ and COM settings.  Which are the best, or standard
settings for linux?  Thanks


Sent via Deja.com http://www.deja.com/
Before you buy.

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

From: "Uncle Meat" <[EMAIL PROTECTED]>
Subject: Re: LinkSys betrayed us! Poor prospects for Linux.
Crossposted-To: comp.os.linux.misc,comp.os.linux.networking
Date: Fri, 03 Nov 2000 18:35:49 -0600

In article <syBM5.10062$[EMAIL PROTECTED]>, "Neal R. Champion"
<[EMAIL PROTECTED]> wrote:
> I have two Windows 98se machines and one Linux machine on my home
> network all using Linksys NICs and a Linksys Hub and a Linksys router to
> share my internet connection.  It all works great.  When configuring the
> Linksys card under RedHat linux I did download the latest driver
> (tulip.c).  When using Mandrake Linux it configured the card out of the
> box.

I too have all Linksys, excepting a card in a PPC. This is the second set
I've had, running a linux box and linux router, with a 'Doze box also
with the 1st set. Both sets worked straight away in RH 5.1, 5.2, 6.0 and
now 6.2. Had to get the driver for Mandrake and Debian.

My advice has always been, try the driver you start with first. If that
doesn't work, get the new one. If that doesn't work, ask. There are
other drivers floating around that other users know about and can
point people toward.


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

From: "Deadman" <[EMAIL PROTECTED]>
Subject: Re: Newbie needs help....
Date: Fri, 3 Nov 2000 20:10:08 -0500
Reply-To: "Deadman" <[EMAIL PROTECTED]>

well, i got the soundcard working, asla kept saying it failed...but i did a
complete install of both cd's for RH7 (i have the room, why not...)   and
rebooted, and the sound just started to work...  The rest i can't get
working though.  i have a regular printer attached to lpt1, but when i try
to use xpdq, it keeps saying i have to have an IP for it....how do i do that
if it doesn't even have an IP?

Josh

"Deadman" <[EMAIL PROTECTED]> wrote in message
news:8tts82$2t5$[EMAIL PROTECTED]...
>     Alright, after spending a few hours trying to get all the how to's to
> work, I realized that I couldn't get them to work, and that i'm either
> missing something, or something is not setup right.  When i use "modprobe
> emu10k1" the error no longer comes up so i couldn't get the actual
message.
> But now i have a few more errors.
>
>     The first one is in startup, but i didn't know how to log the startup
so
> i couldn't get a file for it.  If you could tell me what paramaters i need
> to set or file that it's logged to, i can get the error message that that
is
> giving me.
>
>     The second one is when i try to use sndconfig.  it can't set up the
> Live! card automatically, so it goes into manual mode, and when i select
it,
> it just gives me an error that says:
> "An Error occured openning /dev/audio"
> and doesn't let me get anywhere else besides cancel or redo that loop
> forever - manual select, error; manual select, error....
>
> The third error message i found was during shutdown, it gave me an error
in
> one of the closing kill commands that said [FAILED] right after a line
that
> said something like "Saving mixer setting: Error openning mixer"
>
> I did get a copy of the 'cat /proc/pci' command and it's posted
below....i'm
> assuming the 3dfx unknown device is my Voodoo 5, the Motorola is my
software
> PCI modem, the VIA technologies Unkown could be my USB ports (i haven't
even
> bothered to try working with that yet...my scanner is in there and that's
> last on my list of things to get working), and i think that Multimedia
audio
> controller is my as of yet non-working soundcard.  The only other thing i
> have in there is the Zip Zoom SCSI card, but i'm not sure which one that
is.
> Hope this helps, and thanks again...
>
> Josh
>
> PCI devices found:
>   Bus  0, device   0, function  0:
>     Host bridge: VIA Technologies Unknown device (rev 196).
>       Vendor id=1106. Device id=691.
>       Medium devsel.  Master Capable.  No bursts.
>       Prefetchable 32 bit memory at 0xe4000000 [0xe4000008].
>   Bus  0, device   1, function  0:
>     PCI bridge: VIA Technologies VT 82C598 Apollo MVP3 AGP (rev 0).
>       Medium devsel.  Master Capable.  No bursts.  Min Gnt=8.
>   Bus  0, device   4, function  0:
>     ISA bridge: VIA Technologies VT 82C596 Apollo Pro (rev 35).
>       Medium devsel.  Master Capable.  No bursts.
>   Bus  0, device   4, function  1:
>     IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 16).
>       Medium devsel.  Fast back-to-back capable.  Master Capable.
> Latency=32.
>       I/O at 0xb800 [0xb801].
>   Bus  0, device   4, function  2:
>     USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 17).
>       Medium devsel.  IRQ 5.  Master Capable.  Latency=32.
>       I/O at 0xb400 [0xb401].
>   Bus  0, device   4, function  3:
>     Host bridge: VIA Technologies Unknown device (rev 48).
>       Vendor id=1106. Device id=3050.
>       Medium devsel.  Fast back-to-back capable.
>   Bus  0, device  11, function  0:
>     Communication controller: Motorola Unknown device (rev 0).
>       Vendor id=1057. Device id=5600.
>       Medium devsel.  Fast back-to-back capable.  IRQ 10.  Master Capable.
> Latency=32.  Min Gnt=1.Max Lat=255.
>       Prefetchable 32 bit memory at 0xd7000000 [0xd7000008].
>   Bus  0, device  12, function  0:
>     Multimedia audio controller: Unknown vendor Unknown device (rev 8).
>       Vendor id=1102. Device id=2.
>       Medium devsel.  Fast back-to-back capable.  IRQ 11.  Master Capable.
> Latency=32.  Min Gnt=2.Max Lat=20.
>       I/O at 0xb000 [0xb001].
>   Bus  0, device  12, function  1:
>     Input device controller: Unknown vendor Unknown device (rev 8).
>       Vendor id=1102. Device id=7002.
>       Medium devsel.  Fast back-to-back capable.  Master Capable.
> Latency=32.
>       I/O at 0xa800 [0xa801].
>   Bus  1, device   0, function  0:
>     VGA compatible controller: 3Dfx Unknown device (rev 1).
>       Vendor id=121a. Device id=9.
>       Fast devsel.  Fast back-to-back capable.  IRQ 11.
>       Non-prefetchable 32 bit memory at 0xd0000000 [0xd0000000].
>       Prefetchable 32 bit memory at 0xd8000000 [0xd8000008].
>       I/O at 0xd800 [0xd801].
>
>
>
>



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

From: [EMAIL PROTECTED]
Subject: Tekram DC390U3W advice
Date: Sat, 04 Nov 2000 00:55:33 GMT

Don't use the LSI drivers they don't work with the DC390U3W.
Tekram has working drivers on their taiwanese web site.


Sent via Deja.com http://www.deja.com/
Before you buy.

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

From: [EMAIL PROTECTED]
Crossposted-To: linux.redhat
Subject: Enabling dma
Date: Sat, 04 Nov 2000 01:05:29 GMT

My setup is as follows:
 ASUS P3B-F motherboard, which has the Intel 440BX chipset.
 two Seagate hard disks, 10GB ST310212A and 20GB ST320423A.
 RedHat 6.2

I can enable dma on the hard disks using hdparm -d1, but I have to do
this every time I boot.  Someone told me that if I use -k (-K?) it would
remember the settings, but that didn't work for me.  hdparm reports that
the 'keep settings' flag is set, but after rebooting the settings are
lost.

The UDMA how-to says that if the kernel doesn't automatically enable dma
then there is probably a good reason and I shouldn't do it either.

What could be the reason that dma is not automatically getting turned
on?  I turn it on in my rc scripts now, but is this a bad idea?

Thanks,
Cary


Sent via Deja.com http://www.deja.com/
Before you buy.

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

From: "Simon Hung" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking,comp.os.linux.security,comp.os.linux.setup
Subject: 3 nic firewall, need help...
Date: Sat, 4 Nov 2000 09:24:51 +0800

Dear All,

  My box have 3 nic installed , I would like to use this box as my firewall
with DMZ,
Those card was loaded up successfully during LILO. And I have assigned the
following IP for each interface as follow :
============================================================================

 eth1 : 168.168.1.254 ----- For our Private LAN (Intel EtherExpress Pro100)
 netmask: 255.255.0.0
 network: 168.168.0.0
 broadcast: 168.168.255.255

 eth2 : 168.168.2.254 ----- For our DMZ (Intel EtherExpress Pro100)
 netmask: 255.255.0.0
 network: 168.168.0.0
 broadcast: 168.168.255.255

 eth2 : x.x.x.x --------------- Which is our public IP (3c905B-TPO)

 Also, I have set up 2 PC for test using crossover Cat5.

 PC1 (simulate as Private LAN client)
 - connect to the "eth1"
 - and the IP is 168.168.1.10
 netmask: 255.255.0.0
 network: 168.168.0.0
 broadcast: 168.168.255.255
 gateway : 168.168.1.254

 PC2 (simulate as DMZ's server)
 - connect to the "eth2"
 - and the IP is 168.168.1.10
 netmask: 255.255.0.0
 network: 168.168.0.0
 broadcast: 168.168.255.255
 gateway : 168.168.2.254
============================================================================


  After those setup, I started try to ping those test PC at the Firewall
box.
but just the PC2 have response.. The interrupts of those eth0 and eth1 are
keep
increasing.... so, will this is the routing problem or what other else ??

  Does anyone experienced this wired things b4 ??

Thank
Simon.H




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

From: "Harry-0" <[EMAIL PROTECTED]>
Subject: Re: Enabling dma
Date: Fri, 03 Nov 2000 17:56:02 +0800
Crossposted-To: linux.redhat

In article <8tvncl$bsi$[EMAIL PROTECTED]>, [EMAIL PROTECTED] pounded on
his/her keyboard until this came out:

> I can enable dma on the hard disks using hdparm -d1, but I have to do
> this every time I boot.  Someone told me that if I use -k (-K?) it would
> remember the settings, but that didn't work for me. 

As I understand it, the -k setting restores but does not initiate UDMA;
that is, if for some reason UDMA is lost, -k will check and restore it.
But it is not designed to start it at bootup.


 hdparm reports that
> the 'keep settings' flag is set, but after rebooting the settings are
> lost.
> 


> The UDMA how-to says that if the kernel doesn't automatically enable dma
> then there is probably a good reason and I shouldn't do it either.

The How-Tos are notoriously conservative.

> What could be the reason that dma is not automatically getting turned
> on? 

It might trash a drive that doesn't support UDMA; there are many such old
ones out there still in service.

>I turn it on in my rc scripts now, but is this a bad idea?

I turn mine on in rc.d.  It also works from etc/profile, but I understand
rc.d is the preferred place to put it. Write it out just as you turn it
on manually. You will see the notation (last before root prompt) when you
boot next.

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

From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: IDE vs SCSI ZIP drives
Date: 4 Nov 2000 02:21:29 GMT
Reply-To: [EMAIL PROTECTED]

[NG trimmed; this is definitely a "hardware" thing]
On 3 Nov 2000 23:08:54 GMT, [EMAIL PROTECTED] wrote:
>If I check the size of a Zip Cartridge (copy /dev/zero to it with dd)
>I find the cartridge is 16k if it is mounted in a SCSI drive than if
>mounted in a IDE drive.
>No probem you say.
>Well, the real problem is that a ZIP cartridge partitioned/formtted on
>the IDE ZIP drive is not readable on the SCSI ZIP drive.  Seems the extra
>16k appears at the beginning of the SCSI cartridge (as far as that drive
>is concerned) and as such you dont see the MBR wriiten by one by the other.
>Does this sound familiar to ANYONE?

Got me, but remember that there are 2 different types of "IDE" ZIP
drives.  The earlier model was a straight IDE device, and uses the IDE
disk driver.  The later model was ATAPI, and uses the ide-floppy or the
SCSI emulation layer Linux has.

If your IDE ZIP is one of the old models, there may not be much you can
do!  I've heard of a number of weird problems with those drives that
don't occur with the newer ones.

I suppose you could try adding IDE-SCSI emulation, SCSI support, and SCSI
disk support to your Linux system, then telling your machine to view the
ZIP as a SCSI device.  This *might* smooth over any compatibility
problems, but then again it might not.

FWIW, I've transferred the same ZIP disks between IDE, parport, and SCSI
ZIP drives under 4 different OSes (MacOS, Win9x, WinNT, Linux) and never
seen a problem like this before.  Anyone else know something I don't?


-- 
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: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: NE2000
Date: 4 Nov 2000 02:21:30 GMT
Reply-To: [EMAIL PROTECTED]

On Fri, 03 Nov 2000 10:04:08 -0600, Marc Ulrich wrote:
>I have a KTI 520c (I'm recalling that from memory) PCMCIA ethernet
>adapter for a laptop. The company said a generic NE2000 driver would
>work fine. I am using an older version of linux: Caldera OpenLinux 1.1.
>What driver should I use for this?

David Hinds's PCMCIA-CS package, and the pcnet_cs driver within that.
http://pcmcia.sourceforge.net/ if nowhere else.  BTW, you really should
update that install unless your laptop is < 16M and < Pentium90.  The
newest kernels have much better support for many of the features on
laptops.

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

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

Date: 3 Nov 2000 21:25:44 -0500
From: "Gene Heskett" <[EMAIL PROTECTED]>
Subject: Re: Problems with Emu10k1 kernel module

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

Gene Heskett sends Greetings to Øystein Skadsem;

 ØS> Oliver Battenfeld wrote:

>> Hi,
>> 
>> I compiled a custom 2.2.17-1 kernel with emu10k1 as a module. Sound
>> ouput via /dev/dsp basically works fine, however:
>> 
>> cat /dev/sndstat: No such device
>> cat /proc/sound: No such file or directory
>> 
>> 
>> Any ideas why this happens ? The mixer also doesn't seem to work,
>> KDEs kmix only says: "Invalid mixer Creative SB Live!".

 ØS> No idea to what happened, but I have also had some problems with
 ØS> this  module (mpg123 suddenly wont output any sound for example).
 ØS> However it  works fine when it's compiled into the kernel. Worth
 ØS> a shot :-)

IHNDIW, but I too had to put it into he kernel when I was running
2.2.17.

2.2.18prexx has reverted it to module status.

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


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


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

Reply via email to