• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 2 3 [4] 5 6 ... 30
46  Linux Stuff / Kernel / Re: sheeva/dream 3.2.4 new kernel available on: February 07, 2012, 02:05:41 PM
The *.config files (which were present in your previous kennel builds) are not there.
They are.
Yes - they are there now.
But they aren't there for 3.2.5.
47  Linux Stuff / Kernel / Re: sheeva/dream 3.2.4 new kernel available on: February 06, 2012, 03:55:48 PM
The *.config files (which were present in your previous kennel builds) are not there.
48  Hardware and U-Boot firmware / Hardware / Re: Real Time Clock dead? on: February 02, 2012, 02:44:40 PM
Thanks.  I'll give that a go.

Minor problem at first as:
  • I couldn't get one the case apart (one of the screws was locked in place, but eventually I won).
  • I have a Rev1.3 motherboard, which looks different and doesn't have the big silver button form the middle of the image.  Then I realized that's not the battery....

It's an AG10.  So I'll look for a local supplier tomorrow.
49  Hardware and U-Boot firmware / Hardware / Real Time Clock dead? on: February 01, 2012, 02:59:54 PM
The power to my SheevaPlug was cut two days ago, and on rebooting the system started on 1 Jan 2000.

ntpd fixes this once it gets going, but the system does now start after reboot with the wrong time, which didn't use to happen.

Trying to run the rtctest.c program (in src/Documentation/rtc.txt) produces a timeout to /dev/rtc0

Is this recoverable?  I can live with it - just need to make sure that things like boinc don't start until after ntp is up,  rather than its default of "as soon as the file systems are there".
50  Linux Stuff / Linux distributions / Re: why I can not start NFS daemon? on: December 07, 2011, 04:49:02 PM
Do the syslog message show anything more useful?
51  Linux Stuff / Kernel / Re: 3.1.4 new kernel available on: December 01, 2011, 01:47:27 PM
Thanks.  Running fine on a SheevaPlug with Debian squeeze.
52  Linux Stuff / Kernel / Re: 3.1.2 new kernel available on: November 27, 2011, 04:30:06 PM
No, I'm American.  American phrases are borrowed from all over.
Indeed - many from the (English) Bible or Shakespeare - "giving up the ghost" is the former.
53  Linux Stuff / Kernel / Re: 3.1.2 new kernel available on: November 22, 2011, 03:04:49 PM
Many thanks.
OK for me on a SheevaPlug, running with a Buffalo Wireless-N Nfiniti dongle (rt2800usb).
54  Linux Stuff / Kernel / Re: 3.1 new kernel available on: October 24, 2011, 05:03:59 PM
3.1 is now available.
Thanks - up and running on my SheevaPlug.
The mirror may not always be current.
Still hasn't updated since 2.6.38
The kernel source is here, for those of you who need to compile custom modules.
Isn't that just the stock 3.1 kernel from kernel.org + the patches form your links?  If so, a download from kernel.org + patches would be quicker, and save your download allowance.
PS: How does one build a single module, assuming I've got the source in place and applied your config?  "make <module_name>"?
55  Linux Stuff / Kernel / Re: 3.0.7 new kernel available on: October 21, 2011, 03:59:57 PM
It would seem that with 3.0.7 on a sheevaplug that all led control is disabled
Setting any values of brightness has no effect.
Setting 0 for blue works for me, but 1 to 255 are all the same intensity.  red and green have never done anything (well, until recently green controlled the blue LED, but that was just a labelling oddity).
56  Hardware and U-Boot firmware / Hardware / Re: question regarding the Guruplug on: October 13, 2011, 05:00:40 PM
... and I am not sure an application written for a x86 intel platform will work on this sheevaplug ARM architecture without modifying the application, is that correct?
Only if you've written some hardware architecture-specific code into the application.
Otherwise you will have to compile and link it for ARM, but not modify anything.
57  Linux Stuff / Kernel / Re: 3.0.4 new kernel available on: September 18, 2011, 06:42:30 PM
On a SheevaPlug the blue led is now controlled by the plug:blue:health trigger (instead of the green one doing it, as previosuly).
The green and red triggers don't affect anything,.
58  General Category / General Discussion / Re: Which device is right for us? on: September 09, 2011, 05:44:39 PM
More expensive than Plugs, but:


59  Linux Stuff / Kernel / Re: 3.0.3 new kernel available on: August 31, 2011, 05:39:21 PM
The patch didn't apply cleanly to 3.0.4, ...
Hardly surprising as the standard kernel code has "plug:green:health" set as MPP49_GPIO, not MPP48_GPIO and no sign of any blue one (in the code - it does have a blue LED and a green one, with no sign of a red one).
Mind you - triggering the "plug:green:health" device does actually change the blue LED, and changing the "plug:red:health" trigger does nothing, so perhaps the code from this patch would actually correct things so that blue and green LEDs can both be changed.

The patch against the 3.0.4 code would be:
--- linux-3.0.4/arch/arm/mach-kirkwood/sheevaplug-setup.c.orig  2011-08-29 21:56:30.000000000 +0100
+++ linux-3.0.4/arch/arm/mach-kirkwood/sheevaplug-setup.c       2011-09-01 01:35:03.000000000 +0100
@@ -66,6 +66,12 @@
                .name                   = "plug:green:health",
                .default_trigger        = "default-on",
+               .gpio                   = 48,
+               .active_low             = 1,
+       },
+       {
+               .name                   = "plug:blue:health",
+               .default_trigger        = "default-on",
                .gpio                   = 49,
                .active_low             = 1,
@@ -86,8 +92,9 @@
 static unsigned int sheevaplug_mpp_config[] __initdata = {
        MPP29_GPIO,     /* USB Power Enable */
-       MPP46_GPIO,     /* LED Red */
-       MPP49_GPIO,     /* LED */
+       MPP46_GPIO,     /* LED Red Misc */
+       MPP48_GPIO,     /* LED Green Health */
+       MPP49_GPIO,     /* LED Blue Health */
60  Linux Stuff / Kernel / Re: mmc support in 2.6.37 and 2.6.38 on: August 29, 2011, 04:36:29 PM
I have a vague memory of reading somewhere that inserting an SD card (or CF, or XD) into a USB adaptor doesn't produce any resulting signal, so it can only be detected by continually polling them.
On a desktop system this would be done by hal(?), which probably isn't running on the Plug.
So, if the adaptor behaves like USB this could be the problem.
Pages: 1 2 3 [4] 5 6 ... 30