Re: Synology PPCBoot SK98 network bug fix

[Frank Wille <frank%phoenix.owl.de@localhost>]

On Fri, 17 Jun 2011 10:59:01 +0100
Julian Coleman <jdc%coris.org.uk@localhost> wrote:

> >   a: 144808272        63     4.2BSD   2048 16384     0
> >   d: 167773473 144808335       RAID
> > Here rf_offset should be 144808335+RF_PROTECTED_SECTORS and not
> > 63+RF_PROTECTED_SECTORS. Solution: Use the RAID partition's 'p_offset'
> > instead of 'first'.
> 
> That's true.  However, as I mentioned before, perhaps it is better to only
> allow a RAID partition as the first partition (or not at all).  In the
> above case, we can't tell if the bootable partition is 'a' or 'd'.  So,
> I'm inclined to just check if partition 'a' is of type RAID.

We can do that. But then you still have to modify your code, because
currently it will continue looking for RAID, even if there had already
been a valid partition.


> Yes.  There are two disk lights on the DS207.  I will look through the
> linux source to see where they are controlled from.

Ok.


> Somewhat more annoying to me is my current network problem.  I mentioned
> before that neither altboot nor the kernel could transmit packets.  This

Didn't transmit always work before? Perhaps you are currently running one
of your own test versions of altboot and it does a bad SKnet configuration?


> will try and spot what has gone wrong in the chip initialisation (I have
> register dumps from altboot to compare).

Good luck!
You already tried an older, known to work, altboot? Or can you isolate
the problem by using a small network, with just one switch, a server
and your NAS?

-- 
Frank Wille