maemo.org - Talk - N900 Mouse cursor appeared on screen and text only squares no fonts, video driver or desktop config?

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

- General (https://talk.maemo.org/forumdisplay.php?f=7)

N900 Mouse cursor appeared on screen and text only squares no fonts, video driver or desktop config?

hello, sorry to bother but i'm in a hurry.

Today i was taking some pictures with Fcam, then the phone shutted down and i had to turn it on.

When it turned on, there is no icons, no wallpaper and there's no fonts, instead i only see squares where fonts should be.

Cant access it with nokia suite, i put it in suite mode (other option goes mass usb device) but nokia does not discover it.

I tried to reflash it, but, flasher dont find a suitable usb device, the driver is correctly installed and i pluged the phone while holding "u" key. Also it appears on windows device manager.

I can only use it as pendrive because is the only way it works.

I can also enter via ssh, since i could find how to enable WiFi. But i dont know what to do next, i can see the whole filesystem but cant tell if something is wrong or blocked, every file permission and owner seems to be ok.

Please,. i need urgent help, i have a meeting in the afternoon, i scheduled yesterday so is not yet in any backup, i lost my contact info. meeting address and etc...

Help, this has to be fixable using command line, but i-m not very good on linux.

Thanks in advance, my job is on the line if i loose the meeting because of this phone.

Just to update, the whole filesystem seems to be locked in read only mode. I cant do anything even as root under terminal, everything says cant write here, cant write there.

Re: N900 No fonts (squares instead), no icons and no wallpaper.

I dont know if it works on N900 but theres folder called .backup in N9. It has contacts and messages backed up and I think Nokia pc suite can read those files.

Re: N900 No fonts (squares instead), no icons and no wallpaper.

All my contacts and everything is backed up, but i dont care to loose anything else, almos t everything is old enough as to be in my memory or reconstructable.
I scheduled this meeting and contact yesterday, that didnt went to any backup and i cant reme,ber anything except the first name of the person i talked to.

There-s no .baclup folder that i can find here.

If i cant bring the phone back to life i cant put more time on it, it started to go bananas some time ago.. Camera-ui closing, ok i reopen it, video recording feezing, ok, take it again.
e-mail giving error entering an infinite open close loop, ok, unistall and kill anything related.

But this is it, is too much, cant have a phone intended only for those who develop for it. Today i was about 1 hour trying to understand how to reflash it, a couple hours searching if there was a fast reset for configs, now i spent another hour or more trying to enter filesystem, using apt, etc...

If this morning i would walk 2km to buy a new android phone (wich i-m considering to buy for some time on) at this moment i would have a working phone and a meeting to go.
Just because i tried to keep this piece of machinery, now i have probably got into trouble with my work, lost a phone, lost a very important new contact ang got p..sed of..

I guess my first Android/Windows phone is going to be here tomorrow and this would be the last time a Linux/dobyyourself device gets in beteen me and my work to make me loose time and a job. (since is not the first and have not been few)

Re: N900 No fonts (squares instead), no icons and no wallpaper.

making fsck had no effect

Re: N900 No fonts (squares instead), no icons and no wallpaper.

damn my N900 died the same way this week. Wondering what's going on!?

My usb connection died a long time ago so I always swapped batteries when they were empty and last weekend after a reboot I noticed my desktop being weird. Some widgets were missing, some others were added (the "Get Started" thing and some that are probably in the factory default settings). Also there were no messages and a bunch of other things were missing or not working (like the email application error loop you mentioned).

After some checking apparently my fat32 partition wasn't mounted, so I tried to do that manually (gave me a NFS handle error). Fsck'ing the partition didn't do a thing so I gave up and just used it a few more days as a simple phone.

Well and two days ago I once again swapped the battery and upon booting all fonts were missing, replaced by squares and I had what looked like a simple GTK theme on the buttons and stuff. :/

My guess here is that the flash memory chip died.

Re: N900 No fonts (squares instead), no icons and no wallpaper.

Well... some hours later... new phone in the pocket, my Galaxy Ace2 is working and saved my life and work. 5 minutes after i bought this phone i received a call from the other person, i explaine what happened and everything else went fine.

I was fidling with the N900 trying to find something anywhere, and i noticed a couple things.

The first, i touched cssu config in the menu that opens with power button and inside there, text was perfect.

The second, in that same place i noticed a small cursor (like the one on your computer screen that you move with the mouse) that moved to the place i touched.

So i guess, and only guess, that this may be an issue with the display driver or the desktop config.

Anyone who could give some advice? I've been few hours with the new phone and i'm desperate for my keyboard...

Re: N900 Mouse cursor appeared on screen and text only squares no fonts, video driver or desktop config?

OptFS filesystem corruption - happened, when your device crashed. It wouldn't be anything serious, probably, but CSSU tried to fsck it at startup, and segfaulting e2fsprogs messed up filesystem.

If you had backupmenu backup, restore it. If no - reflash. As for your reflash problems, try different machine, different OS (liveCd linux?), etc. It's quite common problem.

/Estel

Re: N900 Mouse cursor appeared on screen and text only squares no fonts, video driver or desktop config?

Ok, thank you Estel i will try other computers, maybe over Linux.

I dont want to lose the N900, i'm about to start to hate android and touchscreen only writing on such small device.

Will try and tell.

YEYYY!!!!!
[crazyface]Is aliive...
Is aliiiiiive...
[/crazyface]

Well, i had to make a full reflash on a compuiter with 32bits windows (Win8 BTW) since none of my computers using 64bits windows allowed me to do it.

Now... I have to recover almost 3 years of software installing and customizing.
This is gonna hurt surely. I tought that Nokia suite's full backup backed up everything... But it does not.

Anyway, i'm now starting to get it it motion again to try stop using the new phone (Samsung with android) wich is making me crazy, but not because of software issues... for hardware crazyness.

I never lost signal with my N900, even inside elevators, basements, etc... (never tried underwater) this crappy 400 US dollars samsung loses signal in plain street.

And the worst thing is that this s..t came with a faulty audio jack, but, since is a mechanical damage, warranty does not cover it. I'm starting to hate Samsung, so, in order to keep my almost good relation with that brand, i hope i can start using my Nokia as soon as possible.

Thanks Estel, i revived my wonder machine only because you said i had to try different computers, otherwise i was convinced the phoen was completelly unrecoverable.

Re: N900 Mouse cursor appeared on screen and text only squares no fonts, video driver or desktop config?

I recommend you to install backupmenu from now, and do regular full backups now and then. That way if your phone ever goes ASDF it is one click away to recovering ' 3 years of software recovering and customizing '. :)

Re: N900 Mouse cursor appeared on screen and text only squares no fonts, video driver or desktop config?

I'm still trying to get everything installed, and i'm again and again having the same issues i had when trying to get everything in motion the first time.

Since i have a new Android phone, i;m not in a hurry, but there is so much i miss from the N900 than i want it working NOW!!!..

When i finish everything and i could start to use it again i will install backupmenu for sure, i can't stand all this pain again.

Thank you very much, and thanks to eveyrone who had patience on every question i have made since i started to ask for help here.

Re: N900 Mouse cursor appeared on screen and text only squares no fonts, video driver or desktop config?

RichardN900, MONVMENTVM, ..guess I'm a little late to the party.

I just restarted my n900 and had it come up with the same issue. All text rendered as squares, and a little black cursor while clicking.

Asked in #maemo to compare with non-broken devices, but others did not find anything incorrect with the font path I'm seeing.
Not certain about the rest.
/tmp/Xorg.0.log reads:

Code:

(WW) Failed to open protocol names file /usr/lib/xorg/protocol.txt(++) Log file: "/tmp/Xorg.0.log", Time: Thu Oct 31 20:18:56 2013

(==) Using config file: "/etc/X11/xorg.conf"

(==) No Layout section.  Using the first Screen section.

(==) No screen section available. Using defaults.

(**) |-->Screen "Default Screen Section" (0)

(**) |   |-->Monitor "<default monitor>"

(==) No monitor specified for screen "Default Screen Section".

        Using a default monitor configuration.

(==) Automatically adding devices

(==) Automatically enabling devices

(WW) `fonts.dir' not found (or not valid) in "/".

        Entry deleted from font path.

        (Run 'mkfontdir' on "/").

(==) FontPath set to:

        built-ins

(==) ModulePath set to "/usr/lib/xorg/modules"

(II) Cannot locate a core pointer device.

(II) Cannot locate a core keyboard device.

(II) The server relies on HAL to provide the list of input devices.

        If no devices become available, reconfigure HAL or disable AllowEmptyInput.

(--) using VT number 2



(WW) xf86OpenConsole: setpgid failed: Operation not permitted

(WW) xf86OpenConsole: setsid failed: Operation not permitted

(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so

(II) Module extmod: vendor="X.Org Foundation"

        compiled for 1.6.99.1, module version = 1.0.0

(II) Loading /usr/lib/xorg/modules/extensions/libdbe.so

(II) Module dbe: vendor="X.Org Foundation"

        compiled for 1.6.99.1, module version = 1.0.0

(II) Loading /usr/lib/xorg/modules/extensions/librecord.so

(II) Module record: vendor="X.Org Foundation"

        compiled for 1.6.99.1, module version = 1.13.0

(II) Loading /usr/lib/xorg/modules/extensions/libdri2.so

(II) Module dri2: vendor="X.Org Foundation"

        compiled for 1.6.99.1, module version = 1.0.0

(==) Matched fbdev for the autoconfigured driver

(==) Assigned the driver to the xf86ConfigLayout

(II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so

(II) Module fbdev: vendor="X.Org Foundation"

        compiled for 1.6.99.1, module version = 0.4.0

(II) FBDEV: driver for framebuffer: fbdev

(WW) Falling back to old probe method for fbdev

(II) Loading /usr/lib/xorg/modules/linux/libfbdevhw.so

(II) Module fbdevhw: vendor="X.Org Foundation"

        compiled for 1.6.99.1, module version = 0.0.2

(II) FBDEV(0): using default device

(II) Running in FRAMEBUFFER Mode

(II) FBDEV(0): Creating default Display subsection in Screen section

        "Default Screen Section" for depth/fbbpp 16/16

(==) FBDEV(0): Depth 16, (==) framebuffer bpp 16

(==) FBDEV(0): RGB weight 565

(==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)

(==) FBDEV(0): Default visual is TrueColor

(II) FBDEV(0): hardware: omapfb (video memory: 1920kB)

(II) FBDEV(0): Output LCD has no monitor section

(II) FBDEV(0): Output LCD connected

(II) FBDEV(0): Using exact sizes for initial modes

(II) FBDEV(0): Output LCD using initial mode 800x480

(II) FBDEV(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.

(II) Loading /usr/lib/xorg/modules/libfb.so

(II) Module fb: vendor="X.Org Foundation"

        compiled for 1.6.99.1, module version = 1.0.0

(==) FBDEV(0): DPI set to (96, 96)

(II) FBDEV(0): Pitch updated to 2048 after ModeInit

(II) Loading /usr/lib/xorg/modules/libexa.so

(II) Module exa: vendor="X.Org Foundation"

        compiled for 1.6.99.1, module version = 2.4.0

(II) EXA(0): Driver allocated offscreen pixmaps

(II) EXA(0): Driver registered support for the following operations:

(II)         Solid

(II)         Copy

(II) FBDEV(0): [DRI2] Setup complete

(==) FBDEV(0): Backing store disabled

(II) FBDEV(0): RandR 1.2 enabled, ignore the following RandR disabled message.

(--) RandR disabled

(II) FBDEV(0): Setting screen physical size to 211 x 127

(II) config/hal: waiting for HAL...

(II) config/hal: initialised context in 4200 milliseconds.

(II) Loading /usr/lib/xorg/modules/input/evdev_drv.so

(II) Module evdev: vendor="X.Org Foundation"

        compiled for 1.6.99.1, module version = 2.1.99

(**) TSC2005 touchscreen: Device: "/dev/input/event3"

(**) TSC2005 touchscreen: Calibration factors: 222 3895 3746 245 0 0

(II) TSC2005 touchscreen: Found x and y absolute axes

(II) TSC2005 touchscreen: Found absolute touchscreen

(II) TSC2005 touchscreen: Configuring as touchscreen

(**) TSC2005 touchscreen: (accel) acceleration profile 0

(**) TSC2005 touchscreen: (accel) filter chain progression: 2.00

(**) TSC2005 touchscreen: (accel) filter stage 0: 20.00 ms

(**) TSC2005 touchscreen: (accel) set acceleration profile 0

(**) omap_twl4030keypad: Device: "/dev/input/event1"

(II) omap_twl4030keypad: Found keys

(II) omap_twl4030keypad: Configuring as keyboard

/var/log/fsck_home.log reads:

Code:

2013-10-26 15:37:02  fsck -a /home

fsck 1.41.3.maemo0 (12-Oct-2008)

/dev/mmcblk0p2 contains a file system with errors, check forced.

/dev/mmcblk0p2: Directory inode 115132, block 0, offset 0: directory corrupted





/dev/mmcblk0p2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

        (i.e., without -a or -p options)



1999-12-31 18:11:39  fsck -a /home

fsck 1.41.3.maemo0 (12-Oct-2008)

/dev/mmcblk0p2: recovering journal

/dev/mmcblk0p2: Superblock last mount time is in the future.  FIXED.

/dev/mmcblk0p2 contains a file system with errors, check forced.

/dev/mmcblk0p2: Directory inode 115132, block 0, offset 0: directory corrupted





/dev/mmcblk0p2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

        (i.e., without -a or -p options)



1999-12-31 18:13:26  fsck -a /home

fsck 1.41.3.maemo0 (12-Oct-2008)

/dev/mmcblk0p2 contains a file system with errors, check forced.

/dev/mmcblk0p2: Directory inode 115132, block 0, offset 0: directory corrupted





/dev/mmcblk0p2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

        (i.e., without -a or -p options)



2013-10-31 20:18:19  fsck -a /home

fsck 1.41.3.maemo0 (12-Oct-2008)

/dev/mmcblk0p2: recovering journal

JBD: recovery pass 2 ended at transaction 1775851, expected 1775927

fsck.ext3: Input/output error while recovering ext3 journal of /dev/mmcblk0p2



2013-10-31 20:18:56  fsck -a /home

fsck 1.41.3.maemo0 (12-Oct-2008)

/dev/mmcblk0p2 contains a file system with errors, check forced.

/dev/mmcblk0p2: Inode 8, i_blocks is 16408, should be 8224.  FIXED.

/dev/mmcblk0p2: Inode 11062 is in use, but has dtime set.  FIXED.

/dev/mmcblk0p2: Inode 11062 has compression flag set on filesystem without compression support.  



/dev/mmcblk0p2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

        (i.e., without -a or -p options)

Indeed looks like (at least) /dev/mmcblk0p2 my ext3 /home fs had been getting a little .. damaged and then fsck.ext3 had a segfault this evening.

rootfs appears to be mounted fine (rw) yet apt-get "E: Unable to write to /var/cache/apt/" :\

Re: N900 Mouse cursor appeared on screen and text only squares no fonts, video driver or desktop config?

flashed FIASCO image (kernel/rootfs/bootloader stages) and was able to get only one good boot. rebooting every time came up with the no font/squares instead of text problem, only now GTK theme came up as the default/grey and pink boxes/no background image was shown on the App Menu/hildon-status-menu,

I dont recall going out of my way to optify anything on n900, and mount is indicating /home is still rw (Was able to configure WiFi, install rootsh and OpenSSH sshd before rebooting) but it seems like ext3 journal is really holding everything back somehow (and getting worse)

after trying to install a third package, apt log began to state /opt was read-only, unable to complete further install.

From dmesg

Code:

[   11.610260] journal_bmap: journal block not found at offset 12 on mmcblk0p2

[   11.610351] JBD: bad block at offset 12

[   11.610412] journal_bmap: journal block not found at offset 179 on mmcblk0p2

[   11.610443] JBD: bad block at offset 179

[   11.610504] JBD: recovery failed

[   11.610504] EXT3-fs: error loading journal.

[   16.297698] McSAAB: ACWAKE DOWN

[   16.297760] McSAAB: ACWAKE UP

[   16.297821] McSAAB: WAKELINES TEST OK

[   22.462158] EXT3-fs warning: mounting fs with errors, running e2fsck is recommended

[   22.462371] kjournald starting.  Commit interval 1 seconds

[   22.474487] EXT3 FS on mmcblk0p2, internal journal

[   22.474517] EXT3-fs: mounted filesystem with writeback data mode.

[   23.139434] journal_bmap: journal block not found at offset 12 on mmcblk0p2

[   23.139465] Aborting journal on device mmcblk0p2.

[   23.472625] journal commit I/O error

[   25.780029] ext3_abort called.

[   25.780059] EXT3-fs error (device mmcblk0p2): ext3_journal_start_sb: Detected aborted journal

[   25.780090] Remounting filesystem read-only

Seems to be all set now, after wiping mmcblk0p2 via:

- powering off
sudo flasher-3.5 -F "RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin" -f
- hold 'u' on keypad
- plugging in USB cable
- unpluging USB when flasher exits
- remove battery
sudo flasher-3.5 -F RX-51_2009SE_20.2010.36-2.002_PR_COMBINED_002_ARM.bin -f
- hold 'u' on keypad
- plugging in USB cable
- unpluging USB when flasher exits
- remove battery

Re: N900 Mouse cursor appeared on screen and text only squares no fonts, video driver or desktop config?

Was about to say that the relevant stuff (themes, fonts, icons, cursors) are in /opt so you need to flash VANILLA but you got there on your own. Glad you got it working.