[App_rpt-users] Network Driver
Jon Rorke
jrorke at cogeco.ca
Mon Mar 14 13:11:59 UTC 2011
The Intel D510 MO I have has a Realtek ethernet chipset. The ACID distro
had no problem with that.
The Shuttle XS35-704 seems to have the same micro but has a different
ethernet chipset (JME) according to the spec sheet. Acid has no driver
for it and that is the problem.
On 3/14/2011 8:36 AM, Steve Schulze wrote:
> Thanks Chuck.
>
> It's strange that it can't even find the Ethernet controller.
>
> 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.
>
> 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?
> I downloaded it a few months ago when I was building 27616. Maybe I
> need to d/l the latest version.
>
> Thanks for your help.
> 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
>
> http://yellowthunder.org/dstar.html
>
> On 3/14/2011 00:01, Chuck Henderson wrote:
>> 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.
>>
>> On Sun, Mar 13, 2011 at 8:00 PM, Steve Schulze
>> <n9udo at yellowthunder.org <mailto:n9udo at yellowthunder.org>> wrote:
>>
>> Thanks for all your help Doug however, the Atom D510 MB does not
>> have any PCI slots.
>>
>> Maybe I'll have to find a Linksys dongle.
>>
>>
>>
>>
>> Thanks!
>>
>> 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
>>
>> http://yellowthunder.org/dstar.html
>>
>>
>> On 3/13/2011 18:03, Doug Bade wrote:
>>
>> 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.
>>
>> 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...
>>
>> Doug
>> KD8B
>>
>> On 3/13/2011 6:15 PM, Steve Schulze wrote:
>>
>> Well.....That didn't work.
>>
>> Seems the Linksys device is discontinued at Staples.
>> Stopped by the local Rad-Shack and got a TrendNet TU2-ET100.
>>
>> Tried a fresh install of Acid and same story.
>>
>> 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.
>>
>> I have verified that the adapter works and my Ethernet
>> cable is good.
>>
>> I'm just stuck.
>>
>>
>> Thanks!
>>
>> 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
>>
>> http://yellowthunder.org/dstar.html
>>
>>
>> On 3/13/2011 13:47, Doug Bade wrote:
>>
>> Steve;
>> I would suspect you need a lot of support files to do
>> the make that are not on the computer to compile it..
>>
>> 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..
>>
>> 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.
>>
>> Doug
>> KD8B
>>
>>
>>
>>
>> On 3/13/2011 1:58 PM, Steve Schulze wrote:
>>
>> 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.
>>
>> Using the ISO I used to build node 27616, I run
>> the setup on the new machine.
>>
>> When it got to the first reboot, it indicated
>> that it did not have internet connectivity and
>> could not continue.
>>
>> 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.
>>
>> 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.
>>
>> Of course, I found many suggestions on how to
>> load this driver however, I'm not having any luck.
>>
>> I downloaded the driver JME-1.0.7.1.tbz2 and did
>> the following:
>>
>> # tar xjvf jme-1.0.7.1.tbz2 ;worked fine, no
>> problem.
>>
>>
>> Changed to the directory where the decompression
>> took place and then
>>
>> # make install ;this is where it failed. I
>> get the following error:
>>
>> make: *** /lib2/modules/2.6.18-194.el5/build: No
>> such file or directory. Stop.
>> make: *** [all] Error 2
>>
>>
>> Would this be a result of not having a complete
>> install of the OS at this stage?
>>
>>
>> Looking for some insight on how to install this
>> driver.
>>
>>
>> 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.
>>
>>
>>
>> Thanks!
>>
>>
>> _______________________________________________
>> App_rpt-users mailing list
>> App_rpt-users at ohnosec.org
>> <mailto:App_rpt-users at ohnosec.org>
>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> App_rpt-users mailing list
>> App_rpt-users at ohnosec.org <mailto:App_rpt-users at ohnosec.org>
>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>>
>>
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20110314/aa4a125f/attachment.html>
More information about the App_rpt-users
mailing list