From: Jim Fitzmaurice (jpfitz@fnal.gov)
Date: Wed Nov 06 2002 - 15:49:10 EST
I was finally able to reboot my system, and the solution provided by Phillip
Brown, (included below) worked. I now have alt0 and alt1 on my system and
they are as they should be.
----- Original Message -----
From: Jim Fitzmaurice <jpfitz@fnal.gov>
To: Tru64 -unix -managers <Tru64-unix-managers@ornl.gov>
Sent: Wednesday, October 30, 2002 3:03 PM
Subject: SUMMARY: My alt0 is now alt2.
> I guess this is actually only a partial summary as I haven't rebooted
> yet, but one will be required.
>
> After my original question several people referred to the System Admin
> Guide Chapter 5, which I'd already referred to and couldn't find a clear
> answer in reference to PCI devices. Plenty of info on SCSI however. Some
> people actually sent the "hwmgr" commands that they'd used to move scsi
> devices. And one reference to a dsfmgr command that I mentioned in my
> update.
>
> One person, Tim Brown actually gave me an answer that might work,
> removing alt0, and alt2 then rebooting. To add some credibility to this
> answer, after I sent the update indicating I was working with a PCI
device,
> I got the same answer from Dr. Blinn and Jan Mark Holzer. However, I
didn't
> think this would work in my case, because I have an alt1, that I want to
> keep. And I'm not sure how the name algorithm works, so I was afraid
> deleting alt0 and alt2 then rebooting, would still bring up the device as
> alt2. I did not want to attempt deleting alt0, alt1, and alt2, then
> rebooting. I was afraid the two cards might come back reversed.
>
> The most complete answer and the one I used came from Phillip Brown
who
> gave me two options. The first was a repeat of the option outlined above.
> The second option involved "telling" the name sub-system which name to
use.
> I had more confidence in that method so, after asking for a little
> clarification on pci bus specification, I set it up. Now, I just have to
> wait for a studies period so I can reboot and see if it works. Mr. Brown
> also added a short explanation of why dsfmgr doesn't work in this case. I
> included his answer in it entirety, although I believe, in the last line,
he
> meant "effective" not "affective". Unless he's really passionate about his
> devices. ;-)
>
> From: Brown, Phillip <Phillip.Brown@hp.com>
> Sent: Tuesday, October 29, 2002 2:45 PM
> Subject: RE: UPDATE: My alt0 is now alt2.
>
>
> Hi, Jim:
>
> Your goal, to fix your naming problem, is resolved by removing your alt
> devices from the name sub-system and then rebooting.
>
> To remove the entries from the name sub-system, use the following
commands:
>
> # hwmgr -remove name -entry alt2 <- and any others
>
> Then reboot your system and that device should become alt0.
>
> Or:
>
> Instead of relying on the name sub-system to assign the name during boot
> using its algorithm, you will "tell" the name sub-system what to use. You
> will need to look at the entries for the alt devices using this command:
>
> # hwmgr -show name
>
> You will notice the slot assigned to alt2. This is where the device is
> located. You'll use this slot number later.
>
> Remove the alt2 entry from the name sub-system using this command:
>
> # hwmgr -remove name -entry alt2
>
> Now edit the alt0 entry to use the slot where the network device is now
> located. Do this using this command:
>
> # hwmgr -edit name -entry alt0 -slot xxx
> (where xxx is the slot where the device is currently located)
>
> Now reboot your system.
>
>
> As you may notice, this is a dynamic modification of the name sub-system's
> data - the names of the "hardware component", not the names of the "device
> special files". So, dsfmgr doesn't work in cases like these.
>
> Also, it requires a reboot (at this time) for the names to become
affective
> whichever option you use.
>
> Regards,
>
> Phillip S. Brown
> HP Mission Critical
> UNIX Support Solutions
> Phone: 719.592.4809
> Page: 1.800.759.8888 #1249433
>
>
>
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:58 EDT