Tiny Core Linux
Tiny Core Extensions => TCE Talk => Topic started by: Daniel on March 10, 2011, 04:53:49 AM
-
My configuration:
Board : intel Atom Z510 1.1 Ghz + US15W (menlow)
Screen 800x600x24bits on LVDS port
512Mo DDR2
4Go Nand Flash (on USB).
I've got the Fedora11 and Meego1 drivers : X1.6.4 or 1.7.99.
With xorg.conf configuration (joined).
Using install (original joined) scripts (adapted for TCL), with both drivers (and updated xorg.conf) X doesn't start
(screen not found : Xorg.0.log)
I've got souces (see install.zip for script) ... but with adapted script to TCL, i've got tar errors (make directory) ... and the make cmd fail!
1: is the xorg.conf update ok for TCL ?
2: what is this tar error ? (sure, with error, i can't do make)
3: i've got the intel sources, but 32Mb. if somebody want have a look, i can put it on an ftp server.
4: if any information is missing, please ask me!
Thanks
Daniel.
PS: i can't join files ... i will try again after post : Impossible.
Administrators contacted.
-
It seems this US15W is an PowerVR chip, licensed by Intel as GMA 500. Following these instructions http://www.nanoant.com/linux/compiling-kernel-iegd-10x-module-for-any-linux-distribution (http://www.nanoant.com/linux/compiling-kernel-iegd-10x-module-for-any-linux-distribution) the biggest problem is the kernel module. An install script will not work because you have to build this one yourself ;-) Binaries/sources for the intel IEGD driver are available here http://edc.intel.com/Software/Downloads/IEGD/Default.aspx?id=1013 (http://edc.intel.com/Software/Downloads/IEGD/Default.aspx?id=1013) in version 10.4. However... no guarantee it will work at all. I'll take a look at the kernel module.
[edit]
Intel "source" only contains precompiled binary drivers for Xorg xserver 1.6.4, which makes it incompatible to Xorg-7.5 with xserver 1.7.7. I read some people are backporting xserver 1.6 to Xorg-7.5 to be able to use the binaries. Kernel module iegd_mod.ko compiles and can be added to graphics-2.6.33.3-tinycore...
[/edit]
-
Thanks!
I will look to your links!
I've put accessible drivers and configuration ... follow links :
http://dl.free.fr/rUyX9Gkm6 (http://dl.free.fr/rUyX9Gkm6) for install (in driver package)
http://dl.free.fr/r3WstfjHf (http://dl.free.fr/r3WstfjHf) full driver package (with sources)
http://dl.free.fr/d4tfLU2PD (http://dl.free.fr/d4tfLU2PD) X log
Daniel.
-
If all you need is 800x600x24 then it might be possible that Xfbdev could work directly - without any need of 915resolution and/or uvesafb, under the condition that you can get that mode at boot time.
-
FWIW I uploaded an iegd-emgd-2.6.33.3-tinycore.tcz extension, which contains modules for Intel embedded chips: iegd_mod.ko and emgd.ko. For accelerated graphics and some binary form Xorg driver from Intel you will at least need this extension. If the binaries from Intel are working with either Xorg-7.4 (1.6) or Xorg-7.5 (1.7) from our repository I'm not able to say.
-
KO test with iegd-emgd-2.6.33.3-tinycore.tcz + Xorg7.5.tcz and intel drivers compiled for X 1.7.3.
Here are dmesg and Xorg.0.log with intel xorg.conf configuration
http://dl.free.fr/aY0oi5CmR (http://dl.free.fr/aY0oi5CmR)
And xorg.conf custom
##
## X Config options generated from CED
## x11 conf skeleton
## DriverVer=
##
Section "Screen"
Identifier "Screen0"
Device "IntelEMGD-0"
Monitor "Monitor0"
SubSection "Display"
EndSubSection
EndSection
# Primary (First/only) display
Section "Device"
Identifier "IntelEMGD-0"
Driver "emgd"
VendorName "Intel(R) DEG"
BoardName "Embedded Graphics"
BusID "0:2:0"
Screen 0
Option "PcfVersion" "1792"
Option "ConfigId" "1"
Option "ALL/1/name" "PPC10p4_EMGD_LPG"
Option "ALL/1/General/PortOrder" "40000"
Option "ALL/1/General/DisplayConfig" "1"
Option "ALL/1/General/DisplayDetect" "0"
Option "ALL/1/Port/4/General/name" "PORT_LVDS"
Option "ALL/1/Port/4/General/EdidAvail" "3"
Option "ALL/1/Port/4/General/EdidNotAvail" "1"
Option "ALL/1/Port/4/General/Rotation" "0"
Option "ALL/1/Port/4/General/Edid" "1"
Option "ALL/1/Port/4/FpInfo/BkltMethod" "0"
Option "ALL/1/Port/4/Attr/26" "24"
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
# InputDevice "Mouse0" "CorePointer"
# InputDevice "Keyboard0" "CoreKeyboard"
# InputDevice "DevInputMice" "SendCoreEvents"
EndSection
Thanks
Daniel.
-
The emgd extension should depend on the graphics- one, it seems.
-
What does that means ?
What have i to do to have a correct configured xorg.conf ?
Or does i need correct drivers ?
thanks
Daniel.
-
This graphic card is on 4000 installed machines (ubuntu 8.04) !
We have planed when it run's to update them with TCL.
And others 300 (actual park) machines ... (actually under ubuntu 10.04).
The production is continuing. (around 1000 per year).
:)
Daniel.
-
Until the dep file is fixed, load the graphics-2.6.33.3-tinycore.tcz extension also.
-
next test:
kernel command line : ... vga=789 text consoleblank=0
in order to start X manualy (because of black screen with no action possible : (with xorg.conf.vesa copied on xorg.conf)).
Here is the dmesg results
http://dl.free.fr/p5GnT1hKh (http://dl.free.fr/p5GnT1hKh)
Daniel.
-
dep file fixed - like curaga suggested you also need graphics-2.6.33.3-tinycore.tcz extension (not either this one or iegd-emgd, you need both).
then try this one again:
iegd-emgd-2.6.33.3-tinycore.tcz + Xorg7.5.tcz and intel drivers compiled for X 1.7.3 ( + graphics-2.6.33.3-tinycore)
it looks quite good he just can't load the emgd kernel module because of the missing drm modules from graphics-2.6.33.3-tinycore!
-
I've done test with this configuration yesterday.
But i have black screen locked, with no possibility to go to console debug :(
I can't have a look to xorg.0.log :(
Have i to modify xorg.conf ?
Daniel.
-
I've generated a new intel driver : full generation is here http://dl.free.fr/getfile.pl?file=/kpUZo5Sa (http://dl.free.fr/getfile.pl?file=/kpUZo5Sa)
In this file, for xorg 1.7.3, there is an install script. But is it ok for TCL ?
With iedg-emgd ... + Xorg7.5 + graphics- ... and the intel EMGD driver, i've got same results:
locked black screen! :(
How can i get xorg.0.log without terminal ?
Can this file generated on a fixed media ?
or ?
thanks
Daniel.
-
you should start an sshd server on the client and tail Xorg.0.log from another pc when starting X, this way Xorg will still hang up but you will have output. you can also debug X over ssh with the use of gdb ;-)
-
It couldn't harm to add to your xorg.conf the following:
Section "ServerFlags"
Option "DontZap" "false"
EndSectionso the option to kill X with Ctrl+Alt+BkSp would be present.
Also you could try to add the bootcode 'multivt', to have a remote chance to still being able to switch to a free VT.
-
I'm starting to desesperate :(
I do test with new tce backup directory!
iegd-emgd + xorg7.5 + graphics ...
emgd_drv* copied in /usr/local/lib/X11/modules/drivers/
emgd_dri.so copied in /usr/local/lib/X11/modules/dri/
lib* copied if /usr/local/lib/
multvt and ServerFlags updated.
==> i have always locked black screen (no multivt or Ctrl+Alt+Backspace possible action).
In that configuration, i replace in xorg.conf "vesa" by "emgd" in section Device -> Driver
with /usr/local/lib/X11/modules/drivers/emgd_drv.so, i've got "cannot open shared object libpvr2d.so" error.
is it helping ?
I will now try gutmensch sshd server command ...
Thanks
Daniel.
-
It looks like there is loading driver problem!
But i'm not a specialist :(
I've got 1.7.3 X driver, used with X 1.7.7 ...
Is it possible to have X 1.9 ? (i've got X 1.9 drivers).
would it be better ?
Thanks,
Daniel.
-
when i replace in xorg.conf "vesa" by "emgd" in section Device -> Driver
with /usr/local/lib/X11/modules/drivers/emgd_drv.so, i've got "cannot open shared object libpvr2d.so" error.
I put it on /usr/lib (with others libs) and i've got same results : completely blocked (no keyboard led on-off when num led key pressed, no debug console, no X kill ... ) ...
My conclusion : driver incompatibility. Comming from Intel drivers ? ???
I will have a new look to the intel driver generation tool. But it was carrefully done!
Daniel.
-
I've got the Xorg.0.log :D
I've just mount /var/log/ on a device!!! :)
Here it is:
X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.33.3-tinycore i686
Current Operating System: Linux box 2.6.33.3-tinycore #2012 SMP Wed May 12 17:05:42 EEST 2010 i686
Kernel command line: boot=/ initrd=/tinycore.gz quiet BOOT_IMAGE=/bzImage
Build Date: 28 May 2010 06:50:29PM
Current version of pixman: 0.18.4
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: Mon Mar 14 09:14:04 2011
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "X.org Configured"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "IntelEMGD-0"
(**) |-->Input Device "EETI"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(==) 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/
(**) ModulePath set to "/usr/local/lib/X11/modules"
(II) Loader magic: 0x819471c
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 6.0
X.Org XInput driver : 7.0
X.Org Server Extension : 2.0
(--) using VT number 2
(--) PCI:*(0:0:2:0) 8086:8108:8086:8119 rev 7, Mem @ 0xb0080000/524288, 0xc0000000/268435456, 0xb0000000/262144, I/O @ 0x00001800/8
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(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. This was enabled by default and also specified in the config file.
(II) "dri2" 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.7.7, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "dri"
(II) Loading /usr/local/lib/X11/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.7.7, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "extmod"
(II) Loading /usr/local/lib/X11/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.7.7, 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.7.7, 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: "dri2"
(II) Loading /usr/local/lib/X11/modules/extensions/libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
compiled for 1.7.7, module version = 1.1.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "emgd"
(II) Loading /usr/local/lib/X11/modules/drivers/emgd_drv.so
(II) Module emgd: vendor="Intel(R) Corporation"
compiled for 1.7.3, module version = 1.5.1816
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 6.0
(II) LoadModule: "egalax"
(II) Loading /usr/local/lib/X11/modules/input/egalax_drv.so
(II) Module egalax: vendor="X.Org Foundation"
compiled for 1.7.0, module version = 3.4.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 7.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.7.7, module version = 1.5.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 7.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.7.7, module version = 1.4.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 7.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
(==) EMGD(0): RGB weight 888
(==) EMGD(0): Default visual is TrueColor
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
[drm] failed to load kernel module "emgd"
(II) EMGD(0): Graphics hardware initialization failed.
(II) EMGD(0): The cause was a failure to connect with the DRM during PreInit().
(II) EMGD(0): Cannot open a connection with the DRM
(II) UnloadModule: "emgd"
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found
Please consult the TinyCore Linux support
at www.tinycorelinux.com
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
I will do others tests : in this, i have emgd configuration (replacing vesa).
Daniel.
-
Here is new tst results : http://dl.free.fr/oIc5EzwHc (http://dl.free.fr/oIc5EzwHc)
the lasts lines of Xorg.0.log with Intel configured xorg.conf
(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
(==) EMGD(0): RGB weight 888
(==) EMGD(0): Default visual is TrueColor
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
After that, le machine is blocked!
What is the next not written operation ?
[Edit] i see : drmOpenByBusid: (founded on other Xorg.0.log).
But ...what is the stop loading problem ???
Thanks
Daniel.
-
A simple question :
Where drivers files have to be copied ?
I have an installer ... but not for TCL.
And some files have to be copied to specifics places.
Perhaps X loading is stopped due to missing lib ?
I accept any help!
thanks
Daniel.
-
As i said before, i've got last Intel driver generator!
I know (with an hardware man) what i have to do to set corresponding material parameters.
But is there any specific software - kernel - mod ... etc ... parameters to set to be compliant with TCL ?
Or to do a generic emgd configuration driver?
Thanks
Daniel.
-
I accept any help!
Or so you say... but I never noted you responding to Reply #3 :-\
-
I've got the Xorg.0.log :D
I've just mount /var/log/ on a device!!! :)
Here it is:
That would imply that you should also be able to catch /var/log/messages (when having syslogd running) which might be of more interest, as at least I could not see anything from Xorg.0.log which would justify a lockup.
-
you can try other things:
1. disable dri and dri2 altogether in xorg.conf (see if your emgd_drv works at all, might be a problem of the emgd.ko kernel module)
2. the emgd kernel module is included in your intel emgd packages in a file called emgd_drm.tgz (or something like that), you should of course compile it for the driver you're using (I didn't have the intel xorg 1.7.3 "sources", just found some for 1.6.4 and 1.5.3). I can update the iegd-emgd extension to include the module from your special version, but I would need a link to them first...
3. as already stated by tinypoodle, start your tinycore with the boot codes "syslog debug" to enable verbose logging to /var/log/messages
-
If all you need is 800x600x24 then it might be possible that Xfbdev could work directly - without any need of 915resolution and/or uvesafb, under the condition that you can get that mode at boot time.
I miss (having a better look and) a response of your message :( sorry!
I have vga=789 on kernel command line : 800x600x24 ok!
I don't use 915resolution.
I 've never hear about uvesafb before ...
About Xfbdev :
I'am not using Xvesa because i need to use openJdk (HeadFull) and I want to replace ubuntu 8.04 and 10.04 by TCL!
But, if Xfbdev makes my application running (with no problem for OpenJDK...) as fast as the actual ubuntu (i've got actually 2 application : one under ubuntu 8.04, and an other unde ubuntu 10.04), why not!
if my application can run better with Xfbdev than under X, it will be used!
I will make the test and tell results!
Thanks,
Daniel.
-
tinypoodle, i've test with Xfbdev.
It is running!! :)
With performances! :D
BUT ... i need TouchScreen!
And actually, i don't know if i can install eGalax Driver! blocking problem ! :(
It was a compatibity problem with Xvesa and a major reason of using X!
And i've loosed my french keyboard configuration (minor problem)
Thanks,
Daniel.
-
you can try other things:
1. disable dri and dri2 altogether in xorg.conf (see if your emgd_drv works at all, might be a problem of the emgd.ko kernel module)
2. the emgd kernel module is included in your intel emgd packages in a file called emgd_drm.tgz (or something like that), you should of course compile it for the driver you're using (I didn't have the intel xorg 1.7.3 "sources", just found some for 1.6.4 and 1.5.3). I can update the iegd-emgd extension to include the module from your special version, but I would need a link to them first...
3. as already stated by tinypoodle, start your tinycore with the boot codes "syslog debug" to enable verbose logging to /var/log/messages
Results 1: (with 3)
Disabling dri and dri2 : i've comment load "dri" in section "Module" : is it ok ?
Here are results : http://dl.free.fr/vZDHIXqkS (http://dl.free.fr/vZDHIXqkS)
X not started :(
Point 2 : is there any driver sources in the link http://dl.free.fr/getfile.pl?file=/kpUZo5Sa (http://dl.free.fr/getfile.pl?file=/kpUZo5Sa)
last intel driver files generated ... in the \IEMGD_HEAD_Linux\DebianSqueeze\ directory ?
If not, i will ask sources to Intel!
Daniel.
-
Not sure where you see a relation between OpenJDK and X server, I have used OpenJDK more recently and sun's java back when it was proprietary over many years with plenty of different versions of Xvesa without the slightest issue.
Xfbdev and Xvesa are X server implementations as much as X.org (and various others).
-
Yes, my java application runs ok with Xfbdev!
But touchDriver install.sh needs X!
I think, install stript need to be converted (or i have to do manual copy, before make an extension).
Have a look to it if you want : http://home.eeti.com.tw/web20/eGalaxTouchDriver/linuxDriver.htm (http://home.eeti.com.tw/web20/eGalaxTouchDriver/linuxDriver.htm)
==> depending of X version, a driver is selected : what is X version for Xfbdev ? 1.7 ?
How is managed mouse ? mousse_drv ... ?
Actually, the standalone flashplayer 10.02 under Xfbdev ... with flash10.tcz. Not without! (missing libgtk-x11-2.so...)
With X, the 10.02 flashplayer is launched with flash10.tcz installed, but block screen !!! :(
The TCL firefox was running (launchin application.swf), but i need to put my firefox in a directory, with 10.02
flash plugins.
Here is some problems i have to resolve before choosing TCL :(
Or succed to configure X with intel drivers ...
Thanks for all
Daniel.
-
Did you load input-tablet-touchscreen-2.6.33.3-tinycore.tcz and verify that module 'usbtouchscreen' is loaded?
-
no :(
because of my ubuntu experiences ... and incomptibility problems with eGalax!
and i didn't know this .tcz
but that is the first thing i will try on monday! :)
perhaps eeti - eGalax are included ... or compatible in that package :)
thanks
Daniel
-
The poulsbo chip really is horrible. Looks rather good for Intel when the binary driver even hangs your machine.
Since you got good performance in Xfbdev, you can just use Xorg with its fbdev module instead of Intel's binary drivers.
Use the vga=xxx bootcode, and select fbdev as the driver in xorg.conf. This way you can use your egalax driver too.
-
i will try that too!
performances are pretty good ... but not as good as ubuntu 8.04 with iegd driver.
i've got others problems with ubuntu on this machine.
between performances and problems resolution, a choice will be done ... if i can't have performances as good as with ubuntu.
Daniel.
-
no :(
because of my ubuntu experiences ... and incomptibility problems with eGalax!
and i didn't know this .tcz
but that is the first thing i will try on monday! :)
perhaps eeti - eGalax are included ... or compatible in that package :)
thanks
Daniel
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/release/src/kernel/config-2.6.33.3-tinycore
CONFIG_TOUCHSCREEN_USB_COMPOSITE=m
CONFIG_TOUCHSCREEN_USB_EGALAX=y
-
I've installed input-tablet-touchscreen-2.6.33.3-tinycore.tcz with Xvesa.
How can i calibrate ?
i will have a look to that problem!
Thanks
Daniel.
-
I don't find any information to calibrate my usbtouchscreen :( after installing input-tablet-touchscreen-2.6.33.3-tinycore.tcz).
I will try now with Xfbdev ...
I know how to configure with X (by saving files after driver install with eGalax setup.sh).
Daniel.
PS: Xvesa could replace Xfbdev if i have touchscreen, but with my configuration, performances are better with Xfbdev.
I will try X with fbdev param (test performances ... and eeti touchscreen driver if necessary).
-
You can only use the calibration data with Xorg.
http://linux.chapter7.ch/touchkit/calibrator.c
-
That means i can't have touchscreen with Xvesa and Xfbvdev ? :(
D.
-
Yes, but uncalibrated, I believe. Not sure though.
-
With input-tablet-touchscreen-2.6.33.3-tinycore.tcz i thought it was possible ... for Xvesa or Xfbdev :(
What i know is that the touchscreen is managed like a mouse ... but only click is used (where the mouse pointer is).
I spoke about eGalax driver on a TCL thread : driver install-configuration. http://forum.tinycorelinux.net/index.php?topic=8528.15 (http://forum.tinycorelinux.net/index.php?topic=8528.15)
But X is needed!
Now, my solution is : X
- with intel US15W drivers
- with fbdev configuration.
Actually, i've got problems with intel driver!
I don't know what i have to do after all my tests :(
I'm preparing fbdev configuration tests.
Xfbdev is better than Xvesa (for my configuration).
But the actual ubuntu 8.04 with intel iegd driver is better than Xfbdev! (my test application tell 2 times better).
I was expecting kernel 2.6.33 is better than 2.6.24 ...
Missing "only" intel drivers usage to know!
Daniel.
-
X with fbdev configuration (and eGalax touch configured)
Performances are not here :(
My application test is a carrousel rotation of 6 pictures. (done in flash, with ip java communication : huge graphical test part).
With ubuntu 8.04 (iegd intel driver) : less than 2s.
With Xfbdev : around 3.15s
With Xvesa : around 3.6s
With X - fbdev : more than 4s :(
Missing X with emgd intel driver (normally better than iegd driver).
Daniel.
-
I can send one machine (if 24V alim disposable for panel) ... if somebody wants to work on the intel driver integration ... ;D
:)
Daniel.
PS : i am in France (Valence 26000).
-
It's a binary driver, nobody but Intel can do anything about it not working.
-
I'm not a driver specialist ... but it was thinking soures are here (in the emgd_drm.tar) : http://dl.free.fr/kavJVQXwf (http://dl.free.fr/kavJVQXwf)
Couldn't it be a configuration problem ?
Thanks
Daniel.
-
Those are only the kernel & config ui sources, the Xorg driver is binary only.
If it hangs your machine, it's very likely not a config problem :P
-
That means i can't have touchscreen with Xvesa and Xfbvdev ? :(
D.
http://www.nico.schottelius.org/software/gpm/browse_source/gpm-1.99.6/doc/README.evabs
If gpm works in repeater mode then it might be possible to use it under any X server.
-
I will test tomorrow driver with corresponding DebianSqueeze!
and i will ask directly to "Mister Intel" the corresponding driver for tcl X and kernel ! :)
If i don't ask, i won't have any possibility to have it! ;)
thanks
Daniel.
-
I will not continue now testing touch install with Xvesa and Xfbdev because of graphical performances :(
My only chance is with intel drivers!
Gutmensch said to me where to put files, not following intel setup.sh.
--> /usr/local/lib/X11/modules/drivers .... for emgd_drv*.so
--> /usr/local/lib/X11/modules/dri/ .... for emgd_dri.so
--> /usr/local/lib ... for others libs (and i think all others files ... like emgd.4.gz)
list of files:
emgd.4.gz
emgd_dri.so
emgd_drv.so
emgd_drv_video.so
install.sh
libEGL.so
libGLESv2.so
libGLES_CM.so
libglslcompiler.so
libIMGegl.so
libOpenVG.so
libOpenVGU.so
libpvr2d.so
libPVROGL.so
libpvrPVR2D_DRIWSEGL.so
libPVRScopeServices.so
libsrv_init.so
libsrv_um.so
libva-x11.so.1.0.1
libva.so.1.0.1
libXegd_escape.a
libXegd_escape.so.2.0.0
powervr.ini
Do i understand and not forgot anything ?
Perhaps the problem is comming from what i do !
If (when) it is ok, and same problem, i will test with 1.7.99 intel driver ... if it is not 'stupid' :)
thanks
Daniel.
-
I've install Debian Squeeze. (X1.7.7)
Stop gdm
install intel emgd driver (with install.sh from intel package for Debian Squeeze)
set xorg.conf (intel emgd params)
Start gdm
X 1.7.7 doesn't start!!! (emgd not found).
It is not normal ! :(
I have an Intel Contact ...
tbc ...
Daniel.
-
What do you think about that ? :)
http://intellinuxgraphics.org/download.html
http://intellinuxgraphics.org/build.html
Daniel.
-
Intel's proper open source drivers only work on real Intel hardware. The poulsbo is crappy PowerVR hardware with an Intel badge on it, with only binary drivers.
-
:( :'(
I've got a Privileged intel Access!
I ask questions on Intel community threads ...
I'm waiting ...
I think until Debian squeeze (same computer: i can have a few of them) do not use the driver ... it probably not work on TCL :(
Thanks,
Daniel.
-
Debian is as unsopported by the non-free driver as TC is :P
-
But Intel provide the debian squeeze driver in his configuration tool (and tool generated drivers packages) ...
-
I could not see any support for Debian whatsoever in the official Intel matrix neither for IEGD nor for EMGD.
-
in the 1.5.2 intel pack (gold), there is the debian squeeze driver for us15w.
==>last gold intel tool generates that http://dl.free.fr/getfile.pl?file=/kpUZo5Sa (http://dl.free.fr/getfile.pl?file=/kpUZo5Sa)
-
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.
-
For X 7.5
--> /usr/local/lib/X11/modules/drivers .... for emgd_drv*.so
--> /usr/local/lib/X11/modules/dri/ .... for emgd_dri.so
--> /usr/local/lib ... for others libs (and i think all others files ... like emgd.4.gz)
Same for X 7.4 ?
Thanks
Daniel.
-
Same paths in 7.4.
-
Thanks! :)
Same results with Xorg-7.4!
Bloqued when starting X with no error in "messages" file :(
Xorg.0.log:
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)
-
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.
-
Thanks!!!
I've directly ask to be contacted by Intel, with the correct subject!
I hope to have corresponding information! ( succed ??? )
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.
-
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.
-
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.
-
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').
-
No Free lunch there! :P
-
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' ;D
Daniel.
-
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
$ 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:
$ sudo modprobe drm-kms-helper
-
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 (http://dl.free.fr/mh6thDBUN)
I will do the same test tomorrow with eGalax driver!!!
May it be now the cause?
Thanks :)
Daniel.
-
both log files look good, so I'm not able to tell you what's going wrong...
-
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.
-
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.