Will Woods wrote:
On Mon, 2012-06-25 at 21:42 -0500, David A. Marlin wrote:
Will Woods wrote:
... but mostly you'd want to
examine the various logs in /tmp. Probably you could boot with 'sshd'
and just scp them off the system.
Please see attached.
So:
[wwoods@samus ks-install-logs]$ grep 'to step' anaconda.log
05:10:39,705 INFO anaconda: dispatch: moving (1) to step sshd
05:10:39,745 INFO anaconda: dispatch: moving (1) to step kickstart
05:10:57,565 INFO anaconda: dispatch: moving (1) to step setuptime
01:10:58,005 INFO anaconda: dispatch: moving (1) to step
autopartitionexecute
01:10:58,482 INFO anaconda: dispatch: moving (1) to step storagedone
01:10:58,485 INFO anaconda: dispatch: moving (1) to step
enablefilesystems
01:11:20,176 INFO anaconda: dispatch: moving (1) to step reposetup
The last step it hit was 'reposetup' - my guess would be that anaconda
can't reach the repo (or thinks it's offline because of the NM problems
you mentioned).
I think you have it exactly right. It thinks it's offline because of
the NM problems, caused by the network driver.
You could try a VNC install to confirm?
I have manually booted the system to an F17 rootfs with the same kernel
and see the same issue with NetworkManager. The message in the kernel
log is:
<warn> /sys/devices/virtual/net/eth0: couldn't determine device
driver; ignoring...
which I believe is caused by the driver not providing a 'device' link in
/sys/devices/virtual/net/eth0.
Thanks again for your help,
d.marlin
========
-w
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
