[Solved] TC3.8_4 Real Time Upgrade

[Rich]

Hi MTCAT
Do this:

Code: [Select]

cd /lib/modules/2.6.33.3-l1-rt19/build
ls -l > buildDir.txtAttach the file to your next post.

... Also attached a screenshot, why is there a "dot" before "/driver/24dsi.ko" ?

One of the make files is prepending the  driver  directory name with  ./.  The  ./  syntax means look for what follows in
the current directory.

Create a script called  ls  like this:

Code: [Select]

echo "echo This is not the command you are looking for." > ls
chmod 775 ls
If you execute  ls  you'll get a directory listing as expected.
If you execute  ./ls  you've told the OS to look for  ls  in the current directory.

[MTCAT]

Hi Rich,

Thanks for the help, I made the symbolic link as usual, "sudo ln -s /home/linux-2.6.33.3 /lib/modules/2.6.33.3-l1-rt19/build", but, when I try to "cd /lib/modules/2.6.33.3-l1-rt19/build" I can't do so, I get returned;

sh: cd: can't cd to /lib/modules/2.6.33.3-l1-rt19/build

I tried this both as regular user and root with the same result as above.

Inside /lib/modules/2.6.33-l1-rt19 the "build" link shows up as;

lrwxrwxrwx 1 root root  20 May 14 12:18 build -->/home/linux-2.6.33.3

So, not sure, the link is there but I can't use it for some reason ?

Thanks,

David

[Rich]

Hi MTCAT
What does this return:

Code: [Select]

ls -l /home/linux-2.6.33.3
Maybe that should be:

Code: [Select]

sudo ln -s /home/tc/linux-2.6.33.3 /lib/modules/2.6.33.3-l1-rt19/build

[MTCAT]

Hi Rich,

Thanks, you could be on to something, typing "ls -l /home/linux-2.6.33.3" I get

ls: cannot access /home/linux-2.6.33.3: No such file or directory

But, "ls -l /home/tc/linux-2.6.33.3", everything shows up, I'll try the new symbolic link including "tc" and see if that works !

Thanks,

David

[Rich]

Hi MTCAT
I've made this statement to others in the past, but I feel it bears repeating:
You are no longer in high school. Spelling counts. Punctuation counts. Capitalization counts.

[MTCAT]

Thank you so much Rich and Juanito, that worked !, some progress, I was using the wrong path in the symbolic link, I think (hope) it should be good now, I think I just need to change "insmod" command in the "start" script with "modprobe" and hopefully that will work 100 percent.

After doing the symbolic link with the right path, I can now build the 24dsi.ko module (awesome !) in the "pre-built" RT kernel but it unfortunately fails to load the module with "insmod", I'm seeing now an error later on in the build process when it actually tries to load the module;

Driver loading: 24dsi ...
insmod: can't insert 'home/tc/24dsi.4.11.91.32.0/24dsi/./driver/24dsi.ko': Invalid module format
--->ERROR<---: Unable to load module.

Darn-it, have to go to work now, maybe I should do the "auto-load" modifications to the start script, which includes replacing insmod with modprobe, and then see if that loads the module okay ?

Thanks,

David

[Rich]

Hi MTCAT
What does this return:

Code: [Select]

modinfo /home/tc/24dsi.4.11.91.32.0/24dsi/./driver/24dsi.ko

[MTCAT]

Hi Rich and Juanito, sorry, I was thinking of "~" as "/home" only when in fact it's "/home/tc", my apologies for the extra hassle.

Thanks,

David

[MTCAT]

Hi Rich,

"modinfo /home/tc/24dsi.4.11.91.32.0/24dsi/./driver/24dsi.ko" just returns,

filename: /home/tc/24dsi.4.11.91.32.0/24dsi/./driver/24dsi.ko

Doesn't give any information about which kernel it was compiled for, I think modinfo is supposed to do that as well ?

Thanks,

David

[Rich]

Hi MTCAT
That suggests  /home/tc/24dsi.4.11.91.32.0/24dsi/./driver/24dsi.ko  does not exist.

[MTCAT]

Hi Rich,

Sorry, I missed ".linux" in the path,

"modinfo 'home/tc/24dsi.linux.4.11.91.32.0/24dsi/driver/24dsi.ko" returns,

filename: /home/tc/24dsi.linux.4.11.91.32.0/24dsi/driver/24dsi.ko
description: 24DSI driver 4.11.91.32.0
author: General Standards Corporation, www.generalstandards.com
license: GPL
vermagic: 2.6.33.3-rt19 SMP preempt mod_unload 486
depends:

That's odd how vermagic shows "2.6.33.3-rt19" when "uname -r" returns "2.6.33.3-l1-rt19"

Sorry, I have to go to work darn-it, but will check on the posts from there, and can continue to (hopefully) finish this off tonight !

Thanks again for all the help.

David

[Rich]

Hi MTCAT

... That's odd how vermagic shows "2.6.33.3-rt19" when "uname -r" returns "2.6.33.3-l1-rt19" ...

That's also why it returns  Invalid module format.

[MTCAT]

Hi Rich,

Type corrected below in modinfo path, sorry again, that's a lot of sorry's for one morning !

"modinfo /home/tc/24dsi.linux.4.11.91.32.0/24dsi/driver/24dsi.ko" returns,

filename: /home/tc/24dsi.linux.4.11.91.32.0/24dsi/driver/24dsi.ko
description: 24DSI driver 4.11.91.32.0
author: General Standards Corporation, www.generalstandards.com
license: GPL
vermagic: 2.6.33.3-rt19 SMP preempt mod_unload 486
depends:

That's odd how vermagic shows "2.6.33.3-rt19" when "uname -r" returns "2.6.33.3-l1-rt19"

Sorry, I have to go to work darn-it, but will check on the posts from there, and can continue to (hopefully) finish this off tonight !

Thanks again for all the help.

David

[MTCAT]

Hi Rich,

Do you have any ideas why the GSC "start" script is seeing a different kernel version ?

As I see it, I have maybe two options;

1) Try inserting 24dsi.ko on the pre-built kernel again (2.6.33.3-l1-rt19) but using  modprobe with --force-vermagic option ?, reading up on that this morning, to tell modprobe to ignore kernel string mismatch ? Seems a bit disappointing to have to do that though ?

2) Try to make the DIY RT kernel (2.6.33.3-rt19-tinycore) behave properly as it already can build and insert the 24dsi.ko module properly, but the install has other issues still.

With respect to number (2), I don't know if you have the time to look through my "recipe" for the DIY RT kernel build (see reply 119), I'm pretty sure I used the wrong config file, so maybe that explains all the weirdness right off the bat, but, I'm wondering if you see any other mistakes in that list....I could try doing the DIY RT kernel again this weekend and see if we can get a better result ?

What do you think ?

Thanks,

David

[Rich]

Hi MTCAT
What does this return:

Code: [Select]

cat /lib/modules/2.6.33.3-l1-rt19/build/include/generated/utsrelease.h