Topic: Speedport W500V runs Kamikaze r8025

The content of this topic has been archived on 24 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Page 1 of 1

Post #1

abra

22 Jul 2007, 14:20

Hi !

There i've prepared a OpenWrt image for the famous Speedport W500V (and perhaps the W500, 500V, please report) . It is just a proof of concept but it works.
The image can be downloaded from here.

What I ve done and why:
1. Prepared a Kernel (2.6.8.1) with the original firmware build suite from the telekom.
1.a) patsched out some bugs found in 2.6.8.1 release. (ip_dst_cache cleanup)
2. Prepared a Kamikaze tar.gz-filesystem image with my needed options.
3. Merged the t-kom binary only utils and build kamikaze filesystem.
4. Build an own /etc/preinit to have a failsafe mode.
5. Build with the kernel and the filesystem the new firmware image using the broadcom binary-only tools, because the kamikaze tools don't produce the right format.

In 1. I adopted the /drivers/mtd/maps/bcrm963xx.c driver to the old kernel, with some small patching e.g. added mini_fo.
Also I must not enable QoS, VLAN and some other interesting options because this breaks the binary only modules for wireless lan, wan, dsl.
QoS and some other features extends struct sk_buff, which is used by the binary onley stuff and breaks it. (kernel panic random segfaults)

My image has no support for VoIP, because of space.

This was done by hand.

cya
--- Edits:
- changed URL so every collected material vor the Speedport W500V is downloadable
- v2 works okay
- v3 has support for leds, but some times makes trouble, when loading atm modules
- v4 fixed some bugs. made led handling more complete, a small portal webinterface has been added

(Last edited by abra on 16 Jul 2008, 21:38)

Post #2

tekknokrat

5 Jan 2008, 15:12

Hi,

nice to see some work on w500v.
I think the breakage with qos and other parts are because of heavy changes in kernel since 2.6.8.
Can you explain why did the voip didn't work?

Post #3

tekknokrat

6 Jan 2008, 13:52

Yesterday I tried your image which looks promising to me.

Some Questions which burns in my mind:

Do you think the wl0 device could be controlled with the generic wireless-tools?
Do you think someone could change the adsl port in an eth0 port for using the box as an router?
What kind of hardware is the pot/voip part?

Post #4

abra

7 Jan 2008, 03:35

Holla, nice to see that some tries my work.

tekknokrat wrote:

nice to see some work on w500v.

It's no official openwrt work, it was just a try to get this route _useable_.

tekknokrat wrote:

I think the breakage with qos and other parts are because of heavy changes in kernel since 2.6.8.
Can you explain why did the voip didn't work?

The QoS does not work, because the telekom binary only kernel modules for the dsl, atm, ethernet and wlan controller begin to segfault when i enable QoS.

Voip did not work for two reasons, firstly i thought it is just problem of space in the flash. but i solved that.
Now it just segfaults, when started. strace says it doesn't like the openwrt uclibcxx.

tekknokrat wrote:

Yesterday I tried your image which looks promising to me.
Some Questions which burns in my mind:
Do you think the wl0 device could be controlled with the generic wireless-tools?
Do you think someone could change the adsl port in an eth0 port for using the box as an router?
What kind of hardware is the pot/voip part?

No the wl0 device is configured only via the supplies wl and nas tools.

The adsl port is an atm port you can configure it via adslctl and atmctl.
with br2864ctl you can create your ethernet if aftwerwards.

Just have look in /etc/init.d/nas0 and /etc/config/system

the voip part is undocumented broadcom crap.

btw i have put some scripts in /etc/init.d and /etc/rcS.d that are not openwrt standard, but make some things regarding dsl/ethernet/pppoe easier. just have a look and ask.

cya

Post #5

nbd

7 Jan 2008, 15:08

Hi guys,

sorry to say this, but I think that at the moment, working on the Broadcom 63xx platform is a complete waste of time.
Here's why:
- No driver sources
- Crappy driver binaries, locked into an old kernel
- *No* help, support or anything from Broadcom
- Frequent GPL violations on the platform, many of which seem to be caused by Broadcom themselves
Do you really want to reward Broadcom for such crappy behavior by giving them a usable development platform?

Let's look at the alternatives to BCM963xx:
- For TI AR7 we have open drivers and the port is making progress
- For Infineon Danube/Amazon we have open drivers and Infineon is even participating in OpenWrt development.

With open alternatives being available, why waste time helping Broadcom with their ugly mess they call software?
Maybe you won't agree with my choice, but I choose to spend my time on things that generate incentive for hardware
manufacturers to open up and release their drivers under a free license, instead of making it easier for them to
keep things the way they are.

comments/flames welcome.

- Felix

Post #6

abra

7 Jan 2008, 18:58

Hi !

nbd wrote:

sorry to say this, but I think that at the moment, working on the Broadcom 63xx platform is a complete waste of time.

You are right of course. It was just a triy to make this router useful.
Not only Broadcom makes crappy undocumented hardware, Telekom cripples it a bit mor.

Work has stopped already. I reached my goals: More control over the router + openvpn server and client + wireless access point.
I answer just to help a bit and fix bugs of my firmware as the time investment is not to large.

nbd wrote:

Here's why:
- No driver sources
- Crappy driver binaries, locked into an old kernel
- *No* help, support or anything from Broadcom
- Frequent GPL violations on the platform, many of which seem to be caused by Broadcom themselves
Do you really want to reward Broadcom for such crappy behavior by giving them a usable development platform?
Let's look at the alternatives to BCM963xx:
- For TI AR7 we have open drivers and the port is making progress
- For Infineon Danube/Amazon we have open drivers and Infineon is even participating in OpenWrt development.
With open alternatives being available, why waste time helping Broadcom with their ugly mess they call software?
Maybe you won't agree with my choice, but I choose to spend my time on things that generate incentive for hardware
manufacturers to open up and release their drivers under a free license, instead of making it easier for them to
keep things the way they are.

! you're quite right !

cya keep up your good work

Post #7

tekknokrat

13 Jan 2008, 17:45

@abra: thanks for your answer.
My provider doesnt use pppoe so I can't test your firmware in this way.
I now use it as an router and try to forget about voip ;-)

The adsl port is an atm port you can configure it via adslctl and atmctl.
with br2864ctl you can create your ethernet if aftwerwards.

Do you mean the port is usable for ethernet, too? Someone mentioned its only wired via the 2 solder joints for dsl

@nbd wrote:

sorry to say this, but I think that at the moment, working on the Broadcom 63xx platform is a complete waste of time.

I also agree with your oppinion.
Its really a waste of time trying to reach some goal with closed / nonconform utils!

Post #8

abra

14 Jan 2008, 08:28

Hi !

tekknokrat wrote:

@abra: thanks for your answer.
My provider doesnt use pppoe so I can't test your firmware in this way.
I now use it as an router and try to forget about voip ;-)
The adsl port is an atm port you can configure it via adslctl and atmctl.
with br2864ctl you can create your ethernet if aftwerwards.
Do you mean the port is usable for ethernet, too? Someone mentioned its only wired via the 2 solder joints for dsl.

The connector is only for DSL/ATM. What I meant ist, that you can extract an ethernet tunnel (Ethernet over ATM) from that port.

BTW What connection type do you have? And how do you use it as router? Wireless router?

cya

(Last edited by abra on 14 Jan 2008, 15:30)

Post #9

knurps

22 Jan 2008, 11:30

Hi i am new to kamikaze and just want to make some tryouts with my speedport w500v.

I have some problems that i get not solved right now and hope to get some help :-)

I can't change the ip of the br0 device from 192.168.1.1 in anything else except other ips in range 192.168.1.1-254. Adapt the iptable rules doesn't work for me.

General configuration with /etc/config/network doesn't work either the same for /etc/config/system. I had to create both files from sample config files but they seem to be ignored.

Maybe someone can provide a few general information about configuration.

Thx

Knurps

Post #10

abra

23 Jan 2008, 19:10

Hi !

knurps wrote:

Hi i am new to kamikaze and just want to make some tryouts with my speedport w500v.
I have some problems that i get not solved right now and hope to get some help :-)

Of course :)

knurps wrote:

I can't change the ip of the br0 device from 192.168.1.1 in anything else except other ips in range 192.168.1.1-254. Adapt the iptable rules doesn't work for me.
General configuration with /etc/config/network doesn't work either the same for /etc/config/system. I had to create both files from sample config files but they seem to be ignored.

What you have you done in detail? Changing /etc/config/system and after this try /etc/init.d/br0 restart or a reboot of the router should do.
And yes changing /etc/config/network is ignored. Why? Have a look at the end of this answer.

Concerning the firewall rules: Because I did it for my own testing, the FW has not the default OpenWrt-Firewall. It's using a self made script set called iptpf, written by me, but this is disabled by default. If you understand iptables have a look in /rom/etc/pf/rules/filter and /rom/etc/pf/rules/nat.

knurps wrote:

Maybe someone can provide a few general information about configuration.

The time I made this FW-image, I was new to kamikaze, too, because of that, I made some very specialised scripts and settings in /etc/init.d and /etc/config.
All you can configure with uci is in /etc/config/system.
Everything else lies in /etc/init.d

Scripts that should be started on boot-up are in /etc/rcS.d/S[0-9][0-9]*.

But ask more precise if you want a good answer.

cya

(Last edited by abra on 23 Jan 2008, 19:12)

Post #11

RobertD

18 May 2008, 19:41

Hi,

First of all a big Thanks on abra for this perfect Firmware.

I have flashed the Firmware (v3) on a W500V and it works perfect.
But i have 2 Problems.
Is it possible to compile the follow packages for this Plattform:
kmod-fs-cifs
kmod-loop

and in the ipkg.conf from this firmware is a old repro not available
(src snapshots http://downloads.openwrt.org/snapshots/ … /packages)

Sorry for my bad English, but i work on it to make it better.

Thanks a lot,
Robert.

(Last edited by RobertD on 22 May 2008, 18:25)

Post #12

RobertD

20 May 2008, 19:25

@ Update

i get compiled successful the cifs and loop modules.
But i have problems with mounting the swapfile:

root@openwrt:/lib/modules/2.6.8.1# lsmod | grep loop
loop                    9936  0

 losetup /dev/loop/0 /tmp/swap

root@openwrt:/dev/loop# losetup /dev/loop/0 /tmp/swap
root@openwrt:/dev/loop# swapon /dev/loop/0
swapon: /dev/loop/0: Function not implemented

Can anybody help me with this problem ?

I dont know what i can make to fix this Problem.

Must be rebuild the swap-uitls package ?
Must be rebuild the kernel-image ?

Robert

(Last edited by RobertD on 20 May 2008, 19:31)

Post #13

abraXxl

20 May 2008, 22:32

RobertD wrote:

@ Update
i get compiled successful the cifs and loop modules.
But i have problems with mounting the swapfile:

Fine,

RobertD wrote:

root@openwrt:/lib/modules/2.6.8.1# lsmod | grep loop
loop                    9936  0

 losetup /dev/loop/0 /tmp/swap

root@openwrt:/dev/loop# losetup /dev/loop/0 /tmp/swap
root@openwrt:/dev/loop# swapon /dev/loop/0
swapon: /dev/loop/0: Function not implemented

The loop device is ok, but the swap support is not in kernel, sorry i had no reason to enable it.

I think you have to recompile the kernel. with swap support. An the compile a new image (kernel + roorfs).
For that use the fsworks-archive in the download directory (link in first post now).
You need the kernel image and a tar of all non system directories from your current speedport rootfs.
Look at the Makefile to know whats happening.

If you have questions don't bother to ask.

g'f8 g'n8

abra

Post #14

RobertD

22 May 2008, 12:00

Hi abra,

Thanks for Reply

I use the t-com sources 1.37 to build the vmlinux, if itÂ´s created then i copied it to your folder (v3/kernel/linux/)
When i build the t-com kernel (i edit the kernel-config at /home/compil/firmware/t-com/bcm963xx_SpeedportW500V.01.37.v1L.300L01.V27_consumer/hostTools/scripts/defconfig-bcm.template).

The image will be created (make.log)

root@linux:/home/compil/firmware/bcm963xx_fs_kernel.v3.fsworks/v3# make PROFILE=96348GWV_DT
cp -a fs.src tmp/fs
hosttools/mkdev.sh tmp/fs
mknod: `tmp/fs/dev/initctl': File exists
mknod: `tmp/fs/dev/mem': File exists
mknod: `tmp/fs/dev/kmem': File exists
mknod: `tmp/fs/dev/null': File exists
mknod: `tmp/fs/dev/port': File exists
mknod: `tmp/fs/dev/zero': File exists
mknod: `tmp/fs/dev/random': File exists
mknod: `tmp/fs/dev/urandom': File exists
mknod: `tmp/fs/dev/ptyp0': File exists
mknod: `tmp/fs/dev/ptyp1': File exists
mknod: `tmp/fs/dev/ttyp0': File exists
mknod: `tmp/fs/dev/ttyp1': File exists
mknod: `tmp/fs/dev/tty0': File exists
mknod: `tmp/fs/dev/tty1': File exists
mknod: `tmp/fs/dev/ttyS0': File exists
mknod: `tmp/fs/dev/tty': File exists
mknod: `tmp/fs/dev/console': File exists
mknod: `tmp/fs/dev/ptmx': File exists
mknod: `tmp/fs/dev/ppp': File exists
mknod: `tmp/fs/dev/bcmatm0': File exists
mknod: `tmp/fs/dev/brcmboard': File exists
mknod: `tmp/fs/dev/bcmvdsl0': File exists
mknod: `tmp/fs/dev/bcmadsl0': File exists
mknod: `tmp/fs/dev/bcmaal20': File exists
mknod: `tmp/fs/dev/bcmles0': File exists
mknod: `tmp/fs/dev/bcm': File exists
mknod: `tmp/fs/dev/mtdblock0': File exists
mknod: `tmp/fs/dev/mtdblock1': File exists
mknod: `tmp/fs/dev/mtdblock2': File exists
mknod: `tmp/fs/dev/mtdblock3': File exists
mknod: `tmp/fs/dev/mtdblock4': File exists
mknod: `tmp/fs/dev/mtdblock5': File exists
mknod: `tmp/fs/dev/mtdblock6': File exists
mknod: `tmp/fs/dev/mtdblock7': File exists
mknod: `tmp/fs/dev/mtd0': File exists
mknod: `tmp/fs/dev/mtd1': File exists
mknod: `tmp/fs/dev/mtd2': File exists
mknod: `tmp/fs/dev/mtd3': File exists
mknod: `tmp/fs/dev/mtd4': File exists
mknod: `tmp/fs/dev/mtd5': File exists
mknod: `tmp/fs/dev/mtd6': File exists
mknod: `tmp/fs/dev/mtd7': File exists
mknod: `tmp/fs/dev/mtd0ro': File exists
mknod: `tmp/fs/dev/mtd1ro': File exists
mknod: `tmp/fs/dev/mtd2ro': File exists
mknod: `tmp/fs/dev/mtd3ro': File exists
mknod: `tmp/fs/dev/mtd4ro': File exists
mknod: `tmp/fs/dev/mtd5ro': File exists
mknod: `tmp/fs/dev/mtd6ro': File exists
mknod: `tmp/fs/dev/mtd7ro': File exists
ln: creating symbolic link `tmp/fs/dev/fd/fd': No such file or directory
rm -rf tmp/fs/lib/modules tmp/fs/linuxrc
moddir="`find -L kernel -name "2.*[0-9]" | tail -n 1`"; \
        kver="`basename $moddir`"; \
        mkdir -p "tmp/fs/lib/modules/$kver"; \
        find $moddir -name "*.ko" -exec cp {} "tmp/fs/lib/modules/$kver" \; \

hosttools/mksquashfs tmp/fs tmp/sqfs.img -noappend -be -lzma -no-fragments -noI
Creating big endian filesystem on tmp/sqfs.img, block size 65536.

Big endian filesystem, data block size 65536, uncompressed data, compressed metadata, no fragments
Filesystem size 3495.72 Kbytes (3.41 Mbytes)
        17.18% of uncompressed filesystem size (20344.66 Kbytes)
Inode table size 32639 bytes (31.87 Kbytes)
        100.00% of uncompressed inode table size (32639 bytes)
Directory table size 16608 bytes (16.22 Kbytes)
        100.00% of uncompressed directory table size (16608 bytes)
Number of duplicate files found 334
Number of inodes 1387
Number of files 698
Number of symbolic links  505
Number of device nodes 49
Number of fifo nodes 1
Number of socket nodes 0
Number of directories 134
Number of uids 2
        dx-operator (1000)
        root (0)
Number of gids 0
/opt/toolchains/uclibc-crosstools_gcc-3.4.2_uclibc-20050502/bin/mips-linux-uclibc-objcopy -O binary tmp/vmlinux tmp/vmlinux.bin
hosttools/cmplzma -k -2 tmp/vmlinux tmp/vmlinux.bin tmp/vmlinux.lz
Code text starts: textAddr=0x80010000  Program entry point: 0x801B0018,
Before compression: 1773701  After compression (level=2): 548305
Percent Compression = 69.09
hosttools/bcmImageBuilder \
                --output tmp/fs_kernel \
                --chip 6348 \
                --board "96348GW" \
                --blocksize 64 \
                --cfefile cfe.bin \
                --rootfsfile tmp/sqfs.img --kernelfile tmp/vmlinux.lz
bcmImageBuilder
        File tag size                 : 256
        Root filesystem image size    : 3579904
        Kernel image size             : 548317
        Combined image file size      : 4128477

hosttools/addvtoken tmp/fs_kernel bcm963xx_fs_kernel
addvtoken: Output file size = 4128497 with image crc = 0xe3ba3a7a
chmod 644 bcm963xx_fs_kernel

My new Problem is, the Device wont boot with this selfmade Image.
On the Device only lights the Leds power (green) and lan, not the adsl.
When i flased your image, the device boots (lights on ,power,lan,adsl) after few seconds you hear a "klick" and the device is over network available (ping).
But with my Image a dont hear the "Klick". I have no serial-cable attached on the device but i mean it cant find the rootfs ?

This is my first time with compiling a Firmware.
What i want to activate on the Kernel is (loop,cifs,tun,swap Support).

My Question are:
Is it possible that you can post your working kernel ".config"
Or better if you have time can you write me a Howto, what i must do to build a working firmware.

Thanks Robert.

(Last edited by RobertD on 25 May 2008, 16:26)

Post #15

RobertD

22 May 2008, 17:59

Another Question

I want to access this device over serial with your firmware.
i use Cutecom with the follow parameters:

Device: /dev/ttyUSB0
Parity: None
Boud rate: 115200
Data bits: 8
Stop bits: 1
Open for: [x] Reading [x] Writing

I use a USB-Serial Adapt.
The Serial-Cable is with "GND", "RX" and "TX" attached on the Device.

When i press on Cutecom "Open device"
i can see the follow text on the cutecom-window:

\0x00

i can write for example

uname -r

in cutecom and press enter, the only what i get is: More from this binary text.
What must i set to get a reply over Serial like this:

2.6.8.1

Thanks, Robert

Post #16

RobertD

25 May 2008, 16:41

Hi abra

What did you mean with:

abraXxl wrote:

You need the kernel image and a tar of all non system directories from your current speedport rootfs.

Are non system directoriers: /dev /proc/ ?.

The only way to do that is:
mount a external share over cifs.
and run follow command on the device:

root@openwrt:/tmp/smbshare# tar -v -cf dev.tar.gz /dev/

@Serial Connection:
I was not able to create a readable connecting over Serial to this Device.
The only was i get ist unreadable Text: \0xx\0x00nY1

I hope anybody can help me.

Sincerely Robert

Post #17

RobertD

9 Jun 2008, 17:58

Hello abra

Version 4 (bcm963xx_fs_kernel.v4) is really great.
But i have one wish is it possible to compile a image with swap-support for me please ?

I have compiled 4 Images but they dont work, i can ping the router with my compiled images but when i want to connect to the device over telnet he close the connection, and i dont know why.

Thanks,
Robert

Post #18

abraXxl

9 Jun 2008, 23:13

Hi !

RobertD wrote:

Hello abra
Version 4 (bcm963xx_fs_kernel.v4) is really great.
But i have one wish is it possible to compile a image with swap-support for me please ?
I have compiled 4 Images but they dont work, i can ping the router with my compiled images but when i want to connect to the device over telnet he close the connection, and i dont know why.
Thanks,
Robert

I can't at the moment recompile with swap support, lack of time, sorry, and no build environment.
All I have done to make a new image, i took the fsworks tar.gz. and incorporated some fixes sent to me by others into the fs source. The vmlinuz is still the same as in v3.

Regarding your four images: What have precisly done to get new images? I can just guess.

If you recompile the kernal dont enable QoS it will break ADSL, ENET and WLAN. If you just take the vmlinux or vmlinux.lz image build from original Tcom-Sources you will be able to complete the fsworks build process.

About serial problem: If you have set 115200,8N1 then it should show typical kernal boot messages on the terminal. If this don't happen try a bit around: exchange TX,RX and power cycle the device.

If you further questions, just. If my time permits i will answer.

cya

(Last edited by abraXxl on 9 Jun 2008, 23:15)

Post #19

RobertD

11 Jun 2008, 20:46

Hi abra
thanks for answers

OH my GOD my new Image works ;-)
i use as kernel .config the 6348.config.v08 from your t-com patch
My Problem was i use the wrong kernel-configs

My current Flash-Image has a Size of 3,7MB (3 873 145 B)
I think the max Size of a flash-image is 4,0 MB, right ?
(openwrt wiki says: 4 MB Flash (different chips have been seen, most are JEDIC AMD command set)

ok one problem left:
i canÂ´t edit for example /etc/config/system
it tells me only read-only.
What must i do to fix this ?
At the kernel-config i found an entry:
CONFIG_ROOTFS_JFFS2 is not set
must i enable it with "y" ?

The complete 6348.config.v08

/ # mount
rootfs on / type rootfs (rw)
/dev/root on / type squashfs (ro)
/proc on /proc type proc (rw,nodiratime)
tmpfs on /tmp type tmpfs (rw)
tmpfs on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw)

/ # df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/mtdblock2            3.2M      3.2M         0 100% /
tmpfs                   256.0k      4.0k    252.0k   2% /tmp
tmpfs

/ # logread
Jan  1 01:00:16 speedport syslog.info syslogd started: BusyBox v1.8.2
Jan  1 01:00:16 speedport user.notice kernel: klogd started: BusyBox v1.8.2 (2007-12-10 23:21:58 CET)
Jan  1 01:00:16 speedport user.warn kernel: Linux version 2.6.8.1 (root@unixstation) (gcc version 3.4.2) #1 Wed Jun 11 20:14:29 CEST 2008
Jan  1 01:00:16 speedport user.warn kernel: Total Flash size: 4096K with 71 sectors
Jan  1 01:00:16 speedport user.warn kernel: 96348GW prom init
Jan  1 01:00:16 speedport user.warn kernel: CPU revision is: 00029107
Jan  1 01:00:16 speedport user.warn kernel: mpi: No Card is in the PCMCIA slot
Jan  1 01:00:16 speedport user.warn kernel: Determined physical RAM map:
Jan  1 01:00:16 speedport user.warn kernel:  memory: 00fa0000 @ 00000000 (usable)
Jan  1 01:00:16 speedport user.debug kernel: On node 0 totalpages: 4000
Jan  1 01:00:16 speedport user.debug kernel:   DMA zone: 4000 pages, LIFO batch:1
Jan  1 01:00:16 speedport user.debug kernel:   Normal zone: 0 pages, LIFO batch:1
Jan  1 01:00:16 speedport user.debug kernel:   HighMem zone: 0 pages, LIFO batch:1
Jan  1 01:00:16 speedport user.warn kernel: Built 1 zonelists
Jan  1 01:00:16 speedport user.warn kernel: Kernel command line: root=31:2 ro init=/etc/preinit
Jan  1 01:00:16 speedport user.warn kernel: brcm mips: enabling icache and dcache...
Jan  1 01:00:16 speedport user.warn kernel: Primary instruction cache 16kB, physically tagged, 2-way, linesize 16 bytes.
Jan  1 01:00:16 speedport user.warn kernel: Primary data cache 8kB 2-way, linesize 16 bytes.
Jan  1 01:00:16 speedport user.warn kernel: PID hash table entries: 64 (order 6: 512 bytes)
Jan  1 01:00:16 speedport user.warn kernel: Using 128.000 MHz high precision timer.
Jan  1 01:00:16 speedport user.warn kernel: Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Jan  1 01:00:16 speedport user.warn kernel: Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Jan  1 01:00:16 speedport user.info kernel: Memory: 13880k/16000k available (1486k kernel code, 2100k reserved, 237k data, 76k init, 0k highmem)
Jan  1 01:00:16 speedport user.warn kernel: Calibrating delay loop... 253.95 BogoMIPS
Jan  1 01:00:16 speedport user.warn kernel: Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Jan  1 01:00:16 speedport user.warn kernel: Checking for 'wait' instruction...  unavailable.
Jan  1 01:00:16 speedport user.info kernel: NET: Registered protocol family 16
Jan  1 01:00:16 speedport user.warn kernel: Can't analyze prologue code at 801823a4
Jan  1 01:00:16 speedport user.warn kernel: Registering mini_fo version $Id$
Jan  1 01:00:16 speedport user.info kernel: JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc.
Jan  1 01:00:16 speedport user.info kernel: PPP generic driver version 2.4.2
Jan  1 01:00:16 speedport user.info kernel: NET: Registered protocol family 24
Jan  1 01:00:16 speedport user.warn kernel: Using noop io scheduler
Jan  1 01:00:16 speedport user.warn kernel: bcm963xx: 0x00400000 at 0x1fc00000
Jan  1 01:00:16 speedport user.info kernel: bcm963xx: Found 1 x16 devices at 0x0 in 16-bit bank
Jan  1 01:00:16 speedport user.warn kernel:  Amd/Fujitsu Extended Query Table at 0x0040
Jan  1 01:00:16 speedport user.warn kernel: bcm963xx: Swapping erase regions for broken CFI table.
Jan  1 01:00:16 speedport user.notice kernel: number of CFI chips: 1
Jan  1 01:00:16 speedport user.notice kernel: cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
Jan  1 01:00:16 speedport user.warn kernel: bcm963xx: Read Signature value of CFE1CFE1
Jan  1 01:00:16 speedport user.warn kernel: bcm963xx: CFE bootloader detected
Jan  1 01:00:16 speedport user.warn kernel: bcm963xx: CFE boot tag found with version 6 and board type 96348GW.
Jan  1 01:00:16 speedport user.warn kernel: bcm963xx: Partition 0 is CFE offset 0 and length 10000
Jan  1 01:00:16 speedport user.warn kernel: bcm963xx: Partition 1 is kernel offset 337100 and length 8a865
Jan  1 01:00:16 speedport user.warn kernel: bcm963xx: Partition 2 is rootfs offset 10100 and length 327000
Jan  1 01:00:16 speedport user.warn kernel: bcm963xx: Partition 3 is rootfs_data offset 3d0000 and length 30000
Jan  1 01:00:16 speedport user.warn kernel: bcm963xx: Partition 4 is linux offset 10000 and length 3f0000
Jan  1 01:00:16 speedport user.notice kernel: Creating 5 MTD partitions on "bcm963xx":
Jan  1 01:00:16 speedport user.notice kernel: 0x00000000-0x00010000 : "CFE"
Jan  1 01:00:16 speedport user.notice kernel: 0x00337100-0x003c1965 : "kernel"
Jan  1 01:00:16 speedport user.warn kernel: mtd: partition "kernel" doesn't start on an erase block boundary -- force read-only
Jan  1 01:00:16 speedport user.notice kernel: 0x00010100-0x00337100 : "rootfs"
Jan  1 01:00:16 speedport user.warn kernel: mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only
Jan  1 01:00:16 speedport user.notice kernel: 0x003d0000-0x00400000 : "rootfs_data"
Jan  1 01:00:16 speedport user.notice kernel: 0x00010000-0x00400000 : "linux"
Jan  1 01:00:16 speedport user.warn kernel: brcmboard: brcm_board_init entry
Jan  1 01:00:16 speedport user.warn kernel: bcm963xx_serial driver v2.0
Jan  1 01:00:16 speedport user.info kernel: NET: Registered protocol family 2
Jan  1 01:00:16 speedport user.info kernel: IP: routing cache hash table of 512 buckets, 4Kbytes
Jan  1 01:00:16 speedport user.info kernel: TCP: Hash tables configured (established 512 bind 1024)
Jan  1 01:00:16 speedport user.info kernel: NET: Registered protocol family 1
Jan  1 01:00:16 speedport user.info kernel: NET: Registered protocol family 17
Jan  1 01:00:16 speedport user.notice kernel: Ebtables v2.0 registered
Jan  1 01:00:16 speedport user.info kernel: NET: Registered protocol family 8
Jan  1 01:00:16 speedport user.info kernel: NET: Registered protocol family 20
Jan  1 01:00:16 speedport user.info kernel: 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
Jan  1 01:00:16 speedport user.info kernel: All bugs added by David S. Miller <davem@redhat.com>
Jan  1 01:00:16 speedport user.warn kernel: VFS: Mounted root (squashfs filesystem) readonly.
Jan  1 01:00:16 speedport user.info kernel: Freeing unused kernel memory: 76k freed
Jan  1 01:00:16 speedport user.warn kernel: Algorithmics/MIPS FPU Emulator v1.5
Jan  1 01:00:16 speedport user.err kernel: jffs2: Too few erase blocks (3)
Jan  1 01:00:16 speedport user.err kernel: jffs2: Too few erase blocks (3)
Jan  1 01:00:16 speedport user.warn kernel: atmapi: module license 'Proprietary' taints kernel.
Jan  1 01:00:17 speedport user.warn kernel: blaadd: blaa_detect entry
Jan  1 01:00:17 speedport user.warn kernel: adsl: adsl_init entry
Jan  1 01:00:19 speedport user.warn kernel: Broadcom BCM6348B0 Ethernet Network Device v0.3 Apr 19 2007 16:50:39
Jan  1 01:00:19 speedport user.warn kernel: Config Internal PHY Through MDIO
Jan  1 01:00:19 speedport user.info kernel: BCM63xx_ENET: 100 MB Full-Duplex (auto-neg)
Jan  1 01:00:19 speedport user.warn kernel: eth0: MAC Address: 00:16:38:74:5F:88
Jan  1 01:00:20 speedport user.debug kernel: PCI: Setting latency timer of device 0000:00:01.0 to 64
Jan  1 01:00:20 speedport user.warn kernel: PCI: Enabling device 0000:00:01.0 (0004 -> 0006)
Jan  1 01:00:20 speedport user.warn kernel: wl: srom not detected, using main memory mapped srom info (wombo board)
Jan  1 01:00:20 speedport user.warn kernel: wl0: wlc_attach: using main board MAC address base in NVRAM (wombo board)
Jan  1 01:00:20 speedport user.warn kernel: wl0 MAC Address: 00:16:38:74:5F:89
Jan  1 01:00:20 speedport user.warn kernel: wl0: Broadcom BCM4318 802.11 Wireless Controller 3.131.35.0.cpe0.1dt
Jan  1 01:00:20 speedport user.info kernel: Broadcom BCMPROCFS v1.0 initialized
Jan  1 01:00:20 speedport user.warn kernel: ip_tables: (C) 2000-2002 Netfilter core team
Jan  1 01:00:20 speedport user.warn kernel: ip_conntrack version 2.1 (125 buckets, 0 max) - 384 bytes per conntrack
Jan  1 01:00:22 speedport user.info rcS: insmod: Loading module failed: No such file or directory
Jan  1 01:00:23 speedport user.info rcS: insmod: Loading module failed: No such file or directory
Jan  1 01:00:23 speedport user.info rcS: insmod: Loading module failed: No such file or directory
Jan  1 01:00:24 speedport user.info rcS: insmod: Loading module failed: No such file or directory
Jan  1 01:00:24 speedport user.info rcS: insmod: Loading module failed: No such file or directory
Jan  1 01:00:24 speedport user.info rcS: insmod: Loading module failed: No such file or directory
Jan  1 01:00:24 speedport user.info kernel: Universal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky
Jan  1 01:00:24 speedport user.info rcS: kernel.panic = 3
Jan  1 01:00:24 speedport user.info rcS: net.ipv4.conf.default.arp_ignore = 1
Jan  1 01:00:24 speedport user.info rcS: net.ipv4.conf.all.arp_ignore = 1
Jan  1 01:00:24 speedport user.info rcS: net.ipv4.ip_forward = 1
Jan  1 01:00:24 speedport user.info rcS: net.ipv4.icmp_echo_ignore_broadcasts = 1
Jan  1 01:00:24 speedport user.info rcS: net.ipv4.icmp_ignore_bogus_error_responses = 1
Jan  1 01:00:24 speedport user.info rcS: net.ipv4.tcp_fin_timeout = 30
Jan  1 01:00:24 speedport user.info rcS: net.ipv4.tcp_keepalive_time = 120
Jan  1 01:00:24 speedport user.info rcS: net.ipv4.tcp_timestamps = 0
Jan  1 01:00:24 speedport user.info rcS: net.ipv4.netfilter.ip_conntrack_tcp_timeout_established = 3600
Jan  1 01:00:24 speedport user.info rcS: net.ipv4.netfilter.ip_conntrack_udp_timeout = 60
Jan  1 01:00:24 speedport user.info rcS: net.ipv4.netfilter.ip_conntrack_udp_timeout_stream = 180
Jan  1 01:00:24 speedport user.info rcS: net.ipv4.netfilter.ip_conntrack_tcp_timeout_close_wait = 300
Jan  1 01:00:24 speedport user.info rcS: net.ipv4.ip_conntrack_max = 2048
Jan  1 01:00:24 speedport user.info rcS: net.ipv4.ip_dynaddr = 1
Jan  1 01:00:26 speedport user.info kernel: device eth0 entered promiscuous mode
Jan  1 01:00:27 speedport user.crit kernel: eth0 Link UP.
Jan  1 01:00:28 speedport user.info rcS: Setting country code using abbreviation: "DE"
Jan  1 01:00:29 speedport user.info kernel: device wl0 entered promiscuous mode
Jan  1 01:00:29 speedport user.info kernel: br0: port 2(wl0) entering learning state
Jan  1 01:00:29 speedport user.info kernel: br0: port 1(eth0) entering learning state
Jan  1 01:00:29 speedport user.info kernel: br0: topology change detected, propagating
Jan  1 01:00:29 speedport user.info kernel: br0: port 2(wl0) entering forwarding state
Jan  1 01:00:29 speedport user.info kernel: br0: topology change detected, propagating
Jan  1 01:00:29 speedport user.info kernel: br0: port 1(eth0) entering forwarding state
Jan  1 01:00:30 speedport user.info rcS: br0: wait for bridge to enter forwarding state ..done

Thanks Robert

(Last edited by RobertD on 11 Jun 2008, 20:51)

Post #20

abra

12 Jun 2008, 11:23

Ola !

RobertD wrote:

OH my GOD my new Image works ;-)
i use as kernel .config the 6348.config.v08 from your t-com patch
My Problem was i use the wrong kernel-configs
My current Flash-Image has a Size of 3,7MB (3 873 145 B)
I think the max Size of a flash-image is 4,0 MB, right ?
(openwrt wiki says: 4 MB Flash (different chips have been seen, most are JEDIC AMD command set)

Fine that your kernel works.

If you need the current kernel config of the V3/V4 images have look in /proc/config.gz running v3 or v4.
I just enabled this feature if i remember correctly.

Keep in mind when using the mini_fo/jffs2 overlay for a writable rootfs, that jffs2 needs at least 3 erase blocks in the rootfs_data partition. That means you need a bit more that 192kb in the corresponding mtd-partition.

RobertD wrote:

ok one problem left:
i canÂ´t edit for example /etc/config/system
it tells me only read-only.
What must i do to fix this ?
At the kernel-config i found an entry:
CONFIG_ROOTFS_JFFS2 is not set
must i enable it with "y" ?

yes of course you must enable this for a writeable rootfs.

RobertD wrote:

/ # mount
rootfs on / type rootfs (rw)
/dev/root on / type squashfs (ro)
/proc on /proc type proc (rw,nodiratime)
tmpfs on /tmp type tmpfs (rw)
tmpfs on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw)

There is no jffs2 mounted. Include jffs2 in the kernel. So creating the mini_fo overlay fails and the init is started from the read only squashfs.

cya

Post #21

RobertD

29 Jun 2008, 10:34

Hi abra

Thanks for the answer it helps me a lot.
After removing the openvpn binary i got more free space and jffs2 works.

I have 2 W500V Routers the first with "Wrt500v" firmware and the second with "bitswitcher" firmware.

The next Step is the first Router has problems with the l2tp Protocol.
The Router reboots when i want to open a connection from the laptop to the external l2tp server.

I think the problem is with creating a ppp Session on the first Router.
What can i do to fix this Problem.

The first router runs with the v3 Firmware:

root@wrt500v:/proc/var/fyi/wan #ls -la
dr-xr-xr-x   18 root     root            0 Jun 29 11:07 .
dr-xr-xr-x    4 root     root            0 Jun 29 11:07 ..
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp0
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp1
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp10
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp11
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp12
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp13
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp14
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp15
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp2
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp3
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp4
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp5
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp6
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp7
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp8
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp9

the second router:

root@bitswitcher:/proc/var/fyi/wan #ls -la
dr-xr-xr-x   18 root     root            0 Jun 29 11:07 .
dr-xr-xr-x    4 root     root            0 Jun 29 11:07 ..
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp0
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp1
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp10
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp11
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp12
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp13
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp14
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp15
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp2
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp3
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp4
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp5
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp6
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp7
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp8
dr-xr-xr-x    2 root     root            0 Jun 29 11:07 .ppp9
lrwxrwxrwx    1 root     root            5 Jun 29 11:07 ppp_1_32_1 -> .ppp0

If you have time, is it possible that you can release your v4 patched files (bcm963xx_fs_kernel.v4.fsworks.tar.bz2),
or what must i do to extract your v4 image.

Thanks for the help.
Robert

(Last edited by RobertD on 29 Jun 2008, 10:44)

Post #22

abraXxl

29 Jun 2008, 12:49

Hi !

RobertD wrote:

Hi abra
[...]
Thanks for the answer it helps me a lot.
After removing the openvpn binary i got more free space and jffs2 works.

fine

RobertD wrote:

The next Step is the first Router has problems with the l2tp Protocol.
The Router reboots when i want to open a connection from the laptop to the external l2tp server.

I don't know what happens there. I think some problems in netfilter. Broadcom has done some black magic in the T-Com kernel, I tried to remove this code, but perhaps i messed it somewhere up.

RobertD wrote:

I think the problem is with creating a ppp Session on the first Router.
What can i do to fix this Problem.
[...]
/proc/var/fyi/wan

For l2tp from internal laptop to external l2tp concetrator no ppp session is created on the router. The kernel just schould forward it transparently.
Regrading the /proc/var/fyi/wan-Thing. This ist one of the black magic broadcom has done. Don't use it. The pppd 2.4 from the Wrt500v images don't rely on it anymore.
And of course bitswitcher uses it, as a t-com/hitachi/targa fork. The ppp settings on the wrt500v are done in /etc/config/system.

RobertD wrote:

If you have time, is it possible that you can release your v4 patched files (bcm963xx_fs_kernel.v4.fsworks.tar.bz2),
or what must i do to extract your v4 image.

Do this on the WRT500V

wrt500 # mkdir /tmp/foo
wrt500 # mount -t squashfs /dev/mtdblock2 /tmp/foo

Do this an an workstation connected to the Wrt500v.

workstation # ssh root@wrt500v tar cf - -C /tmp/foo . > rootfs_for_fsworks.tar

have fun ...

PS: by the way 3:2 for germany ;)

Post #23

noadsl

16 Jul 2008, 18:49

I am looking for an ADSL router solution as described here.

I am not interested in the VOIP bit but DSL modem + WLAN must work reliably.

As described in above post, I am trying to set this up for German friend. I have no means of testing the set-up as I have no ADSL access where I live.

RobertD - if you could give me any idea how reliable your 2 Speedports are, I would be grateful.

Post #24

abraXxl

16 Jul 2008, 21:31

Hi !

noadsl wrote:

I am looking for an ADSL router solution as described here.
I am not interested in the VOIP bit but DSL modem + WLAN must work reliably.
As described in above post, I am trying to set this up for German friend. I have no means of testing the set-up as I have no ADSL access where I live.

Ive done a similiar setup for my parents. They have _very_ basic knowledge of IT. They are happy to know what a window is ... on the screen . I live and work about 700 km away from them I organized a basic dsl setup with a speedport w500v used as a DSL modem with router.
The router is switched on 24/7, has an openvpn connection and publishes its IP via ez-ipupdate,
so I can ssh and rdesktop over the vpn line. The DSL part is quite stable. In 5 months is has lost two times the dsl sync. This is signaled by the LEDs of the w500v. I told them to power cycle if dsl LED is orange or online led is off for more than 5 minutes.

This features are in the v4 image you can download from this topic.

cya

Post #25

noadsl

16 Jul 2008, 23:56

Thank you for your reply.

abraXxl wrote:

speedport w500v used as a DSL modem with router.

Do you mean you use the Speedport's router capabilities or do you use a separate router?

Do your parents use WLAN?

abraXxl wrote:

This features are in the v4 image you can download from this topic.

Which features did you mean? The LEDs?

Are you using the http://vvv.borkum.net/files/w500v/ firmware?

(Last edited by noadsl on 16 Jul 2008, 23:59)

The discussion might have continued from here.

Page 1 of 1