The reason I said that is it is not loading the required ELF binary (
virtio_mmio_nic).
Also when i clicked on wired in sculpt there is no mac address
initialization i can see into the sculpt.
Also i am not able to download and add any components in running sculpt.
It is just running in the runtim
Hello Divya,
On Wed, Mar 29, 2023 at 19:52:03 CEST, Divya Sharma wrote:
> [init -> runtime] child "nic_drv"
> [init -> runtime] RAM quota: 20232K
> [init -> runtime] cap quota: 266
> [init -> runtime] ELF binary: nic_drv -->
> [init -> runtime] priority: 2
> [init -> runtime] child "n
Thanks Norman and Martin for details explanation,
I removed the static drivers configuration rules from drivers subsystem and
kept the other scripts(like sculpt.run) as it is modified at [1] and got
the following log entries in terminal when clicked on wired in Sculpt.
[init -> runtime] child "ni
Hello,
I modified the sculpt.run as you said but still the uplink session
is not getting created may be because of the label mismatch.
[init] Warning: drivers: no route to service "Uplink"
(label="drivers -> virtio_mmio_nic -> ")
[init -> drivers -> virtio_mmio_nic] Error: U
Hi Divya,
First of all, I'm not sure whether you see this right: It's not your NIC
router that is missing a route but your NIC driver. In Genode NIC
drivers are NIC session clients and the NIC router is a NIC session server.
Second, the main problem in your case seems to be that you do the NIC
dr
On Sat, Mar 25, 2023 at 2:28 PM Divya Sharma
wrote:
> Thanks Norman for your suggestion.
> I modified the sculpt.run as you said but still the uplink session is not
> getting created may be because of the label mismatch.
>
> [init] Warning: drivers: no route to service "Uplink" (label="drivers ->
Hello Divya,
On 2023-03-15 11:27, Divya Sharma wrote:
As you said i launched only [init -> runtime -> virtio_mmio_nic]
component,but still the runtime version is not getting the mac
address,as seen in the log ,don't why.Is there anything left for routing
the uplink request from nic driver to
As you said i launched only [init -> runtime -> virtio_mmio_nic]
component,but still the runtime version is not getting the mac address,as
seen in the log ,don't why.Is there anything left for routing the uplink
request from nic driver to virtio_mmio_nic.
kindly guide me on it.
Divya.
On Sat
Divya,
On Sat, Mar 11, 2023 at 6:19 AM Divya Sharma
wrote:
> Thanks Martin and Colin for your help.
> I configured the virtio_mmio_nic configuration for virt_qemu_arm_v8a
> using [1] archive?
> But after that i got stuck in the error
> [init] Warning: drivers: no route to service "Uplink" (label
Thanks Martin and Colin for your help.
I configured the virtio_mmio_nic configuration for virt_qemu_arm_v8a using
[1] archive?
But after that i got stuck in the error
[init] Warning: drivers: no route to service "Uplink" (label="drivers ->
virtio_mmio_nic -> ")
[init -> drivers -> virtio_mmio_nic]
Hello,
some reason. I assume that an image file with this name is not present,
> but without further information about your sculpt setup (package list,
> sculpt config, etc.), I cannot say for sure.
>
> I just noticed, that the virt qemu NIC driver binary is not named
> nic_drv but virtio_mmio_nic
Hi Divya,
AFAIK, only NIC and input are supported currently on virt_qemu in
general, but I'm not too much into that topic.
The error you posted is simply saying that the program that prints it
(see the label prefix in the log) tries to open an image file named
"nic_drv" and that the request was d
hello guys,
After many efforts and with your generous help I'm able to build and run
sculpt an image for "virt_qemu_arm_v8a".
But now I want to enable some driver support in OS like USB,Wifi and
Lan-Ethernet.
while trying to configure Lan got this error.
" Error: nic_drv: environment ROM session de
Hi Divya,
As a further notice, there is also the alternative way of providing the
event_filter config statically (instead of the dynamic way via the
sculpt_manager).
In order for this to work you'd need an individual *.sculpt file for
your platform (see [1] and [2] for how this works). In this fi
Hi Divya,
Your drivers seem to come up fine, but your event filter (the server for
filtering and multiplexing your input events) indicates that it cannot
accept the sessions that the drivers are trying to create [3] because
you didn't configure event_filter appropriately. However, the config for
t
Hi Divya,
The log file you attached contains nothing substantial because, AFAICT,
you have to add LOG=core to your command line:
make run/sculpt_test ... LOG=core
Please consider re-sending the log file with the mentioned option added.
As Stefan already mentioned, Sculpt + ARM + Qemu is not off
Thanks a lot Stefan for your explanation about the driver configuration.
I followed your roadmap and tried to configure the drivers with help of the
driver subsystem file that you mentioned for virt_qemu_arm_v8a platform and
generated the image.elf at /
*genode/build/arm_v8a/var/run/sculpt/boot/ima
Hello Divya,
as has been said, the virt_qemu_arm_v8a platform is not supported to run
Sculpt yet. Nonetheless, essential drivers that need to be assembled
to run Sculpt OS on this platform are already available in Genode.
Therefore, it is mostly some integration work necessary, which you
would nee
Hello genodians
This is continuous from previous mail
I'm fine a lot about virt_qemu in previous mails and any other sources but
unable to find proper documentation or anything.
So if anyone suggest anything for virt_qemu for arm that would be great.
Thanks and Regards
Divya
On Sat, 1 Oct, 20
Hello genodians,
We are trying to port genode for BOARD=virt_qemu_arm_v8a
So for that we need to change this file
" Given the sculpt.run script in 'repos/gems/run/', you'll find the
restrictions in lines 13-23. Of course you might add the virt_qemu
platform here. However, you've to build a proper
20 matches
Mail list logo
