fit-IoT Users Forum

madgrt wrote:

Kleborp wrote:There's an easier fix for this, after looking at the patch and related code I found the following comment:

Thank-you and well done Kleborp!
A very nice fix until the Ubuntu kernel is patched. Have you submitted the bug fix to them yet?

I don't think this is worth a bug fix, it's not really a bug on Ubuntu's (or any other distro's) end, but more upstream (kernel developers), and I think someone already submitted the above patch to their mailling list so hopefully the next kernel release has the patch added.

Great!!
Work just perfectly with my debian 5.03
Easy to fix. Just wnat to say congratulation...

The issue is now fixed by default with Karmic.

I have a 2.0ghz FitPC2 and just bought a 1.1ghz FitPC2. The 2.0ghz one works beautifully, the 1.1ghz version won't reboot. I tried the 'reboot=b' solution on Ubuntu 11.04 - no go

Any suggestions?

confirmed reboot=b doesn't work in 11.04 server for 1.1ghz fitpc2

what might be the non-obvious difference between the 1.1 and 2 ghz models?

any ideas anyone other recompilation. i think if kernel updates happen then we have to rebuild it every time right?

Do the units have the same BIOS version?

well my 1.1ghz model is the latest version as per the fit website (bios date may 2010).

if the bios is the issue then why doesn't the firm release a bios fix ???

I'm not saying it is the BIOS, but since we're asking to reboot through BIOS/ACPI it is a good place to start looking. Matthew Garrett has an interesting blog post about rebooting.

Fixing the BIOS is unfortunately non-trivial.

ok will read. BTW there's another post in the 11.04 sub-forum (http://www.fit-pc2.com/forum/viewtopic.php?f=70&t=2369) where someone says installing the desktop (kernel?) version makes things work...hmm.