Re: ANNOUNCE: Diablo-Turbo first beta available
 

I'm running from flash. I don't quite understand how to convert my filesystem to ext3. Can you direct me to a walk through?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Don't worry about that then, that's only for systems running from mmc.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

What if I am running from mmc? I always think flash media = flash.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

mmc (sd/minisd) has a controller chip->it abstracts the underlying flash and emulates a disk->you can use any filesystem (fat, ntfs, ext3, whatever)
flash->barebones flash->you have to use a special filesystem (jffs2 here)
Very different

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Boot to the real flash (not mmc) and run these as root, just change the device to match your ext2 partition.
Then edit /mnt/initfs/bootmenu.conf so it boots as ext3 and reboot.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

bluez-utils_3.28-0osso7 breaks the depedency of bluez-utils-test (bluez-utils_3.28-0osso6), which in turn breaks minigpsd. That leaves one of my favorite mapping programs, Maemo Mapper, without a gps to use.

Could someone rebuild bluez-utils-test for the new bluez-utils?

TIA,
- John

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Hi I would like to test this update, but the whole topic is to big to be read and understood without confusion.

Can somebody write an overview on what is the current status in term of stability and what follows?

For instance the list of present issues?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Already uploaded to the garage page.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

It installed fine and minigpsd is now happy again.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

That's if you are using bootmenu, but bootmenu is not needed to boot from mmc, you can setup the device to boot first from mmc using flasher (from your PC "flasher-3.0 --set-root-device mmc") or cal-tool (from your device "chroot /mnt/initfs cal-tool -R mmc")

Re: ANNOUNCE: Diablo-Turbo first beta available
 

The first post contains the current status and known issues. I update it from time to time as issues appear or are resolved, or new updates are published.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Thanks auouymous for the fsck/tune2fs code. It worked and my update is complete, however I am still struggling with editing the boot menu. I am using bootmenu (I select the partition on boot), however my inexperience/confusion has created another roadblock. I do not have a bootmenu.conf in mnt/initfs but I do have a bootmenu.sh. I tried editing the bootmenu.conf.n8x0.example and follow the steps here but it wouldn't let me save in the initfs_flasher folder. Am I going about this all wrong? Is there a simpler/better way to edit the bootmenu?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Oops, edit /mnt/initfs/bootmenu.sh and reboot.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

It appears to me that you tried to save the bootmenu.conf in the /mnt/initfs folder. Instead, you need to download the complete fanoush flasher package and put it in your home directory. Did you see the links in my earlier post?

Are we talking about a similar boot menu as shown on these images 1 or 2?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Yes, that bootmenu. Once installed you can just edit /mnt/initfs/bootmenu.sh instead of reflashing.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Getting an incompatible file error when i attempt to install.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

You have to install it with dpkg, not App. Manager

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Yes, that's the boot menu I use. So how do I edit it without reflashing? That's where I am having my trouble. What program or command should I use and how can I save/overwrite it?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

The initfs partition is mounted read-only, you have to mount it rw to change anything:
"mount -o remount,rw /mnt/initfs" and when you are done "mount -o remount,ro /mnt/initfs"

Re: ANNOUNCE: Diablo-Turbo first beta available
 

shut down problem fixed. Thanks folks.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

When will this make the community SSU for all us novices? Im still at 5.2010.33-1
Pressing update is so much easier than all the steps on page 1

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Success! Thank you all for your help. This was my first time posting and I'm impressed with the knowledge and activity of this community. Thanks!

Re: ANNOUNCE: Diablo-Turbo first beta available
 

OK, stupid questions but I can't figure them out before trying to install ...

Do you need to install Diablo/Community SSU before (or, for that matter, after) installing Diablo Turbo?

If you're running your system off an SD Card (dual booting), can you just install Diablo Turbo directly into the SD-based OS?

If you have to install it on the internal flash memory (i.e., not on a card), or you do install it there even if you don't have to, does it positively impact the N8x0's performance when you run the SD-based OS?

Thanks!

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Per the first post in this thread....Install the SSU before DIablo Turbo (Assuming, due to the order of the install instructions at the end of the post...) ;)


YES, My N800 has a stock Diablo install on the internal flash, with the Community SSU/Diablo Turbo on the SD Boot. (only time I boot to flash is to clone the Internal card ->External card for backups)

Hmmmm don't know this one :o

Good luck!

Sno

Re: ANNOUNCE: Diablo-Turbo first beta available
 

The kernel is shared between both systems

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Hiya Mac.

Any clue yet as to why Xbindkeys doesn't seem to take like it used to before Diablo Turbo?

I have this set up for the file /home/user/.xbindkeysrc

"/usr/bin/prevw"
F7

In that prevw file is this...
xte 'keydown Control_L' 'key r' 'keyup Control_L'

This produces a CTRL-r signal to be used with Dial Central. Basically it's a hardware key to refresh for all incoming text messages.

It barely works like before.

My hardware keys responded 100% of the time before installing Diablo Turbo.

Now, I seriously will have to press the hardware key like 10 times before it will do anything.

I'm actually thinking of reflashing my tablet tomorrow because of this.

Any ideas on why the change in behavior?

Oh, and without running Xbindkeys, the hardware keys work 100% of the time in such things as Tear and Xterm.

Thank you!

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I've been unable to reproduce that problem, and the fact that tear and xterm show no problem means that the keys are working, and suggest that the problem is with xbindkeys.
What xbindkeys release are you using? A while ago I uploaded xbindkeys to extras-devel as a support package for snx, are you using the extras-devel package or is it from somewhere else?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I have found the problem with boingomobile, it makes improper use of the session bus.
I have uploaded new dbus packages with the fix. You only need to update if you need boingomobile.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

This is the one I'm using Mac.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Please, delete your version and try "apt-get install xbindkeys" first (with extras-devel enabled), restart xbindkeys and check if the problem is still there.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Okay. I will do this later tonight.

Thank you. :)

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Sorry. I have no clue what any of this means.


[1|root@Nokia-N800-43-7|~]apt-get install xbindkeys
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run `apt-get -f install' to correct these:
The following packages have unmet dependencies:
osso-software-version-rx34: Depends: kernel-diablo-flasher (= 2.6.21-200842maemo1) but 2.6.21-200835maemo1rotation is to be installed
Depends: xserver-xomap (= 1:1.3.99.0~git20070321-0osso20083801) but 1:1.3.99.0~git20070321-0osso20083101rotation is to be installed
qemu-kvm: Depends: libuuid1 but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Well, all I can say is that I also use Xbindkeys when playng ADOM.
http://talk.maemo.org/showthread.php?t=70484

All the keys work to perfection.

It's like Tear and Dial Central aren't "focused" on the screen like they used to be before DT or something.

I'm not sure how to explain it any better.

I'm positive that Xbindkeys executes my scripts every time I press a hardware key, it's just that my scripts only work now either every time or up to 1 in 10 tries.

I wish that I knew what was wrong.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

top fuel rules

Re: ANNOUNCE: Diablo-Turbo first beta available
 

:Facepalm:
You have a mess of a system. You need to fix it first. Let's guide you step by step:
- enable the community ssu repository and the sdk repository
- uninstall kernel-dt-sd ("dpkg -r kernel-dt-sd", no need to reboot), to allow it to make a correct backup later when reinstalling
- install osso-software-version-rx34-unlocked asking to fix any broken package ("apt-get -f install osso-software-version-rx34-unlocked", no need to reboot). This should upgrade your system to community ssu and fix the mess.
- install xbindkeys ("apt-get install xbindkeys")
- install kernel-dt-sd ("dpkg -i kernel-dt-sd_2.6.21-3_all.deb")
- reboot
Then test your xbindkeys script

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I can do all of that except I don't understand how to enable the SDK repository.

Google made me confused on this.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Go to http://repository.maemo.org and near the end of the page you'll find it with a one-click install link.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Is this just temporarily down or is it gone for good?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Oh, well. The install file seems gone :(, but the repo is there, add it by hand:
http://repository.maemo.org diablo/sdk free non-free

Re: ANNOUNCE: Diablo-Turbo first beta available
 

http://img228.imageshack.us/img228/5046/57823039.png

Eh?

Is this correct? :)