Help!!! I have tried everything I can find in How-to, Manuals, Yast etc. --- No Eth1 start-up.---- Lilo boot prompt, lilo: linux ether= 10,0x300,eth1 , doesn't work either rc.config looks OK. Can someone walk me though the basics...??? Jack -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
If you are using dhclient, don't. Get dhcpcd from rufus.w3.org and use that. Your lost cards will then re-appear. At least that worked for me. Jack Schneider wrote:
Help!!! I have tried everything I can find in How-to, Manuals, Yast etc. --- No Eth1 start-up.---- Lilo boot prompt, lilo: linux ether= 10,0x300,eth1 , doesn't work either rc.config looks OK.
Can someone walk me though the basics...???
Jack
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- Michael H. Collins http://www.linuxlink.com 512-442-3151 512-656-9508 The Ultimate WM http://www.xfce.org Do you want FUN with Linux? http://www.austinlug.org http://hebb.cis.uoguelph.ca/~dave/27320/new/unixphil.html -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Jack Schneider wrote:
Help!!! I have tried everything I can find in How-to, Manuals, Yast etc. --- No Eth1 start-up.---- Lilo boot prompt, lilo: linux ether= 10,0x300,eth1 , doesn't work either rc.config looks OK.
Can someone walk me though the basics...???
I just went through this too. It seemed that the SuSE people messed up again. I found the solution on their support web site (sort of...) In /etc/modules.conf there was a line with alias eth0 off that had to be changed to alias eth0 3c59x (for my 3Com card) I just guessed that for the second card I would need a similar line for eth1. It worked Damon Register -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
That is weird. I didn't have to do that. But mine was an upgrade. I also let yast set mine. nicFunn!! Damon Register wrote:
In /etc/modules.conf there was a line with alias eth0 off that had to be changed to alias eth0 3c59x (for my 3Com card) I just guessed that for the second card I would need a similar line for eth1. It worked
-- Michael H. Collins http://www.linuxlink.com 512-442-3151 512-656-9508 The Ultimate WM http://www.xfce.org Do you want FUN with Linux? http://www.austinlug.org http://hebb.cis.uoguelph.ca/~dave/27320/new/unixphil.html -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Damon Register writes -
I just went through this too. It seemed that the SuSE people messed up again. I found the solution on their support web site (sort of...) In /etc/modules.conf there was a line with alias eth0 off that had to be changed to alias eth0 3c59x (for my 3Com card) I just guessed that for the second card I would need a similar line for eth1. It worked
I had to do the same thing to /etc/modules.conf ... alias eth0 tulip alias eth1 tulip But, that didn't solve the problem. I had an interrupt conflict on my PCI bus! Both ethernet cards (Linksys) were trying to access IRQ 9. So, in my BIOS setup, I changed the interrupt for eth0's slot to IRQ 10 and all was well. Hope this helps, Buddy Coffey Advanced Electromagnetics -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
I didn't pay any attention to where the RPM put the executable. It did however put it in /sbin. I disabled dhclient in yast and put chcpcd in /etc/rc.d/boot.local. Like this. /sbin/dhcpcd echo "Starting dhcpcd" And it worked. Damon Register wrote:
Jack Schneider wrote:
Help!!! I have tried everything I can find in How-to, Manuals, Yast etc. --- No Eth1 start-up.---- Lilo boot prompt, lilo: linux ether= 10,0x300,eth1 , doesn't work either rc.config looks OK.
Can someone walk me though the basics...???
I just went through this too. It seemed that the SuSE people messed up again. I found the solution on their support web site (sort of...) In /etc/modules.conf there was a line with alias eth0 off that had to be changed to alias eth0 3c59x (for my 3Com card) I just guessed that for the second card I would need a similar line for eth1. It worked
Damon Register
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- Michael H. Collins http://www.linuxlink.com 512-442-3151 512-656-9508 The Ultimate WM http://www.xfce.org Do you want FUN with Linux? http://www.austinlug.org http://hebb.cis.uoguelph.ca/~dave/27320/new/unixphil.html -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (4)
-
bcoffey＠ni.net -
dregiste＠bellsouth.net -
mhtexcollins＠austin.rr.com -
puck1＠maine.rr.com