> Date: Fri, 19 Sep 2008 10:19:21 +0200
> From: Guillaume Assens <iceman_im(a)hotmail.fr>
> Subject: [fedora-arm] Rfsbuild not working...
> To: <fedora-arm(a)redhat.com>
> Message-ID: <BLU137-W738E0F096F7F196BAEF10EC4E0(a)phx.gbl>
> Content-Type: text/plain; charset="iso-8859-1"
>
>
> Hi,
>
> I'm a newbie in cross-compilation and i couldn't get rfsbuild working on my fedora F9.
>
> In fact my aim is to use Rfsbuild to create an rfs for an ARMv5 processor based developement board.
>
> But i've got "RFS build file not found"...
> I dont know if it's my host PC configuration or not...
>
> Plz help me undesrstand...
>
> Thank you in advance,
> iceman_im
>
> see the build rfslog here :
>
> Invoking server script...
> startQEMU
> Build RFS under QEMU using rfsb=192.168.100.123:/home/assensg/ARM_Fedora/newrfs/rfsb
> Kernel: ./zImage
> -initrd ./initrd.gz
> console=ttyAMA0 root=/dev/ram ramdisk_size=92386 ip=192.168.100.123:192.168.100.123:10.0.0.1:255.255.255.0:localhost:eth0:none
This is telling the ARM kernel running under QEMU that its
IP=192.168.100.123 and the (nfs) server IP= 192.168.100.123 - probably
not what you want. You probably have an IP address for your host
already (192.168.100.123 I expect) - you want to specify a different
IP here for the ARM kernel - choose a 192.168.100.nnn address that is
not used by anything else on your network.
Also if your host is on the 192.168.100.nnn network your gateway is
probably not 10.0.0.1 - more likely it is 192.168.100.1. Only you can
check these numbers - here is the format:
ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>
client-ip is the address you want to assign to the QEM ARM kernel
server-ip is your host IP that will be exporting the NFS directory
where you want to build the new RFS presumeably.
gw-ip is the address of your gateway to the internet
So check them out and edit startQemu accordingly.
The string for rfsb is derived from the server-ip and the path to
newrfs that you specified
> rfsb=192.168.100.123:/home/assensg/ARM_Fedora/newrfs/rfsb
After you straighten out your IP addresses make sure that your server
is exporting the newrfs directory?: /home/assensg/ARM_Fedora/newrfs.
It might be better to export a directory which is not in your home
path, e.g. /rfsdir. But in any case you should verify that you have
NFS working on your host system first - you can find lots of help in
the NFS-Howto. When you are sure the host NFS server is working then
test
QEMU access to it as indicated in the README:
...
3. Create the RFS directory:
# mkdir /newrfs
4. Export /newrfs via NFS. <<<<< this is
what you need to check!!!
Check that it is accessible from QEMU.
# ./startQEMU 192.168.100.123:/newrfs/abcde
>From QEMU you should see 192.168.100.123:/newrfs mounted on /newrfs.
QSH# df -a /
If NFS is not working it is likely that QEMU networking is not set up
properly or NFSD on the host is not successfully exporting /newrfs.
- tony
> Uncompressing Linux.................................................................................................. done, booting the kernel.
> Linux version 2.6.24-rc7 (buytenh(a)delta.wantstofly.org) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33.fa1)) #1 Wed Jan 16 02:28:08 CET 2008
> CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00093177
> Machine: ARM-Versatile PB
> Memory policy: ECC disabled, Data cache writeback
> CPU0: D VIVT write-through cache
> CPU0: I cache: 4096 bytes, associativity 4, 32 byte lines, 32 sets
> CPU0: D cache: 65536 bytes, associativity 4, 32 byte lines, 512 sets
> Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
> Kernel command line: console=ttyAMA0 root=/dev/ram ramdisk_size=92386 ip=192.168.100.123:192.168.100.123:10.0.0.1:255.255.255.0:localhost:eth0:none rfsb=192.168.100.123:/home/assensg/ARM_Fedora/newrfs/rfsb
> PID hash table entries: 1024 (order: 10, 4096 bytes)
> Console: colour dummy device 80x30
> Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
> Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
> Memory: 256MB = 256MB total
> Memory: 231296KB available (2796K code, 243K data, 116K init)
> Mount-cache hash table entries: 512
> CPU: Testing write buffer coherency: ok
> net_namespace: 64 bytes
> NET: Registered protocol family 16
> PCI core found (slot 11)
> PCI: bus0: Fast back to back transfers disabled
> PCI map irq: slot 0, pin 1, devslot 12, irq: 27
> SCSI subsystem initialized
> Time: timer3 clocksource has been installed.
> NET: Registered protocol family 2
> IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
> TCP established hash table entries: 8192 (order: 4, 65536 bytes)
> TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
> TCP: Hash tables configured (established 8192 bind 8192)
> TCP reno registered
> checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
> Freeing initrd memory: 25322K
> NetWinder Floating Point Emulator V0.97 (double precision)
> Installing knfsd (copyright (C) 1996 okir(a)monad.swb.de).
> JFFS2 version 2.2. (NAND) (c) 2001-2006 Red Hat, Inc.
> io scheduler noop registered
> io scheduler anticipatory registered (default)
> io scheduler deadline registered
> io scheduler cfq registered
> CLCD: unknown LCD panel ID 0x00001000, using VGA
> CLCD: Versatile hardware, VGA display
> Clock CLCDCLK: setting VCO reg params: S=1 R=99 V=98
> Console: switching to colour frame buffer device 80x30
> Serial: AMBA PL011 UART driver
> dev:f1: ttyAMA0 at MMIO 0x101f1000 (irq = 12) is a AMBA/PL011
> console [ttyAMA0] enabled
> dev:f2: ttyAMA1 at MMIO 0x101f2000 (irq = 13) is a AMBA/PL011
> dev:f3: ttyAMA2 at MMIO 0x101f3000 (irq = 14) is a AMBA/PL011
> fpga:09: ttyAMA3 at MMIO 0x10009000 (irq = 38) is a AMBA/PL011
> RAMDISK driver initialized: 16 RAM disks of 92386K size 1024 blocksize
> tun: Universal TUN/TAP device driver, 1.6
> tun: (C) 1999-2004 Max Krasnyansky
> smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre
> eth0: SMC91C11xFD (rev 1) at d0866000 IRQ 25 [nowait]
> eth0: Ethernet addr: 52:54:00:12:34:56
> PCI: enabling device 0000:00:0c.0 (0140 -> 0143)
> sym0: rev 0x0 at pci 0000:00:0c.0 irq 27
> sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
> sym0: SCSI BUS has been reset.
> scsi0 : sym-2.2.3
> scsi 0:0:2:0: CD-ROM QEMU QEMU CD-ROM 0.9. PQ: 0 ANSI: 3
> target0:0:2: tagged command queuing enabled, command queue depth 16.
> target0:0:2: Beginning Domain Validation
> target0:0:2: Domain Validation skipping write tests
> target0:0:2: Ending Domain Validation
> Driver 'sd' needs updating - please use bus_type methods
> mice: PS/2 mouse device common for all mice
> input: AT Raw Set 2 keyboard as /class/input/input0
> rtc-pl031 dev:e8: rtc core: registered pl031 as rtc0
> input: ImExPS/2 Generic Explorer Mouse as /class/input/input1
> TCP cubic registered
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> RPC: Registered udp transport module.
> RPC: Registered tcp transport module.
> VFP support v0.3: implementor 41 architecture 1 part 10 variant 9 rev 0
> rtc-pl031 dev:e8: setting system clock to 2008-09-19 08:07:38 UTC (1221811658)
> RAMDISK: Compressed image found at block 0
> VFS: Mounted root (ext2 filesystem) readonly.
> Freeing init memory: 116K
>
> modprobe: FATAL: Could not load /lib/modules/2.6.24-rc7/modules.dep: No such file or directory
>
> Mount failed for selinuxfs on /selinux: No such device
> INIT: version 2.86 booting
> Welcome to Fedora
> Press 'I' to enter interactive startup.
> modprobe: FATAL: Could not load /lib/modules/2.6.24-rc7/modules.dep: No such file or directory
>
> Cannot access the Hardware Clock via any known method.
> Use the --debug option to see the details of our search for an access method.
> Setting clock (utc): Fri Sep 19 04:08:15 EDT 2008 [ OK ]
> Setting hostname localhost.localdomain: [ OK ]
> Checking filesystems
> Checking all file systems.
> [ OK ]
> Remounting root filesystem in read-write mode: [ OK ]
> mount: can't find / in /etc/fstab or /etc/mtab
> Mounting local filesystems: [ OK ]
> Enabling /etc/fstab swaps: [ OK ]
> INIT: Entering runlevel: 3
> Entering non-interactive startup
> FATAL: Could not load /lib/modules/2.6.24-rc7/modules.dep: No such file or directory
> Bringing up loopback interface: [ OK ]
> FATAL: Could not load /lib/modules/2.6.24-rc7/modules.dep: No such file or directory
> Starting rpcbind: [ OK ]
> modprobe: FATAL: Could not load /lib/modules/2.6.24-rc7/modules.dep: No such file or directory
>
> Starting NFS statd: [ OK ]
> Starting RPC idmapd: FATAL: Could not load /lib/modules/2.6.24-rc7/modules.dep: No such file or directory
> Error: RPC MTAB does not exist.
> Mounting other filesystems: [ OK ]
> Starting system logger: [ OK ]
> Starting kernel logger: [ OK ]
> Starting system message bus: [ OK ]
>
> Fedora release 8 (Werewolf)
> Kernel 2.6.24-rc7 on an armv5tel
>
> localhost login: root (automatic login)
> Automatic RFS build starting in 5 seconds.
> Hit Ctl-C to interrupt....
> Server: 192.168.100.123, rfspath: /home/assensg/ARM_Fedora/newrfs, rfsb: /home/assensg/ARM_Fedora/newrfs/rfsb
> Mounting: 192.168.100.123:/home/assensg/ARM_Fedora/newrfs
> mount: mount to NFS server '192.168.100.123' failed: System Error: Network is unreachable.
> *** RFS build file not found: /home/assensg/ARM_Fedora/newrfs/rfsb
> -bash-3.2#
