I have finally got my walnut card from IBM and compiled linux for it.
I used the version from Frank (mvista) on area51 dated 01_03_03 but changed
the configuration to remove kgdb and enable float emulation.
Things looks quite good I now have a debian potato for ppc running on the card
but there is a few problems.
1. It kills the Ethernet port on a cisco catalyst 5505 switch/router.
This is something I never seen before but when I use a port that is 10Mb
linux sends out something that the switch dose not like and it simply
disable the port. I put a 3com 10Mb hub between but the same problem so it's
not electric. I was however unsuccessful in getting any useful information
from the network people on what rule was violated. It dose not happen on a
100Mb port. I guess that it is some clock or timing that is wrong in the
Ethernet driver.
2. it's not possible to run gdb
3. dpkg segfaults
It's quite easy to get into a state where dpkg segfaults. A reboot fixes
the problem. To get into the mess again all you have to do is start emacs.
On the bright side alot of stuff works. I did the kernel compile test and that
worked.
If anybody want's to run debian I could write a small howto but I'am not going
to do that if nobody ask's for it.
--
Kenneth Johansson
Ericsson Business Innovation AB Tel: +46 8 404 71 83
Viderögatan 3 Fax: +46 8 404 72 72
164 80 Stockholm kenneth.johansson@inn.ericsson.se
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Kenneth Johansson wrote:
I have finally got my walnut card from IBM and compiled linux for it.
I used the version from Frank (mvista) on area51 dated 01_03_03 but changed
the configuration to remove kgdb and enable float emulation.
Things looks quite good I now have a debian potato for ppc running on the card
but there is a few problems.
1. It kills the Ethernet port on a cisco catalyst 5505 switch/router.
This is something I never seen before but when I use a port that is 10Mb
linux sends out something that the switch dose not like and it simply
disable the port. I put a 3com 10Mb hub between but the same problem so it's
not electric. I was however unsuccessful in getting any useful information
from the network people on what rule was violated. It dose not happen on a
100Mb port. I guess that it is some clock or timing that is wrong in the
Ethernet driver.
Can you get a network trace to see what packets are involved?
2. it's not possible to run gdb
Yes, ptrace is still not yet implemented for the 4xx. This means that both gdb
and gdbserver do not work. I have been working on this but don't yet have a
robust version in place. I hope to have this available very soon. (If anyone
feels like debugging this, I can send them my current patch.)
3. dpkg segfaults
It's quite easy to get into a state where dpkg segfaults. A reboot fixes
the problem. To get into the mess again all you have to do is start emacs.
On the bright side alot of stuff works. I did the kernel compile test and that
worked.
If anybody want's to run debian I could write a small howto but I'am not going
to do that if nobody ask's for it.
Kenneth,
Thanks for the feedback.
-Frank
--
Frank Rowand [off-list ref]
MontaVista Software, Inc
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Frank Rowand wrote:
Kenneth Johansson wrote:
quoted
> Things looks quite good I now have a debian potato for ppc running on the card
quoted
but there is a few problems.
1. It kills the Ethernet port on a cisco catalyst 5505 switch/router.
Can you get a network trace to see what packets are involved?
Yes I can snoop it with tcpdump but it has to wait until next week. This will only
show something if the content of the packet is wrong but I think the problem is more
timing related but that is only a guess.
quoted
2. it's not possible to run gdb
Yes, ptrace is still not yet implemented for the 4xx. This means that both gdb
That explains it :)
robust version in place. I hope to have this available very soon. (If anyone
feels like debugging this, I can send them my current patch.)
I can test it but don't have much time to actually debug this right now. Once this works
it should be simpler to find out what the kernel dose when running emacs that prevents dpkg
to run after it.
--
Kenneth Johansson
Ericsson Business Innovation AB Tel: +46 8 404 71 83
Viderögatan 3 Fax: +46 8 404 72 72
164 80 Stockholm kenneth.johansson@inn.ericsson.se
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/