subject:"MIPS64EL port box is ready for use"

On 25 October 2013 17:22, YunQiang Su wzss...@gmail.com wrote:

After more than half of a year's hard work, we have the mips64el port
almost done.
Now we have more than 7600 packages build successfully.
The current build status can be found in http://vip.moonux.org/attempted/

Hey! - well done. That's quite some effort!

Now I get a new board and give it 18GiB DDR3 memory and 1TB hardisk.
Most important is that it is running a Debian Unstable, MIPS64EL.

Anyone has need to port package(s) can apply a account.
Please post me your ssh public key signed by a trust-able PGP key.

I also working on make a rootfs to make it easy to install this port.

Here we still have 2 problems:
1. I believe that it is time of use to talk about how to make this
port to debian-ports.org.
Anyone can help us?

One of the issues will be hardware availability. If I can source the above
boards (which it looks like I can), then I can help with that. Also, we are
trying out the Loongson 2F mini-PC's, expanding their RAM to their maximum
(which may only be 1Gbyte, but we hope 2Gbyte), and adding SSD's. If that
works out then they are cheaper, available, and we can relatively easily
build a small farm of those for (donated to) Debian I hope.

2. Which ISA to be used for this port when it is in debian-ports.
Now we use mips64r2 with tune loongson3a.
Should we downgrade ISA requirement to mips3 or mips64?

Much though I would love to say go with MIPS64R2, I suspect for the main
debian-ports.org upload that is not the best single choice. The Loongson 2F
cores are MIPSIII I believe, as are some other platforms. I have a
suspicion that some of the Broadcom chips for instance are MIPS32R1.
I would suggest that we go with MIPSIII for the first mips64le upload, and
then we can work on MIPS32R2 for the 'unofficial ports' to begin with. What
do you think ?

Thanks for all of the people helped me to make this project be realized:
Eleanor Chen, Aron Xu, Anthony Fok, Fuxin Zhang from Lemote and lots
of other people.

You have my thanks as well :-)

--
YunQiang Su

Graham

--
To UNSUBSCRIBE, email to debian-mips-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAKcpw6WvRdF-9O7HKZSr_Vr_ZugF4W0VbTsd=cx-3=qawpz...@mail.gmail.com

Re: MIPS64EL port box is ready for use (Was: mips64el port build failed list)

2013-10-29 Thread YunQiang Su

On Tue, Oct 29, 2013 at 7:05 PM, Graham Whaley graham.wha...@gmail.com wrote:
On 25 October 2013 17:22, YunQiang Su wzss...@gmail.com wrote:

Hey! - well done. That's quite some effort!

Now I get a new board and give it 18GiB DDR3 memory and 1TB hardisk.
Most important is that it is running a Debian Unstable, MIPS64EL.

Nice. Can I ask which board that is? I have some boards reserved for me in
Loongson that I am highly likely to purchase, and suspect (but would like to
confirm) that they are the same board that you are using. I will also check
on any further availability. If I can I will donate one/some of these for
Debian as well.
I prefer that you don't purchase this model of board: I can even not
use the power
button of chassis. Maybe that you can purchase a newer model.
If IPMI is available, it will be much better.

Anyone has need to port package(s) can apply a account.
Please post me your ssh public key signed by a trust-able PGP key.

I also working on make a rootfs to make it easy to install this port.

Here we still have 2 problems:
1. I believe that it is time of use to talk about how to make this
port to debian-ports.org.
Anyone can help us?

2. Which ISA to be used for this port when it is in debian-ports.
Now we use mips64r2 with tune loongson3a.
Should we downgrade ISA requirement to mips3 or mips64?

Much though I would love to say go with MIPS64R2, I suspect for the main
debian-ports.org upload that is not the best single choice. The Loongson 2F
cores are MIPSIII I believe, as are some other platforms. I have a suspicion
that some of the Broadcom chips for instance are MIPS32R1.
I would suggest that we go with MIPSIII for the first mips64le upload, and
then we can work on MIPS32R2 for the 'unofficial ports' to begin with. What
do you think ?
It is also my opinion. Use MIPSIII can make more people use it, and we can
work with some of other unofficial ports.

Thanks for all of the people helped me to make this project be realized:
Eleanor Chen, Aron Xu, Anthony Fok, Fuxin Zhang from Lemote and lots
of other people.

You have my thanks as well :-)

--
YunQiang Su

Graham

--
YunQiang Su

--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/cakcpw6upmbad8xydoovmmslvs5h6mjtagt90bvqvyxyo1s-...@mail.gmail.com

Re: MIPS64EL port box is ready for use (Was: mips64el port build failed list)

2013-10-29 Thread YunQiang Su

On Sat, Oct 26, 2013 at 9:50 AM, Paul Wise p...@debian.org wrote:
On Sat, Oct 26, 2013 at 12:22 AM, YunQiang Su wrote:

After more than half of a year's hard work, we have the mips64el port
almost done.
Now we have more than 7600 packages build successfully.

Congrats!

Please create a page on the Debian wiki and or update the MIPSPort
wiki page about this new architecture. You could also send patches to
update the list of ports on the Debian website:

https://wiki.debian.org/MIPSPort
http://www.debian.org/ports/
http://www.debian.org/ports/mips/
http://www.debian.org/devel/website/
I have update the wiki pages and working on update WML.

The current build status can be found in http://vip.moonux.org/attempted/

Would you like me to register mips64el.debian.net and CNAME it to
vip.moonux.org or another domain?

Now I get a new board and give it 18GiB DDR3 memory and 1TB hardisk.
Most important is that it is running a Debian Unstable, MIPS64EL.

Anyone has need to port package(s) can apply a account.
Please post me your ssh public key signed by a trust-able PGP key.

You should probably talk to DSA about getting it a debian.net domain
and getting it listed in LDAP as a porter machine.

https://db.debian.org/machines.cgi
I have mailed to DSA, and am waiting for their response.

I also working on make a rootfs to make it easy to install this port.

In Debian we usually expect people to either run debootstrap or d-i to
perform Debian installations since otherwise some files that should be
different between installs will be identical. So please just point
people at debootstrap instead. This is a problem with Debian that we
currently have to work around once for every image creation tool; all
of debian-live, cloud images, mips64el rootfs' etc need/have hacks to
remove files like the dbus machine identifier or the openssh host keys
from the system after debootstrap has run.
The patch for loongson 3A has not be in upstream kernel.
The D-I support is not possible for now.
Live system may be a good option.

Here we still have 2 problems:
1. I believe that it is time of use to talk about how to make this
port to debian-ports.org.
Anyone can help us?

http://www.debian-ports.org/contacts

I have heard rumours on IRC that debian-ports.org is having resource
issues so adding new ports there might be hard.

2. Which ISA to be used for this port when it is in debian-ports.
Now we use mips64r2 with tune loongson3a.
Should we downgrade ISA requirement to mips3 or mips64?

That is up to yourself and people who own or otherwise care about MIPS
hardware. Take into consideration what hardware is available
commercially now and will be in the future, as well as what hardware
most people already own. I don't know much about GCC tuning but I
expect that tuning for one specific machine isn't a good idea.

For future the future steps, here are the requirements for adding
mips64el to the archive and getting it officially included in a future
Debian release:

https://ftp-master.debian.org/archive-criteria.html
http://release.debian.org/testing/arch_policy.html
Thanks for you link.

--
bye,
pabs

http://wiki.debian.org/PaulWise

--
To UNSUBSCRIBE, email to debian-mips-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/caktje6en85omcxtdu+3-zj3-k5rgppemiwg6vah1jpbe2sc...@mail.gmail.com

--
YunQiang Su

--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAKcpw6UVzKe5q8fO_02fVYOp04jxVW5y9=cxrn766e6onkf...@mail.gmail.com

Re: MIPS64EL port box is ready for use (Was: mips64el port build failed list)

On 29 October 2013 11:50, YunQiang Su wzss...@gmail.com wrote:
[snip]

Nice. Can I ask which board that is? I have some boards reserved for me
in
Loongson that I am highly likely to purchase, and suspect (but would
like to
confirm) that they are the same board that you are using. I will also
check
on any further availability. If I can I will donate one/some of these for
Debian as well.
I prefer that you don't purchase this model of board: I can even not
use the power
button of chassis. Maybe that you can purchase a newer model.

Thanks for the heads up - but, which board is it? ;-) Do you have a
model/reference number so I can check if the ones I am offered are the same
as the one you have? I have found a few different ones via google. I would
suspect you have athe 3A-RS780 board:
http://www.loongson.cn/product_info.php?id=35

rather than the dual-SoC LS3-CCNUMA-DEV board
http://www.loongson.cn/product_info.php?id=36

but maybe you have something completely different ?

If IPMI is available, it will be much better.

IPMI would be lovely, but I'm not sure we can locate a board right now with
that - so, we may have to fix remote management with a remotely controlled
power/reset box - I believe they exist (something else I've been looking
into). If the DSA already use some then I'd be interested to hear which :-)

[snip]

Much though I would love to say go with MIPS64R2, I suspect for the main
debian-ports.org upload that is not the best single choice. The
Loongson 2F
cores are MIPSIII I believe, as are some other platforms. I have a
suspicion
that some of the Broadcom chips for instance are MIPS32R1.
I would suggest that we go with MIPSIII for the first mips64le upload,
and
then we can work on MIPS32R2 for the 'unofficial ports' to begin with.
What
do you think ?
It is also my opinion. Use MIPSIII can make more people use it, and we can
work with some of other unofficial ports.

Hey, agreement! :-)

Thanks for all of the people helped me to make this project be realized:
Eleanor Chen, Aron Xu, Anthony Fok, Fuxin Zhang from Lemote and lots
of other people.

You have my thanks as well :-)

--
YunQiang Su

Graham

--
To UNSUBSCRIBE, email to debian-mips-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
listmas...@lists.debian.org
Archive:

http://lists.debian.org/CAKcpw6WvRdF-9O7HKZSr_Vr_ZugF4W0VbTsd=cx-3=qawpz...@mail.gmail.com

--
YunQiang Su

Re: MIPS64EL port box is ready for use (Was: mips64el port build failed list)

On Tue, Oct 29, 2013 at 7:05 PM, Graham Whaley graham.wha...@gmail.com wrote:
On 25 October 2013 17:22, YunQiang Su wzss...@gmail.com wrote:

Hey! - well done. That's quite some effort!

Now I get a new board and give it 18GiB DDR3 memory and 1TB hardisk.
Most important is that it is running a Debian Unstable, MIPS64EL.

It is a development board donated by Lemote, and we were told that it
was used for internal testing.

Anyone has need to port package(s) can apply a account.
Please post me your ssh public key signed by a trust-able PGP key.

I also working on make a rootfs to make it easy to install this port.

Here we still have 2 problems:
1. I believe that it is time of use to talk about how to make this
port to debian-ports.org.
Anyone can help us?

I don't think Loongson 2F mini-PC is a good choice since the limited
amount of DIMMs and its limitation on using DDR2 memory only. It's not
quite cost effective comparing with the 3A server boards. We've found
that even the development board has competent performance for being a
buildd. The board uses DDR3 memory add it performs much better than
any other Loongson 2/3 products (Gdium Liberty, 2E/F mini-PC, 3A
notebook) which uses DDR2 memory.

2. Which ISA to be used for this port when it is in debian-ports.
Now we use mips64r2 with tune loongson3a.
Should we downgrade ISA requirement to mips3 or mips64?

Much though I would love to say go with MIPS64R2, I suspect for the main
debian-ports.org upload that is not the best single choice. The Loongson 2F
cores are MIPSIII I believe, as are some other platforms. I have a suspicion
that some of the Broadcom chips for instance are MIPS32R1.
I would suggest that we go with MIPSIII for the first mips64le upload, and
then we can work on MIPS32R2 for the 'unofficial ports' to begin with. What
do you think ?

It would require much more resource to spend on making more ports,
this means more build machines and man power, which is not sufficient
at mean time.

Thanks for all of the people helped me to make this project be realized:
Eleanor Chen, Aron Xu, Anthony Fok, Fuxin Zhang from Lemote and lots
of other people.

You have my thanks as well :-)

--
YunQiang Su

Graham

--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAMr=8w6xasskt0neb2y2zmyutkc3sdeza0qe78pcwh7dpcr...@mail.gmail.com

Re: MIPS64EL port box is ready for use (Was: mips64el port build failed list)

On Tue, Oct 29, 2013 at 8:13 PM, Graham Whaley graham.wha...@gmail.com wrote:

On 29 October 2013 11:50, YunQiang Su wzss...@gmail.com wrote:
[snip]

Nice. Can I ask which board that is? I have some boards reserved for me
in
Loongson that I am highly likely to purchase, and suspect (but would
like to
confirm) that they are the same board that you are using. I will also
check
on any further availability. If I can I will donate one/some of these
for
Debian as well.
I prefer that you don't purchase this model of board: I can even not
use the power
button of chassis. Maybe that you can purchase a newer model.

rather than the dual-SoC LS3-CCNUMA-DEV board
http://www.loongson.cn/product_info.php?id=36

but maybe you have something completely different ?

What we are running isn't any of them, and the 2-way server board
looks promising.

If IPMI is available, it will be much better.

I don't know if IPMI is available, but there is certain kind of PCI
device that can help with remotely power on/off the machine controlled
by SMS. I'm curious if DSA think IPMI is mandatory for buildd and
porterbox.

[snip]

Much though I would love to say go with MIPS64R2, I suspect for the main
debian-ports.org upload that is not the best single choice. The Loongson
2F
cores are MIPSIII I believe, as are some other platforms. I have a
suspicion
that some of the Broadcom chips for instance are MIPS32R1.
I would suggest that we go with MIPSIII for the first mips64le upload,
and
then we can work on MIPS32R2 for the 'unofficial ports' to begin with.
What
do you think ?
It is also my opinion. Use MIPSIII can make more people use it, and we can
work with some of other unofficial ports.

Hey, agreement! :-)

Thanks for all of the people helped me to make this project be
realized:
Eleanor Chen, Aron Xu, Anthony Fok, Fuxin Zhang from Lemote and lots
of other people.

You have my thanks as well :-)

--
YunQiang Su

Graham

--
Regards,
Aron Xu

--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAMr=8w7-zd77fdzw1zuxmeacapfvcd-u0fyzqzo6+0c-bqd...@mail.gmail.com

Re: MIPS64EL port box is ready for use (Was: mips64el port build failed list)

2013-10-29 Thread YunQiang Su

On Tue, Oct 29, 2013 at 10:50 PM, Graham Whaley graham.wha...@gmail.com wrote:



 On 29 October 2013 13:34, Aron Xu a...@debian.org wrote:


 It would require much more resource to spend on making more ports,
 this means more build machines and man power, which is not sufficient
 at mean time.


 True. I hopefully have some resource coming online, and I may also have some
 in-house build hardware available to help with any unofficial ports. We will
 just have to be pragmatic, and it will take time...
Let's pull Fuxin Zhang in and ask him about it.
@Fuxin:
Is there a server available to by which support IPMI? How about its precise?
Or is their any something else which is suitable for build machine?
Imgtec may purchase some.

  Graham



-- 
YunQiang Su


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAKcpw6Vm+6t9+TVJ9sZn00Hp8d30AANdye8z91=UF=y9f-c...@mail.gmail.com

Re: MIPS64EL port box is ready for use (Was: mips64el port build failed list)

On 29 October 2013 13:40, Aron Xu happyaron...@gmail.com wrote:


 What we are running isn't any of them, and the 2-way server board
 looks promising.

 Thanks both. OK, so I've no details from Loongson about the boards they
have for me yet either - I suspect it may be the same as your board.

What we need to consider here is also board price and availability. We can
buy 2f mini-PCs, relatively cheap and easily. If they satisfy a need then
they may be (a mid-term/interim) solution to shortage of hardware right
now. If I find we can source the 3A DDR3 motherboards easily them yippee,
but right now that is less clear than sourcing the 2F mini-PC's.



 I don't know if IPMI is available, but there is certain kind of PCI
 device that can help with remotely power on/off the machine controlled
 by SMS. I'm curious if DSA think IPMI is mandatory for buildd and
 porterbox.

 I think DSA would like to make it a requirement for the future, but they
are pragmatic, and right now many boxes (not just MIPS) do not have good
remote power/reset control. There are external boxes that can do this
though, and we are investigating them already for internal use, and I'll
share any useful findings.


 --
 Regards,
 Aron Xu


 thanks guys - I'll keep you posted with my progress as well.

 Graham

Re: MIPS64EL port box is ready for use (Was: mips64el port build failed list)

On 29 October 2013 13:34, Aron Xu a...@debian.org wrote:


 It would require much more resource to spend on making more ports,
 this means more build machines and man power, which is not sufficient
 at mean time.


True. I hopefully have some resource coming online, and I may also have
some in-house build hardware available to help with any unofficial ports.
We will just have to be pragmatic, and it will take time...

 Graham

Re: MIPS64EL port box is ready for use

2013-10-29 Thread Tollef Fog Heen

]] Aron Xu 

  IPMI would be lovely, but I'm not sure we can locate a board right now with
  that - so, we may have to fix remote management with a remotely controlled
  power/reset box - I believe they exist (something else I've been looking
  into). If the DSA already use some then I'd be interested to hear which :-)
 
 I don't know if IPMI is available, but there is certain kind of PCI
 device that can help with remotely power on/off the machine controlled
 by SMS. I'm curious if DSA think IPMI is mandatory for buildd and
 porterbox.

We would very much like «reasonable remote access».  Whether that's IPMI
onto a BMC or serial console which can interact with the boot loader and
a network-enabled power strip is less important.  Of course, having nice
features like mounting of ISOs over HTTP and such is a nice bonus, but
not a requirement.

We haven't really talked about how and when it should be enforced, but
I'm reluctant to take on more porter hardware that lacks reasonable
remote management.

-- 
Tollef Fog Heen (speaking on behalf of himself, but with a DSA hat)
UNIX is user friendly, it's just picky about who its friends are


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/m2fvrkf16y@rahvafeir.err.no

Re: MIPS64EL port box is ready for use

2013-10-29 Thread David Kuehling

Hi,

 Graham == Graham Whaley graham.wha...@gmail.com writes:

 What we need to consider here is also board price and availability. We
 can buy 2f mini-PCs, relatively cheap and easily. If they satisfy a
 need then they may be (a mid-term/interim) solution to shortage of
 hardware right now. If I find we can source the 3A DDR3 motherboards
 easily them yippee, but right now that is less clear than sourcing the
 2F mini-PC's.

somewhat related information: just found out that there is (seems to be)
a Loongson 3A based mini-PC:

  http://www.lemote.com/products/computer/fulong/348.html

Price point seems to be RMB 3999, if I understand this shop's page
correctly:

  
http://item.taobao.com/item.htm?spm=a1z10.1.w4004-2611770768.2.DQacwZid=22206048695

Not sure how stable/usable that hardware would be, tough.  I currently
consider getting one to replace my 2f mini-PC.  It may only come with a
single-core version of the 3A (description says LoongSon2G/3A, not sure
what that means).

cheers,

David
-- 
GnuPG public key: http://dvdkhlng.users.sourceforge.net/dk2.gpg
Fingerprint: B63B 6AF2 4EEB F033 46F7  7F1D 935E 6F08 E457 205F



pgp4xQlQWK66i.pgp
Description: PGP signature

Re: MIPS64EL port box is ready for use

On Tue, Oct 29, 2013 at 6:15 PM, Tollef Fog Heen tfh...@err.no wrote:
]] Aron Xu

We would very much like «reasonable remote access». Whether that's IPMI
onto a BMC or serial console which can interact with the boot loader and
a network-enabled power strip is less important. Of course, having nice
features like mounting of ISOs over HTTP and such is a nice bonus, but
not a requirement.

We haven't really talked about how and when it should be enforced, but
I'm reluctant to take on more porter hardware that lacks reasonable
remote management.

I thinlk we could hack a low cost arm like a cubiebox to do that. They
are plenty of gpio available and reseting power is only matter or
putting on/off a relay... Bonus point it will run debian :)

Bastien

--
Tollef Fog Heen (speaking on behalf of himself, but with a DSA hat)
UNIX is user friendly, it's just picky about who its friends are

--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/m2fvrkf16y@rahvafeir.err.no

--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/cae2spabklsotzisu+6pw4desx5u5t9db2xdcsamfdvj0w6o...@mail.gmail.com

Re: MIPS64EL port box is ready for use

On Wed, Oct 30, 2013 at 1:15 AM, Tollef Fog Heen tfh...@err.no wrote:
]] Aron Xu

We haven't really talked about how and when it should be enforced, but
I'm reluctant to take on more porter hardware that lacks reasonable
remote management.

If we can find a way of letting Loongson 3A board supports remote
console then you are able to re-install the system because PMON have
networking support and can boot the system from tftp. Power control
can be done by hacking the on-board power button pins.

Thanks,
Aron Xu

--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAMr=8w5zqqkac0k1j9wfmbff5ybq8rc-n7fjq1rx0dqtjhd...@mail.gmail.com

Re: MIPS64EL port box is ready for use

On Tue, Oct 29, 2013 at 7:35 PM, Aron Xu a...@debian.org wrote:
On Wed, Oct 30, 2013 at 1:15 AM, Tollef Fog Heen tfh...@err.no wrote:
]] Aron Xu

IPMI would be lovely, but I'm not sure we can locate a board right now
with
that - so, we may have to fix remote management with a remotely controlled
power/reset box - I believe they exist (something else I've been looking
into). If the DSA already use some then I'd be interested to hear which
:-)

We haven't really talked about how and when it should be enforced, but
I'm reluctant to take on more porter hardware that lacks reasonable
remote management.

It could be done trivally from a chip arm card. Using socat from a tty
to a ssh tunnel
see http://www.dest-unreach.org/socat/doc/socat-ttyovertcp.txt

Thanks,
Aron Xu

--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/camr8w5zqqkac0k1j9wfmbff5ybq8rc-n7fjq1rx0dqtjhd...@mail.gmail.com

--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/cae2spayt8d49dlzcgggup67dbb4xjbfhgmdblnwhomjs9ij...@mail.gmail.com

Re: MIPS64EL port box is ready for use

On Wed, Oct 30, 2013 at 2:40 AM, Bastien ROUCARIES
roucaries.bast...@gmail.com wrote:
On Tue, Oct 29, 2013 at 7:35 PM, Aron Xu a...@debian.org wrote:
On Wed, Oct 30, 2013 at 1:15 AM, Tollef Fog Heen tfh...@err.no wrote:
]] Aron Xu

IPMI would be lovely, but I'm not sure we can locate a board right now
with
that - so, we may have to fix remote management with a remotely
controlled
power/reset box - I believe they exist (something else I've been looking
into). If the DSA already use some then I'd be interested to hear which
:-)

We haven't really talked about how and when it should be enforced, but
I'm reluctant to take on more porter hardware that lacks reasonable
remote management.

It could be done trivally from a chip arm card. Using socat from a tty
to a ssh tunnel
see http://www.dest-unreach.org/socat/doc/socat-ttyovertcp.txt

Looks really cool, and I think it's doable to support power control
like what you've suggested already.

Cheers,
Aron Xu

--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAMr=8w6R+x2+bQ5JWao_fzynnjHt4Nf=rng+edfpjrk01l+...@mail.gmail.com

Re: MIPS64EL port box is ready for use

On Wed, Oct 30, 2013 at 3:11 AM, Bastien ROUCARIES
roucaries.bast...@gmail.com wrote:
On Tue, Oct 29, 2013 at 7:56 PM, Aron Xu a...@debian.org wrote:
On Wed, Oct 30, 2013 at 2:40 AM, Bastien ROUCARIES
roucaries.bast...@gmail.com wrote:
On Tue, Oct 29, 2013 at 7:35 PM, Aron Xu a...@debian.org wrote:
On Wed, Oct 30, 2013 at 1:15 AM, Tollef Fog Heen tfh...@err.no wrote:
]] Aron Xu

IPMI would be lovely, but I'm not sure we can locate a board right now
with
that - so, we may have to fix remote management with a remotely
controlled
power/reset box - I believe they exist (something else I've been
looking
into). If the DSA already use some then I'd be interested to hear
which :-)

We haven't really talked about how and when it should be enforced, but
I'm reluctant to take on more porter hardware that lacks reasonable
remote management.

It could be done trivally from a chip arm card. Using socat from a tty
to a ssh tunnel
see http://www.dest-unreach.org/socat/doc/socat-ttyovertcp.txt

Looks really cool, and I think it's doable to support power control
like what you've suggested already.

What are the safety specification appliable by DSA ? Main tension ?
Does the board have a power brick ?

I'm not sure about DSA's opinion, and here is the information about
the board. It is an almost standard ITX one, and we've put it in an
ITX chassis retired from a ~2006 Lenovo PC, using its power supply.
The board has some pins for connecting power bottons (Power and
Reset), though we are not using it because it looks not fit to the
connector of the chassis. There is a dedicate button on the board to
power on/off the machine as well. We used the on board button and no
hard reset needed/conducted since successful installation of hardware.
The mentioned ITX machine (6100 model) available for purchase is just
a complete PC box.

Thanks,
Aron Xu

--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAMr=8w72n5gqjuzez8tgw+_r+z0e6ur7kvtt0vv5m3fogtx...@mail.gmail.com

Re: MIPS64EL port box is ready for use

On Tue, Oct 29, 2013 at 7:56 PM, Aron Xu a...@debian.org wrote:
On Wed, Oct 30, 2013 at 2:40 AM, Bastien ROUCARIES
roucaries.bast...@gmail.com wrote:
On Tue, Oct 29, 2013 at 7:35 PM, Aron Xu a...@debian.org wrote:
On Wed, Oct 30, 2013 at 1:15 AM, Tollef Fog Heen tfh...@err.no wrote:
]] Aron Xu

IPMI would be lovely, but I'm not sure we can locate a board right now
with
that - so, we may have to fix remote management with a remotely
controlled
power/reset box - I believe they exist (something else I've been looking
into). If the DSA already use some then I'd be interested to hear which
:-)

We haven't really talked about how and when it should be enforced, but
I'm reluctant to take on more porter hardware that lacks reasonable
remote management.

It could be done trivally from a chip arm card. Using socat from a tty
to a ssh tunnel
see http://www.dest-unreach.org/socat/doc/socat-ttyovertcp.txt

Looks really cool, and I think it's doable to support power control
like what you've suggested already.

What are the safety specification appliable by DSA ? Main tension ?
Does the board have a power brick ?

Bastien

Cheers,
Aron Xu

--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/cae2spabpc2o9+f55vot9vrnmuowmn0jgkkt7zrt9vvwmhl-...@mail.gmail.com

Re: MIPS64EL port box is ready for use

On Tue, Oct 29, 2013 at 8:25 PM, Aron Xu a...@debian.org wrote:
On Wed, Oct 30, 2013 at 3:11 AM, Bastien ROUCARIES
roucaries.bast...@gmail.com wrote:
On Tue, Oct 29, 2013 at 7:56 PM, Aron Xu a...@debian.org wrote:
On Wed, Oct 30, 2013 at 2:40 AM, Bastien ROUCARIES
roucaries.bast...@gmail.com wrote:
On Tue, Oct 29, 2013 at 7:35 PM, Aron Xu a...@debian.org wrote:
On Wed, Oct 30, 2013 at 1:15 AM, Tollef Fog Heen tfh...@err.no wrote:
]] Aron Xu

IPMI would be lovely, but I'm not sure we can locate a board right
now with
that - so, we may have to fix remote management with a remotely
controlled
power/reset box - I believe they exist (something else I've been
looking
into). If the DSA already use some then I'd be interested to hear
which :-)

We haven't really talked about how and when it should be enforced, but
I'm reluctant to take on more porter hardware that lacks reasonable
remote management.

It could be done trivally from a chip arm card. Using socat from a tty
to a ssh tunnel
see http://www.dest-unreach.org/socat/doc/socat-ttyovertcp.txt

Looks really cool, and I think it's doable to support power control
like what you've suggested already.

What are the safety specification appliable by DSA ? Main tension ?
Does the board have a power brick ?

The mini itx does not specify a power connector So if you use an
atx power control do something like this
http://www.mupuf.org/blog/2013/05/11/wtrpm-a-web-based-wt-suite-to-power-up-slash-down-your-computers/

Thanks,
Aron Xu

--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAE2SPAZ�ek9ml4ygcsxlxzhfu_qq98y9o5gkeftwnpjne...@mail.gmail.com

Re: MIPS64EL port box is ready for use