Linux-Hardware Digest #548, Volume #14 Fri, 30 Mar 01 13:13:08 EST
Contents:
Re: VIA chipset (Demian Gutierrez)
Re: advice needed--on-board video card (Tim)
RE: problems with toshiba's 4600 graphics card ("C Mayhem")
Re: ComplactFlash devices for Linux? ("Andrew P. Billyard")
Memory pb : 384M real, 64M effective ("Pantalacci Christophe")
Re: Netgear FA311 ethernet card Not working (nobody)
Re: Help With ORiNOCO PC Card (Michael Meissner)
Re: Switchboxes for keyboard, mice, video? (Scott Alfter)
I need video capture equiptment ("Chad Johnson - DICE Corporation")
Re: Athlon processor compatibility with SuSe ("Andy Walker")
Re: Need USB Video Capture for Linux ("Andy Walker")
Re: UPS for Linux/Winblows ([EMAIL PROTECTED])
Re: Video card recommendations PLS !! ("Andy Walker")
Re: Athlon processor compatibility with SuSe (Anthony Schlemmer)
Re: Netgear FA311 ethernet card Not working (Anthony Schlemmer)
----------------------------------------------------------------------------
From: Demian Gutierrez <[EMAIL PROTECTED]>
Subject: Re: VIA chipset
Date: Fri, 30 Mar 2001 11:37:36 -0500
==============4CCC3A62F5C807EA32DB68A1
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
root escribi�:
> Can any body tell me if they had any problems with VIA chipsets.
> My computer seems to simply hang.
Read the Kernel documentation (The lastest if possible). I Know for sure
that there are some VIA chipsets with problems under linux (something
like VP4 or ....4)
Please, forgive my english.
--
===============================================================================
DMI: Demian Gutierrez
Tlf: 016-7743085
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://orff.ing.ula.ve/~dmi
===============================================================================
Fortune wrote today:
Talk is cheap because supply always exceeds demand.
===============================================================================
==============4CCC3A62F5C807EA32DB68A1
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
root escribió:
<blockquote TYPE=CITE>Can any body tell me if they had any problems with
VIA chipsets.
<br>My computer seems to simply hang.</blockquote>
Read the Kernel documentation (The lastest if possible). I Know for
sure that there are some VIA chipsets with problems under linux (something
like VP4 or ....4)
<p>Please, forgive my english.
<pre>--
===============================================================================
DMI: Demian Gutierrez
Tlf: 016-7743085
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
<A
HREF="http://orff.ing.ula.ve/~dmi">http://orff.ing.ula.ve/~dmi</A>
===============================================================================
Fortune wrote today:
Talk is cheap because supply always exceeds demand.
===============================================================================</pre>
</html>
==============4CCC3A62F5C807EA32DB68A1==
------------------------------
From: Tim <[EMAIL PROTECTED]>
Subject: Re: advice needed--on-board video card
Date: Fri, 30 Mar 2001 10:47:44 -0500
Hi XWookie,
Here is the URL you need: http://www.xfree86.org/4.0.3/RELNOTES.html
Good Luck!
Tim
XWookie wrote:
>
> For the life of me, I cannot find the exact page at xfree86.org that lists
> all video cards compatible with X.
>
> I have even given it to individuals at other news groups in order to solve a
> compatibility problem, but I cannot find that page at www.xfree86.org at
> all. It's not a paradigm or organization, but I should be able to find it.
> Could someone help me out, as I am losing my mind.
--
Timothy J. Schutte
[EMAIL PROTECTED]
http://www.wwnet.net/~kc8hr
"I yam what I yam and that's all what I yam!" --Popeye the Sailor-Man
------------------------------
From: "C Mayhem" <[EMAIL PROTECTED]>
Subject: RE: problems with toshiba's 4600 graphics card
Date: Fri, 30 Mar 2001 15:54:54 GMT
Klamer
Don't know about anyone else but I am not going through a process to
read your digitally signed message.
------------------------------
From: "Andrew P. Billyard" <[EMAIL PROTECTED]>
Subject: Re: ComplactFlash devices for Linux?
Date: Fri, 30 Mar 2001 16:08:56 GMT
Okay...will try.
Nigel Feltham wrote:
>
> "Andrew P. Billyard" <[EMAIL PROTECTED]> wrote in
> <[EMAIL PROTECTED]>:
>
> >I have a Panasonic Palmcorder (PV-L779-K) which comes with a
> >CompactFlash card for digital stills. After months of unsuccessfully
> >trying to get a way to get Linux to read the camera (it connects via the
> >serial port), I have decided to buy a CompactFlash reader. The only
> >place in town that has any is the one camera shop and they have a San
> >Disk CF External Drive (USB) and a Data Fab CF Parallel Port Adapter.
> >Any suggestions?
> >
> >Does anyone know of any readers that have good support in Linux? Are
> >there any web pages which list such devices?
> >
> >Andrew
> >
>
> If you have access to a laptop or PCMCIA interface for your PC then
> PCMCIA to compact flash adapters work well with linux - they appear
> as IDE drives and just need mounting (mount /dev/hde1 /mountpoint).
>
> You could also try using the GPhoto package included in most current
> distro's to read the data using the serial port (try all listed cameras
> if your one is not specifically listed - it may have copied the protocol
> from another manufacturer or model).
------------------------------
From: "Pantalacci Christophe" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc,comp.os.linux.setup
Subject: Memory pb : 384M real, 64M effective
Date: Fri, 30 Mar 2001 18:23:59 +0200
Hi,
I've got this kind of problem :
Linux only sees 64M of RAM. When I modify lilo.conf by adding
append="mem=384M" and executing lilo, my whole system crashes at reboot with
segmentation faults everywhere, and i must reinstall.
I've tried several distributions, like RedHat 7.0 and Mandrake 7.2, but
nothing changes.
I guess it's a hardware issue, maybe due to the VIA chipset.
The config is the following :
PIII 733 Mhz
3x128Mo RAM (100Mhz)
Chipset VIA Apollo Pro
Thanks for the help
Christophe
------------------------------
From: nobody <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.networking
Subject: Re: Netgear FA311 ethernet card Not working
Date: Fri, 30 Mar 2001 16:39:25 GMT
"Peter T. Breuer" wrote:
[r.e. fa311.c 2.4.0 patch]
> > long, and it compiles and runs fine. I'll post a patch in this
>
> It runs? That's very surprising. Much more fundamental things changed
> between 2.0.36 and 2.4.0! Well done!
>
> Making those sorts of changes (syntax, essentially) is only the
> first hurdle in a port. Now you need to compare your code with a
> similar driver that is known to be working on the kernel.
I haven't tested it extensively against the natsemi driver, and this
appears to have been yet another job of reinventing the wheel. However,
having done it, I haven't gotten any errors in a few days of normal use,
and am getting expected speeds.
My patch is at http://members.home.net/dlooney1/fa311-2.4.0.patch
(signature fa311-2.4.0.patch.asc). To apply, cp it to the
/usr/src/linux/drivers/net directory, copy the diskette fa311.c and
fa311.h files to the directory, cd to that directory, patch -p1 -b <
fa311-2.4.0.patch. This patches the Makefile, Config.in, and fa311.c
files. Then cd ../.., make xconfig, select to compile the fa311 module
(just after the 3com drivers in 10/100 cards in net devices).
> If you know
> which driver the code was developed from in the first place, then you
> need to compare it with the 2.4.0 version of that driver. Sometimes you
> need to go through with a microscope.
See above. I'll continue to play with this, and compare (if possible)
with the natsemi code.
> Kudos to you if you really have moved the 2.0.36 code forward to 2.4.
> Send it to Alan Cox or just publish it on the kernel list. It'll be
> picked up and corrected :-).
But perhaps not useful; I'll see if anybody wants it. Perhaps one thing
to do would be to send it to Netgear, in the hopes they would put
something more recent than 2.0.36 source on their diskettes.
------------------------------
Subject: Re: Help With ORiNOCO PC Card
From: Michael Meissner <[EMAIL PROTECTED]>
Date: 31 Mar 2001 01:06:20 -0500
"-=Nitro7=-" <[EMAIL PROTECTED]> writes:
> Hello,
> I am trying to set up my wireless connection with an ORiNOCO Silver PC
> Card. I do not know even where to begin
> if someone can point me in the right direction I am sure I could figure the
> rest out. I am running Redhat 7.
(Note, I work for the GCC group, not the Linux group, so take what I say with
appropriate grains of salt :-)
The wireless HowTo is:
http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Wireless.html
For my laptop, I needed to modify three files (note, I build my own kernels and
pcmcia drivers). The driver to use is the wvlan_cs driver. The OriNOCO
supplied wavelan2_cs driver will also work with 2.2 kernels, but I found that
it won't work with 2.4 kernels. Originally I used the non-free Orinoco driver
was to support encryption, but now the latest pcmcia-cs release supports
encryption in the wvlan-cs driver, so when I rev'ed up my laptop to the
2.4.2-ac27 kernel and Red Hat 7.1 beta, I made the switch.
/etc/pcmcia/network.opts:
# Network adapter configuration
#
# The address format is "scheme,socket,instance,hwaddr".
#
# Note: the "network address" here is NOT the same as the IP address.
# See the Networking HOWTO. In short, the network address is the IP
# address masked by the netmask.
#
logger -p "user.info" "Network.opts ADDRESS='$ADDRESS'"
case "$ADDRESS" in
# # Transceiver selection, for some cards -- see 'man ifport'
# IF_PORT=""
# # Use BOOTP (via /sbin/bootpc)? [y/n]
# BOOTP="n"
# # Use DHCP (via /sbin/dhcpcd)? [y/n]
# DHCP="n"
# # Use /sbin/pump for BOOTP/DHCP? [y/n]
# PUMP="n"
# # Host's IP address, netmask, network address, broadcast address
# IPADDR=""
# NETMASK="255.255.255.0"
# NETWORK="1.2.0.0"
# BROADCAST="1.2.255.255"
# # Gateway address for static routing
# GATEWAY="1.2.0.1"
# # Things to add to /etc/resolv.conf for this interface
# DOMAIN=""
# SEARCH=""
# DNS_1=""
# DNS_2=""
# DNS_3=""
# # NFS mounts, should be listed in /etc/fstab
# MOUNTS=""
# # For IPX interfaces, the frame type and network number
# IPX_FRAME=""
# IPX_NETNUM=""
# # Extra stuff to do after setting up the interface
# start_fn () { return; }
# # Extra stuff to do before shutting down the interface
# stop_fn () { return; }
*,*,*,*)
DHCP="y"
;;
esac
start_fn () {
/sbin/ifup $1
if [ -x /etc/rc.d/init.d/xntp ]; then
/etc/rc.d/init.d/xntp restart
elif [ -x /etc/rc.d/init.d/ntp ]; then
/etc/rc.d/init.d/xntp restart
fi
}
stop_fn () {
if [ -x /etc/rc.d/init.d/xntp ]; then
/etc/rc.d/init.d/xntp stop
elif [ -x /etc/rc.d/init.d/ntp ]; then
/etc/rc.d/init.d/xntp stop
fi
/sbin/ifdown $1
}
/etc/pcmcia/config.opts:
#
# Local PCMCIA Configuration File
#
# System resources available for PCMCIA devices
#
# Exclude extra ports not needed on Tecra & causes problems with some versions
of pcmcia-cs.
#include port 0x100-0x4ff, port 0x1000-0x17ff
include port 0x100-0x4ff
include memory 0xc0000-0xfffff
include memory 0xa0000000-0xa0ffffff, memory 0x60000000-0x60ffffff
#
# Extra port range for IBM Token Ring
#
#include port 0xa00-0xaff
#
# Resources we should not use, even if they appear to be available
#
# modem
exclude irq 3
# serial port
exclude irq 4
# sound system
exclude irq 5
# parallel port
#exclude irq 7
# Wvlan resources
# irq_list=i,j,...
# Specifies the set of interrupts that may be allocated by this driver.
#
# port_type=n
# Select WaveLAN port type: [1] BSS - Basic Service Set (default), [2]
# WDS - Wireless Distribution System, [3] Pseudo-IBSS - ad-hoc network
# (no AccessPoint, PtP).
#
# station_name=s
# Sets the station name. The default is card-configured.
#
# network_name=s
# Sets the independent network name in ad-hoc mode. Sets the desired
# network (desired ESSID) to connect to if using an access point. The
# default is card-configured.
#
# channel=n
# Channel (frequency) for ad-hoc networks and is useless if using an
# access point. Valid range: [0-14] (depends on local restrictions) and
# defaults to [3]
#
# ap_density=n
# Sets the access point density (sensitivity). This affects modem and
# roaming thresholds. [1] low density (default), [2] medium density, [3]
# high density.
#
# medium_reservation=n
# Sets the medium reservation (RTS/CTS frame length), which affects the
# number of octets in a message or fragment above which a RTS/CTS
# handshake is performed. [500] hidden stations, [2347] no RTS/CTS
# (default). Valid range: [0-2347]
#
# frag_threshold=n
# Defines the number of bytes used for the fragmentation boundary for
# directed messages (Fragmentation length unicast message transmission).
# [2346] is the default, valid range: [256-2346] (even numbers only!).
#
# transmit_rate=n
# Transmit rate control. [1] fixed low, [2] fixed high, [3] auto select
# high (default), [4] fixed medium, [5] fixed high, [6] auto select
# standard, [7] auto select medium.
#
# eth=n
# Network device naming. By default [0] devices are named wvlan#, set
# this to [1] to have devices named eth#.
#
# mtu=n
# Maximum transfer unit. [1500] is the default, valid range: [256-2296]
module "wvlan_cs" opts "port_type=3 station_name=glinda eth=1"
/etc/pcmcia/wireless.opts:
# Wireless LAN adapter configuration
#
# The address format is "scheme,socket,instance,hwaddr".
#
# Theory of operation : all the Wireless specific configuration is done
# through the Wireless Extensions, so we will just call 'iwconfig' with
# the right parameters defined below.
# Of course, you need to have iwconfig installled on your system.
# To download iwconfig, or for more info on Wireless Extensions :
# http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html
#
# Note : you don't need to fill all parameters, leave them blank, in most
# cases the driver will initialise itself with sane defaults values or
# automatically figure out the value... And not all drivers do support
# all settings...
#
# Finally, send comments and flames to me, Jean Tourrilhes <[EMAIL PROTECTED]>
#
case "$ADDRESS" in
# Orinoco/wavelan 802.11b card
*,*,*,00:60:1D:1E:DB:88)
INFO="Meissner Orinoco 802.11b gold card"
MODE="Ad-Hoc"
KEY="s:xxxxxxxxxxxxx [1]"
# Note replace the x's above with your encryption key in ascii.
;;
# Generic example (decribe all possible settings)
*,*,*,*)
INFO="Fill with your own settings..."
# ESSID (extended network name) : My Network, any
ESSID=""
# NWID/Domain (cell identifier) : 89AB, 100, off
NWID=""
# Operation mode : Ad-Hoc, Managed, Master, Repeater, Secondary, auto
MODE=""
# Frequency or channel : 1, 2, 3 (channel) ; 2.422G, 2.46G (frequency)
FREQ=""
CHANNEL=""
# Sensitivity (cell size + roaming speed) : 1, 2, 3 ; -70 (dBm)
SENS=""
# Bit rate : auto, 1M, 11M
RATE=""
# Encryption key : 4567-89AB-CD, s:password
KEY=""
# RTS threshold : off, 500
RTS=""
# Fragmentation threshold : off, 1000
FRAG=""
# Other iwconfig parameters : power off, ap 01:23:45:67:89:AB
IWCONFIG=""
# iwspy parameters : + 01:23:45:67:89:AB
IWSPY=""
# iwpriv parameters : set_port 2, set_histo 50 60
IWPRIV=""
;;
esac
--
Michael Meissner, Red Hat, Inc. (GCC group)
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA
Work: [EMAIL PROTECTED] phone: +1 978-486-9304
Non-work: [EMAIL PROTECTED] fax: +1 978-692-4482
------------------------------
From: [EMAIL PROTECTED] (Scott Alfter)
Crossposted-To: comp.sys.ibm.pc.hardware.chips
Subject: Re: Switchboxes for keyboard, mice, video?
Date: Fri, 30 Mar 2001 17:17:04 -0000
=====BEGIN PGP SIGNED MESSAGE=====
Hash: SHA1
In article <[EMAIL PROTECTED]>,
Jonadab the Unsightly One <[EMAIL PROTECTED]> wrote:
>I used to think RJ45 Ethernet cords were hot-pluggable, but
>I've found that sometimes a reboot is required to get the
>connection working again (at least in Windoze; I haven't
>tried this with Linux, since there is no Linux at work
>(which is where the LAN is) unfortunately).
Linux is smarter than Win9x/NT about networking. You can bring network
interfaces up and down all day long, change IP addresses, twiddle MAC
addresses, etc., and not have to reboot. Win2K sometimes lets you get away
with some network changes without rebooting (you can usually set/change an
IP address), so it seems to have caught up with Linux somewhat in that
regard. I've also heard that NetWare is fairly smart about dealing with
changes in network configuration, but I don't have much experience with it.
_/_
/ v \
(IIGS( Scott Alfter (remove Voyager's hull number for email address)
\_^_/ http://salfter.dyndns.org
=====BEGIN PGP SIGNATURE=====
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE6xMH4VgTKos01OwkRApNLAKDOLvTrEhL7ruN7SCOM93HW2wzGpACgzSQC
NFe1Z9W1ha52g73E3H4Svck=
=0wmW
=====END PGP SIGNATURE=====
------------------------------
From: "Chad Johnson - DICE Corporation" <[EMAIL PROTECTED]>
Subject: I need video capture equiptment
Date: Fri, 30 Mar 2001 12:18:08 -0500
I am working with both Red Hat linux as well as Caldera. I need a video
capture board (PCI) with multiple camera hookups (would like 8). I
currently have a board from integral technologies that works under Windows
(by the way, I hate windows) and I want to do this under linux. Does
anybody know of a board that I can use for this or know how to make this
board work. The board I have uses a saa7146 chipst for the i2c communiction
and I have loaded the i2c portion from the lm-sensors project as well as a
few other drivers and cannot seem to get it to work. Any info would be
really appreciated.
------------------------------
From: "Andy Walker" <[EMAIL PROTECTED]>
Subject: Re: Athlon processor compatibility with SuSe
Date: Fri, 30 Mar 2001 18:22:41 -0000
Allen Blackburn wrote in message <[EMAIL PROTECTED]>...
>Hi there:
>
>I'm really new to Linux (but not Unix), and I'm gearing up to set up my
>own PC with Linux. I was thinking about buying a new 1.1 GHz AMD 761
>Athlon chip with 266 MHz bus, with a Gigabyte GA7DX motherboard. I also
>wanted to load SuSe 7.1. However, these hardware choices are not on
>their website in their hardware compatiblity list. My questions are: Is
>it a bad idea to go ahead and try to make it work, or would anyone out
>there recommend a different set of hardware and/or Linux distribution?
>
>Thank you very much in advance!
>
Linux works great with my Athelon600 and the new kernel 2.4 can now be
compiled specifically for it! I'm pretty sure I tried SuSe successfully on
it but RedHat6.2 kept locking up during installation (once installed it
worked fine). Mandrake seems to work the best for me.
Good luck
------------------------------
From: "Andy Walker" <[EMAIL PROTECTED]>
Subject: Re: Need USB Video Capture for Linux
Date: Fri, 30 Mar 2001 18:25:34 -0000
Robert L. Klungle wrote in message <[EMAIL PROTECTED]>...
>Any one know where I can find a driver and hardware (manufacturor) for a
>USB Video capture device??
>Video capture needs to receive RS170 and generate a JPEG file.
>Current Linux is 2.2.18 (RedHat).
>
>Been to linux-usb several times and they don't seem to list this. Maybe
>I don't know what I am seeing.
>
>Hopefully.....bob
>
>
I've heard that Pinnacle PCTV USB works with KWinTV but I've never tested it
myself. Some distributions come with KWinTV already installed.
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: UPS for Linux/Winblows
Date: Fri, 30 Mar 2001 17:29:04 GMT
Reply-To: [EMAIL PROTECTED]
In <MHRw6.354$[EMAIL PROTECTED]> [EMAIL PROTECTED]
writes:
>Hmm.. I bought a APC Smart-UPS from their web site - refurb... Made my
>own cable and used the apcupsd software for monitoring the UPS. Works like
>a charm - and cost me all of about $25...
OK, I should have been more specific. APC has not given away info about
the interface they use on their serial port, I don't know who wrote
apcupsd and where he/she/them got their information, but it surely wasn't
easy (I tried it once).
HTH,
Uli
--
Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED]
Stormweg 24 |listening to:Something Good To Go By(The Decibels)
24539 Neumuenster, Germany|Cheap Excitement (Stratford Mercenaries)
------------------------------
From: "Andy Walker" <[EMAIL PROTECTED]>
Subject: Re: Video card recommendations PLS !!
Date: Fri, 30 Mar 2001 18:34:25 -0000
[EMAIL PROTECTED] wrote in message
<[EMAIL PROTECTED]>...
>Hi folks
>
>Just wondering what suggestions people may have for the video card for
>a new linux box.
>
>Probably be running with an AMD 1000 on an ASUS A7V133 board (maybe
>the A7M266)
>
>I've seen mention of GeForce2 MX (which doesn't mean much to me)
>Researching that on the www I can't make any sense of it. Seems
>everybody makes one.
>
>So what do YOU recommend?
>
>Cello
The manufacturer is largely irrelevant, it's the graphics chip that counts.
Practically anything with a TNT2 chipset will work and most Matrox cards.
I think I have seen GeForce2 cards listed as suitable but I can't be sure.
------------------------------
From: Anthony Schlemmer <[EMAIL PROTECTED]>
Subject: Re: Athlon processor compatibility with SuSe
Date: Fri, 30 Mar 2001 17:40:43 GMT
I've got SuSE 7.1 running on an Asus A7V mobo with a 900 Mhz T-Bird. The
system is my primary workstation and is running 24/7.
Tony
Allen Blackburn wrote:
> Hi there:
>
> I'm really new to Linux (but not Unix), and I'm gearing up to set up my
> own PC with Linux. I was thinking about buying a new 1.1 GHz AMD 761
> Athlon chip with 266 MHz bus, with a Gigabyte GA7DX motherboard. I also
> wanted to load SuSe 7.1. However, these hardware choices are not on
> their website in their hardware compatiblity list. My questions are: Is
> it a bad idea to go ahead and try to make it work, or would anyone out
> there recommend a different set of hardware and/or Linux distribution?
>
> Thank you very much in advance!
>
>
------------------------------
From: Anthony Schlemmer <[EMAIL PROTECTED]>
Subject: Re: Netgear FA311 ethernet card Not working
Crossposted-To: comp.os.linux.networking
Date: Fri, 30 Mar 2001 18:04:42 GMT
nobody wrote:
FWIW, I've been using the "natsemi" driver on with my FA311TX with the
2.4.0 kernel with no problems. The 2.4.0 kernel I have was supplied as part
of the SuSE 7.1 disro and so I wasn't responsible for compiling that
kernel. I have more recently downloaded and installed a 2.4.2 kernel and
the "natsemi" driver is part of that kernel and also works with my FA311
card. I have no complaints about the speed of the card and I'm not getting
any errors with the "natsemi" driver.
My last ditch effort would have been to hack the fa311 code but I tried to
avoid that at all costs. Thankfully I didn't have to look any farther than
the Linux network driver page which listed the "natsemi" as the one to use
with the FA311.
Tony
> "Peter T. Breuer" wrote:
>
> [r.e. fa311.c 2.4.0 patch]
>
>> > long, and it compiles and runs fine. I'll post a patch in this
>>
>> It runs? That's very surprising. Much more fundamental things changed
>> between 2.0.36 and 2.4.0! Well done!
>>
>> Making those sorts of changes (syntax, essentially) is only the
>> first hurdle in a port. Now you need to compare your code with a
>> similar driver that is known to be working on the kernel.
>
> I haven't tested it extensively against the natsemi driver, and this
> appears to have been yet another job of reinventing the wheel. However,
> having done it, I haven't gotten any errors in a few days of normal use,
> and am getting expected speeds.
>
> My patch is at http://members.home.net/dlooney1/fa311-2.4.0.patch
> (signature fa311-2.4.0.patch.asc). To apply, cp it to the
> /usr/src/linux/drivers/net directory, copy the diskette fa311.c and
> fa311.h files to the directory, cd to that directory, patch -p1 -b <
> fa311-2.4.0.patch. This patches the Makefile, Config.in, and fa311.c
> files. Then cd ../.., make xconfig, select to compile the fa311 module
> (just after the 3com drivers in 10/100 cards in net devices).
>
>> If you know
>> which driver the code was developed from in the first place, then you
>> need to compare it with the 2.4.0 version of that driver. Sometimes you
>> need to go through with a microscope.
>
> See above. I'll continue to play with this, and compare (if possible)
> with the natsemi code.
>
>> Kudos to you if you really have moved the 2.0.36 code forward to 2.4.
>> Send it to Alan Cox or just publish it on the kernel list. It'll be
>> picked up and corrected :-).
>
> But perhaps not useful; I'll see if anybody wants it. Perhaps one thing
> to do would be to send it to Netgear, in the hopes they would put
> something more recent than 2.0.36 source on their diskettes.
>
------------------------------
** 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
******************************
