<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
Steve;<br>
I sent a reply to you personally although I wanted it to go to
the group.. I really dislike reflectors that pre-suppose that
answers should be private... but anyhow.....<br>
<br>
I had an additional though to that email...<br>
<br>
You may need to disable the onboard NIC temporarily in bios to get
through install, then re-enable it.. The chip for the onboard NIC is
still probably the issue ... make it invisible for now....If you
STILL have an issue at that point, it would seem that I would be
looking at a local cabling/switch/DHCP port issue... but that does
seem a lot less likely..<br>
<br>
I have used my USB-200M to do at least a dozen or 2 CentOS builds of
one form or another on my Atoms..<br>
<br>
Doug<br>
<br>
<br>
On 3/19/2011 8:05 AM, Steve Schulze wrote:
<blockquote cite="mid:4D849C0E.9040601@yellowthunder.org"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
Well, I'm still stuck.<br>
<br>
Got the Linksys USB-200M. Tried a fresh install of ACID.<br>
<br>
It almost looked like it was going to work. When the boot got to
starting interface for eth2, it pauses and says determining IP
information and cable unplugged?<br>
<br>
Well, tried a few different known good cables and no luck.<br>
<br>
Able to see the device in setup and configure for DHCP or Static
but still no luck.<br>
<br>
My first install for 27616 went off without a hitch on an IBM
NetVista 1.8gHz P4.<br>
<br>
<br>
Does anybody else have any other ideas?<br>
<br>
<br>
Thanks for all of your help.<br>
<br>
<pre class="moz-signature" cols="72">Steve Schulze - Radio Amateur, General Class - N9UDO
Administrator, Baraboo, Wisconsin D-Star System - WB9FDZ
Administrator, Baraboo, Wisconsin AllStar Link - 27616, 27727
Treasurer, Badgerland Amateur Television Society - KB9SFS
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://yellowthunder.org/dstar.html">http://yellowthunder.org/dstar.html</a>
</pre>
<br>
On 3/14/2011 10:00, Scott Weis wrote:
<blockquote cite="mid:091a01cbe258$8e2b6880$aa823980$@kb2ear.net"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas","serif";
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt;
font-family: "Calibri","sans-serif";
color: rgb(31, 73, 125);">I have used this adapter for
this sort of problem:
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.amazon.com/Cisco-Linksys-USB200M-EtherFast-Network-Adapter/dp/B000085ZKV/">http://www.amazon.com/Cisco-Linksys-USB200M-EtherFast-Network-Adapter/dp/B000085ZKV/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt;
font-family: "Calibri","sans-serif";
color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt;
font-family: "Calibri","sans-serif";
color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<div>
<div style="border-width: 1pt medium medium; border-style:
solid none none; border-color: rgb(181, 196, 223)
-moz-use-text-color -moz-use-text-color; padding: 3pt 0in
0in;">
<p class="MsoNormal"><b><span style="font-size: 10pt;
font-family:
"Tahoma","sans-serif"; color:
windowtext;">From:</span></b><span style="font-size:
10pt; font-family:
"Tahoma","sans-serif"; color:
windowtext;"> <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:app_rpt-users-bounces@ohnosec.org">app_rpt-users-bounces@ohnosec.org</a>
[<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="mailto:app_rpt-users-bounces@ohnosec.org">mailto:app_rpt-users-bounces@ohnosec.org</a>]
<b>On Behalf Of </b>Steve Schulze<br>
<b>Sent:</b> Monday, March 14, 2011 8:36 AM<br>
<b>To:</b> Chuck Henderson<br>
<b>Cc:</b> <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</a><br>
<b>Subject:</b> Re: [App_rpt-users] Network Driver<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks Chuck.<br>
<br>
It's strange that it can't even find the Ethernet
controller.<br>
<br>
When I do a 'setup' from the command prompt to look at the
network settings, it's not there. If I attach the TrendNet
Ethernet dongle and reboot and go back into setup, it sees
that one but not the built-in one. And for some strange
reason with DHCP or static IP the system will not continue
to load.<br>
<br>
I would assume (maybe a bad idea) that the ACID distro on
the site is the latest and hasn't been updated in a while?<br>
I downloaded it a few months ago when I was building 27616.
Maybe I need to d/l the latest version.<br>
<br>
Thanks for your help.<br>
<br>
<o:p></o:p></p>
<pre>Steve Schulze - Radio Amateur, General Class - N9UDO<o:p></o:p></pre>
<pre>Administrator, Baraboo, Wisconsin D-Star System - WB9FDZ<o:p></o:p></pre>
<pre>Administrator, Baraboo, Wisconsin AllStar Link - 27616, 27727<o:p></o:p></pre>
<pre>Treasurer, Badgerland Amateur Television Society - KB9SFS<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><a moz-do-not-send="true" href="http://yellowthunder.org/dstar.html">http://yellowthunder.org/dstar.html</a><o:p></o:p></pre>
<p class="MsoNormal"><br>
On 3/14/2011 00:01, Chuck Henderson wrote: <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom: 12pt;">I use the
D510MO board and it does have one PCI slot. It also
installs fine with the ACID.iso using DHCP. No Ethernet
issues with the built in Ethernet.<o:p></o:p></p>
<div>
<p class="MsoNormal">On Sun, Mar 13, 2011 at 8:00 PM, Steve
Schulze <<a moz-do-not-send="true"
href="mailto:n9udo@yellowthunder.org">n9udo@yellowthunder.org</a>>
wrote:<o:p></o:p></p>
<p class="MsoNormal">Thanks for all your help Doug however,
the Atom D510 MB does not have any PCI slots.<br>
<br>
Maybe I'll have to find a Linksys dongle. <o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom: 12pt;"><br>
<br>
<br>
<br>
Thanks!<br>
<br>
Steve Schulze - Radio Amateur, General Class - N9UDO<br>
Administrator, Baraboo, Wisconsin D-Star System - WB9FDZ<br>
Administrator, Baraboo, Wisconsin AllStar Link - 27616,
27727<br>
Treasurer, Badgerland Amateur Television Society -
KB9SFS<br>
<br>
<a moz-do-not-send="true"
href="http://yellowthunder.org/dstar.html"
target="_blank">http://yellowthunder.org/dstar.html</a><br>
<br>
<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">On 3/13/2011 18:03, Doug Bade
wrote:<o:p></o:p></p>
<p class="MsoNormal"> I can only speak from my
problems with some of my atom 230 330 D410 boards all
having similar issues as the NIC chip is newer than
CentOS can accurately identify. It sees it and uses
the wrong driver. It is an issue with other distro's I
have messed with too.<br>
<br>
The Linksys route has always fixed it up... You may
be able to temporarily plug a PCI NIC into the empty
slot ( I assume there is one as there is on most
Atoms) by removing the shield... Maybe better luck
that way...<br>
<br>
Doug<br>
KD8B<br>
<br>
On 3/13/2011 6:15 PM, Steve Schulze wrote:<o:p></o:p></p>
<p class="MsoNormal">Well.....That didn't work.<br>
<br>
Seems the Linksys device is discontinued at Staples.
Stopped by the local Rad-Shack and got a TrendNet
TU2-ET100.<br>
<br>
Tried a fresh install of Acid and same story.<br>
<br>
If I do the interactive startup and don't start
firstboot and local I can go in at the command prompt
and configure the adapter using setup, the system does
see it. If I do a DHCP or static IP address, I get the
same result.<br>
<br>
I have verified that the adapter works and my Ethernet
cable is good.<br>
<br>
I'm just stuck.<br>
<br>
<br>
Thanks!<br>
<br>
Steve Schulze - Radio Amateur, General Class - N9UDO<br>
Administrator, Baraboo, Wisconsin D-Star System -
WB9FDZ<br>
Administrator, Baraboo, Wisconsin AllStar Link -
27616, 27727<br>
Treasurer, Badgerland Amateur Television Society -
KB9SFS<br>
<br>
<a moz-do-not-send="true"
href="http://yellowthunder.org/dstar.html"
target="_blank">http://yellowthunder.org/dstar.html</a><br>
<br>
<br>
On 3/13/2011 13:47, Doug Bade wrote:<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal">Steve;<br>
I would suspect you need a lot of support files to do
the make that are not on the computer to compile it..<br>
<br>
The quickest fix I found for Atom boards that do not
have ethernet chips that are recognized by the CentOS
install is to buy a Linksys USB ethernet dongle from
your local staples, best buy or whatever and plug it
in. CentOS recognizes it and after you finish the
build, your on-board will also be recognized. You can
then remove the usb and configure the on-board as
needed.. It is a $30.00 fix but if you play in Linux,
it is not unusual the new motherboards have network
chipsets that will be supported but many times are not
in the installation CD's..<br>
<br>
Your alternate plan is install all the build resources
needed to be able to run make... but that will
probably require a working network connection to
download all that :-) You can bring them all in via
usb thumb drive or such.. but I think the usb network
device will get the job done most painlessly !! Albeit
at addition hardware cost.<br>
<br>
Doug<br>
KD8B<br>
<br>
<br>
<br>
<br>
On 3/13/2011 1:58 PM, Steve Schulze wrote:<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom: 12pt;">I'm
installing a new node (27727) onto a new PC. I thought
I would try a Shuttle XS35-704. Nice little machine
with the 1.66 Atom processor, 2GB ram and 320GB HDD.<br>
<br>
Using the ISO I used to build node 27616, I run the
setup on the new machine.<br>
<br>
When it got to the first reboot, it indicated that it
did not have internet connectivity and could not
continue.<br>
<br>
Used interactive startup and didn't load 'firstboot'
and 'local' so I could get a prompt. Logged in as root
and run setup to take a look at the network settings.
Low and behold the network card was not there.<br>
<br>
After many hours searching the internet for answers
for loading drivers from the command prompt, I was
able to find the driver for the built-in NIC. A JMC260
PCI Express Fast Ethernet Controller.<br>
<br>
Of course, I found many suggestions on how to load
this driver however, I'm not having any luck.<br>
<br>
I downloaded the driver JME-1.0.7.1.tbz2 and did the
following:<br>
<br>
# tar xjvf jme-1.0.7.1.tbz2 ;worked fine, no
problem.<br>
<br>
<br>
Changed to the directory where the decompression took
place and then<br>
<br>
# make install ;this is where it failed. I get the
following error:<br>
<br>
make: *** /lib2/modules/2.6.18-194.el5/build: No such
file or directory. Stop.<br>
make: *** [all] Error 2<br>
<br>
<br>
Would this be a result of not having a complete
install of the OS at this stage?<br>
<br>
<br>
Looking for some insight on how to install this
driver.<br>
<br>
<br>
BTW, prior to installing the Acid ISO, I had installed
the XIPPR ISO 'xosipt_20100518_1438.iso' and the
network card worked fine. I wanted to evaluate the
XIPPR before installing ACID.<br>
<br>
<br>
<br>
Thanks!<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom: 12pt;"><br>
_______________________________________________<br>
App_rpt-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:App_rpt-users@ohnosec.org"
target="_blank">App_rpt-users@ohnosec.org</a><br>
<a moz-do-not-send="true"
href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users"
target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>
<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom: 12pt;"><br>
<br>
<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom: 12pt;"><br>
<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal"><br>
_______________________________________________<br>
App_rpt-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:App_rpt-users@ohnosec.org"
target="_blank">App_rpt-users@ohnosec.org</a><br>
<a moz-do-not-send="true"
href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users"
target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<pre wrap=""><fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
App_rpt-users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a>
</pre>
</blockquote>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
App_rpt-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a>
<a class="moz-txt-link-freetext" href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a>
</pre>
</blockquote>
<br>
</body>
</html>