hello to all; I want to port l4linux which is running on Fiasco.oc directly on hardware and also on p2020. when i was running l4linux.iso on hardware it is not showing the command prompt.it am getting only peguin picture. can you please tell me what i should do.
thanks and regards, vishallinux
Hi,
On 08.05.2012 12:22, Vishal Gupta wrote:
hello to all; I want to port l4linux which is running on Fiasco.oc directly on hardware and also on p2020. when i was running l4linux.iso on hardware it is not showing the command prompt.it am getting only peguin picture. can you please tell me what i should do.
The p2020 seems to be a PowerPC derivate? So I'm not sure if Fiasco.OC will run on it out of the box. At least Genode isn't fit for that platform, so there is some work to do beforehand.
With hardware you mean an x86 platform? I guess the p2020 board is hardware too ;-).
Regarding x86/ARM, if you're using the l4linux.run run-script in 'ports-foc/run' - which is actually designed to use as an automated test with QEMU - it assumes at least two serial lines whereby the first one is used for the kernel debugger and the second one should display the Linux command line. Have you both ports available?
Please, post the output of the first serial line (kernel-debugger console), if you detect any problems.
Regards, Stefan
thanks and regards, vishallinux
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hi Vishal,
just as a shot in the dark, the problem may be related to the NIC driver. The l4linux.run scenario expects an e1000 ethernet card to be present. Maybe your machine lacks such a device? For a quick test, I just tried starting the l4linux.iso image on Qemu while omitting the network-related arguments and observed the effect that you reported (only a lonely penguin who looks desperately for a command-line prompt).
You could try to remove the NIC driver from your setup. Just comment-out the following lines in 'ports-foc/run/l4linux.run'
#append_if [have_spec x86] config { # <start name="nic_drv"> # <resource name="RAM" quantum="2M"/> # <provides><service name="Nic"/></provides> # </start>}
Of course, this change will make the automated test ('make run/l4linux') fail since no network will be available anymore. But you can give the resulting ISO image ('var/run/l4linux.iso') a try on your PC hardware and see if you get to see the prompt.
Still, I second Stefan's suggestion about making the output of the serial console available.
Cheers Norman
Re:
Hi Vishal, just as a shot in the dark, the problem may be related to the NIC driver. The l4linux.run scenario expects an e1000 ethernet card to be present. Maybe your machine lacks such a device? For a quick test, I just tried starting the l4linux.iso image on Qemu while omitting the network-related arguments and observed the effect that you reported (only a lonely penguin who looks desperately for a command-line prompt). You could try to remove the NIC driver from your setup. Just comment-out the following lines in 'ports-foc/run/l4linux.run' #append_if [have_spec x86] config { # <start name="nic_drv"> # <resource name="RAM" quantum="2M"/> # <provides><service name="Nic"/></provides> # </start>} Of course, this change will make the automated test ('make run/l4linux') fail since no network will be available anymore. But you can give the resulting ISO image ('var/run/l4linux.iso') a try on your PC hardware and see if you get to see the prompt. Still, I second Stefan's suggestion about making the output of the serial console available. Cheers Norman Hello Norman I tried what ever you suggested me. But untill i am not getting the command prompt on x86_32 bit pc. First I want to tell you my problem. actually i am running l4linux on fiasco.oc in Qemu. and i am getting a Autologin terminal. but when the L4linux.iso file i burned on CD and try to bbot it on my X86 PC i am not getting command prompt just it is showing the penguin picture. actually i want to write my on application and want to use mysql on l4linux/fiasco.oc. but i am not able to understand how i should do it. Plz help So i can use my x86 pc (hardware-hard disk) with l4linux....
________________________________ From: Vishal Gupta <vishalsets@...111...> To: "genode-main@lists.sourceforge.net" genode-main@lists.sourceforge.net Sent: Tuesday, 8 May 2012 3:52 PM Subject: Want to Boot l4linux.iso directly on hardware???????
hello to all; I want to port l4linux which is running on Fiasco.oc directly on hardware and also on p2020. when i was running l4linux.iso on hardware it is not showing the command prompt.it am getting only peguin picture. can you please tell me what i should do.
thanks and regards, vishallinux
Hi Vishal,
First I want to tell you my problem. actually i am running l4linux on fiasco.oc in Qemu. and i am getting a Autologin terminal. but when the L4linux.iso file i burned on CD and try to bbot it on my X86 PC i am not getting command prompt just it is showing the penguin picture. actually i want to write my on application and want to use mysql on l4linux/fiasco.oc. but i am not able to understand how i should do it. Plz help So i can use my x86 pc (hardware-hard disk) with l4linux....
I suggest you to first experiment with a much simpler scenarios than L4Linux until having reached a profound level of understanding of the fundamentals of Genode, its configuration and boot concept, and the Fiasco.OC kernel debugger. In particular I warmly suggest following Stefan's advise to retrieve the output of the serial line of your PC.
Acquainting yourself with the following topics will certainly boost your experience:
* Connect the serial line with your test PC to your workstation PC (using minicom or a similar terminal program), watch the boot messages of the Fiasco.OC kernel and Genode. If you post a problem, supply those messages along with your posting. Otherwise it is almost impossible to remotely diagnose your problem.
* Start using the kernel debugger to see what is going on. If you reach a little proficiency with using this powerful tool, you will be able to pinpoint problems much easier.
* Investigate booting over network rather than via an ISO image (configure and use a boot loader that supports TFTP or HTTP, set up a proper network boot environment in your network). This eliminates the long-taking (and potentially frustrating) manual steps of burning and booting ISO images.
* Find out how Genode's run scripts are working under the hood. This is fundamental to reach a self-determined mode of working. Your current approach of "I tried what ever you suggested me" will not make you happy in the long run.
Once you have reached confidence in creating and booting small custom Genode scenarios (routing of services, assignment of resources, using device drivers), you will be ready to move on to more advanced features such as embedding L4Linux into the picture, or letting L4Linux access a hard disk via a block-device driver.
Regards Norman
-
Norman Feske -
Stefan kalkowski -
Vishal Gupta