Hi Detlev and Wolfgang, -------------------------------------------------------------------------------------------------------------------------------------------- ***********************************************SOLUTION N°1************************************************************************** --------------------------------------------------------------------------------------------------------------------------------------------
I followed the steps on this link http://www.denx.de/wiki/DULG/AN2009_02_EldkReleaseBuildEnvironment with QEMU. when launching QEMU as told in the link : # qemu -m 1024 -net nic,model=rtl8139 -net tap,script=/etc/ifup-build -hda root-rh-7.3.img -hdc /dev/vg0/eldk_build I got these errors : /etc/ifup-build: could not launch network script Could not initialize device 'tap' The ifup-build file exists and I have not done modifications in it. Concerning the device tap : I tried before launching QEMU : # tunctl -d tap0 Set 'tap0' nonpersistent # tunctl -u alberix -t tap0 Set 'tap0' persistent and owned by uid 1000 and then : qemu -m 1024 -net nic,model=rtl8139 -net tap,fd=tap0,script=/etc/ifup-build -hda root-rh-7.3.img -hdc /dev/vg0/eldk_build The next steps worked pretty well (I have done exactly what it's told in the link above) till I tried to access the VBH from the host with this command line as explain on the link : $ cd /net/eldk-build/opt/eldk/ It says No such file or directory On my envirronment host, I use Ubuntu : there is not directory /net so it's normal. How can I reach /opt/ ? Is there any command to do from the host to make him being able to see /opt/ ? (When I look for /opt/, it doesn't fing anything) I thought it may comes from tap0. after this command line : ifconfig tap0 10.100.0.1 netmask 255.255.255.252 I have this network configuration on the host : eth0 Link encap:Ethernet HWaddr 00:1d:60:db:26:31 inet adr:192.93.121.5 Bcast:192.93.121.255 Masque:255.255.255.0 adr inet6: fe80::21d:60ff:fedb:2631/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Packets reçus:26937 erreurs:0 :0 overruns:0 frame:0 TX packets:14684 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:1000 Octets reçus:15018512 (15.0 MB) Octets transmis:2484870 (2.4 MB) Interruption:23 Adresse de base:0x800 lo Link encap:Boucle locale inet adr:127.0.0.1 Masque:255.0.0.0 adr inet6: ::1/128 Scope:Hôte UP LOOPBACK RUNNING MTU:16436 Metric:1 Packets reçus:70 erreurs:0 :0 overruns:0 frame:0 TX packets:70 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 Octets reçus:5344 (5.3 KB) Octets transmis:5344 (5.3 KB) tap0 Link encap:Ethernet HWaddr da:51:cd:da:d4:58 inet adr:10.100.0.1 Bcast:10.100.0.3 Masque:255.255.255.252 adr inet6: fe80::d851:cdff:feda:d458/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Packets reçus:0 erreurs:0 :0 overruns:0 frame:0 TX packets:0 errors:0 dropped:38 overruns:0 carrier:0 collisions:0 lg file transmission:500 Octets reçus:0 (0.0 B) Octets transmis:0 (0.0 B) virbr0 Link encap:Ethernet HWaddr 06:d2:63:22:e6:a3 inet adr:192.168.122.1 Bcast:192.168.122.255 Masque:255.255.255.0 adr inet6: fe80::4d2:63ff:fe22:e6a3/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Packets reçus:0 erreurs:0 :0 overruns:0 frame:0 TX packets:29 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 Octets reçus:0 (0.0 B) Octets transmis:4528 (4.5 KB) And this network configuration on the VBH : eth0 Link encap:Ethernet HWaddr 52:54:00:12:34:56 inet adr:10.100.0.2 Bcast:10.100.0.3 Masque:255.255.255.252 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX Packets:0 erreurs:0 dropped:0 overruns:0 frame:0 TX packets:96 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:5760 (5.6 Kb) Interrupt:11 Base address:0x9000 lo Link encap:Local Loopback inet adr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX Packets:98 erreurs:0 dropped:0 overruns:0 frame:0 TX packets:98 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:7808 (7.6 Kb) TX bytes:7808 (7.6 Kb) I should be able to ping the VBH from the host (the same in the inverse way) but I don't. PING 10.100.0.2 (10.100.0.2) 56(84) bytes of data. >From 10.100.0.1 icmp_seq=1 Destination Host Unreachable Even if I set : Host ip address for eth0 : 192.93.121.5 (same as before) Host ip address for tap0 : 192.93.121.54 VBH ip address for eth0 : 192.93.121.53 I got the same (no ping). It seems the host and the VBH cannot communicate. I may have forgot something, do you have any idea ? -------------------------------------------------------------------------------------------------------------------------------------------- ***********************************************SOLUTION N°2************************************************************************** -------------------------------------------------------------------------------------------------------------------------------------------- Concerning the other way (not running Qemu) using chroot, I don't manage to do it. Here is what I have done : $ mount -o loop -t auto /home/alberix/Documents/eldk_build/root-rh-7.3.img /dev/sda8 It tells me to specify the type of filesystem. So I tried : $ mount -t ext3 /home/alberix/Documents/eldk_build/root-rh-7.3.img /dev/sda8 but it tells me the type is wrong (even with ext2) and doing : $ dmesg | tail I got : [ 68.112018] virbr0: no IPv6 routers present [ 78.176015] eth0: no IPv6 routers present [ 84.952727] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. [ 1039.142136] tun: Universal TUN/TAP device driver, 1.6 [ 1039.142140] tun: (C) 1999-2004 Max Krasnyansky <[email protected]> [11079.456495] VFS: Can't find ext4 filesystem on dev loop0. [11924.595581] VFS: Can't find ext3 filesystem on dev loop0. [12020.438808] VFS: Can't find an ext2 filesystem on dev loop0. [12029.619199] VFS: Can't find ext4 filesystem on dev loop0. [12069.589080] VFS: Can't find ext3 filesystem on dev loop0. The type of root-rh-7.3.img is unknown and when I try to convert it in a .iso with iat, I got : This image is not CD IMAGE I am not able to chroot into the RH-7.3 build environment. -------------------------------------------------------------------------------------------------------------------------------- Thank you for your replies Best Regards Marie-Reine ________________________________________ De : Detlev Zundel [[email protected]] Date d'envoi : mercredi 28 juillet 2010 18:51 À : Marie Reine SARAZIN Cc : eldk-list Objet : Re: RE : How can I build agin the toolchain ? (ELDK) Hi Marie Reine, [please keep the list on CC, as this is intersting for more people] > Thank you for your reply. No, there is not any fix for the driver. Maybe you can come up with an functionally equivalent substitution code? > My problem is that my processor does not support virtualization > technology. So i cannot use kvm. Is there any other way to setup the > required build environment ? Well actually QEMU does not need kvm to run, it only runs faster using it on the same architecture. You should even be able to run QEMU emulating an Intel CPU on a Power Architecture machine :) If you have hardware which is still supported by RH-7.3 you can of course do all this in a non-emulated environment just as well. Cheers Detlev -- LISP is the most powerful programming language, and if you want an inter- preter, LISP is the best. None of the other languages come anywhere near LISP in their power. The most exciting things about LISP are read, eval, and print. If you look at other languages, they have no equivalent for any of those. -- Richard Stallman -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: [email protected] _______________________________________________ eldk mailing list [email protected] http://lists.denx.de/mailman/listinfo/eldk
