Similar troubles, here, but I have many more. In general, it seems running
Windoze and a reboot causes all changes to be lost, and boot errors on the
ethernet card.
I suspect I don't know where to make the changes properly to cause them to
work after a reboot. I was doing all sorts of commands by hand to try to
get things to run. I bet you did too. If I knew what the correct ones all
were, and their correct sequence, I still wouldn't know where to put them in
a startup type script, or what startup type script to put them in. Once
upon a time, I worked on an SCO Unix box that I had to modify an init.d file
in /etc if I recall correctly (was 10 yrs ago).
I also suspect that the ISP sees the machine differently even though the MAC
address is the same, and maybe doesn't like the change, thus causing the
"Failed" crap on boot. Maybe powering off the Cable Modem for a few minutes
before the reboot into Linux would help. I'm so discouraged at this point,
I haven't booted the Linux in a week, pondering what to try next.
FYI, don't bother trying a Broadband router (instead of a Linux router box)
if you plan to use IRC, as they don't provide Identd, so you can't get on
any servers. I guess I'll keep trying to get the Linux running. I'll be
damned if I'll go buy Wingate and suffer permanently in the land of MS. And
I pray I needn't install a Backoffice server to solve this, either. It
would be disheartening to have to do so.
good luck,
BobC
----- Original Message -----
From: "Roger Sherman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, November 17, 2000 11:26 PM
Subject: [newbie] This bites (further cable woes)
So, when I installed 7.2 a few days ago, I was thrilled to see it
configured my cable modem for me. Yesterday, I decided it was time to
install a firewall, which I attempted. It went poorly, so I decided to
put it on the shelf til I could talk to someone who knew a bit about
it. My roommate wanted to use the PC, and go into WIndows, which he
did. Later I booted back into Linux, and saw as it was initializing
everything, that eth0 failed to initialize. The reason given was
Initializing eth0 - Determining IP information via dhcpcd - failed
I figured it was because of my botched firewall attempt, so I
uninstalled it, and still nothing. So, since Id just installed
everything, and nothing was really tweaked to my liking, I just
reinstalled the whole thing. Problem solved, and I was back online.
Until I rebooted again - this time with no firewall to muck things up.
Same result though, same message.
Can anyone tell me how to get back online? I typed in ifconfig, and it
didnt tell me anything except that I was offline, I tried to
reconfigure my cable setup through DrakeConf - Network and Internet
Configuration; it told me it was starting eth0 again, then a minute
later it said it was already configured. In a terminal, as su, I typed
dhcpcd, but it didnt do anything. Thats it for me, Im a newbie, I have
no tricks up my sleeve.
So is it possible to dual boot and still be able to initialize eth0
upon booting? Id really hate to think I might have to reinstall Linux
a couple times a week if I want to be online, but at the same time, I
want nothing to do with Windows anymore, and am considering making
this PC strictly a Linux box. Problem being, if I get knocked offline
like that, then I have to reinstall Windows to get help.
Help!!!
peace,
Rog
http://www.slammingrooves.com
