Hi all,
We have just got a new batch of blade servers in and are attempting to
pxeboot with the discovery image.
We are able to do the initial pxe request, and boot into the image.
However, once booted into the image, the network interface does not start,
nor show up in /proc/net/dev (only shows, lo and dummy0). Is there a
possible issue with the network drivers available in the discovery image
currently running against the new hardware?
Any help is appreciated.
Thanks!
Chuck
Quite likely, the TCL kernel is 3.0.x IIRC. Not sure there's much we can do
to the TCL image, however, we hope to have an RPM image ready soon, if
you're interesting in beta-testing it 
Greg
Hi all,
We have just got a new batch of blade servers in and are attempting to
pxeboot with the discovery image.We are able to do the initial pxe request, and boot into the image.
However, once booted into the image, the network interface does not start,
nor show up in /proc/net/dev (only shows, lo and dummy0). Is there a
possible issue with the network drivers available in the discovery image
currently running against the new hardware?Any help is appreciated.
Hi Greg,
I have been searching through the build iso script and working to move to
the 5.x latest for testing purposes. Anything I find, success wise that
is, I will make sure to post and send to you. Of course, I am always
interested in helping beta-testing!
Thanks!
Chuck
On 31 October 2013 20:24, gilbertc777@gmail.com wrote:
Hi all,
We have just got a new batch of blade servers in and are attempting to
pxeboot with the discovery image.We are able to do the initial pxe request, and boot into the image.
However, once booted into the image, the network interface does not start,
nor show up in /proc/net/dev (only shows, lo and dummy0). Is there a
possible issue with the network drivers available in the discovery image
currently running against the new hardware?Any help is appreciated.
Quite likely, the TCL kernel is 3.0.x IIRC. Not sure there’s much we can
do to the TCL image, however, we hope to have an RPM image ready soon, if
you’re interesting in beta-testing itGreg
–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/4tOzO9BvNKQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.
The other issue I forgot to mention is that I am not sure if the 3.x kernel
will support the network card, or require the broadcom drivers be built.
After looking at the latest release, the tiny core does not yet have
drivers for Broadcom BCM57810 specifically.
Hi Greg,
I have been searching through the build iso script and working to move to
the 5.x latest for testing purposes. Anything I find, success wise that
is, I will make sure to post and send to you. Of course, I am always
interested in helping beta-testing!Thanks!
Chuck
On Thu, Oct 31, 2013 at 10:13 PM, Greg Sutcliffe <greg.sutcliffe@gmail.com > > wrote:
On 31 October 2013 20:24, gilbertc777@gmail.com wrote:
Hi all,
We have just got a new batch of blade servers in and are attempting to
pxeboot with the discovery image.We are able to do the initial pxe request, and boot into the image.
However, once booted into the image, the network interface does not start,
nor show up in /proc/net/dev (only shows, lo and dummy0). Is there a
possible issue with the network drivers available in the discovery image
currently running against the new hardware?Any help is appreciated.
Quite likely, the TCL kernel is 3.0.x IIRC. Not sure there’s much we can
do to the TCL image, however, we hope to have an RPM image ready soon, if
you’re interesting in beta-testing itGreg
–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/4tOzO9BvNKQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.
I am currently working on work which Greg started, which is new
discovery image based on oVirt Node. It is slightly bigger, but on the
other hand it is based on Fedora 19 - with all the goodies included. I
mean – drivers 
We should have some alfa-stage images ready next week, I will announce
it on the list. Stay tuned.
LZ
–
Later,
Lukas “lzap” Zapletal
irc: lzap #theforeman