Fedora 11 + Lenovo T500 + Avocent Switchview

equals no video on startup... for some reason. It is some combination of all three hardware bits.. not sure exactly what to do about it though. My first set of problems seemed to be BIOS settings. On first connecting the monitor directly to the laptop I got no detection or startup except every few reboots. I then went into the T500's BIOS to assume a VGA out and some other flags. That has gotten it to work directly most of the time.

Going through the Avocent at startup always ends up with no video so I have to plug the monitor in directly and then everything back into the switch to get it to continue to work. I got it to work once through the avocent but got this kernel oops.

[drm:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer
------------[ cut here ]------------
WARNING: at drivers/gpu/drm/i915/i915_gem_tiling.c:473 i915_gem_set_tiling+0x4ba/0x52c [i915]() (Not tainted)
Hardware name: 2241B36
failed to unbind object for tiling switchModules linked in: fuse ipt_MASQUERADE iptable_nat nf_nat rfcomm bridge stp llc bnep sco l2cap sunrpc ip6t_REJECT nf_conntrack_ipv6 ip6table_filter ip6_tables ipv6 cpufreq_ondemand acpi_cpufreq freq_table dm_multipath kvm_intel kvm uinput arc4 snd_hda_codec_conexant ecb snd_hda_intel pcspkr snd_hda_codec iwlagn i2c_i801 firewire_ohci sdhci_pci sdhci joydev ricoh_mmc snd_hwdep uvcvideo mmc_core iwlcore firewire_core snd_pcm ata_generic yenta_socket lib80211 iTCO_wdt rsrc_nonstatic iTCO_vendor_support crc_itu_t mac80211 thinkpad_acpi videodev rfkill hwmon snd_timer v4l1_compat v4l2_compat_ioctl32 snd soundcore wmi snd_page_alloc pata_acpi cfg80211 btusb e1000e bluetooth xts gf128mul cryptd aes_x86_64 aes_generic dm_crypt i915 drm i2c_algo_bit video output i2c_core [last unloaded: microcode]
Pid: 2134, comm: Xorg Not tainted 2.6.30.8-64.fc11.x86_64 #1
Call Trace:
[] warn_slowpath_common+0x95/0xc3
[] warn_slowpath_fmt+0x50/0x66
[] i915_gem_set_tiling+0x4ba/0x52c [i915]
[] ? i915_gem_set_tiling+0x0/0x52c [i915]
[] drm_ioctl+0x21d/0x2e9 [drm]
[] ? avc_has_perm+0x6b/0x91
[] ? do_sync_write+0xfa/0x14b
[] vfs_ioctl+0x7e/0xaa
[] do_vfs_ioctl+0x46c/0x4c3
[] sys_ioctl+0x65/0x9c
[] system_call_fastpath+0x16/0x1b
---[ end trace 152ab49aad65c390 ]---

My guess is that there is something in the kernel driver that is not getting the right signal detection and the X11 code says no monitor is hooked up.. so we aren't able to connect to it via system-config-display or the new X widget tool.

Well on the good news.. I can now get my two test boxes working via the monitor/keyboard so my wires went down.. I just have to play around when I start the laptop up.