Hello, I've been trying to make a bootable rootfs for the nanonote, while I use the openwrt 2.6.35 kernel.
I noticed that the openwrt kernel uses /etc/preinit as init script. I prepared that in the rootfs. I also have the same NAND map as set in the kernel for qi_lb60 (three partitions). I also see that the qi_lb60 platform defines a keymap - why that keymap does not include a kernel scroll-up/scroll-down? Page up/down mapped to the right volume keys would work great, and a userland keymap load can override that later. I also saw that uboot sets these command arguments for the kernel: mem=32M console=tty0 console=ttyS0,57600n8 ubi.mtd=2 rootfstype=ubifs root=ubi0:rootfs rw rootwait As the last console is the serial port, it means that /dev/console will be the serial port and not tty0. Why is so? Looking at the serial port, thought, I could not see the usual busybox 'init' (my /etc/preinit run #!/bin/sh\nexec /sbin/init) invitation to open a console pressing Enter. Instead, there I see: [ 11.090000] Freeing unused kernel memory: 144k freed [ 11.240000] Algorithmics/MIPS FPU Emulator v1.5 /bin/sh: can't access tty; job control turned off And the last thing that appears on tty0 is, the Algorithmics kernel line. So I guess the proper way to boot something is to have inittab spawning an interactive process on tty0, instead of expecting /dev/console to work on the screen/keyboard. Right? Sorry if I ask trivial questions... I know that some distributions have all this solved, but I'm taking it as a way to learn. Maybe I am using something outdatted. If someone thinks that I should use more up to date versions, please let me know. Regards, Lluís. _______________________________________________ Qi Hardware Discussion List Mail to list (members only): [email protected] Subscribe or Unsubscribe: http://lists.en.qi-hardware.com/mailman/listinfo/discussion
