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

Active Topics

U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1) (841)
to Alternatives by omniteal@pm.me - 1 hr, 34 mins ago
List of well performing apps on Leste (34)
to Maemo 7 / Leste by biketool - 12 hrs, 32 mins ago
Maemo repository (5)
to Community by dredlok706 - 2 days, 7 hrs ago
Re-commissioning N9 in 2018 (127)
to MeeGo / Harmattan by smatkovi - 2 days, 10 hrs ago
Porting apps to Leste (41)
to Maemo 7 / Leste by Arno_11 - 3 days, 3 hrs ago
N900 is not recognizable on any of my devices (windows 10,7, xp) What can I do? (1)
to Nokia N900 by nieldk - 4 days, 16 hrs ago
more...

Page 2 of 2

< Prev

Thread Tools

RichardN900	2013-09-02 , 14:23
Posts: 75 \| Thanked: 42 times \| Joined on Dec 2011 @ Uruguay	#11

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.

Quote & Reply |

bjv	2013-11-01 , 03:23
Posts: 35 \| Thanked: 33 times \| Joined on Feb 2010 @ North America	#12

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/" :\

Quote & Reply |

bjv	2013-11-02 , 01:25
Posts: 35 \| Thanked: 33 times \| Joined on Feb 2010 @ North America	#13

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

Quote & Reply |

	pichlo	2013-11-02 , 08:41
	Posts: 6,453 \| Thanked: 20,983 times \| Joined on Sep 2012 @ UK	#14

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.