I have installed Xorg*, lightdm, and xfce4
The only log I can find is lightdm's, and the pertinant errors seems to be:
failed to launch plymouth
and
Can't launch X server X not found in path
Whats next?
Thanks all
Cheers, Gene
Well, I managed to get myself locked out, as in despite having power, my wireless mouse and keyboard were not available to X so I was stuck looking at a useless X login screen. I suspect I was missing an X package.
This all took place while I was trying to get an
=======
auto eth0
iface eth0 inet static
address xx.xx.xx.xx/24
gateway xx.xx.xx.xx
======
configuration to actually give me a gateway address in the routing tables.
To make that work, I had to rm /etc/resolv.conf until it was truly gone, then compose my own and make it immutable so dhcpd couldn't clear it out despite the eth0 file plainly saying it was static.
But to make the gateway address stick, I had to have both:
gateway xx.xx.xx.xx
and
up route add default gw xx.xx.xx.xx
in the eth0 file, remove either and I get no gateway in the routing table shown by route -n.
So thats fixed. But I had to start with a newly built image, it was not possible to add it to the stretch-minimal-rock64-0.5.10-118-arm64.img, but I found it was dated, and dl'd stretch-minimal-rock64-0.5.13-130-arm64.img, which with the above doubled entries in the eth0 file, is working without the after lokgin, route add monkey business. Thanks for that.
Now I need an rt-preempt kernel to run the app that this rock64 is destined to run. Any chance of that?
And to do that, I need X, something in the LXDE or xfce4 territory. Is there a meta file that will install it all in one swell foop?
I have a USB-3, terabyte Seagate drive plugged into the USB-3 port, which doesn't seem to affect the USB2 power, and its currently running on a 2.5 amp wal wart stolen from an r- pi 3b fed to pins 2 and 8 on the aux header. Nothing on the drive yet. Just testing the psu.
I keep checking the store, but the heat sinks have not appeared yet. Running quite cool w/o it, but its not doing much yet.
.
Thanks everybody for answers to my 2 questions above.
"/usr/local/sbin/install_desktop.sh mate" desktop needs a new ubuntu entry in /etc/apt/sources.list.
Example deb line plz?
Thanks all.
I am using ayufan' s debian stretch image for weeks. Installed X, lightdm and fluxbox. Works great, even hw-videoplayback with gst-launch for supported codecs. Don't see you installed any greeter for lightdm, perhaps you missed that?
I installed lightdm-gtk-greeter, should work with xfce4, too. I am not using the Mate stuff, would have choosen another image if I wanted that.
10-04-2017, 12:15 AM
(This post was last modified: 10-04-2017, 01:36 AM by MarkHaysHarris777.)
I wound up doing a tasksel LXDE. I can still do a remote login using ssh -Y rock64@rock64Sheldon which is its alias in the /etc/hosts file.
I don't recall now if I can login locally, I've spent since last Friday trying to get my rider to run as the place has turned into a jungle. Carb full of crap, no high speed jets, blocked off by crappy fuel deposits. It took a 1.5 hour soaking and agitation in 20 minute carb cleaner.
I just checked, lightdm-gtk-greeter is installed and that must be what I am looking at.
Looking at dmesg, both wireless mouse and wireless keyboard are found, but apparently not found by X, hence I cannot login locally. Looking at /var/log/Xorg.0.log now. From that its finding more than one keyboard and mouse!
Code: [ 19.941] (II) input device 'rk8xx_pwrkey', /dev/input/event0 is tagged by udev as: Keyboard
[ 19.941] (II) input device 'rk8xx_pwrkey', /dev/input/event0 is a keyboard
[ 19.958] (**) Option "config_info" "udev:/sys/devices/platform/ff160000.i2c/i2c-1/1-0018/input/input0/event0"
[ 19.958] (II) XINPUT: Adding extended input device "rk8xx_pwrkey" (type: KEYBOARD, id 6)
[ 19.958] (**) Option "xkb_model" "pc105"
[ 19.958] (**) Option "xkb_layout" "us"
[ 19.961] (II) input device 'rk8xx_pwrkey', /dev/input/event0 is tagged by udev as: Keyboard
[ 19.961] (II) input device 'rk8xx_pwrkey', /dev/input/event0 is a keyboard
[ 19.964] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event1)
[ 19.964] (**) Logitech USB Receiver: Applying InputClass "libinput pointer catchall"
[ 19.964] (II) Using input driver 'libinput' for 'Logitech USB Receiver'
[ 19.964] (**) Logitech USB Receiver: always reports core events
[ 19.964] (**) Option "Device" "/dev/input/event1"
[ 19.964] (**) Option "_source" "server/udev"
[ 20.017] (II) input device 'Logitech USB Receiver', /dev/input/event1 is tagged by udev as: Mouse
[ 20.017] (II) input device 'Logitech USB Receiver', /dev/input/event1 is a pointer caps
[ 20.029] (**) Option "config_info" "udev:/sys/devices/platform/ff580000.usb/usb1/1-1/1-1:1.0/0003:046D:C52F.0001/input/input1/event1"
[ 20.029] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: MOUSE, id 7)
[ 20.030] (**) Option "AccelerationScheme" "none"
[ 20.030] (**) Logitech USB Receiver: (accel) selected scheme none/0
[ 20.030] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[ 20.030] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[ 20.083] (II) input device 'Logitech USB Receiver', /dev/input/event1 is tagged by udev as: Mouse
[ 20.083] (II) input device 'Logitech USB Receiver', /dev/input/event1 is a pointer caps
[ 20.085] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event2)
[ 20.085] (**) Logitech USB Receiver: Applying InputClass "libinput keyboard catchall"
[ 20.085] (II) Using input driver 'libinput' for 'Logitech USB Receiver'
[ 20.085] (**) Logitech USB Receiver: always reports core events
[ 20.085] (**) Option "Device" "/dev/input/event2"
[ 20.085] (**) Option "_source" "server/udev"
[ 20.087] (II) input device 'Logitech USB Receiver', /dev/input/event2 is tagged by udev as: Keyboard
[ 20.087] (II) input device 'Logitech USB Receiver', /dev/input/event2 is a keyboard
[ 20.105] (II) libinput: Logitech USB Receiver: needs a virtual subdevice
[ 20.105] (**) Option "config_info" "udev:/sys/devices/platform/ff580000.usb/usb1/1-1/1-1:1.1/0003:046D:C52F.0002/input/input2/event2"
[ 20.105] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: MOUSE, id 8)
[ 20.105] (**) Option "AccelerationScheme" "none"
[ 20.105] (**) Logitech USB Receiver: (accel) selected scheme none/0
[ 20.105] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[ 20.105] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[ 20.107] (II) input device 'Logitech USB Receiver', /dev/input/event2 is tagged by udev as: Keyboard
[ 20.107] (II) input device 'Logitech USB Receiver', /dev/input/event2 is a keyboard
[ 20.109] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event3)
[ 20.109] (**) Logitech USB Receiver: Applying InputClass "libinput keyboard catchall"
[ 20.109] (II) Using input driver 'libinput' for 'Logitech USB Receiver'
[ 20.109] (**) Logitech USB Receiver: always reports core events
[ 20.109] (**) Option "Device" "/dev/input/event3"
[ 20.109] (**) Option "_source" "server/udev"
[ 20.111] (II) input device 'Logitech USB Receiver', /dev/input/event3 is tagged by udev as: Keyboard
[ 20.112] (II) input device 'Logitech USB Receiver', /dev/input/event3 is a keyboard
[ 20.123] (**) Option "xkb_model" "pc105"
[ 20.123] (**) Option "xkb_layout" "us"
[ 20.125] (II) input device 'Logitech USB Receiver', /dev/input/event3 is tagged by udev as: Keyboard
[ 20.125] (II) input device 'Logitech USB Receiver', /dev/input/event3 is a keyboard
[ 20.127] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event4)
[ 20.128] (**) Logitech USB Receiver: Applying InputClass "libinput pointer catchall"
[ 20.128] (**) Logitech USB Receiver: Applying InputClass "libinput keyboard catchall"
[ 20.128] (II) Using input driver 'libinput' for 'Logitech USB Receiver'
[ 20.128] (**) Logitech USB Receiver: always reports core events
[ 20.128] (**) Option "Device" "/dev/input/event4"
[ 20.128] (**) Option "_source" "server/udev"
[ 20.130] (II) input device 'Logitech USB Receiver', /dev/input/event4 is tagged by udev as: Keyboard Mouse
[ 20.130] (II) input device 'Logitech USB Receiver', /dev/input/event4 is a pointer caps
[ 20.130] (II) input device 'Logitech USB Receiver', /dev/input/event4 is a keyboard
[ 20.142] (II) libinput: Logitech USB Receiver: needs a virtual subdevice
[ 20.142] (**) Option "config_info" "udev:/sys/devices/platform/ff5d0000.usb/usb3/3-1/3-1:1.1/0003:046D:C52B.0004/input/input4/event4"
[ 20.142] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: MOUSE, id 10)
[ 20.142] (**) Option "AccelerationScheme" "none"
[ 20.142] (**) Logitech USB Receiver: (accel) selected scheme none/0
[ 20.142] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[ 20.142] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[ 20.144] (II) input device 'Logitech USB Receiver', /dev/input/event4 is tagged by udev as: Keyboard Mouse
[ 20.144] (II) input device 'Logitech USB Receiver', /dev/input/event4 is a pointer caps
[ 20.144] (II) input device 'Logitech USB Receiver', /dev/input/event4 is a keyboard
[ 20.158] (**) Logitech USB Receiver: Applying InputClass "libinput keyboard catchall"
[ 20.158] (II) Using input driver 'libinput' for 'Logitech USB Receiver'
[ 20.158] (**) Logitech USB Receiver: always reports core events
[ 20.158] (**) Option "Device" "/dev/input/event2"
[ 20.158] (**) Option "_source" "_driver/libinput"
[ 20.158] (II) libinput: Logitech USB Receiver: is a virtual subdevice
[ 20.159] (**) Option "config_info" "udev:/sys/devices/platform/ff580000.usb/usb1/1-1/1-1:1.1/0003:046D:C52F.0002/input/input2/event2"
[ 20.159] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 11)
[ 20.159] (**) Option "xkb_model" "pc105"
[ 20.159] (**) Option "xkb_layout" "us"
[ 20.159] (**) Logitech USB Receiver: Applying InputClass "libinput pointer catchall"
[ 20.160] (**) Logitech USB Receiver: Applying InputClass "libinput keyboard catchall"
[ 20.160] (II) Using input driver 'libinput' for 'Logitech USB Receiver'
[ 20.160] (**) Logitech USB Receiver: always reports core events
[ 20.160] (**) Option "Device" "/dev/input/event4"
[ 20.160] (**) Option "_source" "_driver/libinput"
[ 20.160] (II) libinput: Logitech USB Receiver: is a virtual subdevice
[ 20.160] (**) Option "config_info" "udev:/sys/devices/platform/ff5d0000.usb/usb3/3-1/3-1:1.1/0003:046D:C52B.0004/input/input4/event4"
[ 20.160] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 12)
[ 20.160] (**) Option "xkb_model" "pc105"
[ 20.160] (**) Option "xkb_layout" "us"
And it continues as if in a loop till its out of resources. I think its all pasted in above.
So, how is this to be fixed? Seems like 1 keyboard and one mouse is all it should need, and whats plugged in works fine when X is not running.
The 2nd question is, how fast can the rock64's gpio run, on the pi3 its writing at 33 megahertz, and reading at 25 megahertz, and similar speeds are needed for the application this is being built to run. That is LinuxCNC.
Thanks for any help with the overzealous input discovery. X is not my forte obviously.
Cheers, gene83
edit: added code block mhh
(10-03-2017, 05:15 AM)RockyBoulder Wrote: I am using ayufan' s debian stretch image for weeks. Installed X, lightdm and fluxbox. Works great, even hw-videoplayback with gst-launch for supported codecs. Don't see you installed any greeter for lightdm, perhaps you missed that?
I installed lightdm-gtk-greeter, should work with xfce4, too. I am not using the Mate stuff, would have choosen another image if I wanted that.
Here's what I did to get an LXDE desktop working on the latest stretch image:
sudo apt-get install --no-install-recommends xserver-xorg
sudo apt-get install --no-install-recommends xinit
sudo apt-get install lxde-core lxappearance
sudo apt-get install lightdm
sudo nano /etc/lightdm/lightdm.conf, and set the auto-login user
I did all the LXDE install. But the auto-login looks promising because at present, if the blanker times out, it locks the screen and I am looking at the login-greeter. But nothing I have entered in the greeter is accepted to unlock the screen, so I have been forced to reboot to get a working greeter again. So I have learned that if I have to leave it un-used for the timeout, save my work before walking away. Good practice, but still a right PITA.
Thanks dontpostalot
Cheers gene83.
Not sure if it applies or if it makes any sense but I did an apt-get xscreensaver to prevent it from autologging me out, it's running quite stable for me now.
(10-03-2017, 05:15 AM)RockyBoulder Wrote: I am using ayufan' s debian stretch image for weeks. Installed X, lightdm and fluxbox. Works great, even hw-videoplayback with gst-launch for supported codecs. Don't see you installed any greeter for lightdm, perhaps you missed that?
I installed lightdm-gtk-greeter, should work with xfce4, too. I am not using the Mate stuff, would have choosen another image if I wanted that.
|
