Results 1 to 4 of 4

Thread: Launching X server on an Intel Oak Trail computer

  1. #1

    Default Launching X server on an Intel Oak Trail computer

    I am trying to get the X server working on my tablet PC, and so far I have had limited success. openSUSE 11.4 won't even install (hangs on 'loading basic drivers'), but I did get to install the 12.1 beta. Now here's the strange thing: the installer has a graphical mode and it works like a charm. It's responsive and even supports the touchscreen of the computer. However, after the installation, the X server fails to launch. Which is not very surprising, considering that I didn't get it working on any other Linux distribution so far, but it's obvious that it can work, as demonstrated by the installation program.

    My Xorg.0.log on the tablet PC contains these bits of interest:
    Code:
    (==) Matched psb as autoconfigured driver 0
    (==) Matched psb_drv as autoconfigured driver 1
    (==) Matched fbdev as autoconfigured driver 2
    (==) Matched vesa as autoconfigured driver 3
    
    (II) LoadModule: "psb"
    (WW) Warning, couldn't open module psb
    (II) UnloadModule: "psb"
    (II) Unloading psb
    (EE) Failed to load module "psb" (module does not exist, 0)
    (II) LoadModule: "psbdrv"
    (WW) Warning, couldn't open module psbdrv
    (II) UnloadModule: "psbdrv"
    (II) Unloading psbdrv
    (EE) Failed to load module "psbdrv" (module does not exist, 0)
    
    (WW) xf86OpenConsole: setpgid failed: Operation not permitted
    (WW) xf86OpenConsole: setsid failed: Operation not permitted
    
    (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
    (EE) open /dev/fb0: No such file or directory
    (WW) Falling back to old probe method for fbdev
    
    (II) VESA(1): Bad V_BIOS checksum
    (II) VESA(1): Pribary V_BIOS segment is: 0xc000
    (II) VESA(1): VESA BIOS detected
    
    (II) VESA(1): VESA VBE DDC supported
    (II) VESA(1): VESA VBE DDC Level none
    (II) VESA(1): VESA VBE DDC transfer in appr. 0 sec.
    (II) VESA(1): VESA VBE DDC read failed
    (II) VESA(1): VESA VBE PanelID read successfully
    (II) VESA(1): PanelID returned panel resolution 1280x800
    The log ends with this:

    Code:
    (II) VESA(0): VESA VBE OEM Software Rev: 1.0
    (II) VESA(0): VESA VBE OEM Vendor: Intel Corporation
    (II) VESA(0): VESA VBE OEM Product: Intel(R)Oaktrail Graphics Controller
    (II) VESA(0): VESA VBE OEM Product Rev: Hardware Version 0.0
    (II) VESA(0): virtual address = (nil),
    
    physical address = 0x7f700000, size = 8060928
    (II) VESA(0): virtual address = 0xb710b000,
    physical address = 0xa0000, size = 65536
    c000:0287: 3A ILLEGAL EXTENDED X86 OPCODE! (II) VESA(0): Setting up VESA mode 0x118 (1024x768) (II) VESA(0): VBESetVBEMode failed Fatal server error: AddScreen/ScreenInit failed for driver 0
    And if I try to do a startx:

    Code:
    hostname: Name or service not known
    xauth: file /home/user/.serverauth.1802 does not exist
    
    Fatal server error:
    Cannot move old log file "/var/log/Xorg.0.log" to "/var/log/Xorg.0.log.old"
    
    xinit: giving up
    xinit: unable to connect to X server: Connection refused
    xinit: server error
    ------------------------------------------------------
    xinit failed. /usr/bin/Xorg is not setuid, maybe that's the reason?
    If so either use a display manager (strongly recommended) or adjust /etc/permissions.local
    I'm using (or trying to use, anyway) IceWM, and it won't boot either, saying that you have to have X started first. But, as I mentioned, the same thing happens on every other desktop interface anyway.

    I'm trying to get this working on a Fujitsu Stylistic tablet. The lspci output is this:
    Code:
    00:00.0 Host bridge: Intel Corporation Device 4110 (rev 04)
    00:02.0 VGA compatible controller: Intel Corporation Device 4102 (rev 04)
    00:1f.0 ISA bridge: Intel Corporation Device 0817 (rev 03)
    01:01.0 Display controller: Intel Corporation Moorestown External Displays (rev 01)
    03:10.0 System peripheral: Intel Corporation Moorestown SC DMA (rev 01)
    05:11.0 Communication controller: Intel Corporation Moorestown SPI Ctrl 1 (rev 01)
    07:12.0 Communication controller: Intel Corporation Moorestown I2C 0 (rev 01)
    08:13.0 Communication controller: Intel Corporation Moorestown I2C 1 (rev 01)
    09:14.0 Communication controller: Intel Corporation Moorestown I2C 2 (rev 01)
    0b:15.0 Audio device: Intel Corporation Moorestown Audio Ctrl
    0c:16.0 USB Controller: Intel Corporation Moorestown USB Ctrl (rev 01)
    0d:17.0 USB Controller: Intel Corporation Moorestown OTG Ctrl (rev 01)
    0e:18.0 SD Host controller: Intel Corporation Moorestown SD Host Ctrl 0 (rev 01)
    0f:19.0 SD Host controller: Intel Corporation Moorestown SD Host Ctrl 1 (rev 01)
    10:1a.0 SD Host controller: Intel Corporation Moorestown SPI Ctrl 2 (rev 01)
    11:1b.0 SATA controller: Intel Corporation Device 0816 (rev 01)
    A few more things to note is that the device is actually using UEFI, and not BIOS, and a. Also, lsmod shows both psb and psb_drv, although I had to use "nomodesest" in order to get the OS to boot past the driver loading stage (it always hangs on the card reader for some reason). Any ideas about what is causing the errors and why is there a difference between the installation program and the installed system?

  2. #2
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,130
    Blog Entries
    2

    Default Re: Launching X server on an Intel Oak Trail computer

    Since you're now running a Beta, I recommend you re-post your question (or the Forums Admin can move) this thread to the "Beta/Pre-release" forum

    Pre-Release/Beta

    Sorry I can't help on your specific problem...

    Tony

  3. #3

    Default Re: Launching X server on an Intel Oak Trail computer

    Well, this issue is not specific to the beta, it happens on every other distribution and would happen in the release version as well, if it actually ran without locking up.

    Anyway, I have found some interesting information here:
    Re: Can't start X on Intel GMA600 display card system - Adam Jackson - com.redhat.fedora-test-list - MarkMail
    It seems like a driver issue, but then again, what makes the installation program there run correctly?..

  4. #4

    Default Re: Launching X server on an Intel Oak Trail computer

    All right, I managed to figure that one out by myself! I observed the differences between the installation program and the installed OS, and the solution is pretty simple - I had to add 'vga=792' to the kernel boot options (and still have nomodeset, but that's apparently a different issue). So now I get TWM! (I was expecting IceWM, but that works too for the time being, and that's also an entirely different issue. )

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •