Where to build/install ADC module

[MTCAT]

Hi Rich,

When I ran "sudo depmod", nothing was echoed to screen, so hopefully that's normal.

But, when I ran "sudo start24dsi", I got the same error again,

Driver loading: 24dsi........
---->ERROR<----: module file does not exist: /usr/local/bin/24dsi.ko

Newbie question/comment, why in the "standard" install as per GSC is the "start" script in the same directory as the module "24dsi.ko" (/usr/src/linux/drivers/24dsi/driver), or is that not the actual module file that the start script loads ?, I know you said that we should not put 24dsi.ko in /usr/local/bin in our case.

Thanks,

David

[Rich]

Hi MTCAT
Ok, I see the problem.

Change this:

Code: [Select]

modprobe ${module_file}to this:

Code: [Select]

modprobe ${module_name}

[MTCAT]

Hi Rich,

Sorry to be such a pain, but still nothing, same result, no driver loaded when typing "lsmod", and I also ran "sudo depmod" followed by "sudo start24dsi" and still the same error.

Could this be it ? In the "standard" install, the directory is like /usr/src/linux/drivers/24dsi/driver

In our case, by "symmetry", we seem to be missing the driver directory, does that matter ?

In our case we have the module file located at

~/package/usr/local/lib/modules/2.6.33.3-tinycore/kernel/drivers/24dsi

Do we maybe need to add a "driver" directory underneath "24dsi" directory, and put 24dsi.ko there ?

Thanks,

David

[Rich]

Hi MTCAT
Make sure  squashfs-tools-4.x  is installed and run this:

Code: [Select]

unsquashfs -ll /etc/sysconfig/tcedir/optional/24dsi-2.6.33.3-tinycore-686.tcz > 24dsiList.txtAttach  24dsiList.txt  to your next post.

Then change the  modprobe  command to this:

Code: [Select]

modprobe 24dsi

[MTCAT]

Hi Rich,

Thanks, I'll give that a try tonight.

Just to be sure, regarding the modprobe command change, you mean for me to do that inside the start24dsi script ?, i.e., change

modprobe ${module_name}

to

modprobe 24dsi

Just want to make sure.

Thanks,

David

[Rich]

Hi MTCAT
Exactly.

But I would also like to see what winds up in  24dsiList.txt  from the other command I listed.

[MTCAT]

Hi Rich,

I don't have a "tcedir" directory in /etc/sysconfig, just some files in there.

Thanks,

David

[Rich]

Hi MTCAT
Then run the command on whatever drive contains  tce/optional/24dsi-2.6.33.3-tinycore-686.tcz.

[Rich]

Hi MTCAT

I don't have a "tcedir" directory in /etc/sysconfig, just some files in there.

I forgot older versions of Tinycore don't have that link. This should work:

Code: [Select]

unsquashfs -ll `cat /opt/.tce_dir`/optional/24dsi-2.6.33.3-tinycore-686.tcz > 24dsiList.txtRemember, those are back ticks, not single quotes.

[MTCAT]

Hi Rich,

I ran "unsquashfs" on both /mnt/sdb1/tce/optional/24dsi-2.6.33.3-tinycore-686.tcz and then also with your fancier command, the output of the first "unsquashfs" is attached as 24dsiList.txt, and the output of your fancy command is 24dsiListv2.txt

Unfortunately, changing to "modprobe 24dsi" inside start24dsi didn't do anything for us, still no "24dsi" listed when typing "lsmod".

Hopefully you see something off in the output of unsquashfs.

Thanks,

David

[Rich]

Hi MTCAT
Does this return anything:

Code: [Select]

modinfo 24dsi
If not, how about if you run this first:

Code: [Select]

sudo /sbin/depmod -a

[MTCAT]

Hi Rich,

modinfo.txt contains the output of running "modinfo 24dsi" before doing anything special.

modinfo2.txt contains the output of running "modinfo 24dsi" after running "sudo /sbin/depmod -a".

I did run modinfo previously and was curious to see that both the 486 and 686 drivers are referred to as "486" in vermagic.

Thanks,

David

[MTCAT]

Hi Rich,

Sorry, forgot the attachments, here they are !

David

[Rich]

Hi MTCAT

... I did run modinfo previously and was curious to see that both the 486 and 686 drivers are referred to as "486" in vermagic.

If you compiled with:

Code: [Select]

-march=i486 -mtune-i686It generates 486 compatible code but orders instruction to take advantage of the pipelining in a 686.

So  modinfo finds it. See if  modprobe  knows where it is:

Code: [Select]

modprobe -l 24dsi
If it does, and  /usr/local/bin/start24dsi  contains  modprobe 24dsi , then I see no reason why this should not load the driver:

Code: [Select]

sudo start24dsi

[MTCAT]

Hi Rich,

Thanks for the explanation re: 486 and 686.

I ran "modprobe -l 24dsi" and I was returned with;

kernel.tclocal/drivers/24dsi/24dsi.ko

But, when I typed "sudo start24dsi", I get the usual error again,

Driver loading: 24dsi........
---->ERROR<----: module file does not exist: /usr/local/bin/24dsi.ko

However, did we try this already ?, when I simply type out "sudo modprobe 24dsi", that worked ! ! ?, I can do an "lsmod", and it's there now, "24dsi" is listed amongst the loaded modules !

But, I did put "modprobe 24dsi" into the start24dsi script in /home/tc/package/usr/local/bin, and then re-squashed the "package" directory, and put the .tcz file in /mnt/sdb1/tce/optional so, I'm not sure what I'm doing wrong....

Should I maybe just change my bootlocal.sh ?, namely, remove

/usr/local/bin/start24dsi

and replace with

modprobe 24dsi

Would that work ?, or be an okay way of going about things ?

Thanks,

David