public inbox for discuss@lists.illumos.org (since 2011-08)
 help / color / mirror / Atom feed
From: Peter Tribble <peter.tribble@gmail.com>
To: illumos-discuss <discuss@lists.illumos.org>
Subject: Re:   Re: [discuss] No network connection after updating OpenIndiana
Date: Sun, 28 Jul 2024 18:00:09 +0100	[thread overview]
Message-ID: <CAEgYsbH3Dt7AG=Bfvk33sL7gOu3s_EQYoiAcS_h9yfY1s60h=A@mail.gmail.com> (raw)
In-Reply-To: <3ac73720-b2aa-4799-9dd6-44ad0f0bc36e@me.com>

[-- Attachment #1: Type: text/plain, Size: 1959 bytes --]

On Sun, Jul 28, 2024 at 5:34 PM Ignacio Soriano Hernandez via
illumos-discuss <discuss@lists.illumos.org> wrote:

> No worries, it is not working in Virtualbox VM's either after today's
> latest pkg update .. e1000g0 registered/unregistered nwamd_door_req_state:
> ncu interface:e1000g0 not found ..
>

So the basic question is: has the device not been recognised by the driver,
or is it some
higher level in the stack (like nwam) that's gone wrong? (The fact that the
interface
name appears in the error messages seems to indicate that the device
exists.)

I'm not exactly sure how to identify this. But:

Does anything appear in /dev/net?

Can 'dladm show-phys' see it?

Does 'prtconf -D | grep e1000' show it?

The thing is, the last update to the driver was over 4 months ago, so a
broken
driver seems unlikely.


> Tested in OI VM's on VBox 7 Solaris and LMDE 6.
>
> Cheers
>
> Iggi
>
>
>
> forums.scavenger100 via illumos-discuss <discuss@lists.illumos.org>
> schrieb am 28. Juli 2024 um 17:07:
>
>
> I have the impression that there is very little testing. You only release
> a new release occasionally to show that the project is still alive. Whether
> the release is working is another story. I wrote here to inform you that
> there is a problem. Hopefully you can resolve it in the next round of
> updates. I will go back to Windows and wait. This is how we do things in
> Windows and I have gotten used to it.
>
>
> *illumos <https://illumos.topicbox.com/latest>* / illumos-discuss / see
> discussions <https://illumos.topicbox.com/groups/discuss> + participants
> <https://illumos.topicbox.com/groups/discuss/members> + delivery options
> <https://illumos.topicbox.com/groups/discuss/subscription> Permalink
> <https://illumos.topicbox.com/groups/discuss/Te24adcd65fc49422-M73b9053754ad9f304ba8ceae>
>


-- 
-Peter Tribble
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/

[-- Attachment #2: Type: text/html, Size: 3478 bytes --]

  reply	other threads:[~2024-07-28 17:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-28 14:38 forums.scavenger100
2024-07-28 14:44 ` [discuss] " Marcel Telka
2024-07-28 14:52   ` forums.scavenger100
2024-07-28 15:06     ` forums.scavenger100
2024-07-28 16:34       ` Aw: " Ignacio Soriano Hernandez
2024-07-28 17:00         ` Peter Tribble [this message]
2024-07-28 17:06           ` Robert Mustacchi
2024-07-28 18:41             ` Aw: " Ignacio Soriano Hernandez
2024-07-28 17:03       ` John D Groenveld
2024-07-28 23:51       ` Goetz T. Fischer
2024-07-29 17:18         ` Toomas Soome
2024-07-30 17:26           ` Aw: " Ignacio Soriano Hernandez
2024-07-30 21:18             ` forums.scavenger100
2024-07-30 21:31               ` Aw: " Ignacio Soriano Hernandez
2024-07-28 15:35   ` Peter Tribble
2024-07-28 19:56     ` Aw: " Ignacio Soriano Hernandez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAEgYsbH3Dt7AG=Bfvk33sL7gOu3s_EQYoiAcS_h9yfY1s60h=A@mail.gmail.com' \
    --to=peter.tribble@gmail.com \
    --cc=discuss@lists.illumos.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).