... I have been running the latest builds for the past 3 or 4 and have no problems with any of them
Do you have multiple drives connected to the router? If so, I might just try the latest build.
I don't, I just have 1 x IDE to USB laptop HDD connected but it works fine, 80GB NTFS single partition
Have not tried multiple partitions or drives yet
I just share it via Samba Server settings and with the latest 18777 it shows up on the LAN like a normal machine would _________________ TPLINK TL-WR2543ND (5GHz)
WRT160NL (2.4GHz)
I don't, I just have 1 x IDE to USB laptop HDD connected but it works fine, 80GB NTFS single partition
Have not tried multiple partitions or drives yet
I just share it via Samba Server settings and with the latest 18777 it shows up on the LAN like a normal machine would
Thanks for the info...
My main reason for purchasing this device was to install optware (especially asterisk, samba3, minidlna,...). I wonder if anyone has tested that with a more recent firmware.
Unfortunately, at the moment, it looks like the script at http://wrt160nl.org/files/wrt160nlmod.sh does not work with this build 16785 because the usb devices are located in a different branch...
Code:
root@DDWRT:~# cd /tmp
root@DDWRT:/tmp# wget http://wrt160nl.org/files/wrt160nlmod.sh
Connecting to wrt160nl.org (79.172.211.165:80)
wrt160nlmod.sh 100% |*******************************| 14645 --:--:-- ETA
root@IRLN:/tmp# chmod +x wrt160nlmod.sh
root@IRLN:/tmp# ./wrt160nlmod.sh initiate
##################################
# wrt160nlmod INITIAL SETUP () #
##################################
Finding USB drives... find: /dev/scsi/: No such file or directory
done.
Mounting USB drive...
/mnt has been already used. umounting... mount: can't find /mnt in /etc/fstab
done.
Copying stuff to USB... cp: cannot create directory '/mnt/etc': Read-only file system
cp: cannot create directory '/mnt/bin': Read-only file system
cp: cannot create directory '/mnt/dev': Read-only file system
cp: cannot create directory '/mnt/lib': Read-only file system
cp: cannot create directory '/mnt/usr': Read-only file system
cp: cannot create directory '/mnt/tmp': Read-only file system
cp: cannot create directory '/mnt/jffs': Read-only file system
done.
Mounting USB over running system... mount: mounting /mnt/etc on /etc failed: No such file or directory
mount: mounting /mnt/bin on /bin failed: No such file or directory
mount: mounting /mnt/dev on /dev failed: No such file or directory
mount: mounting /mnt/lib on /lib failed: No such file or directory
mount: mounting /mnt/usr on /usr failed: No such file or directory
mount: mounting /mnt/tmp on /tmp failed: No such file or directory
mount: mounting /mnt/jffs on /jffs failed: No such file or directory
done.
Setting up ipkg... mv: cannot rename '/etc/ipkg.conf': Read-only file system
./wrt160nlmod.sh: line 425: can't create /etc/ipkg.conf: Read-only file system
cp: cannot create '/bin/ipkg.orig': Read-only file system
cat: can't open '/bin/ipkg.orig': No such file or directory
./wrt160nlmod.sh: line 425: can't create /bin/ipkg: Read-only file system
done.
./wrt160nlmod.sh: line 425: can't create /etc/rcc.iptables.cronjob: Read-only file system
chmod: /etc/rcc.iptables.cronjob: No such file or directory
size: 22887 bytes (42649 left)
Creating startup scripts... done.
mkdir: cannot create directory '/mnt/downloads': Read-only file system
mkdir: cannot create directory '/mnt/downloads/': Read-only file system
chmod: /mnt/downloads: No such file or directory
Code:
root@DDWRT:/# find /dev/scsi/
find: /dev/scsi/: No such file or directory
Is there any major reason why 16795 is recommended over the latest 18777 for the WRT160NL ?
I have been running the latest builds for the past 3 or 4 and have no problems with any of them
Past 3 builds have been ok with the 160nl, and if you notice those past 3 builds have come out pretty much back to back from each other date wise, before those past 3 builds though - after 16785 the image became to big thus bricked the unit, and that is why i still recommended 16785. hope that answers your question. _________________ Wireless N Config | Linking Routers | DD-WRT Wiki | DD-WRT Builds | Peacock - Broadcom FAQ
Joined: 06 Feb 2010 Posts: 7401 Location: Little Rock
Posted: Tue Mar 27, 2012 1:57 Post subject:
hiazle wrote:
Do you have multiple drives connected to the router? If so, I might just try the latest build.
USB is hub technology, AFAIK you can hook up a hub to any USB port and use multiple devices - even drives. On any of my 1 port units i have done this many times with no problems. I don't currently use multiple drives or any other USB devices as i don't need them anymore. _________________ Wireless N Config | Linking Routers | DD-WRT Wiki | DD-WRT Builds | Peacock - Broadcom FAQ
Is there any major reason why 16795 is recommended over the latest 18777 for the WRT160NL ?
I have been running the latest builds for the past 3 or 4 and have no problems with any of them
Past 3 builds have been ok with the 160nl, and if you notice those past 3 builds have come out pretty much back to back from each other date wise, before those past 3 builds though - after 16785 the image became to big thus bricked the unit, and that is why i still recommended 16785. hope that answers your question.
Thanks for that, I guess I got lucky and skipped the builds that were too big, I was running the build that the main router database gives out when you enter the router name into the search bar, then once registering on the forums, I found the FTP
dumb luck !
I guess using the USB2.0 to RS232 TTL Module PL2303 would unbrick it again though?
(Old SamKnows monitoring router I unlocked the same way) _________________ TPLINK TL-WR2543ND (5GHz)
WRT160NL (2.4GHz)
Do you have multiple drives connected to the router? If so, I might just try the latest build.
USB is hub technology, AFAIK you can hook up a hub to any USB port and use multiple devices - even drives. On any of my 1 port units i have done this many times with no problems. I don't currently use multiple drives or any other USB devices as i don't need them anymore.
It looks like there is a bug in the mounting logic in 16785. For some reason, when I connected more than one drive, only the first one was mounted to /mnt.
With the latest (18777), the first partition of every drive is mounted to /mnt/sd?_part1. I have to manually mount the other partitions in the startup script like this:
Code:
if [ ! -d /tmp/mnt/sda_part3 ]; then
mkdir /tmp/mnt/sda_part3
fi
mount /dev/sda3 /tmp/mnt/sda_part3
Once mounted, NAS seems to work. So, in essence, 18777 is not quite perfect, but it works.
Thanks for the link. It still does not work in 16785 because the mount points are different from what the script expects.
Well, then it is the script that isn't compatible with svn16785, is probably written for a much earlier version.
Scripts are made for editing - go do it! _________________ Kernel panic: Aiee, killing interrupt handler!
Thanks for the link. It still does not work in 16785 because the mount points are different from what the script expects.
Well, then it is the script that isn't compatible with svn16785, is probably written for a much earlier version.
Scripts are made for editing - go do it!
Thanks for the tip! I kept getting error "Invalid argument" when trying to execute the "mount" command, so I gave up and flashed the latest build (18777) which seems to work well so far, except for the swap partition which is not automatically mounted.
I tried the following:
Code:
root@DDWRT root $ busybox swapon /dev/sda2
swapon: applet not found
root@DDWRT root $ swapon /dev/sda2
swapon: /dev/sda2: Function not implemented
root@DDWRT root $ opkg install swap-utils
Package swap-utils (2.13.0.1-4) installed in root is up to date.
root@DDWRT root $ mkswap /dev/sda2
Setting up swapspace version 1, size = 268431 kB
no label, UUID=b2cc3712-cf35-4810-a609-76dc04f180d8
root@DDWRT root $ swapon
usage: swapon [-hV]
swapon -a [-e] [-v]
swapon [-v] [-p priority] special|LABEL=volume_name ...
swapon [-s]
root@DDWRT root $ swapon -s
swapon: /proc/swaps: No such file or directory