[maemo-developers] [maemo-developers] Re: Troubles installing Herring
From: Neil MacLeod gmane at nmacleod.comDate: Thu Dec 21 01:36:43 EET 2006
- Previous message: [maemo-developers] Troubles installing Herring
- Next message: [maemo-developers] mount problem
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Aniello Del Sorbo wrote: > Hallo, > > it's been three days since I've been trying to install Herring/Sardine > onto my 770 ("Melkor"). > > At first I tried to install Sardine, but whenever I booted Melkor from > the MMC I got a white screen (as explained in this bug report: > > (https://maemo.org/bugzilla/show_bug.cgi?id=910) > > Thus I choose to try our Herring. > > I decided to start from scratch: I flashed Melkor to IT2006 > (SU-18_2006SE_2.2006.39-14_PR_F5_MR0_ARM) and installed OSSO XTerm and > flashed with the new initfs as explained in the instructions. > > Copied the IT2006 onto the MMC again and tried to boot from it. It worked. > > Restarted from the flash, I then chrooted to /opt, changed the > sources.list (I just left the herring repository inside) and did this: > > apt-get update (worked fine) > apt-get install hildon-application-framework > > This already gave me some errors (same as Sardine however), specifically: > > /bin/sh: /usr/sbin/dpkg-preconfigure: not found > I don't think this is an issue. > and > > ldconfig: Can't open configuration file /etc/ld.so.conf: No such file or > directory > After chroot, execute "touch /etc/ld.so.conf" to create the missing file in which case you won't see this error during the update. > (the latter, of course, for many packages) > > I went forward and did the: > > apt-get upgrade > > it gave me the very same errors (sardine had more, so I think that was > related to some relatively new changes to the sardine reps) plus this: > At some point it should have output a message saying that several packages were being withheld - you should have made a note of these packages and installed them manually at the end. The lack of these packages will probably result in a white screen on boot. > *** > * Updating MIME database in /usr/share/mime... > * Warning: Unknown media type in type 'sketch/png' > *** > > (every now and then) > > and: > > Setting up libx11-6 (1.0.0-6osso4) ... > fgrep: invalid option -- x Probably not good. > > moreover, when it tried to stop maemo-launcher it told me that that was > not running: > > Stopping Maemo Launcher: maemo-launcher not running. > Remember that you are upgrading a chroot filesystem - to all intents and purposes nothing is running which is why you can update the OS. > while, when trying to starting it up again: > > Installing new version of config file /etc/init.d/maemo-launcher ... > Starting Maemo Launcher: maemo-launchermaemo-launcher[3539]: GLIB > CRITICAL ** Gdk - gdk_display_close: assertion `GDK_IS_DISPLAY > (display)' failed > . > > maemo-defender: died stating file a: '/proc/3541/exe' > maemo-launcher: error rising the oom shield for pid=3541 status=7680 > See above - you're updating the chroot'ed filesystem so the updater is simply getting confused here. I don't think the above is an issue (would be nice if the installer were a bit smarter though). > > and it stopped here. > Sounds about right. > an: apt-get upgrade didn't give me any issues, so I tried to reboot. > I kept the MENU key pressed, but it keeps booting from flash (even if I > read the line "keep MENU key pressed for advanced options bla bla"...) > > Did something went really wrong ? and what ? Are you not getting the boot options screen? For me it pops up automatically with a 30 second countdown timer, I don't need to press the menu button at all. I think the 770 will boot from internal flash if the device you are trying to boot from is invalid - if you do get the boot options screen perhaps your MMC filesystem is corrupted. Before rebooting the 770 I think it's always useful to execute sync (three times - just an old habit! sync will flush any unwritten system buffers) then run "shutdown -r now" (having exited from the chroot fs) to reboot the device. Depending on how you reboot your 770 it may lead to a corrupt MMC/ext2 file system. > > From what I have understood the first errors should be normal and cause > no harm. But the last ones ? > > Any ideas ? > > -- > anidel
- Previous message: [maemo-developers] Troubles installing Herring
- Next message: [maemo-developers] mount problem
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]