maemo.org - Talk - First Diablo SSU update is out (4.2008.30-2)

maemo.org - Talk (https://talk.maemo.org/index.php)

- OS2008 / Maemo 4 / Chinook - Diablo (https://talk.maemo.org/forumdisplay.php?f=29)

- - First Diablo SSU update is out (4.2008.30-2) (https://talk.maemo.org/showthread.php?t=22733)

Re: First Diablo SSU update is out (4.2008.30-2)

Quote:

Originally Posted by jhford (Post 212648)

Why can't I see it on my tablet?

~~Because you uninstalled osso-software-version-rx*4.~~

Or, more likely, since the maemo.org and Nokia Maemo-related services are currently down. . . .

Re: First Diablo SSU update is out (4.2008.30-2)

Quote:

Originally Posted by qole (Post 212469)

Ok, as root, I had to do the mount command

Code:

mount -t jffs2 /dev/mtdblock4 /debian

(you might need to mkdir /debian first)

Then I had to use my very newest version of the chroot scripts to chroot in. You need the new version, otherwise you could overwrite important files.

The /home/user/.chroot file needs this:

Code:

IMGFILE=/dev/mtdblock4

IMGFS=jffs2

It will fail to mount the partition, but you've already mounted it manually, and then it works.

I was able to do apt-get -f install in the chroot, and it installed then rebooted automatically... back to my flash partition! Yay!

Note, I cleared some space to get it to finish the install... You'll need to do it too, if you're in this boat.

Hi,

I've done successfully all steps up to changing the .chroot file.

What would be the next step?

I've tried /sbin/debian and gives the error:

Code:

 

Setting up the chroot...



/sbin/debian: line 112: gxmessage: not found

Thanks.

Re: First Diablo SSU update is out (4.2008.30-2)

Quote:

Originally Posted by GeneralAntilles (Post 212695)

Because you uninstalled osso-software-version-rx*4.

Did I just do the same? I couldn't get maemo-recorder to install with app manager so I tried to do it with apt-get install, but I got the same message I got when I first installed diablo telling me to apt-get -f install.........

Quote:

my_tablet:~# apt-get install telnet
Reading package lists... Done
Building dependency tree
Reading state information... Done
telnet is already the newest version.
You might want to run `apt-get -f install' to correct these:
The following packages have unmet dependencies:
osso-software-version-rx44: Depends: kernel-diablo-flasher (= 2.6.21-200829maemo1) but 2.6.21-200823maemo3 is to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).

my_tablet:~# apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages will be REMOVED:
osso-software-version-rx44
0 upgraded, 0 newly installed, 1 to remove and 44 not upgraded.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Do you want to continue [Y/n]? y
(Reading database ... 24207 files and directories currently installed.)
Removing osso-software-version-rx44 ...

my_tablet:~# apt-get install maemo-recorder
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
gstreamer0.10-plugins-extra
Use 'apt-get autoremove' to remove them.
The following packages will be upgraded:
maemo-recorder
1 upgraded, 0 newly installed, 0 to remove and 43 not upgraded.
Need to get 77.4kB of archives.
After unpacking 20.5kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
maemo-recorder
Install these packages without verification [y/N]? y
Get:1 http://repository.maemo.org chinook/free maemo-recorder 0.2.0 [77.4kB]
Fetched 77.4kB in 2s (32.8kB/s)
(Reading database ... 24206 files and directories currently installed.)
Preparing to replace maemo-recorder 0.2.0 (using .../maemo-recorder_0.2.0_armel.deb) ...
Unpacking replacement maemo-recorder ...
dpkg: error processing /var/cache/apt/archives/maemo-recorder_0.2.0_armel.deb (--unpack):
trying to overwrite `/usr/lib/gstreamer-0.10/libgstwavenc.so', which is also in package gstreamer0.10-plugins-extra
Errors were encountered while processing:
/var/cache/apt/archives/maemo-recorder_0.2.0_armel.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
my_tablet:~#

Re: First Diablo SSU update is out (4.2008.30-2)

this doesn't work for some reason. i read this thread and nobody seems to have the same problems. this is what happens in xterm.

/home/user # apt-get clean
/home/user # apt-get install osso-software-version-rx34-unlocked
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
osso-software-version-rx34-unlocked: Depends: bluez-utils (>= 3.28-0osso4) but it is not going to be installed
Depends: busybox (>= 3:1.6.1.legal-1osso15) but it is not going to be installed
Depends: dnsmasq (>= 2.35-1osso4) but it is not going to be installed
Depends: fakedebconf (>= 0.0.2) but it is not going to be installed
Depends: hal (>= 0.5.11~git20080402-1osso1) but it is not going to be installed
Depends: hildon-application-framework-rx34-rx44 (>= 2008.10) but it is not going to be installed
Depends: ke-recv (>= 2.27-1) but it is not going to be installed
Depends: libconbtui0 (>= 1.5.46) but it is not going to be installed
Depends: libicd-network-dun (>= 1:0.18) but it is not going to be installed
Depends: libicd-network-ipv6 (>= 0.15-0.1) but it is not going to be installed
Depends: lsb-base (>= 3.1-23osso2) but it is not going to be installed
Depends: netbase (>= 1:4.24.osso9) but it is not going to be installed
Depends: osso-applet-device (>= 2.1.13-1) but it is not going to be installed
Depends: osso-applet-languageregional (>= 2.1.9-1) but it is not going to be installed
Depends: osso-applet-memory (>= 2.2.12-1) but it is not going to be installed
Depends: osso-bluez-compat (>= 0.14) but it is not going to be installed
Depends: osso-connectivity (>= 2.2.0-17) but it is not going to be installed
Depends: osso-connectivity-ui (>= 1.5.46) but it is not going to be installed
Depends: osso-connectivity-ui-btsettings (>= 1.5.46) but it is not going to be installed
Depends: osso-connectivity-ui-conndlgs (>= 1.5.46) but it is not going to be installed
Depends: osso-connectivity-ui-connmgr (>= 1.5.46) but it is not going to be installed
Depends: osso-connectivity-ui-gwsettings (>= 1.5.46) but it is not going to be installed
Depends: osso-connectivity-ui-gwwizard (>= 1.5.46) but it is not going to be installed
Depends: osso-connectivity-ui-iapsettings (>= 1.5.46) but it is not going to be installed
Depends: osso-connectivity-ui-statusbar (>= 1.5.46) but it is not going to be installed
Depends: osso-core (>= 0.200720.1) but it is not going to be installed
Depends: osso-core-busybox (>= 0.200720.1) but it is not going to be installed
Depends: osso-dsm (>= 5:2008w01.1) but it is not going to be installed
Depends: osso-filemanager (>= 1:3003) but it is not going to be installed
Depends: osso-ipv6 (>= 0.1-12) but it is not going to be installed
Depends: osso-startup-wizard (>= 2.2.26-1) but it is not going to be installed
Depends: ppp (>= 2.4.4rel-8osso4) but it is not going to be installed
Depends: telepathy-stream-engine (>= 0.4.0-0osso6) but 0.4.0-0osso5 is to be installed
Depends: udev (>= 0.114-2osso3) but it is not going to be installed
Depends: wide-dhcpv6-client (>= 20070507-3osso5) but it is not going to be installed
E: Broken packages
/home/user #

Re: First Diablo SSU update is out (4.2008.30-2)

Just a note, if you are unsure about space,

mkdir /media/mmc2/cache/apt/archives
rm /var/cache/apt/archives
ln -s /media/mmc2/cache/apt/archives /var/cache/apt/archives

(It's a little trick I learnt from http://mariusv.wordpress.com/2008/05...sant-surprise/ when installing *everything* (a total chinook to diablo install ;)))

@Saturn

[s]Dunno why using qole's chroot scripts is an requirement.[/s]. (Thanks Bundyo!)
If you are root and mounted mtdblock4 on /debian,
just run "chroot /debian"

Re: First Diablo SSU update is out (4.2008.30-2)

maemo.org and related Nokia services are currently down.

Anyone trying to update or install applications from Nokia and maemo.org sources will be unable to.

Re: First Diablo SSU update is out (4.2008.30-2)

@qwerty12:

You also have to mount /dev /proc /sys and /tmp :) Before chrooting.

EDIT: With --bind.

mount --bind /dev [your-mount-point]/dev

Re: First Diablo SSU update is out (4.2008.30-2)

Quote:

Originally Posted by GeneralAntilles (Post 212703)

maemo.org and related Nokia services are currently down.

Anyone trying to update or install applications from Nokia and maemo.org sources will be unable to.

Well, looks like the ISP jumped the gun a bit on the server move (location, not hardware, yet, but it was supposed to be tomorrow). Everything should be back up later today.

The good news is this is the first step for getting the new servers for maemo.org in place. ;)

Re: First Diablo SSU update is out (4.2008.30-2)

Bigger, badder and with a huge pipe? :D

Re: First Diablo SSU update is out (4.2008.30-2)

I had some problems with the update. Long time ago, I had the bad idea of running an apt-get remove gizmo-installer. For some reason in the dependency handling of apt-get, apt-get kindly suggested me to remove some packages that were no longer required:

Code:

initfs-flasher kernel-diablo-flasher flash-and-reboot

oops... I said yes. This screwed up the update: only part of the updates were installed yesterday on my N810, and the system did not reflash nor reboot itself. I struggled for a while in the attempt to re-install the packages that I had accidentally removed, and in the end I had to go for a quicker fix: reflashing the tablet. Has anybody else incurred in the accidental removal of these packages? Is there a smarter fix than what I did?