Description of problem: After taking the nightly boot.iso and booting from USB I am only presented with local storage to select installation media from and I am unable to install via a network connection. Version-Release number of selected component (if applicable): Rawhide 8/24 build How reproducible: 100% Steps to Reproduce: 1. dd boot.iso to usb 2. boot to usb 3. unable to install via network Actual results: Unable to install via network Expected results: Ability to do network installation. Additional info: NetworkManager: <info> starting... NetworkManager: <info> Trying to start the modem-manager NetworkManager: ifcfg-rh: Could not get hostname: failed to read /etc/sysconfig/network NetworkManager: Loaded plugin ifcfg-rh: (c) 2007 - 2008 Red hat, Inc. <--snip--> NetworkManager: <info> Wireless now enabled by radio killswitch NetworkManager: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth0 ... NetworkManager: ifcfg-rh: read connection 'System eth0' NetworkManager: ifcfg-rh: Ignoring connection 'System eth0' and its device because NM_CONTROLLED was false. NetworkManager: <info> (eth0): new Ethernet device (driver: 'r8169') NetworkManager: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0 NetworkManager: <WARN> defualt_adapter_cb(): bluez error getting default adapter: The name org.bluez was not provided by any .service files NetworkManager: <info> Trying to start the supplicant
Created attachment 358596 [details] sosreport I am attaching an sosreport from LiveCD install of F11 updated to rawhide.
(In reply to comment #1) > Created an attachment (id=358596) [details] > sosreport > > I am attaching an sosreport from LiveCD install of F11 updated to rawhide. I lied this is just from a fully update F11 install not updated to rawhide.
After updating NetworkManager to what is in rawhide I get the following in messages Aug 25 13:08:55 dhcp242-41 NetworkManager: <info> starting... Aug 25 13:08:55 dhcp242-41 NetworkManager: <info> Trying to start the modem-manager... Aug 25 13:08:55 dhcp242-41 NetworkManager: Loaded plugin ifcfg-rh: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Aug 25 13:08:55 dhcp242-41 NetworkManager: <WARN> nm_signal_handler(): Caught signal 11. Generating backtrace... Aug 25 13:08:55 dhcp242-41 NetworkManager: ******************* START ********************************** Aug 25 13:08:55 dhcp242-41 modem-manager: Loaded plugin ZTE Aug 25 13:08:55 dhcp242-41 modem-manager: Loaded plugin Novatel Aug 25 13:08:55 dhcp242-41 modem-manager: Loaded plugin Option High-Speed Aug 25 13:08:55 dhcp242-41 rpc.statd[882]: Version 1.2.0 Starting Aug 25 13:08:55 dhcp242-41 modem-manager: Loaded plugin Huawei Aug 25 13:08:55 dhcp242-41 modem-manager: Loaded plugin Option Aug 25 13:08:55 dhcp242-41 modem-manager: Loaded plugin Nokia Aug 25 13:08:55 dhcp242-41 modem-manager: Loaded plugin Ericsson MBM Aug 25 13:08:55 dhcp242-41 modem-manager: Loaded plugin Gobi Aug 25 13:08:55 dhcp242-41 modem-manager: Loaded plugin Sierra Aug 25 13:08:55 dhcp242-41 modem-manager: Loaded plugin MotoC Aug 25 13:08:55 dhcp242-41 modem-manager: Loaded plugin Generic Aug 25 13:08:56 dhcp242-41 NetworkManager: ******************* END ********************************** running service network restart and dhclient brings up the interface and successfully grabs an IP.
So based on the bits in comment #1: NetworkManager: ifcfg-rh: Ignoring connection 'System eth0' and its device because NM_CONTROLLED was false. something is telling NM to ignore eth0. That's normal behavior during isntall until you tell anaconda that you'd like to use the network to install, at which point anaconda will flip NM_CONTROLLED to true and the network will come up. What you're saying is that the anaconda never asked whether you wanted a network install or not, right?
Alright, I managed to figure out to press F2 and then back to get a prompt asking to install to an URL (I swear this wasn't working before...). Anyway, when NetworkManager is trying to get an IP it segfaults killing the installation with; loader received SIGSEGV! Backtrace: /sbin/loader[0x40776e] /lib64/libc.so.6[0x7fff118a86f0] /lib64/libc.so.6(strrchr+0x1a)[0x7fff118ef37a] /sbin/loader[0x417efa] /sbin/loader[0x408dc9] /lib64/libc.so.6(__libc_start_main+0xfd)[0x7fff1188bb8d] /sbin/loader[0x4058f9] install exited abnormally [1/1] you may safely reboot your system
Created attachment 358743 [details] VT4 page1
Created attachment 358744 [details] VT4 page2 Don't mind the usb bit I believe the last relevant bit is nm-dispathcer.action: nm_dispatcher_action: Invalid connection: '(null)' / 'connection setting not found' invalid:1
*** This bug has been marked as a duplicate of bug 519288 ***
re-opening as this issue still persists even though 519288 has been resolved. Radek, I am having the same issue this still simply does not work maneuvering as described below. AFAICT I should be using version 12.24-1 of anaconda. **It should be noted that escaping out of the Install/upgrade screen and specifying 'linux askmethod' at boot: does work and there is not backtrace.** How to reproduce; http://mirror.uoregon.edu/fedora/linux/development/x86_64/os/images/ boot.iso 15-Sep-2009 05:36 167M After booting from the boot.iso on a usb key and selecting Install/Upgrade, then selecting the language and keyboard, I am presented with the "Select Partition" screen that asks for the "Directory holdings image:" and lists the local sd* devices and prompting to "press F2 to configure additional devices". After pressing F2 I am presented with the "Driver Disk Source" screen at which point I press Back to finally get to the "Installation Method" screen where I can select URL to install from. After selecting URL it takes you to the "Configure TCP/IP" screen which asks about static or dhcp (either of which produce the same backtrace). At this point while configuring NM we receive the following backtrace; loader recieved SIGSEGV! Backtrace: /sbin/loader[0x40782e] /lib/libc.so.6(+0x335f0)[0x7fbd098ee5f0] /lib/libc.so.6(strrchr+0x1a)[0x7fbd0993dc8a] /sbin/loader[0x418098] /sbin/loader[0x408e11] /lib/libc.so.6(__libc_start_main+0xfd)[0x7fbd098d9b4d] /sbin/loader[0x4058f9] install exited abnormally [1/1] you may safely reboot your system As an aside, maybe replacing "you may safely reboot your system" with "Hey, we've had a fatal error here please report to bugzilla.redhat.com" might be more appropriate. It appears as if everything works in vty4 and we get an ip get a hostname, but directly after this we see nm-dispathcer.action: nm_dispatcher_action: Invalid connection: '(null)' / 'connection setting not found' invalid:1 NetworkManager: ifcfg-rh: updating /etc/sysconfig/network-scripts/ifcfg-eth0 Again, This boot.iso does work when escaping out of the Install/Update splash screen where you are presented with the 'boot:' prompt and you initiate installation using 'linux askmethod'
(In reply to comment #9) > loader recieved SIGSEGV! Backtrace: > /sbin/loader[0x40782e] /usr/src/debug/anaconda-12.24/loader/loader.c:1725 > /lib/libc.so.6(+0x335f0)[0x7fbd098ee5f0] > /lib/libc.so.6(strrchr+0x1a)[0x7fbd0993dc8a] > /sbin/loader[0x418098] /usr/src/debug/anaconda-12.24/loader/urlinstall.c:118 > /sbin/loader[0x408e11] /usr/src/debug/anaconda-12.24/loader/loader.c:1578 > /lib/libc.so.6(__libc_start_main+0xfd)[0x7fbd098d9b4d] > /sbin/loader[0x4058f9] > install exited abnormally [1/1] > you may safely reboot your system This is caused by hd install UI not reinitializing loaderData->stage2Data when going back to Install Method screen (has been fixed for nfs install already) and regards specifically installs with stage2= provided as boot parameter. I am going to send a patch for review.
This bug should be fixed in version 12.26 of anaconda.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping