[gr4vity]

Hi,
I have older kernel v4.xx on my pc which contains inteldrmfb  frame buffer device

Code: [Select]

:/# dmesg | grep -i frame
[    0.024000] Security Framework initialized
[    0.805597] vesafb: framebuffer at 0xd0000000, mapped to 0x0000000010fb3298, using 5120k, total 5120k
[    0.837432] Console: switching to colour frame buffer device 160x64
[    0.869164] fb0: VESA VGA frame buffer device
[    1.277694] r8169 0000:02:00.0 eth0: jumbo features [frames: 4080 bytes, tx checksumming: ko]
[    1.809437] Console: switching to colour frame buffer device 240x67
[    1.814496] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
However MLD-5.5 testing kernel contains i915drmfb

Code: [Select]

MLD> dmesg | grep -i frame
[    0.229231] LSM: Security Framework initializing
[    2.129757] vesafb: framebuffer at 0xd0000000, mapped to 0x(____ptrval____), using 8128k, total 8128k
[    2.161657] Console: switching to colour frame buffer device 160x64
[    2.193683] fb0: VESA VGA frame buffer device
[    7.205119] r8169 0000:02:00.0 eth0: jumbo features [frames: 4080 bytes, tx checksumming: ko]
[    8.052321] Console: switching to colour frame buffer device 240x67
[    8.070380] i915 0000:00:02.0: fb0: i915drmfb frame buffer device
I have a problem with i915drmfb because it doesn't offer the resolution i want.
Is it possible to build kernel with inteldrmfb instead?

Best Regards.

[gr4vity]

There is another problem, if i used nomodeset during boot i can't have a desktop environment.
I'm stuck in command line mode.
If i want to have desktop i must remove xorg-intel package.
It doesn't work like that on ubuntu.
I can boot using nomodeset and still have a desktop environment.
Any idea?

[clausmuus]

Yes. The xorg-ntel Packard add some options to the xorg config.

[gr4vity]

Hi Claus,
I don't know why i didn't think about that 
I figured that out when i used xorg-intel and xorg-nvidia packages simultaneously.

In this case with nomodeset i have to delete intel *.sh files in
/etc/X11/xorg.conf.d
I still can't figure out the issue with inteldrmfb.

Best Regards.

[clausmuus]

Have you try to use the "modesetting" xorg driver instat of the "intel" driver? You can change this at the end of the /etc/X11/xorg.conf.d/30_intel.sh file.

[gr4vity]

Hi Claus,
Yes, i tried it ... that works with KMS which already enabled.
I removed vga=0x314 and used modesetting

Code: [Select]

MLD> dmesg | grep -i frame
[    0.234795] LSM: Security Framework initializing
[    7.609868] r8169 0000:02:00.0 eth0: jumbo features [frames: 4080 bytes, tx checksumming: ko]
[    8.411491] Console: switching to colour frame buffer device 240x67
[    8.429650] i915 0000:00:02.0: fb0: i915drmfb frame buffer device
i915drmfb is loaded.
I just want to keep everything as is using vga=ask in order to select a higher resolution so fb0 uses VESA VGA
Then it switch to inteldrmfb not i915drmfb.

I googled it, i don't see much results.
I think older kernel comes with inteldrmfb and newer kernel comes with i915drmfb.

Edit: i found a patch which changed fb device name from inteldrmfb to  i915drmfb in the following link

https://yhbt.net/lore/all/87zgxbzpiu.fsf@intel.com/T/

Code: [Select]

diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
index 785dcf20c77b..46082490dc9a 100644
--- a/drivers/gpu/drm/i915/i915_drv.c
+++ b/drivers/gpu/drm/i915/i915_drv.c
@@ -554,7 +554,7 @@ static int i915_driver_hw_probe(struct drm_i915_private *dev_priv)
  if (ret)
  goto err_perf;
 
- ret = drm_aperture_remove_conflicting_pci_framebuffers(pdev, "inteldrmfb");
+ ret = drm_aperture_remove_conflicting_pci_framebuffers(pdev, "i915drmfb");
  if (ret)
  goto err_ggtt;
Best Regards.