Hi Jesse > > 2- I cloned the git/drm tree using branch modesetting-101 > > Compilation was fine, intel_fb loads and the drm/framebuffer appears in > > /proc/fb but I have some troubles / remarks > > Yeah, (2) is the right thing to do. The patches are out of date.
Ok thank you, I have checked out the last release yesterday to make some new tests > > Hm, so it just defaults to 640x480... you'd have to add some debugging code > to the i2c code that fetches the EDID data to see what's going on. I may > just be that the timing is off somewhere, just enough to prevent the kernel > from receiving the EDID block. I haven't done it yet, but I'll try to do some debugging soon > > Second, when the mode "640x480" is set the screen does not display anything > > good. I only get some black screen which is sometime replace with coloured > > snow (I don't know how to explain it better...). > > If I try mplayer -vo fbdev(2), I'm only able to get a black screen > > > > So, here are my questions : > > > > - Are you still working on this drm/fb (modesetting) ? > > Yes, though I haven't checked anything in for a few weeks. I hope to be back > on it shortly (have a few other features to get working first). Great to hear that ! > > - Is there a place where I can find a full procedure to make reliable > > tests ? > > - Are you interested in feedbacks ? (do you want me to make some specific > > tests, do you want access to my computer, ...) > > - ... > > Yes, definitely. It's great that there's interest in the tree, and we're > interested in hearing about problems or different usage models for the code, > but keep in mind that it's *very* bleeding edge, so when it breaks you get to > keep both pieces. :) No problem about "bleeding edge" code. I know the difference between stable code and very experimental code ;-) Anyway, I tried the last release of the modsetting-101 branch yesterday night and I wasn't able to make it work : - I compiled the code (everything was fine) - I inserted the drm module Jul 2 21:10:56 coreduo [drm] Initialized drm 1.1.0 20060810 - I inserted the i915 module Jul 2 21:11:10 coreduo ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 16 Jul 2 21:11:10 coreduo PCI: Setting latency timer of device 0000:00:02.0 to 64 Jul 2 21:11:10 coreduo i2c_adapter i2c-3: unable to read EDID block. Jul 2 21:11:10 coreduo i2c_adapter i2c-3: unable to read EDID block. Jul 2 21:11:10 coreduo i2c_adapter i2c-3: unable to read EDID block. Jul 2 21:11:10 coreduo i915 0000:00:02.0: LVDS: no EDID data Jul 2 21:11:11 coreduo i2c_adapter i2c-3: sendbytes: error - bailout. Jul 2 21:11:11 coreduo i2c_adapter i2c-3: unable to read EDID block. Jul 2 21:11:11 coreduo i915 0000:00:02.0: TMDS-1: no EDID data Jul 2 21:11:11 coreduo allocated 640x480 fb: 0x00020000, bo f611c6c0 Jul 2 21:11:11 coreduo fb0: intelfb frame buffer device Jul 2 21:11:11 coreduo [drm] Initialized i915 1.9.0 20070209 on minor 0 Driver insertion seems fine except I still got the EDID trouble (I'll try to do some debug) When the driver is loaded, I get a blue screen on my hdmi/Plasma TV set showing the message "No signal" (that was not the case with previous release) If I try to remove the module i915 from the kernel, I get a big error : Jul 2 21:11:24 coreduo ACPI: PCI interrupt for device 0000:00:02.0 disabled Jul 2 21:11:24 coreduo BUG: unable to handle kernel paging request at virtual address f8d82080 Jul 2 21:11:24 coreduo printing eip: Jul 2 21:11:24 coreduo f8d0e8a3 Jul 2 21:11:24 coreduo *pde = 37853067 Jul 2 21:11:24 coreduo *pte = 00000000 Jul 2 21:11:24 coreduo Oops: 0002 [#1] Jul 2 21:11:24 coreduo SMP Jul 2 21:11:24 coreduo Modules linked in: i915 drm snd_pcm_oss snd_mixer_oss snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device tun thermal processor fan eth1394 ftdi_sio usbserial lirc_igorplugusb(F) lirc_dev ves1820 ohci1394 dvb_ttpci dvb_core saa7146_vv video_buf saa7146 videodev v4l2_common v4l1_compat tt pci_eeprom ieee1394 rtc_cmos rtc_core rtc_lib evdev pcspkr ehci_hcd uhci_hcd usbcore snd_hda_intel snd_hda_codec snd_pcm snd_timer snd soundcore snd_page_all oc Jul 2 21:11:24 coreduo CPU: 1 Jul 2 21:11:24 coreduo EIP: 0060:[<f8d0e8a3>] Tainted: GF VLI Jul 2 21:11:24 coreduo EFLAGS: 00010282 (2.6.21-gentoo-r3-coreduo-nofb #5) Jul 2 21:11:24 coreduo EIP is at i915_driver_unload+0x48/0x185 [i915] Jul 2 21:11:24 coreduo eax: f8d80000 ebx: ef0b6800 ecx: c17ff080 edx: c16bb860 Jul 2 21:11:24 coreduo esi: f00a8000 edi: ef0b6800 ebp: f8d16604 esp: ef381eb8 Jul 2 21:11:24 coreduo ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068 Jul 2 21:11:24 coreduo Process rmmod (pid: 20192, ti=ef380000 task=f7d5a030 task.ti=ef380000) Jul 2 21:11:24 coreduo Stack: ef0b6944 ef0b6818 f8d165a8 f8d16604 ef0b6800 f8d165a8 f8d165a8 f8d241f0 Jul 2 21:11:24 coreduo f8d165a8 f8d165a8 f8d243e0 f7f97000 c02467d7 f7f97048 c02917bd f7f97048 Jul 2 21:11:24 coreduo f7f88200 c0291cca f8d16600 f8d165a8 f8d165a8 c0400b40 ef380000 c02913d8 Jul 2 21:11:24 coreduo Call Trace: Jul 2 21:11:24 coreduo [<f8d241f0>] drm_cleanup+0x7a/0x19b [drm] Jul 2 21:11:24 coreduo [<f8d243e0>] drm_cleanup_pci+0x16/0x24 [drm] Jul 2 21:11:24 coreduo [<c02467d7>] pci_device_remove+0x16/0x36 Jul 2 21:11:24 coreduo [<c02917bd>] __device_release_driver+0x64/0x8d Jul 2 21:11:24 coreduo [<c0291cca>] driver_detach+0xc3/0xc9 Jul 2 21:11:24 coreduo [<c02913d8>] bus_remove_driver+0x63/0x81 Jul 2 21:11:24 coreduo [<c0291cf1>] driver_unregister+0x8/0x1d Jul 2 21:11:24 coreduo [<c0246931>] pci_unregister_driver+0xe/0x67 Jul 2 21:11:24 coreduo [<f8d243c8>] drm_exit+0xb7/0xb9 [drm] Jul 2 21:11:24 coreduo [<c01367cb>] sys_delete_module+0x138/0x19a Jul 2 21:11:24 coreduo [<c01493f5>] remove_vma+0x36/0x3b Jul 2 21:11:24 coreduo [<c0149e3f>] do_munmap+0x16e/0x1c3 Jul 2 21:11:24 coreduo [<c0102702>] sysenter_past_esp+0x5f/0x85 Jul 2 21:11:24 coreduo [<c0350000>] xfrm_state_add+0x13/0x1d0 Jul 2 21:11:24 coreduo ======================= Jul 2 21:11:24 coreduo Code: 01 00 8b 56 50 85 d2 74 2c 89 f8 e8 33 a8 01 00 c7 46 50 00 00 00 00 c7 46 54 00 00 00 00 c7 46 58 00 00 00 00 8b 46 08 8b 40 1 0 <c7> 80 80 20 00 00 00 f0 ff 1f 8b 46 60 85 c0 0f 85 f3 00 00 00 Jul 2 21:11:24 coreduo EIP: [<f8d0e8a3>] i915_driver_unload+0x48/0x185 [i915] SS:ESP 0068:ef381eb8 If I do a "shutdown -r now", the whole system seems to freeze (I'm ssh'ing it because I dont have anything displayed on the console since I inserted the i915 module) Here is the log (after the shutdown -r now) Jul 2 21:12:04 coreduo shutdown[1642]: shutting down for system reboot Jul 2 21:12:04 coreduo init: Switching to runlevel: 6 I cannot get more information... from the system logs So here are some questions : 1. If I compile the source code, do I need to install libdrm.so/la before doing the insmod 2. Is there a way to force the driver to keep the display on TMDS-1 ? Thank you Philippe ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
