starcms wrote:

I'm also seeing this oddness in my log with the new build:

Wed Jun 28 23:33:43 2017 user.err kernel: [    8.076638] procd: cannot set group tty for /dev/ttyS11

Likely due to https://git.lede-project.org/?p=source. … 9122dfa242

2.4Ghz drops out for ALL devices, mix of Samsung, Apple, Android, HP, phones, tablets laptops.

Yes, SSID is the same.  I will try deleting the 2.4 Ghz SSID on the devices, will be a challenge to get them all :-)

rhauff wrote:

2.4Ghz drops out for ALL devices, mix of Samsung, Apple, Android, HP, phones, tablets laptops.

Yes, SSID is the same.  I will try deleting the 2.4 Ghz SSID on the devices, will be a challenge to get them all :-)

Ok, I cleared the profiles on all our devices, then rebooted the router.  Now I see the rooter has rebooted itself twice in the last hour.
I keep fearing that I have a hardware problem, but the stock firmware runs semi-reliable now after I factory-reset it.

rhauff wrote:

rhauff wrote:

2.4Ghz drops out for ALL devices, mix of Samsung, Apple, Android, HP, phones, tablets laptops.

Yes, SSID is the same.  I will try deleting the 2.4 Ghz SSID on the devices, will be a challenge to get them all :-)

Ok, I cleared the profiles on all our devices, then rebooted the router.  Now I see the rooter has rebooted itself twice in the last hour.
I keep fearing that I have a hardware problem, but the stock firmware runs semi-reliable now after I factory-reset it.

Update:  After running for 2 hours ( was away from home) i came back and 2.4Ghz light is out.  LEDE shows 2.4Ghz is still enabled, but I am unable to login.  I have saved System & Kernel logs if anybody is interested.  For now I am going back to stock Linksys & will try rollback to previous firmware (whatever that is, but it seemed to work).
If that does not work, I'll be taking this back to the store for a new unit.  Then put LEDE on it :-)

Hi. I've just tried the reghack2, it doesn't seem to work on the latest kernel.

I can't change any of the wireless settings, channel, etc.

Is there a newer version? Thanks.

rev6 wrote:

Hi. I've just tried the reghack2, it doesn't seem to work on the latest kernel.

I can't change any of the wireless settings, channel, etc.

Is there a newer version? Thanks.

You did not state the router model you are using. Might help
Anyway, I am running david's latest, r4470, on my wrt3200acm and can control the wireless settings without issue.

Hi. I've just tried the reghack2, it doesn't seem to work on the latest kernel.

I can't change any of the wireless settings, channel, etc.

Is there a newer version? Thanks.

rev6 wrote:

Hi. I've just tried the reghack2, it doesn't seem to work on the latest kernel.

I can't change any of the wireless settings, channel, etc.

Is there a newer version? Thanks.

This only works on the older v1 version of the WRT1X00AC(S) routers.
For the newer v2 version and all versions of the WRT3200ACM, the channels and power settings can't be changed anymore.
if you have a problem with that, I you'll have to take up your case with the FCC, who imposed newer rules to all manufacturers.

Using the latest R4470 firmware, I can still change them on my WRT1900ACS v1.

rev6 wrote:

Hi. I've just tried the reghack2, it doesn't seem to work on the latest kernel.

I can't change any of the wireless settings, channel, etc.

Is there a newer version? Thanks.

This only works on the older v1 version of the WRT1X00AC(S) routers.
For the newer v2 version and all versions of the WRT3200ACM, the channels and power settings can't be changed anymore.
if you have a problem with that, I you'll have to take up your case with the FCC, who imposed newer rules to all manufacturers.

Using the latest R4470 firmware, I can still change them on my WRT1900ACS v1.

hnyman wrote:

starcms wrote:

I'm also seeing this oddness in my log with the new build:

Wed Jun 28 23:33:43 2017 user.err kernel: [    8.076638] procd: cannot set group tty for /dev/ttyS11

Likely due to https://git.lede-project.org/?p=source. … 9122dfa242

Good find!  So what does this mean exactly?  In future builds, @david needs to remove a script or patch or something which changes the group for /dev/tty* to tty because that commit makes it unnecessary because now procd does it automatically?

And since the group is now already set to tty, it just gives an error when trying to set it to tty again?

Or does it mean the new procd commit isn't working correctly and hence the error messages?

starcms wrote:

hnyman wrote:

Likely due to https://git.lede-project.org/?p=source. … 9122dfa242

Good find!  So what does this mean exactly?  In future builds, @david needs to remove a script or patch or something which changes the group for /dev/tty* to tty because that commit makes it unnecessary because now procd does it automatically?

And since the group is now already set to tty, it just gives an error when trying to set it to tty again?

Or does it mean the new procd commit isn't working correctly and hence the error messages?

Any feedback on this?  It seems pretty important because of the kernel procd errors I'm assuming everyone is getting in the latest build.

I have a WRT1200AC V1 running dd-wrt, it seems to lag after awhile so I want to load up LEDE. Can I flash directly from from dd-wrt to LEDE using the bin file?

lede-mvebu-linksys-wrt1200ac-squashfs-sysupgrade.bin

Is there any progress on the random reboots with the 4.9 kernel on the WRT1900AC V1?

I tried again today and it randomly reboots on my WRT1900AC V1 so I went back to 4.4 kernel that is rock solid.

I would like to go to the new kernel just to keep up but it seems to be taking a long time to track down the 4.9 reboot problem.

autist wrote:

I have a WRT1200AC V1 running dd-wrt, it seems to lag after awhile so I want to load up LEDE. Can I flash directly from from dd-wrt to LEDE using the bin file?

lede-mvebu-linksys-wrt1200ac-squashfs-sysupgrade.bin

You will need to use the .img and start fresh. The differences are too vast.

davidc502 wrote:

autist wrote:

I have a WRT1200AC V1 running dd-wrt, it seems to lag after awhile so I want to load up LEDE. Can I flash directly from from dd-wrt to LEDE using the bin file?

lede-mvebu-linksys-wrt1200ac-squashfs-sysupgrade.bin

You will need to use the .img and start fresh. The differences are too vast.

can I just load the img file from dd-wrt?

davidc502 wrote:

autist wrote:

I have a WRT1200AC V1 running dd-wrt, it seems to lag after awhile so I want to load up LEDE. Can I flash directly from from dd-wrt to LEDE using the bin file?

lede-mvebu-linksys-wrt1200ac-squashfs-sysupgrade.bin

You will need to use the .img and start fresh. The differences are too vast.

can I just load the img file from dd-wrt?

autist wrote:

davidc502 wrote:

You will need to use the .img and start fresh. The differences are too vast.

can I just load the img file from dd-wrt?

I go back and forth from ddwrt and lede. I always flash full images from the stock ui. Never have a problem. I would be very cautious trying to flash from ddwrt to lede.

Regarding tty messages:

If you kept settings when flashing it's possible your original /etc/group was preserved, overwriting the auto-generated groups file with the added tty line.

cat /etc/group

If you don't see a tty group you'll need to add the line right after group 4.

tty:x:5:

InkblotAdmirer wrote:

Regarding tty messages:

If you kept settings when flashing it's possible your original /etc/group was preserved, overwriting the auto-generated groups file with the added tty line.

cat /etc/group

If you don't see a tty group you'll need to add the line right after group 4.

tty:x:5:

You, sir, are a genius!  Didn't think keeping setiings/restoring a backup would mess with any deep configuration like that.  Thank you very much!

So @david, sorry for the confusion.  Nothing wrong with your build.  But anyone upgrading and keeping settings and getting procd errors in their log, make sure your /etc/group file looks like this (add the tty line in that exact place):

root:x:0:
daemon:x:1:
adm:x:4:
tty:x:5:
mail:x:8:
audio:x:29:
www-data:x:33:
ftp:x:55:
users:x:100:
network:x:101:
nogroup:x:65534:
dnsmasq:x:453:dnsmasq

So the only issue with r4470 was dnscrypt not being built with plugins enabled.

starcms wrote:

InkblotAdmirer wrote:

Regarding tty messages:

If you kept settings when flashing it's possible your original /etc/group was preserved, overwriting the auto-generated groups file with the added tty line.

cat /etc/group

If you don't see a tty group you'll need to add the line right after group 4.

tty:x:5:

You, sir, are a genius!  Didn't think keeping setiings/restoring a backup would mess with any deep configuration like that.  Thank you very much!

So @david, sorry for the confusion.  Nothing wrong with your build.  But anyone upgrading and keeping settings and getting procd errors in their log, make sure your /etc/group file looks like this (add the tty line in that exact place):

root:x:0:
daemon:x:1:
adm:x:4:
tty:x:5:
mail:x:8:
audio:x:29:
www-data:x:33:
ftp:x:55:
users:x:100:
network:x:101:
nogroup:x:65534:
dnsmasq:x:453:dnsmasq

So the only issue with r4470 was dnscrypt not being built with plugins enabled.

So do we add the tty group after or before group 4?

Regarding tty messages:

If you kept settings when flashing it's possible your original /etc/group was preserved, overwriting the auto-generated groups file with the added tty line.

cat /etc/group

If you don't see a tty group you'll need to add the line right after group 4.

tty:x:5: