Nabble - debian-arm

Re: QNAP: TS-419 and newest kernel

2009-12-15T09:09:59Z

On Tuesday 15 December 2009 12:27:42 Martin Michlmayr wrote:
> * Adrian von Bidder <avbidder@...> [2009-12-14 21:28]:
> > Just a quick update:
> > * 2.6.30 kernel (2.6.30-8+orion1) from tbm's repository works fine.
> > * 2.6.31 kernel (2.6.31-2) from sid sometimes boots but mostly soon-ish
> > brings the loss of connection to the disks that I already wrote about
>
> I think another user reported this problem with the 2.6.30 so I doubt
> it's 2.6.31 specific (although I might be wrong).

First time I reported it it was 2.6.30 from your repository. I only saw it
the once, though, and could install Debian just fine after that. In 2.6.31 it
seems ridiculously easy to trigger; within a few moments after boot (often it
doesn't even boot to where I can log in.)

> > * 2.6.32 (2.6.32-1, the sid version of the one I compiled myself from
> > the sid sources becore the official binary was available :-) ; the
> > package is linux- image-2.6.32-trunk-kirkwood, not sure why 'trunk' is
> > suddenly used) reliably doesn't boot through (sorry, still no console
> > cable, so I can't help much more here :-(
> > * 2.6.32-rc8-kirkwood (2.6.32~rc8-1~experimental.1): seems to work.
> > I've booted it two or three times now and did some stuff in btrfs.
>
> I haven't tested 2.6.32-1 yet but I don't see why it shouldn't work
> (especially given that rc8 worked). Can you try the 2.6.32-1 from the
> Debian archive? If it doesn't work, I'll take a look.

Sorry to be unprecise here: I did try first the self-compiled 2.6.32-trunk-
kirkwood and then the sid kernel, too. And now I tried the sid kernel again,
to make sure I hadn't used the wrong copy of the deb before, with the same
result: rc8 works, 2.6.32-trunk-kirkwood doesn't work anymore :-/

I did quite a few things on btrfs today (copying stuff around mostly, creating
very few snapshots too) and rc8 is stable for me.

I could send you the initrd if it is any use to you.

cheers
-- vbi

--
This product is under strict quality contril with perfect packing and
quality when leving the factory.please keep away from damp.high
temperature or sun expose.If found any detectives when purchasing.
please return the productby airmail to our administration section and
inform the time, place.and store of this purchase for our improvement.We
shall give you a satisfactory reply.Thanks for your patronage and
welcome your comments.
-- http://www.engrish.com/

signature.asc (399 bytes) Download Attachment

Re: QNAP: TS-419 and newest kernel

2009-12-15T03:27:42Z

* Adrian von Bidder <avbidder@...> [2009-12-14 21:28]:
> Just a quick update:
> * 2.6.30 kernel (2.6.30-8+orion1) from tbm's repository works fine.
> * 2.6.31 kernel (2.6.31-2) from sid sometimes boots but mostly soon-ish
> brings the loss of connection to the disks that I already wrote about

I think another user reported this problem with the 2.6.30 so I doubt
it's 2.6.31 specific (although I might be wrong).

> * 2.6.32 (2.6.32-1, the sid version of the one I compiled myself from the sid
> sources becore the official binary was available :-) ; the package is linux-
> image-2.6.32-trunk-kirkwood, not sure why 'trunk' is suddenly used) reliably
> doesn't boot through (sorry, still no console cable, so I can't help much more
> here :-(
> * 2.6.32-rc8-kirkwood (2.6.32~rc8-1~experimental.1): seems to work. I've
> booted it two or three times now and did some stuff in btrfs.

I haven't tested 2.6.32-1 yet but I don't see why it shouldn't work
(especially given that rc8 worked). Can you try the 2.6.32-1 from the
Debian archive? If it doesn't work, I'll take a look.
--
Martin Michlmayr
http://www.cyrius.com/

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

smbclient package and 'not found' error

2009-12-15T02:14:30Z

Hello,

I try to run the smbclient on my ARM Platform (Samsung S3C2440a
ARM920T). In order to this I've downloaded the smbclient and
samba-common packages from arm branch (3.0.24-6etch10), and extract
they on my host by following command:

dpkg-deb -x samba-common_3.4.2-1~bpo50+3_all.deb ~/samba
dpkg-deb -x samba-common_3.4.2-1~bpo50+3_all.deb ~/samba

After that, I've transfered ~/samba directory to my target board. When
I run any binary files from usr/bin path I get the following errors:

root@arm:~/samba/usr/bin$ ./smbclient
-/bin/sh: smbclient: not found

root@arm:~/samba/usr/bin$ ./smbget
-/bin/sh: smbget: not found

root@arm:~/samba/usr/bin$ ./findsmb
-/bin/sh: findsmb: not found

I don't exactly understand it. What have I missed? Maybe I have to
'convert' somehow these binary files?

Thank you in advance for any hints and engagement.

--
Piotr Piwko
http://www.embedded-engineering.pl/

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

QNAS: TS-419 and newest kernel

2009-12-14T12:28:54Z

Heyho!

Just a quick update:
* 2.6.30 kernel (2.6.30-8+orion1) from tbm's repository works fine.
* 2.6.31 kernel (2.6.31-2) from sid sometimes boots but mostly soon-ish
brings the loss of connection to the disks that I already wrote about (at
least to tbm)
* 2.6.32 (2.6.32-1, the sid version of the one I compiled myself from the sid
sources becore the official binary was available :-) ; the package is linux-
image-2.6.32-trunk-kirkwood, not sure why 'trunk' is suddenly used) reliably
doesn't boot through (sorry, still no console cable, so I can't help much more
here :-(
* 2.6.32-rc8-kirkwood (2.6.32~rc8-1~experimental.1): seems to work. I've
booted it two or three times now and did some stuff in btrfs.

So I guess I'll stay with rc8 now and look if it stays stable.

cheers
-- vbi

signature.asc (399 bytes) Download Attachment

Re: kirkwood mv643xx_eth wrong tcp checksums

2009-12-14T12:02:06Z

* Lennert Buytenhek <buytenh@...> [2009-11-25 23:10]:
> > Instead of the latest 2.6.32rc8 kernel I have now compiled the 2.6.30
> > kernel that came with debian squeeze with your workaround and it works!
>
> Odd. Let me figure out why on 2.6.32-rc it isn't working.

Any update on this?

--
Martin Michlmayr
http://www.cyrius.com/

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: Emergency telnet?

2009-12-14T12:01:25Z

* Swen van Brussel <swen@...> [2009-12-10 23:16]:
> > Thanks for the pointer; [tbm: if you're reading this, perhaps put this info
> > on your serial console page for those who don't care to build their own?
>
> The specific cable you want is the 'WE' version.

Do you think you can create a wiki page about this at
qnap.nas-central.org so I can link to it?

--
Martin Michlmayr
http://www.cyrius.com/

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: debian's installer suspended !

2009-12-14T11:58:28Z

* アズマ <masha_kazuhra3n@...> [2009-12-08 23:39]:
> Marvell>> mmcinit
> Error! cmd : 8, err : 0201

I cannot really see anything wrong. The only thing I see is this
error but then the files seem to load properly... but maybe the files
weren't loaded properly. Can you try to load it via USB or TFTP?
--
Martin Michlmayr
http://www.cyrius.com/

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: nslu2: two devices: one by default

2009-12-13T03:33:15Z

En/na Przemyslaw Kwiatkowski ha escrit:
>
>
> Please note, that ethernet bridge *may* not work in your lan, because
> your wifi accespoint possibly already has such bridge built-in. It
> means, that you will create a loop. I am not sure what will happen then.
> Some tests will be necessary. :-)
>
>
mmmm... thanks for saying. I think I maintain different ip's and do not
bridge. It's more difficult what I want.... ;-)

Xan.

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: nslu2: two devices: one by default

2009-12-12T10:54:42Z

Hello,

Xan pisze:

>>>>> 172.26.0.0/16 dev eth0 proto kernel scope link src 172.26.0.2
>>>>> 172.26.0.0/16 dev wlan0 proto kernel scope link src 172.26.0.3
>>>>> default via 172.26.0.1 dev wlan0
>>>>> default via 172.26.0.1 dev eth0 )
>>>>>
>>>> Suggestion: You could try to bridge eth0 and wlan0. This way you may
>>>> have the same IP address (say 172.26.0.2) on both interfaces, and this
>>>> IP should be reachable whenever one of the interfaces is up.
>>>>
>>> It sounds good. How to do that?. Can you point me some tutorial for
>>> doing that?
>>
>> Start here:
>> http://wiki.debian.org/BridgeNetworkConnections

Please note, that ethernet bridge *may* not work in your lan, because
your wifi accespoint possibly already has such bridge built-in. It
means, that you will create a loop. I am not sure what will happen then.
Some tests will be necessary. :-)

--
Przemyslaw Kwiatkowski [Micha], micha@..., 2:480/127@FidoNet
SMS# +48 601 238089, GPG: 2CA0 F353 85FD B0F1 1BD4 73D7 F85D 2717

"Any technology distinguishable from magic is insufficiently advanced."
(c) Gregory Benford

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: nslu2: two devices: one by default

2009-12-12T10:00:23Z

En/na Przemyslaw Kwiatkowski ha escrit:

> Hello,
>
> Xan pisze:
>
>
>>>> 172.26.0.0/16 dev eth0 proto kernel scope link src 172.26.0.2
>>>> 172.26.0.0/16 dev wlan0 proto kernel scope link src 172.26.0.3
>>>> default via 172.26.0.1 dev wlan0
>>>> default via 172.26.0.1 dev eth0 )
>>>>
>>> Suggestion: You could try to bridge eth0 and wlan0. This way you may
>>> have the same IP address (say 172.26.0.2) on both interfaces, and this
>>> IP should be reachable whenever one of the interfaces is up.
>>>
>>>
>> It sounds good. How to do that?. Can you point me some tutorial for
>> doing that?
>>
>
> Start here:
> http://wiki.debian.org/BridgeNetworkConnections
>
>

Thanks.
Xan

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: nslu2: two devices: one by default

2009-12-12T09:19:03Z

Hello,

Xan pisze:

>>> 172.26.0.0/16 dev eth0 proto kernel scope link src 172.26.0.2
>>> 172.26.0.0/16 dev wlan0 proto kernel scope link src 172.26.0.3
>>> default via 172.26.0.1 dev wlan0
>>> default via 172.26.0.1 dev eth0 )
>>
>> Suggestion: You could try to bridge eth0 and wlan0. This way you may
>> have the same IP address (say 172.26.0.2) on both interfaces, and this
>> IP should be reachable whenever one of the interfaces is up.
>>
> It sounds good. How to do that?. Can you point me some tutorial for
> doing that?

Start here:
http://wiki.debian.org/BridgeNetworkConnections

--
Przemyslaw Kwiatkowski [Micha], micha@..., 2:480/127@FidoNet
SMS# +48 601 238089, GPG: 2CA0 F353 85FD B0F1 1BD4 73D7 F85D 2717

"Any technology distinguishable from magic is insufficiently advanced."
(c) Gregory Benford

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: nslu2: two devices: one by default

2009-12-12T09:00:27Z

En/na Przemyslaw Kwiatkowski ha escrit:

> Hello,
>
> Xan pisze:
>
>
>> 172.26.0.0/16 dev eth0 proto kernel scope link src 172.26.0.2
>> 172.26.0.0/16 dev wlan0 proto kernel scope link src 172.26.0.3
>> default via 172.26.0.1 dev wlan0
>> default via 172.26.0.1 dev eth0 )
>>
>
> Suggestion: You could try to bridge eth0 and wlan0. This way you may
> have the same IP address (say 172.26.0.2) on both interfaces, and this
> IP should be reachable whenever one of the interfaces is up.
>
>
>

It sounds good. How to do that?. Can you point me some tutorial for
doing that?

Thanks,
Xan.

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: nslu2: two devices: one by default

2009-12-12T02:36:39Z

Hello,

Xan pisze:

> 172.26.0.0/16 dev eth0 proto kernel scope link src 172.26.0.2
> 172.26.0.0/16 dev wlan0 proto kernel scope link src 172.26.0.3
> default via 172.26.0.1 dev wlan0
> default via 172.26.0.1 dev eth0 )

Suggestion: You could try to bridge eth0 and wlan0. This way you may
have the same IP address (say 172.26.0.2) on both interfaces, and this
IP should be reachable whenever one of the interfaces is up.

--
Przemyslaw Kwiatkowski [Micha], micha@..., 2:480/127@FidoNet
SMS# +48 601 238089, GPG: 2CA0 F353 85FD B0F1 1BD4 73D7 F85D 2717

"Any technology distinguishable from magic is insufficiently advanced."
(c) Gregory Benford

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: Emergency telnet?

2009-12-10T14:16:07Z

On Dec 1, 2009, at 2:53 PM, Adrian von Bidder wrote:

> Thanks for the pointer; [tbm: if you're reading this, perhaps put this info
> on your serial console page for those who don't care to build their own?
> Manufacturer link is
> http://www.ftdichip.com/Products/EvaluationKits/TTL-232R-3V3.htm ] haven't
> researched if the cables are available pre-built and am not familiar enough
> with electronics to build my own.

The specific cable you want is the 'WE' version. Then you can take the cable connected to the display of your 419P and use that to connect to the serial cable. I took two pictures of the way I managed it and put them online at http://www.1m95.nl/qnap/. These are unedited, so rather large :)

First pic shows the way I connected the wire ends from the ftdi cable to the cable inside the qnap, second pic shows the entire contraption connected to the qnap system board. Note the jumper on JP1 that's needed to switch the console output to the correct connector (Thanks to Martin for telling me about that).

Connection details (again, thanks to Martin)

ftdi qnap

RED (VCC) --> RED (VCC)
ORANGE (TX) --> BROWN (RX)
YELLOW (RX) --> ORANGE (TX)
BLACK (GND) --> BLACK (GND)

Note that the cable from the qnap is twisted, so the order won't be the same if you decide to make your own connector directly on the ftdi cable.

@tbm: Feel free to use these pics on your website

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: nslu2: two devices: one by default

2009-12-10T11:38:26Z

On Thu, Dec 10, 2009 at 05:03:40PM +0100, Xan wrote:

> Hi,
>
> I have now this route table:
>
> # route
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> localnet * 255.255.0.0 U 0 0 0 eth0
> localnet * 255.255.0.0 U 0 0 0
> wlan0
> default 172.26.0.1 0.0.0.0 UG 0 0 0
> wlan0
> default 172.26.0.1 0.0.0.0 UG 0 0 0 eth0
>
> (with ip route I get:
> 172.26.0.0/16 dev eth0 proto kernel scope link src 172.26.0.2
> 172.26.0.0/16 dev wlan0 proto kernel scope link src 172.26.0.3
> default via 172.26.0.1 dev wlan0
> default via 172.26.0.1 dev eth0 )
>
> and I want to get that:
>
> # route
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> localnet * 255.255.0.0 U 0 0 0 eth0
> default 172.26.0.1 0.0.0.0 UG 0 0 0 eth0
>
>
> Can I get that with the following command? Please confirm:
>
> ip route del default via 172.26.0.1 dev wlan0
> ip route del 172.26.0.1/16 dev wlan0 proto kernel scope link src 172.26.0.1
>
> and
>
> ip route add 172.26.0.1/16 dev eth0 proto kernel scope link src 172.26.0.1
> ip route add default via 172.26.0.1 dev eth0
>
> ?
>
> Is it correct?

Should work, or you could do:

ip route replace 172.26.0.1/16 dev eth0 proto kernel scope link src 172.26.0.1
ip route replace default via 172.26.0.1 dev eth0

instead of del and add.

--
Len Sroensen

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: nslu2: two devices: one by default

2009-12-10T08:03:40Z

Hi,

I have now this route table:

# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
localnet * 255.255.0.0 U 0 0 0 eth0
localnet * 255.255.0.0 U 0 0 0
wlan0
default 172.26.0.1 0.0.0.0 UG 0 0 0
wlan0
default 172.26.0.1 0.0.0.0 UG 0 0 0 eth0

(with ip route I get:
172.26.0.0/16 dev eth0 proto kernel scope link src 172.26.0.2
172.26.0.0/16 dev wlan0 proto kernel scope link src 172.26.0.3
default via 172.26.0.1 dev wlan0
default via 172.26.0.1 dev eth0 )

and I want to get that:

# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
localnet * 255.255.0.0 U 0 0 0 eth0
default 172.26.0.1 0.0.0.0 UG 0 0 0 eth0

Can I get that with the following command? Please confirm:

ip route del default via 172.26.0.1 dev wlan0
ip route del 172.26.0.1/16 dev wlan0 proto kernel scope link src 172.26.0.1

and

ip route add 172.26.0.1/16 dev eth0 proto kernel scope link src 172.26.0.1
ip route add default via 172.26.0.1 dev eth0

?

Is it correct?

Thanks a lot,
Xan.

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: debian install for KURO-SHEEVA

2009-12-10T07:13:48Z

* Riku Voipio <riku.voipio@...> [2009-12-10 16:50]:
> OTOH if the current SheevaPlug kernel in squeeze works otherwise
> in kuro-sheeva (as from the original post it seems), it is probably
> not worth adding another machine id for it? Would it break booting on
> original sheevaplug, if we add probing the builtin kirkwood sata
> controller to the current sheevaplug platform?

Well, I suspect it will cause more power consumption.

--
Martin Michlmayr
http://www.cyrius.com/

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: debian install for KURO-SHEEVA

2009-12-10T06:50:46Z

Hi Masakazu Asuma,

To the original poster - can you point us to the Linux kernel sources
and/or results of "dmesg" command on the KURO-SHEEVA?

On Thu, Dec 10, 2009 at 10:04:30AM +0000, Martin Michlmayr wrote:
> The SheevaPlug platform code does not initialize PCI since the
> SheevaPlug doesn't have PCI. It probably makes sense to add a
> separate platform file for the KURO-SHEEVA but I don't know any
> details about this device so I cannot say for sure.

OTOH if the current SheevaPlug kernel in squeeze works otherwise
in kuro-sheeva (as from the original post it seems), it is probably
not worth adding another machine id for it? Would it break booting on
original sheevaplug, if we add probing the builtin kirkwood sata
controller to the current sheevaplug platform?

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Richiesta autorizzazione

2009-12-10T03:11:51Z

Buongiorno,

sono Giorgia Ferrari, assistente Marketing di Forum Media Srl, società operante nel campo dell'editoria e della formazione professionale.

La presente per richiederLe l'autorizzazione, ai sensi della vigente normativa sulla Privacy, ad inviarLe, a titolo informativo, tramite e-mail qualche dettaglio sui nostri recenti prodotti editoriali specifici per il settore Tecnico-Amministrativo, Ambiente e Sicurezza, Risorse Umane, Management e Formazione Professionale.

A questo proposito vorremmo inviarLe, a titolo informativo, schede prodotto dettagliate in modo che Lei possa valutare un Suo possibile interesse. Nel caso in cui preferisca ricevere dette informazioni via fax, oppure ad altro indirizzo di posta elettronica, voglia cortesemente trasmetterci i riferimenti.

Teniamo a precisare che, nel rispetto rigoroso della normativa sulla privacy, valuteremo solo autorizzazioni con la modalità opt-in, ossia non invieremo nulla senza un Suo regolare ed espresso assenso.

RingraziandoLa per l'attenzione, Le porgo i miei più cordiali saluti.

Giorgia Ferrari
FORUM MEDIA
www.forum-media.it

Il vostro indirizzo e-mail è trattato in conformità all'Art. 13 del D.lgs 30 giugno 2003 n.196, garantendo la massima riservatezza ed al fine di fornire utili informazioni commerciali per la Sua/Vostra attività. Se non volete ricevere più messaggi inviati per conto dell'operatore si prega di inviare un messaggio all'indirizzo unsubscribe@....

Re: debian install for KURO-SHEEVA

2009-12-10T02:51:29Z

* Holland, John <John.Holland@...> [2009-12-10 11:36]:
> The Kirkwood does support PCI. I just assumed there's nothing
> attached.

Yeah, that's what I meant. Sorry for being unclear.
--
Martin Michlmayr
http://www.cyrius.com/

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: debian install for KURO-SHEEVA

2009-12-10T02:36:12Z

On 10.12.2009, at 11:04, "Martin Michlmayr" <tbm@...> wrote:

> * Holland, John <John.Holland@...> [2009-12-10 08:19]:
>>> I think the esata driver will be included in the base-installer.
>>
>> Could you drop down into a shell and list the attached pci devices?
>
> The SheevaPlug platform code does not initialize PCI since the
> SheevaPlug doesn't have PCI. It probably makes sense

The Kirkwood does support PCI. I just assumed there's nothing
attached. And thought the differences between SheevaPlug and Kuro-
Sheeva are similar to the differences between TS-[12]19 and TS-219P.

> to add a
> separate platform file for the KURO-SHEEVA but I don't know any
> details about this device so I cannot say for sure.
>
> --
> Martin Michlmayr
> http://www.cyrius.com/

___________________________________________

Cellent Finance Solutions AG

Firmensitz: Calwer Straße 33, 70173 Stuttgart
Registergericht: Amtsgericht Stuttgart, HRB 720743
Vorstand: Thomas Wild
Vorsitzender des Aufsichtsrats: Rudolf Zipf

Re: debian install for KURO-SHEEVA

2009-12-10T02:04:30Z

* Holland, John <John.Holland@...> [2009-12-10 08:19]:
> >I think the esata driver will be included in the base-installer.
>
> Could you drop down into a shell and list the attached pci devices?

The SheevaPlug platform code does not initialize PCI since the
SheevaPlug doesn't have PCI. It probably makes sense to add a
separate platform file for the KURO-SHEEVA but I don't know any
details about this device so I cannot say for sure.

--
Martin Michlmayr
http://www.cyrius.com/

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: debian install for KURO-SHEEVA

2009-12-09T23:19:19Z

On 10.12.2009, at 01:54, "東　政一" <azuma-mk@...>
wrote:

> HI!
> I bought a KURO-SHEEVA released recently.
>
> It is added one esata port to the Original SHEEVA-PLUG.
> By using SD card 128mb, I installed the debian squeeze according to
> http://www.cyrius.com/debian/kirkwood/sheevaplug/install.html
>
> But at the disk detection stage of the installation, a external disk
> (500gb)
>
> connected via esata port was never detected.

Being that the eSATA specification does not support powering disks
(power eSATA is something else), connected devices must be powered
seperately.

> I think the esata driver will be included in the base-installer.

Could you drop down into a shell and list the attached pci devices?

$ lspci -vv

Possibly, a different discrete PCI eSATA chip than that in the QNAP
TS-219P is being used. If this holds true, you may require another
eSATA kernel driver than the one supplied with the default debian
distribution.

> Please give me the suggestion for the solution.
>
> BEST REGARDS,
> MASAKAZU AZUMA
>
>
>
>
>
> --
> To UNSUBSCRIBE, email to debian-arm-REQUEST@...
> with a subject of "unsubscribe". Trouble? Contact listmaster@...
>

___________________________________________

Cellent Finance Solutions AG

Firmensitz: Calwer Straße 33, 70173 Stuttgart
Registergericht: Amtsgericht Stuttgart, HRB 720743
Vorstand: Thomas Wild
Vorsitzender des Aufsichtsrats: Rudolf Zipf

debian install for KURO-SHEEVA

2009-12-09T16:26:57Z

HI!
I bought a KURO-SHEEVA released recently.

It is added one esata port to the Original SHEEVA-PLUG.
By using SD card 128mb, I installed the debian squeeze according to
http://www.cyrius.com/debian/kirkwood/sheevaplug/install.html

But at the disk detection stage of the installation, a external disk(500gb)

connected via esata port was never detected.
I think the esata driver will be included in the base-installer.
Please give me the suggestion for the solution.

BEST REGARDS,
MASAKAZU AZUMA

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

debian's installer suspended !

2009-12-08T06:39:27Z

hi !

I am in trouble with debian's installer suspending .
please give me some advise.

console's log s are as below.
==================================================================

U-Boot 1.1.4 (Sep 14 2009 - 15:36:37) Marvell version: 3.4.19

U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CFB00

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000 size 256MB
DRAM CS[1] base 0x10000000 size 256MB
DRAM Total size 512MB 16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB
Flash: 0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled

USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0 [PRIME], egiga1
Hit any key to stop autoboot: 0
Marvell>> mmcinit
Error! cmd : 8, err : 0201
SD found. Card desciption is:
Manufacturer: 0x01, OEM "PA"
Product name: "S128B", revision 5.6
Serial number: 2423100053
Manufacturing date: 10/2005
CRC: 0x00, b0 = 0
Marvell>> fatload mmc 0:1 0x0800000 /uInitrd
reading /uInitrd

2703032 bytes read
Marvell>> fatload mmc 0:1 0x400000 /uImage
reading /uImage

1811960 bytes read
Marvell>> setenv bootargs console=ttyS0,115200n8
base-installer/initramfs-tools/driver-policy=most
Marvell>> bootm 0x400000 0x0800000
## Booting image at 00400000 ...
Image Name: Debian kernel
Created: 2009-11-02 12:19:19 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1811896 Bytes = 1.7 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 00800000 ...
Image Name: debian-installer ramdisk
Created: 2009-11-02 12:19:20 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 2702968 Bytes = 2.6 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK

Starting kernel ...

Uncompressing
Linux....................................................................................................................
done, booting the kernel.

======================================================================================

env vars are as below.

Marvell>> printenv
baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.0.0
console=a0000
e=ttyS0,115200
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/mtdblock2 ro
ethmtu=1500
usb0Mode=host
nandEcc=1bit
ethact=egiga0
serverip=10.10.0.2
ipaddr=10.10.0.1
cesvcid=ULULULULULULPPULULULULULDA
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console)
root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end)
$(mvPhoneConfig); bootm 0x2000000;
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethaddr=00:50:43:01:69:4D
run_diag=no
bootargs=console=ttyS0,115200
mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)
rw root=/dev/mtdblock1 rw
ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none
bootcmd=nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
mainlineLinux=yes
arcNumber=2097
stdin=serial
stdout=serial
stderr=serial
nandEnvBase=a0000
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes
pcieTune=no

Environment size: 1445/131068 bytes

best eregards,
m.azuma

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

RE: E220 Modem

2009-12-07T09:24:53Z

Apparently people have managed to get this modem working on the NSLU2 under different firmware ie openWRTso it seems like a Debian issue, I did find this....

It is a conflict between usb-storage and the option module. You should disable the usb-storage for the mode.

However I need the usb-storage module as I'm using a usb hard disk.

More info....

HUAWEI E220 is supported natively by Linux, over usbserial.ko
(usbserial-generic) interface. Linux kernel versions prior to 2.6.20
have some problems with it.

> Date: Mon, 7 Dec 2009 11:56:02 +0100
> From: wouter@...
> To: brianplatt@...
> CC: debian-arm@...
> Subject: Re: E220 Modem
>
> On Sat, Dec 05, 2009 at 09:48:37PM +0000, Brian Platt wrote:
> > I've been trying for ages to try and get my T-Mobile E220 modem working on my
> > Linksys NSLU2 but I can't for love nor money and hoping someone on here can
> > help me, here's some info....
>
> Perhaps the NSLU2 is just too slow to be able to manage the data rate
> properly?
>
> I've been having similar issues with a USB GigE NIC that I tried
> connecting to my NSLU2. Worked just fine on my laptop, wouldn't even
> initialize on the NSLU2. I can't be sure, of course, but since the
> bitrate is much higher than the clock frequency, it's not impossible
> that the system just can't keep up with the interrupts DMA requests or
> whatever that the USB device needs to do.
>
> Of course I never got to prove this theory, so that's all that it is.
>
> (Side note: yes, I know how stupid the concept of a USB GigE NIC is, but
> the shop had no other choice.)
>
> --
> The biometric identification system at the gates of the CIA headquarters
> works because there's a guard with a large gun making sure no one is
> trying to fool the system.
> http://www.schneier.com/blog/archives/2009/01/biometrics.html

View your other email accounts from your Hotmail inbox. Add them now.

Re: E220 Modem

2009-12-07T02:58:51Z

>>>>> "Wouter" == Wouter Verhelst <wouter@...> writes:

Hi,

Wouter> I've been having similar issues with a USB GigE NIC that I tried
Wouter> connecting to my NSLU2. Worked just fine on my laptop, wouldn't even
Wouter> initialize on the NSLU2. I can't be sure, of course, but since the
Wouter> bitrate is much higher than the clock frequency, it's not impossible
Wouter> that the system just can't keep up with the interrupts DMA requests or
Wouter> whatever that the USB device needs to do.

Or the driver has alignment/dma issues?

Wouter> Of course I never got to prove this theory, so that's all that
Wouter> it is. (Side note: yes, I know how stupid the concept of a USB
Wouter> GigE NIC is, but Wouter> the shop had no other choice.)

What chipset/driver was this?

--
Bye, Peter Korsgaard

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: E220 Modem

2009-12-07T02:56:02Z

On Sat, Dec 05, 2009 at 09:48:37PM +0000, Brian Platt wrote:
> I've been trying for ages to try and get my T-Mobile E220 modem working on my
> Linksys NSLU2 but I can't for love nor money and hoping someone on here can
> help me, here's some info....

Perhaps the NSLU2 is just too slow to be able to manage the data rate
properly?

I've been having similar issues with a USB GigE NIC that I tried
connecting to my NSLU2. Worked just fine on my laptop, wouldn't even
initialize on the NSLU2. I can't be sure, of course, but since the
bitrate is much higher than the clock frequency, it's not impossible
that the system just can't keep up with the interrupts DMA requests or
whatever that the USB device needs to do.

Of course I never got to prove this theory, so that's all that it is.

(Side note: yes, I know how stupid the concept of a USB GigE NIC is, but
the shop had no other choice.)

--
The biometric identification system at the gates of the CIA headquarters
works because there's a guard with a large gun making sure no one is
trying to fool the system.
http://www.schneier.com/blog/archives/2009/01/biometrics.html

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

E220 Modem

2009-12-05T13:48:37Z

I've been trying for ages to try and get my T-Mobile E220 modem working on my Linksys NSLU2 but I can't for love nor money and hoping someone on here can help me, here's some info....

Linux nslu2 2.6.26-2-ixp4xx #1 Thu Aug 20 02:40:52 UTC 2009 armv5tel GNU/Linux

Bus 003 Device 004: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem / E270 HSDPA/HSUPA Mod

dmesg
[42950609.840000] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[42950609.860000] option 3-1:1.0: device disconnected
[42950609.860000] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[42950609.870000] option 3-1:1.1: device disconnected
[42950646.950000] usb 3-1: new full speed USB device using ohci_hcd and address 5
[42950647.130000] usb 3-1: configuration #1 chosen from 1 choice
[42950647.160000] scsi8 : SCSI emulation for USB Mass Storage devices
[42950647.170000] usb 3-1: New USB device found, idVendor=12d1, idProduct=1003
[42950647.180000] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[42950647.180000] usb 3-1: Product: HUAWEI Mobile
[42950647.190000] usb 3-1: Manufacturer: HUAWEI Technologies
[42950647.190000] usb 3-1: USB disconnect, address 5
[42950647.210000] usb-storage: device found at 5
[42950647.210000] usb-storage: waiting for device to settle before scanning
[42950647.970000] usb 3-1: new full speed USB device using ohci_hcd and address 6

I tried
usb_modeswitch -v 0x12d1 -p 0x1003 -d 1
usb_modeswitch -v 0x12d1 -p 0x1003 -H 1

dmesg showed
[42950648.160000] usb 3-1: configuration #1 chosen from 1 choice
[42950648.170000] usb-storage: probe of 3-1:1.0 failed with error -5
[42950648.170000] option 3-1:1.0: GSM modem (1-port) converter detected
[42950648.180000] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB0
[42950648.200000] usb-storage: probe of 3-1:1.1 failed with error -5
[42950648.200000] option 3-1:1.1: GSM modem (1-port) converter detected
[42950648.210000] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB1
[42950648.250000] scsi11 : SCSI emulation for USB Mass Storage devices
[42950648.260000] usb 3-1: New USB device found, idVendor=12d1, idProduct=1003
[42950648.260000] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[42950648.270000] usb 3-1: Product: HUAWEI Mobile
[42950648.280000] usb 3-1: Manufacturer: HUAWEI Technologies
[42950648.290000] usb-storage: device found at 6
[42950648.290000] usb-storage: waiting for device to settle before scanning
[42950653.290000] usb-storage: device scan complete
[42950653.300000] scsi 11:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2
[42950653.380000] sr0: scsi-1 drive
[42950653.380000] sr 11:0:0:0: Attached scsi CD-ROM sr0
[42950653.380000] sr 11:0:0:0: Attached scsi generic sg1 type 5

wvdialconf
Scanning your serial ports for a modem.

ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
WvModem<*1>: Cannot get information for serial port.
ttyUSB0<*1>: ATQ0 V1 E1 -- OK
ttyUSB0<*1>: ATQ0 V1 E1 Z -- OK
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyUSB0<*1>: Modem Identifier: ATI -- Manufacturer: huawei
ttyUSB0<*1>: Speed 9600: AT -- OK
ttyUSB0<*1>: Max speed is 9600; that should be safe.
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
WvModem<*1>: Cannot get information for serial port.
ttyUSB1<*1>: ATQ0 V1 E1 -- OK
ttyUSB1<*1>: ATQ0 V1 E1 Z -- OK
ttyUSB1<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyUSB1<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyUSB1<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyUSB1<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyUSB1<*1>: Modem Identifier: ATI -- Manufacturer: huawei
ttyUSB1<*1>: Speed 9600: AT -- OK
ttyUSB1<*1>: Max speed is 9600; that should be safe.
ttyUSB1<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK

Found a modem on /dev/ttyUSB0.
Modem configuration written to /etc/wvdial.conf.
ttyUSB0<Info>: Speed 9600; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
ttyUSB1<Info>: Speed 9600; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"

wvdial
--> WvDial: Internet dialer version 1.60
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Sending: AT&FE0V1X1&D2&C1S0=0
AT&FE0V1X1&D2&C1S0=0
OK
--> Modem initialized.
wvdial: utils/wvtask.cc:198: WvTaskMan::WvTaskMan(): Assertion `getcontext(&get_stack_return) == 0' failed.
Aborted

New! Receive and respond to mail from other email accounts from within Hotmail Find out how.

Re: Notes on the QNAP-419P

2009-12-02T14:33:35Z

* Adrian von Bidder <avbidder@...> [2009-12-02 22:25]:

> > [ 673.000000] ata1: Unable to stop eDMA
> > [ 673.100000] ata1.00: exception Emask 0x52 SAct 0x1 SErr 0xffffffff
> > action 0xe frozen [ 673.100000] ata1: SError: { RecovData RecovComm
> > UnrecovData Persist Proto HostInt PHYRdyChg PHYInt CommWake 10B8B Dispar
> > BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch }
> > [ 673.100000] ata1.00: cmd 60/08:00:6e:b6:34/00:00:03:00:00/40 tag 0 ncq
> > 4096 in [ 673.100000] res 40/00:00:00:00:00/00:00:00:00:00/00
> > Emask 0x56 (ATA bus error) [ 673.100000] ata1.00: status: { DRDY }
> > [ 673.100000] ata1: hard resetting link
> > +++
>
> Just a quick note: I played around with this device quite a bit, and it didn't
> happen again.

Someone else described the same problem (showed up once, and
everything working fine after a reboot). I'll ask Marvell if they
have an idea.
--
Martin Michlmayr
http://www.cyrius.com/

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: Notes on the QNAP-419P

2009-12-02T13:25:25Z

On Wednesday 02 December 2009 20:15:57 Adrian von Bidder wrote:

> uname -a
> Linux syydelaervli 2.6.30-2-kirkwood #1 Sat Nov 7 00:22:58 UTC 2009
> armv5tel GNU/Linux
>
>
> +++
> [ 673.000000] ata1: Unable to stop eDMA
> [ 673.100000] ata1.00: exception Emask 0x52 SAct 0x1 SErr 0xffffffff
> action 0xe frozen [ 673.100000] ata1: SError: { RecovData RecovComm
> UnrecovData Persist Proto HostInt PHYRdyChg PHYInt CommWake 10B8B Dispar
> BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch }
> [ 673.100000] ata1.00: cmd 60/08:00:6e:b6:34/00:00:03:00:00/40 tag 0 ncq
> 4096 in [ 673.100000] res 40/00:00:00:00:00/00:00:00:00:00/00
> Emask 0x56 (ATA bus error) [ 673.100000] ata1.00: status: { DRDY }
> [ 673.100000] ata1: hard resetting link
> +++

Just a quick note: I played around with this device quite a bit, and it didn't
happen again.

Since the process was moving root fs from this disk to a RAID on two others it
might be a only slightly bad disk (I'll sure do some nasty burn in testing of
that disk) or a rare kernel bug that I didn't trigger anymore.

cheers
-- vbi

--
Wibble.

signature.asc (399 bytes) Download Attachment

Re: Notes on the QNAP-419P

2009-12-02T11:15:57Z

Heyho!

[ for the other debian-arm people: I have installed the 419 as per
instruction I kindly got from Martin, but couldn't boot with a RAID1 root
device. The following may be a defective disk or it may be a kernel bug, not
sure.]

On Tuesday 01 December 2009 13:01:58 you wrote:
> Please try again with RAID. If it doesn't work, I'll do a test
> myself.

Ok, I'm trying it now starting from an almost unmodified Debian installed as
per your instructions (I just changed the rootpw.)

Ooops.

[ context switch ... ]

ssh, then ls /: no output. (I can Ctrl+C though)

given that the disks are brand new and the Kirkwood support in the kernel is
also rather new: kernel bug?

uname -a
Linux syydelaervli 2.6.30-2-kirkwood #1 Sat Nov 7 00:22:58 UTC 2009 armv5tel GNU/Linux

+++
[ 673.000000] ata1: Unable to stop eDMA
[ 673.100000] ata1.00: exception Emask 0x52 SAct 0x1 SErr 0xffffffff action 0xe frozen
[ 673.100000] ata1: SError: { RecovData RecovComm UnrecovData Persist Proto HostInt PHYRdyChg PHYInt CommWake 10B8B Dispar
BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch }
[ 673.100000] ata1.00: cmd 60/08:00:6e:b6:34/00:00:03:00:00/40 tag 0 ncq 4096 in
[ 673.100000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
[ 673.100000] ata1.00: status: { DRDY }
[ 673.100000] ata1: hard resetting link
+++

Seems I don't have disk access anymore. ('ls' in ~ works, ls / doesn't.
reboot doesn't either. So my guess is: anything that is cached is fine...)

Disks are:
[ 3.800000] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 3.840000] ata1.00: ATA-8: ST3500418AS, CC37, max UDMA/133
[ 3.840000] ata1.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 3.900000] ata1.00: configured for UDMA/133
[ 3.900000] scsi 0:0:0:0: Direct-Access ATA ST3500418AS CC37 PQ: 0 ANSI: 5
[ 6.260000] sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
[ 6.260000] sd 0:0:0:0: [sda] Write Protect is off
[ 6.260000] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 6.260000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

(and the same for sdb, sdc, sdd.)

Trying to get that repeated now.

Should I try squeeze/sid/experimental kernels? [generally: is it safe to
update to squeeze+sid on this system? I'm likely to want to try btrfs
soon-ish if architecture support is in standard Debian kernels.]

Unrelated:

[ 1.750000] mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
[ 1.750000] mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
[ 1.790000] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[ 1.830000] mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
[ 1.870000] mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
[ 1.910000] mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
...
[ 33.900000] xor: measuring software checksum speed
[ 33.950000] arm4regs : 1090.000 MB/sec
[ 34.000000] 8regs : 808.400 MB/sec
[ 34.050000] 32regs : 728.400 MB/sec
[ 34.050000] xor: using function: arm4regs (1090.000 MB/sec)

is 'xor: using...' only indicating which software xor method is fastest, or
is md here not using hardware xor?

Just curious, the load on this system will be so light it could use xor on
the 8051 of an old 2400 baud modem for all I care. Or almost. ;-)

cheers
-- vbi

--
featured link: http://www.pool.ntp.org

signature.asc (399 bytes) Download Attachment

nslu2 debian lenny root fs on nfs

2009-12-02T07:24:05Z

Hello All,

I have a nslu2 installed with debian lenny on usb flash drive.

I'm looking for instruction or howto for moving the content of the usb
flash drive to a nfs share to run nslu2 diskless.

I have see some way to do this with APEX and initramfs

sorry for my bad english !

Re: What was installed? (was: NSLU2 with lenny armel: segfaults with filesystem commands (ls, cp, mv))

2009-12-02T01:12:55Z

Thanks Derek, that was exactly what I was looking for! And the Perl script
saved me a lot of work, that made my day!

> The file you want is /var/lib/dpkg/status (or failing that status-old
> which is the previous version).
>
> It's a text file divided into sections by blank lines. Each section should
> start with a 'Package:' line naming the package and then shold contain a
> 'Status:' line like 'Status: install ok installed' (or 'Status: purge ok
> not-installed', etc).
>
> Manual editing could take ages, so I'd use a scripting language to
> generate a series of installation commands. e.g.
>
> perl -ne 'if(/^Package: (.+)$/){$p=$1};if(/^Status: (.+)
> installed$/){print qq{apt-get install },$p,qq{\n};}' </var/lib/dpkg/status
>
> Of course, you could just take it as an opportunity to only install
> packages you want.

That was the purpose of my question from the beginning. D-I installs tons
of packages that other packages depend on, so it is really difficult to
sort out what is needed and what not.

Regards, Richard

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: What was installed? (was: NSLU2 with lenny armel: segfaults with filesystem commands (ls, cp, mv))

2009-12-01T08:42:34Z

The file you want is /var/lib/dpkg/status (or failing that status-old which is the previous version).

It's a text file divided into sections by blank lines. Each section should start with a 'Package:' line naming the package and then shold contain a 'Status:' line like 'Status: install ok installed' (or 'Status: purge ok not-installed', etc).

Manual editing could take ages, so I'd use a scripting language to generate a series of installation commands. e.g.

perl -ne 'if(/^Package: (.+)$/){$p=$1};if(/^Status: (.+) installed$/){print qq{apt-get install },$p,qq{\n};}' < /var/lib/dpkg/status

Of course, you could just take it as an opportunity to only install packages you want.

2009/12/1 <u7l11ey@...>

Hello,

it turned out that the segfaults that where happening with certain
filesystem commands on my NSLU2 were most likely caused by a faulty USB
flash stick after all. More and more errors started happening, so I
finally couldn't deny that possibility any longer.

Some parts of the filesystem on that stick are still readable, but my slug
won't boot from it any more. I bought a new one and am just finishing a
fresh Debian install. Is there a way to find out what which software
packages were installed on the old stick, by reading certain files? If so,
which files must I look for, and how can I extract that info from them?

Regards, Richard

--
To UNSUBSCRIBE, email to debian-arm-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

--
Derek.