Lapdock (again)

I tried to repair my Lapdock configuration this morning.
Broken SD card…

I reinstalled the system: no problem with new ROM, but auto mode switch to 1920×1080 and does not propose 1360×768. And of course, the format of MDF changed, so my old MDF is not supported any more. So I used Anymode: screen corrupted, only at 1360×768. Strange. I switch back to the RC12 rom, with my old MDF: screen corrupted, only at 1360×768. Again.

Should I use an older ROM, and which one? Should I use another MDF? Should I change something in my config.txt, or perhaps the firmware file? Can someone send me the right “ROM + config.txt + firmware + MDF (if needed) set?” Thanks!

I’m should be more confident in my backups. Yes, it was a firmware problem. Fixed. RC12 rom works. Does someone have the rc12a Rom? RC14 does not work (cannot read old MDF), but I’m almost sure RC12a will…

Unrelated question. Does someone managed to get alt-break on the Lapdock keyboard? Not to be able to stop applications is sometimes very annoying :)

For Break I use the right-hand Ctrl key with KeyMapper:

RC14 does not work (cannot read old MDF)

I missed that change, but I have not used RC14 yet. How do MDFs differ now? Could the problem lie with needing to use 1360, a multiple of 16, rather than the true resolution of 1368? Am I right about that anyway? ;-)

For Break I use the right-hand Ctrl key with KeyMapper:

Dammit, I already use Ctrl key for right click :)

I missed that change, but I have not used RC14 yet. How do MDFs differ now?

Raik told me that a little change is needed. The “resolution line” should begin with |, or something like this :) He uses config.txt mode, but here it does not work (always revert to 1920×1080).

Anyway, RC12a should work.

Just for information: I now have a working RC12 rom, a yet to be tested RC12a rom, and I plan to make further MDF tests with ROS 5.22. Raik told me he chooses the mode in config.txt file. I tried, but it does not work (the OS still switch to 1920×1080). Probably that, this time, my firmware is too old :)

There are two separate negotiations for screen mode: between GPU and monitor (done by EDID and config.txt) and between RISC OS and GPU (set by RISC OS). Check what the monitor thinks it is receiving as well as what RISC OS thinks it is sending and quote both please.

Will be done with ROS 5.22. For now, config.txt with mode 1360×768 makes the OS boot in 1920×1080 in auto mode. But I need perhaps to upgrade my boot sequence. And perhaps my firmware too.

@Chris
I use a “dirthy” RC14 with parts from all with a RPi Modell A and a Lapdock. Works with hdmi_group=2 and hdmi_mode=39 (1360×768) and a “normal” MDF.
Now I try RC14. Works not. ReadEDID is not implemented I mean ("not found-message in TaskWindow).
Now I try the first 5.23 ROM. The old way is also not working.
ReadEDID give nothing (the next *(Star) in TaskWindow) but set the Lapdock Monitor. But the usable Resolution is the last activ one (I try with 1920×1080 and 1260×720).
If I use GetMonInfo to read the EDID data it displayed the correct EDID one (1366×768, different frequence and so on… sorry I forgot the file). A MDF with this are ignored. This was also with the old ROMs and the reason why we are using 1360×768.

The EDID-File created by GetMonInfo you can find here

I forgot: If I use 1260×720 and change to 1360×768 via iconbar Screen-App it works. If I configure 1360×768 (same MDF) via !Configure it failed.

For now, config.txt with mode 1360×768 makes the OS boot in 1920×1080

Not true, I’m afraid. The two are unconnected. config.txt controls the GPU and asks it to talk to the monitor in the mode specified. RISC OS has a separate screen setting that it uses to talk to the GPU. The GPU automatically stretches and shrinks what it gets from the OS into the format it has been asked to use by the monitor.

The monitor then, given its native resolution on an LCD panel is fixed, and might not match either of the above then does its best to display what it gets from the GPU. Complicated isn’t it?

So it uses 1366×768, but shows the screen in 1920×1080 and can’t switch to 1360×768 without corrupting all.
With RC12, it clearly boots in the mode configured in config.txt. With RC14, I’m not so sure.

The monitor then, given its native resolution on an LCD panel is fixed, and might not match either of the above then does its best to display what it gets from the GPU.

Right and not. The Lapdock can handle more than one resolution. The nativ (real) resolution is 1366×768. 1360×768 works perfect. The Atrix Smartphone for the Lapdock can also handle more than one rsolution. Not sure what the range is but 1920×1080 also working with the Lapdock. The Lapdock scales intern.
The problem must be a other one. At this time I start with Generic 1280×72060Hz (in predesk via configure) works and a second Obey in Tasks switch to 1360x76855Hz (I insert in the Generic MDF). Works. But I can not back to 1920×1080 (not a problem). Displayed data dust.
If I try to use 1360×768 in Predesk (via configure)… works not. If I use “Auto” it displayed a 1920×1080 Desktop. If I try to change to 1360×768... works not.
Not sure what the problem is but they are (m)any differences in RC14. With RC12, RC12a(and before) all things fine with the Lapdock Display.

Sorry,I forgot.
From time to time I try a development ROM (5.21). After change the ROM and Restart, the Monitorsettigs are ignored. Thats the reason why I insert hdmi_group=2 and hdmi_mode=39 in the config.txt. After this, my old settings are working after ROM changing.
With RC14 and also with the 5.23 ROM…
With RC14 and also with 5.23 I try hdmi_group=1. The desktop is displayed in a small letterbox and very blurry.

Hi Raik/David

I’ve updated my Lapdock on numerous occasions from RC12 upwards and it is now running 5.23 and the screen setting are correct and not corrupted ot stretched to 1920 × 1080 so I know it works OK.

I also updated the disc/!Boot structure on many occasions though I did need to delete the contents of !Boot.Choices.Boot when going to RC14 as it casued some issues.

Config.txt is set as follows for my mark 1 version of the Pi.

hdmi_drive=2
hdmi_group=2
hdmi_mode=86
hdmi_force_edid_audio=1
disable_overscan=1
fake_vsync_isr=1
gpu_mem=64
init_emmc_clock=100000000
kernel=RISCOS.IMG

Hi Doug,

1920×1080 is not the problem. We are using 1360×768 and this is not working correct with RC14 and 5.23. RC12 is working perfect with this.

Raik,

Sorry if I did not make it clear but I am running at 1360 × 768 ok with the latest !Boot and 5.23.

Doug

Sorry, a other point is not clear ;-)
Use you RC12 and upgrade or RC14.
My main card is RC12 and I upgrade to "dirty " RC14 and more… works. If I use a clean RC14 works not, also not with 5.23 stuff.

Raik

OK I have only upgraded so that could be classed as a “dirty” upgrade.

I seemed to remember some debate about having to add the following line to CONFIG/TXT with some versions of the firmware as the red/blue colour channels are swapped by default:

framebuffer_swap=0

So you could try that?

Doug

I know the debate and I have the entry inside but this is not the reason for the problem. Without only any colours on the screen are changed.

RC14 “Second chance” ;-) I have try to merge in the latest !Boot and before I unprotect !Boot and set the fileroptions to force.
Now it looks like it works with 5.23.

Hi all, I have a Lapdock 100 and have been running it with Raspbian for some time.

Now, I want to use it as a RISC OS laptop. This almost works, with 2 issues:

1) I only get a display if the lapdock is discharged, the Pi is plugged in to it, and I apply external power to the Lapdock, so everything comes on at once. This is true with Raspbian too, I will deal with it separately – just mentioning here.

2) Using RC14 Risc OS, I cannot use the internal keyboard and mouse, which ‘just work’ under Raspbian. I can use an external keyboard which is odd. F12 and *configure mousetype 0-3 does not affect the mouse working.

Any ideas why #2 is the case and what I can do about it??

I am using RC14 and got 1366*768 resolution by using this config.txt file:

fake_vsync_isr=1
framebuffer_swap=0
gpu_mem=64
init_emmc_clock=100000000
kernel=RISCOS.IMG

hdmi_force_hotplug=1
hdmi_ignore_edid=0xa5000080
hdmi_drive=2
hdmi_group=2

hdmi_mode=81

config_hdmi_boost=5

I doubt it has too much to do with your problem, but RISC OS can manage 1360 × 768—not 1366 × 768.

(Corrected the figure—it was a typo as the following post indicates.)

David I think a typo occurred!
1360 × 768