Followed the instructions on page:

http://sardine.garage.maemo.org/getting_started.html

Now my device, during startup, reboots every time.....
(after the intial startup screeen of kernel version etc)

http://maemo.org/

btw. if there is anything exciting to report from sardine, plz dont hesitate to tell us :-)

@Nightmare - not really sure what you are suggesting... is it that the OP shouldn't be using Sardine on the device? Perhaps s/he falls into the "tinkerer" category - I know I do. I tried Sardine and also got the reboot loop - not surprising really, as "apt-get upgrade" failed due to a multitude of missing dependencies!

Just out of interest, has anyone succeeded installing Sardine on the device by following the Wiki "getting started" instructions?

Right. I feel bad for the Nokia devs right now.

More notes:

On the same page, no less. That said, it'll just whitescreen as the AF will fail to init.

From: http://maemo.org/maemowiki/SardineDistro (the Current Issues page)

The correct way to do it is at: http://maemo.org/maemowiki/HowTo_GetStartedWithSardine --- put together by me (from the notes of Fanoush and others) --- I followed the process myself, and it worked fine, although Sardine isn't terribly useful right now. I didn't notice any massive gains in performance, reliability, or flash player version =)

I was able to do it a while ago, but it took a couple tries before I managed to figure out what you needed to do to make it work. Obviously disabling the lifeguard reset was key... I'm still running it on a day-to-day basis, and I bug the developers in my spare time to fix stuff If anyone is looking for major changes they will be disappointed since there are few things that are recognizable as different. Mostly I run into packages that aren't compatible in one way or another with the new changes.

I wish I had a better idea of what the devs are concentrating on. There's an RSS feed for the changes (http://repository.maemo.org/sardine/rss20.xml) but it seems pretty slow-paced and related to small bug fixes as opposed to new applications or larger changes. I'm guessing the exciting stuff still happens behind closed doors so as to facilitate a bigger "splash" when it's finally released.

Larry

Thanks Larry - I thought the missing dependencies and failed upgrade would have been responsible for the reboots, but I must admit I didn't disable the lifeguard reset, will try that later this wek. Did you get any errors when performing the apt-get upgrade on a chroot'd rsync'd copy of OS2006?

I am a AIX and RedHat guy, so I am not really familiar with apt-get. I saw the upgrade option and curiosity got the best of me.

I am running OS2006

The next thing I know I was upgrading some packages, it got to maemo-launcher and POW (REBOOT), OK no problem came right back up, ran apt-get upgrade again, ERROR, says runs dpkg --configure -a , I think that was the command, anyway ran that. ERROR tells me maemo-launcher is hosed.

This system is booted from MMC, I downloaded maemo-launcher, booted back to flash, insmod ext2, mounted my mmcp2 and used dpkg --admin --root and set it to the mnt dirs. I was then able to put maemo-launcher back onto the mounted system. It was kind of cool, I booted back onto mmcp2 and dpkg and apt-get were all set again.

Questions:

Does upgrading get me anything, I have heard about the reboot loops?

Are reboot loops only in sardine?

Now when I run apt-get upgrade, it says 0 upgraded, 4 not upgraded

The following packages have been kept back
hildon-fmmm
hildon-widgetsmm
libglibmm-2.4.1
libgtkmm-2.4.1

What does kept back mean? Can I download them and install them with dpkg? Should I, were they kept back for a reason? Am I in am unstable state?

IS THE WORLD ENDING???

Anyway, if anyone can shed any light into any of this I'd be grateful~