maemo.org - Talk
Page 8 of 16 « First 67 8 910 Last »
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   OS2008 / Maemo 4 / Chinook - Diablo (https://talk.maemo.org/forumdisplay.php?f=29)
-   -   ANNOUNCE: Diablo-Turbo first beta available (https://talk.maemo.org/showthread.php?t=69740)

scy 2011-03-23 07:38
Re: ANNOUNCE: Diablo-Turbo first beta available
 
First of all, thanks for this great work!

I successfully installed the first update. The N810 is - subjectively definitely - responding quicker having diablo turbo installed.

After trying to install the second updates, I ran into problems. First, the kernel install reports an error message "short read buffer_copy" and then I realized that everytime after I installed the kernel fsck.ext2 reports errors.

Can this be caused by the install? Kindly let me know your ideas how to solve this issue.

Here are the details:
(1) Installing diablo turbo
The error message is:
Reading database...
Preparing to replace kernel-dt-sd 2.6.21-2 (using kernel-dt-sd_2.6.21-3_all.deb)...
Unpacking replacement...
dpkg-deb (subprocess): short read in buffer_copy (failed to write to pipe in copy)
dpkg-deb: supbrocess paste returned exit status 2
dpkg: error processing kernel-dt-sd_2.6.21-3_all.deb (--install):
short read in buffer_copy (backend dpkg-deb during `./boot/zImage-sd-preempt-256Hz')
Installing new kernel modules in initfs...
Flashing new kernel image...
Image(s) successfully flashed
Kernel image flashed
Please reboot
Errors were encountered while processing:
kernel-dt-sd_2.6.21-3_all.deb

-> rebooting works, uname still reports kernel 19 Feb

(2) fsck internal partition

fsck.ext2 /dev/mmcblk0p2
Pass 1
Inode 18792, i_block is 64, should be 8
(...)
Pass 5
Block Bitmap differ (65368--65374)
Free blocks count is wrong in group #1 (160, counted=167)
Free blocks count is wrong (104468, counted=104475)

I corrected this, tried to install the kernel again. But groundhog day returned:

18793, 65369--65375, 159-166, 104466, 104473
18795, 41629--41635, 157-164, 104462, 104469
18796, 65378--65384, 156-163, 104460, 104467

I checked badblocks on the partition with no avail.

Comments? Is there a connection with the diablo turbo install? How best to proceed?

maacruz 2011-03-23 07:44
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by edt (Post 973585)
> What is the effect of that patch? Links?
> if it is for current kernels, I doubt it can be ported, at least with a > reasonable amount of work.

I allows the ondemand policy to use intermediate frequencies more often instead of just the highest and lowest.
It looks quite interesting :)
Quote:
Does this have all the patches (nokia's too) for n8x0 included. If not where are the patches from nokia? I'll see if the ondemand stuff can be backported.
The diablo kernel comes not from mainline but form the omap branch, it contains all the patches from Nokia.
You can download the tar.gz from the maemo repositories: http://repository.maemo.org/pool/dia...source-diablo/
All my patches are for this kernel
Welcome aboard :)
Other projects I'm interested in are:
- Porting the kdbus patch (I think I'm near completion)
- Improving ramzswap: see if it possible to write a defragmenter, and try to make the backing swap useful by making the swap device size independent from the backing swap device.

maacruz 2011-03-23 08:11
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by scy (Post 973685)
First of all, thanks for this great work!

I successfully installed the first update. The N810 is - subjectively definitely - responding quicker having diablo turbo installed.

After trying to install the second updates, I ran into problems. First, the kernel install reports an error message "short read buffer_copy" and then I realized that everytime after I installed the kernel fsck.ext2 reports errors.

Can this be caused by the install? Kindly let me know your ideas how to solve this issue.
You simply have a damaged filesystem for whatever reason (sure you haven't a full filesystem?). DT has that shutdown issue which causes the filesystem not to be umounted when it happens, and ext2 doesn't act kindly if it is not unmounted, having a tendency to accumulate errors.
At my firsts attemps at boot from mmc, much before DT, I also ran into troubles with ext2 quite often.
The best sollution is to move to ext3, as the journal protects you from the usual problems that arise if the ext2 filesystem is not properly umounted.
To solve your problem now, boot into flash and "fsck -p -f" the ext2 partition. Then I suggest you to convert it to ext3 (Diablo incorrectly mounts ext3 as ext2 but DT fixes that)

maacruz 2011-03-23 08:13
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by Straycat (Post 973264)
I have installed all the packages the old and the upgraded ones.

With the new bluez-utils package I can pair with my BH-214 headset and it plays for 2-3 seconds aprox. Then it suddenly stops playing. Pairing is still established but no sound trough headset.

I'm still testing.
Please keep me updated, I do not have a BT headset to be able to test this.

maacruz 2011-03-23 08:23
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by luca (Post 973517)
Ok, but the "Sat Feb 19" one cannot be from the community update (I checked the repository and that was in august 2010), according to the date it must be one of the diablo turbo one.
The only diablo turbo kernel package I installed is the "broken" one, and you said that, due to a bug, it didn't really install the kernel.
I'm confused now, (more than usual ;))
You probably flashed a DT test zImage before installing the kernel-dt-sd package.
I'm actually surprised you haven't run into any issue because of kernel modules.

danramos 2011-03-23 09:13
Re: ANNOUNCE: Diablo-Turbo first beta available
 
I went ahead and followed your directions to install everything including update2 on my Nokia N800. It took maybe several minutes between downloading and ssh'ing into my tablet to issue the dpkg commands, reboot and VOILA! Easy peasy!

I have to say that it *DOES* breath a LOT more life into this device. One of the most OBNOXIOUS damned things about the N800 over all the years I've had it was the damned blocking and the reboots from unresponsiveness. But now--it doesn't seem to happen anymore. It's FAR more responsive and SEEMS to work a little more smoothly, if not actually faster or more efficiently. It's certainly made it feel "right" and useful again after rarely using my N800 anymore now that I spoiled myself on the fluidity of Android.

I'm REALLY glad to see a few real and tangible updates coming to the OS at a low-level (where it counts! Like in the kernel and bluez stack and so on).

THANK YOU!!! :)

danramos 2011-03-24 01:26
Re: ANNOUNCE: Diablo-Turbo first beta available
 
OK, I'm even more impressed that I was able to even play unconverted avi files and that the camera apps don't crash the heck out of my N800 like they have been for years.

If you know me and have followed my conversations, you know it's not impossible for me to hand out compliments about Maemo but it's been rare. It's been increasingly rarer as time goes on and Maemo becomes more stale and rotten with time and with the closed-source portions preventing much from being done. I went through the trouble of pointing this out to put it into perspective when I tell you that I'm impressed and you've done a splendid job, maacruz! I can't thank you enough for making this N800 interesting and useful to me again.

Straycat 2011-03-24 13:03
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by maacruz (Post 973709)
Please keep me updated, I do not have a BT headset to be able to test this.
Well... now I'm hearing Rory Gallagher trough the bluetooth headset without any trouble so...

Maybe some reboot helped to solve the initial problem. I'll keep you in touch with this.

Now another question, did you know how can I enable the a2dp profile on the device??

Thanks in advance!

luca 2011-03-24 17:49
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by maacruz (Post 973713)
You probably flashed a DT test zImage before installing the kernel-dt-sd package.
No, I didn't. I just installed these packages:

dbus_1.0.2-0osso15_armel.deb
libdbus-1-3_1.0.2-0osso15.armel.deb
dbus-1-utils_1.0.2-0osso15_armel.deb
libgconf2-6_2.16.9-1osso15_armel.deb
dt-init-scripts_1.0.1-2_all.deb
mini-rc_0.2.11-1_all.deb
gconf2_2.16.0-1osso15_armel.deb
ramzswap-dt_0.5.5-4_armel.deb
kernel-dt-sd_2.6.21-2_all.deb
sysvinit_2.85-22.osso15-dt1_armel.deb


Quote:
Originally Posted by maacruz (Post 973713)
I'm actually surprised you haven't run into any issue because of kernel modules.
Well, apparently there's no problem with that, there's a handful of modules loaded: ramzswap, xvmalloc, g_file_storage, nfs, lockd, sunrpc, cx3110x, umac, omap_rng, rng_core. I'm really suprised about the nfs modules (they come from the kernel-diablo-modules-extra package that I didn't even remember I had installed).
Anyway, I compared with cmp the modules in the package (in /usr/share/Diablo-Turbo/initfs/modules/) with the modules in initfs and they are the same (save for pc2400m.ko, which isn't present in initfs).

The real problem is, what do I do now? Install the latest package as is or do I have some cleanup to do?

maacruz 2011-03-24 19:44
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by Straycat (Post 974652)
Now another question, did you know how can I enable the a2dp profile on the device??
http://talk.maemo.org/showthread.php?t=13468

maacruz 2011-03-24 19:51
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by luca (Post 974899)
The real problem is, what do I do now? Install the latest package as is or do I have some cleanup to do?
Install the latest package, no cleanup is needed.

auouymous 2011-03-25 04:16
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Do all of you who get the shutdown problem have the bootmenu installed? I never had it until reflashing with the bootmenu and it happens every time from both flash and mmc.

maacruz 2011-03-25 07:23
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by auouymous (Post 975292)
Do all of you who get the shutdown problem have the bootmenu installed? I never had it until reflashing with the bootmenu and it happens every time from both flash and mmc.
Do you have the latest kernel-dt-sd and mini-rc packages installed?
If in doubt, install them again.

z2n 2011-03-25 16:43
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Yet another voice in the chorus of "thanks".

I installed Diablo-Turbo on my N810-WiMax about 3 weeks ago. I first upgraded to the community SSU (to both the internal flash and the SD card), then I installed the Diablo-Turbo packages to just the SD card. The installation was easy and the machine was distinctly faster.

The upgrade yesterday was similarly easy and productive.

I boot from flash (using Fanoush's bootmenu), and here are some of the apps which people may have concerns about conflicting with the Diablo-Turbo packages. These all work correctly for me:

advanced-backlight
advanced-power
advanced-power-monitor
dbus-scripts-settings
dbus-switchboard
large-statusbar-clock
slidelock

luca 2011-03-25 18:42
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by maacruz (Post 975012)
Install the latest package, no cleanup is needed.
Done, the update worked.

auouymous 2011-03-25 20:42
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by maacruz (Post 975342)
Do you have the latest kernel-dt-sd and mini-rc packages installed? If in doubt, install them again.
I had kernel-2 (not the zImage that was later released) and packages for it installed without the bootmenu, worked fine. Flashed with bootmenu, spent a couple days setting it up while using CSSU, downloaded the four new DT files (deleting the old first) and ever since then it won't shutdown.

So its gotta be bootmenu+DT, the DT files released on the 18th or the radiation I'm receiving in America from Japan. ;) Do you still have a copy of the previous mini-rc that I could try? Is it safe to downgrade from kernel-3 to kernel-2, was it only kernel-1 that had packaging problems?

EDIT: And yes, I did reinstall kernel and mini-rc even though dpkg -l showed them installed with correct version and it had no effect.

scy 2011-03-26 13:39
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by maacruz (Post 973707)
You simply have a damaged filesystem for whatever reason (sure you haven't a full filesystem?). DT has that shutdown issue which causes the filesystem not to be umounted when it happens, and ext2 doesn't act kindly if it is not unmounted, having a tendency to accumulate errors.
At my firsts attemps at boot from mmc, much before DT, I also ran into troubles with ext2 quite often.
The best sollution is to move to ext3, as the journal protects you from the usual problems that arise if the ext2 filesystem is not properly umounted.
To solve your problem now, boot into flash and "fsck -p -f" the ext2 partition. Then I suggest you to convert it to ext3 (Diablo incorrectly mounts ext3 as ext2 but DT fixes that)
Thanks. In the meantime, I successfully converted the partition into ext3 using your steps and also added an additional layer of work as described here. The inode errors, however, are still coming back.

I also discovered the reason for the "short read in buffer_copy" errors: the deb file, which I was trying to install with dpkg, was not download fully. After i wget the file again, the "short read" error disappeared.

However, I still could not install the new kernel. A downgrade to kernel 1 worked. An upgrade not:

dpkg -i kernel kernel-dt-sd_2.6.21-3_all.deb
Reading database...
Preparing to replace kernel-dt-sd 2.6.21-1 (using kernel-dt-sd_2.6.21-3_all.deb)...
Unpacking replacement...
Setting up kernel kernel-dt-sd (2.6.21-1)
Installing new kernel modules in initfs...
Flashing new kernel image...
Image(s) successfully flashed
Kernel image flashed
Please reboot

Any hints?

maacruz 2011-03-26 15:24
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by auouymous (Post 975778)
I had kernel-2 (not the zImage that was later released) and packages for it installed without the bootmenu, worked fine. Flashed with bootmenu, spent a couple days setting it up while using CSSU, downloaded the four new DT files (deleting the old first) and ever since then it won't shutdown.

So its gotta be bootmenu+DT, the DT files released on the 18th or the radiation I'm receiving in America from Japan. ;) Do you still have a copy of the previous mini-rc that I could try? Is it safe to downgrade from kernel-3 to kernel-2, was it only kernel-1 that had packaging problems?

EDIT: And yes, I did reinstall kernel and mini-rc even though dpkg -l showed them installed with correct version and it had no effect.
Opps, there is actually a bug in the mini-rc workaround.
I have uploaded a new mini-rc package. Please, try it.
https://garage.maemo.org/frs/downloa...2.11-3_all.deb

maacruz 2011-03-26 15:28
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by scy (Post 976098)
However, I still could not install the new kernel. A downgrade to kernel 1 worked. An upgrade not:

dpkg -i kernel kernel-dt-sd_2.6.21-3_all.deb
Reading database...
Preparing to replace kernel-dt-sd 2.6.21-1 (using kernel-dt-sd_2.6.21-3_all.deb)...
Unpacking replacement...
Setting up kernel kernel-dt-sd (2.6.21-1)
Installing new kernel modules in initfs...
Flashing new kernel image...
Image(s) successfully flashed
Kernel image flashed
Please reboot

Any hints?
I feel confused:
dpkg -i kernel kernel-dt-sd_2.6.21-3_all.deb ->you are upgrading to kernel 3
but...
Setting up kernel kernel-dt-sd (2.6.21-1) shows kernel 1 installed?

scy 2011-03-26 15:54
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Thanks. Now I successfully installed kernel 3!

The naming errors where due to the fact that I used wget and only modified the filename after I had download the kernel 1 file:

i.e.

first I downloaded https : // garage. maemo. org / frs / download.php / 9327 / kernel-dt-sd_2.6.21-1_all.deb
(ID 9327)

then I downloaded https : // garage. maemo. org / frs / download.php / 9327 / kernel-dt-sd_2.6.21-3_all.deb
(ID 9327)

instead of https : // garage. maemo. org / frs / download.php / 9431 / kernel-dt-sd_2.6.21-3_all.deb
(CORRECT ID 9431)

;-)

I will have to check now if the other files installed really are all up-to-date.

Straycat 2011-03-27 11:33
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Sorry, I've been playing around the values for '/sys/power/op_active' (now 0) and '/sys/power/op_dsp' (now 0 too).

Now CPU Policy under advanced-power shows my N800 running always at 400MHz so there is not CPU scale.

Anyone to show me the appropiate values? Or it is better to reinstall any dt package?

Thanks in advance.

auouymous 2011-03-27 12:22
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by Straycat (Post 976518)
Sorry, I've been playing around the values for '/sys/power/op_active' (now 0) and '/sys/power/op_dsp' (now 0 too).

Now CPU Policy under advanced-power shows my N800 running always at 400MHz so there is not CPU scale.
op_dsp = 0-3 with 0 locking cpu at 400 and 3 at 165, but only when DSP is enabled. There is a /etc/kernel-tunables file where you can set the value for this at boot and I believe it contains a comment with the frequency for each value.

I don't think you are suppose to modify op_active, the governor will automatically change it. Is adv-power set to performance (always 400) or ondemand (dynamic)?

@ maacruz, I might not be having any shutdown problems. The screen does turn off (with minirc 2 and 3) but I thought it only required a short press to power the device back up but is now requiring a long press. :confused:

Straycat 2011-03-27 12:46
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by auouymous (Post 976540)
...

I don't think you are suppose to modify op_active, the governor will automatically change it. Is adv-power set to performance (always 400) or ondemand (dynamic)?...
Thanks!

I have set adv-power to 'on demand'.

And I think you are right, auouymous, about 'op_active' is changed bye the governor automatically.

maacruz 2011-03-27 17:31
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by auouymous (Post 976540)
@ maacruz, I might not be having any shutdown problems. The screen does turn off (with minirc 2 and 3) but I thought it only required a short press to power the device back up but is now requiring a long press. :confused:
It always has required a long press for me: Device is off, press the button, led starts glowing, keep pressing, led reach maximum, device turns on.

danramos 2011-03-28 08:29
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by maacruz (Post 976699)
It always has required a long press for me: Device is off, press the button, led starts glowing, keep pressing, led reach maximum, device turns on.
Same here--always been the same way for me on both of the N800's I've owned.

maacruz 2011-03-28 18:10
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by scy (Post 976129)
Thanks. Now I successfully installed kernel 3!

The naming errors where due to the fact that I used wget and only modified the filename after I had download the kernel 1 file:

i.e.

first I downloaded https : // garage. maemo. org / frs / download.php / 9327 / kernel-dt-sd_2.6.21-1_all.deb
(ID 9327)

then I downloaded https : // garage. maemo. org / frs / download.php / 9327 / kernel-dt-sd_2.6.21-3_all.deb
(ID 9327)

instead of https : // garage. maemo. org / frs / download.php / 9431 / kernel-dt-sd_2.6.21-3_all.deb
(CORRECT ID 9431)

;-)

I will have to check now if the other files installed really are all up-to-date.
Do you still have filesystem problems or are they finally fixed?

heavyt 2011-03-28 20:47
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Having a problem installing Boingomobile after Diablo-Turbo was installed. Before I had Diablo-Turbo on my unit Boingomobile ran without a problem, but now when I install Boingomobile (took it off while installing DT) and then do a reboot I am not able to see mmc2 or mmc1 in the file manager and some of my icons are gone (Large clock, Personal Menu). Plus the desktop seems to do a couple of resets after the end of a reboot sequence. When I remove Boingomobile and reboot all returns to normal.There could be more problems..still looking.

Could someone give Boingomobile app a try, you do not need to open an account just install the app and reboot, thank you.

Jimcz 2011-03-28 20:50
Re: ANNOUNCE: Diablo-Turbo first beta available
 
I updated toTURBO and I notice a great improvement. However, I was wondering if someone could help. I'm not a noob, but I am very inexperienced. After installing Turbo, I noticed the "os2008 commuunity SSU update (unlocked)" was in the application manager updater. I was told I was unable to update.

Then I tried apt-get upgrade and received the following:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
poppler-utils x11-common
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
2 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up gconf2 (2.16.0-1osso15) ...
chmod: /var/lib/gconf/apps/modest/server_accounts/GmailID_store/%gconf.xml: Input/output error
dpkg: error processing gconf2 (--configure):
subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of osso-software-version-rx34-unlocked:
osso-software-version-rx34-unlocked depends on gconf2 (>= 2.16.0-1osso14); however:
Package gconf2 is not configured yet.
dpkg: error processing osso-software-version-rx34-unlocked (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
gconf2
osso-software-version-rx34-unlocked
E: Sub-process /usr/bin/dpkg returned an error code (1)


It looks like gconf2 may be my problem? Was it not installed correctly? How do I configure gconf2?
I tried redownloading and installing gconf2 and got the following:
dpkg -i gconf2_2.16.0-1osso15_armel.deb
(Reading database ... 22003 files and directories currently installed.)
Preparing to replace gconf2 2.16.0-1osso15 (using gconf2_2.16.0-1osso15_armel.deb) ...
Unpacking replacement gconf2 ...
Setting up gconf2 (2.16.0-1osso15) ...
chmod: /var/lib/gconf/apps/modest/server_accounts/GmailID_store/%gconf.xml: Input/output error
dpkg: error processing gconf2 (--install):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
gconf2


I tried a few other things with no luck. How do I fix this so everything is working as intended?

maacruz 2011-03-28 21:25
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by Jimcz (Post 977341)
It looks like gconf2 may be my problem? Was it not installed correctly? How do I configure gconf2?
I tried redownloading and installing gconf2 and got the following:
dpkg -i gconf2_2.16.0-1osso15_armel.deb
(Reading database ... 22003 files and directories currently installed.)
Preparing to replace gconf2 2.16.0-1osso15 (using gconf2_2.16.0-1osso15_armel.deb) ...
Unpacking replacement gconf2 ...
Setting up gconf2 (2.16.0-1osso15) ...
chmod: /var/lib/gconf/apps/modest/server_accounts/GmailID_store/%gconf.xml: Input/output error
dpkg: error processing gconf2 (--install):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
gconf2
It seems like the file /var/lib/gconf/apps/modest/server_accounts/gmailID_store/%gconf.xml is damaged and that causes gconf2 to fail.
Try deleting that file (it contains your configured email accounts in modest, you may try to backup it first)

EDIT: if you are on ext2, fsck your filesystem instead as scy suggests and move to ext3

auouymous 2011-03-28 21:27
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by heavyt (Post 977338)
Having a problem installing Boingomobile after Diablo-Turbo was installed. Before I had Diablo-Turbo on my unit Boingomobile ran without a problem, but now when I install Boingomobile (took it off while installing DT) and then do a reboot I am not able to see mmc2 or mmc1 in the file manager and some of my icons are gone (Large clock, Personal Menu). Plus the desktop seems to do a couple of resets after the end of a reboot sequence. When I remove Boingomobile and reboot all returns to normal.
Confirmed. Nothing happened after rebooting but opening file manager showed no mmc cards and then hildon-desktop crashed and loads its failsafe statusbar set. Everything returns to normal when uninstalling boingomobile.

scy 2011-03-28 21:55
Re: ANNOUNCE: Diablo-Turbo first beta available
 
@maacruz: Thanks for asking. Installation of kernel version 3 is successfully completed with all accompanying files. Uname reports a 13 march kernel.

The rootfs still gets mounted as ext2 though. Is there some additional magic I have to do for this partition to get recognized as ext3? Do I need to edit fstab?

Code:
/etc $ cat /etc/fstab
rootfs  /              rootfs  defaults,errors=remount-ro,noatime      0 0
/dev/mmcblk0p1  /media/mmc1 vfat rw,noauto,nodev,noexec,nosuid,utf8,uid=29999 0 0
So the filesystem errors are also still there. I regularly boot into flash and fsck them out.

@Jimcz: I had input/output errors which had gone away after fsck my ext2 filesystem.

maacruz 2011-03-28 21:56
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by auouymous (Post 977360)
Confirmed. Nothing happened after rebooting but opening file manager showed no mmc cards and then hildon-desktop crashed and loads its failsafe statusbar set. Everything returns to normal when uninstalling boingomobile.
Sigh... there it goes my 12 days uptime
Confirmed, no mmc cards. hildon-desktop didn't crash for me.
My hildon-desktop package version is 1:2.0.18-1fix1, seems probably a patched version I built around august, from cssu sources.

maacruz 2011-03-28 22:07
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by scy (Post 977377)
@maacruz: Thanks for asking. Installation of kernel version 3 is successfully completed with all accompanying files. Uname reports a 13 march kernel.

The rootfs still gets mounted as ext2 though. Is there some additional magic I have to do for this partition to get recognized as ext3? Do I need to edit fstab?

Code:
/etc $ cat /etc/fstab
rootfs  /              rootfs  defaults,errors=remount-ro,noatime      0 0
/dev/mmcblk0p1  /media/mmc1 vfat rw,noauto,nodev,noexec,nosuid,utf8,uid=29999 0 0
So the filesystem errors are also still there. I regularly boot into flash and fsck them out.

@Jimcz: I had input/output errors which had gone away after fsck my ext2 filesystem.
It should be mounted as ext3
Look at /mnt/initfs/linuxrc and see if the first line after the comments is
FS_MODULES="mbcache jbd ext3 ext2"

auouymous 2011-03-28 22:52
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by maacruz (Post 977380)
hildon-desktop didn't crash for me.
My hildon-desktop package version is 1:2.0.18-1fix1, seems probably a patched version I built around august, from cssu sources.
I have the same version of hildon-desktop.

Jimcz 2011-03-29 01:30
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by maacruz (Post 977389)
It should be mounted as ext3
Look at /mnt/initfs/linuxrc and see if the first line after the comments is
FS_MODULES="mbcache jbd ext3 ext2"
Maacruz - That is exactly what it says. Do I need to change it?

maacruz 2011-03-29 10:07
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by Jimcz (Post 977473)
Maacruz - That is exactly what it says. Do I need to change it?
No, that is how it must be for ext3 automounting to work.
Have you converted your filesystem to ext3? or are you running from flash?

maacruz 2011-03-29 10:12
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by heavyt (Post 977338)
Having a problem installing Boingomobile after Diablo-Turbo was installed. Before I had Diablo-Turbo on my unit Boingomobile ran without a problem, but now when I install Boingomobile (took it off while installing DT) and then do a reboot I am not able to see mmc2 or mmc1 in the file manager and some of my icons are gone (Large clock, Personal Menu). Plus the desktop seems to do a couple of resets after the end of a reboot sequence. When I remove Boingomobile and reboot all returns to normal.There could be more problems..still looking.

Could someone give Boingomobile app a try, you do not need to open an account just install the app and reboot, thank you.
Do you remember your problems after installing DT a while ago? Now we know the cause

heavyt 2011-03-29 12:11
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by maacruz (Post 977634)
Do you remember your problems after installing DT a while ago? Now we know the cause
Yes I do. A bummer because Boingomobile is needed when I am on the road plus I am paying for the service.
:mad:

maacruz 2011-03-29 13:05
Re: ANNOUNCE: Diablo-Turbo first beta available
 
Quote:
Originally Posted by heavyt (Post 977705)
Yes I do. A bummer because Boingomobile is needed when I am on the road plus I am paying for the service.
:mad:
I'll have a look at it. In the meanwhile, you already know the workaround.

scy 2011-03-29 13:36
Re: ANNOUNCE: Diablo-Turbo first beta available
 
@maacruz: Thanks, solved. The root partition mounts as ext3 now. You pointed me into the right area. linuxrc FS_modules were fine, bootmenu.conf was not. Therein ext2 was set for my root partition.

Thus, I updated these lines in the bootmenu.conf and flashed the menu with fanoush's flasher again:
Code:
MENU_2_MODULES="mbcache jbd ext3"
MENU_2_FSTYPE="ext3"
Link: How to flash boot menu (steps 6-9) and bootmenu.conf example


All times are GMT. The time now is 04:54.
Page 8 of 16 « First 67 8 910 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8