Setting kernel options at compile time.
I'm trying to get a 2.2.19 kernel loaded on an i810 system using RPLD on a diskless system. I can get the kernel loaded and running. The problem is the i810 needs the kernel parameter "mem=xxxM" set to tell the kernel how much memory the system has since the on the i810 the kernel doesn't know how much was taken for video. The catch I'm running into is RPLD cannot pass parameters to the kernel and without this setting the system has video problem, most likely from the memory sharing issues. When the mem parameter is set when using a disk it doesn't demonstrate any problems. What I'm trying to figure out is how to compile in this setting. Thanks, Chip Schweiss - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Setting kernel options at compile time.
I'm trying to get a 2.2.19 kernel loaded on an i810 system using RPLD on a diskless system. I can get the kernel loaded and running. The problem is the i810 needs the kernel parameter mem=xxxM set to tell the kernel how much memory the system has since the on the i810 the kernel doesn't know how much was taken for video. The catch I'm running into is RPLD cannot pass parameters to the kernel and without this setting the system has video problem, most likely from the memory sharing issues. When the mem parameter is set when using a disk it doesn't demonstrate any problems. What I'm trying to figure out is how to compile in this setting. Thanks, Chip Schweiss - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: Re: 2.2.18pre21 - IP kernel level autoconfiguration
The problem seems to be deeper than that. I first encountered the problem with only bootp compiled in. In my configuration I am not able to supply kernel parameters on the client which may be why you were able to get bootp to execute. Chip > It seem somewhere between 2.2.17 and the current 2.2.18 kernel, IP > kernel level autoconfiguration has been broken. Upon kernel loading > the Ethernet card is detected and loaded properly, but the bootp code > never seems to be executed and mounting the root partion via NFS then > fails from lack of IP configuration. > I haven't had any luck tracing down the root of this problem. > Anyone else experience this problem or have a patch to fix it? Hi! I've the same behavior here: server kernel : 2.2.17 dhcpd : 2.0b1pl29 client kernel : 2.2.18-21 client cmdline: root=/dev/nfs nfsroot=/foo/bar ip=bootp After some quick tests seem that if you want bootp you _need_ to compile the client's kernel with _only_ bootp, if you have also dhcp, it doesn't work :( Dhcp into kernel is COOL and I hope that someone is porting on 2.4 ;), doesn't seem that hard hope this help, luca - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RE: Re: 2.2.18pre21 - IP kernel level autoconfiguration
The problem seems to be deeper than that. I first encountered the problem with only bootp compiled in. In my configuration I am not able to supply kernel parameters on the client which may be why you were able to get bootp to execute. Chip It seem somewhere between 2.2.17 and the current 2.2.18 kernel, IP kernel level autoconfiguration has been broken. Upon kernel loading the Ethernet card is detected and loaded properly, but the bootp code never seems to be executed and mounting the root partion via NFS then fails from lack of IP configuration. I haven't had any luck tracing down the root of this problem. Anyone else experience this problem or have a patch to fix it? Hi! I've the same behavior here: server kernel : 2.2.17 dhcpd : 2.0b1pl29 client kernel : 2.2.18-21 client cmdline: root=/dev/nfs nfsroot=/foo/bar ip=bootp After some quick tests seem that if you want bootp you _need_ to compile the client's kernel with _only_ bootp, if you have also dhcp, it doesn't work :( Dhcp into kernel is COOL and I hope that someone is porting on 2.4 ;), doesn't seem that hard hope this help, luca - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
2.2.18pre21 - IP kernel level autoconfiguration
It seem somewhere between 2.2.17 and the current 2.2.18 kernel, IP kernel level autoconfiguration has been broken. Upon kernel loading the Ethernet card is detected and loaded properly, but the bootp code never seems to be executed and mounting the root partion via NFS then fails from lack of IP configuration. I haven't had any luck tracing down the root of this problem. Anyone else experience this problem or have a patch to fix it? Chip Schweiss - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
2.2.18pre21 - IP kernel level autoconfiguration
It seem somewhere between 2.2.17 and the current 2.2.18 kernel, IP kernel level autoconfiguration has been broken. Upon kernel loading the Ethernet card is detected and loaded properly, but the bootp code never seems to be executed and mounting the root partion via NFS then fails from lack of IP configuration. I haven't had any luck tracing down the root of this problem. Anyone else experience this problem or have a patch to fix it? Chip Schweiss - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
