nls_base neither in kernel nor has a package i the x-wrt build

[GoogleCodeExporter]

What steps will reproduce the problem?
1. # opkg  update
2. # opkg -conf /etc/opkg.conf install kmod-fs-cifs
3. # opkg -V3 -conf /etc/opkg.conf install mount-utils
4. # insmod cifs

What is the expected output? What do you see instead?

Don't know expect output but get back :
#insmod cifs
insmod: unresolved symbol load_nls

What version of the product are you using? On what operating system and web
browser?

Firmware             OpenWrt Kamikaze - With X-Wrt Extensions 8.09
Kernel        Linux 2.4.35.4 #12 Wed Feb 18 12:17:45 CST 2009
MAC        
Device       Linksys WRT54G/GS/GL
Board       Broadcom BCM5352 chip rev 0
Username        

Web mgt. console        Webif²
Version      r4710 

As issue occur in ssh on the router this is not related to the workstation

Please provide any additional info below.

SUMMARY of likely origin : the nls_base is now compiled in the kernel and
not as a package, but the build did neither build it in the kernel nor a
package nls_base. This seams to be a x-wrt issue and not a openwrt issue

more details in forum post : 
http://forum.x-wrt.org/index.php/topic,1223.0.html

When searching on news and bug tracker this seams to be an issue very much
located on x-wrt, other claims it's not openwrt.
https://dev.openwrt.org/ticket/4772
https://dev.openwrt.org/ticket/4611 

Original issue reported on code.google.com by yves.gar...@gmail.com on 9 Apr 2009 at 7:24

[GoogleCodeExporter]

Well, I can only confirm it. The NLS support is not built-in in the X-Wrt image.
I have no idea why. The kernel default configs in the buildroot are several 
months
old without a change in that area.

The list of symbols in "Linux version 2.4.35.4 (buildbot@travis-pc.lan) (gcc 
version
3.4.6 (OpenWrt-2.0)) #6 Wed Feb 18 12:05:31 CST 2009" is:
...
devfs_register_tape
tty_unregister_devfs
...

The list of symbols in a properly built kernel is:
...
devfs_register_tape
utf8_wcstombs
utf8_wctomb
utf8_mbstowcs
utf8_mbtowc
load_nls_default
load_nls
unload_nls
unregister_nls
register_nls
tty_unregister_devfs
...

The brcm-2.4 images must be rebuilt.

Original comment by lubekgc@gmail.com on 10 Apr 2009 at 2:57

• Added labels: Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

you may have a look to 
https://dev.openwrt.org/changeset/10712 

other mention that there build don't have issues due to changes and patch that
contains this : 

+CONFIG_PACKAGE_kmod-nls-base=y
+# CONFIG_PACKAGE_kmod-nls-cp1250 is not set
+# CONFIG_PACKAGE_kmod-nls-cp1251 is not set
+CONFIG_PACKAGE_kmod-nls-cp437=y
+# CONFIG_PACKAGE_kmod-nls-cp850 is not set
+# CONFIG_PACKAGE_kmod-nls-iso8859-1 is not set

Do you have an idea of when the image would be rebuild ??

Original comment by yves.gar...@gmail.com on 10 Apr 2009 at 5:27

[GoogleCodeExporter]

I am currently looking into the issue.

Original comment by kemen04@gmail.com on 13 Apr 2009 at 8:17

[GoogleCodeExporter]

I'm trying to build openwrt from svn 8.09 branch and get the same problem with 
8.09, r15991. I have to build 
kernel myself because I'm running D-Link DIR-320 (need special kernel options 
to run). Cannot find solution 
yet.

Original comment by troex@fury.scancode.ru on 22 May 2009 at 5:29

[GoogleCodeExporter]

Basically you need to build all packages for the current target in the basic
buildroot to get a properly built kernel (similar to a release one in features).
Switching off some packages chained to kernel modules results in a kernel 
missing
just these chained parts. It may be handy when you do not need these parts or 
you are
targeting a smaller kernel.
Because it is not documented anywhere, it is very likely that many users 
building
their own kernels fail the same way.
Ask in the OpenWrt forum if you need more information.

I am closing the issue as the X-Wrt build was fixed.

Original comment by lubekgc@gmail.com on 25 May 2009 at 7:19

• Changed state: Verified