Page 2 of 4
trying xorg-autoconf 2.1
Posted: Mon 02 Mar 2020, 20:04
by foxpup
I have tried xorg-autoconf 2.1. It chooses the modesetting driver.
But I lose keyboard and mouse with it (cursor in the middle of screen), so unable to do anything.
Posted: Mon 02 Mar 2020, 22:28
by mistfire
@foxpup may I see the generated xorg.conf made by xorg-autoconf?
Posted: Tue 03 Mar 2020, 10:53
by mistfire
I found something weird. Ubuntu uses modesetting driver with glamor acceleration for later intel gpu.
@foxpup
May I see also the Xorg.0.log when you lost the keyboard and mouse upon using the generated xorg.conf made by xorg-autoconf?
Posted: Tue 03 Mar 2020, 13:25
by foxpup
mistfire wrote:I found something weird. Ubuntu uses modesetting driver with glamor acceleration for later intel gpu.
@foxpup
May I see also the Xorg.0.log when you lost the keyboard and mouse upon using the generated xorg.conf made by xorg-autoconf?
I am not near the machine, but later, in the evening ... .
Just thinking how i can get the xorg log if I cannot do anything with mouse and keyboard?!
Any good idea? Maybe add a script in Startup to cp it?
(I have to shut down with the button.)
You are right about the glamor acceleration.
Stretch is not ubuntu but (old) debian, by the way.
Posted: Tue 03 Mar 2020, 15:41
by mistfire
foxpup wrote:mistfire wrote:I found something weird. Ubuntu uses modesetting driver with glamor acceleration for later intel gpu.
@foxpup
May I see also the Xorg.0.log when you lost the keyboard and mouse upon using the generated xorg.conf made by xorg-autoconf?
I am not near the machine, but later, in the evening ... .
Just thinking how i can get the xorg log if I cannot do anything with mouse and keyboard?!
Any good idea? Maybe add a script in Startup to cp it?
(I have to shut down with the button.)
How about after you reproduce that error, revert back to a working xorg.conf then start X again. Then post the contents of /var/log/Xorg.0.log.old here?
Posted: Tue 03 Mar 2020, 19:18
by foxpup
Thanx for the tip, @mistfire.
Done.
Posted: Tue 03 Mar 2020, 19:30
by enrique
foxpup
Puppy save files are just images of a partition. Think of them like a disk on a file. So what you have to do is move that save file to a new location. Then boot and save a new one. Now that you have a working puppy, Use it to mount the last save. Some puppy may even allow to mount the partition with double click. But lets do it manually.
Let say you old puppy save was "bionicpup64save.4fs".
*move to the location where your old "bionicpup64save.4fs" is
#cd [your location]
*Create a folder where to mount:
#mkdir /tmp/mnt
*Now mount "bionicpup64save.4fs"
#mount bionicpup64save.4fs /tmp/mnt
Now you can access you old files. Just remember that your old /etc/X11/xorg.conf is now at /tmp/mnt/etc/X11/xorg.conf
Do any changes you need to do. Then close the old puppy save by doing
#unmount /tmp/mnt
And move again your "bionicpup64save.4fs back to the puppy folder.
Simple.
Posted: Wed 04 Mar 2020, 08:10
by mistfire
@foxpup
I analyzed your xorg log that you sent to me
Here is the reason why mouse and keyboard dont work. Look at this part
Code: Select all
[ 17.636] (II) LoadModule: "mouse"
[ 17.637] (WW) Warning, couldn't open module mouse
[ 17.637] (II) UnloadModule: "mouse"
[ 17.637] (II) Unloading mouse
[ 17.637] (EE) Failed to load module "mouse" (module does not exist, 0)
[ 17.637] (II) LoadModule: "kbd"
[ 17.638] (WW) Warning, couldn't open module kbd
[ 17.638] (II) UnloadModule: "kbd"
[ 17.638] (II) Unloading kbd
[ 17.638] (EE) Failed to load module "kbd" (module does not exist, 0)
Also on this part of your log.
Code: Select all
[ 19.509] (**) Mouse0: always reports core events
[ 19.509] (**) Option "Device" "/dev/mouse"
[ 19.509] (EE) Failed to look up path '/dev/input/mice'
[ 19.509] (II) opening input device '/dev/input/mice' failed (No such device).
[ 19.509] (II) failed to create input device '/dev/input/mice'.
[ 19.509] (EE) libinput: Mouse0: Failed to create a device for /dev/mouse
[ 19.509] (EE) PreInit returned 2 for "Mouse0"
[ 19.509] (II) UnloadModule: "libinput"
[ 19.509] (II) LoadModule: "kbd"
[ 19.510] (WW) Warning, couldn't open module kbd
[ 19.510] (II) UnloadModule: "kbd"
[ 19.510] (II) Unloading kbd
[ 19.510] (EE) Failed to load module "kbd" (module does not exist, 0)
[ 19.510] (EE) No input driver matching `kbd'
[ 19.510] (II) Falling back to input driver `libinput'
[ 19.510] (II) Using input driver 'libinput' for 'Keyboard0'
[ 19.510] (**) Option "CoreKeyboard"
[ 19.510] (**) Keyboard0: always reports core events
May I see your working xorg.conf? I think you don't have xf86-input-keyboard and xf86-input-mouse on your system. Only libinput that's why your keyboard and mouse don't work.
Also may I see the contents of /dev/input/ in your system
Posted: Wed 04 Mar 2020, 19:43
by foxpup
mistfire wrote:May I see your working xorg.conf? I think you don't have xf86-input-keyboard and xf86-input-mouse on your system. Only libinput that's why your keyboard and mouse don't work.
Also may I see the contents of /dev/input/ in your system
PPM says xserver-xorg-input-mouse and xserver-xorg-input-kbd (and others) are already installed.
But I do not find kbd_drv.so, mouse_drv.so ...
Maybe I should install anyway (for real) and test?
Posted: Wed 04 Mar 2020, 19:57
by foxpup
@enrique
Thanx for explaining.
I use pupsave directories and I do work with them with ease.
I think you miss the point here.
The point is, when I cannot do anything anymore I shut down pressing the start button a long time (10 seconds?) and nothing is saved to the pupsave.
I don't think the solution mistfire suggested would have worked either.
I just discovered that pressing the start button for 1 second, maybe 2, the option to save came up.
I even had my keyboard back!
Posted: Wed 04 Mar 2020, 20:05
by enrique
You are correct.
Posted: Thu 05 Mar 2020, 03:47
by mistfire
@foxpup
right now I'm modifying xorg-autoconf that allows to use evdev or libinput if xf86-input-keyboard or xf86-input-mouse is not found. Based on your Xorg log. modesetting with glamor works. But the mouse and keyboard is only the problem
Posted: Thu 05 Mar 2020, 03:48
by mistfire
Reserved
Posted: Thu 05 Mar 2020, 09:12
by foxpup
mistfire wrote:@foxpup
right now I'm modifying xorg-autoconf that allows to use evdev or libinput if xf86-input-keyboard or xf86-input-mouse is not found. Based on your Xorg log. modesetting with glamor works. But the mouse and keyboard is only the problem
Can you not find that in Xorgwizard?
I am a total noob here, sorry
Posted: Thu 05 Mar 2020, 10:37
by mistfire
@foxpup can you please try the latest version that I uploaded (located at the first post of this thread)? I added handling of input devices. If xorg mouse driver and xorg keyboard is missing it will use evdev otherwise it will use libinput if evdev is missing
Posted: Thu 05 Mar 2020, 20:26
by foxpup
Sorry, it did not get to X.
Posted: Fri 06 Mar 2020, 05:34
by williams2
X started with new xorg.conf auto generated by PuppyOS. (no errors)
X started with a blank xorg.conf file (no errors)
X would not start using xorg-autoconf-2.2.pet
http://s000.tinyupload.com/index.php?fi ... 7754539922
Posted: Fri 06 Mar 2020, 06:50
by mistfire
@williams2 and @foxpup
Thanks for reporting report. I found the problem. Since both of you are using evdev and libinput. The InputDevice line on ServerLayout section must be removed or disabled. So I apply a fix that InputDevice line on ServerLayout will be disabled if evdev or libinput was used as xorg driver for input devices.
Please test the xorg-autoconf-2.2.1 to see if the fixes that I applied works.
Posted: Fri 06 Mar 2020, 08:53
by williams2
xorg-autoconf-2.2.1:
video display works.
No mouse, no touchpad, no keyboard.
http://s000.tinyupload.com/index.php?fi ... 3511321953
Posted: Fri 06 Mar 2020, 09:26
by mistfire
Thanks @williams
No mouse, no touchpad, no keyboard occured because AutoAdd is disabled. It seems that we need a better detection whether AutoAdd must be enable or disabled. Because some xorg freezes if AutoAdd is enabled.