Broadcom K3.X testing, test users wanted

Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3 ... 40, 41, 42 ... 56, 57, 58  Next
View previous topic :: View next topic  
Author Message
RazzMaTazz
DD-WRT Novice


Joined: 21 Mar 2012
Posts: 21
PostPosted: Fri Mar 28, 2014 18:27    Post subject: "Assign WAN Port To Switch" fails in repeater mode Reply with quote
In repeater mode I can check the box to "Assign WAN Port to Switch" (and then "Save", "Apply Settings", and even "Reboot"). The checkbox stays checked, but the WAN port never works as a LAN port on the following DD-WRT versions:
* DD-WRT v24-sp2 (03/14/14) kongac - build 23720M
* dd-wrt.v24-23720_NEWD-2_K3.x_big

This feature worked on older versions but the throughput became very slow (bogged down) in repeater mode.

Is there any way for me to work around this bug or any version that works well?

Is there any way to report such bugs?
Back to top View user's profile Send private message
Sponsor
muadeep
DD-WRT Novice


Joined: 14 Dec 2006
Posts: 23
PostPosted: Sat Apr 05, 2014 13:46    Post subject: LINKSYS E900 Reply with quote
Dear Friends,

I upgraded my Linksys E900 to the latest broadcom_K3X dd-wrt.v24-23838_NEWD-2_K3.x_mega-e900.bin, I'm using it in Repeater mode! so far so good it's been 1 day without any issues yet!, I'll be monitoring and let you know.

I question please, I've got a WRT160NV3 as far as I can see there is a dd-wrt.v24-23838_NEWD-2_K3.x_mega_wrt160nv3.bin in broadcom_K3X but it's almost 8000 KB, how is it possible? I thought that the WRT160NV3 can only support 4000 KB, can someone clarify this, thanks in advance.

Muadeep

linksysy E900 -> dd-wrt.v24-23838_NEWD-2_K3.x_mega-e900.bin
WRT160NV3 -> DD-WRT v24-sp2 (12/19/10) std-nokaid-small - build 15943M NEWD-2 K2.6
Back to top View user's profile Send private message
kozarrat
DD-WRT Novice


Joined: 05 Dec 2009
Posts: 47
PostPosted: Sun Apr 13, 2014 15:59    Post subject: Reply with quote
E3000. After bricking 10+ times finally got it to work by flashing:
1. K2.6 21676
2. K3.x 21676 mega
3. K3.x 23838 mega

I could super easily mount a 3TB NTFS NAS. Haven't tested file transfer speeds yet. Might switch to ext3 later but I have a ton of windows machines on the network so hopefully NTFS works for streaming movies.

2.4 and 5ghz channels both working. WAN/LAN and wireless all working fine so far.
Back to top View user's profile Send private message
withwolf1987
DD-WRT Novice


Joined: 21 Apr 2008
Posts: 14
PostPosted: Mon Apr 14, 2014 13:24    Post subject: Netgear WNR3500l v1 Reply with quote
Dear all.
I have an Netgear WNR3500l v1. with actually "dd-wrt.v24-21061_NEWD-2_K2.6_std_usb_nas.bin"

Can I use "dd-wrt.v24-23838_NEWD-2_K3.x_mega.bin"

I'm worryd about to brick my router because of problems with maga bulits.

withwolf1987
Back to top View user's profile Send private message
slobodan
DD-WRT Guru


Joined: 03 Nov 2011
Posts: 1555
Location: Zwolle
PostPosted: Mon Apr 14, 2014 14:05    Post subject: Re: Netgear WNR3500l v1 Reply with quote
withwolf1987 wrote:
Dear all.
I have an Netgear WNR3500l v1. with actually "dd-wrt.v24-21061_NEWD-2_K2.6_std_usb_nas.bin"

Can I use "dd-wrt.v24-23838_NEWD-2_K3.x_mega.bin"

I'm worryd about to brick my router because of problems with maga bulits.

withwolf1987

Test builds are for the adventurous, they are not guaranteed to work, nor is it guaranteed that they won't brick your router.
_________________
2 times APU2 Opnsense 21.1 with Sensei

2 times RT-AC56U running DD-WRT 45493 (one as Gateway, the other as AP, both bridged with LAN cable)

3 times Asus RT-N16 shelved

E4200 V1 running freshtomato 2020.8 (bridged with LAN cable)

3 times Linksys WRT610N V2 converted to E3000 and 1 original E3000 running freshtomato 2020.8 (bridged with LAN cable)


Back to top View user's profile Send private message Yahoo Messenger MSN Messenger
withwolf1987
DD-WRT Novice


Joined: 21 Apr 2008
Posts: 14
PostPosted: Tue Apr 15, 2014 7:02    Post subject: Re: Netgear WNR3500l v1 Reply with quote
slobodan wrote:
withwolf1987 wrote:
Dear all.
I have an Netgear WNR3500l v1. with actually "dd-wrt.v24-21061_NEWD-2_K2.6_std_usb_nas.bin"

Can I use "dd-wrt.v24-23838_NEWD-2_K3.x_mega.bin"

I'm worryd about to brick my router because of problems with maga bulits.

withwolf1987

Test builds are for the adventurous, they are not guaranteed to work, nor is it guaranteed that they won't brick your router.


I know that Test builds have some dysfunctions. I can live with some problems.
What me concern that my router wont work anymore.
I read that there is an issue with the mega builds and the sice of flashmemory in the WNR3500L.

Can anybody say something about this?

Wont lose my router because some stupid thing.
Back to top View user's profile Send private message
slobodan
DD-WRT Guru


Joined: 03 Nov 2011
Posts: 1555
Location: Zwolle
PostPosted: Thu Apr 17, 2014 11:49    Post subject: Re: Netgear WNR3500l v1 Reply with quote
withwolf1987 wrote:
I know that Test builds have some dysfunctions. I can live with some problems.
What me concern that my router wont work anymore.
I read that there is an issue with the mega builds and the sice of flashmemory in the WNR3500L.

Can anybody say something about this?

Wont lose my router because some stupid thing.

In case you did not read it already: flash test builds only if you are able to unbrick your router (i.e. have experience with doing it).
_________________
2 times APU2 Opnsense 21.1 with Sensei

2 times RT-AC56U running DD-WRT 45493 (one as Gateway, the other as AP, both bridged with LAN cable)

3 times Asus RT-N16 shelved

E4200 V1 running freshtomato 2020.8 (bridged with LAN cable)

3 times Linksys WRT610N V2 converted to E3000 and 1 original E3000 running freshtomato 2020.8 (bridged with LAN cable)


Back to top View user's profile Send private message Yahoo Messenger MSN Messenger
stopspazzing
DD-WRT Novice


Joined: 26 Oct 2008
Posts: 10
PostPosted: Mon Apr 21, 2014 3:26    Post subject: Reply with quote
Linksys e2000

Original firmware was ddwrt build 02/19/2014 n60k
dd-wrt.v24-23598_NEWD-2_K2.6_big-nv60k.bin

Flashed right to K3.x (gutsy I know)

(build date 4/18/14) dd-wrt.v24-23919_NEWD-2_K3.x_mega-e2000.bin

Have no issues, have yet to find any problems. Even OpenVPN works. Will report if I find any.

Update:
http://router-ip/Info.htm aka Status > Sys-Info

Broken, sends me back to Setup
Back to top View user's profile Send private message
stopspazzing
DD-WRT Novice


Joined: 26 Oct 2008
Posts: 10
PostPosted: Mon Apr 21, 2014 3:33    Post subject: Reply with quote
rizla7 wrote:
e2500v2 - 23598 K3.x_mega-nv60k -- wireless issues

so yea, not even a day later, the wireless speeds crawled to 11mbps tx. mixed mode. but the connection seemed to be 'frozen', could not obtain ping, etc. but wireless was up, read a signal and connected.

set mode to mixed-ng, now tx sits at 65m, but rx at 115-130m.

the tx sometimes drops to 40-50ish, which the rx bounces between 1m and 117-130m constantly.

for the record, 17201/18024 was a stable 300m with another router: wrt160nv3 (which is now bricked).

Have you tried: ftp://ftp.dd-wrt.com/others/eko/BrainSlayer-V24-preSP2/2014/04-18-2014-r23919/broadcom_K3X/dd-wrt.v24-23919_NEWD-2_K3.x_mega-e2500.bin
Back to top View user's profile Send private message
thomas01155
DD-WRT Novice


Joined: 29 Oct 2010
Posts: 25
PostPosted: Mon Apr 21, 2014 17:40    Post subject: Reply with quote
Which is the right build to use on F7D4301/F7D8301? Thanks
Back to top View user's profile Send private message
tsynik
DD-WRT User


Joined: 18 Apr 2014
Posts: 151
PostPosted: Mon Apr 21, 2014 21:18    Post subject: Reply with quote
dd-wrt.v24-23919_NEWD-2_K3.x_mega-WNDR4500V2.bin - No MAC and wireless radio.
dd-wrt.v24-23838_NEWD-2_K3.x_mega-WNDR4500V2 - both radios work.
None of .chk fw can be flashed via Web UI from stock Netgear fw (incompatible firmware message). So, I flashed it via tftp earlier (23838). 23919 bin was flashed via Web UI from <kong>'s initial dd-wrt.v24-K3_WNDR4500V2.chk (which can be flashed from stock fw via web)

Also, poor PPTP performance even on unencrypted connection on both... Does it all in userspace? Isn't it better to use accel-pptp and / or accel-ppp instead?
Back to top View user's profile Send private message
Climax69
DD-WRT Novice


Joined: 15 Nov 2009
Posts: 38
PostPosted: Fri Apr 25, 2014 11:33    Post subject: Reply with quote
Can someone give me some advise on upgrading my WRT320Nv1 to a K3.x kernel? Currently I'm running K2.6 23919 big.

The first reason is that with K2.6 builds WiFi isn't working and I've read that K3.x hasn't got this problem.

Secondly currently I've only got 32kb of NVRAM which is almost completely in use and what I've read is that OpenVPN is one of the big consumers. Since there's only a mega version with OpenVPN available for K3.x.. In the OP it isn't clear for me whether -all- K3.x routers have 64kb NVRAM or just certain ones?

So the main question is: can I upgrade straight to
1. dd-wrt.v24-23919_NEWD-2_K3.x_mega.bin
or 2. dd-wrt.v24-23919_NEWD-2_K3.x_mega_wrt320n.bin
or 3. dd-wrt.v24-23919_NEWD-2_K3.x_mega-nv64k.bin
or 4. ...?

My end result must be: K3.x with at least 64kb NVRAM Smile Thanks in advance for the help!

Edit: PS for the record I haven't converted it into an E2000.
Back to top View user's profile Send private message
mbze430
DD-WRT User


Joined: 14 May 2012
Posts: 239
PostPosted: Fri Apr 25, 2014 19:13    Post subject: Re: "Assign WAN Port To Switch" fails in repeater Reply with quote
RazzMaTazz wrote:
In repeater mode I can check the box to "Assign WAN Port to Switch" (and then "Save", "Apply Settings", and even "Reboot"). The checkbox stays checked, but the WAN port never works as a LAN port on the following DD-WRT versions:
* DD-WRT v24-sp2 (03/14/14) kongac - build 23720M
* dd-wrt.v24-23720_NEWD-2_K3.x_big

This feature worked on older versions but the throughput became very slow (bogged down) in repeater mode.

Is there any way for me to work around this bug or any version that works well?

Is there any way to report such bugs?


have you found a fix for this? I am also having the same problem with a WZR-D1800H that uses a Broadcom SOC ... running dd-wrt "DD-WRT v24-sp2 (04/17/14) kongac - build 23900M"
Back to top View user's profile Send private message
mcc23
DD-WRT Novice


Joined: 20 Apr 2014
Posts: 6
PostPosted: Fri Apr 25, 2014 22:03    Post subject: Possibility of K3 Mini Build? Reply with quote
Is there a "FAQ"/Post about the build issues for building a K3.x "Mini" build?

- Is a <4Mb K3.x "mini" build possible?

Like some other posters, the recent K2.6 builds break the wireless functionality and the advice appears to be to upgrade to K3.x.

I am on a limited/4Mb Flash Netgear WNR2000v2 - hence my interest.

Many Thanks
- Mike
Back to top View user's profile Send private message
Climax69
DD-WRT Novice


Joined: 15 Nov 2009
Posts: 38
PostPosted: Sat Apr 26, 2014 8:19    Post subject: Reply with quote
Climax69 wrote:
Can someone give me some advise on upgrading my WRT320Nv1 to a K3.x kernel? Currently I'm running K2.6 23919 big.

The first reason is that with K2.6 builds WiFi isn't working and I've read that K3.x hasn't got this problem.

Secondly currently I've only got 32kb of NVRAM which is almost completely in use and what I've read is that OpenVPN is one of the big consumers. Since there's only a mega version with OpenVPN available for K3.x.. In the OP it isn't clear for me whether -all- K3.x routers have 64kb NVRAM or just certain ones?

So the main question is: can I upgrade straight to
1. dd-wrt.v24-23919_NEWD-2_K3.x_mega.bin
or 2. dd-wrt.v24-23919_NEWD-2_K3.x_mega_wrt320n.bin
or 3. dd-wrt.v24-23919_NEWD-2_K3.x_mega-nv64k.bin
or 4. ...?

My end result must be: K3.x with at least 64kb NVRAM Smile Thanks in advance for the help!

Edit: PS for the record I haven't converted it into an E2000.

Ok, dd-wrt.v24-23919_NEWD-2_K3.x_mega.bin worked for me. WiFi works back again and I've 256KB NVRAM Smile

Edit: Seems to be locking up every 3 or 4 minutes.. Not sure why.

Code:

Jan  1 00:00:08 192.168.1.253 syslog: wland : WLAN daemon successfully started
Jan  1 00:00:08 192.168.1.253 syslog: klogd : klog daemon successfully started
Jan  1 00:00:08 192.168.1.253 kernel: klogd started: BusyBox v1.22.1 (2014-04-18 10:28:52 CEST)
Jan  1 00:00:08 192.168.1.253 kernel: Linux version 3.10.37 (root@dd-wrt.buildserver) (gcc version 4.7.3 20121106 (prerelease) (Linaro GCC 4.7-2012.11) ) #2093 Fri Apr 18 10:30:35 CEST 2014
Jan  1 00:00:08 192.168.1.253 kernel: CPU revision is: 00019740 (MIPS 74Kc)
Jan  1 00:00:08 192.168.1.253 kernel: Found an ST compatible serial flash with 128 64KB blocks; total size 8MB
Jan  1 00:00:08 192.168.1.253 kernel: found nvram at 7E0000
Jan  1 00:00:08 192.168.1.253 kernel: map 60K cfe nvram at 801000
Jan  1 00:00:08 192.168.1.253 kernel: copy 61440 bytes as cfe nvram
Jan  1 00:00:08 192.168.1.253 kernel: Determined physical RAM map:
Jan  1 00:00:08 192.168.1.253 kernel:  memory: 02000000 @ 00000000 (usable)
Jan  1 00:00:08 192.168.1.253 kernel: Zone ranges:
Jan  1 00:00:08 192.168.1.253 kernel:   Normal   [mem 0x00000000-0x01ffffff]
Jan  1 00:00:08 192.168.1.253 kernel:   HighMem  empty
Jan  1 00:00:08 192.168.1.253 kernel: Movable zone start for each node
Jan  1 00:00:08 192.168.1.253 kernel: Early memory node ranges
Jan  1 00:00:08 192.168.1.253 kernel:   node   0: [mem 0x00000000-0x01ffffff]
Jan  1 00:00:08 192.168.1.253 kernel: On node 0 totalpages: 8192
Jan  1 00:00:08 192.168.1.253 kernel: free_area_init_node: node 0, pgdat 80581e10, node_mem_map 81000000
Jan  1 00:00:08 192.168.1.253 kernel:   Normal zone: 64 pages used for memmap
Jan  1 00:00:08 192.168.1.253 kernel:   Normal zone: 0 pages reserved
Jan  1 00:00:08 192.168.1.253 kernel:   Normal zone: 8192 pages, LIFO batch:0
Jan  1 00:00:08 192.168.1.253 kernel: Primary instruction cache 32kB, 4-way, VIPT, I-cache aliases, linesize 32 bytes.
Jan  1 00:00:09 192.168.1.253 kernel: pci 0000:00:07.0: [14e4:080e] type 00 class 0x050000
Jan  1 00:00:09 192.168.1.253 kernel: pci 0000:00:07.0: reg 10: [mem 0x18007000-0x18007fff]
Jan  1 00:00:09 192.168.1.253 kernel: pci 0000:00:07.0: reg 30: [mem 0x00000000-0x000007ff pref]
Jan  1 00:00:09 192.168.1.253 kernel: pci 0000:00:08.0: [14e4:4711] type 00 class 0x040100
Jan  1 00:00:09 192.168.1.253 kernel: pci 0000:00:08.0: reg 10: [mem 0x18008000-0x18008fff]
Jan  1 00:00:09 192.168.1.253 kernel: pci 0000:00:08.0: reg 30: [mem 0x00000000-0x000007ff pref]
Jan  1 00:00:09 192.168.1.253 syslog: pptpd : pptp daemon successfully stoped
Jan  1 00:00:09 192.168.1.253 kernel: pflash: found no supported devices
Jan  1 00:00:09 192.168.1.253 kernel: try to find cfe size up to 8388608
Jan  1 00:00:09 192.168.1.253 kernel: bootloader size: 262144
Jan  1 00:00:09 192.168.1.253 kernel: nvram size: 65536
Jan  1 00:00:09 192.168.1.253 kernel: bcmsflash: Filesystem type: squashfs, size=0x59182a
Jan  1 00:00:09 192.168.1.253 kernel: 0x000000000000-0x000000040000 : "cfe"
Jan  1 00:00:09 192.168.1.253 kernel: 0x000000040000-0x0000007e0000 : "linux"
Jan  1 00:00:09 192.168.1.253 kernel: 0x00000022b400-0x0000007c0000 : "rootfs"
Jan  1 00:00:09 192.168.1.253 kernel: mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
Jan  1 00:00:09 192.168.1.253 kernel: mtd: partition "rootfs" set to be root filesystem
Jan  1 00:00:09 192.168.1.253 kernel: 0x0000007e0000-0x0000007f0000 : "nvram"
Jan  1 00:00:09 192.168.1.253 kernel:     Actions configured
Jan  1 00:00:09 192.168.1.253 kernel: Netfilter messages via NETLINK v0.30.
Jan  1 00:00:09 192.168.1.253 kernel: nf_conntrack version 0.5.0 (399 buckets, 1596 max)
Jan  1 00:00:09 192.168.1.253 kernel: nf_conntrack_rtsp v0.6.21 loading
Jan  1 00:00:09 192.168.1.253 kernel: xt_time: kernel timezone is -0000
Jan  1 00:00:09 192.168.1.253 kernel: ip_set: protocol 6
Jan  1 00:00:09 192.168.1.253 kernel: gre: GRE over IPv4 demultiplexor driver
Jan  1 00:00:09 192.168.1.253 kernel: nf_nat_rtsp v0.6.21 loading
Jan  1 00:00:09 192.168.1.253 kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Jan  1 00:00:09 192.168.1.253 kernel: TCP: bic registered
Jan  1 00:00:09 192.168.1.253 kernel: TCP: cubic registered
Jan  1 00:00:09 192.168.1.253 kernel: TCP: westwood registered
Jan  1 00:00:09 192.168.1.253 kernel: TCP: highspeed registered
Jan  1 00:00:09 192.168.1.253 kernel: TCP: hybla registered
Jan  1 00:00:09 192.168.1.253 kernel: TCP: htcp registered
Jan  1 00:00:09 192.168.1.253 kernel: TCP: vegas registered
Jan  1 00:00:09 192.168.1.253 kernel: TCP: lp registered
Jan  1 00:00:09 192.168.1.253 kernel: TCP: yeah registered
Jan  1 00:00:09 192.168.1.253 kernel: TCP: illinois registered
Jan  1 00:00:09 192.168.1.253 kernel: NET: Registered protocol family 17
Jan  1 00:00:09 192.168.1.253 kernel: Bridge firewalling registered
Jan  1 00:00:09 192.168.1.253 kernel: igs: Unknown symbol emfc_igmp_snooper_register (err 0)
Jan  1 00:00:09 192.168.1.253 kernel: igs: Unknown symbol osl_attach (err 0)
Jan  1 00:00:09 192.168.1.253 kernel: igs: Unknown symbol emfc_rtport_add (err 0)
Jan  1 00:00:09 192.168.1.253 kernel: igs: Unknown symbol emfc_igmp_snooper_unregister (err 0)
Jan  1 00:00:09 192.168.1.253 kernel: igs: Unknown symbol emfc_mfdb_membership_del (err 0)
Jan  1 00:00:09 192.168.1.253 kernel: igs: Unknown symbol emfc_mfdb_membership_add (err 0)
Jan  1 00:00:09 192.168.1.253 kernel: NET: Registered protocol family 10
Jan  1 00:00:09 192.168.1.253 kernel: sit: IPv6 over IPv4 tunneling driver
Jan  1 00:00:09 192.168.1.253 kernel: device br0 entered promiscuous mode
Jan  1 00:00:09 192.168.1.253 kernel: device vlan1 entered promiscuous mode
Jan  1 00:00:09 192.168.1.253 kernel: device eth0 entered promiscuous mode
Jan  1 00:00:09 192.168.1.253 kernel: device eth1 entered promiscuous mode
Jan  1 00:00:09 192.168.1.253 kernel: br0: port 2(eth1) entered forwarding state
Jan  1 00:00:09 192.168.1.253 kernel: br0: port 2(eth1) entered forwarding state
Jan  1 00:00:09 192.168.1.253 kernel: br0: port 1(vlan1) entered forwarding state
Jan  1 00:00:09 192.168.1.253 kernel: br0: port 1(vlan1) entered forwarding state
Jan  1 00:00:09 192.168.1.253 kernel: device br0 left promiscuous mode
Jan  1 00:00:09 192.168.1.253 kernel: device br0 entered promiscuous mode
Jan  1 00:00:09 192.168.1.253 kernel: device br0 left promiscuous mode
Jan  1 00:00:09 192.168.1.253 kernel: br0: port 2(eth1) entered forwarding state
Jan  1 00:00:09 192.168.1.253 kernel: br0: port 1(vlan1) entered forwarding state
Jan  1 00:00:09 192.168.1.253 syslog: upnp : upnp daemon successfully started
Jan  1 00:00:10 192.168.1.253 syslog: cron : cron daemon successfully started
Jan  1 00:00:10 192.168.1.253 cron[1301]: (CRON) STARTUP (fork ok)
Jan  1 00:00:10 192.168.1.253 cron[1301]: (crontabs) ORPHAN (no passwd entry)
Jan  1 00:00:10 192.168.1.253 radvd[1265]: version 1.10.0 started
Jan  1 00:00:10 192.168.1.253 radvd[1265]: IPv6 forwarding setting is: 0, should be 1 or 2
Jan  1 00:00:10 192.168.1.253 radvd[1265]: IPv6 forwarding seems to be disabled, but continuing anyway.
Jan  1 00:00:10 192.168.1.253 radvd[1265]: syntax error in /tmp/radvd.conf, line 1:
Jan  1 00:00:10 192.168.1.253 radvd[1265]: error parsing or activating the config file: /tmp/radvd.conf
Jan  1 00:00:10 192.168.1.253 radvd[1265]: Exiting, failed to read config file.
Jan  1 00:00:10 192.168.1.253 syslog: radvd : RADV daemon successfully started
Jan  1 00:00:10 192.168.1.253 kernel: device vlan2 entered promiscuous mode
Jan  1 00:00:10 192.168.1.253 kernel: device vlan2 left promiscuous mode
Jan  1 00:00:10 192.168.1.253 syslog: dnsmasq : dnsmasq daemon successfully started
Jan  1 00:00:10 192.168.1.253 dropbear[1327]: Failed loading /etc/dropbear/dropbear_rsa_host_key
Jan  1 00:00:10 192.168.1.253 dropbear[1327]: Failed loading /etc/dropbear/dropbear_dss_host_key
Jan  1 00:00:10 192.168.1.253 syslog: dropbear : ssh daemon successfully started
Jan  1 00:00:11 192.168.1.253 syslog: ttraff : traffic counter daemon successfully started
Jan  1 00:00:12 192.168.1.253 syslog: httpd : https daemon successfully started
Jan  1 00:00:12 192.168.1.253 syslog: NAS : NAS lan (wl0 interface) successfully started
Jan  1 00:00:14 192.168.1.253 syslog: klogd : kernel log daemon successfully stopped
Jan  1 00:00:14 192.168.1.253 kernel: klogd: exiting
Jan  1 00:00:14 192.168.1.253 syslog: httpd : http daemon successfully stopped
Jan  1 00:00:18 192.168.1.253 syslog: httpd : http daemon hanging, send SIGKILL
Jan  1 00:00:18 192.168.1.253 syslog: klogd : kernel log daemon hanging, send SIGKILL
Jan  1 00:00:18 192.168.1.253 syslog: syslogd : syslog daemon successfully stopped
Jan  1 00:00:18 192.168.1.253 syslog: klogd : klog daemon successfully started
Jan  1 00:00:18 192.168.1.253 syslog: reset button : resetbutton daemon successfully started
Back to top View user's profile Send private message
Goto page Previous  1, 2, 3 ... 40, 41, 42 ... 56, 57, 58  Next Display posts from previous:    Page 41 of 58
Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum