[Qemu-devel] BeOS 5.0.3 network problems

[Qemu-devel] BeOS 5.0.3 network problems

[ruiapimenta]

I've successfully installed BeOS personal edition and upgrades
But I can't manage to put network working!

user net:
I get 0.0.0.0 has an ip - don't work

tap0:
netstat list
0:  192.168.2.2   // ip i gave it
1:      0.0.0.0   // Our famous ip :P
2:    127.0.0.1   // lo0 ? OK

this doesn't work also.

With other OSes I have installed the two methods above worked fine

Using FreeBSD 5.2.1 port 0.6.1s.2001115 (CVSup'ed)

Also, no luck with google.

Any help will be apreciated,

Rui

P.S.: Thanks for this incredible piece of software!



-----------------------------------
Chegou o Clix Turbo ADSL a 8 Megas
Internet + Telefone sem assinatura telefónica
Saiba mais em http://adsl.clix.pt

Re: [Qemu-devel] BeOS 5.0.3 network problems

[Christian Wiese]

ruiapimenta@clix.pt wrote:

>I've successfully installed BeOS personal edition and upgrades
>But I can't manage to put network working!
>  
>
Hi,

just4info. I tried also Zeta which uses Bone and not the R5-net_server. 
The results are the same. But the output on serial 1 looks like no 
answer to any paket are received (some timeout if i remember correctly). 
There is even no answer an a ping to 10.0.2.2. So the problem is very 
basic. The N2k-card is detected and the MAC is Ok, so I think that the 
initial part is working.
For my tests I set the IP to 10.0.2.5, DNS to 10.0.2.3 and Gateway to 
10.0.2.2.
On another note, can someone send me a profiling-exe for windows? If I 
build with -enable-gprof it builds now, but no output is created. I read 
somewhere that Mingw has a gprof-bug, not sure if this is my problem. Thx.

Greetings,
 Chris

Re: [Qemu-devel] BeOS 5.0.3 network problems

[Christian Wiese]

ruiapimenta@clix.pt wrote:

>Totally off-topic:
>What's the difference between "normal" and profiling?
>Forgive my ignorance...
>
>Regards,
>Rui
>  
>
If you run a program which is build with profiling enabled, the time is 
measured which was spend to execute different functions. This allows you 
to detect very time-consuming functions. As you may have noticed, BeOS 
in qEmu uses 100% of your host-cpu-time even if BeOS itself is idle (and 
uses HLT-instruction). With the use of a profiled-build I hope to 
identify the function which is "running wild".

Re: [Qemu-devel] BeOS 5.0.3 network problems

[Christian Wiese]

ruiapimenta@clix.pt wrote:

>Hum... I've compiled QEMU 0.6.1s20041115, could you
>tell me how do I generate a profiling qemu executable? 
>(I can use gcc32 or gcc34 - FreeBSD systems )
>And how do i search for the "cpu hungry" functions?
>  
>
Do a configure with option "-enable-gprof".  Use the generated binary as 
it is the normal qEmu. Do average stuff in BeOS and shut down. In your 
working directory should be a new file. These file listed all called 
functions and the time the programm has spend in it. Then you could run 
BeOS and do nothing. The resulting file should show us, where the time 
has gone :-)

>BeOS seems a nice simple clear OS, that I would like to test
>a litle bit more.
>  
>
It´s worth it. BeOS is a fantastic OS, but not enough developers at the 
moment :-/  Hope this will change with Zeta and Haiku

For further question you can mail me directly, so we don´t flood the list.

Greetings,
 Chris