NSLU2-Linux
view · edit · print · history

Unslung.KnownProblems History

Hide minor edits - Show changes to markup

June 28, 2008, at 04:37 PM by Bermuda -- Spelling Bermuda
Changed lines 17-18 from:
  • Unslung is not aware of the 2007 changes to Daylight Savings Time affecting users in the United States, Canada, and Burmuda. Unslung uses the timezone information from the Linksys firmware, which has not been updated to include the new DST info passed into law by the Energy Policy Act of 2005. Starting in 2007, DST will run from the second Sunday in March to the first Sunday in November, extending the total time period for DST by 4 weeks. During these 4 weeks, the date/time information used and displayed by the Linksys firmware and by Unslung will remain on standard time instead of DST. Brian Zhou mentions a way to fix this problem: http://www.nslu2-linux.org/wiki/Unslung/TimeZoneUpdate
to:
  • Unslung is not aware of the 2007 changes to Daylight Savings Time affecting users in the United States, Canada, and Bermuda. Unslung uses the timezone information from the Linksys firmware, which has not been updated to include the new DST info passed into law by the Energy Policy Act of 2005. Starting in 2007, DST will run from the second Sunday in March to the first Sunday in November, extending the total time period for DST by 4 weeks. During these 4 weeks, the date/time information used and displayed by the Linksys firmware and by Unslung will remain on standard time instead of DST. Brian Zhou mentions a way to fix this problem: http://www.nslu2-linux.org/wiki/Unslung/TimeZoneUpdate
May 18, 2008, at 10:20 AM by maisondouf --
May 18, 2008, at 10:18 AM by maisondouf --
Changed lines 20-21 from:
to:
December 31, 2007, at 01:46 AM by mwester -- Note that also applies to 6.10-beta
Changed lines 5-6 from:

Unslung 6.8

to:

Unslung 6.8-beta & Unslung 6.10-beta

November 21, 2007, at 07:18 PM by mkohler --
Changed lines 11-12 from:
  • There have been a number of reports of difficulties formatting certain types of devices with Unslung 6.8-beta. Generally, these devices seem to be large disks (where "large" seems to be drives greater than 250GB in size). These problems include the inability to format the drives with the Linksys Web GUI, and may also include the inability to "fsck" the filesystems at boot, and other problems. There have also been verified cases of select USB flash devices that fail to format with Unslung 6.8-beta. The problem description is rather vague -- which is part of the problem (as soon as the problem is better-defined, a solution may be easier to find). One case, involving a Sandisk Mini Cruzer 1.0GByte flash device, has been reproduced, and a workaround has been documented on the Unslung.FailedFormatFix page.
to:
  • There have been a number of reports of difficulties formatting certain types of devices with Unslung 6.8-beta. Generally, these devices seem to be large disks (where "large" seems to be drives greater than 250GB in size). These problems include the inability to format the drives with the Linksys Web GUI, and may also include the inability to "fsck" the filesystems at boot, and other problems. One workaround to this problem is to format the "large disk" with fat32 using the disk manufacturer's disk formatting utility. After this is complete, reformat the "large disk" using the Linksys Web GUI. There have also been verified cases of select USB flash devices that fail to format with Unslung 6.8-beta. The problem description is rather vague -- which is part of the problem (as soon as the problem is better-defined, a solution may be easier to find). One case, involving a Sandisk Mini Cruzer 1.0GByte flash device, has been reproduced, and a workaround has been documented on the Unslung.FailedFormatFix page.
September 30, 2007, at 10:59 PM by marceln -- Added buggy ntfs driver
Added lines 22-23:
  • The ntfs driver hangs the slug under medium to heavy write access.
July 08, 2007, at 02:48 AM by Jeremy Jefferson -- U3 Removal Link
Changed lines 7-8 from:
  • Unslung does not support U3-enabled USB flash devices. U3 USB flash devices do not identify themselves as standard mass storage devices. You must use the flash devices vendor's utility to disable the U3 functionality and return it to a standard USB mass storage mode before you can use the device with Unslung. Note that this problem is not limited to Unslung firmware; U3 devices are problematic with the native Linksys firmware (and many other systems) as well. (The presence of a U3 device can usually be determined by examining the output of the "dmesg" command in Unslung -- a U3 device will identify itself as a CDROM as well as the standard device.)
to:
  • Unslung does not support U3-enabled USB flash devices. U3 USB flash devices do not identify themselves as standard mass storage devices. You must use the flash devices vendor's utility to disable the U3 functionality and return it to a standard USB mass storage mode before you can use the device with Unslung. Note that this problem is not limited to Unslung firmware; U3 devices are problematic with the native Linksys firmware (and many other systems) as well. (The presence of a U3 device can usually be determined by examining the output of the "dmesg" command in Unslung -- a U3 device will identify itself as a CDROM as well as the standard device.) HowTo.RemoveU3
June 11, 2007, at 10:22 PM by mwester -- Updated the text for clarity, and removed pre-5.5 history
Changed lines 7-14 from:
  • Unslung does not support U3-enabled USB flash devices. U3 USB flash devices do not identify themselves as standard mass storage devices. You must use the flash devices vendor's utility to disable the U3 functionality and return it to a standard USB mass storage mode before you can use the device with Unslung. Note that this problem is not limited to Unslung firmware; U3 devices are problematic with the native Linksys firmware (and many other systems) as well.
  • The README erroneously states that the smallest USB flash device that is supported is 256MB. In fact, due to changes in the partition sizes used by the Linksys firmware, the smallest USB flash device that can be formatted by the Web GUI is 512MB.
  • There have been a number of reports of difficulties using "large" drives with Unslung 6.8-beta (where "large" seems to be drives greater than 250GB in size). These problems include the inability to format the drives with the Linksys Web GUI, and may also include the inability to "fsck" the filesystems at boot, and other problems. The problem description is rather vague -- which is part of the problem (as soon as the problem is better-defined, a solution may be easier to find).
Suggestion: Try formatting the drive in a Windows machine as NTFS, the Slug may then able to format the drive.
to:
  • Unslung does not support U3-enabled USB flash devices. U3 USB flash devices do not identify themselves as standard mass storage devices. You must use the flash devices vendor's utility to disable the U3 functionality and return it to a standard USB mass storage mode before you can use the device with Unslung. Note that this problem is not limited to Unslung firmware; U3 devices are problematic with the native Linksys firmware (and many other systems) as well. (The presence of a U3 device can usually be determined by examining the output of the "dmesg" command in Unslung -- a U3 device will identify itself as a CDROM as well as the standard device.)
  • The README erroneously states that the smallest USB flash device that is supported is 256MB. In fact, due to changes in the partition sizes used by the Linksys firmware, the smallest USB flash device that can be formatted by the Web GUI is 512MB. If you must use a smaller device, a (non-trivial) technique for doing so is documented on the wiki.
  • There have been a number of reports of difficulties formatting certain types of devices with Unslung 6.8-beta. Generally, these devices seem to be large disks (where "large" seems to be drives greater than 250GB in size). These problems include the inability to format the drives with the Linksys Web GUI, and may also include the inability to "fsck" the filesystems at boot, and other problems. There have also been verified cases of select USB flash devices that fail to format with Unslung 6.8-beta. The problem description is rather vague -- which is part of the problem (as soon as the problem is better-defined, a solution may be easier to find). One case, involving a Sandisk Mini Cruzer 1.0GByte flash device, has been reproduced, and a workaround has been documented on the Unslung.FailedFormatFix page.
Deleted lines 64-118:

Unslung 4.20

The Maintenance Mode code is Unslung 4.20 is completely broken. This is a good thing, cause it caused us to move to RedBoot Upgrade Mode instead (which is far more reliable, and will be used for all future firmware versions).

Unslung 3.18

As far as we know, all major problems in Unslung 3.18 are a part of the Linksys legacy.

Power off issues

Sometimes (often) the slug does not shut down properly when pressing the power button. It beeps, but does not power off. Similar problems are also seen when running halt from the command line. It seems that Linksys has modified the Busybox halt (reasonable assumption from looking at the binary), but has not released the modifications in line with the Busybox GPL license (if this is indeed the case, Linksys is in violation of GPL). Update: Linksys does, in fact, release the Busybox sources; they are compliant with the GPL.

Large file issues

There are problems transfering large files (larger than 4GB). This bug is fixed in Linksys firmware 2.3R29, and therefore should be fixed in Unslung 5.x (which is based on 2.3R29).

I also expect some bugs when transfering multiple 700 mo files.(With 2 different NSLU2/Hardware). Even with the 5.x release. The workaround (for me) is simple... only transfer one of these 700 mo files at time or transfer using a FTP/SSH client. (Line From KGP / Nuage). And don't access the Web Interface. It MIGHT be related to the relative low memory of the NSLU2.

USB issues

There are a number of problems with USB in the kernel. Known problems are:

  • Hubs not working at all or only certain types of hubs.
  • Some disks not being picked up by the USB storage unless being present at boot up.
  • CD/DVD/tape devices not being avilable for mounting - this is because the kernel does not support devfs. Devfs support is in Unslung 4.x.
  • Only a limited number of devices may be hooked up. This is probably a bug in the Linksys USB high speed driver. The error messages are typically like this:

(:table border=0 width=90% bgcolor=#eeffee:) (:cell:)

 Mar 22 16:24:38 Naseem hub.c: new USB device 00:01.2-1.2, assigned address 4
 Mar 22 16:24:38 Naseem usb.c: not enough configurations
 Mar 22 16:24:38 Naseem hub.c: new USB device 00:01.2-1.2, assigned address 5
 Mar 22 16:24:38 Naseem usb.c: not enough configurations

(:tableend:)

  • Connecting more than two devices may cause local kernel crashes while disconnecting devices or accessing /proc/bus/usb-files, but doesn't seem to bring the system down completely. These crashes are logged like this:

(:table border=0 width=90% bgcolor=#eeffee:) (:cell:)

 Mar  6 13:36:53 Naseem Internal error: Oops: 0
 Mar  6 13:36:53 Naseem CPU: 0
 Mar  6 13:36:53 Naseem pc : [<c01259d4>]    lr : [<c0125acc>]    Tainted: P
 Mar  6 13:36:53 Naseem sp : c03a5f68  ip : 60000013  fp : 00000000
 Mar  6 13:36:53 Naseem r10: 00000018  r9 : c02723e0  r8 : 0000000d
 Mar  6 13:36:53 Naseem r7 : c1e72600  r6 : c1e947c0  r5 : c01e3d8c  r4 :  00000000
 Mar  6 13:36:53 Naseem r3 : 534c4f54  r2 : c1e72604  r1 : c1e947c0  r0 : c01c1cb0
 Mar  6 13:36:53 Naseem Flags: NzCv?  IRQs? on  FIQs? on  Mode SVC_32  Segment kernel
 Mar  6 13:36:53 Naseem Control: 39FF  Table: 015B4000  DAC: 0000001D
 Mar  6 13:36:53 Naseem Process khubd (pid: 8, stack limit = 0xc03a4368)
 Mar  6 13:36:53 Naseem Stack: (0xc03a5f68 to 0xc03a6000)
 ...

(:tableend:)

Tips:

  • If your hubs works, use the first port on the hub for you disk.
  • Connect your hub to the first USB port on the NSLU2 (marked "disk 1")

bob_tm

May 18, 2007, at 01:27 PM by mwester -- formatting
Changed lines 7-8 from:
  • Unslung does not appear to respond well to "U3" USB flash devices. U3 USB flash devices do not identify themselves as standard mass storage devices. You must use the flash devices vendor's utility to disable the U3 functionality and return it to a standard USB mass storage mode before you can use the device with Unslung. Note that this problem is not limited to Unslung firmware; U3 devices are problematic with the native Linksys firmware (and many other systems) as well.
to:
  • Unslung does not support U3-enabled USB flash devices. U3 USB flash devices do not identify themselves as standard mass storage devices. You must use the flash devices vendor's utility to disable the U3 functionality and return it to a standard USB mass storage mode before you can use the device with Unslung. Note that this problem is not limited to Unslung firmware; U3 devices are problematic with the native Linksys firmware (and many other systems) as well.
May 18, 2007, at 01:26 PM by mwester -- Add note on U3 devices
Added lines 7-8:
  • Unslung does not appear to respond well to "U3" USB flash devices. U3 USB flash devices do not identify themselves as standard mass storage devices. You must use the flash devices vendor's utility to disable the U3 functionality and return it to a standard USB mass storage mode before you can use the device with Unslung. Note that this problem is not limited to Unslung firmware; U3 devices are problematic with the native Linksys firmware (and many other systems) as well.
March 11, 2007, at 02:40 PM by na -- new link
Changed lines 17-18 from:
  • Unslung is not aware of the 2007 changes to Daylight Savings Time affecting users in the United States, Canada, and Burmuda. Unslung uses the timezone information from the Linksys firmware, which has not been updated to include the new DST info passed into law by the Energy Policy Act of 2005. Starting in 2007, DST will run from the second Sunday in March to the first Sunday in November, extending the total time period for DST by 4 weeks. During these 4 weeks, the date/time information used and displayed by the Linksys firmware and by Unslung will remain on standard time instead of DST. Brian Zhou mentions a way to fix this problem: http://www.nslu2-linux.org/wiki/Profiles/BrianZhou
to:
  • Unslung is not aware of the 2007 changes to Daylight Savings Time affecting users in the United States, Canada, and Burmuda. Unslung uses the timezone information from the Linksys firmware, which has not been updated to include the new DST info passed into law by the Energy Policy Act of 2005. Starting in 2007, DST will run from the second Sunday in March to the first Sunday in November, extending the total time period for DST by 4 weeks. During these 4 weeks, the date/time information used and displayed by the Linksys firmware and by Unslung will remain on standard time instead of DST. Brian Zhou mentions a way to fix this problem: http://www.nslu2-linux.org/wiki/Unslung/TimeZoneUpdate
March 11, 2007, at 02:23 PM by na --
Changed lines 17-18 from:
  • Unslung is not aware of the 2007 changes to Daylight Savings Time affecting users in the United States, Canada, and Burmuda. Unslung uses the timezone information from the Linksys firmware, which has not been updated to include the new DST info passed into law by the Energy Policy Act of 2005. Starting in 2007, DST will run from the second Sunday in March to the first Sunday in November, extending the total time period for DST by 4 weeks. During these 4 weeks, the date/time information used and displayed by the Linksys firmware and by Unslung will remain on standard time instead of DST. Brian Zhou mentions a DST patch: [http://www.nslu2-linux.org/wiki/Profiles/BrianZhou]
to:
  • Unslung is not aware of the 2007 changes to Daylight Savings Time affecting users in the United States, Canada, and Burmuda. Unslung uses the timezone information from the Linksys firmware, which has not been updated to include the new DST info passed into law by the Energy Policy Act of 2005. Starting in 2007, DST will run from the second Sunday in March to the first Sunday in November, extending the total time period for DST by 4 weeks. During these 4 weeks, the date/time information used and displayed by the Linksys firmware and by Unslung will remain on standard time instead of DST. Brian Zhou mentions a way to fix this problem: http://www.nslu2-linux.org/wiki/Profiles/BrianZhou
March 11, 2007, at 02:22 PM by na -- DST 2007 patch listed
Changed lines 17-19 from:
  • Unslung is not aware of the 2007 changes to Daylight Savings Time affecting users in the United States, Canada, and Burmuda. Unslung uses the timezone information from the Linksys firmware, which has not been updated to include the new DST info passed into law by the Energy Policy Act of 2005. Starting in 2007, DST will run from the second Sunday in March to the first Sunday in November, extending the total time period for DST by 4 weeks. During these 4 weeks, the date/time information used and displayed by the Linksys firmware and by Unslung will remain on standard time instead of DST.
    ****So not even a patch?!?!****
to:
  • Unslung is not aware of the 2007 changes to Daylight Savings Time affecting users in the United States, Canada, and Burmuda. Unslung uses the timezone information from the Linksys firmware, which has not been updated to include the new DST info passed into law by the Energy Policy Act of 2005. Starting in 2007, DST will run from the second Sunday in March to the first Sunday in November, extending the total time period for DST by 4 weeks. During these 4 weeks, the date/time information used and displayed by the Linksys firmware and by Unslung will remain on standard time instead of DST. Brian Zhou mentions a DST patch: [http://www.nslu2-linux.org/wiki/Profiles/BrianZhou]
March 11, 2007, at 12:40 PM by jbf --
Changed lines 17-18 from:
  • Unslung is not aware of the 2007 changes to Daylight Savings Time affecting users in the United States, Canada, and Burmuda. Unslung uses the timezone information from the Linksys firmware, which has not been updated to include the new DST info passed into law by the Energy Policy Act of 2005. Starting in 2007, DST will run from the second Sunday in March to the first Sunday in November, extending the total time period for DST by 4 weeks. During these 4 weeks, the date/time information used and displayed by the Linksys firmware and by Unslung will remain on standard time instead of DST. <font color=red>So not even a patch??</font>
to:
  • Unslung is not aware of the 2007 changes to Daylight Savings Time affecting users in the United States, Canada, and Burmuda. Unslung uses the timezone information from the Linksys firmware, which has not been updated to include the new DST info passed into law by the Energy Policy Act of 2005. Starting in 2007, DST will run from the second Sunday in March to the first Sunday in November, extending the total time period for DST by 4 weeks. During these 4 weeks, the date/time information used and displayed by the Linksys firmware and by Unslung will remain on standard time instead of DST.
    ****So not even a patch?!?!****
March 11, 2007, at 12:39 PM by jbf --
Changed lines 17-18 from:
  • Unslung is not aware of the 2007 changes to Daylight Savings Time affecting users in the United States, Canada, and Burmuda. Unslung uses the timezone information from the Linksys firmware, which has not been updated to include the new DST info passed into law by the Energy Policy Act of 2005. Starting in 2007, DST will run from the second Sunday in March to the first Sunday in November, extending the total time period for DST by 4 weeks. During these 4 weeks, the date/time information used and displayed by the Linksys firmware and by Unslung will remain on standard time instead of DST.
to:
  • Unslung is not aware of the 2007 changes to Daylight Savings Time affecting users in the United States, Canada, and Burmuda. Unslung uses the timezone information from the Linksys firmware, which has not been updated to include the new DST info passed into law by the Energy Policy Act of 2005. Starting in 2007, DST will run from the second Sunday in March to the first Sunday in November, extending the total time period for DST by 4 weeks. During these 4 weeks, the date/time information used and displayed by the Linksys firmware and by Unslung will remain on standard time instead of DST. <font color=red>So not even a patch??</font>
February 04, 2007, at 05:06 PM by mwester -- correct GPL concern comment
Changed lines 74-75 from:

Sometimes (often) the slug does not shut down properly when pressing the power button. It beeps, but does not power off. Similar problems are also seen when running halt from the command line. It seems that Linksys has modified the Busybox halt (reasonable assumption from looking at the binary), but has not released the modifications in line with the Busybox GPL license (if this is indeed the case, Linksys is in violation of GPL).

to:

Sometimes (often) the slug does not shut down properly when pressing the power button. It beeps, but does not power off. Similar problems are also seen when running halt from the command line. It seems that Linksys has modified the Busybox halt (reasonable assumption from looking at the binary), but has not released the modifications in line with the Busybox GPL license (if this is indeed the case, Linksys is in violation of GPL). Update: Linksys does, in fact, release the Busybox sources; they are compliant with the GPL.

February 04, 2007, at 04:52 PM by mwester -- formatting fix
Changed lines 10-11 from:

Suggestion: Try formatting the drive in a Windows machine as NTFS, the Slug may then able to format the drive.

to:
Suggestion: Try formatting the drive in a Windows machine as NTFS, the Slug may then able to format the drive.
February 04, 2007, at 04:51 PM by mwester -- Added DST issue for Unslung
Changed lines 10-11 from:

-- Try formatting the drive in a Windows machine as NTFS, the Slug may then able to format the drive.

to:

Suggestion: Try formatting the drive in a Windows machine as NTFS, the Slug may then able to format the drive.

Added lines 16-17:
  • Unslung is not aware of the 2007 changes to Daylight Savings Time affecting users in the United States, Canada, and Burmuda. Unslung uses the timezone information from the Linksys firmware, which has not been updated to include the new DST info passed into law by the Energy Policy Act of 2005. Starting in 2007, DST will run from the second Sunday in March to the first Sunday in November, extending the total time period for DST by 4 weeks. During these 4 weeks, the date/time information used and displayed by the Linksys firmware and by Unslung will remain on standard time instead of DST.
Changed lines 22-23 from:

Just to expand on the above issue;

to:

Just to expand on the above issues:

January 28, 2007, at 08:20 AM by Prenexus -- Try formatting in NTFS for solving >250GB issue
Changed lines 10-11 from:
to:

-- Try formatting the drive in a Windows machine as NTFS, the Slug may then able to format the drive.

January 05, 2007, at 12:48 AM by mwester -- Formatting
Changed lines 19-27 from:

[-Just to expand on the above issue;

  • Following reboot of the NSLU2 a share created on disk1 will retain the correct name and clients will be able to reconnect without issue. A 'dummy' share with ~1 mapped to a non-existent directory on disk2 will be created but this can be ignored. It isn't possible for a client to connect to this 'dummy' share.
  • On reboot R63 mangles any shares previously created on disk2 by rewriting /etc/share.info and /etc/samba/smb.conf. The original share will be remapped to point at a non-existent directory on disk1 and a new share with ~1 created and correctly mapped to disk2. This breaks client connectivity. To reconnect, clients must now use the share name with a ~1 appended to connect to the disk2 share. It isn't possible for clients to connect to the remapped 'dummy' original share.
  • Following a reboot the dummy shares created by R63 will be shown in red in the web interface.

So, the bottom line is that if you build shares on disk2, expect to reconfigure client connectivity or bypass via HowTo.UseSharesOnTwoNativeDisksInUnslung68. This isn't a major problem as in all cases the NSLU2 maps data to the correct drive but it is irritating. - richdunlop-]

to:

Just to expand on the above issue;

* Following reboot of the NSLU2 a share created on disk1 will retain the correct name and clients will be able to reconnect without issue. A 'dummy' share with ~1 mapped to a non-existent directory on disk2 will be created but this can be ignored. It isn't possible for a client to connect to this 'dummy' share.

* On reboot R63 mangles any shares previously created on disk2 by rewriting /etc/share.info and /etc/samba/smb.conf. The original share will be remapped to point at a non-existent directory on disk1 and a new share with ~1 created and correctly mapped to disk2. This breaks client connectivity. To reconnect, clients must now use the share name with a ~1 appended to connect to the disk2 share. It isn't possible for clients to connect to the remapped 'dummy' original share.

* Following a reboot the dummy shares created by R63 will be shown in red in the web interface.

So, the bottom line is that if you build shares on disk2, expect to reconfigure client connectivity or bypass via HowTo.UseSharesOnTwoNativeDisksInUnslung68. This isn't a major problem as in all cases the NSLU2 maps data to the correct drive but it is irritating. - richdunlop

January 05, 2007, at 12:46 AM by mwester -- Minor formatting
Changed lines 19-20 from:

Just to expand on the above issue;

to:

[-Just to expand on the above issue;

Changed line 27 from:

So, the bottom line is that if you build shares on disk2, expect to reconfigure client connectivity or bypass via HowTo.UseSharesOnTwoNativeDisksInUnslung68. This isn't a major problem as in all cases the NSLU2 maps data to the correct drive but it is irritating. - richdunlop

to:

So, the bottom line is that if you build shares on disk2, expect to reconfigure client connectivity or bypass via HowTo.UseSharesOnTwoNativeDisksInUnslung68. This isn't a major problem as in all cases the NSLU2 maps data to the correct drive but it is irritating. - richdunlop-]

January 05, 2007, at 12:41 AM by mwester -- Highlight the key terms
Changed lines 7-15 from:
  • The README erroneously states that the smallest USB flash device that is supported is 256MB. In fact, due to changes in the partition sizes used by the Linksys firmware, the smallest USB flash device that can be formatted by the Web GUI is 512MB.
  • There have been a number of reports of difficulties using "large" drives with Unslung 6.8-beta (where "large" seems to be drives greater than 250GB in size). These problems include the inability to format the drives with the Linksys Web GUI, and may also include the inability to "fsck" the filesystems at boot, and other problems. The problem description is rather vague -- which is part of the problem (as soon as the problem is better-defined, a solution may be easier to find).
  • Some users have reported that after unslinging, the device is unable to automatically mount FAT or NTFS disks that previously the Linksys R63 firmware was able to mount. An additional symptom is that on the Web GUI, the FAT or NTFS drive is displayed as "Not Formatted" even though the drive is correctly formatted and can be mounted and used with the standard Linksys R63 firmware. This problem may be due to selecting Language Support other than "USA (437)" on the Web GUI, Administration->System page. See Unslung.UnslungLanguageSupport for more information on this.
  • The "Administration->Advanced->Upgrade" page in Unslung 6.8-beta is exactly the same as the same page in the Linksys R63 firmware. However, the documentation clearly states that this page cannot be used to upgrade or install firmware. You must use Redboot Upgrade Mode to install firmware, be it Unslung or Linksys firmware. See HowTo.InstallUnslungFirmware for more information.
  • Creating a share, or adding a user with a private share, via the Linksys Web GUI can create two shares: one with the original name, the other with the original name with "~1" appended -- each is associated with a different drive in a two-drive NSLU2 configuration. Since the share directory only actually exists on one of the two drives, only one of the two shares will work. This is not an Unslung 6.x bug -- this is actually completely consistent with the (strange) behavior of the native Linksys R63 firmware. Since the shares are managed by Linksys code for which we have no source code, this is not something that can be changed in Unslung.
to:
  • The README erroneously states that the smallest USB flash device that is supported is 256MB. In fact, due to changes in the partition sizes used by the Linksys firmware, the smallest USB flash device that can be formatted by the Web GUI is 512MB.
  • There have been a number of reports of difficulties using "large" drives with Unslung 6.8-beta (where "large" seems to be drives greater than 250GB in size). These problems include the inability to format the drives with the Linksys Web GUI, and may also include the inability to "fsck" the filesystems at boot, and other problems. The problem description is rather vague -- which is part of the problem (as soon as the problem is better-defined, a solution may be easier to find).
  • Some users have reported that after unslinging, the device is unable to automatically mount FAT or NTFS disks that previously the Linksys R63 firmware was able to mount. An additional symptom is that on the Web GUI, the FAT or NTFS drive is displayed as "Not Formatted" even though the drive is correctly formatted and can be mounted and used with the standard Linksys R63 firmware. This problem may be due to selecting Language Support other than "USA (437)" on the Web GUI, Administration->System page. See Unslung.UnslungLanguageSupport for more information on this.
  • The "Administration->Advanced->Upgrade" page in Unslung 6.8-beta is exactly the same as the same page in the Linksys R63 firmware. However, the documentation clearly states that this page cannot be used to upgrade or install firmware. You must use Redboot Upgrade Mode to install firmware, be it Unslung or Linksys firmware. See HowTo.InstallUnslungFirmware for more information.
  • Creating a share, or adding a user with a private share, via the Linksys Web GUI can create two shares: one with the original name, the other with the original share name with "~1" appended -- each is associated with a different drive in a two-drive NSLU2 configuration. Since the share directory only actually exists on one of the two drives, only one of the two shares will work. This is not an Unslung 6.x bug -- this is actually completely consistent with the (strange) behavior of the native Linksys R63 firmware. Since the shares are managed by Linksys code for which we have no source code, this is not something that can be changed in Unslung.
December 18, 2006, at 12:35 AM by mwester -- Updated with USB flash size and large disk size problems
Added lines 7-10:
  • The README erroneously states that the smallest USB flash device that is supported is 256MB. In fact, due to changes in the partition sizes used by the Linksys firmware, the smallest USB flash device that can be formatted by the Web GUI is 512MB.
  • There have been a number of reports of difficulties using "large" drives with Unslung 6.8-beta (where "large" seems to be drives greater than 250GB in size). These problems include the inability to format the drives with the Linksys Web GUI, and may also include the inability to "fsck" the filesystems at boot, and other problems. The problem description is rather vague -- which is part of the problem (as soon as the problem is better-defined, a solution may be easier to find).
November 24, 2006, at 11:16 AM by richdunlop -- Added a not about interface display of remapped shares.
Added lines 21-22:
  • Following a reboot the dummy shares created by R63 will be shown in red in the web interface.
November 24, 2006, at 11:13 AM by richdunlop --
Changed line 21 from:

So, the bottom line is that if you build shares on disk2, expect to reconfigure client connectivity or bypass via HowTo.UseSharesOnTwoNativeDisksInUnslung68. This isn't a major problem as in all cases the NSLU2 maps data to the correct drive but it is irritating.

to:

So, the bottom line is that if you build shares on disk2, expect to reconfigure client connectivity or bypass via HowTo.UseSharesOnTwoNativeDisksInUnslung68. This isn't a major problem as in all cases the NSLU2 maps data to the correct drive but it is irritating. - richdunlop

November 24, 2006, at 11:12 AM by richdunlop -- Added more detailed info regarding R63 share remapping on reboot.
Added lines 13-23:

Just to expand on the above issue;

  • Following reboot of the NSLU2 a share created on disk1 will retain the correct name and clients will be able to reconnect without issue. A 'dummy' share with ~1 mapped to a non-existent directory on disk2 will be created but this can be ignored. It isn't possible for a client to connect to this 'dummy' share.
  • On reboot R63 mangles any shares previously created on disk2 by rewriting /etc/share.info and /etc/samba/smb.conf. The original share will be remapped to point at a non-existent directory on disk1 and a new share with ~1 created and correctly mapped to disk2. This breaks client connectivity. To reconnect, clients must now use the share name with a ~1 appended to connect to the disk2 share. It isn't possible for clients to connect to the remapped 'dummy' original share.

So, the bottom line is that if you build shares on disk2, expect to reconfigure client connectivity or bypass via HowTo.UseSharesOnTwoNativeDisksInUnslung68. This isn't a major problem as in all cases the NSLU2 maps data to the correct drive but it is irritating.


April 25, 2006, at 07:46 PM by adriaan --
Changed line 12 from:
to:
April 25, 2006, at 07:45 PM by adriaan --
Changed line 12 from:
Bypass:
to:
April 25, 2006, at 07:42 PM by adriaan --
Changed line 12 from:
to:
Bypass:
April 16, 2006, at 09:36 PM by osas --
Changed lines 42-43 from:
to:

In order to be able to ssh in after a reboot, you may want to apply the hack in the /opt/etc/init.d/S51dropbear before starting dropbear.

April 16, 2006, at 02:15 AM by mwester -- added multiple share problem with R63
Changed lines 7-10 from:

Some users have reported that after unslinging, the device is unable to automatically mount FAT or NTFS disks that previously the Linksys R63 firmware was able to mount. An additional symptom is that on the Web GUI, the FAT or NTFS drive is displayed as "Not Formatted" even though the drive is correctly formatted and can be mounted and used with the standard Linksys R63 firmware. This problem may be due to selecting Language Support other than "USA (437)" on the Web GUI, Administration->System page. See Unslung.UnslungLanguageSupport for more information on this.

The "Administration->Advanced->Upgrade" page in Unslung 6.8-beta is exactly the same as the same page in the Linksys R63 firmware. However, the documentation clearly states that this page cannot be used to upgrade or install firmware. You must use Redboot Upgrade Mode to install firmware, be it Unslung or Linksys firmware. See HowTo.InstallUnslungFirmware for more information.

to:
  • Some users have reported that after unslinging, the device is unable to automatically mount FAT or NTFS disks that previously the Linksys R63 firmware was able to mount. An additional symptom is that on the Web GUI, the FAT or NTFS drive is displayed as "Not Formatted" even though the drive is correctly formatted and can be mounted and used with the standard Linksys R63 firmware. This problem may be due to selecting Language Support other than "USA (437)" on the Web GUI, Administration->System page. See Unslung.UnslungLanguageSupport for more information on this.
  • The "Administration->Advanced->Upgrade" page in Unslung 6.8-beta is exactly the same as the same page in the Linksys R63 firmware. However, the documentation clearly states that this page cannot be used to upgrade or install firmware. You must use Redboot Upgrade Mode to install firmware, be it Unslung or Linksys firmware. See HowTo.InstallUnslungFirmware for more information.
  • Creating a share, or adding a user with a private share, via the Linksys Web GUI can create two shares: one with the original name, the other with the original name with "~1" appended -- each is associated with a different drive in a two-drive NSLU2 configuration. Since the share directory only actually exists on one of the two drives, only one of the two shares will work. This is not an Unslung 6.x bug -- this is actually completely consistent with the (strange) behavior of the native Linksys R63 firmware. Since the shares are managed by Linksys code for which we have no source code, this is not something that can be changed in Unslung.
April 14, 2006, at 01:30 AM by mwester --
Added lines 9-10:

The "Administration->Advanced->Upgrade" page in Unslung 6.8-beta is exactly the same as the same page in the Linksys R63 firmware. However, the documentation clearly states that this page cannot be used to upgrade or install firmware. You must use Redboot Upgrade Mode to install firmware, be it Unslung or Linksys firmware. See HowTo.InstallUnslungFirmware for more information.

April 14, 2006, at 12:52 AM by mwester --
Changed lines 7-8 from:

Some users have reported that after unslinging, the device is unable to automatically mount FAT or NTFS disks that the Linksys R63 firmware was able to mount. On the Web GUI, the FAT or NTFS drive is displayed as "Not Formatted". This problem may be due to selecting Language Support other than "USA (437)" on the Web GUI, Administration->System page. See UnslungLanguageSupport for more information on this.

to:

Some users have reported that after unslinging, the device is unable to automatically mount FAT or NTFS disks that previously the Linksys R63 firmware was able to mount. An additional symptom is that on the Web GUI, the FAT or NTFS drive is displayed as "Not Formatted" even though the drive is correctly formatted and can be mounted and used with the standard Linksys R63 firmware. This problem may be due to selecting Language Support other than "USA (437)" on the Web GUI, Administration->System page. See Unslung.UnslungLanguageSupport for more information on this.

April 13, 2006, at 11:53 PM by mwester --
Changed lines 7-8 from:

<tbd>

to:

Some users have reported that after unslinging, the device is unable to automatically mount FAT or NTFS disks that the Linksys R63 firmware was able to mount. On the Web GUI, the FAT or NTFS drive is displayed as "Not Formatted". This problem may be due to selecting Language Support other than "USA (437)" on the Web GUI, Administration->System page. See UnslungLanguageSupport for more information on this.

April 12, 2006, at 09:16 PM by mwester -- Fixed line length format problem, added placeholder for 6.8
Added lines 5-8:

Unslung 6.8

<tbd>

Changed lines 34-35 from:
  1. To read about the difference between urandom and random go here: http://people.freebsd.org/~dougb/randomness.html
to:
  1. To read about the difference between urandom and random go here:
  2. http://people.freebsd.org/~dougb/randomness.html
Changed line 62 from:

(:table border=0 width=100% bgcolor=#eeffee:)

to:

(:table border=0 width=90% bgcolor=#eeffee:)

Changed line 70 from:

(:table border=0 width=100% bgcolor=#eeffee:)

to:

(:table border=0 width=90% bgcolor=#eeffee:)

November 16, 2005, at 10:30 PM by g -- added some of the known problems for unslung 5.5 and some workarounds
Added lines 5-34:

Unslung 5.5

Virtually all optware packages are broken because /opt/bin is not in the system path!! hack to fix:

 
# create /etc/profile
echo export PATH=/opt/local/bin:/opt/bin:$PATH:/opt/sbin:/opt/usr/bin:/opt/usr/sbin >/etc/profile
echo export LD_LIBRARY_PATH=/opt/lib >> /etc/profile
echo export TERMINFO=/opt/share/terminfo >> /etc/profile
echo alias ls='ls -F' >> /etc/profile
echo export PS1='\u@\h:\w\$ ' >> /etc/profile
# reload the new profile
. /etc/profile 

/dev/random blocks rather then giving random data as it is supposed to... this effects dropbear and other packages that need to generate keys... dropbear install hangs with the following message:

 
Will output 1024 bit rsa secret key to '/opt/etc/dropbear/dropbear_rsa_host_key'
Generating key, this may take a while...
Warning: Reading the random source seems to have blocked.
If you experience problems, you probably need to find a better entropy source.

hack to fix:

 
mv /dev/random /dev/random-blocks
ln -s /dev/urandom /dev/random
# To read about the difference between urandom and random go here: http://people.freebsd.org/~dougb/randomness.html

then reinstall dropbear or restart whatever process blocked trying to get data from random.

July 04, 2005, at 07:56 PM by KGP --
Changed lines 19-20 from:

I also expect some bugs when transfering multiple 700 mo files.(With 2 different NSLU2/Hardware). Even with the 5.x release. The workaround (for me) is simple... only transfer one of these 700 mo files at time or transfer using a FTP/SSH client. (Line From KGP / Nuage)

to:

I also expect some bugs when transfering multiple 700 mo files.(With 2 different NSLU2/Hardware). Even with the 5.x release. The workaround (for me) is simple... only transfer one of these 700 mo files at time or transfer using a FTP/SSH client. (Line From KGP / Nuage). And don't access the Web Interface. It MIGHT be related to the relative low memory of the NSLU2.

July 04, 2005, at 07:54 PM by KGP --
Added lines 19-20:

I also expect some bugs when transfering multiple 700 mo files.(With 2 different NSLU2/Hardware). Even with the 5.x release. The workaround (for me) is simple... only transfer one of these 700 mo files at time or transfer using a FTP/SSH client. (Line From KGP / Nuage)

June 14, 2005, at 12:05 PM by rwhitby --
Added lines 5-8:

Unslung 4.20

The Maintenance Mode code is Unslung 4.20 is completely broken. This is a good thing, cause it caused us to move to RedBoot Upgrade Mode instead (which is far more reliable, and will be used for all future firmware versions).

Changed lines 17-18 from:

There are problems transfering large files (larger than 4GB). This bug is fixed in Linksys firmware 2.3R29, but Linksys has not yet released the source code for their GPL code modifications for that firmware.

to:

There are problems transfering large files (larger than 4GB). This bug is fixed in Linksys firmware 2.3R29, and therefore should be fixed in Unslung 5.x (which is based on 2.3R29).

May 27, 2005, at 07:39 PM by williamwaggoner2003 -- minor grammar and typo fixes
Changed lines 3-4 from:

In all major software systems there are known issues. Some are easily fixed and some not so easily fixed. Unslung's commitment Linksys compatibility also restricts what can be fixed as not all Linksys SW for the NSLU2 is avilable in source form. This page will have some minor point as well as major sections describing workarounds. People resolving one or more of the major issues here will be regarded as heroes of the people and receive an embarrassing amount of praise.

to:

In all major software systems there are known issues. Some are easily fixed and some not so easily fixed. Unslung's commitment to Linksys compatibility also restricts what can be fixed as not all Linksys SW for the NSLU2 is available in source form. This page will have some minor points as well as major sections describing workarounds. People resolving one or more of the major issues here will be regarded as heroes of the people and receive an embarrassing amount of praise.

Changed line 28 from:
  • Connecting more than two devices may cause local kernel crashes, while disconnecting devices or accessing /proc/bus/usb-files, but doesn't seem to bring the system down completely. These crashes are logged like this:
to:
  • Connecting more than two devices may cause local kernel crashes while disconnecting devices or accessing /proc/bus/usb-files, but doesn't seem to bring the system down completely. These crashes are logged like this:
March 24, 2005, at 10:55 AM by bobtm --
Changed line 3 from:

In all major software systems there are known issues. Some are easily fixed and some not so easily fixed. Unslung's commitment Linksys compatibility also restricts what can be fixed as not all Linksys SW for the NSLU2 is avilable in source form. This page will have some minor point as well as major sections describing workarounds.

to:

In all major software systems there are known issues. Some are easily fixed and some not so easily fixed. Unslung's commitment Linksys compatibility also restricts what can be fixed as not all Linksys SW for the NSLU2 is avilable in source form. This page will have some minor point as well as major sections describing workarounds. People resolving one or more of the major issues here will be regarded as heroes of the people and receive an embarrassing amount of praise.

Added lines 7-14:

As far as we know, all major problems in Unslung 3.18 are a part of the Linksys legacy.

Power off issues

Sometimes (often) the slug does not shut down properly when pressing the power button. It beeps, but does not power off. Similar problems are also seen when running halt from the command line. It seems that Linksys has modified the Busybox halt (reasonable assumption from looking at the binary), but has not released the modifications in line with the Busybox GPL license (if this is indeed the case, Linksys is in violation of GPL).

Large file issues

There are problems transfering large files (larger than 4GB). This bug is fixed in Linksys firmware 2.3R29, but Linksys has not yet released the source code for their GPL code modifications for that firmware.

Deleted lines 20-21:
Added lines 28-44:
  • Connecting more than two devices may cause local kernel crashes, while disconnecting devices or accessing /proc/bus/usb-files, but doesn't seem to bring the system down completely. These crashes are logged like this:

table border=0 width=100% bgcolor=#eeffee? cell?

 Mar  6 13:36:53 Naseem Internal error: Oops: 0
 Mar  6 13:36:53 Naseem CPU: 0
 Mar  6 13:36:53 Naseem pc : [<c01259d4>]    lr : [<c0125acc>]    Tainted: P
 Mar  6 13:36:53 Naseem sp : c03a5f68  ip : 60000013  fp : 00000000
 Mar  6 13:36:53 Naseem r10: 00000018  r9 : c02723e0  r8 : 0000000d
 Mar  6 13:36:53 Naseem r7 : c1e72600  r6 : c1e947c0  r5 : c01e3d8c  r4 :  00000000
 Mar  6 13:36:53 Naseem r3 : 534c4f54  r2 : c1e72604  r1 : c1e947c0  r0 : c01c1cb0
 Mar  6 13:36:53 Naseem Flags: NzCv?  IRQs? on  FIQs? on  Mode SVC_32  Segment kernel
 Mar  6 13:36:53 Naseem Control: 39FF  Table: 015B4000  DAC: 0000001D
 Mar  6 13:36:53 Naseem Process khubd (pid: 8, stack limit = 0xc03a4368)
 Mar  6 13:36:53 Naseem Stack: (0xc03a5f68 to 0xc03a6000)
 ...

tableend?

March 22, 2005, at 04:04 PM by bobtm --
Added lines 12-22:
  • Only a limited number of devices may be hooked up. This is probably a bug in the Linksys USB high speed driver. The error messages are typically like this:

table border=0 width=100% bgcolor=#eeffee? cell?

 Mar 22 16:24:38 Naseem hub.c: new USB device 00:01.2-1.2, assigned address 4
 Mar 22 16:24:38 Naseem usb.c: not enough configurations
 Mar 22 16:24:38 Naseem hub.c: new USB device 00:01.2-1.2, assigned address 5
 Mar 22 16:24:38 Naseem usb.c: not enough configurations

tableend?

March 22, 2005, at 03:34 PM by bobtm --
Changed lines 14-15 from:
  • If your hubs works, use the first port for disk devices.
to:
  • If your hubs works, use the first port on the hub for you disk.
  • Connect your hub to the first USB port on the NSLU2 (marked "disk 1")
March 21, 2005, at 06:17 PM by bobtm --
Changed lines 1-18 from:

Describe KnownProblems here.

to:

Known problems in Unslung firmware

In all major software systems there are known issues. Some are easily fixed and some not so easily fixed. Unslung's commitment Linksys compatibility also restricts what can be fixed as not all Linksys SW for the NSLU2 is avilable in source form. This page will have some minor point as well as major sections describing workarounds.

Unslung 3.18

USB issues

There are a number of problems with USB in the kernel. Known problems are:

  • Hubs not working at all or only certain types of hubs.
  • Some disks not being picked up by the USB storage unless being present at boot up.
  • CD/DVD/tape devices not being avilable for mounting - this is because the kernel does not support devfs. Devfs support is in Unslung 4.x.

Tips:

  • If your hubs works, use the first port for disk devices.

bob_tm

view · edit · print · history · Last edited by Bermuda.
Based on work by maisondouf, mwester, mkohler, marceln, Jeremy Jefferson, na, jbf, Prenexus, richdunlop, adriaan, osas, g, KGP, rwhitby, williamwaggoner2003, and bobtm.
Originally by bobtm.
Page last modified on June 28, 2008, at 04:37 PM