Re: Re: getting IP support in redboot for older n2100s
It should work. I'm not sure the upgrade process of the Thecus firmware will complain when the version you're running is not higher than the one you want to upgrade to, but hopefully it will just let you do it. The other option would be to unpack the Thecus firmware (according to the instructions below) and then write the RedBoot binary directly to /dev/mtd0 IMHO, if written the firmware is written from debian -- like in the deinstallation instructions -- ,it cannot refuse to upgrade. However, I think writing redboot directly from debian is *too dangerous*, as there is no revovery route, except maybe JTAG (has the Thecus JTAG, btw). The safest way would be hooking up RS232 and just load the thecus firmware into RAM and boot from there. If it refuses to upgrade, another soution can be tried. If not, this is the far less risky way... Has anyone tried this recently? I haven't used the Thecus firmware recently. I heard there's a version v2.1.06 of the firmware now and I wanted to test it, but I can only find v2.1.05 online. 2.1.0.6 is available on the US Site, 2.1.0.5 on the German one. Mine came with 2.1.0.6, and all works like 2.1.05 (concerning RedBoot and the installation instructions) Tobi -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
State of the arm/ixp4xx 2.6.24 kernel (important if you run Debian on an NSLU2)
Hi All For the arm/ixp4xx Debian 2.6.24 kernel (used on the Linksys NSLU2), I switched to Krzysztof Hasala's Ethernet driver. I did this because 2.6.25 will definitely contain the Krzysztof's support for the IXP4xx network processor engine and hardware queue manager, and should contain the NSLU2 and NAS100D platform support (Rod Whitby has submitted those patches to Russell King's ARM patch system). Therefore, the only parts left for full support in the kernel for IXP4xx networking will be Krzysztof's Ethernet and High Speed Serial (HSS) drivers, and I'm hoping that he will submit these to the Linux netdev mailing list for review soon. The first paragraph contained the good news. The bad news is that although Krzysztof's driver is works well, udev does not load the driver automatically. This means that you should *not* run a 2.6.24 kernel on your NSLU2 unless you have serial port access, because you will not have network access without loading the driver manually. I'm working on a solution to this problem, but until one exists, be careful when 2.6.24 hits unstable. Gordon -- Gordon Farquharson GnuPG Key ID: 32D6D676 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: State of the arm/ixp4xx 2.6.24 kernel (important if you run Debian on an NSLU2)
* Gordon Farquharson [EMAIL PROTECTED] [2008-01-27 12:07]: The first paragraph contained the good news. The bad news is that although Krzysztof's driver is works well, udev does not load the driver automatically. This means that you should *not* run a 2.6.24 kernel on your NSLU2 unless you have serial port access, because you will not have network access without loading the driver manually. I'm working on a solution to this problem, but until one exists, be careful when 2.6.24 hits unstable. If it takes too long (i.e. longer than 2.6.24 being uploaded to the archive), maybe joeyh would consider putting a workaround into nslu2-utils that loads the driver manually if the kernel is = 2.6.24. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: State of the arm/ixp4xx 2.6.24 kernel (important if you run Debian on an NSLU2)
Gordon Farquharson wrote: For the arm/ixp4xx Debian 2.6.24 kernel (used on the Linksys NSLU2), I switched to Krzysztof Hasala's Ethernet driver. The first paragraph contained the good news. The bad news is that although Krzysztof's driver is works well, udev does not load the driver automatically. FYI, in nslu2-linux and openwrt, we compile the ethernet driver into the kernel (you don't save any memory making something a module when the module will *always* be loaded), and just let udev load the microcode. Perhaps the Debian ixp4xx kernel can use a similar approach? -- Rod -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
