Has anyone had any success getting this module working with any of the 8.2 kernels. My current mobo has this intergrated and I can't get it working. Any ideas? Alfredo
Hi Alfredo! yup. works fine for me. what is the error? -- michael On Wed, 27 Aug 2003, Alfredo Yunes wrote:
Has anyone had any success getting this module working with any of the 8.2 kernels. My current mobo has this intergrated and I can't get it working. Any ideas?
Michael Galloway wrote:
Hi Alfredo! yup. works fine for me. what is the error? in reply to: On Wed, 27 Aug 2003, Alfredo Yunes wrote:
Has anyone had any success getting this module working with any of the 8.2 kernels. My current mobo has this intergrated and I can't get it working. Any ideas?
I have the same problem. The install appeared to detect the NIC and I told it all the static parameters I need. I'm a newbie with SuSE and the only message that seems relevant is in /var/log/boot.msg: <notice>/etc/init.d/rc3.d/S05network start Setting up network interfaces: lo done eth0 failed <notice>'/etc/init.d/rc3.d/S05network start' exits with status 0 Is there somewhere else I can find better information to debug? Thanks, Dave
Hi Dave! do an lsmod to see if the e1000 module is loaded: watson:~ # lsmod e1000 65924 1 if not try to install the module by hand: insmod e1000 -- michael On Thu, 28 Aug 2003, Dave Howorth wrote:
I have the same problem. The install appeared to detect the NIC and I told it all the static parameters I need. I'm a newbie with SuSE and the only message that seems relevant is in /var/log/boot.msg:
<notice>/etc/init.d/rc3.d/S05network start Setting up network interfaces: lo done eth0 failed <notice>'/etc/init.d/rc3.d/S05network start' exits with status 0
Is there somewhere else I can find better information to debug?
Thanks, Dave
Michael Galloway wrote:
do an lsmod to see if the e1000 module is loaded:
Done - the answer is no.
if not try to install the module by hand: insmod e1000
Fails - the output is: Using lib/modules/2.4.20-64GB-SMP/kernel/drivers/net/e1000/e1000.o /lib/modules/2.4.20-64GB-SMP/kernel/drivers/net/e1000/e1000.o: init_module: No such device Hint <snip> syslog or <snip> dmesg There's nothing in dmesg that seems relevant and there doesn't seem to be a syslog anywhere under /var ??? How do I fix 'no such device'? On my Debian box there is a /proc/sys/net/ipv4/conf/eth0 There's no such directory on the SuSE box, FWIW. Thanks, Dave
On Thursday 28 August 2003 15:55, Dave Howorth wrote: <SNIP>
On my Debian box there is a /proc/sys/net/ipv4/conf/eth0 There's no such directory on the SuSE box, FWIW.
It'll only be there once the card is set up successfully. HTH Dylan
Thanks, Dave
-- Sweet moderation Heart of this nation Desert us not We are between the wars - Billy Bragg
Dylan wrote:
On my Debian box there is a /proc/sys/net/ipv4/conf/eth0 There's no such directory on the SuSE box, FWIW. It'll only be there once the card is set up successfully. HTH
Well, I guess it's nice to know :) Even more interesting would be how to set up the interface! The interface is not a card, it's on the mobo, BTW. I'm running with failsafe startup so noapic and acpi=off are there. lspci -v says: 02:01.0 Ethernet controller: Intel Corp: Unknown device 1019 Subsystem: Intel Corp.: Unknown device 3025 Flags: bus master, 66Mhz, medium devsel, latency 0, IRQ 9 Memory at ff9e0000 (32-bit, non-prefetchable) [size=128K] I/O ports at cc00 [size=32] Capabilities: [dc] Power Management version 2 (with acpi enabled, the IRQ is 18. apic doesn't seem to change anything.) Thanks, Dave
Dave Howorth wrote:
lspci -v says:
02:01.0 Ethernet controller: Intel Corp: Unknown device 1019 Subsystem: Intel Corp.: Unknown device 3025 Flags: bus master, 66Mhz, medium devsel, latency 0, IRQ 9 Memory at ff9e0000 (32-bit, non-prefetchable) [size=128K] I/O ports at cc00 [size=32] Capabilities: [dc] Power Management version 2
Oh, change to 2.4.21. This should work then. -- Andreas
I also have this integrated into the mobo (Albatron 865PE ProII) and the only way I was able to make it work was to upgrade to Mantel's 2.4.21 kernel. Alfredo On Thu, 2003-08-28 at 10:31, Dave Howorth wrote:
Michael Galloway wrote:
Hi Alfredo! yup. works fine for me. what is the error? in reply to: On Wed, 27 Aug 2003, Alfredo Yunes wrote:
Has anyone had any success getting this module working with any of the 8.2 kernels. My current mobo has this intergrated and I can't get it working. Any ideas?
I have the same problem. The install appeared to detect the NIC and I told it all the static parameters I need. I'm a newbie with SuSE and the only message that seems relevant is in /var/log/boot.msg:
<notice>/etc/init.d/rc3.d/S05network start Setting up network interfaces: lo done eth0 failed <notice>'/etc/init.d/rc3.d/S05network start' exits with status 0
Is there somewhere else I can find better information to debug?
Thanks, Dave -- Alfredo Yunes <alyunes@optonline.net>
Alfredo Yunes wrote:
I also have this integrated into the mobo (Albatron 865PE ProII) and the only way I was able to make it work was to upgrade to Mantel's 2.4.21 kernel.
Thanks for the link to Mantel - I'm now using his vmlinuz-2.4.21-58-smp. I've persuaded the kernel to boot (the default command-line options caused an error) but eth0 doesn't come up. There's a message: Setting up network interfaces: eth0 failed Is there a log or command to discover more detail of the problem? Once it's booted I can start the network by hand (modprobe e1000; ifup eth0) so it seems likely to be a config error somewhere. Is there a way to make it load automatically? Or what is the SuSE way to configure it manually (rc.local etc)? Thanks, Dave
Dave Howorth wrote:
I also have this integrated into the mobo (Albatron 865PE ProII) and the only way I was able to make it work was to upgrade to Mantel's 2.4.21 kernel.
Thanks for the link to Mantel - I'm now using his vmlinuz-2.4.21-58-smp. I've persuaded the kernel to boot (the default command-line options caused an error) but eth0 doesn't come up. There's a message:
Setting up network interfaces: eth0 failed
Is there a log or command to discover more detail of the problem?
Once it's booted I can start the network by hand (modprobe e1000; ifup eth0) so it seems likely to be a config error somewhere.
Is there a way to make it load automatically? Or what is the SuSE way to configure it manually (rc.local etc)?
Go to /etc/modules.conf and check, if eth0 is assigned to e1000. And maybe check your bootup "dmesg | less". -- Andreas
Andreas Winkelmann wrote:
Go to /etc/modules.conf and check, if eth0 is assigned to e1000.
Andreas, many thanks for your continuing patience and help. eth0 appears in two lines and one's a comment: alias eth0 off #alias eth0 nvnet e1000 does not occur in the file. I don't know anything about kernel modules or this file, so after a quick look at the man page I did 'modprobe -c', expecting to see a line for e1000 (because I have now installed that module) but there was nothing, just the same line for eth0. I'd guess that taking out the 'alias eth0 off' line might permit the module to load properly, but I'm nervous about making changes when (a) I don't understand how/why it got to be like that, and (b) I suspect there may be a SuSE-way (yast?) to make the change rather than just edit the file. I made the change but it didn't change the behaviour so I've put it back how it was
And maybe check your bootup "dmesg | less".
The only lines referring to the e1000 driver are at the end: Intel(R) PRO/1000 Network Driver - version 5.2.13 Copyright (c) 1999-2003 Intel Corporation. PCI: Setting latency timer of device 02:01.0 to 64 eth0: Intel(R) PRO/1000 Network Connection e1000: eth0 NIC Link is Up 100 Mbps Full Duplex eth0: no IPv6 routers present which look good to me, but they were added by my manual modprobe command :( These are also the only reference to eth0. ------------------------------------------------------ BandiPat wrote:
There were problems with Mantel's 2.4.21-58, which is mostly corrected with the -59 build he presently has on his site. I still don't have 3D with the -59 build, but we have traced that down now as well and I am looking forward to the next one to get that back also. So far, the 2.4.21-59 build is working quite well.
Hmm, OK, a kernel that's less than a week old. I'm trying to build a system for a biologist to use reliably for their daily work, so you're making me nervous about stability. Anyway, I've installed the -59 kernel, but it seems to behave exactly like the -58 as far as I can tell in 5 minutes. I'd like to ask another question about this kernel. Once I get the network reliable, I'd like to set the BIOS to make the SATA drives visible in native mode. At the moment it's in legacy mode so I can't see the SATA drives, the PATA drive and the CD at the same time. At least the disks work reliably in this mode, and getting the network to boot is higher priority. But do you think native SATA will work? Thanks again, Dave
Dave Howorth wrote:
Go to /etc/modules.conf and check, if eth0 is assigned to e1000.
Andreas, many thanks for your continuing patience and help.
eth0 appears in two lines and one's a comment:
alias eth0 off
#alias eth0 nvnet
e1000 does not occur in the file. I don't know anything about kernel modules or this file, so after a quick look at the man page I did 'modprobe -c', expecting to see a line for e1000 (because I have now installed that module) but there was nothing, just the same line for eth0.
Please change the line: alias eth0 off to: alias eth0 e1000 Then reboot...
I'd guess that taking out the 'alias eth0 off' line might permit the module to load properly, but I'm nervous about making changes when (a) I don't understand how/why it got to be like that, and (b) I suspect there may be a SuSE-way (yast?) to make the change rather than just edit the file. I made the change but it didn't change the behaviour so I've put it back how it was
I don't know yast[2] very good, maybe there are ways, but i know none.
And maybe check your bootup "dmesg | less".
The only lines referring to the e1000 driver are at the end:
Intel(R) PRO/1000 Network Driver - version 5.2.13 Copyright (c) 1999-2003 Intel Corporation. PCI: Setting latency timer of device 02:01.0 to 64 eth0: Intel(R) PRO/1000 Network Connection e1000: eth0 NIC Link is Up 100 Mbps Full Duplex eth0: no IPv6 routers present
which look good to me, but they were added by my manual modprobe command :( These are also the only reference to eth0.
-- Andreas
On Wednesday 03 September 2003 11:46 am, Dave Howorth wrote:
Alfredo Yunes wrote:
I also have this integrated into the mobo (Albatron 865PE ProII) and the only way I was able to make it work was to upgrade to Mantel's 2.4.21 kernel.
Thanks for the link to Mantel - I'm now using his vmlinuz-2.4.21-58-smp. I've persuaded the kernel to boot (the default command-line options caused an error) but eth0 doesn't come up. There's a message:
Setting up network interfaces: eth0 failed
Is there a log or command to discover more detail of the problem?
Once it's booted I can start the network by hand (modprobe e1000; ifup eth0) so it seems likely to be a config error somewhere.
Is there a way to make it load automatically? Or what is the SuSE way to configure it manually (rc.local etc)?
Thanks, Dave ================
Dave, There were problems with Mantel's 2.4.21-58, which is mostly corrected with the -59 build he presently has on his site. I still don't have 3D with the -59 build, but we have traced that down now as well and I am looking forward to the next one to get that back also. So far, the 2.4.21-59 build is working quite well. Regards, Pat -- --- KMail v1.5.3-2 --- SuSE Linux Pro v8.2 --- Registered Linux User #225206 On any other day, that might seem strange...
Alfredo Yunes wrote:
Has anyone had any success getting this module working with any of the 8.2 kernels. My current mobo has this intergrated and I can't get it working. Any ideas?
You have tried such boot-options like "acpi=off" or "noapic". Look in Output of "dmesg". What says "lspci -v". -- Andreas
participants (6)
-
Alfredo Yunes -
Andreas Winkelmann -
BandiPat -
Dave Howorth -
Dylan -
Michael Galloway