On Tue, Jul 31, 2012 at 03:55:08AM +0000, [email protected] wrote:
> Well, If I hit a key to stop the boot then execute printenv: it shows me this:
>
> et: No ethernet found.
> Hit any key to stop autoboot: 0
> Overo # printenv
> bootcmd=if mmc init; then if run loadbootscript; then run bootscript; else if
> run loaduimage; then run mmcboot; else run nandboot; fi; fi; else run
> nandboot;
> fi
> bootdelay=5
> baudrate=115200
> loadaddr=0x82000000
> console=ttyS2,115200n8
^^^^^^
Try with ttyO2 instead for kernels >2.6.36:
setenv console ttyO2,115200n8
saveenv
--
Denys
> mpurate=500
> vram=12M
> dvimode=1024x768MR-16@60
> defaultdisplay=dvi
> mmcroot=/dev/mmcblk0p2 rw
> mmcrootfstype=ext3 rootwait
> nandroot=/dev/mtdblock4 rw
> nandrootfstype=jffs2
> mmcargs=setenv bootargs console=${console} mpurate=${mpurate} vram=${vram}
> omapfb.mode=dvi:${dvimode} omapfb.debug=y omapdss.def_disp=${defaultdisplay}
> root=
> ${mmcroot} rootfstype=${mmcrootfstype}
> nandargs=setenv bootargs console=${console} mpurate=${mpurate} vram=${vram}
> omapfb.mode=dvi:${dvimode} omapfb.debug=y omapdss.def_disp=${defaultdisplay}
> root
> =${nandroot} rootfstype=${nandrootfstype}
> loadbootscript=fatload mmc 0 ${loadaddr} boot.scr
> bootscript=echo Running bootscript from mmc ...; source ${loadaddr}
> loaduimage=fatload mmc 0 ${loadaddr} uImage
> mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}
> nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr}
> 280000 400000; bootm ${loadaddr}
> stdin=serial
> stdout=serial
> stderr=serial
> dieid#=1eba00029ff80000016842c91601702f
>
> Environment size: 1209/131068 bytes
>
> - Josh
>
>
> On Jul 30, 2012, at 8:51 PM, ext Denys Dmytriyenko wrote:
>
> > On Tue, Jul 31, 2012 at 12:31:10AM +0000, [email protected] wrote:
> >> Incidentally, I don't get all of the kernel boot messages when my gumstix
> >> boots. It says
> >>
> >> Starting kernel ...
> >>
> >> Uncompressing Linux... done, booting the kernel.
> >>
> >> Yocto (Built by Poky 7.0) 1.2+snapshot-20120730 overo ttyO2
> >>
> >> overo login:
> >>
> >>
> >> And then I'm at the login prompt. I'm assuming there is some boot setting
> >> which controls this? All of the messages are showing up in
> >> /var/log/messages, however.
> >
> > What's your "bootargs" variable in u-boot? Does it contain "quiet"? Does it
> > have the proper console settings?
> >
> > --
> > Denys
> >
> >
> >> On Jul 30, 2012, at 12:42 PM, ext Denys Dmytriyenko wrote:
> >>
> >>> On Mon, Jul 30, 2012 at 07:10:23PM +0000, [email protected]
> >>> wrote:
> >>>> Hmm. I don't see to have depmod installed. Perhaps that is part of my
> >>>> problem. What package would I need to add to the minimal-core-image to
> >>>> get
> >>>> that?
> >>>
> >>> Josh,
> >>>
> >>> core-image-minimal uses busybox for tools like insmod and modprobe. The
> >>> default configuration for busybox does not have depmod enabled. As of
> >>> module-init-tools, they are being built, but not installed on the
> >>> filesystem.
> >>> So, you can either modify busybox config to enable depmod, or add
> >>> module-init-tools-depmod package to your filesystem. The new way is to
> >>> use
> >>> kmod, which is available in oe-core master, or meta-oe in denzil. But
> >>> oe-core
> >>> master setup is broken for me at the moment, so I can't verify that kmod
> >>> is
> >>> included. At least it's not listed in the image/task...
> >>>
> >>> Denys
> >>>
> >>>
> >>>> On Jul 30, 2012, at 1:07 AM, ext Enrico wrote:
> >>>>
> >>>>> On Sat, Jul 28, 2012 at 9:30 PM, <[email protected]> wrote:
> >>>>>> This does work. When I boot the wpa stuff is included but I still
> >>>>>> don't have a network driver loaded. If I include the built
> >>>>>> modules-3.2.19-r0-overo.tgz in my rootfs I can cd into the directory
> >>>>>> with all of the modules. However insmod libertas.ko fails with
> >>>>>>
> >>>>>> insmod: can't insert 'libertas_tf_usb.ko': unknown symbol in
> >>>>>> module, or unknown parameter
> >>>>>>
> >>>>>> and modprobe fails with
> >>>>>>
> >>>>>> modprobe: module libertas not found in modules.dep
> >>>>>>
> >>>>>>
> >>>>>> So, what should I do to make sure the libertas module is compiled
> >>>>>> correctly, included in my kernel, and then actually used at runtime?
> >>>>>
> >>>>> try with "depmod -a" (this must be done only once after you untar the
> >>>>> modules) before modprobe libertas.
> >>>>>
> >>>>> I am not sure but i think it was "modprobe libertas_sdio", try that
> >>>>> too. And of course you will need the libertas firmware
> >>>>> (sd8686....bin).
> >>>>>
> >>>>> Enrico
> >>>>
> >>>> _______________________________________________
> >>>> meta-ti mailing list
> >>>> [email protected]
> >>>> https://lists.yoctoproject.org/listinfo/meta-ti
> >>
> >> _______________________________________________
> >> meta-ti mailing list
> >> [email protected]
> >> https://lists.yoctoproject.org/listinfo/meta-ti
> >>
>
_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti