| View previous topic :: View next topic |
| Author |
Message |
suicideducky
Apprentice
Joined: 29 Jan 2007
Posts: 208
|
 Posted: Sun Apr 29, 2007 6:59 am Post subject: (solved)few errors on startup after fresh install |
 |
|
ok well I just accidentally whiped my whole hdd..... don't ask 
so I was doing a fresh gentoo install.
and that worked out fine
after the install i rebooted and it came up with the dhcp client not installed but i fixed that by emerging baslayout (had a thread about this last install)
and now when it boots its comes up with the following error
| Code: | | network interface eth0 does not exist |
my /etc/conf.d/net:
| Code: | config_eth0=( "dhcp" )
dhcp_eth0="nodns nontp nonis" |
I also get the following error's:
| Code: | warning: the current /etc/modules.conf has not been automatically generated (this has a yellow star)
Use "update-modules force" to force (re)generation (this has a red star)
|
another error:
| Code: | one of the files in /etc/{conf.d,init.d} or /etc/rc.conf
has a modification time in the future! (yellow star) |
the error code avoce appears 9 or 10 times during startup 
Any help would be greatly apprechiated.
Thanks again, Ducky
Last edited by suicideducky on Sun Apr 29, 2007 8:31 am; edited 1 time in total |
|
| Back to top |
|
 |
didymos
Advocate
Joined: 10 Oct 2005
Posts: 4798
Location: California
|
| Posted: Sun Apr 29, 2007 7:06 am Post subject: Re: few errors on startup after fresh install |
|
|
| suicideducky wrote: | ok well I just accidentally whiped my whole hdd..... don't ask
so I was doing a fresh gentoo install.
and that worked out fine
after the install i rebooted and it came up with the dhcp client not installed but i fixed that by emerging baslayout (had a thread about this last install)
and now when it boots its comes up with the following error
| Code: | | network interface eth0 does not exist |
my /etc/conf.d/net:
| Code: | config_eth0=( "dhcp" )
dhcp_eth0="nodns nontp nonis" |
|
Can you get it working manually?
| Quote: |
I also get the following error's:
| Code: | warning: the current /etc/modules.conf has not been automatically generated (this has a yellow star)
Use "update-modules force" to force (re)generation (this has a red star)
|
|
Not a big deal, just run the command it suggests to get rid of that.
| Quote: |
another error:
| Code: | one of the files in /etc/{conf.d,init.d} or /etc/rc.conf
has a modification time in the future! (yellow star) |
the error code avoce appears 9 or 10 times during startup
|
Could be a filesystem error, or the system clock isn't properly set. Do any the files show up as "from the future"? If the clock is cool, try to re-emerge the packages that installed those scripts or just run touch on the offenders.
_________________
Thomas S. Howard |
|
| Back to top |
|
|
bunder
Bodhisattva
Joined: 10 Apr 2004
Posts: 5213
|
| Posted: Sun Apr 29, 2007 7:09 am Post subject: Re: few errors on startup after fresh install |
|
|
| suicideducky wrote: | ok well I just accidentally whiped my whole hdd..... don't ask
so I was doing a fresh gentoo install.
and that worked out fine
after the install i rebooted and it came up with the dhcp client not installed but i fixed that by emerging baslayout (had a thread about this last install)
and now when it boots its comes up with the following error
| Code: | | network interface eth0 does not exist |
my /etc/conf.d/net:
| Code: | config_eth0=( "dhcp" )
dhcp_eth0="nodns nontp nonis" |
I also get the following error's:
| Code: | warning: the current /etc/modules.conf has not been automatically generated (this has a yellow star)
Use "update-modules force" to force (re)generation (this has a red star)
|
another error:
| Code: | one of the files in /etc/{conf.d,init.d} or /etc/rc.conf
has a modification time in the future! (yellow star) |
the error code above appears 9 or 10 times during startup
Any help would be greatly apprechiated.
Thanks again, Ducky |
lets see if i can help you out.
1) missing eth0 - check your kernel config to see if you actually built the driver (in either builtin or modular form)
2) conf.net - looks fine to me.
3) modules.conf - run "modules-update force" if this appears again after fixing eth0
4) mod times in the future - check /etc/conf.d/clock and make sure that the correct timezone and systohc are set. then try rebooting and see if that clears.
hope this helps. 
_________________
goodbye fgo. it was nice knowing you. |
|
| Back to top |
|
|
suicideducky
Apprentice
Joined: 29 Jan 2007
Posts: 208
|
| Posted: Sun Apr 29, 2007 7:32 am Post subject: Update |
|
|
ok well I can gurantee the driver for my eth0 card is compiled as a module in the kernel.
this is not my 1st install, and everytime it hast 'just worked' from the genkernel config (excluding the no dhcpcd client install which i fixed already) but i manually went through, found my driver and made sure it was compiled in the kernel.
/etc/conf.d/clock seems to have the correct timezone set (NZ)
and with
| Quote: | modules.conf - run "modules-update force" if this appears again after fixing eth0
|
should it only be ran AFTER I have fixed eth0?
ok well as far as I can see the main problem is getting eth0 up and running. It works from the livecd so I can chroot in and still use the system, just not exactly what i would call fully functional.
| Code: |
Could be a filesystem error, or the system clock isn't properly set. Do any the files show up as "from the future"? If the clock is cool, try to re-emerge the packages that installed those scripts or just run touch on the offenders.
|
this may sound like a stupid question, but how do I find out if they appear "from the future"
and how exactly do I know which files are the offenders?
I have no graphical enviorment as of yet (just incase that made it somehow different, which i doubt)
Thanks again, Ducky |
|
| Back to top |
|
|
bunder
Bodhisattva
Joined: 10 Apr 2004
Posts: 5213
|
| Posted: Sun Apr 29, 2007 7:47 am Post subject: Re: Update |
|
|
| suicideducky wrote: | ok well I can gurantee the driver for my eth0 card is compiled as a module in the kernel.
this is not my 1st install, and everytime it hast 'just worked' from the genkernel config (excluding the no dhcpcd client install which i fixed already) but i manually went through, found my driver and made sure it was compiled in the kernel.
/etc/conf.d/clock seems to have the correct timezone set (NZ)
and with
| Quote: | modules.conf - run "modules-update force" if this appears again after fixing eth0
|
should it only be ran AFTER I have fixed eth0?
ok well as far as I can see the main problem is getting eth0 up and running. It works from the livecd so I can chroot in and still use the system, just not exactly what i would call fully functional.
| Code: |
Could be a filesystem error, or the system clock isn't properly set. Do any the files show up as "from the future"? If the clock is cool, try to re-emerge the packages that installed those scripts or just run touch on the offenders.
|
this may sound like a stupid question, but how do I find out if they appear "from the future"
and how exactly do I know which files are the offenders?
I have no graphical enviorment as of yet (just incase that made it somehow different, which i doubt)
Thanks again, Ducky |
the reason i said to do it after fixing eth0 was that if you had to do any kernel work, modules-update should be run after that.
as for the file names in the future, i think fsck can fix that. you can force a fsck on reboot by using "shutdown -rF now"
to find which ones are bad, do a few "ls -l"'s and "touch" any bad files. check your clock by using "date" of course.
cheers
_________________
goodbye fgo. it was nice knowing you. |
|
| Back to top |
|
|
suicideducky
Apprentice
Joined: 29 Jan 2007
Posts: 208
|
| Posted: Sun Apr 29, 2007 8:04 am Post subject: |
|
|
ok ive ran the following
| Code: |
update-modules force |
and there where a few files in init.d and conf.d that were touched in the future (i think i tried setting the clock assuming it wsa 24 hour time before so thats probably human error) so i ran
| Code: | touch /etc/cond.d/*
touch /etc/init.d/*
touch etc/rc.conf |
and then
so everything is fixed MINUS the eth0 problem.
still appearing.
and twice, it gets call in boot as net.etho and then again in default as netmount.
any suggestions?
I'm thinking of using the minimal cd, chrooting into my gentoo, and then running
would this fix anything?
thanks again, Ducky. |
|
| Back to top |
|
|
bunder
Bodhisattva
Joined: 10 Apr 2004
Posts: 5213
|
| Posted: Sun Apr 29, 2007 8:06 am Post subject: |
|
|
do you see anything if you run "ifconfig eth0", or do you see a no such device error?
_________________
goodbye fgo. it was nice knowing you. |
|
| Back to top |
|
|
suicideducky
Apprentice
Joined: 29 Jan 2007
Posts: 208
|
| Posted: Sun Apr 29, 2007 8:19 am Post subject: |
|
|
| bunder wrote: | | do you see anything if you run "ifconfig eth0", or do you see a no such device error? |
I checked this before and forgot to post it, sorry 
ok with dhcpcd eth0 (to try to manualy start my connection) and it comes up with
| Code: | | Error, eth0: ioctl SIOCGIFHWADDR: No such device |
and with ifconfig eth0
| Code: | | eth0: error fetchng interface information: Device not found |
thanks again, Ducky |
|
| Back to top |
|
|
bunder
Bodhisattva
Joined: 10 Apr 2004
Posts: 5213
|
| Posted: Sun Apr 29, 2007 8:27 am Post subject: |
|
|
ok, so far it doesn't look like its loading eth0. try adding the module name to /etc/modules.autoload.d/kernel-2.6 and restarting. if that doesn't work, post a full dmesg after booting.
_________________
goodbye fgo. it was nice knowing you. |
|
| Back to top |
|
|
suicideducky
Apprentice
Joined: 29 Jan 2007
Posts: 208
|
| Posted: Sun Apr 29, 2007 8:31 am Post subject: |
|
|
| bunder wrote: | | ok, so far it doesn't look like its loading eth0. try adding the module name to /etc/modules.autoload.d/kernel-2.6 and restarting. if that doesn't work, post a full dmesg after booting. |
solved. thanks again bunder
added "e100" (my driver) to /etc/modules.autoload.d/kernel-2.6 and rebooted.
thanks very much
Ducky |
|
| Back to top |
|
|
|
Installing Gentoo
