For
some reason, this machine needs to be turned off for
at least a few minutes before I can re-use the
ethernet.
The ethernet card is a built-in e1000g.
This problem was solved (fingers crossed) after I disabled Wake On LAN and
Ethernet LAN Option ROM at the BIOS. I don't know which one
Oops, forgot to mention this. If you do not have a qualified domain name as
your hostname or as an alias (i.e., using the laptop hostname instead of the
qualified domain name such as laptop.com or laptop.net, etc.), Solaris will
complain about an unqualified unknown host. The easiest approach
Your hostname is literally set to 'unknown', and
your
system can't find
it in the DNS. You could/should set a proper
hostname and add that
entry to /etc/hosts and make sure files is in your
/etc/nsswitch.conf
cheers,
steve
The hostname ¨unknown¨ was set by Solaris.
Will the following entry be acceptable?
127.0.0.1 localhost laptop loghost
Yes (I am answering my own question), and it solved the ¨Could not look up
internet address for unknown¨ the Unresolved loghost problems.
This message posted from opensolaris.org
John Brewer writes:
Dhcp client did work on and off there were several code changes and putbacks,
it had worked with Time Warners Cable modem, and DSL modem in between these
versions of snv_b55 to snv_b61 and one of the 10u4 beta's with a few other
caviate's
Does the vender id and device id that
/usr/X11/bin/scancpi and prtconf -pv output show for
the e1000g show in your /etc/driver_aliases this is
managed by the add_drv command:
add_drv -i pcivendor-id,device-id e100g ( check the
man page for the syntax with single quotes around the
double
Does the vender id and device id that /usr/X11/bin/scancpi and prtconf -pv
output show for the e1000g show in your /etc/driver_aliases this is managed by
the add_drv command:
add_drv -i pcivendor-id,device-id e100g ( check the man page for the syntax
with single quotes around the double
W. Wayne Liauh writes:
However, as you and James discussed in a separate reply, the DHCP client
config needs to be better (an understatement) implemented ( _documented_) in
Solaris, especially now that almost everyone has a dumb DHCP server
(broadband router) at home. The situation becomes
After further investigations, I think the problem is definitely with the Lenovo
R61i notebook (I believe i refers to the Intel chipset). I am not going into
the details, but I have tried a couple of Linux distros, both experienced some
kind of problems. For some reason, this machine needs to
After further investigations, I think the problem is
definitely with the Lenovo R61i notebook (I believe
i refers to the Intel chipset). I am not going
into the details, but I have tried a couple of Linux
distros, both experienced some kind of problems. For
some reason, this machine needs
This has been a ongoing issue:
The dhcp client did work on and off there were several code changes and
putbacks, it had worked with Time Warners Cable modem, and DSL modem in between
these versions of snv_b55 to snv_b61 and one of the 10u4 beta's with a few
other caviate's
OS: S10u4 SXCE (inclusive of 78)
NIC: e1000g on Lenovo Thinkpad R61i
router/ISP: ClearWire modem
I was playing with my ethernet connection, which is connected to ClearWire thru
a WiMax modem. During a reboot, I received the following message after logging
into a GNOME session:
¨Could not
Your hostname is literally set to 'unknown', and your system can't find
it in the DNS. You could/should set a proper hostname and add that
entry to /etc/hosts and make sure files is in your /etc/nsswitch.conf
cheers,
steve
W. Wayne Liauh wrote:
OS: S10u4 SXCE (inclusive of 78)
NIC: e1000g
Your hostname is literally set to 'unknown', and your
system can't find
it in the DNS. You could/should set a proper
hostname and add that
entry to /etc/hosts and make sure files is in your
/etc/nsswitch.conf
cheers,
steve
W. Wayne Liauh wrote:
OS: S10u4 SXCE (inclusive of 78)
W. Wayne Liauh wrote:
Thanks for the quick reply Steve.
The hostname ¨unknown¨ was set by Solaris. It does sound silly, but I have
nothing to do with it. I have tried to set up a more proper hostname (e.g.,
creating a nodename.e1000g, etc.,) sometimes it worked, sometimes it didn´t.
You could put an alias for 'unknown' for 127.0.0.1 in
your /etc/hosts
then, that should fix things.
--
stephen lau | [EMAIL PROTECTED] |
www.whacked.net
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Nope.
16 matches
Mail list logo
