Lonnie and AstLinux Group,
I'm delighted to report a successful and flawless upgrade from 0.7.10 => 1.0.1.
Other than the required upgrade to RUNNIX and changes to
70-persistent-net.rules (required to recognize the new NIC as eth0), the
upgrade was uneventful.
It's amazing what a difference was made after replacing the Intel Pro100
(eePRO100) with an Intel Pro1000 (e1000) NIC card. Now all I need to do is
upgrade my ISP to support the Gigabit speeds this new WAN gateway supports!
Thanks again for all the advice and remote diagnostics.
Dan
-----Original Message-----
From: "Lonnie Abelbeck" <li...@lonnie.abelbeck.com>
Sent: Monday, January 16, 2012 4:33pm
To: "AstLinux Users Mailing List" <astlinux-users@lists.sourceforge.net>
Subject: Re: [Astlinux-users] AstLinux 1.01 Released
Dan, (update)
> There's really nothing special about this NIC card. It's a garden variety,
> low-profile PCI card that can easily be replaced - at far less cost than the
> value of AstLinux developers' time. Ironically, the reason I bought it in
> the first place is because the chipset (at one time) was quite widely
> supported.
Ahhh, updating to a "e1000" card would be a good idea, an Intel PCI PRO/1000
would be good. Note you would have to edit your
"/etc/udev/rules.d/70-persistent-net.rules" file to make the new card eth0, it
will appear as eth2, remove the old eth0 and rename eth2 to eth0 in the
"/etc/udev/rules.d/70-persistent-net.rules" file.
But...
It appears the "e100" kernel driver *might* work for you in the newer kernel.
If you choose to accept this mission...
Given you are now back at 0.7.10, Follow the "Upgrade from 0.7.x to 1.0.x" as
before:
http://doc.astlinux.org/userdoc:upgrade-0.7
When in AstLinux 1.0.1 we know it still won't recognize your old NIC for eth0,
but you can SSH in from a LAN computer using eth1. Then type:
modprobe e100
and see if you old NIC comes to life, looking at /var/log/messages or dmesg .
If so, edit "/etc/rc.modules" and change the "eepro100" line to "e100", save
and reboot. You should be good to go.
If the modprobe did nothing, you need a new NIC, but to get back to 0.7.10,
simply do a "Revert to Previous" for *both* the Firmware and RUNNIX, then
reboot, you are back at 0.7.10.
Lonnie
On Jan 16, 2012, at 2:53 PM, Lonnie Abelbeck wrote:
> Hi Dan,
>
> Thanks to your logs I see your problem.
>
> Your box has two NIC's one is a:
>
> eepro100 0000:07:04.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
> eth0: 0000:07:04.0, 00:d0:b7:xx:xx:xx, IRQ 20.
>
> and the other...
>
> e1000e 0000:00:19.0: PCI INT B -> GSI 19 (level, low) -> IRQ 19
> 0000:00:19.0: eth1: (PCI Express:2.5GB/s:Width x1) 00:21:5a:xx:xx:xx
> 0000:00:19.0: eth1: Intel(R) PRO/1000 Network Connection
>
> The problem is with your first NIC, eepro100, is not longer support in
> AstLinux 1.0.x kernel 2.6.35. It appears to be last available in Linux
> Kernel 2.6.28.
>
> http://cateee.net/lkddb/web-lkddb/EEPRO100.html
>
> http://lwn.net/Articles/216082/
>
> So question to Darrick, and others, is support for this "eepro100" NIC
> included in another driver, or is "eepro100" NIC hardware SOL?
>
> Dan, what kind of a box is this, can the eepro100 NIC be upgraded or is on
> the motherboard. ie, more info on your hardware.
>
> Lonnie
>
>
> On Jan 16, 2012, at 9:20 AM, d...@ryson.org wrote:
>
>> AstLinux Team,
>>
>> Thank your for your tireless efforts. I know it's often said, but it truly
>> bears repeating.
>>
>> I also appreciate the clear, unambiguous upgrade instructions, which I
>> followed explicitly when making the effort to upgrade from 0.7.10 to 1.0.1.
>> Everything was going according to the instructions until I rebooted. My
>> first indication that things hadn't gone well came from the Web Interface,
>> which revealed a number of failed registrations. ("Registration Sent" was
>> shown for all providers under SIP Trunk Registrations.)
>>
>> Further investigation revealed many pages of Notices, Warnings, and Errors
>> in the log. There are too many to list here, but I saved the file and would
>> gladly forward it to one or more developers by private e-mail. Although I
>> was able to access the machine by SSH and HTTPS, it was apparent that much
>> of the trouble impacted network functionality. Even a PING to one of our
>> providers didn't work. No IP address was revealed, suggesting we were
>> having trouble with DNS resolution. I regret that I wasn't able to do more
>> troubleshooting; I was anxious to get the unit back in service.
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Astlinux-users mailing list
> Astlinux-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> pay...@krisk.org.
>
>
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
pay...@krisk.org.
