Arch Linux ARM on N900 - Page 17 - maemo.org

Skry | # 161 | 2013-02-27, 13:42 | Report

Originally Posted by tamas2001 View Post

-->SGX
Most probably I have missed something important, but SGX does not work.. I've installed the sgx-bin and fbdev-sgx packages started the powervr service, some sgx processes are there,but just have fbdev seg fault in Xorg.log

I need some details, you can throw me some logs and such on IRC.

Originally Posted by tamas2001 View Post

-->USB NIC
I've one, based on AX88178 chip, already compiled its driver on N900. I'll test it just need proper cable to be able to connect (USB NIC<-->N900).

Don't bother, host mode is not working with 3.5.x nor is it working in upstream, and I know it's way out of my skills to even try to fix it.

Originally Posted by tamas2001 View Post

-->Overclocking
Is that already possible in any similiar way as with kernel-power?

Overclocking is something I will never implement, support or suggest. Reasons are well discussed on #maemo. N900 is fast enough, it's software that's slow, sucky and bloated

The Following 3 Users Say Thank You to Skry For This Useful Post:
int_ua, tamas2001, tcbl50

Älä hakkaa | # 162 | 2013-02-27, 14:39 | Report

No, I skipped over it as my only concern was that photo. :P Nevertheless, thinking out a solution could be worth it, as illume seems to be a very popular theme.

Originally Posted by caveman View Post

Have you succeeded with the illume profile?

Skry | # 163 | 2013-02-27, 15:55 | Report

tamas2001 made me find out that I have forgot to upgrade xf86-video-fbdev-sgx-git on repository so it was not working. That's fixed now and the new version is out.

Unfortunately adapting ti-omap3-sgx-bin to new mesa packaging was not that simple as it first appeared..

Originally Posted by

17:34:26 [ Skry] I still need to rework ti-omap3-sgx because the linker problem, meanwhile if you have something that supports gles you need to setup LD_PRELOAD environment variable
17:35:43 [ Skry] for example, running "application" from command line: LD_PRELOAD="/usr/lib/v7l/neon/libEGL.so /usr/lib/v7l/neon/libGLESv2.so" application
17:37:16 [ Skry] or you can export it, or put those libs to /etc/ld.so.preload as a whitespace separated list
17:38:13 [ Skry] this is solely because the change in Arch Linux mesa packaging, I can't replace mesa libs anymore like I did previously
17:39:09 [ Skry] anyway, there is pretty much nothing that has gles support enabled in alarm repositories

Last edited by Skry; 2013-02-27 at 16:01.

The Following 2 Users Say Thank You to Skry For This Useful Post:
int_ua, Sourav.dubey

caveman | # 164 | 2013-02-27, 17:33 | Report

@Skry: I really appreciate the work you are doing.

This is 3rd (re)install based on the information on this thread.

The first one was not successful as I could never boot. As you have pointed out in a previous pont, that was due to the u-boot version.

The second one went fine, and I used it to get a feel of what was going on.

This is the 3rd, and I hope it will achieve 'production' status. I used the 2013-02 rootfs, and installation has been flawless.

As I had no previous experience with arch linux, so I suggest a few more words in the install instructions, to ease the life of those who have no previous experience with arch. For instance, on the section about Xorg, I suggest that you mention the packages that have to be installed, such as xorg-init and xorg-server, in addition the those that are already mentioned. Maybe a link to https://wiki.archlinux.org/index.php/Xorg#Running would be enough.

I particularly like the work that has been done on the keyboard stuff. One item I had on my wish-list was vt switch on the console, which has just been posted.

Another item on my wish-list is a touch-friendly environment, and there were posts with WIP on hildon-desktop and e17. I am not sure how operational are those right now, but I believe those are the best alternatives available at the moment. I tried to load illume with e17 but got a load of errors and a black screen, but menus worked :-)

Keep up the good work!

The Following 5 Users Say Thank You to caveman For This Useful Post:
Estel, int_ua, Skry, Sourav.dubey, Älä hakkaa

caveman | # 165 | 2013-02-27, 17:34 | Report

I find the default console fonts too small for my eyes. Instruction for changing the fonts are at https://wiki.archlinux.org/index.php...#Console_fonts

I am using ter-120n from community/terminus-font.

Last edited by caveman; 2013-02-27 at 18:10. Reason: added ref to font

The Following 3 Users Say Thank You to caveman For This Useful Post:
Sourav.dubey, tcbl50, Älä hakkaa

int_ua | # 166 | 2013-02-27, 21:18 | Report

why do a lot of people ignore LXDE? Am I missing something bad about it?

caveman | # 167 | 2013-02-27, 21:31 | Report

Originally Posted by int_ua View Post

why do a lot of people ignore LXDE? Am I missing something bad about it?

Not at all. LXDE is always the first environment I install, and it just works. However, to be really usable, I have to use the keyboard+openbox shortcuts, or the stylus. Those are important use cases, but I miss the other use case I care: reading stuff without the keyboard open. For that I would like to use only my fingers, and I am not happy with LXDE in this scenario.

The Following User Says Thank You to caveman For This Useful Post:
int_ua

Skry | # 168 | 2013-02-27, 22:35 | Report

Originally Posted by caveman View Post

This is the 3rd, and I hope it will achieve 'production' status. I used the 2013-02 rootfs, and installation has been flawless.

Good to hear. I think this all is shaping up quite nicely.

Originally Posted by caveman View Post

As I had no previous experience with arch linux, so I suggest a few more words in the install instructions, to ease the life of those who have no previous experience with arch.

Arch users are elitist *******s.
I believe I've linked to more than enough information in the guide, and wiki will be there once I have time. I don't like hand holding or explaining something that has been covered already in Arch wiki, and many more sources elsewhere. Supposedly, and hopefully, this approach should keep this guide simple and easy to follow. It also has the added bonus of actually learning stuff. That said, if there is something that seems to confuse the majority, of course I'll try to clarify it.

Originally Posted by caveman View Post

I particularly like the work that has been done on the keyboard stuff. One item I had on my wish-list was vt switch on the console, which has just been posted.

Great! I'll include it in next n900-integration.
Since we're probably not going to use (the not working) cameras in VT, how do you/everyone feel about adding Alt and PrintScreen to cam button? That would give us Alt+whatever on half press, Alt+PrtScr on full press to use as a one key shortcut and a magic sysrg key if desired. Ctrl-Alt(Gr)-Del is also possible, with or without cam button.

Originally Posted by int_ua

why do a lot of people ignore LXDE? Am I missing something bad about it?

IIRC before I cleaned up the guide, I referenced it as an ugly and misconfigured openbox

I think this would be a good moment to say Thank You everyone for your feedback and support, keep it going.

The Following 9 Users Say Thank You to Skry For This Useful Post:
ArchiMark, caveman, int_ua, mr_pingu, PanzerSajt, peterleinchen, Sourav.dubey, tcbl50, Älä hakkaa

caveman | # 169 | 2013-02-28, 11:32 | Report

I am trying the accelerated X driver, but it just gives me a blank screen. Xorg.log.0 has a line saying

Code:

PowerVR device not found

and

Code:

PVR2D_Init() failed

. I believe I have installed all the appropriate packages.

I reverted to standard fbdev driver and everythings is working, but I would appreciate clues to debug this.

Skry | # 170 | 2013-02-28, 12:48 | Report

Originally Posted by caveman View Post

I am trying the accelerated X driver, but it just gives me a blank screen. Xorg.log.0 has a line saying

Code:

PowerVR device not found

and

Code:

PVR2D_Init() failed

. I believe I have installed all the appropriate packages.

I reverted to standard fbdev driver and everythings is working, but I would appreciate clues to debug this.

And you have powervr service started?
It's responsible of loading the kernel modules and starting the device. Post-install script of ti-omap3-sgx-bin should notify you to start or enable it.

Last edited by Skry; 2013-02-28 at 12:52.

The Following User Says Thank You to Skry For This Useful Post:
caveman