#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------
Hi, I've build a firmware using latest trunk for DIR-600 rev B. Everything
seems to work ok after flashing but after the first reboot the router
becames inaccessible via webif or ssh. Looks like settings aren't saved
properly to nvram or they get corrupted somehow.The image is 3.2 Mb large
so it should be ok. Can't attach any log files as long as the router
becames unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------
Hi, I've build a firmware using latest trunk for DIR-600 rev B. Everything
seems to work ok after flashing but after the first reboot the router
becames inaccessible via webif or ssh. Looks like settings aren't saved
properly to nvram or they get corrupted somehow.The image is 3.2 Mb large
so it should be ok. Can't attach any log files as long as the router
becames unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by anonymous):

Nobody is working on the ramips port ? As I see it doesn't seems to get
very much updated in trunk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------
Hi, I've build a firmware using latest trunk for DIR-600 rev B. Everything
seems to work ok after flashing but after the first reboot the router
becames inaccessible via webif or ssh. Looks like settings aren't saved
properly to nvram or they get corrupted somehow.The image is 3.2 Mb large
so it should be ok. Can't attach any log files as long as the router
becames unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by anonymous):

Nobody is working on the ramips port ? As I see it doesn't seems to get
very much updated in trunk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Here's the kernel log.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------
Hi, I've build a firmware using latest trunk for DIR-600 rev B. Everything
seems to work ok after flashing but after the first reboot the router
becames inaccessible via webif or ssh. Looks like settings aren't saved
properly to nvram or they get corrupted somehow.The image is 3.2 Mb large
so it should be ok. Can't attach any log files as long as the router
becames unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by anonymous):

Nobody is working on the ramips port ? As I see it doesn't seems to get
very much updated in trunk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Here's the kernel log.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

This is not normal:

{{{
Data CRC 615041f0 != calculated CRC 5ace6da0 for node at 0006007c
Node CRC ffffffff != calculated CRC 9e903ddf for node at 00060e10
Node CRC ffffffff != calculated CRC 7dc8140f for node at 00060e98
Node CRC ffffffff != calculated CRC 46a2d6d9 for node at 00061014
Write of 307 bytes at 0x000612a0 failed. returned -5, retlen 306
Write of 307 bytes at 0x000613d4 failed. returned -5, retlen 306
Write of 43 bytes at 0x00061f70 failed. returned -5, retlen 40
Write of 43 bytes at 0x00061f9c failed. returned -5, retlen 40
Write of 49 bytes at 0x0006200c failed. returned -5, retlen 48
Write of 49 bytes at 0x00062040 failed. returned -5, retlen 48
Write of 55 bytes at 0x000620b8 failed. returned -5, retlen 54
Write of 55 bytes at 0x000620f0 failed. returned -5, retlen 54
}}}

It sounds like your JFFS is not getting built properly. My guess is your
image is too large (not enough room to build the JFFS)... an easy test is
to build a smaller image (try cutting out LuCI or something) and see if
that works.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------
Hi, I've build a firmware using latest trunk for DIR-600 rev B. Everything
seems to work ok after flashing but after the first reboot the router
becames inaccessible via webif or ssh. Looks like settings aren't saved
properly to nvram or they get corrupted somehow.The image is 3.2 Mb large
so it should be ok. Can't attach any log files as long as the router
becames unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by anonymous):

Nobody is working on the ramips port ? As I see it doesn't seems to get
very much updated in trunk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Here's the kernel log.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

This is not normal:

{{{
Data CRC 615041f0 != calculated CRC 5ace6da0 for node at 0006007c
Node CRC ffffffff != calculated CRC 9e903ddf for node at 00060e10
Node CRC ffffffff != calculated CRC 7dc8140f for node at 00060e98
Node CRC ffffffff != calculated CRC 46a2d6d9 for node at 00061014
Write of 307 bytes at 0x000612a0 failed. returned -5, retlen 306
Write of 307 bytes at 0x000613d4 failed. returned -5, retlen 306
Write of 43 bytes at 0x00061f70 failed. returned -5, retlen 40
Write of 43 bytes at 0x00061f9c failed. returned -5, retlen 40
Write of 49 bytes at 0x0006200c failed. returned -5, retlen 48
Write of 49 bytes at 0x00062040 failed. returned -5, retlen 48
Write of 55 bytes at 0x000620b8 failed. returned -5, retlen 54
Write of 55 bytes at 0x000620f0 failed. returned -5, retlen 54
}}}

It sounds like your JFFS is not getting built properly. My guess is your
image is too large (not enough room to build the JFFS)... an easy test is
to build a smaller image (try cutting out LuCI or something) and see if
that works.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

How image is too big if it's 3.2? I'running DD-WRT with 3.6 MB image and
it works.
And there aren't any extra packages to trim, just basic functions. Perhaps
the space allocation in the make file isn't optimal or the mtd
partitioning is wrong.
Kernel command line: board=DIR-300-revB mtdparts=physmap-
flash.0:192k(u-boot)ro,64k(u-boot-
env)ro,64k(factory)ro,832k(kernel),2944k(rootfs),3776k@0x50000(firmware).
And beside this nothing is saved to nvram as long as after reboot
everything gets corrupted.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------
Hi, I've build a firmware using latest trunk for DIR-600 rev B. Everything
seems to work ok after flashing but after the first reboot the router
becames inaccessible via webif or ssh. Looks like settings aren't saved
properly to nvram or they get corrupted somehow.The image is 3.2 Mb large
so it should be ok. Can't attach any log files as long as the router
becames unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by anonymous):

Nobody is working on the ramips port ? As I see it doesn't seems to get
very much updated in trunk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Here's the kernel log.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

This is not normal:

{{{
Data CRC 615041f0 != calculated CRC 5ace6da0 for node at 0006007c
Node CRC ffffffff != calculated CRC 9e903ddf for node at 00060e10
Node CRC ffffffff != calculated CRC 7dc8140f for node at 00060e98
Node CRC ffffffff != calculated CRC 46a2d6d9 for node at 00061014
Write of 307 bytes at 0x000612a0 failed. returned -5, retlen 306
Write of 307 bytes at 0x000613d4 failed. returned -5, retlen 306
Write of 43 bytes at 0x00061f70 failed. returned -5, retlen 40
Write of 43 bytes at 0x00061f9c failed. returned -5, retlen 40
Write of 49 bytes at 0x0006200c failed. returned -5, retlen 48
Write of 49 bytes at 0x00062040 failed. returned -5, retlen 48
Write of 55 bytes at 0x000620b8 failed. returned -5, retlen 54
Write of 55 bytes at 0x000620f0 failed. returned -5, retlen 54
}}}

It sounds like your JFFS is not getting built properly. My guess is your
image is too large (not enough room to build the JFFS)... an easy test is
to build a smaller image (try cutting out LuCI or something) and see if
that works.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

How image is too big if it's 3.2? I'running DD-WRT with 3.6 MB image and
it works.
And there aren't any extra packages to trim, just basic functions. Perhaps
the space allocation in the make file isn't optimal or the mtd
partitioning is wrong.
Kernel command line: board=DIR-300-revB mtdparts=physmap-
flash.0:192k(u-boot)ro,64k(u-boot-
env)ro,64k(factory)ro,832k(kernel),2944k(rootfs),3776k@0x50000(firmware).
And beside this nothing is saved to nvram as long as after reboot
everything gets corrupted.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

First of all, OpenWrt does not use NVRAM like DD-WRT does. OpenWrt uses a
JFFS2 writeable file system to save the configuration data and additional
packages. There must be enough free space in flash to create the JFFS2
partition. AFAIK, standard images from DD-WRT do not use a JFFS2
partition... so a 3.6MB image will work fine on a 4MB flash (but you can't
add any more packages because you don't have a writeable file system).
OpenWrt needs room to create the JFFS2 file system.

Like I said before, I would first try to trim down your squashfs fs (read-
only) by removing some packages from your build.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------
Hi, I've build a firmware using latest trunk for DIR-600 rev B. Everything
seems to work ok after flashing but after the first reboot the router
becames inaccessible via webif or ssh. Looks like settings aren't saved
properly to nvram or they get corrupted somehow.The image is 3.2 Mb large
so it should be ok. Can't attach any log files as long as the router
becames unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by anonymous):

Nobody is working on the ramips port ? As I see it doesn't seems to get
very much updated in trunk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Here's the kernel log.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

This is not normal:

{{{
Data CRC 615041f0 != calculated CRC 5ace6da0 for node at 0006007c
Node CRC ffffffff != calculated CRC 9e903ddf for node at 00060e10
Node CRC ffffffff != calculated CRC 7dc8140f for node at 00060e98
Node CRC ffffffff != calculated CRC 46a2d6d9 for node at 00061014
Write of 307 bytes at 0x000612a0 failed. returned -5, retlen 306
Write of 307 bytes at 0x000613d4 failed. returned -5, retlen 306
Write of 43 bytes at 0x00061f70 failed. returned -5, retlen 40
Write of 43 bytes at 0x00061f9c failed. returned -5, retlen 40
Write of 49 bytes at 0x0006200c failed. returned -5, retlen 48
Write of 49 bytes at 0x00062040 failed. returned -5, retlen 48
Write of 55 bytes at 0x000620b8 failed. returned -5, retlen 54
Write of 55 bytes at 0x000620f0 failed. returned -5, retlen 54
}}}

It sounds like your JFFS is not getting built properly. My guess is your
image is too large (not enough room to build the JFFS)... an easy test is
to build a smaller image (try cutting out LuCI or something) and see if
that works.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

How image is too big if it's 3.2? I'running DD-WRT with 3.6 MB image and
it works.
And there aren't any extra packages to trim, just basic functions. Perhaps
the space allocation in the make file isn't optimal or the mtd
partitioning is wrong.
Kernel command line: board=DIR-300-revB mtdparts=physmap-
flash.0:192k(u-boot)ro,64k(u-boot-
env)ro,64k(factory)ro,832k(kernel),2944k(rootfs),3776k@0x50000(firmware).
And beside this nothing is saved to nvram as long as after reboot
everything gets corrupted.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

First of all, OpenWrt does not use NVRAM like DD-WRT does. OpenWrt uses a
JFFS2 writeable file system to save the configuration data and additional
packages. There must be enough free space in flash to create the JFFS2
partition. AFAIK, standard images from DD-WRT do not use a JFFS2
partition... so a 3.6MB image will work fine on a 4MB flash (but you can't
add any more packages because you don't have a writeable file system).
OpenWrt needs room to create the JFFS2 file system.

Like I said before, I would first try to trim down your squashfs fs (read-
only) by removing some packages from your build.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

What packages can be removed to make it work ?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------
Hi, I've build a firmware using latest trunk for DIR-600 rev B. Everything
seems to work ok after flashing but after the first reboot the router
becames inaccessible via webif or ssh. Looks like settings aren't saved
properly to nvram or they get corrupted somehow.The image is 3.2 Mb large
so it should be ok. Can't attach any log files as long as the router
becames unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by anonymous):

Nobody is working on the ramips port ? As I see it doesn't seems to get
very much updated in trunk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Here's the kernel log.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

This is not normal:

{{{
Data CRC 615041f0 != calculated CRC 5ace6da0 for node at 0006007c
Node CRC ffffffff != calculated CRC 9e903ddf for node at 00060e10
Node CRC ffffffff != calculated CRC 7dc8140f for node at 00060e98
Node CRC ffffffff != calculated CRC 46a2d6d9 for node at 00061014
Write of 307 bytes at 0x000612a0 failed. returned -5, retlen 306
Write of 307 bytes at 0x000613d4 failed. returned -5, retlen 306
Write of 43 bytes at 0x00061f70 failed. returned -5, retlen 40
Write of 43 bytes at 0x00061f9c failed. returned -5, retlen 40
Write of 49 bytes at 0x0006200c failed. returned -5, retlen 48
Write of 49 bytes at 0x00062040 failed. returned -5, retlen 48
Write of 55 bytes at 0x000620b8 failed. returned -5, retlen 54
Write of 55 bytes at 0x000620f0 failed. returned -5, retlen 54
}}}

It sounds like your JFFS is not getting built properly. My guess is your
image is too large (not enough room to build the JFFS)... an easy test is
to build a smaller image (try cutting out LuCI or something) and see if
that works.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

How image is too big if it's 3.2? I'running DD-WRT with 3.6 MB image and
it works.
And there aren't any extra packages to trim, just basic functions. Perhaps
the space allocation in the make file isn't optimal or the mtd
partitioning is wrong.
Kernel command line: board=DIR-300-revB mtdparts=physmap-
flash.0:192k(u-boot)ro,64k(u-boot-
env)ro,64k(factory)ro,832k(kernel),2944k(rootfs),3776k@0x50000(firmware).
And beside this nothing is saved to nvram as long as after reboot
everything gets corrupted.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

First of all, OpenWrt does not use NVRAM like DD-WRT does. OpenWrt uses a
JFFS2 writeable file system to save the configuration data and additional
packages. There must be enough free space in flash to create the JFFS2
partition. AFAIK, standard images from DD-WRT do not use a JFFS2
partition... so a 3.6MB image will work fine on a 4MB flash (but you can't
add any more packages because you don't have a writeable file system).
OpenWrt needs room to create the JFFS2 file system.

Like I said before, I would first try to trim down your squashfs fs (read-
only) by removing some packages from your build.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

What packages can be removed to make it work ?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

There seems to be enough space on the device.

root@OpenWrt:/# mount
rootfs on / type rootfs (rw)
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime,size=15136k)
tmpfs on /dev type tmpfs (rw,noatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,noatime,mode=600)
root on /tmp/root type tmpfs (rw,noatime,mode=755)
/dev/mtdblock5 on /overlay type jffs2 (rw,noatime)
overlayfs:/overlay on / type overlayfs (rw,noatime)

root@OpenWrt:/# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 2.1M 2.1M 0 100% /rom
tmpfs 14.8M 180.0K 14.6M 1% /tmp
tmpfs 512.0K 0 512.0K 0% /dev
root 14.8M 68.0K 14.7M 0% /tmp/root
/dev/mtdblock5 832.0K 212.0K 620.0K 25% /overlay
overlayfs:/overlay 832.0K 212.0K 620.0K 25% /

Despite all that, still getting errors with jffs.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------
Hi, I've build a firmware using latest trunk for DIR-600 rev B. Everything
seems to work ok after flashing but after the first reboot the router
becames inaccessible via webif or ssh. Looks like settings aren't saved
properly to nvram or they get corrupted somehow.The image is 3.2 Mb large
so it should be ok. Can't attach any log files as long as the router
becames unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by anonymous):

Nobody is working on the ramips port ? As I see it doesn't seems to get
very much updated in trunk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Here's the kernel log.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

This is not normal:

{{{
Data CRC 615041f0 != calculated CRC 5ace6da0 for node at 0006007c
Node CRC ffffffff != calculated CRC 9e903ddf for node at 00060e10
Node CRC ffffffff != calculated CRC 7dc8140f for node at 00060e98
Node CRC ffffffff != calculated CRC 46a2d6d9 for node at 00061014
Write of 307 bytes at 0x000612a0 failed. returned -5, retlen 306
Write of 307 bytes at 0x000613d4 failed. returned -5, retlen 306
Write of 43 bytes at 0x00061f70 failed. returned -5, retlen 40
Write of 43 bytes at 0x00061f9c failed. returned -5, retlen 40
Write of 49 bytes at 0x0006200c failed. returned -5, retlen 48
Write of 49 bytes at 0x00062040 failed. returned -5, retlen 48
Write of 55 bytes at 0x000620b8 failed. returned -5, retlen 54
Write of 55 bytes at 0x000620f0 failed. returned -5, retlen 54
}}}

It sounds like your JFFS is not getting built properly. My guess is your
image is too large (not enough room to build the JFFS)... an easy test is
to build a smaller image (try cutting out LuCI or something) and see if
that works.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

How image is too big if it's 3.2? I'running DD-WRT with 3.6 MB image and
it works.
And there aren't any extra packages to trim, just basic functions. Perhaps
the space allocation in the make file isn't optimal or the mtd
partitioning is wrong.
Kernel command line: board=DIR-300-revB mtdparts=physmap-
flash.0:192k(u-boot)ro,64k(u-boot-
env)ro,64k(factory)ro,832k(kernel),2944k(rootfs),3776k@0x50000(firmware).
And beside this nothing is saved to nvram as long as after reboot
everything gets corrupted.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

First of all, OpenWrt does not use NVRAM like DD-WRT does. OpenWrt uses a
JFFS2 writeable file system to save the configuration data and additional
packages. There must be enough free space in flash to create the JFFS2
partition. AFAIK, standard images from DD-WRT do not use a JFFS2
partition... so a 3.6MB image will work fine on a 4MB flash (but you can't
add any more packages because you don't have a writeable file system).
OpenWrt needs room to create the JFFS2 file system.

Like I said before, I would first try to trim down your squashfs fs (read-
only) by removing some packages from your build.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

What packages can be removed to make it work ?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

There seems to be enough space on the device.

root@OpenWrt:/# mount
rootfs on / type rootfs (rw)
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime,size=15136k)
tmpfs on /dev type tmpfs (rw,noatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,noatime,mode=600)
root on /tmp/root type tmpfs (rw,noatime,mode=755)
/dev/mtdblock5 on /overlay type jffs2 (rw,noatime)
overlayfs:/overlay on / type overlayfs (rw,noatime)

root@OpenWrt:/# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 2.1M 2.1M 0 100% /rom
tmpfs 14.8M 180.0K 14.6M 1% /tmp
tmpfs 512.0K 0 512.0K 0% /dev
root 14.8M 68.0K 14.7M 0% /tmp/root
/dev/mtdblock5 832.0K 212.0K 620.0K 25% /overlay
overlayfs:/overlay 832.0K 212.0K 620.0K 25% /

Despite all that, still getting errors with jffs.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Are you using the dir-300 image from trunk, or the dir-600 patch?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------
Hi, I've build a firmware using latest trunk for DIR-600 rev B. Everything
seems to work ok after flashing but after the first reboot the router
becames inaccessible via webif or ssh. Looks like settings aren't saved
properly to nvram or they get corrupted somehow.The image is 3.2 Mb large
so it should be ok. Can't attach any log files as long as the router
becames unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by anonymous):

Nobody is working on the ramips port ? As I see it doesn't seems to get
very much updated in trunk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Here's the kernel log.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

This is not normal:

{{{
Data CRC 615041f0 != calculated CRC 5ace6da0 for node at 0006007c
Node CRC ffffffff != calculated CRC 9e903ddf for node at 00060e10
Node CRC ffffffff != calculated CRC 7dc8140f for node at 00060e98
Node CRC ffffffff != calculated CRC 46a2d6d9 for node at 00061014
Write of 307 bytes at 0x000612a0 failed. returned -5, retlen 306
Write of 307 bytes at 0x000613d4 failed. returned -5, retlen 306
Write of 43 bytes at 0x00061f70 failed. returned -5, retlen 40
Write of 43 bytes at 0x00061f9c failed. returned -5, retlen 40
Write of 49 bytes at 0x0006200c failed. returned -5, retlen 48
Write of 49 bytes at 0x00062040 failed. returned -5, retlen 48
Write of 55 bytes at 0x000620b8 failed. returned -5, retlen 54
Write of 55 bytes at 0x000620f0 failed. returned -5, retlen 54
}}}

It sounds like your JFFS is not getting built properly. My guess is your
image is too large (not enough room to build the JFFS)... an easy test is
to build a smaller image (try cutting out LuCI or something) and see if
that works.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

How image is too big if it's 3.2? I'running DD-WRT with 3.6 MB image and
it works.
And there aren't any extra packages to trim, just basic functions. Perhaps
the space allocation in the make file isn't optimal or the mtd
partitioning is wrong.
Kernel command line: board=DIR-300-revB mtdparts=physmap-
flash.0:192k(u-boot)ro,64k(u-boot-
env)ro,64k(factory)ro,832k(kernel),2944k(rootfs),3776k@0x50000(firmware).
And beside this nothing is saved to nvram as long as after reboot
everything gets corrupted.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

First of all, OpenWrt does not use NVRAM like DD-WRT does. OpenWrt uses a
JFFS2 writeable file system to save the configuration data and additional
packages. There must be enough free space in flash to create the JFFS2
partition. AFAIK, standard images from DD-WRT do not use a JFFS2
partition... so a 3.6MB image will work fine on a 4MB flash (but you can't
add any more packages because you don't have a writeable file system).
OpenWrt needs room to create the JFFS2 file system.

Like I said before, I would first try to trim down your squashfs fs (read-
only) by removing some packages from your build.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

What packages can be removed to make it work ?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

There seems to be enough space on the device.

root@OpenWrt:/# mount
rootfs on / type rootfs (rw)
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime,size=15136k)
tmpfs on /dev type tmpfs (rw,noatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,noatime,mode=600)
root on /tmp/root type tmpfs (rw,noatime,mode=755)
/dev/mtdblock5 on /overlay type jffs2 (rw,noatime)
overlayfs:/overlay on / type overlayfs (rw,noatime)

root@OpenWrt:/# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 2.1M 2.1M 0 100% /rom
tmpfs 14.8M 180.0K 14.6M 1% /tmp
tmpfs 512.0K 0 512.0K 0% /dev
root 14.8M 68.0K 14.7M 0% /tmp/root
/dev/mtdblock5 832.0K 212.0K 620.0K 25% /overlay
overlayfs:/overlay 832.0K 212.0K 620.0K 25% /

Despite all that, still getting errors with jffs.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Are you using the dir-300 image from trunk, or the dir-600 patch?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

I've applied the DIR-600 patch but even with DIR-300 image it's the same
result.I've trimmed the image even more now it has 2.9 megs and still
getting errors.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------
Hi, I've build a firmware using latest trunk for DIR-600 rev B. Everything
seems to work ok after flashing but after the first reboot the router
becames inaccessible via webif or ssh. Looks like settings aren't saved
properly to nvram or they get corrupted somehow.The image is 3.2 Mb large
so it should be ok. Can't attach any log files as long as the router
becames unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by anonymous):

Nobody is working on the ramips port ? As I see it doesn't seems to get
very much updated in trunk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Here's the kernel log.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

This is not normal:

{{{
Data CRC 615041f0 != calculated CRC 5ace6da0 for node at 0006007c
Node CRC ffffffff != calculated CRC 9e903ddf for node at 00060e10
Node CRC ffffffff != calculated CRC 7dc8140f for node at 00060e98
Node CRC ffffffff != calculated CRC 46a2d6d9 for node at 00061014
Write of 307 bytes at 0x000612a0 failed. returned -5, retlen 306
Write of 307 bytes at 0x000613d4 failed. returned -5, retlen 306
Write of 43 bytes at 0x00061f70 failed. returned -5, retlen 40
Write of 43 bytes at 0x00061f9c failed. returned -5, retlen 40
Write of 49 bytes at 0x0006200c failed. returned -5, retlen 48
Write of 49 bytes at 0x00062040 failed. returned -5, retlen 48
Write of 55 bytes at 0x000620b8 failed. returned -5, retlen 54
Write of 55 bytes at 0x000620f0 failed. returned -5, retlen 54
}}}

It sounds like your JFFS is not getting built properly. My guess is your
image is too large (not enough room to build the JFFS)... an easy test is
to build a smaller image (try cutting out LuCI or something) and see if
that works.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

How image is too big if it's 3.2? I'running DD-WRT with 3.6 MB image and
it works.
And there aren't any extra packages to trim, just basic functions. Perhaps
the space allocation in the make file isn't optimal or the mtd
partitioning is wrong.
Kernel command line: board=DIR-300-revB mtdparts=physmap-
flash.0:192k(u-boot)ro,64k(u-boot-
env)ro,64k(factory)ro,832k(kernel),2944k(rootfs),3776k@0x50000(firmware).
And beside this nothing is saved to nvram as long as after reboot
everything gets corrupted.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

First of all, OpenWrt does not use NVRAM like DD-WRT does. OpenWrt uses a
JFFS2 writeable file system to save the configuration data and additional
packages. There must be enough free space in flash to create the JFFS2
partition. AFAIK, standard images from DD-WRT do not use a JFFS2
partition... so a 3.6MB image will work fine on a 4MB flash (but you can't
add any more packages because you don't have a writeable file system).
OpenWrt needs room to create the JFFS2 file system.

Like I said before, I would first try to trim down your squashfs fs (read-
only) by removing some packages from your build.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

What packages can be removed to make it work ?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

There seems to be enough space on the device.

root@OpenWrt:/# mount
rootfs on / type rootfs (rw)
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime,size=15136k)
tmpfs on /dev type tmpfs (rw,noatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,noatime,mode=600)
root on /tmp/root type tmpfs (rw,noatime,mode=755)
/dev/mtdblock5 on /overlay type jffs2 (rw,noatime)
overlayfs:/overlay on / type overlayfs (rw,noatime)

root@OpenWrt:/# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 2.1M 2.1M 0 100% /rom
tmpfs 14.8M 180.0K 14.6M 1% /tmp
tmpfs 512.0K 0 512.0K 0% /dev
root 14.8M 68.0K 14.7M 0% /tmp/root
/dev/mtdblock5 832.0K 212.0K 620.0K 25% /overlay
overlayfs:/overlay 832.0K 212.0K 620.0K 25% /

Despite all that, still getting errors with jffs.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Are you using the dir-300 image from trunk, or the dir-600 patch?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

I've applied the DIR-600 patch but even with DIR-300 image it's the same
result.I've trimmed the image even more now it has 2.9 megs and still
getting errors.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Try this patch:

{{{
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/mach-
dir300-revb.c
===================================================================
--- target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir300-revb.c
+++ target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir300-revb.c
@@ -51,15 +51,15 @@
}, {
.name = "kernel",
.offset = 0x050000,
- .size = 0x0f0000,
+ .size = 0x0d0000,
}, {
.name = "rootfs",
- .offset = 0x140000,
- .size = 0x2B0000,
+ .offset = 0x120000,
+ .size = 0x2e0000,
}, {
.name = "openwrt",
.offset = 0x050000,
- .size = 0x3a0000,
+ .size = 0x3b0000,
}
};
#endif /* CONFIG_MTD_PARTITIONS */
}}}

You'll need to clean and rebuild your target after patching:
{{{
make target/clean V=99
make target/install V=99
}}}

This patch is for the DIR-300 target. It should also work with the
DIR-600 patch, but you'll have to edit the file names accordingly.

I have not tested this. I don't have a DIR-600 and I hand-wrote this
patch. Use at your own risk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------
Hi, I've build a firmware using latest trunk for DIR-600 rev B. Everything
seems to work ok after flashing but after the first reboot the router
becames inaccessible via webif or ssh. Looks like settings aren't saved
properly to nvram or they get corrupted somehow.The image is 3.2 Mb large
so it should be ok. Can't attach any log files as long as the router
becames unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by anonymous):

Nobody is working on the ramips port ? As I see it doesn't seems to get
very much updated in trunk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Here's the kernel log.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

This is not normal:

{{{
Data CRC 615041f0 != calculated CRC 5ace6da0 for node at 0006007c
Node CRC ffffffff != calculated CRC 9e903ddf for node at 00060e10
Node CRC ffffffff != calculated CRC 7dc8140f for node at 00060e98
Node CRC ffffffff != calculated CRC 46a2d6d9 for node at 00061014
Write of 307 bytes at 0x000612a0 failed. returned -5, retlen 306
Write of 307 bytes at 0x000613d4 failed. returned -5, retlen 306
Write of 43 bytes at 0x00061f70 failed. returned -5, retlen 40
Write of 43 bytes at 0x00061f9c failed. returned -5, retlen 40
Write of 49 bytes at 0x0006200c failed. returned -5, retlen 48
Write of 49 bytes at 0x00062040 failed. returned -5, retlen 48
Write of 55 bytes at 0x000620b8 failed. returned -5, retlen 54
Write of 55 bytes at 0x000620f0 failed. returned -5, retlen 54
}}}

It sounds like your JFFS is not getting built properly. My guess is your
image is too large (not enough room to build the JFFS)... an easy test is
to build a smaller image (try cutting out LuCI or something) and see if
that works.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

How image is too big if it's 3.2? I'running DD-WRT with 3.6 MB image and
it works.
And there aren't any extra packages to trim, just basic functions. Perhaps
the space allocation in the make file isn't optimal or the mtd
partitioning is wrong.
Kernel command line: board=DIR-300-revB mtdparts=physmap-
flash.0:192k(u-boot)ro,64k(u-boot-
env)ro,64k(factory)ro,832k(kernel),2944k(rootfs),3776k@0x50000(firmware).
And beside this nothing is saved to nvram as long as after reboot
everything gets corrupted.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

First of all, OpenWrt does not use NVRAM like DD-WRT does. OpenWrt uses a
JFFS2 writeable file system to save the configuration data and additional
packages. There must be enough free space in flash to create the JFFS2
partition. AFAIK, standard images from DD-WRT do not use a JFFS2
partition... so a 3.6MB image will work fine on a 4MB flash (but you can't
add any more packages because you don't have a writeable file system).
OpenWrt needs room to create the JFFS2 file system.

Like I said before, I would first try to trim down your squashfs fs (read-
only) by removing some packages from your build.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

What packages can be removed to make it work ?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

There seems to be enough space on the device.

root@OpenWrt:/# mount
rootfs on / type rootfs (rw)
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime,size=15136k)
tmpfs on /dev type tmpfs (rw,noatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,noatime,mode=600)
root on /tmp/root type tmpfs (rw,noatime,mode=755)
/dev/mtdblock5 on /overlay type jffs2 (rw,noatime)
overlayfs:/overlay on / type overlayfs (rw,noatime)

root@OpenWrt:/# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 2.1M 2.1M 0 100% /rom
tmpfs 14.8M 180.0K 14.6M 1% /tmp
tmpfs 512.0K 0 512.0K 0% /dev
root 14.8M 68.0K 14.7M 0% /tmp/root
/dev/mtdblock5 832.0K 212.0K 620.0K 25% /overlay
overlayfs:/overlay 832.0K 212.0K 620.0K 25% /

Despite all that, still getting errors with jffs.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Are you using the dir-300 image from trunk, or the dir-600 patch?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

I've applied the DIR-600 patch but even with DIR-300 image it's the same
result.I've trimmed the image even more now it has 2.9 megs and still
getting errors.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Try this patch:

{{{
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/mach-
dir300-revb.c
===================================================================
--- target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir300-revb.c
+++ target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir300-revb.c
@@ -51,15 +51,15 @@
}, {
.name = "kernel",
.offset = 0x050000,
- .size = 0x0f0000,
+ .size = 0x0d0000,
}, {
.name = "rootfs",
- .offset = 0x140000,
- .size = 0x2B0000,
+ .offset = 0x120000,
+ .size = 0x2e0000,
}, {
.name = "openwrt",
.offset = 0x050000,
- .size = 0x3a0000,
+ .size = 0x3b0000,
}
};
#endif /* CONFIG_MTD_PARTITIONS */
}}}

You'll need to clean and rebuild your target after patching:
{{{
make target/clean V=99
make target/install V=99
}}}

This patch is for the DIR-300 target. It should also work with the
DIR-600 patch, but you'll have to edit the file names accordingly.

I have not tested this. I don't have a DIR-600 and I hand-wrote this
patch. Use at your own risk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Use this patch instead. It is properly formatted.

{{{
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/mach-
dir-300-revb.c
===================================================================
--- target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir-300-revb.c
(revision 26751)
+++ target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir-300-revb.c
(working copy)
@@ -51,15 +51,15 @@
}, {
.name = "kernel",
.offset = 0x050000,
- .size = 0x0f0000,
+ .size = 0x0d0000,
}, {
.name = "rootfs",
- .offset = 0x140000,
- .size = 0x2B0000,
+ .offset = 0x120000,
+ .size = 0x2e0000,
}, {
.name = "openwrt",
.offset = 0x050000,
- .size = 0x3a0000,
+ .size = 0x3b0000,
}
};
#endif /* CONFIG_MTD_PARTITIONS */
}}}

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------
Hi, I've build a firmware using latest trunk for DIR-600 rev B. Everything
seems to work ok after flashing but after the first reboot the router
becames inaccessible via webif or ssh. Looks like settings aren't saved
properly to nvram or they get corrupted somehow.The image is 3.2 Mb large
so it should be ok. Can't attach any log files as long as the router
becames unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by anonymous):

Nobody is working on the ramips port ? As I see it doesn't seems to get
very much updated in trunk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Here's the kernel log.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

This is not normal:

{{{
Data CRC 615041f0 != calculated CRC 5ace6da0 for node at 0006007c
Node CRC ffffffff != calculated CRC 9e903ddf for node at 00060e10
Node CRC ffffffff != calculated CRC 7dc8140f for node at 00060e98
Node CRC ffffffff != calculated CRC 46a2d6d9 for node at 00061014
Write of 307 bytes at 0x000612a0 failed. returned -5, retlen 306
Write of 307 bytes at 0x000613d4 failed. returned -5, retlen 306
Write of 43 bytes at 0x00061f70 failed. returned -5, retlen 40
Write of 43 bytes at 0x00061f9c failed. returned -5, retlen 40
Write of 49 bytes at 0x0006200c failed. returned -5, retlen 48
Write of 49 bytes at 0x00062040 failed. returned -5, retlen 48
Write of 55 bytes at 0x000620b8 failed. returned -5, retlen 54
Write of 55 bytes at 0x000620f0 failed. returned -5, retlen 54
}}}

It sounds like your JFFS is not getting built properly. My guess is your
image is too large (not enough room to build the JFFS)... an easy test is
to build a smaller image (try cutting out LuCI or something) and see if
that works.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

How image is too big if it's 3.2? I'running DD-WRT with 3.6 MB image and
it works.
And there aren't any extra packages to trim, just basic functions. Perhaps
the space allocation in the make file isn't optimal or the mtd
partitioning is wrong.
Kernel command line: board=DIR-300-revB mtdparts=physmap-
flash.0:192k(u-boot)ro,64k(u-boot-
env)ro,64k(factory)ro,832k(kernel),2944k(rootfs),3776k@0x50000(firmware).
And beside this nothing is saved to nvram as long as after reboot
everything gets corrupted.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

First of all, OpenWrt does not use NVRAM like DD-WRT does. OpenWrt uses a
JFFS2 writeable file system to save the configuration data and additional
packages. There must be enough free space in flash to create the JFFS2
partition. AFAIK, standard images from DD-WRT do not use a JFFS2
partition... so a 3.6MB image will work fine on a 4MB flash (but you can't
add any more packages because you don't have a writeable file system).
OpenWrt needs room to create the JFFS2 file system.

Like I said before, I would first try to trim down your squashfs fs (read-
only) by removing some packages from your build.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

What packages can be removed to make it work ?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

There seems to be enough space on the device.

root@OpenWrt:/# mount
rootfs on / type rootfs (rw)
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime,size=15136k)
tmpfs on /dev type tmpfs (rw,noatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,noatime,mode=600)
root on /tmp/root type tmpfs (rw,noatime,mode=755)
/dev/mtdblock5 on /overlay type jffs2 (rw,noatime)
overlayfs:/overlay on / type overlayfs (rw,noatime)

root@OpenWrt:/# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 2.1M 2.1M 0 100% /rom
tmpfs 14.8M 180.0K 14.6M 1% /tmp
tmpfs 512.0K 0 512.0K 0% /dev
root 14.8M 68.0K 14.7M 0% /tmp/root
/dev/mtdblock5 832.0K 212.0K 620.0K 25% /overlay
overlayfs:/overlay 832.0K 212.0K 620.0K 25% /

Despite all that, still getting errors with jffs.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Are you using the dir-300 image from trunk, or the dir-600 patch?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

I've applied the DIR-600 patch but even with DIR-300 image it's the same
result.I've trimmed the image even more now it has 2.9 megs and still
getting errors.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Try this patch:

{{{
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/mach-
dir300-revb.c
===================================================================
--- target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir300-revb.c
+++ target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir300-revb.c
@@ -51,15 +51,15 @@
}, {
.name = "kernel",
.offset = 0x050000,
- .size = 0x0f0000,
+ .size = 0x0d0000,
}, {
.name = "rootfs",
- .offset = 0x140000,
- .size = 0x2B0000,
+ .offset = 0x120000,
+ .size = 0x2e0000,
}, {
.name = "openwrt",
.offset = 0x050000,
- .size = 0x3a0000,
+ .size = 0x3b0000,
}
};
#endif /* CONFIG_MTD_PARTITIONS */
}}}

You'll need to clean and rebuild your target after patching:
{{{
make target/clean V=99
make target/install V=99
}}}

This patch is for the DIR-300 target. It should also work with the
DIR-600 patch, but you'll have to edit the file names accordingly.

I have not tested this. I don't have a DIR-600 and I hand-wrote this
patch. Use at your own risk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Use this patch instead. It is properly formatted.

{{{
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/mach-
dir-300-revb.c
===================================================================
--- target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir-300-revb.c
(revision 26751)
+++ target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir-300-revb.c
(working copy)
@@ -51,15 +51,15 @@
}, {
.name = "kernel",
.offset = 0x050000,
- .size = 0x0f0000,
+ .size = 0x0d0000,
}, {
.name = "rootfs",
- .offset = 0x140000,
- .size = 0x2B0000,
+ .offset = 0x120000,
+ .size = 0x2e0000,
}, {
.name = "openwrt",
.offset = 0x050000,
- .size = 0x3a0000,
+ .size = 0x3b0000,
}
};
#endif /* CONFIG_MTD_PARTITIONS */
}}}

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Seems to throw less jffs errors with the new patch applied to dir-600
patch. But after reboot the router becames unavailable.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------
Hi, I've build a firmware using latest trunk for DIR-600 rev B. Everything
seems to work ok after flashing but after the first reboot the router
becames inaccessible via webif or ssh. Looks like settings aren't saved
properly to nvram or they get corrupted somehow.The image is 3.2 Mb large
so it should be ok. Can't attach any log files as long as the router
becames unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by anonymous):

Nobody is working on the ramips port ? As I see it doesn't seems to get
very much updated in trunk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Here's the kernel log.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

This is not normal:

{{{
Data CRC 615041f0 != calculated CRC 5ace6da0 for node at 0006007c
Node CRC ffffffff != calculated CRC 9e903ddf for node at 00060e10
Node CRC ffffffff != calculated CRC 7dc8140f for node at 00060e98
Node CRC ffffffff != calculated CRC 46a2d6d9 for node at 00061014
Write of 307 bytes at 0x000612a0 failed. returned -5, retlen 306
Write of 307 bytes at 0x000613d4 failed. returned -5, retlen 306
Write of 43 bytes at 0x00061f70 failed. returned -5, retlen 40
Write of 43 bytes at 0x00061f9c failed. returned -5, retlen 40
Write of 49 bytes at 0x0006200c failed. returned -5, retlen 48
Write of 49 bytes at 0x00062040 failed. returned -5, retlen 48
Write of 55 bytes at 0x000620b8 failed. returned -5, retlen 54
Write of 55 bytes at 0x000620f0 failed. returned -5, retlen 54
}}}

It sounds like your JFFS is not getting built properly. My guess is your
image is too large (not enough room to build the JFFS)... an easy test is
to build a smaller image (try cutting out LuCI or something) and see if
that works.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

How image is too big if it's 3.2? I'running DD-WRT with 3.6 MB image and
it works.
And there aren't any extra packages to trim, just basic functions. Perhaps
the space allocation in the make file isn't optimal or the mtd
partitioning is wrong.
Kernel command line: board=DIR-300-revB mtdparts=physmap-
flash.0:192k(u-boot)ro,64k(u-boot-
env)ro,64k(factory)ro,832k(kernel),2944k(rootfs),3776k@0x50000(firmware).
And beside this nothing is saved to nvram as long as after reboot
everything gets corrupted.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

First of all, OpenWrt does not use NVRAM like DD-WRT does. OpenWrt uses a
JFFS2 writeable file system to save the configuration data and additional
packages. There must be enough free space in flash to create the JFFS2
partition. AFAIK, standard images from DD-WRT do not use a JFFS2
partition... so a 3.6MB image will work fine on a 4MB flash (but you can't
add any more packages because you don't have a writeable file system).
OpenWrt needs room to create the JFFS2 file system.

Like I said before, I would first try to trim down your squashfs fs (read-
only) by removing some packages from your build.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

What packages can be removed to make it work ?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

There seems to be enough space on the device.

root@OpenWrt:/# mount
rootfs on / type rootfs (rw)
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime,size=15136k)
tmpfs on /dev type tmpfs (rw,noatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,noatime,mode=600)
root on /tmp/root type tmpfs (rw,noatime,mode=755)
/dev/mtdblock5 on /overlay type jffs2 (rw,noatime)
overlayfs:/overlay on / type overlayfs (rw,noatime)

root@OpenWrt:/# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 2.1M 2.1M 0 100% /rom
tmpfs 14.8M 180.0K 14.6M 1% /tmp
tmpfs 512.0K 0 512.0K 0% /dev
root 14.8M 68.0K 14.7M 0% /tmp/root
/dev/mtdblock5 832.0K 212.0K 620.0K 25% /overlay
overlayfs:/overlay 832.0K 212.0K 620.0K 25% /

Despite all that, still getting errors with jffs.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Are you using the dir-300 image from trunk, or the dir-600 patch?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

I've applied the DIR-600 patch but even with DIR-300 image it's the same
result.I've trimmed the image even more now it has 2.9 megs and still
getting errors.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Try this patch:

{{{
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/mach-
dir300-revb.c
===================================================================
--- target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir300-revb.c
+++ target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir300-revb.c
@@ -51,15 +51,15 @@
}, {
.name = "kernel",
.offset = 0x050000,
- .size = 0x0f0000,
+ .size = 0x0d0000,
}, {
.name = "rootfs",
- .offset = 0x140000,
- .size = 0x2B0000,
+ .offset = 0x120000,
+ .size = 0x2e0000,
}, {
.name = "openwrt",
.offset = 0x050000,
- .size = 0x3a0000,
+ .size = 0x3b0000,
}
};
#endif /* CONFIG_MTD_PARTITIONS */
}}}

You'll need to clean and rebuild your target after patching:
{{{
make target/clean V=99
make target/install V=99
}}}

This patch is for the DIR-300 target. It should also work with the
DIR-600 patch, but you'll have to edit the file names accordingly.

I have not tested this. I don't have a DIR-600 and I hand-wrote this
patch. Use at your own risk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Use this patch instead. It is properly formatted.

{{{
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/mach-
dir-300-revb.c
===================================================================
--- target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir-300-revb.c
(revision 26751)
+++ target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir-300-revb.c
(working copy)
@@ -51,15 +51,15 @@
}, {
.name = "kernel",
.offset = 0x050000,
- .size = 0x0f0000,
+ .size = 0x0d0000,
}, {
.name = "rootfs",
- .offset = 0x140000,
- .size = 0x2B0000,
+ .offset = 0x120000,
+ .size = 0x2e0000,
}, {
.name = "openwrt",
.offset = 0x050000,
- .size = 0x3a0000,
+ .size = 0x3b0000,
}
};
#endif /* CONFIG_MTD_PARTITIONS */
}}}

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Seems to throw less jffs errors with the new patch applied to dir-600
patch. But after reboot the router becames unavailable.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Trying to alter some settings via Luci it seems like the rootfs_data
partition is locked and that's causing all the settings not to be written
on the jffs partition, rendering the router unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------
Hi, I've build a firmware using latest trunk for DIR-600 rev B. Everything
seems to work ok after flashing but after the first reboot the router
becames inaccessible via webif or ssh. Looks like settings aren't saved
properly to nvram or they get corrupted somehow.The image is 3.2 Mb large
so it should be ok. Can't attach any log files as long as the router
becames unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by anonymous):

Nobody is working on the ramips port ? As I see it doesn't seems to get
very much updated in trunk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Here's the kernel log.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

This is not normal:

{{{
Data CRC 615041f0 != calculated CRC 5ace6da0 for node at 0006007c
Node CRC ffffffff != calculated CRC 9e903ddf for node at 00060e10
Node CRC ffffffff != calculated CRC 7dc8140f for node at 00060e98
Node CRC ffffffff != calculated CRC 46a2d6d9 for node at 00061014
Write of 307 bytes at 0x000612a0 failed. returned -5, retlen 306
Write of 307 bytes at 0x000613d4 failed. returned -5, retlen 306
Write of 43 bytes at 0x00061f70 failed. returned -5, retlen 40
Write of 43 bytes at 0x00061f9c failed. returned -5, retlen 40
Write of 49 bytes at 0x0006200c failed. returned -5, retlen 48
Write of 49 bytes at 0x00062040 failed. returned -5, retlen 48
Write of 55 bytes at 0x000620b8 failed. returned -5, retlen 54
Write of 55 bytes at 0x000620f0 failed. returned -5, retlen 54
}}}

It sounds like your JFFS is not getting built properly. My guess is your
image is too large (not enough room to build the JFFS)... an easy test is
to build a smaller image (try cutting out LuCI or something) and see if
that works.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

How image is too big if it's 3.2? I'running DD-WRT with 3.6 MB image and
it works.
And there aren't any extra packages to trim, just basic functions. Perhaps
the space allocation in the make file isn't optimal or the mtd
partitioning is wrong.
Kernel command line: board=DIR-300-revB mtdparts=physmap-
flash.0:192k(u-boot)ro,64k(u-boot-
env)ro,64k(factory)ro,832k(kernel),2944k(rootfs),3776k@0x50000(firmware).
And beside this nothing is saved to nvram as long as after reboot
everything gets corrupted.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

First of all, OpenWrt does not use NVRAM like DD-WRT does. OpenWrt uses a
JFFS2 writeable file system to save the configuration data and additional
packages. There must be enough free space in flash to create the JFFS2
partition. AFAIK, standard images from DD-WRT do not use a JFFS2
partition... so a 3.6MB image will work fine on a 4MB flash (but you can't
add any more packages because you don't have a writeable file system).
OpenWrt needs room to create the JFFS2 file system.

Like I said before, I would first try to trim down your squashfs fs (read-
only) by removing some packages from your build.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

What packages can be removed to make it work ?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

There seems to be enough space on the device.

root@OpenWrt:/# mount
rootfs on / type rootfs (rw)
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime,size=15136k)
tmpfs on /dev type tmpfs (rw,noatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,noatime,mode=600)
root on /tmp/root type tmpfs (rw,noatime,mode=755)
/dev/mtdblock5 on /overlay type jffs2 (rw,noatime)
overlayfs:/overlay on / type overlayfs (rw,noatime)

root@OpenWrt:/# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 2.1M 2.1M 0 100% /rom
tmpfs 14.8M 180.0K 14.6M 1% /tmp
tmpfs 512.0K 0 512.0K 0% /dev
root 14.8M 68.0K 14.7M 0% /tmp/root
/dev/mtdblock5 832.0K 212.0K 620.0K 25% /overlay
overlayfs:/overlay 832.0K 212.0K 620.0K 25% /

Despite all that, still getting errors with jffs.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Are you using the dir-300 image from trunk, or the dir-600 patch?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

I've applied the DIR-600 patch but even with DIR-300 image it's the same
result.I've trimmed the image even more now it has 2.9 megs and still
getting errors.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Try this patch:

{{{
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/mach-
dir300-revb.c
===================================================================
--- target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir300-revb.c
+++ target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir300-revb.c
@@ -51,15 +51,15 @@
}, {
.name = "kernel",
.offset = 0x050000,
- .size = 0x0f0000,
+ .size = 0x0d0000,
}, {
.name = "rootfs",
- .offset = 0x140000,
- .size = 0x2B0000,
+ .offset = 0x120000,
+ .size = 0x2e0000,
}, {
.name = "openwrt",
.offset = 0x050000,
- .size = 0x3a0000,
+ .size = 0x3b0000,
}
};
#endif /* CONFIG_MTD_PARTITIONS */
}}}

You'll need to clean and rebuild your target after patching:
{{{
make target/clean V=99
make target/install V=99
}}}

This patch is for the DIR-300 target. It should also work with the
DIR-600 patch, but you'll have to edit the file names accordingly.

I have not tested this. I don't have a DIR-600 and I hand-wrote this
patch. Use at your own risk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Use this patch instead. It is properly formatted.

{{{
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/mach-
dir-300-revb.c
===================================================================
--- target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir-300-revb.c
(revision 26751)
+++ target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir-300-revb.c
(working copy)
@@ -51,15 +51,15 @@
}, {
.name = "kernel",
.offset = 0x050000,
- .size = 0x0f0000,
+ .size = 0x0d0000,
}, {
.name = "rootfs",
- .offset = 0x140000,
- .size = 0x2B0000,
+ .offset = 0x120000,
+ .size = 0x2e0000,
}, {
.name = "openwrt",
.offset = 0x050000,
- .size = 0x3a0000,
+ .size = 0x3b0000,
}
};
#endif /* CONFIG_MTD_PARTITIONS */
}}}

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Seems to throw less jffs errors with the new patch applied to dir-600
patch. But after reboot the router becames unavailable.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Trying to alter some settings via Luci it seems like the rootfs_data
partition is locked and that's causing all the settings not to be written
on the jffs partition, rendering the router unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by info@…):

Hi, i´m new on linux and all this stuff, but after 2 weeks, i´m install
fedora 14, donload from svn the trunk version and build 2 images for my
DIR-600 B.
I build too an usb-serial to see what happen on the serial port.
like Boink say: if i flash , all works fine ! but if i try to change
anything a lot of
jffs2 CRC´s errors are displayed, and i think that the network config file
and others file are not read or corrupted.
i see this thing too: with openwrt the chip is very hot, but with dd-wrt i
can put my finger on it without injurie.
Question: the jffs2 is estable ? i build 2 images:
1_all default from trunk
2_add luci interface
both show the same behavior.
Other issue that i see trough the serial port:
if i flash many times the router with the same image some time when jffs2
finish your job present differents results: no erro, CRC error or many CRC
erros

i wait for your help and i´ll test what you say !

Thanks

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------
Hi, I've build a firmware using latest trunk for DIR-600 rev B. Everything
seems to work ok after flashing but after the first reboot the router
becames inaccessible via webif or ssh. Looks like settings aren't saved
properly to nvram or they get corrupted somehow.The image is 3.2 Mb large
so it should be ok. Can't attach any log files as long as the router
becames unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by anonymous):

Nobody is working on the ramips port ? As I see it doesn't seems to get
very much updated in trunk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Here's the kernel log.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

This is not normal:

{{{
Data CRC 615041f0 != calculated CRC 5ace6da0 for node at 0006007c
Node CRC ffffffff != calculated CRC 9e903ddf for node at 00060e10
Node CRC ffffffff != calculated CRC 7dc8140f for node at 00060e98
Node CRC ffffffff != calculated CRC 46a2d6d9 for node at 00061014
Write of 307 bytes at 0x000612a0 failed. returned -5, retlen 306
Write of 307 bytes at 0x000613d4 failed. returned -5, retlen 306
Write of 43 bytes at 0x00061f70 failed. returned -5, retlen 40
Write of 43 bytes at 0x00061f9c failed. returned -5, retlen 40
Write of 49 bytes at 0x0006200c failed. returned -5, retlen 48
Write of 49 bytes at 0x00062040 failed. returned -5, retlen 48
Write of 55 bytes at 0x000620b8 failed. returned -5, retlen 54
Write of 55 bytes at 0x000620f0 failed. returned -5, retlen 54
}}}

It sounds like your JFFS is not getting built properly. My guess is your
image is too large (not enough room to build the JFFS)... an easy test is
to build a smaller image (try cutting out LuCI or something) and see if
that works.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

How image is too big if it's 3.2? I'running DD-WRT with 3.6 MB image and
it works.
And there aren't any extra packages to trim, just basic functions. Perhaps
the space allocation in the make file isn't optimal or the mtd
partitioning is wrong.
Kernel command line: board=DIR-300-revB mtdparts=physmap-
flash.0:192k(u-boot)ro,64k(u-boot-
env)ro,64k(factory)ro,832k(kernel),2944k(rootfs),3776k@0x50000(firmware).
And beside this nothing is saved to nvram as long as after reboot
everything gets corrupted.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

First of all, OpenWrt does not use NVRAM like DD-WRT does. OpenWrt uses a
JFFS2 writeable file system to save the configuration data and additional
packages. There must be enough free space in flash to create the JFFS2
partition. AFAIK, standard images from DD-WRT do not use a JFFS2
partition... so a 3.6MB image will work fine on a 4MB flash (but you can't
add any more packages because you don't have a writeable file system).
OpenWrt needs room to create the JFFS2 file system.

Like I said before, I would first try to trim down your squashfs fs (read-
only) by removing some packages from your build.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

What packages can be removed to make it work ?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

There seems to be enough space on the device.

root@OpenWrt:/# mount
rootfs on / type rootfs (rw)
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime,size=15136k)
tmpfs on /dev type tmpfs (rw,noatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,noatime,mode=600)
root on /tmp/root type tmpfs (rw,noatime,mode=755)
/dev/mtdblock5 on /overlay type jffs2 (rw,noatime)
overlayfs:/overlay on / type overlayfs (rw,noatime)

root@OpenWrt:/# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 2.1M 2.1M 0 100% /rom
tmpfs 14.8M 180.0K 14.6M 1% /tmp
tmpfs 512.0K 0 512.0K 0% /dev
root 14.8M 68.0K 14.7M 0% /tmp/root
/dev/mtdblock5 832.0K 212.0K 620.0K 25% /overlay
overlayfs:/overlay 832.0K 212.0K 620.0K 25% /

Despite all that, still getting errors with jffs.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Are you using the dir-300 image from trunk, or the dir-600 patch?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

I've applied the DIR-600 patch but even with DIR-300 image it's the same
result.I've trimmed the image even more now it has 2.9 megs and still
getting errors.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Try this patch:

{{{
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/mach-
dir300-revb.c
===================================================================
--- target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir300-revb.c
+++ target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir300-revb.c
@@ -51,15 +51,15 @@
}, {
.name = "kernel",
.offset = 0x050000,
- .size = 0x0f0000,
+ .size = 0x0d0000,
}, {
.name = "rootfs",
- .offset = 0x140000,
- .size = 0x2B0000,
+ .offset = 0x120000,
+ .size = 0x2e0000,
}, {
.name = "openwrt",
.offset = 0x050000,
- .size = 0x3a0000,
+ .size = 0x3b0000,
}
};
#endif /* CONFIG_MTD_PARTITIONS */
}}}

You'll need to clean and rebuild your target after patching:
{{{
make target/clean V=99
make target/install V=99
}}}

This patch is for the DIR-300 target. It should also work with the
DIR-600 patch, but you'll have to edit the file names accordingly.

I have not tested this. I don't have a DIR-600 and I hand-wrote this
patch. Use at your own risk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Use this patch instead. It is properly formatted.

{{{
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/mach-
dir-300-revb.c
===================================================================
--- target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir-300-revb.c
(revision 26751)
+++ target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir-300-revb.c
(working copy)
@@ -51,15 +51,15 @@
}, {
.name = "kernel",
.offset = 0x050000,
- .size = 0x0f0000,
+ .size = 0x0d0000,
}, {
.name = "rootfs",
- .offset = 0x140000,
- .size = 0x2B0000,
+ .offset = 0x120000,
+ .size = 0x2e0000,
}, {
.name = "openwrt",
.offset = 0x050000,
- .size = 0x3a0000,
+ .size = 0x3b0000,
}
};
#endif /* CONFIG_MTD_PARTITIONS */
}}}

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Seems to throw less jffs errors with the new patch applied to dir-600
patch. But after reboot the router becames unavailable.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Trying to alter some settings via Luci it seems like the rootfs_data
partition is locked and that's causing all the settings not to be written
on the jffs partition, rendering the router unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by info@…):

Hi, i´m new on linux and all this stuff, but after 2 weeks, i´m install
fedora 14, donload from svn the trunk version and build 2 images for my
DIR-600 B.
I build too an usb-serial to see what happen on the serial port.
like Boink say: if i flash , all works fine ! but if i try to change
anything a lot of
jffs2 CRC´s errors are displayed, and i think that the network config file
and others file are not read or corrupted.
i see this thing too: with openwrt the chip is very hot, but with dd-wrt i
can put my finger on it without injurie.
Question: the jffs2 is estable ? i build 2 images:
1_all default from trunk
2_add luci interface
both show the same behavior.
Other issue that i see trough the serial port:
if i flash many times the router with the same image some time when jffs2
finish your job present differents results: no erro, CRC error or many CRC
erros

i wait for your help and i´ll test what you say !

Thanks

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

I suspect that the DIR-600 rev B is very similar to the DIR-300 rev B, but
has minor hardware differences... possibly different GPIOs, etc. This is
just speculation, as I don't have either one. You are using an image for
the DIR-300 on the DIR-600 (the DIR-600 patch was just copied from the
DIR-300 target, by request), so there may be incompatibilities.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------
Hi, I've build a firmware using latest trunk for DIR-600 rev B. Everything
seems to work ok after flashing but after the first reboot the router
becames inaccessible via webif or ssh. Looks like settings aren't saved
properly to nvram or they get corrupted somehow.The image is 3.2 Mb large
so it should be ok. Can't attach any log files as long as the router
becames unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by anonymous):

Nobody is working on the ramips port ? As I see it doesn't seems to get
very much updated in trunk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Here's the kernel log.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

This is not normal:

{{{
Data CRC 615041f0 != calculated CRC 5ace6da0 for node at 0006007c
Node CRC ffffffff != calculated CRC 9e903ddf for node at 00060e10
Node CRC ffffffff != calculated CRC 7dc8140f for node at 00060e98
Node CRC ffffffff != calculated CRC 46a2d6d9 for node at 00061014
Write of 307 bytes at 0x000612a0 failed. returned -5, retlen 306
Write of 307 bytes at 0x000613d4 failed. returned -5, retlen 306
Write of 43 bytes at 0x00061f70 failed. returned -5, retlen 40
Write of 43 bytes at 0x00061f9c failed. returned -5, retlen 40
Write of 49 bytes at 0x0006200c failed. returned -5, retlen 48
Write of 49 bytes at 0x00062040 failed. returned -5, retlen 48
Write of 55 bytes at 0x000620b8 failed. returned -5, retlen 54
Write of 55 bytes at 0x000620f0 failed. returned -5, retlen 54
}}}

It sounds like your JFFS is not getting built properly. My guess is your
image is too large (not enough room to build the JFFS)... an easy test is
to build a smaller image (try cutting out LuCI or something) and see if
that works.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

How image is too big if it's 3.2? I'running DD-WRT with 3.6 MB image and
it works.
And there aren't any extra packages to trim, just basic functions. Perhaps
the space allocation in the make file isn't optimal or the mtd
partitioning is wrong.
Kernel command line: board=DIR-300-revB mtdparts=physmap-
flash.0:192k(u-boot)ro,64k(u-boot-
env)ro,64k(factory)ro,832k(kernel),2944k(rootfs),3776k@0x50000(firmware).
And beside this nothing is saved to nvram as long as after reboot
everything gets corrupted.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

First of all, OpenWrt does not use NVRAM like DD-WRT does. OpenWrt uses a
JFFS2 writeable file system to save the configuration data and additional
packages. There must be enough free space in flash to create the JFFS2
partition. AFAIK, standard images from DD-WRT do not use a JFFS2
partition... so a 3.6MB image will work fine on a 4MB flash (but you can't
add any more packages because you don't have a writeable file system).
OpenWrt needs room to create the JFFS2 file system.

Like I said before, I would first try to trim down your squashfs fs (read-
only) by removing some packages from your build.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

What packages can be removed to make it work ?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

There seems to be enough space on the device.

root@OpenWrt:/# mount
rootfs on / type rootfs (rw)
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime,size=15136k)
tmpfs on /dev type tmpfs (rw,noatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,noatime,mode=600)
root on /tmp/root type tmpfs (rw,noatime,mode=755)
/dev/mtdblock5 on /overlay type jffs2 (rw,noatime)
overlayfs:/overlay on / type overlayfs (rw,noatime)

root@OpenWrt:/# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 2.1M 2.1M 0 100% /rom
tmpfs 14.8M 180.0K 14.6M 1% /tmp
tmpfs 512.0K 0 512.0K 0% /dev
root 14.8M 68.0K 14.7M 0% /tmp/root
/dev/mtdblock5 832.0K 212.0K 620.0K 25% /overlay
overlayfs:/overlay 832.0K 212.0K 620.0K 25% /

Despite all that, still getting errors with jffs.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Are you using the dir-300 image from trunk, or the dir-600 patch?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

I've applied the DIR-600 patch but even with DIR-300 image it's the same
result.I've trimmed the image even more now it has 2.9 megs and still
getting errors.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Try this patch:

{{{
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/mach-
dir300-revb.c
===================================================================
--- target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir300-revb.c
+++ target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir300-revb.c
@@ -51,15 +51,15 @@
}, {
.name = "kernel",
.offset = 0x050000,
- .size = 0x0f0000,
+ .size = 0x0d0000,
}, {
.name = "rootfs",
- .offset = 0x140000,
- .size = 0x2B0000,
+ .offset = 0x120000,
+ .size = 0x2e0000,
}, {
.name = "openwrt",
.offset = 0x050000,
- .size = 0x3a0000,
+ .size = 0x3b0000,
}
};
#endif /* CONFIG_MTD_PARTITIONS */
}}}

You'll need to clean and rebuild your target after patching:
{{{
make target/clean V=99
make target/install V=99
}}}

This patch is for the DIR-300 target. It should also work with the
DIR-600 patch, but you'll have to edit the file names accordingly.

I have not tested this. I don't have a DIR-600 and I hand-wrote this
patch. Use at your own risk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Use this patch instead. It is properly formatted.

{{{
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/mach-
dir-300-revb.c
===================================================================
--- target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir-300-revb.c
(revision 26751)
+++ target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir-300-revb.c
(working copy)
@@ -51,15 +51,15 @@
}, {
.name = "kernel",
.offset = 0x050000,
- .size = 0x0f0000,
+ .size = 0x0d0000,
}, {
.name = "rootfs",
- .offset = 0x140000,
- .size = 0x2B0000,
+ .offset = 0x120000,
+ .size = 0x2e0000,
}, {
.name = "openwrt",
.offset = 0x050000,
- .size = 0x3a0000,
+ .size = 0x3b0000,
}
};
#endif /* CONFIG_MTD_PARTITIONS */
}}}

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Seems to throw less jffs errors with the new patch applied to dir-600
patch. But after reboot the router becames unavailable.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Trying to alter some settings via Luci it seems like the rootfs_data
partition is locked and that's causing all the settings not to be written
on the jffs partition, rendering the router unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by info@…):

Hi, i´m new on linux and all this stuff, but after 2 weeks, i´m install
fedora 14, donload from svn the trunk version and build 2 images for my
DIR-600 B.
I build too an usb-serial to see what happen on the serial port.
like Boink say: if i flash , all works fine ! but if i try to change
anything a lot of
jffs2 CRC´s errors are displayed, and i think that the network config file
and others file are not read or corrupted.
i see this thing too: with openwrt the chip is very hot, but with dd-wrt i
can put my finger on it without injurie.
Question: the jffs2 is estable ? i build 2 images:
1_all default from trunk
2_add luci interface
both show the same behavior.
Other issue that i see trough the serial port:
if i flash many times the router with the same image some time when jffs2
finish your job present differents results: no erro, CRC error or many CRC
erros

i wait for your help and i´ll test what you say !

Thanks

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

I suspect that the DIR-600 rev B is very similar to the DIR-300 rev B, but
has minor hardware differences... possibly different GPIOs, etc. This is
just speculation, as I don't have either one. You are using an image for
the DIR-300 on the DIR-600 (the DIR-600 patch was just copied from the
DIR-300 target, by request), so there may be incompatibilities.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by anonymous):

Lane, any idea that you think, please send it and i´ll test it !
Or any attach that you need from my dir-600 after first flash and
second....etc.

Thanks

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------
Hi, I've build a firmware using latest trunk for DIR-600 rev B. Everything
seems to work ok after flashing but after the first reboot the router
becames inaccessible via webif or ssh. Looks like settings aren't saved
properly to nvram or they get corrupted somehow.The image is 3.2 Mb large
so it should be ok. Can't attach any log files as long as the router
becames unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by anonymous):

Nobody is working on the ramips port ? As I see it doesn't seems to get
very much updated in trunk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Here's the kernel log.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

This is not normal:

{{{
Data CRC 615041f0 != calculated CRC 5ace6da0 for node at 0006007c
Node CRC ffffffff != calculated CRC 9e903ddf for node at 00060e10
Node CRC ffffffff != calculated CRC 7dc8140f for node at 00060e98
Node CRC ffffffff != calculated CRC 46a2d6d9 for node at 00061014
Write of 307 bytes at 0x000612a0 failed. returned -5, retlen 306
Write of 307 bytes at 0x000613d4 failed. returned -5, retlen 306
Write of 43 bytes at 0x00061f70 failed. returned -5, retlen 40
Write of 43 bytes at 0x00061f9c failed. returned -5, retlen 40
Write of 49 bytes at 0x0006200c failed. returned -5, retlen 48
Write of 49 bytes at 0x00062040 failed. returned -5, retlen 48
Write of 55 bytes at 0x000620b8 failed. returned -5, retlen 54
Write of 55 bytes at 0x000620f0 failed. returned -5, retlen 54
}}}

It sounds like your JFFS is not getting built properly. My guess is your
image is too large (not enough room to build the JFFS)... an easy test is
to build a smaller image (try cutting out LuCI or something) and see if
that works.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

How image is too big if it's 3.2? I'running DD-WRT with 3.6 MB image and
it works.
And there aren't any extra packages to trim, just basic functions. Perhaps
the space allocation in the make file isn't optimal or the mtd
partitioning is wrong.
Kernel command line: board=DIR-300-revB mtdparts=physmap-
flash.0:192k(u-boot)ro,64k(u-boot-
env)ro,64k(factory)ro,832k(kernel),2944k(rootfs),3776k@0x50000(firmware).
And beside this nothing is saved to nvram as long as after reboot
everything gets corrupted.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

First of all, OpenWrt does not use NVRAM like DD-WRT does. OpenWrt uses a
JFFS2 writeable file system to save the configuration data and additional
packages. There must be enough free space in flash to create the JFFS2
partition. AFAIK, standard images from DD-WRT do not use a JFFS2
partition... so a 3.6MB image will work fine on a 4MB flash (but you can't
add any more packages because you don't have a writeable file system).
OpenWrt needs room to create the JFFS2 file system.

Like I said before, I would first try to trim down your squashfs fs (read-
only) by removing some packages from your build.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

What packages can be removed to make it work ?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

There seems to be enough space on the device.

root@OpenWrt:/# mount
rootfs on / type rootfs (rw)
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime,size=15136k)
tmpfs on /dev type tmpfs (rw,noatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,noatime,mode=600)
root on /tmp/root type tmpfs (rw,noatime,mode=755)
/dev/mtdblock5 on /overlay type jffs2 (rw,noatime)
overlayfs:/overlay on / type overlayfs (rw,noatime)

root@OpenWrt:/# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 2.1M 2.1M 0 100% /rom
tmpfs 14.8M 180.0K 14.6M 1% /tmp
tmpfs 512.0K 0 512.0K 0% /dev
root 14.8M 68.0K 14.7M 0% /tmp/root
/dev/mtdblock5 832.0K 212.0K 620.0K 25% /overlay
overlayfs:/overlay 832.0K 212.0K 620.0K 25% /

Despite all that, still getting errors with jffs.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Are you using the dir-300 image from trunk, or the dir-600 patch?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

I've applied the DIR-600 patch but even with DIR-300 image it's the same
result.I've trimmed the image even more now it has 2.9 megs and still
getting errors.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Try this patch:

{{{
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/mach-
dir300-revb.c
===================================================================
--- target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir300-revb.c
+++ target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir300-revb.c
@@ -51,15 +51,15 @@
}, {
.name = "kernel",
.offset = 0x050000,
- .size = 0x0f0000,
+ .size = 0x0d0000,
}, {
.name = "rootfs",
- .offset = 0x140000,
- .size = 0x2B0000,
+ .offset = 0x120000,
+ .size = 0x2e0000,
}, {
.name = "openwrt",
.offset = 0x050000,
- .size = 0x3a0000,
+ .size = 0x3b0000,
}
};
#endif /* CONFIG_MTD_PARTITIONS */
}}}

You'll need to clean and rebuild your target after patching:
{{{
make target/clean V=99
make target/install V=99
}}}

This patch is for the DIR-300 target. It should also work with the
DIR-600 patch, but you'll have to edit the file names accordingly.

I have not tested this. I don't have a DIR-600 and I hand-wrote this
patch. Use at your own risk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Use this patch instead. It is properly formatted.

{{{
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/mach-
dir-300-revb.c
===================================================================
--- target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir-300-revb.c
(revision 26751)
+++ target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir-300-revb.c
(working copy)
@@ -51,15 +51,15 @@
}, {
.name = "kernel",
.offset = 0x050000,
- .size = 0x0f0000,
+ .size = 0x0d0000,
}, {
.name = "rootfs",
- .offset = 0x140000,
- .size = 0x2B0000,
+ .offset = 0x120000,
+ .size = 0x2e0000,
}, {
.name = "openwrt",
.offset = 0x050000,
- .size = 0x3a0000,
+ .size = 0x3b0000,
}
};
#endif /* CONFIG_MTD_PARTITIONS */
}}}

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Seems to throw less jffs errors with the new patch applied to dir-600
patch. But after reboot the router becames unavailable.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Trying to alter some settings via Luci it seems like the rootfs_data
partition is locked and that's causing all the settings not to be written
on the jffs partition, rendering the router unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by info@…):

Hi, i´m new on linux and all this stuff, but after 2 weeks, i´m install
fedora 14, donload from svn the trunk version and build 2 images for my
DIR-600 B.
I build too an usb-serial to see what happen on the serial port.
like Boink say: if i flash , all works fine ! but if i try to change
anything a lot of
jffs2 CRC´s errors are displayed, and i think that the network config file
and others file are not read or corrupted.
i see this thing too: with openwrt the chip is very hot, but with dd-wrt i
can put my finger on it without injurie.
Question: the jffs2 is estable ? i build 2 images:
1_all default from trunk
2_add luci interface
both show the same behavior.
Other issue that i see trough the serial port:
if i flash many times the router with the same image some time when jffs2
finish your job present differents results: no erro, CRC error or many CRC
erros

i wait for your help and i´ll test what you say !

Thanks

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

I suspect that the DIR-600 rev B is very similar to the DIR-300 rev B, but
has minor hardware differences... possibly different GPIOs, etc. This is
just speculation, as I don't have either one. You are using an image for
the DIR-300 on the DIR-600 (the DIR-600 patch was just copied from the
DIR-300 target, by request), so there may be incompatibilities.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by anonymous):

Lane, any idea that you think, please send it and i´ll test it !
Or any attach that you need from my dir-600 after first flash and
second....etc.

Thanks

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

I will try today to flash a real DIR-300 rev.B with the image to see how
it behaves.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------
Hi, I've build a firmware using latest trunk for DIR-600 rev B. Everything
seems to work ok after flashing but after the first reboot the router
becames inaccessible via webif or ssh. Looks like settings aren't saved
properly to nvram or they get corrupted somehow.The image is 3.2 Mb large
so it should be ok. Can't attach any log files as long as the router
becames unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by anonymous):

Nobody is working on the ramips port ? As I see it doesn't seems to get
very much updated in trunk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Here's the kernel log.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

This is not normal:

{{{
Data CRC 615041f0 != calculated CRC 5ace6da0 for node at 0006007c
Node CRC ffffffff != calculated CRC 9e903ddf for node at 00060e10
Node CRC ffffffff != calculated CRC 7dc8140f for node at 00060e98
Node CRC ffffffff != calculated CRC 46a2d6d9 for node at 00061014
Write of 307 bytes at 0x000612a0 failed. returned -5, retlen 306
Write of 307 bytes at 0x000613d4 failed. returned -5, retlen 306
Write of 43 bytes at 0x00061f70 failed. returned -5, retlen 40
Write of 43 bytes at 0x00061f9c failed. returned -5, retlen 40
Write of 49 bytes at 0x0006200c failed. returned -5, retlen 48
Write of 49 bytes at 0x00062040 failed. returned -5, retlen 48
Write of 55 bytes at 0x000620b8 failed. returned -5, retlen 54
Write of 55 bytes at 0x000620f0 failed. returned -5, retlen 54
}}}

It sounds like your JFFS is not getting built properly. My guess is your
image is too large (not enough room to build the JFFS)... an easy test is
to build a smaller image (try cutting out LuCI or something) and see if
that works.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

How image is too big if it's 3.2? I'running DD-WRT with 3.6 MB image and
it works.
And there aren't any extra packages to trim, just basic functions. Perhaps
the space allocation in the make file isn't optimal or the mtd
partitioning is wrong.
Kernel command line: board=DIR-300-revB mtdparts=physmap-
flash.0:192k(u-boot)ro,64k(u-boot-
env)ro,64k(factory)ro,832k(kernel),2944k(rootfs),3776k@0x50000(firmware).
And beside this nothing is saved to nvram as long as after reboot
everything gets corrupted.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

First of all, OpenWrt does not use NVRAM like DD-WRT does. OpenWrt uses a
JFFS2 writeable file system to save the configuration data and additional
packages. There must be enough free space in flash to create the JFFS2
partition. AFAIK, standard images from DD-WRT do not use a JFFS2
partition... so a 3.6MB image will work fine on a 4MB flash (but you can't
add any more packages because you don't have a writeable file system).
OpenWrt needs room to create the JFFS2 file system.

Like I said before, I would first try to trim down your squashfs fs (read-
only) by removing some packages from your build.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

What packages can be removed to make it work ?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

There seems to be enough space on the device.

root@OpenWrt:/# mount
rootfs on / type rootfs (rw)
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime,size=15136k)
tmpfs on /dev type tmpfs (rw,noatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,noatime,mode=600)
root on /tmp/root type tmpfs (rw,noatime,mode=755)
/dev/mtdblock5 on /overlay type jffs2 (rw,noatime)
overlayfs:/overlay on / type overlayfs (rw,noatime)

root@OpenWrt:/# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 2.1M 2.1M 0 100% /rom
tmpfs 14.8M 180.0K 14.6M 1% /tmp
tmpfs 512.0K 0 512.0K 0% /dev
root 14.8M 68.0K 14.7M 0% /tmp/root
/dev/mtdblock5 832.0K 212.0K 620.0K 25% /overlay
overlayfs:/overlay 832.0K 212.0K 620.0K 25% /

Despite all that, still getting errors with jffs.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Are you using the dir-300 image from trunk, or the dir-600 patch?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

I've applied the DIR-600 patch but even with DIR-300 image it's the same
result.I've trimmed the image even more now it has 2.9 megs and still
getting errors.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Try this patch:

{{{
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/mach-
dir300-revb.c
===================================================================
--- target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir300-revb.c
+++ target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir300-revb.c
@@ -51,15 +51,15 @@
}, {
.name = "kernel",
.offset = 0x050000,
- .size = 0x0f0000,
+ .size = 0x0d0000,
}, {
.name = "rootfs",
- .offset = 0x140000,
- .size = 0x2B0000,
+ .offset = 0x120000,
+ .size = 0x2e0000,
}, {
.name = "openwrt",
.offset = 0x050000,
- .size = 0x3a0000,
+ .size = 0x3b0000,
}
};
#endif /* CONFIG_MTD_PARTITIONS */
}}}

You'll need to clean and rebuild your target after patching:
{{{
make target/clean V=99
make target/install V=99
}}}

This patch is for the DIR-300 target. It should also work with the
DIR-600 patch, but you'll have to edit the file names accordingly.

I have not tested this. I don't have a DIR-600 and I hand-wrote this
patch. Use at your own risk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Use this patch instead. It is properly formatted.

{{{
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/mach-
dir-300-revb.c
===================================================================
--- target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir-300-revb.c
(revision 26751)
+++ target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir-300-revb.c
(working copy)
@@ -51,15 +51,15 @@
}, {
.name = "kernel",
.offset = 0x050000,
- .size = 0x0f0000,
+ .size = 0x0d0000,
}, {
.name = "rootfs",
- .offset = 0x140000,
- .size = 0x2B0000,
+ .offset = 0x120000,
+ .size = 0x2e0000,
}, {
.name = "openwrt",
.offset = 0x050000,
- .size = 0x3a0000,
+ .size = 0x3b0000,
}
};
#endif /* CONFIG_MTD_PARTITIONS */
}}}

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Seems to throw less jffs errors with the new patch applied to dir-600
patch. But after reboot the router becames unavailable.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Trying to alter some settings via Luci it seems like the rootfs_data
partition is locked and that's causing all the settings not to be written
on the jffs partition, rendering the router unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by info@…):

Hi, i´m new on linux and all this stuff, but after 2 weeks, i´m install
fedora 14, donload from svn the trunk version and build 2 images for my
DIR-600 B.
I build too an usb-serial to see what happen on the serial port.
like Boink say: if i flash , all works fine ! but if i try to change
anything a lot of
jffs2 CRC´s errors are displayed, and i think that the network config file
and others file are not read or corrupted.
i see this thing too: with openwrt the chip is very hot, but with dd-wrt i
can put my finger on it without injurie.
Question: the jffs2 is estable ? i build 2 images:
1_all default from trunk
2_add luci interface
both show the same behavior.
Other issue that i see trough the serial port:
if i flash many times the router with the same image some time when jffs2
finish your job present differents results: no erro, CRC error or many CRC
erros

i wait for your help and i´ll test what you say !

Thanks

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

I suspect that the DIR-600 rev B is very similar to the DIR-300 rev B, but
has minor hardware differences... possibly different GPIOs, etc. This is
just speculation, as I don't have either one. You are using an image for
the DIR-300 on the DIR-600 (the DIR-600 patch was just copied from the
DIR-300 target, by request), so there may be incompatibilities.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by anonymous):

Lane, any idea that you think, please send it and i´ll test it !
Or any attach that you need from my dir-600 after first flash and
second....etc.

Thanks

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

I will try today to flash a real DIR-300 rev.B with the image to see how
it behaves.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Flashed a real DIR-300 rev B with latest trunk and the latest DIR-300
patch for mtd's. Works like a breeze even after 3-4 reboots. No jffs
errors at all.So it seems something is not right in the DIR-600 rev B
configs.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------
Hi, I've build a firmware using latest trunk for DIR-600 rev B. Everything
seems to work ok after flashing but after the first reboot the router
becames inaccessible via webif or ssh. Looks like settings aren't saved
properly to nvram or they get corrupted somehow.The image is 3.2 Mb large
so it should be ok. Can't attach any log files as long as the router
becames unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by anonymous):

Nobody is working on the ramips port ? As I see it doesn't seems to get
very much updated in trunk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Here's the kernel log.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

This is not normal:

{{{
Data CRC 615041f0 != calculated CRC 5ace6da0 for node at 0006007c
Node CRC ffffffff != calculated CRC 9e903ddf for node at 00060e10
Node CRC ffffffff != calculated CRC 7dc8140f for node at 00060e98
Node CRC ffffffff != calculated CRC 46a2d6d9 for node at 00061014
Write of 307 bytes at 0x000612a0 failed. returned -5, retlen 306
Write of 307 bytes at 0x000613d4 failed. returned -5, retlen 306
Write of 43 bytes at 0x00061f70 failed. returned -5, retlen 40
Write of 43 bytes at 0x00061f9c failed. returned -5, retlen 40
Write of 49 bytes at 0x0006200c failed. returned -5, retlen 48
Write of 49 bytes at 0x00062040 failed. returned -5, retlen 48
Write of 55 bytes at 0x000620b8 failed. returned -5, retlen 54
Write of 55 bytes at 0x000620f0 failed. returned -5, retlen 54
}}}

It sounds like your JFFS is not getting built properly. My guess is your
image is too large (not enough room to build the JFFS)... an easy test is
to build a smaller image (try cutting out LuCI or something) and see if
that works.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

How image is too big if it's 3.2? I'running DD-WRT with 3.6 MB image and
it works.
And there aren't any extra packages to trim, just basic functions. Perhaps
the space allocation in the make file isn't optimal or the mtd
partitioning is wrong.
Kernel command line: board=DIR-300-revB mtdparts=physmap-
flash.0:192k(u-boot)ro,64k(u-boot-
env)ro,64k(factory)ro,832k(kernel),2944k(rootfs),3776k@0x50000(firmware).
And beside this nothing is saved to nvram as long as after reboot
everything gets corrupted.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

First of all, OpenWrt does not use NVRAM like DD-WRT does. OpenWrt uses a
JFFS2 writeable file system to save the configuration data and additional
packages. There must be enough free space in flash to create the JFFS2
partition. AFAIK, standard images from DD-WRT do not use a JFFS2
partition... so a 3.6MB image will work fine on a 4MB flash (but you can't
add any more packages because you don't have a writeable file system).
OpenWrt needs room to create the JFFS2 file system.

Like I said before, I would first try to trim down your squashfs fs (read-
only) by removing some packages from your build.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

What packages can be removed to make it work ?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

There seems to be enough space on the device.

root@OpenWrt:/# mount
rootfs on / type rootfs (rw)
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime,size=15136k)
tmpfs on /dev type tmpfs (rw,noatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,noatime,mode=600)
root on /tmp/root type tmpfs (rw,noatime,mode=755)
/dev/mtdblock5 on /overlay type jffs2 (rw,noatime)
overlayfs:/overlay on / type overlayfs (rw,noatime)

root@OpenWrt:/# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 2.1M 2.1M 0 100% /rom
tmpfs 14.8M 180.0K 14.6M 1% /tmp
tmpfs 512.0K 0 512.0K 0% /dev
root 14.8M 68.0K 14.7M 0% /tmp/root
/dev/mtdblock5 832.0K 212.0K 620.0K 25% /overlay
overlayfs:/overlay 832.0K 212.0K 620.0K 25% /

Despite all that, still getting errors with jffs.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Are you using the dir-300 image from trunk, or the dir-600 patch?

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

I've applied the DIR-600 patch but even with DIR-300 image it's the same
result.I've trimmed the image even more now it has 2.9 megs and still
getting errors.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Try this patch:

{{{
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/mach-
dir300-revb.c
===================================================================
--- target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir300-revb.c
+++ target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir300-revb.c
@@ -51,15 +51,15 @@
}, {
.name = "kernel",
.offset = 0x050000,
- .size = 0x0f0000,
+ .size = 0x0d0000,
}, {
.name = "rootfs",
- .offset = 0x140000,
- .size = 0x2B0000,
+ .offset = 0x120000,
+ .size = 0x2e0000,
}, {
.name = "openwrt",
.offset = 0x050000,
- .size = 0x3a0000,
+ .size = 0x3b0000,
}
};
#endif /* CONFIG_MTD_PARTITIONS */
}}}

You'll need to clean and rebuild your target after patching:
{{{
make target/clean V=99
make target/install V=99
}}}

This patch is for the DIR-300 target. It should also work with the
DIR-600 patch, but you'll have to edit the file names accordingly.

I have not tested this. I don't have a DIR-600 and I hand-wrote this
patch. Use at your own risk.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

Use this patch instead. It is properly formatted.

{{{
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/mach-
dir-300-revb.c
===================================================================
--- target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir-300-revb.c
(revision 26751)
+++ target/linux/ramips/files/arch/mips/ralink/rt305x/mach-dir-300-revb.c
(working copy)
@@ -51,15 +51,15 @@
}, {
.name = "kernel",
.offset = 0x050000,
- .size = 0x0f0000,
+ .size = 0x0d0000,
}, {
.name = "rootfs",
- .offset = 0x140000,
- .size = 0x2B0000,
+ .offset = 0x120000,
+ .size = 0x2e0000,
}, {
.name = "openwrt",
.offset = 0x050000,
- .size = 0x3a0000,
+ .size = 0x3b0000,
}
};
#endif /* CONFIG_MTD_PARTITIONS */
}}}

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Seems to throw less jffs errors with the new patch applied to dir-600
patch. But after reboot the router becames unavailable.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Trying to alter some settings via Luci it seems like the rootfs_data
partition is locked and that's causing all the settings not to be written
on the jffs partition, rendering the router unavailable after reboot.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by info@…):

Hi, i´m new on linux and all this stuff, but after 2 weeks, i´m install
fedora 14, donload from svn the trunk version and build 2 images for my
DIR-600 B.
I build too an usb-serial to see what happen on the serial port.
like Boink say: if i flash , all works fine ! but if i try to change
anything a lot of
jffs2 CRC´s errors are displayed, and i think that the network config file
and others file are not read or corrupted.
i see this thing too: with openwrt the chip is very hot, but with dd-wrt i
can put my finger on it without injurie.
Question: the jffs2 is estable ? i build 2 images:
1_all default from trunk
2_add luci interface
both show the same behavior.
Other issue that i see trough the serial port:
if i flash many times the router with the same image some time when jffs2
finish your job present differents results: no erro, CRC error or many CRC
erros

i wait for your help and i´ll test what you say !

Thanks

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by Layne Edwards ):

I suspect that the DIR-600 rev B is very similar to the DIR-300 rev B, but
has minor hardware differences... possibly different GPIOs, etc. This is
just speculation, as I don't have either one. You are using an image for
the DIR-300 on the DIR-600 (the DIR-600 patch was just copied from the
DIR-300 target, by request), so there may be incompatibilities.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by anonymous):

Lane, any idea that you think, please send it and i´ll test it !
Or any attach that you need from my dir-600 after first flash and
second....etc.

Thanks

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets

#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

I will try today to flash a real DIR-300 rev.B with the image to see how
it behaves.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Flashed a real DIR-300 rev B with latest trunk and the latest DIR-300
patch for mtd's. Works like a breeze even after 3-4 reboots. No jffs
errors at all.So it seems something is not right in the DIR-600 rev B
configs.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)
#9252: Issues with D-Link 300/600 rev B from trunk
--------------------+-------------------------------------------------------
Reporter: boink | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Attitude Adjustment (trunk)
Component: other | Version: Trunk
Keywords: |
--------------------+-------------------------------------------------------

Comment(by boink):

Flash detection on DIR-600 is :
env[0]: memsize=32
env[1]: initrd_start=0x00000000
env[2]: initrd_size=0x0
env[3]: flash_start=0xBF000000
env[4]: flash_size=0x800000
env[0]: memsize=32
env[1]: initrd_start=0x00000000
env[2]: initrd_size=0x0
env[3]: flash_start=0xBF000000
env[4]: flash_size=0x800000


On DIR-300 is:
env[0]: memsize=32
env[1]: initrd_start=0x00000000
env[2]: initrd_size=0x0
env[3]: flash_start=0xBF000000
env[4]: flash_size=0x400000
env[0]: memsize=32
env[1]: initrd_start=0x00000000
env[2]: initrd_size=0x0
env[3]: flash_start=0xBF000000
env[4]: flash_size=0x400000

Perhaps that's causing some issues with jffs.

--
Ticket URL:
OpenWrt
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
openwrt-
https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
)