=== bjf is now known as bjf-afk [04:31] Does anyone know what boards are going to be supported by Lucid? === kedars_ is now known as kedars [06:17] hi, here's a question about initramfs: I did see the following scripts in /init which deals with root=/dev/nfs and export BOOT=nfs. Why I still need modify /etc/initramfs-tools/initramfs.conf to change BOOT from local to nfs? [06:18] I tried NOT to modify BOOT from local to nfs. The result is the export BOOT=nfs script in /init do NOT work. [06:18] I still saw BOOT=local by command "env", even if I pass "root=/dev/nfs" in bootargs in uboot. [06:19] PS: I'm using default Karmic release [06:19] linux-image-2.6.31-208-dove_2.6.31-208.16_armel.deb [06:21] Is it necessary to create another special uInitrd.nfs for nfs boot? [06:21] thanks [06:24] Sorry, I double checked the /init script and found I missed the following condition [06:24] /dev/nfs) [06:24] [ -z "${BOOT}" ] && BOOT=nfs [06:25] it would NOT export BOOT=nfs if BOOT has another value already (local here). [06:26] eggonlea: You could try passing boot=nfs on the kernel cmdline [06:26] Oh /dev/nfs probably does the trick yes [06:26] let me try [06:26] could we just remove this "[ -z "${BOOT}" ]" in /init? [06:29] well, boot=nfs in cmdline works. [06:30] we have so many args here: netboot, boot, nfsroot=/dev/nfs, BOOT_in_initramfs.conf. [06:31] Have to go through the whole /init script to understand the priority. :( [06:32] anyway, boot_in_cmdline > BOOT_in_initramfs.conf > nfsroot=/dev/nfs_in_cmdline. Thanks! [06:48] Cool [08:15] am not getting GUI for ubuntu on dvi... anybody help... [08:16] check /var/log/Xorg.0.log [08:18] but am getting console version on dvi [08:31] which image i should get for GUI? [08:37] just log in and install xfce or whatever gui you want [08:43] jean85_: You could try installing xubuntu-desktop [08:44] but maybe even that is too memory-hungry for the ram you have on a beagle [08:44] as I said, I've never hooked up a monitor to my beagles [11:45] I have compiled a kernel for my board, How to I generate the folders for it such that I can insert into my rootfs /lib/modules/2.6..... [12:10] Try make INSTALL_MOD_PATH=$PWD/modules-tmp modules_install [12:11] This should build a suitable lib/modules tree in the scratch directory modules-tmp. [12:27] dmart: Cheers, I'll try that [12:36] dmart: Thank worked great cheers, I'm looking to do something similar for creating the linux-headers do you know a similar command? [12:38] Can't help you there I'm afraid... I'm guessing that simply copying linux/include may not work well enough. You could maybe examine debian/rules for the Ubuntu kernel source packages and see how the kernel-headers-* packages are generated. [12:40] Unless you want to rebuild glibc or other low level components, you may get away with not having the correct kernel headers in your fs though. [12:45] Yeah I don't need them at the minute because I compiled a newer kernel than came with the board for some hardware only supported later, before I was trying to compile the kernel module for the old (2.6.21) kernel but was stuggling with getting the correct kernel headers === bjf-afk is now known as bjf === bjf is now known as bjf-afk