natsemi trouble with netgear fa311 in 2.4.6
I have a NetGear FA311 pci card that uses the natsemi.c driver and have had no problems with it in all kernels 2.4.0 through 2.4.5. However with 2.4.6 (also tried 2.4.6-ac2) I am getting strange behavior. As soon as an ip is given to it (with either dhcp or manual ip) this error message keeps repeating: eth0: Something Wicked happened! 18000 and I can't ping anything else except itself. It's always 18000. I've tried switching the card to another pci slot, checked the cables, etc. When I switch back to kernel 2.4.5 everything works perfectly. The bootup message is: eth0: Setting full-duplex based on negotiated link capability. And lspci shows: Ethernet controller: National Semiconductor Corporation: Unknown device 0020 The computer is a k6-2 400 with an ASUS P5A motherboard (ALi chipset) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
natsemi trouble with netgear fa311 in 2.4.6
I have a NetGear FA311 pci card that uses the natsemi.c driver and have had no problems with it in all kernels 2.4.0 through 2.4.5. However with 2.4.6 (also tried 2.4.6-ac2) I am getting strange behavior. As soon as an ip is given to it (with either dhcp or manual ip) this error message keeps repeating: eth0: Something Wicked happened! 18000 and I can't ping anything else except itself. It's always 18000. I've tried switching the card to another pci slot, checked the cables, etc. When I switch back to kernel 2.4.5 everything works perfectly. The bootup message is: eth0: Setting full-duplex based on negotiated link capability. And lspci shows: Ethernet controller: National Semiconductor Corporation: Unknown device 0020 The computer is a k6-2 400 with an ASUS P5A motherboard (ALi chipset) - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: natsemi.c (Netgear FA311 card) probmlems??
On Wed, Apr 11, 2001 at 09:32:36PM -0500, Troy Benjegerdes wrote: > > There are some improvements in the latest 2.4 test patch, 2.4.3-pre8. I > > would be very interested in hearing feedback on that. I finally got two > > test cards, FA311 and FA312, so I can work on it a bit too. > > Okay, I finally got around to testing this on 2.4.4-pre1. for the 5 or so > minutes I've been using it so far, it seems okay (I'm able to log in this > time), and I'm running NetPIPE to check performance. > > Perfomance isn't great (the peak bandwidth is 65 Mbps or so), but this > could be partially due to my switch or the other machine I'm testing it > with. No, performance really is peaked about 65 Mbps or so at the moment. I'm currently using the FA312 here, which was massively broken with my FA312 until 2.4.2-ac which updated the natsemi driver. I have a '311 in a P200 which worked fine before. This is an AMD box, but I suspect the problem was the '312, not the AMD. -- Joseph Carter <[EMAIL PROTECTED]>Free software developer "This is the element_data structure for elements whose *element_type = FORM_TYPE_SELECT_ONE, FORM_TYPE_SELECT_MULT. */ /* * nesting deeper and deeper, harder and harder, go, go, oh, OH, OH!! * Sorry, got carried away there. */ struct lo_FormElementOptionData_struct." -- Mozilla source code PGP signature
Re: natsemi.c (Netgear FA311 card) probmlems??
On Wed, Apr 11, 2001 at 09:32:36PM -0500, Troy Benjegerdes wrote: There are some improvements in the latest 2.4 test patch, 2.4.3-pre8. I would be very interested in hearing feedback on that. I finally got two test cards, FA311 and FA312, so I can work on it a bit too. Okay, I finally got around to testing this on 2.4.4-pre1. for the 5 or so minutes I've been using it so far, it seems okay (I'm able to log in this time), and I'm running NetPIPE to check performance. Perfomance isn't great (the peak bandwidth is 65 Mbps or so), but this could be partially due to my switch or the other machine I'm testing it with. No, performance really is peaked about 65 Mbps or so at the moment. I'm currently using the FA312 here, which was massively broken with my FA312 until 2.4.2-ac which updated the natsemi driver. I have a '311 in a P200 which worked fine before. This is an AMD box, but I suspect the problem was the '312, not the AMD. -- Joseph Carter [EMAIL PROTECTED]Free software developer "This is the element_data structure for elements whose *element_type = FORM_TYPE_SELECT_ONE, FORM_TYPE_SELECT_MULT. */ /* * nesting deeper and deeper, harder and harder, go, go, oh, OH, OH!! * Sorry, got carried away there. */ struct lo_FormElementOptionData_struct." -- Mozilla source code PGP signature
Re: natsemi.c (Netgear FA311 card) probmlems??
On Wed, Mar 28, 2001 at 12:58:57PM -0500, Jeff Garzik wrote: > There are some improvements in the latest 2.4 test patch, 2.4.3-pre8. I > would be very interested in hearing feedback on that. I finally got two > test cards, FA311 and FA312, so I can work on it a bit too. Okay, I finally got around to testing this on 2.4.4-pre1. for the 5 or so minutes I've been using it so far, it seems okay (I'm able to log in this time), and I'm running NetPIPE to check performance. Perfomance isn't great (the peak bandwidth is 65 Mbps or so), but this could be partially due to my switch or the other machine I'm testing it with. > > The 2.4.3-pre8 patch, against kernel 2.4.2, is available from > ftp://ftp.us.kernel.org/pub/linux/kernel/testing/ > > This updated 2.4 natsemi.c merges the changes in Becker's latest, which > should fix eeprom/mac address reading as you mention, and it also > includes some power management fixes required on some boards. > Differences from 2.2 versions include locking updates and some other > small differences. Please test, if you have an opportunity. > > (note you'll have to fix a screwup of mine in drivers/net/Makefile -- > you need to add net_init.o to export-objs before you can build net > drivers as modules. Building them into the kernel works fine.) > > -- > Jeff Garzik | May you have warm words on a cold evening, > Building 1024 | a full moon on a dark night, > MandrakeSoft | and a smooth road all the way to your door. > -- Troy Benjegerdes | master of mispeeling | 'da hozer' | [EMAIL PROTECTED] -"If this message isn't misspelled, I didn't write it" -- Me - "Why do musicians compose symphonies and poets write poems? They do it because life wouldn't have any meaning for them if they didn't. That's why I draw cartoons. It's my life." -- Charles Shulz - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: natsemi.c (Netgear FA311 card) probmlems??
On Wed, Mar 28, 2001 at 12:58:57PM -0500, Jeff Garzik wrote: There are some improvements in the latest 2.4 test patch, 2.4.3-pre8. I would be very interested in hearing feedback on that. I finally got two test cards, FA311 and FA312, so I can work on it a bit too. Okay, I finally got around to testing this on 2.4.4-pre1. for the 5 or so minutes I've been using it so far, it seems okay (I'm able to log in this time), and I'm running NetPIPE to check performance. Perfomance isn't great (the peak bandwidth is 65 Mbps or so), but this could be partially due to my switch or the other machine I'm testing it with. The 2.4.3-pre8 patch, against kernel 2.4.2, is available from ftp://ftp.us.kernel.org/pub/linux/kernel/testing/ This updated 2.4 natsemi.c merges the changes in Becker's latest, which should fix eeprom/mac address reading as you mention, and it also includes some power management fixes required on some boards. Differences from 2.2 versions include locking updates and some other small differences. Please test, if you have an opportunity. (note you'll have to fix a screwup of mine in drivers/net/Makefile -- you need to add net_init.o to export-objs before you can build net drivers as modules. Building them into the kernel works fine.) -- Jeff Garzik | May you have warm words on a cold evening, Building 1024 | a full moon on a dark night, MandrakeSoft | and a smooth road all the way to your door. -- Troy Benjegerdes | master of mispeeling | 'da hozer' | [EMAIL PROTECTED] -"If this message isn't misspelled, I didn't write it" -- Me - "Why do musicians compose symphonies and poets write poems? They do it because life wouldn't have any meaning for them if they didn't. That's why I draw cartoons. It's my life." -- Charles Shulz - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: natsemi.c (Netgear FA311 card) probmlems??
Torrey Hoffman wrote: > > Troy Benjegerdes wrote: > [...] > > Is anyone succesfully using a FA311 card (or anthing with a NatSemi > > DP83815 chip?) > > We are working on the 2.2.x version of the driver. On our hardware, > which has the DP83815 on the motherboard, Donald Becker's version was > capable of sending packets but not receiving. I swapped some email > with him on the subject about 6 weeks ago, sent him some debug output, > but haven't heard anything recently. > > Meanwhile, we are doing some work on it ourselves. A "Jocelyn Mayer" > posted a revised version of the driver which fixed some bugs but > introduced others - at least on our hardware. Check the archives. > > Our version now sends and receives under 2.2.17, and is fixed to read > and set the MAC address properly (!), but tends to have lousy > performance. Large file transfers usually run at a pathetic 250 > KB/s and often stall, but sometimes when the moon is in the right > phase, run at a much more reasonable 7 MB/s. We are working on it... > > If anyone else out there has some improvements, I would love to hear > about them. There are some improvements in the latest 2.4 test patch, 2.4.3-pre8. I would be very interested in hearing feedback on that. I finally got two test cards, FA311 and FA312, so I can work on it a bit too. The 2.4.3-pre8 patch, against kernel 2.4.2, is available from ftp://ftp.us.kernel.org/pub/linux/kernel/testing/ This updated 2.4 natsemi.c merges the changes in Becker's latest, which should fix eeprom/mac address reading as you mention, and it also includes some power management fixes required on some boards. Differences from 2.2 versions include locking updates and some other small differences. Please test, if you have an opportunity. (note you'll have to fix a screwup of mine in drivers/net/Makefile -- you need to add net_init.o to export-objs before you can build net drivers as modules. Building them into the kernel works fine.) -- Jeff Garzik | May you have warm words on a cold evening, Building 1024 | a full moon on a dark night, MandrakeSoft | and a smooth road all the way to your door. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: natsemi.c (Netgear FA311 card) probmlems??
Troy Benjegerdes wrote: [...] > Is anyone succesfully using a FA311 card (or anthing with a NatSemi > DP83815 chip?) We are working on the 2.2.x version of the driver. On our hardware, which has the DP83815 on the motherboard, Donald Becker's version was capable of sending packets but not receiving. I swapped some email with him on the subject about 6 weeks ago, sent him some debug output, but haven't heard anything recently. Meanwhile, we are doing some work on it ourselves. A "Jocelyn Mayer" posted a revised version of the driver which fixed some bugs but introduced others - at least on our hardware. Check the archives. Our version now sends and receives under 2.2.17, and is fixed to read and set the MAC address properly (!), but tends to have lousy performance. Large file transfers usually run at a pathetic 250 KB/s and often stall, but sometimes when the moon is in the right phase, run at a much more reasonable 7 MB/s. We are working on it... If anyone else out there has some improvements, I would love to hear about them. Torrey Hoffman - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: natsemi.c (Netgear FA311 card) probmlems??
Troy Benjegerdes wrote: [...] Is anyone succesfully using a FA311 card (or anthing with a NatSemi DP83815 chip?) We are working on the 2.2.x version of the driver. On our hardware, which has the DP83815 on the motherboard, Donald Becker's version was capable of sending packets but not receiving. I swapped some email with him on the subject about 6 weeks ago, sent him some debug output, but haven't heard anything recently. Meanwhile, we are doing some work on it ourselves. A "Jocelyn Mayer" posted a revised version of the driver which fixed some bugs but introduced others - at least on our hardware. Check the archives. Our version now sends and receives under 2.2.17, and is fixed to read and set the MAC address properly (!), but tends to have lousy performance. Large file transfers usually run at a pathetic 250 KB/s and often stall, but sometimes when the moon is in the right phase, run at a much more reasonable 7 MB/s. We are working on it... If anyone else out there has some improvements, I would love to hear about them. Torrey Hoffman - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: natsemi.c (Netgear FA311 card) probmlems??
Torrey Hoffman wrote: Troy Benjegerdes wrote: [...] Is anyone succesfully using a FA311 card (or anthing with a NatSemi DP83815 chip?) We are working on the 2.2.x version of the driver. On our hardware, which has the DP83815 on the motherboard, Donald Becker's version was capable of sending packets but not receiving. I swapped some email with him on the subject about 6 weeks ago, sent him some debug output, but haven't heard anything recently. Meanwhile, we are doing some work on it ourselves. A "Jocelyn Mayer" posted a revised version of the driver which fixed some bugs but introduced others - at least on our hardware. Check the archives. Our version now sends and receives under 2.2.17, and is fixed to read and set the MAC address properly (!), but tends to have lousy performance. Large file transfers usually run at a pathetic 250 KB/s and often stall, but sometimes when the moon is in the right phase, run at a much more reasonable 7 MB/s. We are working on it... If anyone else out there has some improvements, I would love to hear about them. There are some improvements in the latest 2.4 test patch, 2.4.3-pre8. I would be very interested in hearing feedback on that. I finally got two test cards, FA311 and FA312, so I can work on it a bit too. The 2.4.3-pre8 patch, against kernel 2.4.2, is available from ftp://ftp.us.kernel.org/pub/linux/kernel/testing/ This updated 2.4 natsemi.c merges the changes in Becker's latest, which should fix eeprom/mac address reading as you mention, and it also includes some power management fixes required on some boards. Differences from 2.2 versions include locking updates and some other small differences. Please test, if you have an opportunity. (note you'll have to fix a screwup of mine in drivers/net/Makefile -- you need to add net_init.o to export-objs before you can build net drivers as modules. Building them into the kernel works fine.) -- Jeff Garzik | May you have warm words on a cold evening, Building 1024 | a full moon on a dark night, MandrakeSoft | and a smooth road all the way to your door. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
natsemi.c (Netgear FA311 card) probmlems??
Is anyone succesfully using a FA311 card (or anthing with a NatSemi DP83815 chip?) The natsemi.c driver in 2.4.0 (and the one from Donald Becker's site for 2.2.x) Something seems to be handled incorrectly in the driver, because whenever I subject the card to moderate to heavy load (nfs does this most often), I get errors about 'eth0: something Wicked Happened 0700'. And usually after this happens a couple of times, the driver/card gets wedged and won't send/receive any more packets. The fa31lx70 driver from Netgear's web site at least doesn't get wedged, but has really poor perfomance under heavy load. -- Troy Benjegerdes | master of mispeeling | 'da hozer' | [EMAIL PROTECTED] -"If this message isn't misspelled, I didn't write it" -- Me - "Why do musicians compose symphonies and poets write poems? They do it because life wouldn't have any meaning for them if they didn't. That's why I draw cartoons. It's my life." -- Charles Shulz - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
natsemi.c (Netgear FA311 card) probmlems??
Is anyone succesfully using a FA311 card (or anthing with a NatSemi DP83815 chip?) The natsemi.c driver in 2.4.0 (and the one from Donald Becker's site for 2.2.x) Something seems to be handled incorrectly in the driver, because whenever I subject the card to moderate to heavy load (nfs does this most often), I get errors about 'eth0: something Wicked Happened 0700'. And usually after this happens a couple of times, the driver/card gets wedged and won't send/receive any more packets. The fa31lx70 driver from Netgear's web site at least doesn't get wedged, but has really poor perfomance under heavy load. -- Troy Benjegerdes | master of mispeeling | 'da hozer' | [EMAIL PROTECTED] -"If this message isn't misspelled, I didn't write it" -- Me - "Why do musicians compose symphonies and poets write poems? They do it because life wouldn't have any meaning for them if they didn't. That's why I draw cartoons. It's my life." -- Charles Shulz - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
NetGear fa311 driver update
Hi all,
I brought NetGear's fa311 driver up to compile under 2.4.2. I put the
updated source here -
http://millweed.com/projects/fa311/fa311.c
Or you can apply the following patch to the source gotten from the
NetGear support site
(http://www.netgear-support.com/ts/downloads/fa31lx70.zip) -
--- /tmp/basdf/fa311.c Fri Jan 19 14:20:50 2001
+++ fa311.c Thu Mar 1 18:12:57 2001
@@ -174,23 +174,23 @@
/* Device private data */
struct fa311_priv {
- struct device * next;/* Next fa311device */
+struct net_device * next;/* Next fa311device */
struct fa311_queuetx_queue;/* Transmit Descriptor Queue */
struct fa311_queuerx_queue;/* Receive Descriptor Queue */
-struct enet_statistics stats; /* MIB data */
+struct net_device_stats stats;/* MIB data */
};
-static struct device *fa311_dev_list;/* List of fa311devices */
+static struct net_device *fa311_dev_list; /* List of fa311devices */
/* Linux Network Driver interface routines */
-extern int fa311_probe (struct device *dev);
-static int fa311_open (struct device *dev);
-static int fa311_close (struct device *dev);
-static int fa311_start_xmit (struct sk_buff *skb, struct device *dev);
-static void fa311_set_multicast_list (struct device *dev);
-static int fa311_ioctl (struct device *dev, struct ifreq *rq, int cmd);
+extern int fa311_probe (struct net_device *dev);
+static int fa311_open (struct net_device *dev);
+static int fa311_close (struct net_device *dev);
+static int fa311_start_xmit (struct sk_buff *skb, struct net_device *dev);
+static void fa311_set_multicast_list (struct net_device *dev);
+static int fa311_ioctl (struct net_device *dev, struct ifreq *rq, int cmd);
static void fa311_interrupt (int irq, void *dev_id, struct pt_regs *regs);
-static struct enet_statistics *fa311_get_stats (struct device *dev);
+static struct net_device_stats *fa311_get_stats (struct net_device *dev);
/* Support Functions */
/*static u16 swap_16 (u16 us);*/
@@ -206,11 +206,11 @@
static status fa311_dev_reset (u32 iobase);
static status fa311_queue_create (struct fa311_queue *q, int count, int qtype);
static status fa311_queue_delete (struct fa311_queue *q);
-static virt_addr fa311_tx_desc_get (struct device *dev);
-static virt_addr fa311_rx_desc_get (struct device *dev);
-static status fa311_phy_setup (struct device *dev);
+static virt_addr fa311_tx_desc_get (struct net_device *dev);
+static virt_addr fa311_rx_desc_get (struct net_device *dev);
+static status fa311_phy_setup (struct net_device *dev);
static int fa311_crc (char * mc_addr);
-static void fa311_tx_skb_reclaim (struct device *dev, virt_addr desc_addr);
+static void fa311_tx_skb_reclaim (struct net_device *dev, virt_addr desc_addr);
static void ReadEEWord(u16 iobase,u32 wordOffset,u16* pEeData);
@@ -226,7 +226,7 @@
* registers each FA311 device found.
*/
int
-fa311_probe (struct device *dev)
+fa311_probe (struct net_device *dev)
{
int dev_count;
u8 bus;
@@ -353,7 +353,7 @@
/* fa311_open - open and initialize a device */
static int
-fa311_open (struct device *dev)
+fa311_open (struct net_device *dev)
{
u32 iobase = dev->base_addr;
struct fa311_priv* priv = dev->priv;
@@ -448,7 +448,7 @@
/* fa311_close - close a device, and reclaim resources */
static int
-fa311_close (struct device *dev)
+fa311_close (struct net_device *dev)
{
u32 iobase = dev->base_addr;
struct fa311_priv* priv = dev->priv;
@@ -480,19 +480,19 @@
* CMDSTS, and signals the chip
*/
static int
-fa311_start_xmit (struct sk_buff *skb, struct device *dev)
+fa311_start_xmit (struct sk_buff *skb, struct net_device *dev)
{
u32iobase = dev->base_addr;
u32cmdsts;
virt_addr tx_desc;
-struct enet_statistics *stats_p;
+struct net_device_stats *stats_p;
if (skb->len > ETH_MAX_PKT_SIZE)
return ERROR;
tx_desc = fa311_tx_desc_get(dev);
if (tx_desc == NULL) {
-set_bit (0, >tbusy);
+netif_stop_queue(dev);
DP_REG32_SET (DP_IMR, DP_IMR_TXOK | DP_IMR_TXIDLE);
tx_desc = fa311_tx_desc_get (dev);
}
@@ -553,7 +553,7 @@
* size, and updates the BUFPTR and SKBPTR fields to the newly allocated SKB.
*/
static int
-fa311_start_receive (struct device *dev)
+fa311_start_receive (struct net_device *dev)
{
u32 cmdsts;
int len;
@@ -562,7 +562,7 @@
struct sk_buff *cur_skb;
struct sk_buff *new_skb;
struct sk_buff *rx_skb;
-struct enet_statistics *stats_p;
+struct net_device_stats *stats_p;
stats_p = &((struct fa311_priv *)(dev->priv))->stats;
@@ -648,15 +648,15 @@
}
/* fa311_get_stats - get current device statistics */
-static struct enet_statistics *
-fa311_get_stats (struct device *dev)
+static struct net_device_stats *
+fa311_get_stats (struct net_device *dev)
{
return &((struct
NetGear fa311 driver update
Hi all,
I brought NetGear's fa311 driver up to compile under 2.4.2. I put the
updated source here -
http://millweed.com/projects/fa311/fa311.c
Or you can apply the following patch to the source gotten from the
NetGear support site
(http://www.netgear-support.com/ts/downloads/fa31lx70.zip) -
--- /tmp/basdf/fa311.c Fri Jan 19 14:20:50 2001
+++ fa311.c Thu Mar 1 18:12:57 2001
@@ -174,23 +174,23 @@
/* Device private data */
struct fa311_priv {
- struct device * next;/* Next fa311device */
+struct net_device * next;/* Next fa311device */
struct fa311_queuetx_queue;/* Transmit Descriptor Queue */
struct fa311_queuerx_queue;/* Receive Descriptor Queue */
-struct enet_statistics stats; /* MIB data */
+struct net_device_stats stats;/* MIB data */
};
-static struct device *fa311_dev_list;/* List of fa311devices */
+static struct net_device *fa311_dev_list; /* List of fa311devices */
/* Linux Network Driver interface routines */
-extern int fa311_probe (struct device *dev);
-static int fa311_open (struct device *dev);
-static int fa311_close (struct device *dev);
-static int fa311_start_xmit (struct sk_buff *skb, struct device *dev);
-static void fa311_set_multicast_list (struct device *dev);
-static int fa311_ioctl (struct device *dev, struct ifreq *rq, int cmd);
+extern int fa311_probe (struct net_device *dev);
+static int fa311_open (struct net_device *dev);
+static int fa311_close (struct net_device *dev);
+static int fa311_start_xmit (struct sk_buff *skb, struct net_device *dev);
+static void fa311_set_multicast_list (struct net_device *dev);
+static int fa311_ioctl (struct net_device *dev, struct ifreq *rq, int cmd);
static void fa311_interrupt (int irq, void *dev_id, struct pt_regs *regs);
-static struct enet_statistics *fa311_get_stats (struct device *dev);
+static struct net_device_stats *fa311_get_stats (struct net_device *dev);
/* Support Functions */
/*static u16 swap_16 (u16 us);*/
@@ -206,11 +206,11 @@
static status fa311_dev_reset (u32 iobase);
static status fa311_queue_create (struct fa311_queue *q, int count, int qtype);
static status fa311_queue_delete (struct fa311_queue *q);
-static virt_addr fa311_tx_desc_get (struct device *dev);
-static virt_addr fa311_rx_desc_get (struct device *dev);
-static status fa311_phy_setup (struct device *dev);
+static virt_addr fa311_tx_desc_get (struct net_device *dev);
+static virt_addr fa311_rx_desc_get (struct net_device *dev);
+static status fa311_phy_setup (struct net_device *dev);
static int fa311_crc (char * mc_addr);
-static void fa311_tx_skb_reclaim (struct device *dev, virt_addr desc_addr);
+static void fa311_tx_skb_reclaim (struct net_device *dev, virt_addr desc_addr);
static void ReadEEWord(u16 iobase,u32 wordOffset,u16* pEeData);
@@ -226,7 +226,7 @@
* registers each FA311 device found.
*/
int
-fa311_probe (struct device *dev)
+fa311_probe (struct net_device *dev)
{
int dev_count;
u8 bus;
@@ -353,7 +353,7 @@
/* fa311_open - open and initialize a device */
static int
-fa311_open (struct device *dev)
+fa311_open (struct net_device *dev)
{
u32 iobase = dev-base_addr;
struct fa311_priv* priv = dev-priv;
@@ -448,7 +448,7 @@
/* fa311_close - close a device, and reclaim resources */
static int
-fa311_close (struct device *dev)
+fa311_close (struct net_device *dev)
{
u32 iobase = dev-base_addr;
struct fa311_priv* priv = dev-priv;
@@ -480,19 +480,19 @@
* CMDSTS, and signals the chip
*/
static int
-fa311_start_xmit (struct sk_buff *skb, struct device *dev)
+fa311_start_xmit (struct sk_buff *skb, struct net_device *dev)
{
u32iobase = dev-base_addr;
u32cmdsts;
virt_addr tx_desc;
-struct enet_statistics *stats_p;
+struct net_device_stats *stats_p;
if (skb-len ETH_MAX_PKT_SIZE)
return ERROR;
tx_desc = fa311_tx_desc_get(dev);
if (tx_desc == NULL) {
-set_bit (0, dev-tbusy);
+netif_stop_queue(dev);
DP_REG32_SET (DP_IMR, DP_IMR_TXOK | DP_IMR_TXIDLE);
tx_desc = fa311_tx_desc_get (dev);
}
@@ -553,7 +553,7 @@
* size, and updates the BUFPTR and SKBPTR fields to the newly allocated SKB.
*/
static int
-fa311_start_receive (struct device *dev)
+fa311_start_receive (struct net_device *dev)
{
u32 cmdsts;
int len;
@@ -562,7 +562,7 @@
struct sk_buff *cur_skb;
struct sk_buff *new_skb;
struct sk_buff *rx_skb;
-struct enet_statistics *stats_p;
+struct net_device_stats *stats_p;
stats_p = ((struct fa311_priv *)(dev-priv))-stats;
@@ -648,15 +648,15 @@
}
/* fa311_get_stats - get current device statistics */
-static struct enet_statistics *
-fa311_get_stats (struct device *dev)
+static struct net_device_stats *
+fa311_get_stats (struct net_device *dev)
{
return ((struct fa311_priv
Re: Ethernet drivers: SiS 900, Netgear FA311
[EMAIL PROTECTED] wrote: > > On Sun, Jan 21, 2001 at 01:54:34PM +0100, [EMAIL PROTECTED] wrote: > > On 20 Jan, Jeff Garzik wrote: > > > > > Not true, see natsemi.c (in 2.4.x at least). > > > > Correct, and the cards really work with it. > > natsemi did not work with 2.2.17 on a remote system I do work on, but > did work with the 2.4.0-included driver. Wonder if it'll be making it > into 2.2.x soon.. It is available for 2.2 from http://www.scyld.com/network/ ... All I did was port the Becker driver to 2.4. If someone wants to port his driver into 2.2.latest, I'm sure people will be happy.. Jeff -- Jeff Garzik | "You see, in this world there's two kinds of Building 1024 | people, my friend: Those with loaded guns MandrakeSoft | and those who dig. You dig." --Blondie - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Ethernet drivers: SiS 900, Netgear FA311
On Sun, Jan 21, 2001 at 01:54:34PM +0100, [EMAIL PROTECTED] wrote: > On 20 Jan, Jeff Garzik wrote: > > > Not true, see natsemi.c (in 2.4.x at least). > > Correct, and the cards really work with it. natsemi did not work with 2.2.17 on a remote system I do work on, but did work with the 2.4.0-included driver. Wonder if it'll be making it into 2.2.x soon.. -- Ferret - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Ethernet drivers: SiS 900, Netgear FA311
On 20 Jan, Jeff Garzik wrote: > Not true, see natsemi.c (in 2.4.x at least). Correct, and the cards really work with it. -- Servus, Daniel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Ethernet drivers: SiS 900, Netgear FA311
On 20 Jan, Jeff Garzik wrote: Not true, see natsemi.c (in 2.4.x at least). Correct, and the cards really work with it. -- Servus, Daniel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Ethernet drivers: SiS 900, Netgear FA311
On Sun, Jan 21, 2001 at 01:54:34PM +0100, [EMAIL PROTECTED] wrote: On 20 Jan, Jeff Garzik wrote: Not true, see natsemi.c (in 2.4.x at least). Correct, and the cards really work with it. natsemi did not work with 2.2.17 on a remote system I do work on, but did work with the 2.4.0-included driver. Wonder if it'll be making it into 2.2.x soon.. -- Ferret - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Ethernet drivers: SiS 900, Netgear FA311
Tobias Burnus wrote: > I think those drivers have not yet been merged. Since I happend to have > those (and had problem to get them run with the default kernel) I'd like > to asked whether those can be included into the kernel. They are GNU > licensed. Seemingly the SiS updates the existing sis900 driver, the > FA311 is not yet supported by the kernel. Not true, see natsemi.c (in 2.4.x at least). -- Jeff Garzik | "You see, in this world there's two kinds of Building 1024 | people, my friend: Those with loaded guns MandrakeSoft | and those who dig. You dig." --Blondie - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Ethernet drivers: SiS 900, Netgear FA311
Hi, I think those drivers have not yet been merged. Since I happend to have those (and had problem to get them run with the default kernel) I'd like to asked whether those can be included into the kernel. They are GNU licensed. Seemingly the SiS updates the existing sis900 driver, the FA311 is not yet supported by the kernel. http://www.sis.com.tw/ftp/Drivers/linux/630s/ readme.txt 13-Nov-2000 03:58 3k sis900.c13-Nov-2000 03:5846k sis900.h13-Nov-2000 03:58 9k http://www.netgear-support.com/ts/pwtservicepacks.cfm?spc=0=FA311=0 (e.g. fa311lx.zip: -rw-rw-rw- 48047 Aug 24 22:36 fa311.c -rw-rw-rw- 33203 Aug 24 22:36 fa311.h -rw-rw-rw-7820 Aug 24 22:36 fa311.o -rw-rw-rw- 131 Aug 24 22:36 makefile Tobias -- This above all: To thine own self be true / And it must follow as the night the day / Thou canst not then be false to any man. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Ethernet drivers: SiS 900, Netgear FA311
Hi, I think those drivers have not yet been merged. Since I happend to have those (and had problem to get them run with the default kernel) I'd like to asked whether those can be included into the kernel. They are GNU licensed. Seemingly the SiS updates the existing sis900 driver, the FA311 is not yet supported by the kernel. http://www.sis.com.tw/ftp/Drivers/linux/630s/ readme.txt 13-Nov-2000 03:58 3k sis900.c13-Nov-2000 03:5846k sis900.h13-Nov-2000 03:58 9k http://www.netgear-support.com/ts/pwtservicepacks.cfm?spc=0ss=FA311sortby=0 (e.g. fa311lx.zip: -rw-rw-rw- 48047 Aug 24 22:36 fa311.c -rw-rw-rw- 33203 Aug 24 22:36 fa311.h -rw-rw-rw-7820 Aug 24 22:36 fa311.o -rw-rw-rw- 131 Aug 24 22:36 makefile Tobias -- This above all: To thine own self be true / And it must follow as the night the day / Thou canst not then be false to any man. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Ethernet drivers: SiS 900, Netgear FA311
Tobias Burnus wrote: I think those drivers have not yet been merged. Since I happend to have those (and had problem to get them run with the default kernel) I'd like to asked whether those can be included into the kernel. They are GNU licensed. Seemingly the SiS updates the existing sis900 driver, the FA311 is not yet supported by the kernel. Not true, see natsemi.c (in 2.4.x at least). -- Jeff Garzik | "You see, in this world there's two kinds of Building 1024 | people, my friend: Those with loaded guns MandrakeSoft | and those who dig. You dig." --Blondie - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Netgear FA311
On Mon, 25 Dec 2000, Manfred wrote: > Could you try this setup? > > /* Configure the PCI bus bursts and FIFO thresholds. */ > /* Configure for standard, in-spec Ethernet. */ > np->tx_config = (1<<28) + /* Automatic transmit padding */ > (1<<23) + /* Excessive collision retry */ > (6<<20) + /* Max DMA burst = 128 byte */ > (8<<8) +/* fill threshold = 256 byte */ > 8; /* drain threshold = 256 byte */ > writel(np->tx_config, ioaddr + TxConfig); > Hmm, that little change worked a lot better. However thoughput is down to 700kb/s! Transferring files from the other machine to this machine is much faster - 868kb/s. In the logs, I only got *one* message from the natsemi driver (and this happened when sending files from this machine to the other machine. No problems receiving from the other machine. Dec 25 17:28:12 tahallah kernel: eth0: Something Wicked happened! 0583. But I just realised that the other machine I'm using has an 10 megabit ethernet card (on the hub that one is shown on 10, my machine is shown as 100). I think this explains the throughput problem. When I get another 4 way power socket, I'll put my other machine (which has a 100 megabit card in it) on the network and see if that makes a difference. Cheers, Alex -- Huffapuff! http://www.tahallah.clara.co.uk - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Netgear FA311
Alex wrote: > In the logs I'm seeing this: > > Dec 25 15:25:18 tahallah last message repeated 2 times > Dec 25 15:25:19 tahallah kernel: eth0: Something Wicked happened! 0783. > Dec 25 15:25:19 tahallah kernel: eth0: Something Wicked happened! 0780. 783 means: Tx Underrun Tx Idle Tx Packet Error Tx Descriptor Rx Packet Error Rx Descriptor Rx OK. Hmm. I download the Documentation from National (http://www.national.com/pf/DP/DP83815.html), and the the tx burst size/fill threshold/drain threshold combination is invalid: from natsemi.c: /* Configure the PCI bus bursts and FIFO thresholds. */ /* Configure for standard, in-spec Ethernet. */ np->tx_config = (1<<28) + /* Automatic transmit padding */ (1<<23) + /* Excessive collision retry */ (0x0<<20) + /* Max DMA burst = 512 byte */ (8<<8) +/* fill threshold = 256 byte */ 2; /* drain threshold = 64 byte */ writel(np->tx_config, ioaddr + TxConfig); But: page 51 The MXDMA MUST NOT be greater than the Tx Fill Threshold >> Could you try this setup? /* Configure the PCI bus bursts and FIFO thresholds. */ /* Configure for standard, in-spec Ethernet. */ np->tx_config = (1<<28) + /* Automatic transmit padding */ (1<<23) + /* Excessive collision retry */ (6<<20) + /* Max DMA burst = 128 byte */ (8<<8) +/* fill threshold = 256 byte */ 8; /* drain threshold = 256 byte */ writel(np->tx_config, ioaddr + TxConfig); -- Manfred - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Netgear FA311
Well now I've just set up the network and everything works a treat, currently getting 850kb/s file transfers. Cool. Except for one thing. In the logs I'm seeing this: Dec 25 15:25:18 tahallah last message repeated 2 times Dec 25 15:25:19 tahallah kernel: eth0: Something Wicked happened! 0783. Dec 25 15:25:19 tahallah kernel: eth0: Something Wicked happened! 0780. Dec 25 15:25:19 tahallah last message repeated 2 times Dec 25 15:25:19 tahallah kernel: eth0: Something Wicked happened! 0580. Dec 25 15:25:19 tahallah kernel: eth0: Something Wicked happened! 0783. Dec 25 15:25:19 tahallah kernel: eth0: Something Wicked happened! 0780. Dec 25 15:25:21 tahallah last message repeated 3 times Dec 25 15:25:21 tahallah kernel: eth0: Something Wicked happened! 0783. Dec 25 15:25:22 tahallah kernel: eth0: Something Wicked happened! 0780. That's just a small snippet. Apart from those messages, all seems OK, but I'm just wondering why it's getting those messages - what does those mean? Cheers, Alex -- Huffapuff! http://www.tahallah.clara.co.uk - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Netgear FA311
Well now I've just set up the network and everything works a treat, currently getting 850kb/s file transfers. Cool. Except for one thing. In the logs I'm seeing this: Dec 25 15:25:18 tahallah last message repeated 2 times Dec 25 15:25:19 tahallah kernel: eth0: Something Wicked happened! 0783. Dec 25 15:25:19 tahallah kernel: eth0: Something Wicked happened! 0780. Dec 25 15:25:19 tahallah last message repeated 2 times Dec 25 15:25:19 tahallah kernel: eth0: Something Wicked happened! 0580. Dec 25 15:25:19 tahallah kernel: eth0: Something Wicked happened! 0783. Dec 25 15:25:19 tahallah kernel: eth0: Something Wicked happened! 0780. Dec 25 15:25:21 tahallah last message repeated 3 times Dec 25 15:25:21 tahallah kernel: eth0: Something Wicked happened! 0783. Dec 25 15:25:22 tahallah kernel: eth0: Something Wicked happened! 0780. That's just a small snippet. Apart from those messages, all seems OK, but I'm just wondering why it's getting those messages - what does those mean? Cheers, Alex -- Huffapuff! http://www.tahallah.clara.co.uk - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Netgear FA311
Alex wrote: In the logs I'm seeing this: Dec 25 15:25:18 tahallah last message repeated 2 times Dec 25 15:25:19 tahallah kernel: eth0: Something Wicked happened! 0783. Dec 25 15:25:19 tahallah kernel: eth0: Something Wicked happened! 0780. 783 means: Tx Underrun Tx Idle Tx Packet Error Tx Descriptor Rx Packet Error Rx Descriptor Rx OK. Hmm. I download the Documentation from National (http://www.national.com/pf/DP/DP83815.html), and the the tx burst size/fill threshold/drain threshold combination is invalid: from natsemi.c: /* Configure the PCI bus bursts and FIFO thresholds. */ /* Configure for standard, in-spec Ethernet. */ np-tx_config = (128) + /* Automatic transmit padding */ (123) + /* Excessive collision retry */ (0x020) + /* Max DMA burst = 512 byte */ (88) +/* fill threshold = 256 byte */ 2; /* drain threshold = 64 byte */ writel(np-tx_config, ioaddr + TxConfig); But: page 51 The MXDMA MUST NOT be greater than the Tx Fill Threshold Could you try this setup? /* Configure the PCI bus bursts and FIFO thresholds. */ /* Configure for standard, in-spec Ethernet. */ np-tx_config = (128) + /* Automatic transmit padding */ (123) + /* Excessive collision retry */ (620) + /* Max DMA burst = 128 byte */ (88) +/* fill threshold = 256 byte */ 8; /* drain threshold = 256 byte */ writel(np-tx_config, ioaddr + TxConfig); -- Manfred - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Netgear FA311
On Mon, 25 Dec 2000, Manfred wrote: Could you try this setup? /* Configure the PCI bus bursts and FIFO thresholds. */ /* Configure for standard, in-spec Ethernet. */ np-tx_config = (128) + /* Automatic transmit padding */ (123) + /* Excessive collision retry */ (620) + /* Max DMA burst = 128 byte */ (88) +/* fill threshold = 256 byte */ 8; /* drain threshold = 256 byte */ writel(np-tx_config, ioaddr + TxConfig); Hmm, that little change worked a lot better. However thoughput is down to 700kb/s! Transferring files from the other machine to this machine is much faster - 868kb/s. In the logs, I only got *one* message from the natsemi driver (and this happened when sending files from this machine to the other machine. No problems receiving from the other machine. Dec 25 17:28:12 tahallah kernel: eth0: Something Wicked happened! 0583. But I just realised that the other machine I'm using has an 10 megabit ethernet card (on the hub that one is shown on 10, my machine is shown as 100). I think this explains the throughput problem. When I get another 4 way power socket, I'll put my other machine (which has a 100 megabit card in it) on the network and see if that makes a difference. Cheers, Alex -- Huffapuff! http://www.tahallah.clara.co.uk - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Netgear FA311 (follow-up)
On Sat, 23 Dec 2000, Alex Buell wrote: > I recently bought a Netgear FA311 which does 10/100Mb/ethernet for my > first home network. I've looked and found driver sources which > apparently works only for 2.0.36. Ulp! Before I start cracking my > knuckles and working my deep magic to get it to work on 2.2.x, is > there any drivers already sorted for this card on the 2.2.x series? Thanks to everyone who replied. I've now got Donald Becker's natsemi drivers from his site and have successfully compiled it. Whether it'll work is another story as I've got to crack this box and put in the card.. Won't be long before I'll have my 100 megabits home network up and running, I hope. Not long before I'll frag my kid brother in Quake too! Cheers, Alex -- I stand in my undergarments and hurl inventive in your general direction. http://www.tahallah.clara.co.uk - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Netgear FA311
On Sat, 23 Dec 2000, Alex Buell wrote: > On Sat, 23 Dec 2000, Marcus Meissner wrote: > > > > Is this where you got the sources? > > > http://www.scyld.com/network/natsemi.html (Thanks Steve) > > > > The linux driver is actually on the accompanying floppy disk. Without license > > statement unfortunately. > > I got a floppy disk with the netgear fa311, but the only linux sources on > it was for 2.0.36! yeah i believe that natsemi driver is supposed to work with that 311 card, although i have heard of issues with that now and then. to be honest i haven't followed very closely, as i don't use those cards/chips. that scyld.com page should have all the info you need, as well as info on an accompianing mailing list for further help. if whatever distro/kernel you're using already has a compiled natsemi driver you can just try it out by messing with /etc/conf.modules or /etc/modules.conf or whatever proper files your distribution uses. -tcl. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Netgear FA311
On Sat, 23 Dec 2000, Marcus Meissner wrote: > > Is this where you got the sources? > > http://www.scyld.com/network/natsemi.html (Thanks Steve) > > The linux driver is actually on the accompanying floppy disk. Without license > statement unfortunately. I got a floppy disk with the netgear fa311, but the only linux sources on it was for 2.0.36! Cheers, Alex -- I stand in my undergarments and hurl inventive in your general direction. http://www.tahallah.clara.co.uk - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Netgear FA311
In article <[EMAIL PROTECTED]> you wrote: > Is this where you got the sources? > http://www.scyld.com/network/natsemi.html (Thanks Steve) The linux driver is actually on the accompanying floppy disk. Without license statement unfortunately. Ciao, Marcus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Netgear FA311
Is this where you got the sources? http://www.scyld.com/network/natsemi.html (Thanks Steve) Alex Buell wrote: > > I recently bought a Netgear FA311 which does 10/100Mb/ethernet for my > first home network. I've looked and found driver sources which apparently -- = Mohammad A. Haque http://www.haque.net/ [EMAIL PROTECTED] "Alcohol and calculus don't mix. Project Lead Don't drink and derive." --Unknown http://wm.themes.org/ [EMAIL PROTECTED] = - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Netgear FA311
I don't know how its different from the FA310TX that I have. The 310TX uses the tulip drivers so you may want to give that a shot. Maybe you can get us a name/number off the IC on the card? Alex Buell wrote: > > I recently bought a Netgear FA311 which does 10/100Mb/ethernet for my > first home network. I've looked and found driver sources which apparently > works only for 2.0.36. Ulp! Before I start cracking my knuckles and > working my deep magic to get it to work on 2.2.x, is there any drivers > already sorted for this card on the 2.2.x series? > > If not, where can I find documentation on converting 2.0.x drivers to > 2.2.x? -- = Mohammad A. Haque http://www.haque.net/ [EMAIL PROTECTED] "Alcohol and calculus don't mix. Project Lead Don't drink and derive." --Unknown http://wm.themes.org/ [EMAIL PROTECTED] = - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Netgear FA311
I recently bought a Netgear FA311 which does 10/100Mb/ethernet for my first home network. I've looked and found driver sources which apparently works only for 2.0.36. Ulp! Before I start cracking my knuckles and working my deep magic to get it to work on 2.2.x, is there any drivers already sorted for this card on the 2.2.x series? If not, where can I find documentation on converting 2.0.x drivers to 2.2.x? Thanks. Cheers, Alex -- I stand in my undergarments and hurl inventive in your general direction. http://www.tahallah.clara.co.uk - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Netgear FA311
I recently bought a Netgear FA311 which does 10/100Mb/ethernet for my first home network. I've looked and found driver sources which apparently works only for 2.0.36. Ulp! Before I start cracking my knuckles and working my deep magic to get it to work on 2.2.x, is there any drivers already sorted for this card on the 2.2.x series? If not, where can I find documentation on converting 2.0.x drivers to 2.2.x? Thanks. Cheers, Alex -- I stand in my undergarments and hurl inventive in your general direction. http://www.tahallah.clara.co.uk - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Netgear FA311
I don't know how its different from the FA310TX that I have. The 310TX uses the tulip drivers so you may want to give that a shot. Maybe you can get us a name/number off the IC on the card? Alex Buell wrote: I recently bought a Netgear FA311 which does 10/100Mb/ethernet for my first home network. I've looked and found driver sources which apparently works only for 2.0.36. Ulp! Before I start cracking my knuckles and working my deep magic to get it to work on 2.2.x, is there any drivers already sorted for this card on the 2.2.x series? If not, where can I find documentation on converting 2.0.x drivers to 2.2.x? -- = Mohammad A. Haque http://www.haque.net/ [EMAIL PROTECTED] "Alcohol and calculus don't mix. Project Lead Don't drink and derive." --Unknown http://wm.themes.org/ [EMAIL PROTECTED] = - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Netgear FA311
Is this where you got the sources? http://www.scyld.com/network/natsemi.html (Thanks Steve) Alex Buell wrote: I recently bought a Netgear FA311 which does 10/100Mb/ethernet for my first home network. I've looked and found driver sources which apparently -- = Mohammad A. Haque http://www.haque.net/ [EMAIL PROTECTED] "Alcohol and calculus don't mix. Project Lead Don't drink and derive." --Unknown http://wm.themes.org/ [EMAIL PROTECTED] = - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Netgear FA311
In article [EMAIL PROTECTED] you wrote: Is this where you got the sources? http://www.scyld.com/network/natsemi.html (Thanks Steve) The linux driver is actually on the accompanying floppy disk. Without license statement unfortunately. Ciao, Marcus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Netgear FA311
On Sat, 23 Dec 2000, Alex Buell wrote: On Sat, 23 Dec 2000, Marcus Meissner wrote: Is this where you got the sources? http://www.scyld.com/network/natsemi.html (Thanks Steve) The linux driver is actually on the accompanying floppy disk. Without license statement unfortunately. I got a floppy disk with the netgear fa311, but the only linux sources on it was for 2.0.36! yeah i believe that natsemi driver is supposed to work with that 311 card, although i have heard of issues with that now and then. to be honest i haven't followed very closely, as i don't use those cards/chips. that scyld.com page should have all the info you need, as well as info on an accompianing mailing list for further help. if whatever distro/kernel you're using already has a compiled natsemi driver you can just try it out by messing with /etc/conf.modules or /etc/modules.conf or whatever proper files your distribution uses. -tcl. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Netgear FA311 (follow-up)
On Sat, 23 Dec 2000, Alex Buell wrote: I recently bought a Netgear FA311 which does 10/100Mb/ethernet for my first home network. I've looked and found driver sources which apparently works only for 2.0.36. Ulp! Before I start cracking my knuckles and working my deep magic to get it to work on 2.2.x, is there any drivers already sorted for this card on the 2.2.x series? Thanks to everyone who replied. I've now got Donald Becker's natsemi drivers from his site and have successfully compiled it. Whether it'll work is another story as I've got to crack this box and put in the card.. Won't be long before I'll have my 100 megabits home network up and running, I hope. big evil grin Not long before I'll frag my kid brother in Quake too! Cheers, Alex -- I stand in my undergarments and hurl inventive in your general direction. http://www.tahallah.clara.co.uk - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
