Howdy, I seem to recall something like that with similar hardware, a Nic working in Sculpt, but not in my own run scenarios.
I ended up closing the ticket as fixed-with-workaround, after realizing this one particular Nic card should not be initialized too soon after boot up, but should be delayed by a few seconds by using e.g. the "sequence" Genode component and an ad-hoc "sleep" tiny component.
Who knows, you might be in a similar situation ?
The 'run' code is available on my chiselapp.com repo, here's an excerpt with the jam scripting used, please adapt to gmake:
# Don't launch (nic_drv) immediately, as that won't work on e.g. ThinkCentre M73, delay by 8 seconds (5 secs seems a little iffy): AddComponentAsStart $(runfile) : 28M : sequence : "name="sequence" caps="320"" : " <config> \ <start name="sleep" caps="100"> \ <config> \ <libc stdin="/dev/null" stdout="/dev/log" stderr="/dev/log"/> \ <arg value="/bin/sleep"/> \ <arg value="8"/> \ <vfs> \ <dir name="dev"> <log/> <null/> </dir> \ </vfs> \ </config> \ </start> \ \ <start name="nic_drv" caps="219" > \ <binary name="pc_nic_drv"/> \ <config> \ </config> \ </start> \ </config> \ <route> \ <any-service> <parent/> <any-child/> </any-service> \ </route>
Cédric
De : hamed_khandagh--- via users users@lists.genode.org I am currently evaluating the ping_nic_router application, along with similar networking programs, for establishing network connectivity on x86_64 hardware. My primary network interface card (NIC) is an R8169 model, which none of the existing programs are able to detect. However, upon integrating an Intel e1000 NIC, the connection was successfully established.
Furthermore, the Sculpt operating system is able to interface correctly with both NICs and establish communication with the external network without any issues.
Despite thorough comparison, I have been unable to identify any significant differences between the Sculpt operating system's networking functionality and the ping_nic_router application. I am uncertain whether I am overlooking a particular detail or if there is a requirement to modify the source code to accommodate the r8169 NIC.