Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Start surf browser with xinit , than toggle full screen mode
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
finalturismo
Apprentice
Apprentice


Joined: 06 Jan 2020
Posts: 164

PostPosted: Sun Mar 08, 2020 6:17 am    Post subject: Start surf browser with xinit , than toggle full screen mode Reply with quote

Ok guys so iam stuck on this one, i can launch programs with xinit or by putting them in the .xinitrc file. The application will load, but i cant for the life of me figure out how to toggle full screen mode. I want avoid running any type of window manager altogether.

The idea is to just start a browser on boot , having that be the only function.


Any idea?

If anyone wants to try to figure out with me that would be great, i have been stuck here for 2 days.

The best i can find is use wmctrl or xdotool to toggle the open window to full screen. But for some reason i cant even get that to work.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 47037
Location: 56N 3W

PostPosted: Sun Mar 08, 2020 12:16 pm    Post subject: Reply with quote

finalturismo,

Your Xorg.0.log would be useful. Along with the capabilities of the display you are using.
The display capabilities should be in Xorg.0.log but the auto detect would get it right if they were.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
finalturismo
Apprentice
Apprentice


Joined: 06 Jan 2020
Posts: 164

PostPosted: Sun Mar 08, 2020 1:24 pm    Post subject: Reply with quote

I don't think the problem is with the defaults of Xorg or using a null driver but i could be wrong.

It has no issues toggling full screen when i use ratpoison window manager or openbox.

here is my log

Code:
[   767.483]
X.Org X Server 1.20.6
X Protocol Version 11, Revision 0
[   767.483] Build Operating System: Linux 5.5.7-gentoo-x86_64 x86_64 Gentoo
[   767.483] Current Operating System: Linux autodisk 5.5.7-gentoo-x86_64 #1 SMP Sat Feb 29 16:28:14 CST 2020 x86_64
[   767.483] Kernel command line: BOOT_IMAGE=/vmlinuz-5.5.7-gentoo-x86_64 root=UUID=92bc5d9f-b09a-45d5-8ae2-f715342d8b9d ro
[   767.483] Build Date: 02 March 2020  04:29:59PM
[   767.483] 
[   767.483] Current version of pixman: 0.38.4
[   767.483]    Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
[   767.483] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   767.483] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Mar  7 19:07:57 2020
[   767.483] (==) Using config directory: "/etc/X11/xorg.conf.d"
[   767.483] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   767.484] (==) No Layout section.  Using the first Screen section.
[   767.484] (==) No screen section available. Using defaults.
[   767.484] (**) |-->Screen "Default Screen Section" (0)
[   767.484] (**) |   |-->Monitor "<default monitor>"
[   767.484] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
[   767.484] (==) Automatically adding devices
[   767.484] (==) Automatically enabling devices
[   767.484] (==) Automatically adding GPU devices
[   767.485] (==) Max clients allowed: 256, resource mask: 0x1fffff
[   767.485] (==) FontPath set to:
   /usr/share/fonts/misc/,
   /usr/share/fonts/TTF/,
   /usr/share/fonts/OTF/,
   /usr/share/fonts/Type1/,
   /usr/share/fonts/100dpi/,
   /usr/share/fonts/75dpi/
[   767.485] (==) ModulePath set to "/usr/lib64/xorg/modules"
[   767.485] (II) The server relies on udev to provide the list of input devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
[   767.485] (II) Loader magic: 0x55d5ae90ec60
[   767.485] (II) Module ABI versions:
[   767.485]    X.Org ANSI C Emulation: 0.4
[   767.485]    X.Org Video Driver: 24.0
[   767.485]    X.Org XInput driver : 24.1
[   767.485]    X.Org Server Extension : 10.0
[   767.485] (II) xfree86: Adding drm device (/dev/dri/card0)
[   767.499] (--) PCI:*(6@0:0:0) 102b:0534:1028:04f8 rev 0, Mem @ 0xd8000000/16777216, 0xde7fc000/16384, 0xdd800000/8388608, BIOS @ 0x????????/131072
[   767.499] (II) LoadModule: "glx"
[   767.499] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[   767.500] (II) Module glx: vendor="X.Org Foundation"
[   767.500]    compiled for 1.20.6, module version = 1.0.0
[   767.500]    ABI class: X.Org Server Extension, version 10.0
[   767.500] (==) Matched mga as autoconfigured driver 0
[   767.500] (==) Matched modesetting as autoconfigured driver 1
[   767.500] (==) Matched fbdev as autoconfigured driver 2
[   767.500] (==) Matched vesa as autoconfigured driver 3
[   767.500] (==) Assigned the driver to the xf86ConfigLayout
[   767.500] (II) LoadModule: "mga"
[   767.500] (II) Loading /usr/lib64/xorg/modules/drivers/mga_drv.so
[   767.500] (II) Module mga: vendor="X.Org Foundation"
[   767.500]    compiled for 1.20.6, module version = 2.0.0
[   767.500]    Module class: X.Org Video Driver
[   767.500]    ABI class: X.Org Video Driver, version 24.0
[   767.500] (II) LoadModule: "modesetting"
[   767.501] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[   767.501] (II) Module modesetting: vendor="X.Org Foundation"
[   767.501]    compiled for 1.20.6, module version = 1.20.6
[   767.501]    Module class: X.Org Video Driver
[   767.501]    ABI class: X.Org Video Driver, version 24.0
[   767.501] (II) LoadModule: "fbdev"
[   767.501] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
[   767.501] (II) Module fbdev: vendor="X.Org Foundation"
[   767.501]    compiled for 1.20.6, module version = 0.5.0
[   767.501]    Module class: X.Org Video Driver
[   767.501]    ABI class: X.Org Video Driver, version 24.0
[   767.501] (II) LoadModule: "vesa"
[   767.501] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[   767.501] (II) Module vesa: vendor="X.Org Foundation"
[   767.501]    compiled for 1.20.6, module version = 2.4.0
[   767.501]    Module class: X.Org Video Driver
[   767.501]    ABI class: X.Org Video Driver, version 24.0
[   767.501] (II) MGA: driver for Matrox chipsets: mga2064w, mga1064sg, mga2164w,
   mga2164w AGP, mgag100, mgag100 PCI, mgag200, mgag200 PCI,
   mgag200 SE A PCI, mgag200 SE B PCI, mgag200 EV Maxim,
   mgag200 ER SH7757, mgag200 eW Nuvoton, mgag200 eW3 Nuvoton,
   mgag200eH, mgag200eH3, mgag400, mgag550
[   767.501] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[   767.501] (II) FBDEV: driver for framebuffer: fbdev
[   767.501] (II) VESA: driver for VESA chipsets: vesa
[   767.501] (--) using VT number 7

[   767.504] (EE) mga: The PCI device 0x534 at 06@00:00:0 has a kernel module claiming it.
[   767.505] (EE) mga: This driver cannot operate until it has been unloaded.
[   767.505] (II) modeset(0): using drv /dev/dri/card0
[   767.505] (WW) Falling back to old probe method for fbdev
[   767.505] (II) Loading sub module "fbdevhw"
[   767.505] (II) LoadModule: "fbdevhw"
[   767.505] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[   767.505] (II) Module fbdevhw: vendor="X.Org Foundation"
[   767.505]    compiled for 1.20.6, module version = 0.0.2
[   767.505]    ABI class: X.Org Video Driver, version 24.0
[   767.505] (II) modeset(0): Creating default Display subsection in Screen section
   "Default Screen Section" for depth/fbbpp 24/32
[   767.505] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[   767.505] (==) modeset(0): RGB weight 888
[   767.505] (==) modeset(0): Default visual is TrueColor
[   767.505] (II) Loading sub module "glamoregl"
[   767.505] (II) LoadModule: "glamoregl"
[   767.505] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
[   767.508] (II) Module glamoregl: vendor="X.Org Foundation"
[   767.508]    compiled for 1.20.6, module version = 1.0.1
[   767.508]    ABI class: X.Org ANSI C Emulation, version 0.4
[   767.568] (II) modeset(0): Refusing to try glamor on llvmpipe
[   767.569] (EE) modeset(0): glamor initialization failed
[   767.569] (II) modeset(0): ShadowFB: preferred YES, enabled YES
[   767.569] (II) modeset(0): Double-buffered shadow updates: on
[   767.608] (II) modeset(0): Output VGA-1 has no monitor section
[   767.646] (II) modeset(0): EDID for output VGA-1
[   767.646] (II) modeset(0): Manufacturer: HWP  Model: 3282  Serial#: 16843009
[   767.646] (II) modeset(0): Year: 2016  Week: 8
[   767.646] (II) modeset(0): EDID Version: 1.3
[   767.646] (II) modeset(0): Analog Display Input,  Input Voltage Level: 0.700/0.700 V
[   767.646] (II) modeset(0): Sync:  Separate
[   767.646] (II) modeset(0): Max Image Size [cm]: horiz.: 48  vert.: 27
[   767.646] (II) modeset(0): Gamma: 2.20
[   767.646] (II) modeset(0): DPMS capabilities: Off; RGB/Color Display
[   767.646] (II) modeset(0): First detailed timing is preferred mode
[   767.646] (II) modeset(0): redX: 0.651 redY: 0.338   greenX: 0.318 greenY: 0.612
[   767.646] (II) modeset(0): blueX: 0.151 blueY: 0.065   whiteX: 0.313 whiteY: 0.329
[   767.646] (II) modeset(0): Supported established timings:
[   767.646] (II) modeset(0): 640x480@60Hz
[   767.646] (II) modeset(0): 800x600@60Hz
[   767.646] (II) modeset(0): 1024x768@60Hz
[   767.646] (II) modeset(0): Manufacturer's mask: 0
[   767.646] (II) modeset(0): Supported standard timings:
[   767.646] (II) modeset(0): #0: hsize: 1920  vsize 1080  refresh: 60  vid: 49361
[   767.646] (II) modeset(0): #1: hsize: 1280  vsize 720  refresh: 60  vid: 49281
[   767.646] (II) modeset(0): #2: hsize: 1600  vsize 900  refresh: 60  vid: 49321
[   767.646] (II) modeset(0): #3: hsize: 1440  vsize 900  refresh: 60  vid: 149
[   767.646] (II) modeset(0): #4: hsize: 1680  vsize 1050  refresh: 60  vid: 179
[   767.646] (II) modeset(0): #5: hsize: 1280  vsize 800  refresh: 60  vid: 129
[   767.646] (II) modeset(0): #6: hsize: 1280  vsize 1024  refresh: 60  vid: 32897
[   767.646] (II) modeset(0): Supported detailed timing:
[   767.646] (II) modeset(0): clock: 148.5 MHz   Image Size:  476 x 268 mm
[   767.646] (II) modeset(0): h_active: 1920  h_sync: 2008  h_sync_end 2052 h_blank_end 2200 h_border: 0
[   767.646] (II) modeset(0): v_active: 1080  v_sync: 1084  v_sync_end 1089 v_blanking: 1125 v_border: 0
[   767.646] (II) modeset(0): Ranges: V min: 50 V max: 60 Hz, H min: 30 H max: 80 kHz, PixClock max 175 MHz
[   767.646] (II) modeset(0): Monitor name: HP Z22n
[   767.646] (II) modeset(0): Serial No: 6CM6080KC5
[   767.646] (II) modeset(0): EDID (in hex):
[   767.646] (II) modeset(0):    00ffffffffffff0022f0823201010101
[   767.646] (II) modeset(0):    081a010368301b782aebf5a656519c26
[   767.646] (II) modeset(0):    105054210800d1c081c0a9c09500b300
[   767.646] (II) modeset(0):    810081800101023a801871382d40582c
[   767.646] (II) modeset(0):    4500dc0c1100001e000000fd00323c1e
[   767.646] (II) modeset(0):    5011000a202020202020000000fc0048
[   767.646] (II) modeset(0):    50205a32326e0a2020202020000000ff
[   767.646] (II) modeset(0):    0036434d363038304b43350a20200046
[   767.647] (II) modeset(0): Printing probed modes for output VGA-1
[   767.647] (II) modeset(0): Modeline "1680x1050"x60.0  146.25  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
[   767.647] (II) modeset(0): Modeline "1600x900"x60.0  108.00  1600 1624 1704 1800  900 901 904 1000 +hsync +vsync (60.0 kHz e)
[   767.647] (II) modeset(0): Modeline "1280x1024"x60.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[   767.647] (II) modeset(0): Modeline "1440x900"x59.9  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz e)
[   767.647] (II) modeset(0): Modeline "1280x800"x59.8   83.50  1280 1352 1480 1680  800 803 809 831 -hsync +vsync (49.7 kHz e)
[   767.647] (II) modeset(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[   767.647] (II) modeset(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[   767.647] (II) modeset(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[   767.647] (II) modeset(0): Output VGA-1 connected
[   767.647] (II) modeset(0): Using exact sizes for initial modes
[   767.647] (II) modeset(0): Output VGA-1 using initial mode 1600x900 +0+0
[   767.647] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[   767.647] (==) modeset(0): DPI set to (96, 96)
[   767.647] (II) Loading sub module "fb"
[   767.647] (II) LoadModule: "fb"
[   767.647] (II) Loading /usr/lib64/xorg/modules/libfb.so
[   767.647] (II) Module fb: vendor="X.Org Foundation"
[   767.647]    compiled for 1.20.6, module version = 1.0.0
[   767.647]    ABI class: X.Org ANSI C Emulation, version 0.4
[   767.647] (II) Loading sub module "shadow"
[   767.647] (II) LoadModule: "shadow"
[   767.647] (II) Loading /usr/lib64/xorg/modules/libshadow.so
[   767.647] (II) Module shadow: vendor="X.Org Foundation"
[   767.647]    compiled for 1.20.6, module version = 1.1.0
[   767.647]    ABI class: X.Org ANSI C Emulation, version 0.4
[   767.647] (II) UnloadModule: "fbdev"
[   767.647] (II) Unloading fbdev
[   767.647] (II) UnloadSubModule: "fbdevhw"
[   767.647] (II) Unloading fbdevhw
[   767.647] (II) UnloadModule: "vesa"
[   767.647] (II) Unloading vesa
[   767.647] (==) modeset(0): Backing store enabled
[   767.647] (==) modeset(0): Silken mouse enabled
[   767.647] (II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
[   767.648] (==) modeset(0): DPMS enabled
[   767.648] (II) Initializing extension Generic Event Extension
[   767.648] (II) Initializing extension SHAPE
[   767.648] (II) Initializing extension MIT-SHM
[   767.648] (II) Initializing extension XInputExtension
[   767.648] (II) Initializing extension XTEST
[   767.648] (II) Initializing extension BIG-REQUESTS
[   767.648] (II) Initializing extension SYNC
[   767.648] (II) Initializing extension XKEYBOARD
[   767.648] (II) Initializing extension XC-MISC
[   767.648] (II) Initializing extension XFIXES
[   767.648] (II) Initializing extension RENDER
[   767.648] (II) Initializing extension RANDR
[   767.648] (II) Initializing extension COMPOSITE
[   767.648] (II) Initializing extension DAMAGE
[   767.648] (II) Initializing extension MIT-SCREEN-SAVER
[   767.648] (II) Initializing extension DOUBLE-BUFFER
[   767.648] (II) Initializing extension RECORD
[   767.648] (II) Initializing extension DPMS
[   767.648] (II) Initializing extension Present
[   767.648] (II) Initializing extension DRI3
[   767.648] (II) Initializing extension X-Resource
[   767.648] (II) Initializing extension XVideo
[   767.648] (II) Initializing extension XVideo-MotionCompensation
[   767.648] (II) Initializing extension GLX
[   767.648] (II) AIGLX: Screen 0 is not DRI2 capable
[   767.652] (II) IGLX: Loaded and initialized swrast
[   767.652] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[   767.652] (II) Initializing extension XFree86-VidModeExtension
[   767.652] (II) Initializing extension XFree86-DGA
[   767.652] (II) Initializing extension XFree86-DRI
[   767.652] (II) Initializing extension DRI2
[   767.652] (II) modeset(0): Damage tracking initialized
[   767.652] (II) modeset(0): Setting screen physical size to 423 x 238
[   767.722] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[   767.722] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[   767.722] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[   767.722] (II) LoadModule: "libinput"
[   767.722] (II) Loading /usr/lib64/xorg/modules/input/libinput_drv.so
[   767.724] (II) Module libinput: vendor="X.Org Foundation"
[   767.724]    compiled for 1.20.6, module version = 0.29.0
[   767.724]    Module class: X.Org XInput Driver
[   767.724]    ABI class: X.Org XInput driver, version 24.1
[   767.724] (II) Using input driver 'libinput' for 'Power Button'
[   767.724] (**) Power Button: always reports core events
[   767.724] (**) Option "Device" "/dev/input/event0"
[   767.725] (**) Option "_source" "server/udev"
[   767.727] (II) event0  - Power Button: is tagged by udev as: Keyboard
[   767.727] (II) event0  - Power Button: device is a keyboard
[   767.727] (II) event0  - Power Button: device removed
[   767.792] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input0/event0"
[   767.792] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[   767.794] (II) event0  - Power Button: is tagged by udev as: Keyboard
[   767.794] (II) event0  - Power Button: device is a keyboard
[   767.795] (II) config/udev: Adding input device Dell Dell USB Keyboard (/dev/input/event2)
[   767.795] (**) Dell Dell USB Keyboard: Applying InputClass "evdev keyboard catchall"
[   767.795] (**) Dell Dell USB Keyboard: Applying InputClass "libinput keyboard catchall"
[   767.795] (II) Using input driver 'libinput' for 'Dell Dell USB Keyboard'
[   767.795] (**) Dell Dell USB Keyboard: always reports core events
[   767.795] (**) Option "Device" "/dev/input/event2"
[   767.795] (**) Option "_source" "server/udev"
[   767.796] (II) event2  - Dell Dell USB Keyboard: is tagged by udev as: Keyboard
[   767.796] (II) event2  - Dell Dell USB Keyboard: device is a keyboard
[   767.797] (II) event2  - Dell Dell USB Keyboard: device removed
[   767.842] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/0003:413C:2003.0002/input/input2/event2"
[   767.842] (II) XINPUT: Adding extended input device "Dell Dell USB Keyboard" (type: KEYBOARD, id 7)
[   767.844] (II) event2  - Dell Dell USB Keyboard: is tagged by udev as: Keyboard
[   767.844] (II) event2  - Dell Dell USB Keyboard: device is a keyboard
[   767.845] (II) config/udev: Adding input device Avocent Keyboard/Mouse Function (/dev/input/event3)
[   767.845] (**) Avocent Keyboard/Mouse Function: Applying InputClass "evdev keyboard catchall"
[   767.845] (**) Avocent Keyboard/Mouse Function: Applying InputClass "libinput keyboard catchall"
[   767.845] (II) Using input driver 'libinput' for 'Avocent Keyboard/Mouse Function'
[   767.845] (**) Avocent Keyboard/Mouse Function: always reports core events
[   767.845] (**) Option "Device" "/dev/input/event3"
[   767.845] (**) Option "_source" "server/udev"
[   767.847] (II) event3  - Avocent Keyboard/Mouse Function: is tagged by udev as: Keyboard
[   767.847] (II) event3  - Avocent Keyboard/Mouse Function: device is a keyboard
[   767.847] (II) event3  - Avocent Keyboard/Mouse Function: device removed
[   767.892] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.1/1-1.6.1:1.0/0003:0624:0249.0003/input/input3/event3"
[   767.892] (II) XINPUT: Adding extended input device "Avocent Keyboard/Mouse Function" (type: KEYBOARD, id 8)
[   767.894] (II) event3  - Avocent Keyboard/Mouse Function: is tagged by udev as: Keyboard
[   767.894] (II) event3  - Avocent Keyboard/Mouse Function: device is a keyboard
[   767.895] (II) config/udev: Adding input device Avocent Keyboard/Mouse Function (/dev/input/event4)
[   767.895] (**) Avocent Keyboard/Mouse Function: Applying InputClass "evdev pointer catchall"
[   767.895] (**) Avocent Keyboard/Mouse Function: Applying InputClass "libinput pointer catchall"
[   767.895] (II) Using input driver 'libinput' for 'Avocent Keyboard/Mouse Function'
[   767.895] (**) Avocent Keyboard/Mouse Function: always reports core events
[   767.895] (**) Option "Device" "/dev/input/event4"
[   767.895] (**) Option "_source" "server/udev"
[   767.954] (II) event4  - Avocent Keyboard/Mouse Function: is tagged by udev as: Mouse
[   767.954] (II) event4  - Avocent Keyboard/Mouse Function: device is a pointer
[   767.954] (II) event4  - Avocent Keyboard/Mouse Function: device removed
[   767.989] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.1/1-1.6.1:1.1/0003:0624:0249.0004/input/input4/event4"
[   767.989] (II) XINPUT: Adding extended input device "Avocent Keyboard/Mouse Function" (type: MOUSE, id 9)
[   767.989] (**) Option "AccelerationScheme" "none"
[   767.989] (**) Avocent Keyboard/Mouse Function: (accel) selected scheme none/0
[   767.989] (**) Avocent Keyboard/Mouse Function: (accel) acceleration factor: 2.000
[   767.989] (**) Avocent Keyboard/Mouse Function: (accel) acceleration threshold: 4
[   768.047] (II) event4  - Avocent Keyboard/Mouse Function: is tagged by udev as: Mouse
[   768.047] (II) event4  - Avocent Keyboard/Mouse Function: device is a pointer
[   768.048] (II) config/udev: Adding input device Avocent Keyboard/Mouse Function (/dev/input/mouse1)
[   768.048] (II) No input driver specified, ignoring this device.
[   768.048] (II) This device may have been added with another device file.
[   768.049] (II) config/udev: Adding input device Avocent Keyboard/Mouse Function (/dev/input/event5)
[   768.049] (**) Avocent Keyboard/Mouse Function: Applying InputClass "evdev pointer catchall"
[   768.049] (**) Avocent Keyboard/Mouse Function: Applying InputClass "libinput pointer catchall"
[   768.049] (II) Using input driver 'libinput' for 'Avocent Keyboard/Mouse Function'
[   768.049] (**) Avocent Keyboard/Mouse Function: always reports core events
[   768.049] (**) Option "Device" "/dev/input/event5"
[   768.049] (**) Option "_source" "server/udev"
[   768.107] (II) event5  - Avocent Keyboard/Mouse Function: is tagged by udev as: Mouse
[   768.107] (II) event5  - Avocent Keyboard/Mouse Function: device is a pointer
[   768.107] (II) event5  - Avocent Keyboard/Mouse Function: device removed
[   768.145] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.1/1-1.6.1:1.2/0003:0624:0249.0005/input/input5/event5"
[   768.146] (II) XINPUT: Adding extended input device "Avocent Keyboard/Mouse Function" (type: MOUSE, id 10)
[   768.146] (**) Option "AccelerationScheme" "none"
[   768.146] (**) Avocent Keyboard/Mouse Function: (accel) selected scheme none/0
[   768.146] (**) Avocent Keyboard/Mouse Function: (accel) acceleration factor: 2.000
[   768.146] (**) Avocent Keyboard/Mouse Function: (accel) acceleration threshold: 4
[   768.204] (II) event5  - Avocent Keyboard/Mouse Function: is tagged by udev as: Mouse
[   768.204] (II) event5  - Avocent Keyboard/Mouse Function: device is a pointer
[   768.205] (II) config/udev: Adding input device Avocent Keyboard/Mouse Function (/dev/input/mouse2)
[   768.205] (II) No input driver specified, ignoring this device.
[   768.205] (II) This device may have been added with another device file.
[   768.205] (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/event1)
[   768.205] (**) Logitech USB Optical Mouse: Applying InputClass "evdev pointer catchall"
[   768.205] (**) Logitech USB Optical Mouse: Applying InputClass "libinput pointer catchall"
[   768.205] (II) Using input driver 'libinput' for 'Logitech USB Optical Mouse'
[   768.205] (**) Logitech USB Optical Mouse: always reports core events
[   768.205] (**) Option "Device" "/dev/input/event1"
[   768.205] (**) Option "_source" "server/udev"
[   768.207] (II) event1  - Logitech USB Optical Mouse: is tagged by udev as: Mouse
[   768.207] (II) event1  - Logitech USB Optical Mouse: device is a pointer
[   768.207] (II) event1  - Logitech USB Optical Mouse: device removed
[   768.249] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/0003:046D:C077.0001/input/input1/event1"
[   768.249] (II) XINPUT: Adding extended input device "Logitech USB Optical Mouse" (type: MOUSE, id 11)
[   768.249] (**) Option "AccelerationScheme" "none"
[   768.249] (**) Logitech USB Optical Mouse: (accel) selected scheme none/0
[   768.249] (**) Logitech USB Optical Mouse: (accel) acceleration factor: 2.000
[   768.249] (**) Logitech USB Optical Mouse: (accel) acceleration threshold: 4
[   768.251] (II) event1  - Logitech USB Optical Mouse: is tagged by udev as: Mouse
[   768.251] (II) event1  - Logitech USB Optical Mouse: device is a pointer
[   768.252] (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/mouse0)
[   768.252] (II) No input driver specified, ignoring this device.
[   768.252] (II) This device may have been added with another device file.
[   768.252] (II) config/udev: Adding input device PC Speaker (/dev/input/event6)
[   768.252] (II) No input driver specified, ignoring this device.
[   768.252] (II) This device may have been added with another device file.
[   768.362] (II) modeset(0): Disabling kernel dirty updates, not required.
[   909.132] (II) event0  - Power Button: device removed
[   909.182] (II) event2  - Dell Dell USB Keyboard: device removed
[   909.229] (II) event3  - Avocent Keyboard/Mouse Function: device removed
[   909.265] (II) event4  - Avocent Keyboard/Mouse Function: device removed
[   909.305] (II) event5  - Avocent Keyboard/Mouse Function: device removed
[   909.345] (II) event1  - Logitech USB Optical Mouse: device removed
[   909.386] (II) UnloadModule: "libinput"
[   909.386] (II) UnloadModule: "libinput"
[   909.386] (II) UnloadModule: "libinput"
[   909.386] (II) UnloadModule: "libinput"
[   909.386] (II) UnloadModule: "libinput"
[   909.387] (II) UnloadModule: "libinput"
[   909.535] (II) Server terminated successfully (0). Closing log file.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 47037
Location: 56N 3W

PostPosted: Sun Mar 08, 2020 1:44 pm    Post subject: Reply with quote

finalturismo,

Your kernel is broken and your display is broken.

You probably have the old framebuffer driver in you kernel, hence
Code:
[   767.504] (EE) mga: The PCI device 0x534 at 06@00:00:0 has a kernel module claiming it.
[   767.505] (EE) mga: This driver cannot operate until it has been unloaded.

There may be more junk too.

On to your monitor ...
Code:
[   767.646] (II) modeset(0): First detailed timing is preferred mode
...
[   767.646] (II) modeset(0): Supported detailed timing:
[   767.646] (II) modeset(0): clock: 148.5 MHz   Image Size:  476 x 268 mm
[   767.646] (II) modeset(0): h_active: 1920  h_sync: 2008  h_sync_end 2052 h_blank_end 2200 h_border: 0
[   767.646] (II) modeset(0): v_active: 1080  v_sync: 1084  v_sync_end 1089 v_blanking: 1125 v_border: 0

So it should be running at 1920x1080.

But
Code:
[   767.647] (II) modeset(0): Printing probed modes for output VGA-1
[   767.647] (II) modeset(0): Modeline "1680x1050"x60.0  146.25  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
[   767.647] (II) modeset(0): Modeline "1600x900"x60.0  108.00  1600 1624 1704 1800  900 901 904 1000 +hsync +vsync (60.0 kHz e)
[   767.647] (II) modeset(0): Modeline "1280x1024"x60.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[   767.647] (II) modeset(0): Modeline "1440x900"x59.9  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz e)
[   767.647] (II) modeset(0): Modeline "1280x800"x59.8   83.50  1280 1352 1480 1680  800 803 809 831 -hsync +vsync (49.7 kHz e)
[   767.647] (II) modeset(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[   767.647] (II) modeset(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[   767.647] (II) modeset(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[   767.647] (II) modeset(0): Output VGA-1 connected
[   767.647] (II) modeset(0): Using exact sizes for initial modes
[   767.647] (II) modeset(0): Output VGA-1 using initial mode 1600x900 +0+0

There are no 1920x1080 modes in that list. Its not even using 1680x1050 which is the first in the list. Rather Xorg set up for 1600x900.

That's a feature.

Why do you build the mga driver for a run anywhere system?
You don't care about graphics performance.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
finalturismo
Apprentice
Apprentice


Joined: 06 Jan 2020
Posts: 164

PostPosted: Sun Mar 08, 2020 1:57 pm    Post subject: Reply with quote

I know what your saying but its not this, my log for the most part is clean after i deleted it. I was trying a bunch of random commands. I would like you to try this for your self, from some Googling it seems to be a common hurdle for many people trying to do a web based kiosk setup with xinit.

It does the same thing on my other systems. There must be some settings i need to change for xserver.....

It has no problems when i launch any type of window manager.

Problem is xserver hasnt been used too much like this since the early 2000s and my knowledge on it is limited....


as far as graphics performance, it is not needed at all.

I really want to get to the bottom of this , because iam trying to make a minimalist system with the least amount of packages possible to boot into a web based kiosk that accesses the internal web server.

Gentoo is the perfect solution for this , with its use flag system and ability to build your own kernel. Should be rock solid when finished , if my n00b self can manage to get past this issue XD
Back to top
View user's profile Send private message
Ant P.
Watchman
Watchman


Joined: 18 Apr 2009
Posts: 6868

PostPosted: Sun Mar 08, 2020 4:54 pm    Post subject: Reply with quote

Does your matrox card have enough vram to run at 1920x1080? Try using Depth 16.
Back to top
View user's profile Send private message
finalturismo
Apprentice
Apprentice


Joined: 06 Jan 2020
Posts: 164

PostPosted: Sun Mar 08, 2020 5:30 pm    Post subject: Reply with quote

I think the only way for me to get help on this is if one of you smart linux gurus WOULD TRY IT FOR YOUR SELF.

:)

So you can see whats going on here. I know why it is not working now but i don't know how to solve it. The X server is starting with the correct resolution but the application started sees a smaller resolution than X is actually set for.

For example if i start dwm and launch surf after, i can even close dwm and surf stays at the correct resolution.

There is no display errors, or driver issues. The window it self is not showing at the correct size inside of X.

If i launch just about any wm it will start just fine. The other parts of the screen are also accessible to the mouse and other applications.

The applications launched are not utilizing the full resolution of the X server and i know this is just because of lack of configuration.

For example dwm is able to use the correct resolution of x server, if i knew a little more coding i would solve this my self.

Can someone please just drop down into a tty and just attempt to use startx with surf added to .xinitrc file? so you guys can see what iam talking about.
Back to top
View user's profile Send private message
ff11
l33t
l33t


Joined: 10 Mar 2014
Posts: 657

PostPosted: Sun Mar 08, 2020 5:53 pm    Post subject: Reply with quote

finalturismo wrote:
Can someone please just drop down into a tty and just attempt to use startx with surf added to .xinitrc file? so you guys can see what iam talking about.

Sorry, I don't want to install the "surf".
Have you try the "$HOME/.Xdefaults" ? with something like:
Code:
Surf*geometry: 1920x1080

or
Code:
Surf*mainWin.geometry: 1920x1080


EDIT1: Or even something like xdotool ?
Code:
xdotool search --name "window name" windowsize 1920 1080[

_________________
| Proverbs 26:12 |
| There is more hope for a fool than for a wise man that are wise in his own eyes. |
* AlphaGo - The Movie - Full Documentary
"I want to apologize for being so powerless" - Lee
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 47037
Location: 56N 3W

PostPosted: Sun Mar 08, 2020 6:11 pm    Post subject: Reply with quote

finalturismo,

Xorg does not start with the correct resolution.

Code:
[   767.647] (II) modeset(0): Using exact sizes for initial modes
[   767.647] (II) modeset(0): Output VGA-1 using initial mode 1600x900 +0+0


It starts at 1600x900

What is the native resolution of your display?
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
finalturismo
Apprentice
Apprentice


Joined: 06 Jan 2020
Posts: 164

PostPosted: Sun Mar 08, 2020 7:21 pm    Post subject: Reply with quote

ff11 wrote:
finalturismo wrote:
Can someone please just drop down into a tty and just attempt to use startx with surf added to .xinitrc file? so you guys can see what iam talking about.

Sorry, I don't want to install the "surf".
Have you try the "$HOME/.Xdefaults" ? with something like:
Code:
Surf*geometry: 1920x1080

or
Code:
Surf*mainWin.geometry: 1920x1080


EDIT1: Or even something like xdotool ?
Code:
xdotool search --name "window name" windowsize 1920 1080[


surf ignores geometry commands from what iam seeing.

I tried xdotool but it does not seem to be picking up any window titles.

same goes for wmctrl.
Back to top
View user's profile Send private message
ff11
l33t
l33t


Joined: 10 Mar 2014
Posts: 657

PostPosted: Sun Mar 08, 2020 7:30 pm    Post subject: Reply with quote

finalturismo wrote:

surf ignores geometry commands from what iam seeing.

I tried xdotool but it does not seem to be picking up any window titles.

same goes for wmctrl.

You can use "--pid PID" with xdotool (take a look at manpage of it).
_________________
| Proverbs 26:12 |
| There is more hope for a fool than for a wise man that are wise in his own eyes. |
* AlphaGo - The Movie - Full Documentary
"I want to apologize for being so powerless" - Lee
Back to top
View user's profile Send private message
Banana
l33t
l33t


Joined: 21 May 2004
Posts: 748
Location: Germany

PostPosted: Mon Mar 09, 2020 8:04 am    Post subject: Reply with quote

finalturismo wrote:

I really want to get to the bottom of this , because iam trying to make a minimalist system with the least amount of packages possible to boot into a web based kiosk that accesses the internal web server.

Gentoo is the perfect solution for this , with its use flag system and ability to build your own kernel. Should be rock solid when finished , if my n00b self can manage to get past this issue XD


Did you look into making a boot CD/USB with those settings? Like a kiosk mode usb stick?
_________________
My personal space
Back to top
View user's profile Send private message
finalturismo
Apprentice
Apprentice


Joined: 06 Jan 2020
Posts: 164

PostPosted: Mon Mar 09, 2020 4:44 pm    Post subject: Reply with quote

Banana wrote:
finalturismo wrote:

I really want to get to the bottom of this , because iam trying to make a minimalist system with the least amount of packages possible to boot into a web based kiosk that accesses the internal web server.

Gentoo is the perfect solution for this , with its use flag system and ability to build your own kernel. Should be rock solid when finished , if my n00b self can manage to get past this issue XD


Did you look into making a boot CD/USB with those settings? Like a kiosk mode usb stick?


That is the next issue i will be tackling, the system is already built and pretty much good to go. Right now iam working on cutting down the system to as small as possible. This might take some time because iam still learning Linux a bit my self.

In fact i will be making a thread on what utilities i can use to make a live USB and an installation USB.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 47037
Location: 56N 3W

PostPosted: Mon Mar 09, 2020 4:47 pm    Post subject: Reply with quote

finalturismo,

Code:
emerge catalyst
That's the tool used to build all the Gentoo media.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
finalturismo
Apprentice
Apprentice


Joined: 06 Jan 2020
Posts: 164

PostPosted: Mon Mar 09, 2020 5:10 pm    Post subject: Reply with quote

NeddySeagoon wrote:
finalturismo,

Code:
emerge catalyst
That's the tool used to build all the Gentoo media.


Thank you sir!
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum