RE: [leaf-user] rtl8139.o and Bering 1.1
If I am not mistaken, rtl8139 was based on the original Becker driver( God bless him) and 8139too was a more modern rewrite which addressed many of the glaring deficiencies of that chip. By the way, 8139 is one of those chips subject the ethernet buffer overflow security hole, which the 8139too driver takes care of it by padding the buffer with nulls. mii is, I believe, a pci bus scan. David Pitts [EMAIL PROTECTED] on 02/18/2003 09:05:54 PM To: [EMAIL PROTECTED] cc:(bcc: Phillip Watts/austin/Nlynx) Subject: RE: [leaf-user] rtl8139.o and Bering 1.1 I have successfully been using this combination as well. ie 8139too.o and mii.o. What is preferred for rtl8139 based adaptors? David Pitts IT Services Manager Reid Library University of Western Australia Telephone: (08) 9380 3492 Fax: (08) 9380 1012 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 19 February 2003 5:05 AM To: Chris Hackett Cc: '[EMAIL PROTECTED]' Subject: Re: [leaf-user] rtl8139.o and Bering 1.1 I've been using 8139too.o which I believe requires mii.o for a long time. I forget the issues. Chris Hackett [EMAIL PROTECTED] on 02/18/2003 02:05:55 PM To: '[EMAIL PROTECTED]' [EMAIL PROTECTED] cc:(bcc: Phillip Watts/austin/Nlynx) Subject: [leaf-user] rtl8139.o and Bering 1.1 Hello List! I'm trying to build a Bering 1.1 disk and am wondering if there are any known issues with the rtl8139.o and the Bering 1.1 image? I have put it in the /lib/modules and made the appropriate mods to get it to load. During the boot process, I see something like this: Loading modules rtl8139 - using /lib/modules insmod: unresolved symbol pci_drv_unregister insmod: unresolved symbol pci_drv_register I'm using the rtl8139.o in the same machine with the Eiger2Beta image, and I don't see the unresolved symbol messages with that image. Does anyone have ideas? Are these messages even important? Or can they safely be ignored? Also, after the image laods, when I log into the box, an ip link shows only the 'lo interface .. no eth0 or eth1 that I can find. If anyone can point me in the right direction, I'd sure appreciate it. Thanks!! Chris Hackett --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
RE: [leaf-user] rtl8139.o and Bering 1.1
See http://www.scyld.com/network/rtl8139.html. Becker goes into a bit of a rant about the 8139too driver. -Richard On Wed, 2003-02-19 at 06:20, [EMAIL PROTECTED] wrote: If I am not mistaken, rtl8139 was based on the original Becker driver( God bless him) and 8139too was a more modern rewrite which addressed many of the glaring deficiencies of that chip. By the way, 8139 is one of those chips subject the ethernet buffer overflow security hole, which the 8139too driver takes care of it by padding the buffer with nulls. mii is, I believe, a pci bus scan. David Pitts [EMAIL PROTECTED] on 02/18/2003 09:05:54 PM To: [EMAIL PROTECTED] cc:(bcc: Phillip Watts/austin/Nlynx) Subject: RE: [leaf-user] rtl8139.o and Bering 1.1 I have successfully been using this combination as well. ie 8139too.o and mii.o. What is preferred for rtl8139 based adaptors? David Pitts IT Services Manager Reid Library University of Western Australia Telephone: (08) 9380 3492 Fax: (08) 9380 1012 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 19 February 2003 5:05 AM To: Chris Hackett Cc: '[EMAIL PROTECTED]' Subject: Re: [leaf-user] rtl8139.o and Bering 1.1 I've been using 8139too.o which I believe requires mii.o for a long time. I forget the issues. Chris Hackett [EMAIL PROTECTED] on 02/18/2003 02:05:55 PM To: '[EMAIL PROTECTED]' [EMAIL PROTECTED] cc:(bcc: Phillip Watts/austin/Nlynx) Subject: [leaf-user] rtl8139.o and Bering 1.1 Hello List! I'm trying to build a Bering 1.1 disk and am wondering if there are any known issues with the rtl8139.o and the Bering 1.1 image? I have put it in the /lib/modules and made the appropriate mods to get it to load. During the boot process, I see something like this: Loading modules rtl8139 - using /lib/modules insmod: unresolved symbol pci_drv_unregister insmod: unresolved symbol pci_drv_register I'm using the rtl8139.o in the same machine with the Eiger2Beta image, and I don't see the unresolved symbol messages with that image. Does anyone have ideas? Are these messages even important? Or can they safely be ignored? Also, after the image laods, when I log into the box, an ip link shows only the 'lo interface .. no eth0 or eth1 that I can find. If anyone can point me in the right direction, I'd sure appreciate it. Thanks!! Chris Hackett --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html -- Richard Doyle [EMAIL PROTECTED] --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
RE: [leaf-user] rtl8139.o and Bering 1.1
Very informative. Thanks. Richard Doyle [EMAIL PROTECTED] on 02/19/2003 02:37:49 PM To: Phillip Watts/austin/Nlynx@Nlynx cc: David Pitts [EMAIL PROTECTED], [EMAIL PROTECTED] [EMAIL PROTECTED] Subject: RE: [leaf-user] rtl8139.o and Bering 1.1 See http://www.scyld.com/network/rtl8139.html. Becker goes into a bit of a rant about the 8139too driver. -Richard On Wed, 2003-02-19 at 06:20, [EMAIL PROTECTED] wrote: If I am not mistaken, rtl8139 was based on the original Becker driver( God bless him) and 8139too was a more modern rewrite which addressed many of the glaring deficiencies of that chip. By the way, 8139 is one of those chips subject the ethernet buffer overflow security hole, which the 8139too driver takes care of it by padding the buffer with nulls. mii is, I believe, a pci bus scan. David Pitts [EMAIL PROTECTED] on 02/18/2003 09:05:54 PM To: [EMAIL PROTECTED] cc:(bcc: Phillip Watts/austin/Nlynx) Subject: RE: [leaf-user] rtl8139.o and Bering 1.1 I have successfully been using this combination as well. ie 8139too.o and mii.o. What is preferred for rtl8139 based adaptors? David Pitts IT Services Manager Reid Library University of Western Australia Telephone: (08) 9380 3492 Fax: (08) 9380 1012 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 19 February 2003 5:05 AM To: Chris Hackett Cc: '[EMAIL PROTECTED]' Subject: Re: [leaf-user] rtl8139.o and Bering 1.1 I've been using 8139too.o which I believe requires mii.o for a long time. I forget the issues. Chris Hackett [EMAIL PROTECTED] on 02/18/2003 02:05:55 PM To: '[EMAIL PROTECTED]' [EMAIL PROTECTED] cc:(bcc: Phillip Watts/austin/Nlynx) Subject: [leaf-user] rtl8139.o and Bering 1.1 Hello List! I'm trying to build a Bering 1.1 disk and am wondering if there are any known issues with the rtl8139.o and the Bering 1.1 image? I have put it in the /lib/modules and made the appropriate mods to get it to load. During the boot process, I see something like this: Loading modules rtl8139 - using /lib/modules insmod: unresolved symbol pci_drv_unregister insmod: unresolved symbol pci_drv_register I'm using the rtl8139.o in the same machine with the Eiger2Beta image, and I don't see the unresolved symbol messages with that image. Does anyone have ideas? Are these messages even important? Or can they safely be ignored? Also, after the image laods, when I log into the box, an ip link shows only the 'lo interface .. no eth0 or eth1 that I can find. If anyone can point me in the right direction, I'd sure appreciate it. Thanks!! Chris Hackett --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html -- Richard Doyle [EMAIL PROTECTED] --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge leaf-user mailing list
RE: [leaf-user] rtl8139.o and Bering 1.1
As well as very old. I first saw this rant a couple years ago. At the time I needed an 8139 driver and the RTL8139 just didn't work with the 8139B chip. So I thought I'd try the 8139too in spite of the rant. It worked where the RTL8139 didn't... At 01:23 PM 2/19/2003, [EMAIL PROTECTED] wrote Very informative. Thanks. Richard Doyle [EMAIL PROTECTED] on 02/19/2003 02:37:49 PM To: Phillip Watts/austin/Nlynx@Nlynx cc: David Pitts [EMAIL PROTECTED], [EMAIL PROTECTED] [EMAIL PROTECTED] Subject: RE: [leaf-user] rtl8139.o and Bering 1.1 See http://www.scyld.com/network/rtl8139.html. Becker goes into a bit of a rant about the 8139too driver. -Richard Mike Sensney Association Services, Inc. PO Box 58530, Seattle, WA 98138-1530 206-623-8632 - Fax 206-575-9255 --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
[leaf-user] rtl8139.o and Bering 1.1
Hello List! I'm trying to build a Bering 1.1 disk and am wondering if there are any known issues with the rtl8139.o and the Bering 1.1 image? I have put it in the /lib/modules and made the appropriate mods to get it to load. During the boot process, I see something like this: Loading modules rtl8139 - using /lib/modules insmod: unresolved symbol pci_drv_unregister insmod: unresolved symbol pci_drv_register I'm using the rtl8139.o in the same machine with the Eiger2Beta image, and I don't see the unresolved symbol messages with that image. Does anyone have ideas? Are these messages even important? Or can they safely be ignored? Also, after the image laods, when I log into the box, an ip link shows only the 'lo interface .. no eth0 or eth1 that I can find. If anyone can point me in the right direction, I'd sure appreciate it. Thanks!! Chris Hackett --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
Re: [leaf-user] rtl8139.o and Bering 1.1
Le Mardi 18 Février 2003 21:05, Chris Hackett a écrit : Hello List! I'm trying to build a Bering 1.1 disk and am wondering if there are any known issues with the rtl8139.o and the Bering 1.1 image? I have put it in the /lib/modules and made the appropriate mods to get it to load. During the boot process, I see something like this: Loading modules rtl8139 - using /lib/modules insmod: unresolved symbol pci_drv_unregister insmod: unresolved symbol pci_drv_register As shown in the 2.4.20 modules.dep file: http://leaf.sourceforge.net/devel/jnilo/bering/1.1/modules/2.4.20/modules.dep rtl8139.o depens on pci-scan.o which must be loaded first. Jacques --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
Re: [leaf-user] rtl8139.o and Bering 1.1
I've been using 8139too.o which I believe requires mii.o for a long time. I forget the issues. Chris Hackett [EMAIL PROTECTED] on 02/18/2003 02:05:55 PM To: '[EMAIL PROTECTED]' [EMAIL PROTECTED] cc:(bcc: Phillip Watts/austin/Nlynx) Subject: [leaf-user] rtl8139.o and Bering 1.1 Hello List! I'm trying to build a Bering 1.1 disk and am wondering if there are any known issues with the rtl8139.o and the Bering 1.1 image? I have put it in the /lib/modules and made the appropriate mods to get it to load. During the boot process, I see something like this: Loading modules rtl8139 - using /lib/modules insmod: unresolved symbol pci_drv_unregister insmod: unresolved symbol pci_drv_register I'm using the rtl8139.o in the same machine with the Eiger2Beta image, and I don't see the unresolved symbol messages with that image. Does anyone have ideas? Are these messages even important? Or can they safely be ignored? Also, after the image laods, when I log into the box, an ip link shows only the 'lo interface .. no eth0 or eth1 that I can find. If anyone can point me in the right direction, I'd sure appreciate it. Thanks!! Chris Hackett --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
RE: [leaf-user] rtl8139.o and Bering 1.1
I have successfully been using this combination as well. ie 8139too.o and mii.o. What is preferred for rtl8139 based adaptors? David Pitts IT Services Manager Reid Library University of Western Australia Telephone: (08) 9380 3492 Fax: (08) 9380 1012 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 19 February 2003 5:05 AM To: Chris Hackett Cc: '[EMAIL PROTECTED]' Subject: Re: [leaf-user] rtl8139.o and Bering 1.1 I've been using 8139too.o which I believe requires mii.o for a long time. I forget the issues. Chris Hackett [EMAIL PROTECTED] on 02/18/2003 02:05:55 PM To: '[EMAIL PROTECTED]' [EMAIL PROTECTED] cc:(bcc: Phillip Watts/austin/Nlynx) Subject: [leaf-user] rtl8139.o and Bering 1.1 Hello List! I'm trying to build a Bering 1.1 disk and am wondering if there are any known issues with the rtl8139.o and the Bering 1.1 image? I have put it in the /lib/modules and made the appropriate mods to get it to load. During the boot process, I see something like this: Loading modules rtl8139 - using /lib/modules insmod: unresolved symbol pci_drv_unregister insmod: unresolved symbol pci_drv_register I'm using the rtl8139.o in the same machine with the Eiger2Beta image, and I don't see the unresolved symbol messages with that image. Does anyone have ideas? Are these messages even important? Or can they safely be ignored? Also, after the image laods, when I log into the box, an ip link shows only the 'lo interface .. no eth0 or eth1 that I can find. If anyone can point me in the right direction, I'd sure appreciate it. Thanks!! Chris Hackett --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
Re: [leaf-user] rtl8139.o and Bering 1.1
On Tuesday 18 February 2003 09:05 pm, David Pitts wrote: I have successfully been using this combination as well. ie 8139too.o and mii.o. What is preferred for rtl8139 based adaptors? The 8139too is the 'version 2' module that should work (possibly better) with all rtl8139 chipsets, IIRC, unlike my experience with the different tulip chipsets. -- ~Lynn Avants Linux Embedded Firewall Project developer http://leaf.sourceforge.net --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html