Testers Needed for New RTAI Packages

More
05 Jan 2020 04:34 #154076 by JohnnyCNC
Thanks. I'll give that a try.

Also, at boot it says kernel not compiled with "reptoline".

I also have to choose Linux X3CNC 4.14.132-rtai-amd64 version using the advances options choice on the boot loader each time I boot.

Thanks
John

Please Log in or Create an account to join the conversation.

More
05 Jan 2020 08:37 - 05 Jan 2020 08:39 #154080 by twoflowers

phillc54 wrote: Unfortunately this doesn't work on my machine with i915 graphics. :(

Can you post your /var/log/Xorg.0.log?

@JohnnyCNC: I usually remove all kernels except the one I want to use, then ther's no place for creativity on the bootliaders side.
Last edit: 05 Jan 2020 08:39 by twoflowers.

Please Log in or Create an account to join the conversation.

More
05 Jan 2020 09:24 #154084 by phillc54

twoflowers wrote: Can you post your /var/log/Xorg.0.log?

Here you go.
Attachments:

Please Log in or Create an account to join the conversation.

More
05 Jan 2020 09:40 #154085 by twoflowers
Ok, let's see: You have 1360x768, so no 4:3 VESA resolution. Ergo, yozu need to add a modeline setting to the monitor section. Modeline is created with cvt tool:
$ cvt 1360 768
# 1360x768 59.80 Hz (CVT) hsync: 47.72 kHz; pclk: 84.75 MHz
Modeline "1360x768_60.00"   84.75  1360 1432 1568 1776  768 771 781 798 -hsync +vsync

The Modeline needs to go inside the Monitor-section, the Mode it defines should go inside the Display-Section. So the config would be:
Section "Monitor"
    Identifier  "Monitor0"
    VendorName  "Monitor Vendor"
    ModelName   "Monitor Model" 
    HorizSync   28.0 - 60.0
    VertRefresh 43.0 - 72.0
    Modeline "1360x768_60.00"   84.75  1360 1432 1568 1776  768 771 781 798 hsync +vsync
EndSection

Section "Screen"
    Identifier "Screen0"
    Device     "Card0"
    Monitor    "Monitor0"
    Subsection "Display"
        Viewport  0 0
        Depth     24
        Virtual   1360 768
        Modes "1360x768_60.00"
    EndSubSection
EndSection

Ref.: kodi.wiki/view/Configuring_resolution_via_xorg.conf

Please Log in or Create an account to join the conversation.

More
05 Jan 2020 10:03 #154086 by phillc54
Still no luck.
Attachments:

Please Log in or Create an account to join the conversation.

More
05 Jan 2020 10:20 #154087 by twoflowers
Hm ...
[     8.217] (II) VESA(0): Not using mode "1360x768_60.00" (no mode of this name)

Could you please try "ModeLine" (upper "L") instead of "Modeline" ?

Please Log in or Create an account to join the conversation.

More
05 Jan 2020 10:41 #154088 by phillc54
Same result.
Attachments:

Please Log in or Create an account to join the conversation.

More
05 Jan 2020 11:09 #154090 by twoflowers
Start X in verbose mode, maybe there's something more to see (don't forget to shut down your xserver first):
X -verbose 6 > ~/xlog.txt 2>&1

You could also try changing the name of the ModeLine from "1360x768_60.00" to "1360x768" - but that was ~ 25 years ago ...

Please Log in or Create an account to join the conversation.

More
05 Jan 2020 11:52 #154091 by ChironFZ16
5.2 UEFI_Kernel works fine with Mint 19.3 ;)
chiron@chiron-SystemFZ16:~$ uname -a
Linux chiron-SystemFZ16 5.2.21-rt14 #2 SMP PREEMPT RT Sat Dec 7 12:49:29 CET 2019 x86_64 x86_64 x86_64 GNU/Linux
chiron@chiron-SystemFZ16:~$ inxi -Fz
System:    Host: chiron-SystemFZ16 Kernel: 5.2.21-rt14 x86_64 bits: 64 Desktop: MATE 1.22.2 
           Distro: Linux Mint 19.3 Tricia 
Machine:   Type: Desktop Mobo: ASUSTeK model: TUF Z390-PRO GAMING v: Rev X.0x serial: <filter> 
           UEFI: American Megatrends v: 2417 date: 06/03/2019 
CPU:       Topology: 8-Core model: Intel Core i7-9700KF bits: 64 type: MCP L2 cache: 12.0 MiB 
           Speed: 4830 MHz min/max: 800/5100 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 801 5: 800 6: 800 7: 800 
           8: 800 
Graphics:  Device-1: NVIDIA GP107GL [Quadro P1000] driver: nouveau v: kernel 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa resolution: 3840x2160~60Hz 
           OpenGL: renderer: llvmpipe (LLVM 8.0 256 bits) v: 3.3 Mesa 19.0.8 
Audio:     Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel 
           Device-2: NVIDIA GP107GL High Definition Audio driver: snd_hda_intel 
           Sound Server: ALSA v: k5.2.21-rt14 
Network:   Device-1: Intel Ethernet I219-V driver: e1000e 
           IF: eno1 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 1.36 TiB used: 131.87 GiB (9.4%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 500GB size: 465.76 GiB 
           ID-2: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB 
           ID-3: /dev/sdb vendor: Samsung model: SSD 840 EVO 500GB size: 465.76 GiB 
Partition: ID-1: / size: 456.96 GiB used: 131.85 GiB (28.9%) fs: ext4 dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 36.0 C mobo: N/A gpu: nouveau temp: 44 C 
           Fan Speeds (RPM): cpu: 0 gpu: nouveau fan: 1292 
Info:      Processes: 271 Uptime: 11m Memory: 31.33 GiB used: 1.68 GiB (5.4%) Shell: bash inxi: 3.0.32 
chiron@chiron-SystemFZ16:~$ 

Please Log in or Create an account to join the conversation.

More
06 Jan 2020 03:28 #154121 by phillc54

twoflowers wrote: Start X in verbose mode, maybe there's something more to see (don't forget to shut down your xserver first):

X -verbose 6 > ~/xlog.txt 2>&1

You could also try changing the name of the ModeLine from "1360x768_60.00" to "1360x768" - but that was ~ 25 years ago ...

It didn't add any more useful info.

I think the problem is with the framebuffer driver:
[ 60332.718] (EE) open /dev/fb0: No such file or directory
[ 60332.718] (EE) Screen 0 deleted because of no matching config section.
[ 60332.718] (II) UnloadModule: "modesetting"
[ 60332.718] (EE) Screen 0 deleted because of no matching config section.
[ 60332.718] (II) UnloadModule: "fbdev"
[ 60332.718] (II) UnloadSubModule: "fbdevhw"
Alec is looking into this, but after seeing your post I thought I would give it a shot but it doesn't seem to help with this hardware.

Cheers, Phill.

Please Log in or Create an account to join the conversation.

Time to create page: 0.123 seconds
Powered by Kunena Forum