[pnv lvds] Nothing on screen on Tablet with 11.04, 11.10 and 12.04 worked on Maverick

[PEIGNOT Kévin]

I installed Ubuntu 11.10 on my tablet. It's the LDLC Janus one, a tablet selled by the French seller LDLC without any OSes : http://www.ldlc.com/fiche/PB00118640.html

The installation works great (live CD is OK, including touch screen (even if without multi-touch, maybe this is normal)). But when I reboot, there is nothing on the screen, even if I Ctrl+Alt+F1 or F2... But I'm sure the tablet boots "in background" : I can ear the login sound.

I tried with Ubuntu 11.04, exactly same problem. With Ubuntu 10.10, it works, but without screen touch (that's why I choosed utouch to report the bug even if I'm not sure that's the good attachment). I tried Fedora 15 and 16 it's OK (always without multitouch, but maybe it's normal).

Thanks to this answer : http://askubuntu.com/questions/78400/how-to-report-a-crash-bug-with-nothing-on-screen I can connect via SSH to the tablet to launch dmesg or other. Can you say me what you need ?
---
.tmp.unity.support.test.0:

.tmp.unity.support.test.1:

ApportVersion: 1.23-0ubuntu3
Architecture: i386
CompizPlugins: [core,bailer,detection,composite,opengl,decor,regex,animation,gnomecompat,compiztoolbox,resize,mousepoll,imgpng,vpswitch,move,expo,grid,place,snap,wall,workarounds,ezoom,unitymtgrabhandles,session,fade,scale,unityshell]
CompositorRunning: compiz
DistUpgraded: Fresh install
DistroCodename: oneiric
DistroRelease: Ubuntu 11.10
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation N10 Family Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller])
   Subsystem: Device [1b50:5608]
   Subsystem: Device [1b50:5608]
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: ONKYO ONKYOPC
Package: xorg 1:7.6+7ubuntu7
PackageArchitecture: i386
ProcEnviron:
 LC_CTYPE=fr_FR.UTF-8
 LC_COLLATE=fr_FR.UTF-8
 LANG=fr_FR.UTF-8
 LC_MESSAGES=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=5c7acb64-6a71-419e-a3be-23ec4f017c5a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Tags: oneiric running-unity ubuntu compiz-0.9
Uname: Linux 3.0.0-12-generic i686
UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 1: Error: OpenGL rendering is not supported by the root visual
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/24/2011
dmi.bios.vendor: 1.03(DO)
dmi.bios.version: P10BFZ17
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Tiger Hill
dmi.board.vendor: INTEL Corporation
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: ONKYO
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvn1.03(DO):bvrP10BFZ17:bd05/24/2011:svnONKYO:pnONKYOPC:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnTigerHill:rvrTobefilledbyO.E.M.:cvnONKYO:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: ONKYOPC
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: ONKYO
version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1

[Brendan Donegan (brendan-donegan)]

I'm putting this in Xorg's park, even though it's probably not a bug as such - just something unsupported. This certainly has nothing to do with Ubuntu Friendly (you wouldn't have been able to even run our test suite without anything on screen) so I've marked the bug there 'Invalid'. Probably if you can SSH in then running 'apport-collect 889459' would be helpful to diagnose your issue.

[PEIGNOT Kévin (kpeignot)]

apport information

[PEIGNOT Kévin (kpeignot)]

apport information

[PEIGNOT Kévin (kpeignot)]

apport information

[PEIGNOT Kévin (kpeignot)]

apport information

[PEIGNOT Kévin (kpeignot)]

apport information

[PEIGNOT Kévin (kpeignot)]

apport information

[PEIGNOT Kévin (kpeignot)]

apport information

[PEIGNOT Kévin (kpeignot)]

apport information

[PEIGNOT Kévin (kpeignot)]

apport information

[PEIGNOT Kévin (kpeignot)]

apport information

[PEIGNOT Kévin (kpeignot)]

apport information

[PEIGNOT Kévin (kpeignot)]

apport information

[PEIGNOT Kévin (kpeignot)]

apport information

[PEIGNOT Kévin (kpeignot)]

apport information

[PEIGNOT Kévin (kpeignot)]

apport information

[PEIGNOT Kévin (kpeignot)]

apport information

[PEIGNOT Kévin (kpeignot)]

apport information

[PEIGNOT Kévin (kpeignot)]

apport information

[PEIGNOT Kévin (kpeignot)]

apport information

[PEIGNOT Kévin (kpeignot)]

apport information

[PEIGNOT Kévin (kpeignot)]

apport information

[PEIGNOT Kévin (kpeignot)]

Thanks a lot for your answer, I really didn't know what information provide more, nore on what package attaching this bug.

[PEIGNOT Kévin (kpeignot)]

If this can help you, it seems Chromium OS works (no multi-touch, just simple touch, but it's better than nothing). Android 2.3 and 3.2 x86 works with no touch at all.

[PEIGNOT Kévin (kpeignot)]

The bug occur with Kubuntu 11.10 (I tried, I had hope :D )

[PEIGNOT Kévin (kpeignot)]

I will try soon with Ubuntu 12.04 in case ....

[PEIGNOT Kévin (kpeignot)]

I tried with previse today, same problem, even if I update via chroot. Fedora still don't have thos problem, and live still detect screen and touch events.

[PEIGNOT Kévin (kpeignot)]

I discovered that if I plug an external display, the two displays (the original tablet one's and the external one) work perfectly, then if I disconnect the external display, the original one still works great. If I reboot with only one display : same problem.

Here are the results of the xrandr command

Screen 0: minimum 320 x 200, current 800 x 600, maximum 4096 x 4096
LVDS1 connected 800x600+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1024x600 60.0 +
   800x600 60.3* 56.2
   640x480 59.9
VGA1 connected 800x600+0+0 (normal left inverted right x axis y axis) 338mm x 270mm
   1280x1024 60.0 + 75.0
   1280x960 60.0
   1152x864 75.0
   1024x768 75.1 70.1 60.0
   832x624 74.6
   800x600 72.2 75.0 60.3* 56.2
   640x480 72.8 75.0 66.7 60.0
   720x400 70.1

[PEIGNOT Kévin (kpeignot)]

I tried this http://ubuntuforums.org/showthread.php?t=1613132 (putin the nomodeset option in Grub : no effects)

[Chris Wilson (ickle)]

If ChromeOS/Android work where Ubuntu doesn't, that suggests you need a kernel update for a more recent (or perhaps older!) driver.

[PEIGNOT Kévin (kpeignot)]

I couldn't say, but with old kernels (until 10.10) screen worked great without touch screen. Since 12.10 (and it's always the case for 13.04, touch screen works fine, but I must have an external display at boot and then remove it). What other informations do you need ?

[Chris Wilson (ickle)]

Can you try with the nomodeset option i.e. can it be intialised correctly by the bios?

Then can you install intel-gpu-tools and attach the output of intel_reg_dumper for both nomodeset and normal booting.

As this is still an issue, I would recommend you open an upstream bug on bugzilla.freedesktop.org under DRM - Driver/Intel , and please be prepared to compile kernels.

[PEIGNOT Kévin (kpeignot)]

Ok, I will try to do that as soon as possible.

Is intel_reg_dumper a command I have to run, a file ? where will I find this output ?

[Chris Wilson (ickle)]

intel_reg_dumper is a command found in the intel-gpu-tools package that simply reads a bunch of registers and prints the values to stdout, so redirect that to a file and attach.

[bugbot (bugbot)]

We're closing this bug since there has not been a response from the original reporter. However, the issue still exists please feel free to reopen with the requested information. If you're not the original reporter, we'd prefer you file a new bug report.

Some tips:

  * Report X.org bugs via the command: `ubuntu-bug xorg`

  * Test against the latest development Ubuntu. http://cdimage.ubuntu.com/daily-live/
    Bugs marked as affecting the development version tend to get priority attention.

  * The `xdiagnose` utility has functionality for enabling debugging and
    analyzing a few common X problems.

  * Tag your bugs with the Ubuntu versions you have reproduced the issue in.

  * See https://wiki.ubuntu.com/X/Reporting for tips on writing good bug reports.

[PEIGNOT Kévin (kpeignot)]

Still the problem on raring (didn't had time to test since a few months) :

If I'm starting normally, nothing on screen
If I use recovery mode then resume, unity loads, very very slow, and with bad resolution
Impossible to use unity-system-compositor : unity-system-compositor close the communication and lightdm switch bask on X with the same olds bugs

[Daniel van Vugt (vanvugt)]

Invalid for unity-system-compositor. The bug was reported almost 2 years before unity-system-compositor existed :)