Hi Mike,
Not really information packed:
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu
8232 index 1
inet 127.0.0.1 netmask ff000000
# ifconfig bge0 plumb
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu
8232 index 1
inet 127.0.0.1 netmask ff000000
bge0: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 0.0.0.0 netmask 0
ether 0:11:25:47:2b:10
Prior to the plumb, the router's LEDs for the T43 cable have the LINK
LED flashing wildly (faster than usual during normal activity), the
DUPLEX LED is off, and the 100 LED is on. After the plumb, all 3 are
on. I can follow that w/inetmenu for bge0 and the network comes up.
If hostname.bge0 exists at boot, the network comes up normally, but
of course inetmenu complains.
No clue whether the bad actor is the NIC, Solaris, inetmenu, the router,
or _me_. Well, probably not inetmenu!
IMHO, it would be nice if I could leave hostname.bge0 in place to
stabilize the NIC, and have inetmenu tolerate that situation and
go from there.
I wrote a really crappy zenity script for Fedora Core Linux a while
back that scans for available NIC configurations and when one is
selected, figures out what is already "up" and "downs" it. It was
just a rookie's zenity exercise, but if I can do it, surely it can
be done for Solaris by those of you with acutal skills ;)
Thanks,
Bill
--------------------------------------------
William D Waddington
Bainbridge Island, WA, USA
william.waddington at beezmo.com
--------------------------------------------
"Even bugs...are unexpected signposts on
the long road of creativity..." - Ken Burtch
Mike Ramchand wrote:
> Hi William,
>
> You are probablt right, its not really an inetmenu issue, but becomes
> visible due to the delayed plumbing up of the bge0 interface.
>
> Looks like the bge0 card might be trying to negotiate the network speed
> or something and confusing the router.
>
> Can you do an ifconfig -a to show what is configured prior to running
> inetmenu?
>
> Can you manually do an ifconfig bge0 plumb to see if plumbing the
> interface solves the problem?
>
> Mike
>
> William D Waddington wrote:
>
>> This is probably not an inetmenu bug - directly - but is related to
>> its use.
>>
>> I have installed 1.7 on my ThinkPad T43 so I can switch between the
>> wired NIC and the Intel WiFi NIC. All of this stuff seems to work
>> OK. The problem is that when i boot to Solaris (SNV 28) and _before_
>> I select a NIC, the LEDs on my Linksys DSL router are all flashing
>> frantically, and my entire home LAN is locked up. Things stay this
>> way until I run inetmenu and select bge0.
>>
>> I have no idea if this is particular to the Broadcom NIC and/or bge
>> driver or if it is a general problem. Looks to me like there should
>> be some kind of default configuration of the wired NIC, even before
>> it is selected via inetmenu.
>>
>> Bill This message posted from opensolaris.org
>> _______________________________________________ laptop-discuss
>> mailing list laptop-discuss at opensolaris.org
>
>
>
>
