Re: Re: OE build files

hi,

i have build some new images for the axim

perhaps someone with an serial cable could test them

http://law.hostsen.net/oe/aximx50-image-20070208.tar.bz2

with usb the image doesnt boot...

i ´ll search a serial cable now in the internet (i am from austria).

regards,
 patrick

On Thursday, 8. February 2007 13:08:20 Patrick Steiner wrote:
> i have added a new set of files:
> http://law.hostsen.net/oe/aximx50_oe_stuff_20070208_2.tar.bz2
>
> now the current kernel should build without any problems.
>
> patrick
>
> Patrick Steiner wrote:
> > Paul Sokolovsky wrote:
> >> Hello Patrick,
> >>
> >> Thursday, February 8, 2007, 12:05:57 PM, you wrote:
> >>> thanks that helps me a lot. i´ll try to build a new image today. it
> >>> looks like i have to build a new intrd also.
> >>>
> >>> could someone give me some infos how to build such a file?
> >>> i know its a ext2 image i can mount it via mount -o loop -t ext3....
> >>> but there are not all files in /lib/modules/<kernelversion>/ which are
> >>> required?
> >>> is there some buildscript available?
> >>
> >> You don't need anything special apart from what OE builds for you.
> >> There's no need for initrd to boot any developed 2.6 kernel port, and
> >> likely, no need for any port at all. The only unavoidable case when
> >> you need to build driver as a module (and put it into initrd) is when it
> >> loads firmware. So, if you'd want to boot over WiFi, you'd have to do
> >> that. There're also driver dependencies issues pop up regularly, but
> >> so far for all cases we were able to solve them on kernel level,
> >> producing static kernel capable of loading rootfs from any common
> >> source like ramdisk, SD/CF card, or NFS (over USB).
> >>
> >> OE currently doesn't support building boot initrd's, exactly per the
> >> reason described - you can easily get around it. Of course, you can
> >> use any OE-built image as rootfs initrd, i.e. boot from it as ramdisk.
> >> For example, I had no problems booting with haret 0.4.7 from 40Mb OPIE
> >> initramfs image. Still for development, the most convenient way is NFS
> >> booting. If you don't have that setup, I suggest investing half and
> >> hour into that.
> >
> > is there any how to available?
> >
> > i have uploaded the changed files
> > http://law.hostsen.net/oe/aximx50_oe_stuff_20070208.tar.bz2
> >
> > now i´ll try to build a fresh image an boot it via haret. btw. a irc
> > would be nice :-) i am always on #oe and #angstrom nick (_law_)
> >
> >>> Jake Grimmett wrote:
> >>>> Hi Patrick,
> >>>>
> >>>> I've got my serial port wired up for you - it looks like a simple
> >>>> mistake to fix - you appear to be using the 2.6.19-hh10 kernel with
> >>>> the 2.6.19-hh9 modules...
> >>>>
> >>>> i.e.
> >>>>
> >>>> Linux version 2.6.19-hh10 (pat_at_tux4u.skynet) (gcc version 4.1.1) #
> >>>> CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=0000397f
> >>>> Machine: Dell Axim X50/X51(v)
> >>>> *snip*
> >>>> Kernel command line: root=/dev/ram0 rw ramdisk_size=12288 mem=64M
> >>>> keepinitrd in8
> >>>> *snip*
> >>>> checking if image is initramfs...it isn't (no cpio magic); looks
> >>>> like an initrd
> >>>> *snip*
> >>>> RAMDISK driver initialized: 16 RAM disks of 12288K size 1024 blocksize
> >>>> *snip*
> >>>> Mounting /proc...
> >>>> Trying to mount the fat32 SD card... FATAL: Could not load
> >>>> /lib/modules/2.6.19-y
> >>>> modprobe: FATAL: Could not load
> >>>> /lib/modules/2.6.19-hh10/modules.dep: No such fy
> >>>> mount: Mounting /dev/mmc/blk0/part1 on /mnt/sdcard failed: No such
> >>>> device
> >>>> failed!
> >>>> Dropping to a shell and enabling the telnet daemon
> >>>> /bin/sh: can't access tty; job control turned off
> >>>> / # mmcblk0: mmc0:0d93 SH256 249856KiB
> >>>> mmcblk0: p1
> >>>>
> >>>> on the file system I can see:
> >>>> /lib/modules/2.6.19-hh9/modules.dep
> >>>> but no
> >>>> /lib/modules/2.6.19-hh10
> >>>>
> >>>> hope this lets you build a new image asap!
> >>>>
> >>>> ta ta
> >>>>
> >>>> Jake

-- 
Patrick Steiner | patrick.steiner_at_a1.net
ICQ: 128261350
WWW: http://helmsdeep.homelinux.net/~pat
 
working on (tux4u.skynet):
Fedora Core release 6 (Zod)
GNU/Linux 2.6.19-1.2895.fc6