Loading PCI device when booting

[development]

Dear TinyCore ers,

I make a multi serial port PCI driver in tcem module and place in tce directory.
After booting, I can find my new file in modules directory and the device found with lspci, but I can't find the module with lsmod.
When manually insmod, the device appear in /proc/tty/driver, but can't find multi serial port in /dev/ttyXX.
How to load the PCI modules and create /dev/ttyXX automatically when booting ?
Thanks in advanced for your response.

Regards.
   

[^thehatsrule^]

You'll need to modprobe it (or insmod).

You can add the command to system startup (ie in /opt/bootlocal.sh)
or if you prefer that the extension to handle it, add an executable post-loading script (in /usr/local/tce.installed/pkgname)

[development]

Thanks I will try it.

[development]

I just wondering, How usbserial-2.6.26.tcem can work nicely without scripting ?
Can It working also in multiport serial PCi also ?

[^thehatsrule^]

depmod is executed when it's done.

Where did you place your module(s)?  Afaik somewhere like /lib/modules/`uname -r`/kernel.tclocal is ideal

[development]

It's very nice talking to this forum. Thanks to all moderators and participant that give good and reponsive information.

Altought the module already loaded with bootlocal.sh ,  I still can't get serial device /dev/ttyXX appears.
If we place the modules in /lib/modules/`uname -r`/kernel.tclocal. What's the different with /lib/modules/`uname -r`/kernel ?

[^thehatsrule^]

Are you trying to attach a device to it?  For example, you might need to edit /etc/inittab (and use something other than rungetty - iirc it does not recommend serial use).  This would require a remaster though.

The difference probably won't matter if modprobing already works.  Having the modules in kernel.tclocal/ allows for tclocal persistency, whereas kernel/ will just typically be on ramdisk.

[development]

I attached tty to a serial device, with my own software.
Ok I see, I know the different purposes between those kernel location.
By the way, my question mostly because my limitation understanding in Linux.
What's linux distro has similiarity configuration with tinycore ? Maybe better I must learn from there before exploring tinycore.

Best Regards.

[^thehatsrule^]

Ah, so if you want it to run automatically I guess you could add your software's command to the same script... after the modprobe line.  You might need to add a sleep statement or something similar if the device isn't recognized right away though.

TC specific configuration is probably unique (for the most part), ie tclocal

[development]

Yes, since /dev is non persistance , I must make a script with mknod to create /dev/ttyXX every time at booting. Is it correct ?
But It didn't happend if we use USB serial, that automatically create /dev/ttyUSB when plugin or booting.

[^thehatsrule^]

I thought serial devices could be accessed from /dev/ttyS[0-3] ? (they are currently in TC)

If you need to use mknod, you could either add it to the start of a script, or remaster TC with the file already in it.

[development]

Ok Thanks.

[roberts]

Many ways to accomplish. Everything in unix is a file.
You can include it in a backup and not have to re-create it upon each boot.
Either way.

[development]

After recompiling the kernel, I can found my multiport ttyS device, automatically, since udev working for me.
There are limitation in kernel configuration, the default maximum number is only 4 ports. I change to the number of my serial port and when booting all 33 serial port detected and created /dev/ttySxx automatically .
Thanks for you kind to assist me.

Regards.

[^thehatsrule^]

Good to hear that you've gotten it to work.  I'm just curious though, what are you using that requires 33 serial ports?