[Archive] TomTom v9 Firmware and Maps - Page 250 - GSM-Forum

dsa8310 · 07-14-2012, 13:26

Link to dsa-14July2012.zip:

dsa-14July2012.zip

Here's a quick release, with a real v9(.026) swap enabled kernel to be used by MB.
I have also increased the RSS parameter to 26 instead of 23 in skins.sh .

The August release will deal with K50 & MB, both enabled, with the following rule: both K50 & MB on a v9 or v8 cab means a v9 MB kernel.

ahkp3 · 07-14-2012, 13:26

Quote:

Originally Posted by dsa8310

I was right, v8, v9 they use kernel 2.6.13.
2.6.23 is actually a v10 kernel (with SWAP enabled by default!).

Sorry to ask again, but did you check v9.430 specifically regarding the kernel version?

This version is clearly marked by TomTom to use a 2.6.23 kernel on their GPL website . I can't believe, that TomTom isn't even able to publish correct and consistent information regarding their own linux builds.

dsa8310 · 07-14-2012, 13:41

You want to ruin my TT setup

...

~ # uname -a
Linux TomTom GO 910 2.6.13-tt842337 #1 Tue Jan 31 10:21:35 CET 2012 armv4tl unknown

There is no such thing as a 2.6.23 v9 kernel, even the processor type is different, judging from the different toolchain. Just 2.6.13.
2.6.23 it's actually a v10 kernel, thank you very much, but no thank you...

But again, their v9.026 kernel source seems good enough for the v9 MB.

dsa8310 · 07-14-2012, 13:51

Oops... the so called v9 MB kernel has disabled my on/off button (on go910). So it's not that good after all.
Maybe dsa-30June should be still used instead.

dsa8310 · 07-14-2012, 14:03

We could choose a lower kernel for MB. But I really don't have time to do it now...
Use dsa-30June to alleviate the on/off button issue.

ahkp3 · 07-14-2012, 15:15

Quote:

Originally Posted by dsa8310

~ # uname -a
Linux TomTom GO 910 2.6.13-tt842337 #1 Tue Jan 31 10:21:35 CET 2012 armv4tl unknown

There is no such thing as a 2.6.23 v9 kernel, even the processor type is different, judging from the different toolchain. Just 2.6.13.
2.6.23 it's actually a v10 kernel, thank you very much, but no thank you...

Quote:

Originally Posted by dsa8310

Oops... the so called v9 MB kernel has disabled my on/off button (on go910). So it's not that good after all.
Maybe dsa-30June should be still used instead.

Thank you and sorry for the hassles, DSA! I do really, really appreciate all your effort. You just gave proof, that TomTom does either not have a damn clue about their linux versions or is just playing around once again with us.

I will stick with DSA June 30 or earlier versions until TomTom has released the still missing linux builds. Memboost with 32 MB devices and Navcore 9.430 worked absolutely fine, even during prolonged stress tests.

dsa8310 · 07-14-2012, 22:27

TT has shuffled its GPL page beyond recognition...

Do NOT use dsa-14July, it contains a random v9 MB kernel
Use dsa-30June for now.

However, I've got the correct files (from their names, the links are wrong) and I'm going to release shortly the good v9 kernel(s).

ahkp3 · 07-14-2012, 22:32

Quote:

Originally Posted by dsa8310

TT has shuffled its GPL page beyond recognition...

Thank you very much, indeed! I came across that, too, but I just thought that by now I was way to stupid to even read their web pages....

dsa8310 · 07-14-2012, 23:24

Link to dsa-15July2012.zip:

dsa-15July2012.zip

New: a good v9.170 swap enabled kernel stands as the v9 MB.

It's zImage.734578.
The rest, related to simultaneous K50 & MB, in August.

keessie74 · 07-15-2012, 23:30

Thanks. That's a kernel with automatic power on when you put the device on the cradle. I played with that version before.

dsa8310 · 07-16-2012, 00:28

Yes, I'd say we nailed it this time!

(even the sound volume is better (normal!), beside about 25MB of reported free memory during navigation & jukebox, on my go910)

I think I will promote the v9.170 kernel as K50 too (without swapping).

The MB & K50 is just a detail that would permit real x50 devices to use the v9 MB kernel while installing a v8 (truck) NC. But it's not that urgent, after all real x50 devices have got 64MB of RAM.

Although my 64MB go910 seems more responsive with that much free RAM ?!

keessie74 · 07-16-2012, 21:55

I have a real x50 device. I will do some tests as soon as new DSA will be ready.

dsa8310 · 07-23-2012, 18:25

Link to dsa-23July2012.zip:

dsa-23July2012.zip

New: both MB & K50 could be selected simultaneously to get the MB enabled v9 kernel (regardless of NC version).

The combination is useful to native x50 devices installing a v8 NC (like the truck NC) and wishing MB support beside a v9 kernel.
Just MB means a swap enabled kernel of appropriate version (v8, v89 or v9) according to NC's version (between v8.500 and v9.000 it's v89).
Just K50 means the v9 kernel taken from NC v9.205 (no swap).

We are done, aren't we?

dsa8310 · 07-23-2012, 18:30

From my part, I wish TT would release the source of their v9.205 kernel (#547200).
It's the only kernel working well on my go910 with CF card & the current full Europe map...

dsa8310 · 07-26-2012, 13:13

I have found a solution to the map issue: it seems that all favorites (including home location) should be converted to POIs - while in Home/Operate my Go - and then file mapsettings.cfg (from inside the map folder) should be deleted; another Home/Operate my Go will recreate the mapsettings.cfg file properly (hollow).
In the future, use POIs to navigate to preferred locations, do not add anything to mapsettings.cfg (no address, favorite, home location, nothing). And Google for the favorite --> POI conversion procedure...

So now I can use the v9.450 nc with MB on my go910 with CF instead of HDD, too. I get about 25MB of free memory while using the current full Europe map (during navigation, jukebox, etc).
Getting rid of mapsettings.cfg (and using POIs instead) may be a good idea in general, given that POIs are preserved across map updates, with no issues at all.

07-14-2012, 13:26	#3736 (permalink)
dsa8310 No Life Poster Join Date: Feb 2009 Posts: 2,563 Member: 973199 Status: Offline Thanks: 204 Thanked 1,591 Times in 775 Posts	Link to dsa-14July2012.zip Link to dsa-14July2012.zip: dsa-14July2012.zip Here's a quick release, with a real v9(.026) swap enabled kernel to be used by MB. I have also increased the RSS parameter to 26 instead of 23 in skins.sh . The August release will deal with K50 & MB, both enabled, with the following rule: both K50 & MB on a v9 or v8 cab means a v9 MB kernel.

07-14-2012, 23:24	#3744 (permalink)
dsa8310 No Life Poster Join Date: Feb 2009 Posts: 2,563 Member: 973199 Status: Offline Thanks: 204 Thanked 1,591 Times in 775 Posts	Link to dsa-15July2012.zip Link to dsa-15July2012.zip: dsa-15July2012.zip New: a good v9.170 swap enabled kernel stands as the v9 MB. It's zImage.734578. The rest, related to simultaneous K50 & MB, in August.

07-23-2012, 18:25	#3748 (permalink)
dsa8310 No Life Poster Join Date: Feb 2009 Posts: 2,563 Member: 973199 Status: Offline Thanks: 204 Thanked 1,591 Times in 775 Posts	Link to dsa-23July2012.zip Link to dsa-23July2012.zip: dsa-23July2012.zip New: both MB & K50 could be selected simultaneously to get the MB enabled v9 kernel (regardless of NC version). The combination is useful to native x50 devices installing a v8 NC (like the truck NC) and wishing MB support beside a v9 kernel. Just MB means a swap enabled kernel of appropriate version (v8, v89 or v9) according to NC's version (between v8.500 and v9.000 it's v89). Just K50 means the v9 kernel taken from NC v9.205 (no swap). We are done, aren't we?

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
thread	Thread Starter	Forum	Replies	Last Post
TomTom v8 Firmware and Maps	BuMobiles	GPS devices , Navigators & Maps	5948	03-31-2013 10:47
TomTom v7 Firmware and Maps	BuMobiles	GPS devices , Navigators & Maps	3479	03-05-2013 21:55
how to install tomtom V6 software and maps on NAVMAN F20	sniper007	GPS devices , Navigators & Maps	4	11-06-2012 17:58
TomTom v6-7 and Route 66 v6 Firmware and Maps	BuMobiles	GPS devices , Navigators & Maps	4687	05-25-2012 15:52

07-14-2012, 13:41	#3738 (permalink)
dsa8310 No Life Poster Join Date: Feb 2009 Posts: 2,563 Member: 973199 Status: Offline Thanks: 204 Thanked 1,591 Times in 775 Posts	You want to ruin my TT setup ... ~ # uname -a Linux TomTom GO 910 2.6.13-tt842337 #1 Tue Jan 31 10:21:35 CET 2012 armv4tl unknown There is no such thing as a 2.6.23 v9 kernel, even the processor type is different, judging from the different toolchain. Just 2.6.13. 2.6.23 it's actually a v10 kernel, thank you very much, but no thank you... But again, their v9.026 kernel source seems good enough for the v9 MB.

07-14-2012, 13:51	#3739 (permalink)
dsa8310 No Life Poster Join Date: Feb 2009 Posts: 2,563 Member: 973199 Status: Offline Thanks: 204 Thanked 1,591 Times in 775 Posts	Oops... the so called v9 MB kernel has disabled my on/off button (on go910). So it's not that good after all. Maybe dsa-30June should be still used instead.

07-14-2012, 14:03	#3740 (permalink)
dsa8310 No Life Poster Join Date: Feb 2009 Posts: 2,563 Member: 973199 Status: Offline Thanks: 204 Thanked 1,591 Times in 775 Posts	We could choose a lower kernel for MB. But I really don't have time to do it now... Use dsa-30June to alleviate the on/off button issue.

07-14-2012, 22:27	#3742 (permalink)
dsa8310 No Life Poster Join Date: Feb 2009 Posts: 2,563 Member: 973199 Status: Offline Thanks: 204 Thanked 1,591 Times in 775 Posts	TT has shuffled its GPL page beyond recognition... Do NOT use dsa-14July, it contains a random v9 MB kernel Use dsa-30June for now. However, I've got the correct files (from their names, the links are wrong) and I'm going to release shortly the good v9 kernel(s).

07-15-2012, 23:30	#3745 (permalink)
keessie74 Freak Poster Join Date: Oct 2010 Location: The Netherlands Posts: 133 Member: 1431396 Status: Offline Thanks: 60 Thanked 18 Times in 10 Posts	Thanks. That's a kernel with automatic power on when you put the device on the cradle. I played with that version before.

07-16-2012, 00:28	#3746 (permalink)
dsa8310 No Life Poster Join Date: Feb 2009 Posts: 2,563 Member: 973199 Status: Offline Thanks: 204 Thanked 1,591 Times in 775 Posts	Yes, I'd say we nailed it this time! (even the sound volume is better (normal!), beside about 25MB of reported free memory during navigation & jukebox, on my go910) I think I will promote the v9.170 kernel as K50 too (without swapping). The MB & K50 is just a detail that would permit real x50 devices to use the v9 MB kernel while installing a v8 (truck) NC. But it's not that urgent, after all real x50 devices have got 64MB of RAM. Although my 64MB go910 seems more responsive with that much free RAM ?!

07-16-2012, 21:55	#3747 (permalink)
keessie74 Freak Poster Join Date: Oct 2010 Location: The Netherlands Posts: 133 Member: 1431396 Status: Offline Thanks: 60 Thanked 18 Times in 10 Posts	I have a real x50 device. I will do some tests as soon as new DSA will be ready.

07-23-2012, 18:30	#3749 (permalink)
dsa8310 No Life Poster Join Date: Feb 2009 Posts: 2,563 Member: 973199 Status: Offline Thanks: 204 Thanked 1,591 Times in 775 Posts	From my part, I wish TT would release the source of their v9.205 kernel (#547200). It's the only kernel working well on my go910 with CF card & the current full Europe map...

07-26-2012, 13:13	#3750 (permalink)
dsa8310 No Life Poster Join Date: Feb 2009 Posts: 2,563 Member: 973199 Status: Offline Thanks: 204 Thanked 1,591 Times in 775 Posts	I have found a solution to the map issue: it seems that all favorites (including home location) should be converted to POIs - while in Home/Operate my Go - and then file mapsettings.cfg (from inside the map folder) should be deleted; another Home/Operate my Go will recreate the mapsettings.cfg file properly (hollow). In the future, use POIs to navigate to preferred locations, do not add anything to mapsettings.cfg (no address, favorite, home location, nothing). And Google for the favorite --> POI conversion procedure... So now I can use the v9.450 nc with MB on my go910 with CF instead of HDD, too. I get about 25MB of free memory while using the current full Europe map (during navigation, jukebox, etc). Getting rid of mapsettings.cfg (and using POIs instead) may be a good idea in general, given that POIs are preserved across map updates, with no issues at all.