vlan didn't work

[Shuro]

Hello, on Tiny Core v3.0 vlan is included, but useless because in the kernel is this configured "# CONFIG_VLAN_8021Q is not set" and there is no 8021q module.

[curaga]

vconfig was enabled in busybox before, in 2.x, as well. Good point though.

[Shuro]

Thanks, i hope this is fixed soon...for now i build my own kernel.

[curaga]

Why not just build the module, and submit an extension?

[Shuro]

Iam new and i dont know how to submit an extension, but i made the module :-)

Hope that this helps.

--EDIT--

Okay, cnew problems, when i try to load the module with modprobe it says:

Code: [Select]

modprobe: can't load module 8021q (kernel/net/8021q/8021q.ko.gz): unknown symbol in module, or unknown parameter
dmesg give me more info:

Code: [Select]

8021q: Unknown symbol vlan_dev_vlan_id
hope some one can help.

[Juanito]

See the FAQ on extension submission:

http://wiki.tinycorelinux.com/tiki-view_faq.php?faqId=3#q5

[Juanito]

modprobe: can't load module 8021q (kernel/net/8021q/8021q.ko.gz): unknown symbol in module, or unknown parameter

This often means that the module depends on another module that is not loaded nor loadable.

Does "modinfo 8021q" show any missing deps? Did you do "depmod -a" to be sure the modules list was updated (tce-load would do this anyway)? Is your new module in the correct "tc location" for modules (see the .list file for any current module extensions to see where to put your module)?

[Shuro]

okay, i didn't changed anything...now modprobe 8021q works & vlan works too.

modinfo 8021q says:

Code: [Select]

filename: kernel/net/8021q/8021q.ko.gz
license: GPL
vermagic: 2.6.33.3-tinycore SMP mod_unload 486
where i configure that tinycore load this module on startup?

[Juanito]

If you make a tcz extension out of the module and list that extension in onboot.lst, it will be loaded automatically on start-up - you can use cpanel/appsaudit to modify onboot.lst

[Shuro]

okay, thanks...but tinycore did not load that module by loading the extension, or?

[Juanito]

okay, thanks...but tinycore did not load that module by loading the extension, or?

Ah - it could be/probably is that udev did not recognise the need to load that module once the extension was loaded - in this case you can put "modprobe module_name" in bootlocal.sh

[curaga]

IIRC the kernel is lately getting smart enough to load non-hw modules when something tries to use them, ie vconfig in this case. Not sure if that works though, add a modprobe to be sure.