Hello,
My system is 2 x alix 2d2 with Altitude Adjustment Beta2 (x86/alix2 image)
On both when i try to install some ipk package (like htop) either by gui or console i get same error:

Installing htop (1.0.1-1) to root...
Downloading http://downloads.openwrt.org/attitude_a … -1_x86.ipk.
Collected errors:
* opkg_install_pkg: Package htop md5sum mismatch. Either the opkg or the package index are corrupt. Try 'opkg update'.
* opkg_install_cmd: Cannot install package htop.

opkg update
works well, but nothing change after that.

manual install by:

opkg install http://downloads.openwrt.org/attitude_adjustment/12.09-beta2/x86/alix2/packages/htop_1.0.1-1_x86.ipk

works ok, but then I have to install all dependent packages before manualy.

How to solve this?
Thanks in advance.

(Last edited by vobo on 18 Nov 2012, 00:16)

Is Attitude Adjustment on release candidate stage?

The source code was already changed to reflect that rc stage by r34185 on Tuesday 13 Nov ( http://nbd.name/gitweb.cgi?p=attitude_a … e5b6e9bf2d ), but as the rc binaries have not yet been released on the download site, they are probably being compiled right now.

(Last edited by hnyman on 18 Nov 2012, 11:42)

Do they use a C64 to compile? How long does it take to compile the RC?

(Last edited by stonecarver on 20 Nov 2012, 19:55)

TP-Link TL-MR3420 v1, attitude adjustment 12.09 beta 2.  Works well so far. Uptime8d 2h 9m 39s

Same with me on Client (WDS) it's fairly stable no issues yet.
Also TP-Link TL-WDR4300 v1 AP (WDS) very stable speeds are okay, wireless connection is solid.

Could be that they wait to fix some bugs?

(Last edited by nebbia88 on 22 Nov 2012, 23:07)

Juhosg, one of the devs, said late on Sunday 18th (when he fixed bug 12454 for me https://dev.openwrt.org/ticket/12454#comment:14 ) that "The AA branch is frozen because the buildbots are building the -rc1 release". That is the newest info I have heard. And there have been no checkins to the AA or packages1209 since last week (except one from jow a few minutes ago, but I guess that imagebuilder patch is for the post-rc1 time).

Based on the snapshot buildbots, building a target platform with all packages takes about 15-20 hours on average. And they are building for over 20 platforms. Even with lets say 5 buildslaves it will take several days. Some testing on top of that and we are soon talking about a week in total.

This isn't a complain about slowness or speed about the binaries, just comparing compile duration. I compile them myself on an AMD E-350 machine with 64-bit Linux. If I selected the entire ar71xx target, it takes just above 4 hours for my system to generate all binaries for that entire platform. Are the buildbots running on slower or VMs that are slower?

Dear sirs, again in syslog:
Nov 23 20:55:48 OpenWrt daemon.err dnsmasq[1436]: failed to send packet: Operation not permitted
Nov 23 20:55:48 OpenWrt daemon.err dnsmasq[1436]: failed to send packet: Operation not permitted
Nov 23 20:55:48 OpenWrt daemon.err dnsmasq[1436]: failed to send packet: Operation not permitted
Nov 23 20:55:52 OpenWrt kern.warn kernel: [ 3249.720000] net_ratelimit: 724 callbacks suppressed
Nov 23 20:55:52 OpenWrt kern.warn kernel: [ 3249.730000] nf_conntrack: table full, dropping packet.
Nov 23 20:55:52 OpenWrt kern.warn kernel: [ 3249.730000] nf_conntrack: table full, dropping packet.
Nov 23 20:55:52 OpenWrt kern.warn kernel: [ 3249.740000] nf_conntrack: table full, dropping packet.
Nov 23 20:55:52 OpenWrt kern.warn kernel: [ 3249.740000] nf_conntrack: table full, dropping packet.
Nov 23 20:55:52 OpenWrt kern.warn kernel: [ 3249.750000] nf_conntrack: table full, dropping packet.
Nov 23 20:55:52 OpenWrt kern.warn kernel: [ 3249.990000] nf_conntrack: table full, dropping packet.
Nov 23 20:55:52 OpenWrt kern.warn kernel: [ 3250.000000] nf_conntrack: table full, dropping packet.
Nov 23 20:55:52 OpenWrt kern.warn kernel: [ 3250.000000] nf_conntrack: table full, dropping packet.
Nov 23 20:55:52 OpenWrt kern.warn kernel: [ 3250.010000] nf_conntrack: table full, dropping packet.
Nov 23 20:55:52 OpenWrt kern.warn kernel: [ 3250.010000] nf_conntrack: table full, dropping packet.

And in processes:
1494   nobody     /usr/sbin/dnsmasq -C /var/etc/dnsmasq.conf      83%     3%

(Last edited by Creo2005 on 25 Nov 2012, 09:30)

RC1 just showed up! Happy testing. :-)

http://downloads.openwrt.org/attitude_adjustment/

Edit:
RC1 is running on TP-Link TL-WR941N v3 without problems!

Edit2:
Changelog anyone?

(Last edited by stonecarver on 26 Nov 2012, 18:54)

https://dev.openwrt.org/log/branches/at … ?rev=34185
https://dev.openwrt.org/log/branches/pa … ?rev=34185

Check the changes between beta2=33883  -->  rc1=34185

(Last edited by hnyman on 26 Nov 2012, 19:15)

I have installed RC1 and i have found a bug.
An error while loading page Network-Firewall-Port Forwards.
In Beta2, this error not exist.

(Last edited by mitza97 on 26 Nov 2012, 20:38)

I cannot confirm this bug with RC1.

(Last edited by stonecarver on 26 Nov 2012, 22:26)

anyone tried this RC1 on kirkwood?
beta2 failed to start on my dockstar...
now using beta1

big problem here, with rc1 i ran out of space just installing things needed for extroot!

opkg install block-mount kmod-usb-storage kmod-fs-ext4 e2fsprogs

with beta2 36 KiB left:

/dev/mtdblock3            1152      1116        36  97% /overlay

with rc1 FILESYSTEM FULL.

my best wishes for everyone having 4MB of flash

(Last edited by nebbia88 on 27 Nov 2012, 22:39)

TP-Link TL-WDR4300 Version 1.0, Firmware : Attitude Adjustment 12.09-rc1 - Stable 12 hours
TP-Link TL-WR1043ND Version 1.0, Firmware : Attitude Adjustment 12.09-rc1 - Stable 12 hours

So far I am happy with the release

***FIXED in RC1***

(Last edited by vpritiskovic on 28 Nov 2012, 17:33)

AA 12.09 Beta RC1 on the Lantiq Danube - BT Home Hub 2B - does not boot.

Nor did the AA beta 1 build. Beta 2 did not contain an image for the BBHH2B. For those who might want a working current image (trunk r34388), one can be found here: http://sourceforge.net/projects/hh2b4ev … r%20HHV2B/

Hello and thanks OpenWRT team for good work.
Final version when can be expected ?

It will be quite a while I think, 2-3 months from the way things move. As you can see
https://dev.openwrt.org/query?status=ac … r=priority

alot of bugs need to be ironed and most of them are not even assighned yet.

Never the less, amazing work they are doing.

Why there is still no Image for Gigagset SX76X (SX763) available in trunk?
Why the ugly-usb patch can't be added so it works out-of-the-box?

I've found one developer that made image for this device, but his kernel is too old for me to run FXS ports that are available in the device! And some packages are missing. :-(

I'd like to somehow download image from: http://downloads.openwrt.org/snapshots/trunk/lantiq/
THe one from 12.09-beta doesn't work properly. :-(

The fix is for dwc_otg_ifx.c - I've found info on: http://svn.dd-wrt.com/changeset/18256, but DD-wrt doesnt work for me.

Please, keep up the good work and help me run this thing.
I cant go back to original firmware to get SIP working also... all the fws on the net doesnt work anymore on my device...

Regards,
A.

Hello
How to remove Openwrt firmware on Mikrotik RB751u ?
Firrmware Openwrt 12.9beta1 not working.
No ping for Ip 192.168.1.1 and netinstall RB751u is ready.
Thanks.
Ticket : https://dev.openwrt.org/ticket/12849

Just to let you know the 12.09-rc1 bricks the buffalo whr-hp-g300n device...

Installed the openwrt-ar71xx-generic-whr-hp-g300n-squashfs-sysupgrade.bin on the other day and got a device with the 'red light' constantly on :-(

Had to roll back to 10.03.01 via the tftp method, which was a real pain in the butt.

In case you have the same device, be careful and ready for a potential tftp image reload.

Cheers

ps. as I haven't got a serial console, I have no idea what went wrong and I can't report any errors. Unfortunately all I can say that the image is non-bootable on this device.

I installed rc1 on the WRT350n v2, wireless is not functional at all, tried all configuration types, reflashed several times, and no success.