G'Day,

I'm wrestling with an embedded system, and have a slight problem with trying to run thttpd on it. When I use the factory (2.4) kernel on the board, I am able to run most aspects of my setup fine: thttpd runs, etc. When I switch to the 2.6 kernel I compiled, though, thttpd doesn't seem to work any more. It runs, but when I go to another system on the network, I cannot load any pages. It seems fairly obvious that the kernel I compiled is lacking options, but I cannot find anywhere exactly what network options are required for running a web server. I can ping the board, and it's file system is currently an NFS share, so it obviously has bare minimum network options. I'm probably only missing something small

Any suggestions would be most appreciated.

Those are the only things I can think of you would need: basic networking. I assume you don't have any sort of firewall, of course. Have you tried using a text-mode browser on it to contact localhost?

Thanks for the reply.

I had initially thought it should work with just the basic networking components, and now having that confirmed leaves me even more confused than before. As you assume, there is no firewall (at the moment there is no need), and it does work with the 2.4 kernel (other than changing from 2.4 to 2.6, there's no change to the system between when it is working and not working). Taking your suggestion, I decided to try putting Lynx onto the board and test things out, but it was starting to take too long (the number of compile errors I needed to address just kept on mounting), so I gave up on the idea. In the end, I keep coming back to how to works when I downgrade the kernel: that is what has me stumped!

Well, can you check if the port seems to be open? Checking perhaps with netstat, and telnetting to the port, what happens?

Ha, I had actually just thought of the same thing! I came to post that I ran nmap to check the board out. When I use the 2.4 kernel, I see only port 80 open; when I do the same thing with the 2.6 kernel all ports are closed. That seems to be the problem: obviously it cannot serve pages if the port is closed. The next step is to work out why the heck that is the case though. I'm going to check if I enabled something stupid in the kernel right now, though any further suggestions would be most welcome.

Off the top of my head, make sure the kernel has TCP/IP networking enabled. In fact, would you mind posting your entire kernel configuration? I'll look for anything blantantly obvious.

I wonder if we could be looking at a thttpd issue as well, though I've never used thttpd myself. I need to go check into that.

thttpd works with the 2.4 kernel, so I would imagine the problem is not there. I could be wrong, but that's my feeling. It works on my work PC (Ubuntu with 2.6) perfectly fine with the same /etc/thttpd.conf file too.

I've tried a little messing around so far, but nothing stood out to me. I'm adding and removing things semi-randomly now (I'm not removing anything I obviously need, not adding anything I obviously do not). Here's the original config I had been using up until now:

CONFIG_ARM=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_IOMAP=y

CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_BROKEN_ON_SMP=y

CONFIG_LOCALVERSION=""
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=14
CONFIG_HOTPLUG=y
CONFIG_KOBJECT_UEVENT=y
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SHMEM=y
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0

CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
CONFIG_KMOD=y

CONFIG_ARCH_OMAP=y

CONFIG_ARCH_OMAP16XX=y
CONFIG_ARCH_OMAP_OTG=y

CONFIG_MACH_OMAP_OSK=y

CONFIG_OMAP_MUX=y
CONFIG_OMAP_MUX_WARNINGS=y
CONFIG_OMAP_MPU_TIMER=y
CONFIG_OMAP_LL_DEBUG_UART1=y
CONFIG_OMAP_ARM_192MHZ=y

CONFIG_CPU_32=y
CONFIG_CPU_ARM926T=y
CONFIG_CPU_32v5=y
CONFIG_CPU_ABRT_EV5TJ=y
CONFIG_CPU_CACHE_VIVT=y
CONFIG_CPU_COPY_V4WB=y
CONFIG_CPU_TLB_V4WBI=y

CONFIG_CPU_DCACHE_WRITETHROUGH=y

CONFIG_ZBOOT_ROM_TEXT=0x0
CONFIG_ZBOOT_ROM_BSS=0x0

CONFIG_FPE_NWFPE=y
CONFIG_BINFMT_ELF=y

CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_PM=y
CONFIG_CMDLINE="console=ttyS0,115200n8 noinitrd ip=10.0.0.13:10.0.0.12:10.0.0.2:255.0.0.0sk:eth0ff root=/dev/nfs rw nfsroot=10.0.0.12:/data/rootfs2.6,nolock mem=32M"
CONFIG_ALIGNMENT_TRAP=y

CONFIG_MTD=y
CONFIG_MTD_PARTITIONS=y
CONFIG_MTD_CMDLINE_PARTS=y

CONFIG_MTD_CHAR=y
CONFIG_MTD_BLOCK=y

CONFIG_MTD_CFI=y
CONFIG_MTD_GEN_PROBE=y
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
CONFIG_MTD_CFI_INTELEXT=y
CONFIG_MTD_CFI_UTIL=y

CONFIG_MTD_OMAP_NORv2=y

CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=8192
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""

CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y

CONFIG_NET=y

CONFIG_PACKET=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_IP_PNP_BOOTP=y
CONFIG_IP_TCPDIAG=y

CONFIG_NETDEVICES=y

CONFIG_NET_ETHERNET=y
CONFIG_MII=y
CONFIG_SMC91X=y

CONFIG_PPP=y
CONFIG_PPP_MULTILINK=y

CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y

CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_SG=y

CONFIG_INPUT=y

CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_EVDEV=y

CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_SERPORT=y

CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_OMAP=y
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_OMAP=y

CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y

CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_NR_UARTS=4

CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256

CONFIG_I2C=y
CONFIG_I2C_CHARDEV=y

CONFIG_I2C_OMAP=y

CONFIG_TPS65010=y

CONFIG_EXT2_FS=y

CONFIG_ROMFS_FS=y
CONFIG_DNOTIFY=y
CONFIG_AUTOFS_FS=y
CONFIG_AUTOFS4_FS=y

CONFIG_FAT_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"

CONFIG_PROC_FS=y
CONFIG_SYSFS=y
CONFIG_RAMFS=y

CONFIG_JFFS2_FS=y
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_JFFS2_ZLIB=y
CONFIG_JFFS2_RTIME=y

CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_ROOT_NFS=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_SUNRPC=y

CONFIG_PARTITION_ADVANCED=y
CONFIG_MSDOS_PARTITION=y

CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_ISO8859_1=y

CONFIG_FB=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_OMAP=y
CONFIG_FB_OMAP_INTERNAL_LCDC=y
CONFIG_FB_OMAP_DMA_TUNE=y

CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FONTS=y
CONFIG_FONT_8x8=y

CONFIG_LOGO=y
CONFIG_LOGO_LINUX_CLUT224=y

CONFIG_USB=y

CONFIG_USB_DEVICEFS=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y

CONFIG_USB_OHCI_HCD=y

CONFIG_USB_STORAGE=y

CONFIG_OMAP_UWIRE=y

CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_FRAME_POINTER=y

CONFIG_CRC32=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y

Thanks!

Do you use the same CONFIG_CMDLINE on 2.4?

And, for my own curiousity, what kind of hardware are you working with?

Also, I've been trying to get nfsroot to work on my own machine, but that's a whole 'nother issue.

I did not write the 2.4 kernel, and have not yet been able to find out what the settings in that were (therein lies half my headache), however that CONFIG_CMDLINE is the same as I use in the bootloader for both kernels so I know it is correct.

The hardware is a TI OMAP5912 Starter Kit. A little board sitting next to this PC It's a nice piece of work, I must say, and operating an embedded system via minicom has been fun too.

NFSROOT is working like a charm here (well, now it is - that took a day or two). I would not have a root filesystem without it. Well, I suppose I could flash it, but given how often I make changes that is not a good option at the moment, so I shall leave that for when the contents become a little more defined.

I am impressed. If you don't mind me asking, where did you get the starter kit? I've been looking to play with embedded hardware, but as cheaply as possible (being a college student).

On another note, I think my NFSROOT problems are due to using a PCMCIA NIC. Ugh.

Anyway, I'm looking into the thttpd docs to see if I can see any kernel issues that could be related here.

What kind of logging does thttpd do? And what does its logs say?

I have solved it! Sort of...

I have been adding anything that looked likely to the kernel, and unfortunately bloated it a bit (I will need to trim it back later), but it now works. The trouble is, because I was adding several things at a time, I'm not 100% sure what fixed it yet. I suspect it was adding CONFIG_IPV6 though - that's my gut feeling, rather than substantiated by any fact. Thanks for all the help, Matir, and for the time you have put in for me.

As to the OSK, I didn't buy it - my boss did. I checked up for you, and the product information page is here:
http://focus.ti.com/docs/general/spl...ble+OT+5912osk

Perhaps still out of your price range - when I was a student I would not have easily budgeted that much - but I hope this helps somewhat still. It has been a lot of fun to work with, especially since I wanted to play with embedded hardware as a student too

Yeah, that is a tad much. I wish I could find myself some cheap ARM or similar system... or even an embedded x86 system. It would be fun to be able to run a hidden USB webcam or similar off one

If you know of any others, I'd appreciate you letting me know.

Also, if/when you do narrow down whether or not it is IPV6, I'd appreciate knowing. If thttpd REQUIRES IPv6, that could be a bug, or just something that should be well documented.

It's been great working with you!