Okay, I flashed my Asus WL-520gu with dd-wrt.v24-9973_NEWD_mini_usb.bin; I am getting the same symptoms as I did with v24finalnokaidusb4m9517.bin that bkmo uploaded. I tested with two different USB keys, a 256M Linkyo and a 4G Sandisk Cruzer with the same results. The device is recognized, and I can mount a partition from it, but after reading a few files (I did a wc *), the USB light goes out and I start getting I/O errors.
dmesg says this:
scsi1 : SCSI emulation for USB Mass Storage devices
Vendor: SanDisk Model: U3 Cruzer Micro Rev: 3.27
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sdb at scsi1, channel 0, id 0, lun 0
SCSI device sdb: 8027790 512-byte hdwr sectors (4110 MB)
sdb: Write Protect is off
/dev/scsi/host1/bus0/target0/lun0: p1 p2 p3
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
VFS: Disk change detected on device 08:00
/dev/scsi/host0/bus0/target0/lun0: I/O error: dev 08:00, sector 0
I/O error: dev 08:00, sector 0
SQUASHFS error: Can't find a SQUASHFS superblock on sd(8,17)
SQUASHFS error: Can't find a SQUASHFS superblock on sd(8,18)
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
SQUASHFS error: Can't find a SQUASHFS superblock on sd(8,18)
usb-ohci.c: OHCI Unrecoverable Error, controller usb-00:03.0 disabled
I can rmmod and insmod the usb-ohci, and then I can remount the USB device, but the problem persists. If I try to read from the partition using dd if=part1 of=/dev/null or cat part1 > /dev/null, the router reboots.
Okay, here's some more info: I decided to try some other USB devices: SDHC card reader, IDE drive in a USB enclosure, USB floppy, and a USB 1.1 hub with a flash drive plugged into it. The results were similar with all of these devices (the hub was recognized, and the thumb drive when it was plugged into the hub).
The only device that was a little different from the rest was the floppy -- it crashed the ohci driver before I could even mount it.
Eko:
I got the printer to work with the WL-520GU. But as soon as the router is rebooted it stops recognizing the printer. After that if the printer is turned OFF and ON it will recognize the printer again.
I attached a picture when it begins to recognize the printer after the printer is rebooted.
Well, the good news is that USB2.0 isn't crashing the router any more. I tested 5 different USB keys from 4 different manufacturers and two IDE/USB disk drives. FAT32 file systems can get corrupted from large data transfers; ext2 and ext3 file systems are much more stable -- I was only able to break an ext2 file system on a thumb drive once, and was able to recover it via fsck on a linux notebook.
Read speeds ranged from 3-4MB/sec for the thumb drives and 8-9MB/sec for the disk drives; CPU util was 100% during any sustained read/write to the USB devices.
I was able to get the SCSI driver to lock up with two of the thumb drives using dd if=partXXX of=/dev/null, possibly due to bad flash blocks that mkfs had mapped out.
My USB floppy wasn't recognized, but at least the router didn't lock up over it like before.
It looks like this version doesn't have an ext2 kernel module in the root file system; I've attached one that you can try (scp it to your router and do "insmod ext2.o" to install it). Presumably this is something that can be included in subsequent TNG builds.
I´ve flashed my Asus WL-500g Premium v2 with the new "mini" version, using a USB drive "Kingston Data Traveler 2.0" and it seems to work fine (I´ve only tested vfat unit).
Apart from the rebooting problem, I had another one with the "mega" version I was using before. Very often, I couldn't mount the USB unit, it seemed like if it was not detected (the mounting path ended at "/dev/scsi" no "host", "bus", "target"...). I had to reboot the router several times and hope the unit was detected correctly, now, with the new test version, it doesn´t happen anymore.
Will this fix be ported to the "mega" version soon?
Last edited by aag_ddwrt on Tue Aug 19, 2008 20:11; edited 1 time in total
not detected (the mounting path ended at "/dev/scsi" no "host", "bus", "target"...). I had to reboot the
Hi!
Seems, that something is wrong w usb drivers.
1-th, inspect output of 'dmesg' command, see, are drivers loaded, is usb-storage device detected etc.
regards,
Janis
I've checked the "dmesg" output, but it doesn't help very much. I attach the output just in case it can help somebody.
The version I am using, V24 SP1-mega version, is behaving kind of erratically, sometimes it seems the USB drive is not detected ("mesg2" file attached), but sometimes the drive is detected ("mesg1"), although, even in this case, most times I cannot mount it either. It's just a matter of luck sometimes I can mount it and sometimes I can't.
Anyway, as I said before, the "mini" version in this post seems to work fine.
The new mini version continues to work well for me. I was able to install samba2 from optware onto a USB stick and share it to the network; next is to try the same with a small 2.5" IDE drive.
