Martin Michlmayr wrote:
Oh, I thought you said the current firmware version had the press
reset, do TFTP feature. Bugger.
I was told it did by people on #linkstationwiki - I thought I had broken
this feature on my box by changing the default nvram settings, but after
further
Hey Tim,
* Tim Small [EMAIL PROTECTED] [2008-08-10 12:34]:
- Run a script supplied by Debian that will use nvram to change
bootargs_root=root=/dev/sda2 rw initrd=0x00800040,15M panic=5
to
bootargs_root=root=/dev/sda2 rw initrd=0x00800040 panic=5
Pretty much, but I think the
Martin Michlmayr wrote:
Tim, can please install flash-kernel from unstable, attach the patch
below, run 'flash-kernel' and see if your machine still boots?
Yep, that works - that patch should be OK to commit, I think...
BTW, what about the Terastation Pro II/Live and Linkstation Pro Duo?
Martin Michlmayr wrote:
Does the LS use dhcp in this case to
obtain an IP address and the IP of the server, or will it always use
the hardcoded value (192.168.11.1)?
The Buffalo uboot uses a hard-coded IP address of 192.168.11.150, with a
hard-coded tftp server IP of 192.168.11.1 . I
Martin Michlmayr wrote:
* Tim Small [EMAIL PROTECTED] [2008-08-10 12:34]:
- Run a script supplied by Debian that will use nvram to change
bootargs_root
Pretty much, but I think the best approach is to supply an initrd which
does this automatically
I'm not sure we can do
* Tim Small [EMAIL PROTECTED] [2008-08-10 13:41]:
I'm not sure we can do that. The installer will use an initramfs
rather than an initrd, so the u-boot environment has to be changed
before the installer can be started.
I was thinking that a separate initrd image would be needed for the
On Sun, Aug 10, 2008 at 02:58:57PM +0300, Martin Michlmayr wrote:
[5.72] mv643xx_eth: Unknown symbol generic_mii_ioctl
[5.72] mv643xx_eth: Unknown symbol mii_ethtool_gset
but I'm guessing that this is a problem with this particular build
Strange. Someone else
* Lennert Buytenhek [EMAIL PROTECTED] [2008-08-10 15:47]:
Maybe CONFIG_MII=m and the particular module loader being used isn't
resolving module dependencies? (Or mii.ko isn't included in the fs?)
Yeah, I just checked and mii.ko is not included on the arm image. For
some reason, nic-modules
Martin Michlmayr wrote:
For some reason, nic-modules doesn't depend on nic-shared-modules (which
contains mii) on arm whereas it does on armel. Fortunately, nobody is
supposed to use arm anymore but I'll look into fixing it anyway.
Hmm, yes, my bad, I accidentally clicked the arm, instead
* Tim Small [EMAIL PROTECTED] [2008-08-07 22:25]:
Initially, I didn't think this was possible to do on the lspro,
without using a serial cable (since there is no method on the lspro
V2s which I have to force a tftpboot, without a serial cable, but
some earlier hw/fw versions apparently have
* Martin Michlmayr [EMAIL PROTECTED] [2008-08-09 13:36]:
2) flash-kernel support: flash-kernel (despite the name) now supports
both flash and disk based devices. It has to make a bootable image on
disk. I think the support we have for Kurobox should work out of the
box. We just need to
Per Andersson wrote:
Do you think the current debian installer code and method
for installing Debian on the Kurobox Pro would work for
Linkstation Pro/Live as well? The method goes something
like this:
1) Create a ext2 filesystem on the first partition on the
attached harddrive. (Has to be ext2
(No need to CC me, I read the list.)
On Fri, Aug 8, 2008 at 10:09 AM, Tim Small [EMAIL PROTECTED] wrote:
Per Andersson wrote:
Do you think the current debian installer code and method
for installing Debian on the Kurobox Pro would work for
Linkstation Pro/Live as well? The method goes
Hello,
I presume (but I'm not sure) that the only method for installing Debian
on the kuropro, and lspro will be to start the installer via TFTP.. I
suppose it might also be possible to write an installer image to the HD
of the linkstation (by connecting the drive directly to another machine
On Thu, Aug 7, 2008 at 11:25 PM, Tim Small [EMAIL PROTECTED] wrote:
I presume (but I'm not sure) that the only method for installing Debian on
the kuropro, and lspro will be to start the installer via TFTP.. I suppose
it might also be possible to write an installer image to the HD of the
On Thu, Aug 7, 2008 at 11:25 PM, Tim Small [EMAIL PROTECTED] wrote:
I presume (but I'm not sure) that the only method for installing Debian on
the kuropro, and lspro will be to start the installer via TFTP.. I suppose
it might also be possible to write an installer image to the HD of the
Per Andersson wrote:
Can EM be used similarly on the lspro?
The Buffalo software does indeed include an emergency mode, but this
is entered as a special case from their kernel/initrd pair, both of
which are stored on the hard-disk. Once you install the Debian kernel
and initramfs
On Fri, Aug 8, 2008 at 12:04 AM, Tim Small [EMAIL PROTECTED] wrote:
The Buffalo software does indeed include an emergency mode, but this is
entered as a special case from their kernel/initrd pair, both of which are
stored on the hard-disk. Once you install the Debian kernel and initramfs
Martin Michlmayr wrote:
* Tim Small [EMAIL PROTECTED] [2008-07-27 15:01]:
. Patch the mainline initramfs code in a nice way, so that it'll
work with any lspro firmware version - and hope the kernel
maintainers accept the patch (which they might, as the current code
is arguably a bit
* Tim Small [EMAIL PROTECTED] [2008-07-30 20:37]:
Hmm, I think in order to stand a chance of getting it fixed, you'd
probably need to submit a patch
Not necessarily.
investment, without a guarantee of it getting accepted, I wonder if
it might not be best just to fix the problem in user
On Wed, 2008-07-30 at 23:01 +0300, Martin Michlmayr wrote:
Is the nvram utility included is the LS Pro software environment or is
that only on the Kurobox Pro?
The nvram utility is included with the LS Pro software as well. A free
alternative to it is fw_printenv and fw_setenv, which are
Ryan Tandy wrote:
You may remember that a while back I tried to use your kernel package,
but that my u-boot (from the original lspro firmware) didn't load the
initrd properly when I removed the initrd= boot parameter. Today I
updated the bootloader to 1.10 using the Buffalo updater, installed a
* Tim Small [EMAIL PROTECTED] [2008-07-27 15:01]:
. Patch the mainline initramfs code in a nice way, so that it'll
work with any lspro firmware version - and hope the kernel
maintainers accept the patch (which they might, as the current code
is arguably a bit broken).
Are you going to go
* Ryan Tandy [EMAIL PROTECTED] [2008-07-27 11:40]:
Just for the record, can you tell me what firmware version you now have in
flash?
/proc/cmdline reports BOOTVER=1.10.
Do you remember the version that didn't work?
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to
On Sun, 2008-07-27 at 14:02 -0700, Martin Michlmayr wrote:
Do you remember the version that didn't work?
I can't find it written down anywhere, but I believe it was 1.01. As
far as I can tell there were three versions released by Buffalo: 1.01 on
the first Linkstation hardware, 1.09 on the
25 matches
Mail list logo
