[beagleboard] Cannot access ttyO2

Please post your full serial boot log and .config used when building
(please use pastebin.com).. I've been shipping v3.6.x on both
Beagle's (C4/xM) and it's been booting fine..

Regards,

Hello Robert

it is weekend, so i will post the required files on Monday when i am back to work.
Can you send me, if you please, the Config file that you use for building Linux together with a zipped file containing the required files that should be placed on the bootable SD card (MLO, u-boot.bin, uImage, rootfs)

I would appreciate that. I will keep you informed and will post the required files on Monday.

Have a nice weekend.

Hello Robert

it is weekend, so i will post the required files on Monday when i am back to
work.
Can you send me, if you please, the Config file that you use for building

kernel config:
https://github.com/RobertCNelson/stable-kernel/blob/v3.6.x/patches/defconfig
(or)
https://github.com/beagleboard/kernel/blob/beagleboard-3.6/configs/beagleboard_defconfig

Linux together with a zipped file containing the required files that should
be placed on the bootable SD card (MLO, u-boot.bin, uImage, rootfs)

http://elinux.org/BeagleBoardUbuntu#Demo_Image
http://elinux.org/BeagleBoardDebian#Demo_Image

Regards,

Thanks Robert

I am gonna try it on Monday and I will let you know if I succeed. If not, i will show you the log file of my booting pricess.

Regards

Hello Robert

I am trying to boot Linux 3.6.7 on Beagle-xM, and get the error:
waiting for root device /dev/mmcblk0p2

here is the log file of my booting process:
http://pastebin.com/06NWHigH

Regards

Ahh, that one:

omap_hsmmc omap_hsmmc.0: Failed to get debounce clk
omap_hsmmc omap_hsmmc.0: unable to obtain RX DMA engine channel 62

(see next time make sure to post your bootlog/config. :wink:

It's pretty easy, the hsmmc driver was converted to using the generic
dma, however the Kconfig's do not enable it yet by default...

https://github.com/RobertCNelson/stable-kernel/blob/v3.6.x/patches/defconfig#L3795

Infact i was using config file which is different than the ones posted on your website.
using the config found on your website, and building linux causes this error during the build process:

include/linux/dynamic_debug.h: In function ‘ddebug_dyndbg_module_param_cb’:
include/linux/dynamic_debug.h:111:2: error: implicit declaration of function ‘strstr’ [-Werror=implicit-function-declaration]

I do not know if it is good idea to comment this thing out from the kernel source, or is there any configuration which avoids this from being built during the building process.

Regards

Infact i was using config file which is different than the ones posted on
your website.
using the config found on your website, and building linux causes this error
during the build process:

include/linux/dynamic_debug.h: In function 'ddebug_dyndbg_module_param_cb':
include/linux/dynamic_debug.h:111:2: error: implicit declaration of function
'strstr' [-Werror=implicit-function-declaration]

Yeah, I don't get that error:
http://rcn-ee.homeip.net:8080/job/github_stable-kernel/22/consoleText

So either fixed it in my v3.6.x tree, or your gcc is bugged...

I do not know if it is good idea to comment this thing out from the kernel
source, or is there any configuration which avoids this from being built
during the building process.

Or "you" could just enable this missing kernel configs...

Your choice...

Regards,

It's this patch:
https://github.com/RobertCNelson/stable-kernel/blob/v3.6.x/patches/mainline-fixes/0001-arm-add-definition-of-strstr-to-decompress.c.patch

needed since i have this config enabled: CONFIG_KERNEL_XZ=y

Regards,

Thanks a lot.
I appreciate your help.
I am gonna try it.

Regards

Hello Robert
the patch that you sent to me did not solve the problem. so I changed the configuration and used Gzip instead of XZ and this solved the problem.
Now I get another problem:

Building modules, stage 2.
MODPOST 1809 modules
ERROR: “read_current_timer” [drivers/video/udlfb.ko] undefined!
ERROR: “read_current_timer” [drivers/gpu/drm/udl/udl.ko] undefined!
ERROR: “read_current_timer” [crypto/tcrypt.ko] undefined!
WARNING: modpost: Found 1 section mismatch(es).
To see full details build your kernel with:
‘make CONFIG_DEBUG_SECTION_MISMATCH=y’

did you enconter or solved such issue?

Regards

I see you added a patch that solves this issue, I am gonna try it.

Robert

I finally succeeded and have my image running.
No words that can express my thanks for you.
thank you a lot and I would be glad if you accept that i contact you again in case of any problems.

Regards

Hello Robert
I succeeded to boot linux 3.6.8 on Beagleboard-xM. My aim is to build RT-linux. for this i used the rt-19 patch.
booting the beagleboard with rt patch gets stuck at this point:
http://pastebin.com/A9gk4c8e

do you have an idea what could be the issue?
Regards

Robert
for the new configuration that you put online, the 3.6.8.config for beagleboard, I think these 3 options should be there:
CONFIG_UEVENT_HELPER_PATH=""
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y

otherwise, there will be the problem: cannot open ttyO2

Regards

Ah? my "config"? are you sure, since:

https://github.com/RobertCNelson/stable-kernel/blob/v3.6.x/patches/defconfig#L1317

I've actually had that enabled by default since the start of Ubuntu
Lucid's development cycle.. (late 2009)

Regards,

the 3.6.8.config
https://github.com/RobertCNelson/stable-kernel/blob/v3.6.x/patches/ref_omap2plus_defconfig

on this line:
https://github.com/RobertCNelson/stable-kernel/blob/v3.6.x/patches/ref_omap2plus_defconfig#L763

That's not my config. :wink: (hint: ref = reference)

It's completely auto-generated in the script via:
(where: config=omap2plus_defconfig)

  make ARCH=arm CROSS_COMPILE=${CC} ${config}
  cp -v .config ${DIR}/patches/ref_${config}

To more easily compare the upstream:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob;f=arch/arm/configs/omap2plus_defconfig;hb=HEAD

With my config:
https://github.com/RobertCNelson/stable-kernel/blob/v3.6.x/patches/defconfig

Which is the "ONLY" config I ever mentioned in this email thread...

Regards,

yes sorry. just in case someone asks the same thing.
do you have time to look at my message about the RT patch problem?