US15W card Driver install problem

[curaga]

Same paths in 7.4.

[Daniel]

Thanks!

Same results with Xorg-7.4!

Bloqued when starting X with no error in "messages" file

Xorg.0.log:

Code: [Select]

X.Org X Server 1.6.1
Release Date: 2009-4-14
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.29.1-tinycore i686
Current Operating System: Linux box 2.6.33.3-tinycore #2012 SMP Wed May 12 17:05:42 EEST 2010 i686
Build Date: 25 April 2009  08:42:34PM
 
Before reporting problems, check www.tinycorelinux.com
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Mar 24 15:22:33 2011
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "Monitor0"
(**) |   |-->Device "IntelEMGD-0"
(==) Not automatically adding devices
(==) Not automatically enabling devices
(WW) The directory "/usr/local/lib/X11/fonts/OTF" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/local/lib/X11/fonts/OTF" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/local/lib/X11/fonts/100dpi/" does not exist.
Entry deleted from font path.
(**) FontPath set to:
/usr/local/lib/X11/fonts/misc/,
/usr/local/lib/X11/fonts/TTF/,
/usr/local/lib/X11/fonts/Type1/,
/usr/local/lib/X11/fonts/75dpi/,
/usr/local/lib/X11/fonts/misc/,
/usr/local/lib/X11/fonts/TTF/,
/usr/local/lib/X11/fonts/Type1/,
/usr/local/lib/X11/fonts/75dpi/,
built-ins
(**) ModulePath set to "/usr/local/lib/X11/modules"
(==) |-->Input Device "Mouse0"
(==) |-->Input Device "Keyboard0"
(==) The core pointer device wasn't specified explicitly in the layout.
Using the first mouse device.
(==) The core keyboard device wasn't specified explicitly in the layout.
Using the first keyboard device.
(II) Loader magic: 0x7abc
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 5.0
X.Org XInput driver : 4.0
X.Org Server Extension : 2.0
(II) Loader running on linux
(--) using VT number 2

(--) PCI:*(0@0:2:0) unknown vendor (0x8086) unknown chipset (0x8108) rev 7, Mem @ 0xd0080000/524288, 0xc0000000/268435456, 0xd0040000/262144, I/O @ 0x00001800/8
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri" will be loaded by default.
(II) LoadModule: "glx"
(II) Loading /usr/local/lib/X11/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "extmod"
(II) Loading /usr/local/lib/X11/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/local/lib/X11/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "freetype"
(WW) Warning, couldn't open module freetype
(II) UnloadModule: "freetype"
(EE) Failed to load module "freetype" (module does not exist, 0)
(II) LoadModule: "dri"
(II) Loading /usr/local/lib/X11/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "emgd"
(II) Loading /usr/local/lib/X11/modules//emgd_drv.so
(II) Module emgd: vendor="Intel(R) Corporation"
compiled for 1.6.4.901, module version = 1.5.1816
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "mouse"
(II) Loading /usr/local/lib/X11/modules/input//mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 1.4.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 4.0
(II) LoadModule: "kbd"
(II) Loading /usr/local/lib/X11/modules/input//kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 1.3.2
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 4.0
(II) EMGD: Intel(R) Embedded Media and Graphics Driver version 1.5.1816 for:
Intel US15W Class
(II) Primary Device is: PCI 00@00:02:0
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(==) EMGD(0): RGB weight 888
(==) EMGD(0): Default visual is TrueColor
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)


[tinypoodle]

Here is intel response:
When we provide EMGD, we have to target specific distributions of Linux because the Linux market is so fractured.  Unfortunately, TinyCore is a distribution that we do NOT directly support. It is not completely bad news as the driver is fairly flexible and is successfully used on unsupported distros all the time. The kernel changes to DRM/GART, and scripts are provided as code that you can adapt.  The bigger thing is to be sure to MATCH the X version supported by a particular EMGD release as that generally cannot be adapted.

For example, the currently available release of EMGD (1.5.2) supportes MeeGo 1.0 kernel 2.6.33 with X 1.8.0 and Fedora 11 kernel 2.6.29 with X 1.6.  The kernel close matches the version of yours but the X server is a problem.  You would need to either backrev to 1.6 or upgrade to 1.8.

I believe a bigger problem is the TinyKernel which I've heard is really different from the mainline kernel (but eh DRM support may be able to be adapted).  Also, the Debian Squeeze X is also likely changed from mainline X so that could be even a bigger isse.

If you want accelerated vide/3D, have you considered MeeGo or Fedroa as your distro??

Hope this helps.
-------------------------------------------------------------------------------------------------------------
I will test with X 1.6 ...

may i hope X 1.8 or 1.9 will be soon on the TCL package repository ?

D.

Interesting and something to hold on now, I guess that should have been one of your first steps...

Some observations:
I really had searched in detail all info from Intel about compatibility and even to the degree of bothering with pdf files... Debian is not mentioned anywhere in the slightest, which implies that the left hand doesn't know what the right does...

The answer from intel summons up the whole problematic of closed source proprietary drivers:
1.Either the user restricts himself to a very limited choice of a using a very particular combination of system software which would work with such drivers, because the drivers would not work with most software as it should be - reverse criterium of choice!
2.The user would fiddle around for an unpredictable time hoping such drivers would ever work by chance - notice to which degree the reply from Intel is working with pure speculations.
Debugging is excluded a priori.

[Daniel]

Thanks!!!

I've directly ask to be contacted by Intel, with the correct subject!

I hope to have corresponding information! ( succed )

Daniel.

[Daniel]

I've got one response for Debian Squeeze intel driver use.
Then, i succed to use intel driver on Debian

Thats means emgd driver is running!?!


Daniel.

[Daniel]

i'm understanding more and more

i extract emgd.ko and do command "insmod emgd.ko"

responses :
emgd: unknown symbol drm_helper_mode_fill_fb_struct
emgd: unknown symbol drm_crtc_helper_set_config

Not succed

What have i to do ? (gutmensch ? )

Thanks
Daniel.

[Daniel]

I've adapt the intel script for TCL install (and compilation).

when i do the insmod, i've got :
results : emgd: unknown symbols:

drm_framebuffer_cleanup
drm_open
drm_fasync
drm_poll
drm_mode_crtc_set_gamma_size
drm_core_get_reg_ofs
drm_mode_config_init
drm_crtc_init
drm_exit
drm_core_get_map_ofs
drm_init
drm_helper_mode_fill_fb_struct
drm_mmap
drm_crtc_helper_set_config
drm_core_reclaim_buffers
drm_release

intel thread response:
Well it means either the TinyCore has removed the DRM interface (critical for us to interface to the kernel), OR it has seriously changed the DRM interface.  Because we have no experience with this distribution (not POR for us), we just have no wayt to help you with it.  Maybe others here on the community have some experience that they can provide.  BTW: This is why we provide the source for the DRM interface- so you can adapt it to distributions that we are not going to support.

2 symbols are in gutmensch emgd.ko.

what can i do ? or have i a possibility to do it runs ?

Now, I have only 2 days to make it runs, or tcl will be aborted

Thanks
Daniel.

[gutmensch]

Well, we finally have too much problems here:

1. I cannot test the emgd/iegd/intel closed source stuff personally with any hardware.

2. I can only compile the kernel mod drm source, which Intel provides (but you can do it yourself too, of course - there was nothing more needed than just configure and make) and I did that.

3. I don't like beta-testing and working around closed source crap. If Intel doesn't provide a generic Linux driver, then we may have to face the message: Use meego or die.

4. No offense meant, but you seem to lack very basic understanding. TC didn't remove the DRM interface (you will always need the graphics-2.6.33.3-tinycore, which I told you at least a dozen times). You repeatedly try to convince someone that you have some "source" for "drivers", which just aren't there, so you don't seem to understand the whole Intel driver issue here nor do you read the posts and hints from the people, who try to help you. I really suggest you use debian with the intel stuff if it is working somehow, because I think you need some training first to get the real basics right, which would help you to resolve the problems in tinycore. The best thing would be to start reading posts and messages and to understand them. Then ask questions.

It's a lot of work to get this crappy closed source thing to work and you definitely need some skills to do that, if you don't want to eat the lunch that Intel serves you (meaning: Using approp. meego or other OS').

[tinypoodle]

No Free lunch there!   

[Daniel]

Thanks gutmensch!

I have many work to do, and this is only one of them.
I'm learning Linux day after day ... since last year.


1. i've post a proposal:

« Reply #43 on: March 21, 2011, 10:11:54 AM »
I can send one machine (if 24V alim disposable for panel) ... if somebody wants to work on the intel driver integration ... Grin
Smiley
Daniel.
PS : i am in France (Valence 26000).

2. I did to. and i will have a look, if i don't forget anything.


3. Agree (Meego or Debian Squeeze ...)


4. I've just post Intel response.
Even if i make an error, i'm not so stupid thinking they are right!
With other test (graphics-2.6.33.3-tinycore presence control), i will have others results !?! to post to Intel.

I do test you tell me. every conditions.
When i try to insmod YOUR emgd.ko in GOOD configuration :
posted

emgd: unknown symbol drm_helper_mode_fill_fb_struct
emgd: unknown symbol drm_crtc_helper_set_config

I do test with Debian Squeeze ok :

I've got one response for Debian Squeeze intel driver use.
Then, i succed to use intel driver on Debian

Thats means emgd driver is running!?!

Daniel.

Knowledge, specifics technical english words ... make understanding problems.
Universal problem between men!

I accept to be on error, but i try to correct and beeing better.
Suppose me to don't be 'so basic' 

Daniel.

[gutmensch]

The symbols which are reported as missing are inside the module drm_kms_helper.ko.

depmod creates a correct modules.dep for emgd.ko, the dependencies are:

drm.ko.gz (from graphics-2.6.33.3-tinycore.tcz)
drm_kms_helper.ko.gz (from graphics-2.6.33.3-tinycore.tcz)
agpgart.ko.gz (from graphics-2.6.33.3-tinycore.tcz)
i2c-core.ko.gz (from i2c-2.6.33.3-tinycore.tcz)

iegd-emgd-2.6.33.3-tinycore from the repo depends on graphics-2.6.33.3-tinycore, and that depends on i2c-2.6.33.3-tinycore. So first of all: All modules and symbols in place. I can put iegd-emgd-2.6.33.3-tinycore.tcz to onboot.lst and run

Code: [Select]

$ sudo modprobe emgd

The emgd module is loaded (lsmod), the drm stuff, agpgart and i2c too. So I really don't know what's wrong with your setup.

Verify your setup by trying:

Code: [Select]

$ sudo modprobe drm-kms-helper


[Daniel]

One backup ...

sudo modprobe drm-kms-helper -->[drm] Initialized drm 1.10.20060810

I've done correctly test with intel install script (graphics-2.6.33.3-tinycore is here). But certainly not complete!

Doing the same test with Xorg.0.log and messages files results, and compiling using intel install script:
- i have to put lib files in /usr/lib directory  (i don't know why??? And they are also in /usr/local/lib/ !!! )

Same blocked result!
More logs:)
Here are Xorg.0.log and messages files http://dl.free.fr/mh6thDBUN

I will do the same test tomorrow with eGalax driver!!!
May it be now the cause?

Thanks
Daniel.

[gutmensch]

both log files look good, so I'm not able to tell you what's going wrong...

[Daniel]

Yes, you confirm me what i was thinking! Thanks!

WithTouchscreen configured , i have exactly same result

I have now 2 screen flash before having upper left cursor blocked, without any possibility doing anything

Can i have more log trace ?
Perhaps launching X in debug mode ? (if it is possible)

Daniel.

[Daniel]

I saw yesterday an Intel industrial man

Normaly, i will soon be in contact with one Linux intel expert. (I will send him material!)


Hope he will find why X is blocked ... and a solution 

i will give informations!

Thanks for all!
Daniel.