Bug 204404 - can not configure network card IP while Network installtion
Summary: can not configure network card IP while Network installtion
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 6
Hardware: powerpc
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Woodhouse
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-08-28 21:14 UTC by IBM Bug Proxy
Modified: 2008-08-02 23:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-01-08 00:17:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
IBM Linux Technology Center 26504 0 None None None Never

Description IBM Bug Proxy 2006-08-28 21:14:07 UTC
LTC Owner is: ameet.com
LTC Originator is: zhiwang.com


We install the Fefora 6 test 2 using NFS remote installtion, we can get the
machine booted with a tftp server, and coming to the text installtion interface,
after we select the language and then we select using NFS installtion mode, we
come to configure networks, then:

       1: if we select 
             [*] Use dynamic IP configuration (DHCP) 
             [*] Enable IPv4 support   
         
          the installtion program say :
             
              There was an error configuring   │
                      │ your network interface.    

       2. if we just select :
             
             [*] Enable IPv4 support   

          We can not make the configure of the network card right.

         It always say:

              There was an error configuring   │
                      │ your network interface.    
                

      So, we can not install Fefora 6 test 2 using NFS remote installtion.

thanks,

What happens when you do not select "Use dynamic IP configuration (DHCP)" and
"Enable IPv4 support?"   

just select "Use dynamic IP configuration (DHCP)" or "Enable IPv6 support" will
all error with:



                  ┌──┌──────┤ IPv4 Needed for NFS ├───────�?─�?
                  │  │                                    │ │
                  │ [│ NFS installation method requires   │ │
                  │ [│ IPv4 support.                      │ │
                  │ [│                                    │ │
                  │  │             ┌───────�?              │ │
                  │  │             │ Retry │              │ │
                  │  │             └───────┘              │ │
                  │  │                                    │ │
                  │  │                                    │ │
                  │  └────────────────────────────────────┘ │
                  └───                                      ┘

The ping test from SMS was successful:

10/100 Mbps Ethernet PCI Adapter II: U787B.001.DNW08D6-P1-C2-T1
Speed, Duplex:  auto,auto
Client IP Address: 9.3.xxx.xx
Server IP Address: 9.3.xxx.xx
Gateway IP Address: 9.3.xxx.xx
Subnet Mask IP Address: 255.255.255.0
Protocol: Standard
Spanning Tree Enabled: No
Connector Type:

Comment 1 David Lawrence 2006-09-05 15:21:01 UTC
Reassigning to correct owner, kernel-maint.

Comment 2 Jon Stanley 2007-12-31 02:22:46 UTC
Hello,

I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the Fedora kernel.

http://fedoraproject.org/wiki/KernelBugTriage

I am CC'ing myself to this bug, however this version of Fedora is no longer
maintained.

Please attempt to reproduce this bug with a current version of Fedora (presently
Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a
few days if there is no further information lodged.

Thanks for using Fedora!

Comment 3 Jon Stanley 2008-01-08 00:17:27 UTC
Closing per previous comment.  If you can provide the requested information,
please feel free to re-open this bug.

Comment 4 IBM Bug Proxy 2008-01-16 16:25:24 UTC
------- Comment From ameet.com 2008-01-16 11:22 EDT-------
Closing this Bugzilla as well.


Note You need to log in before you can comment on or make changes to this bug.