From: Philip P. <phi...@re...> - 2009-10-22 17:32:10
|
Also, when you get into the system, what do you have as eth0, etc? Anything? You should only get relocated to eth4 (etc) if eth0-eth3 are already taken. On 10/22/2009 10:44 AM, Lonnie Abelbeck wrote: > Ron, > > Before we get to the ethN issue, I assume you when from a 0.6 to a 0.7 > configuration. > > To Upgrade from AstLinux 0.6 to 0.7... > > Web Interface Method: > ============== > Install 0.7 build from SVN > > ... wait for reboot... > > Network tab -> Firewall sub-tab -> {Save Settings} > > Firewall sub-tab -> {Restart Firewall} > > ...displays the firewall supporting files need upgrading... > > Firewall sub-tab -> {Upgrade/Restart Firewall} |x| Confirm > --- > > Shell Method: > ========= > Install 0.7 build from SVN > > $ reboot > > ssh back to box... > > $ upgrade-arno-firewall upgrade > > $ vi /mnt/kd/rc.conf (hand edit Arno 0.8.x to 0.9.x format) > > $ gen-rc-conf > > $ arno-iptables-firewall restart > --- > > OK, with Arno upgraded, let's look at the interface ordering. New in > 0.7 is a file: > /etc/udev/rules.d/70-persistent-net.rules > > This file assigns the network interface names by MAC address, you may > edit this file if you wish. > > Ron, are you saying this file is assigning eth4-7 ? > > Try deleting this file and reboot and see if you get the expected > eth0-3 in the same auto-generated file. > > This should not be effected by runnix or NDEV. I am a little puzzled > by what you are seeing... > > Lonnie > > > > > On Oct 22, 2009, at 10:26 AM, Ron Byer -- Lists wrote: > > >> Greetings, >> >> I pulled a version of 0.7 (3370) recently, built it, and ran it on a >> net5501. >> >> My compliments to you fellows for how cleanly this came up. I expected >> some time spent sorting out issues, but I believe I have only one >> issue, >> which maybe you have seen. >> >> When I boot on 0.6, runnix comes up and assigns eth0-4, and then >> astlinux does the same. >> >> When I boot on 0.7, runnix comes up and assigns eth0-4, but then >> astlinux comes up and assigns eth4-7. This, of course annoys arno to >> no >> end. >> >> In reading throught the recent archives, I thought that commenting out >> NDEV=eth0 in the default.conf would address the issue, but it had >> little >> effect. >> >> Here are the relevant bits of the boot log: >> >> runnix >> via-rhine.c:v1.10-LK1.4.3 2007-03-06 Written by Donald Becker >> eth0: VIA Rhine III (Management Adapter) at 0xa0004000, >> 00:00:24:cb:d0:f8, IRQ . >> eth4: MII PHY found at address 1, status 0x786d advertising 05e1 >> Link 0021. >> eth0: VIA Rhine III (Management Adapter) at 0xa0004100, >> 00:00:24:cb:d0:f9, IRQ . >> eth6: MII PHY found at address 1, status 0x7849 advertising 05e1 >> Link 0000. >> eth0: VIA Rhine III (Management Adapter) at 0xa0004200, >> 00:00:24:cb:d0:fa, IRQ . >> eth5: MII PHY found at address 1, status 0x786d advertising 05e1 >> Link 45e1. >> eth0: VIA Rhine III (Management Adapter) at 0xa0004300, >> 00:00:24:cb:d0:fb, IRQ . >> eth7: MII PHY found at address 1, status 0x7849 advertising 05e1 >> Link 0000. >> geode-aes: GEODE AES engine enabled. >> AMD Geode RNG detected >> >> ....... >> >> astlinux >> via-rhine.c:v1.10-LK1.4.3 2007-03-06 Written by Donald Becker >> eth0: VIA Rhine III (Management Adapter) at 0xa0004000, >> 00:00:24:cb:d0:f8, IRQ . >> eth4: MII PHY found at address 1, status 0x786d advertising 05e1 >> Link 0021. >> eth0: VIA Rhine III (Management Adapter) at 0xa0004100, >> 00:00:24:cb:d0:f9, IRQ . >> eth6: MII PHY found at address 1, status 0x7849 advertising 05e1 >> Link 0000. >> eth0: VIA Rhine III (Management Adapter) at 0xa0004200, >> 00:00:24:cb:d0:fa, IRQ . >> eth5: MII PHY found at address 1, status 0x786d advertising 05e1 >> Link 45e1. >> eth0: VIA Rhine III (Management Adapter) at 0xa0004300, >> 00:00:24:cb:d0:fb, IRQ . >> eth7: MII PHY found at address 1, status 0x7849 advertising 05e1 >> Link 0000. >> geode-aes: GEODE AES engine enabled. >> AMD Geode RNG detected >> >> >> Thanks for whatever direction you can point me in. >> >> Regards, >> >> Ron >> > |