I did change the mac address, as you can see in the screenshot linked
above, but it lead to the same outcome. Could you think of anything
else I should try? I could change the byte at fff4dfd9 to 80, but I'm
afraid it would lead to the same result. I can't think the network
adapter is defective because I can use it on other operating systems,
and when configured manually (prior to the installer's network
configuration) it works fine, if/when I let the installer deal with
this, even manually assigning an ip address, I do not have network
connectivity at all.
On Thu, Feb 22, 2018 at 1:02 AM, Frank Scheiner <frank.schei...@web.de> wrote:
> Hi Jerome,
> On 02/22/2018 01:23 AM, Jerome Ibanes wrote:
>> Could you try the following in obp:
>> cd /pci@1f,0/ebus@c/eeprom@1,0
>> fff4bfd0 30 dump
>> and tell me the numbers in fff4bfd8 and fff4bfd9, I would like to know
>> if it's 01 80 or 01 83
> That must be the "(real) machine type" (the second byte only, which is the
> first byte of a hostid). Without looking at it, I can say from my banner
> message that I have "(01) 80" currently in there, but I don't know the
> original value. I hadn't recorded that information before my NVRAM battery
> was depleted and I couldn't find a banner message from a Blade 100 online,
> so assumed "80" is correct.
>  on page 17 shows it to be "83" for a Blade 150 (which seems to be
> correct, see below). On the other hand  on page 67 shows it to be "61"
> for a Blade 100 - which must be plain wrong as  lists it as starting with
> "8". Maybe it was "80" for Blade 100s that use the 08:00:20 block and "83"
> for Blade 100s that use the 00:03:ba block, which would make "80" actually
> wrong for my machine and used MAC address block.
> But as my machine doesn't show any issues with IP address auto-configuration
> from the installer despite the assumed wrong "(real) machine type" in the
> hostid, it might be unrelated to your problem.