(05-19-2020, 09:49 AM)JaredT66 Wrote: I'm having an issue getting the graphical boot to start. I can log into the console (ALT-F1) just fine, but the graphical boot just cycles over and over. Anyone else run into this?
Yes, that happened to me about a month ago, both with buster and bullseye (arm64, encrypted disk). I selected the MATE desktop environment, which I prefer to the default GNOME 3 one.
I tried looking at the system log (with `journalctl`) and at several other log files under `/var/log`, but to no avail.
I just tried right now with the default GNOME 3 desktop environment and I do not experience that issue anymore (tried both with buster and bullseye, arm64 and encrypted disk).
Interesting, I tried with both XFCE and Cinnamon. It seems to be a lightdm issue, here is from the /var/log/Xorg.0.log file:
[ 846.860] (II) event1 - gpio-keys: device is a switch device
[ 848.431] (II) event0 - HAILUCK CO.,LTD USB KEYBOARD: device removed
[ 848.490] (II) event3 - HAILUCK CO.,LTD USB KEYBOARD Touchpad: device removed
[ 848.590] (II) event4 - HAILUCK CO.,LTD USB KEYBOARD System Control: device removed
[ 848.650] (II) event5 - HAILUCK CO.,LTD USB KEYBOARD Consumer Control: device removed
[ 848.770] (II) event8 - HAILUCK CO.,LTD USB KEYBOARD Wireless Radio Control: device removed
[ 848.910] (II) event2 - HAILUCK CO.,LTD USB KEYBOARD Mouse: device removed
[ 849.020] (II) event6 - USB Camera: USB Camera: device removed
[ 849.130] (II) event1 - gpio-keys: device removed
[ 849.170] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 1939.518] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 1939.613] (II) event0 - HAILUCK CO.,LTD USB KEYBOARD: is tagged by udev as: Keyboard
[ 1939.614] (II) event0 - HAILUCK CO.,LTD USB KEYBOARD: device is a keyboard
[ 1939.623] (II) event3 - HAILUCK CO.,LTD USB KEYBOARD Touchpad: is tagged by udev as: Touchpad
[ 1939.628] (II) event3 - HAILUCK CO.,LTD USB KEYBOARD Touchpad: device is a touchpad
[ 1939.634] (II) event4 - HAILUCK CO.,LTD USB KEYBOARD System Control: is tagged by udev as: Keyboard
[ 1939.635] (II) event4 - HAILUCK CO.,LTD USB KEYBOARD System Control: device is a keyboard
[ 1939.640] (II) event5 - HAILUCK CO.,LTD USB KEYBOARD Consumer Control: is tagged by udev as: Keyboard
[ 1939.640] (II) event5 - HAILUCK CO.,LTD USB KEYBOARD Consumer Control: device is a keyboard
[ 1939.645] (II) event8 - HAILUCK CO.,LTD USB KEYBOARD Wireless Radio Control: is tagged by udev as: Keyboard
[ 1939.646] (II) event8 - HAILUCK CO.,LTD USB KEYBOARD Wireless Radio Control: device is a keyboard
[ 1939.651] (II) event2 - HAILUCK CO.,LTD USB KEYBOARD Mouse: is tagged by udev as: Mouse
[ 1939.652] (II) event2 - HAILUCK CO.,LTD USB KEYBOARD Mouse: device is a pointer
[ 1939.656] (II) event6 - USB Camera: USB Camera: is tagged by udev as: Keyboard
[ 1939.657] (II) event6 - USB Camera: USB Camera: device is a keyboard
[ 1939.659] (II) event1 - gpio-keys: is tagged by udev as: Keyboard Switch
[ 1939.659] (II) event1 - gpio-keys: device is a keyboard
[ 1939.659] (II) event1 - gpio-keys: device is a switch device
[ 1939.809] (EE)
[ 1939.809] (EE) Backtrace:
[ 1939.810] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x188) [0xaaaad4f2f6c0]
[ 1939.810] (EE) unw_get_proc_info failed: no unwind info found [-10]
[ 1939.810] (EE)
[ 1939.810] (EE) Segmentation fault at address 0xaadaec443a88
[ 1939.810] (EE)
Fatal server error:
[ 1939.810] (EE) Caught signal 11 (Segmentation fault). Server aborting
Tried using the Gnome desktop and still no luck, only thing that seems I'm not 100% sure on is which keyboard to select, is one of the generic ones the option that works best? I would think that shouldn't be an issue since everything works in the console.
I'll keep playing with it.
(05-19-2020, 09:25 PM)JaredT66 Wrote: I'm not 100% sure on is which keyboard to select, is one of the generic ones the option that works best?
Now that you mention that, in my successful installs I also specified, in the Debian setup dialogue windows:
* English (UK) keyboard layout (I have the ISO keyboard)
* Generic 105 keyboard
* No extra locales generated
In my previous attempts, I selected some extra locales (en_UK-UTF8 and en_US-UTF8). Perhaps that was the reason `lightdm` got confused ...
All right, So. pulled the latest installer, ran it. (downloading packages before installation took 3+ hours!)
and, I've got debian bullseye installed to an sd card, however:
I've got a couple problems atm.
boot never gets a gui, the debian gui logo appears, then flashes a curser icon in upper left, then mouse arrow flashes in center of blank screen, then flashes cursor icon in upper left. ad infinitum.
I can Ctrl F1 and log in, however, can't get wifi to do a thing, so can't manipulate anything.
Sudo works, but there was no option to create a root user, as all normal debian installs do.
How do I create a root user in bash shell, and
How do I configure and activate wifi in bash?
I chose debian-desktop, xfce4, and laptop in taskselect in installation.
I just finished re-reading this entire thread while running the installation
TIA.
I've gotten GUI to work by following the steps in
https://forum.pine64.org/showthread.php?...6#pid58436
Important note, ended up using the slightly modified version that Jordon posted on his github to make it get all the way through:
https://forum.pine64.org/showthread.php?...6#pid61256
05-20-2020, 02:41 PM
(This post was last modified: 05-20-2020, 05:47 PM by jazzmans.)
(05-20-2020, 11:24 AM)JaredT66 Wrote: I've gotten GUI to work by following the steps in
https://forum.pine64.org/showthread.php?...6#pid58436
Important note, ended up using the slightly modified version that Jordon posted on his github to make it get all the way through:
https://forum.pine64.org/showthread.php?...6#pid61256
How did you get your wifi working to do this? [edit to answer]
nmcli device wifi list
nmcli device wifi connect "SSID" password "password"
[enter the ssid in double quotes, and the password in the other double quotes keeping the double quotes for both.]
[end edit for wifi]
edit to add;
I had to go into /etc/hosts and enter my hostname there.
I had to add after localhost
127.0.0.1 hostname
[end hosts edit]
# rather then just reply again and again, I'm just going to re-edit this post as I get through various obstacles,
Any Ideas on how to create a root user? using sudo is not normal for me, I'm a debian guy
working on graphics now... what a pita. thanks.
[end edit]
(05-20-2020, 02:41 PM)jazzmans Wrote: How did you get your wifi working to do this? Search this topic for 'nmcli'.
This message was created with 100% recycled electrons
05-20-2020, 05:38 PM
(This post was last modified: 05-20-2020, 08:28 PM by jazzmans.)
(05-20-2020, 04:58 PM)moonwalkers Wrote: (05-20-2020, 02:41 PM)jazzmans Wrote: How did you get your wifi working to do this? Search this topic for 'nmcli'. That was simple, although I have no idea how to search this forum, so I just google searched nmcli. Thanks!
nmcli device wifi list
nmcli device wifi connect "SSID" password "password"
[enter the ssid in double quotes, and the password in the other double quotes.]
For future reference for others.
Now gonna work on the gui.
[edit to add after trying]
startx didn't work, but a reboot seems to have worked! (I hate having to reboot a machine)
haven't done much with it yet, but there's a working desktop! yaay.
None of the hotkeys work, for example, to lower or raise screen brightness, how do I re-enable this?
I'm using XFCE4, cause I always use Xfce4, under keyboards it's set to generic 104-key PC.this is an ansi keyboard.
i use pinebookpro-post-install from manjaro and brightnessctl +brightness-udev, then map the buttons in sway
|
