LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM
Reload this Page Slackware on a pinebook pro
User Name
Password
Slackware - ARM This forum is for the discussion of Slackware ARM.

Notices


Reply
Page 12 of 12 « First 21011 12
  Search this Thread
Old 01-15-2021, 08:58 AM   #166
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,918

Rep: Reputation: Disabled

Hi wowbaggerHU,

found a solution to remove packages
xf86-input-evdev
xf86-input-mouse
and leave xf86-input-libinput
Last edited by sndwvs; 01-15-2021 at 08:59 AM.
 
Old 01-15-2021, 11:39 AM   #167
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 288

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
found a solution to remove packages
xf86-input-evdev
xf86-input-mouse
and leave xf86-input-libinput
Hi sndwvs,

I removed the packages you asked for. Unfortunately the mouse still doesn't show up as a new input device in the xinput output, even though it's connected properly through Bluetooth:
Code:
$ xinput
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ HAILUCK CO.,LTD USB KEYBOARD Mouse      	id=7	[slave  pointer  (2)]
⎜   ↳ HAILUCK CO.,LTD USB KEYBOARD Touchpad   	id=8	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ HAILUCK CO.,LTD USB KEYBOARD            	id=6	[slave  keyboard (3)]
    ↳ HAILUCK CO.,LTD USB KEYBOARD System Control	id=9	[slave  keyboard (3)]
    ↳ HAILUCK CO.,LTD USB KEYBOARD Consumer Control	id=10	[slave  keyboard (3)]
    ↳ HAILUCK CO.,LTD USB KEYBOARD Wireless Radio Control	id=11	[slave  keyboard (3)]
    ↳ USB Camera: USB Camera                  	id=12	[slave  keyboard (3)]
    ↳ gpio-key-power                          	id=13	[slave  keyboard (3)]
Edited to add: the following errors still show up in syslog, although no error is shown in bluetoothctl and the bluetooth applet of Xfce.
Code:
Jan 15 18:50:38 janos-pbp bluetoothd[1042]: src/service.c:service_accept() input-hog profile accept failed for EB:18:DD:31:F7:41
Jan 15 18:50:38 janos-pbp bluetoothd[1042]: profiles/deviceinfo/deviceinfo.c:read_pnpid_cb() Error reading PNP_ID value: Attribute requires authentication before read/write
Last edited by wowbaggerHU; 01-15-2021 at 12:00 PM.
 
Old 01-15-2021, 11:49 AM   #168
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,918

Rep: Reputation: Disabled
the gentoo wiki says to enable UserspaceHID=true and IdleTimeout=0 in /etc/bluetooth/input.conf
and change /etc/bluetooth/main.conf AutoEnable=true
Last edited by sndwvs; 01-15-2021 at 12:13 PM. Reason: update info
 
1 members found this post helpful.
Old 01-15-2021, 12:07 PM   #169
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 288

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
the gentoo wiki says to enable UserspaceHID=true in /etc/bluetooth/input.conf
Thank you sndwvs! That seems to have done the trick!
Code:
janos@janos-pbp:~$ xinput 
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ HAILUCK CO.,LTD USB KEYBOARD Mouse      	id=7	[slave  pointer  (2)]
⎜   ↳ HAILUCK CO.,LTD USB KEYBOARD Touchpad   	id=8	[slave  pointer  (2)]
⎜   ↳ BluetoothMouse3600 Consumer Control     	id=14	[slave  pointer  (2)]
⎜   ↳ BluetoothMouse3600 Mouse                	id=16	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ HAILUCK CO.,LTD USB KEYBOARD            	id=6	[slave  keyboard (3)]
    ↳ HAILUCK CO.,LTD USB KEYBOARD System Control	id=9	[slave  keyboard (3)]
    ↳ HAILUCK CO.,LTD USB KEYBOARD Consumer Control	id=10	[slave  keyboard (3)]
    ↳ HAILUCK CO.,LTD USB KEYBOARD Wireless Radio Control	id=11	[slave  keyboard (3)]
    ↳ USB Camera: USB Camera                  	id=12	[slave  keyboard (3)]
    ↳ gpio-key-power                          	id=13	[slave  keyboard (3)]
    ↳ BluetoothMouse3600 Consumer Control     	id=15	[slave  keyboard (3)]
 
Old 02-04-2021, 09:19 AM   #171
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 288

Rep: Reputation: Disabled
I upgraded to the latest kernel, but something broke. It doesn't seem to find the dtb:

Code:
U-Boot TPL 2020.10-rk3399 (Dec 10 2020 - 15:55:26)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...

U-Boot SPL 2020.10-rk3399 (Dec 10 2020 - 15:55:26 +0100)
Trying to boot from MMC2


U-Boot 2020.10-rk3399 (Dec 10 2020 - 15:57:06 +0100)

SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 Pinebook Pro
DRAM:  3.9 GiB
PMIC:  RK808 
MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... Invalid bus 0 (err=-19)
*** Warning - spi_flash_probe_bus_cs() failed, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Pine64 Pinebook Pro
Net:   No ethernet found.
starting USB...
Bus usb@fe380000: failed to get usb phy
Port not available.
Bus usb@fe3a0000: failed to get usb phy
Port not available.
Bus usb@fe3c0000: failed to get usb phy
Port not available.
Bus usb@fe3e0000: failed to get usb phy
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
Hit any key to stop autoboot:  0 
Card did not respond to voltage select!
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
1651 bytes read in 12 ms (133.8 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 0
96 bytes read in 9 ms (9.8 KiB/s)
Failed to load '/dtb/rk3399-pinebook-pro.dtb'
28580352 bytes read in 1254 ms (21.7 MiB/s)
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
8982329 bytes read in 408 ms (21 MiB/s)
Moving Image from 0x2080000 to 0x2200000, end=3de0000
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    8982265 Bytes = 8.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
SCRIPT FAILED: continuing...
PCIe link training gen1 timeout!

Device 0: unknown device
starting USB...
Bus usb@fe380000: failed to get usb phy
Port not available.
Bus usb@fe3a0000: failed to get usb phy
Port not available.
Bus usb@fe3c0000: failed to get usb phy
Port not available.
Bus usb@fe3e0000: failed to get usb phy
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
USB is stopped. Please issue 'usb start' first.
starting USB...
Bus usb@fe380000: failed to get usb phy
Port not available.
Bus usb@fe3a0000: failed to get usb phy
Port not available.
Bus usb@fe3c0000: failed to get usb phy
Port not available.
Bus usb@fe3e0000: failed to get usb phy
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
failed to find ep-gpios property
No ethernet found.
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-rk3399-pinebook-pro-rk3399
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-rk3399
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
No ethernet found.
Config file not found
starting USB...
Bus usb@fe380000: failed to get usb phy
Port not available.
Bus usb@fe3a0000: failed to get usb phy
Port not available.
Bus usb@fe3c0000: failed to get usb phy
Port not available.
Bus usb@fe3e0000: failed to get usb phy
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
failed to find ep-gpios property
No ethernet found.
No ethernet found.
Invalid bus 0 (err=-19)
Failed to initialize SPI flash at 0:0 (error -19)
=>
I will try to look into it tomorrow.
 
Old 02-04-2021, 09:30 AM   #172
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,918

Rep: Reputation: Disabled
check the dtb symlink on dtb-5.10.11
and output ls -l /boot
 
1 members found this post helpful.
Old 02-04-2021, 12:33 PM   #173
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 288

Rep: Reputation: Disabled
Hi sndwvs,

I tried to build the installer image, but it failed after the kernel compilation when it was building the dt files:
Code:
  DTC     arch/arm64/boot/dts/rockchip/rk3399-rockpro64-v2.dtb
  DTC     arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtb
  DTC     arch/arm64/boot/dts/rockchip/rk3399-sapphire-excavator.dtb
  DTC     arch/arm64/boot/dts/rockchip/rk3399-sapphire.dtb
  DTC     arch/arm64/boot/dts/rockchip/rk3399-station-p1.dtb
Error: arch/arm64/boot/dts/rockchip/rk3399-station-p1.dts:24.1-7 syntax error
FATAL ERROR: Unable to parse input tree
  DTC     arch/arm64/boot/dts/rockchip/rk3399pro-rock-pi-n10.dtb
make[2]: *** [scripts/Makefile.lib:332: arch/arm64/boot/dts/rockchip/rk3399-station-p1.dtb] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [scripts/Makefile.build:496: arch/arm64/boot/dts/rockchip] Error 2
make: *** [Makefile:1342: dtbs] Error 2
|err | details      /data/build/images_build_kit/build/source/build.log
 
Old 02-04-2021, 01:15 PM   #174
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,918

Rep: Reputation: Disabled
Hi wowbaggerHU,
Thanks, typo, corrected.
 
Old 02-05-2021, 06:28 AM   #175
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 288

Rep: Reputation: Disabled
Hi sndwvs,

Okay, the image built fine with your latest modifications.

After booting a base image from the SD card reader, I was able to chroot into the original installation, and fix the /boot partition.
What was wrong:
- /boot/dtb was an empty directory rather than a symlink to the dtb-KERNELVERSION directory
- I had to build a new initrd
- I had to clean up some leftover files

Now the system works fine once again.
 
Old 02-05-2021, 06:41 AM   #176
sndwvs
Senior Member
 
Registered: Aug 2014
Posts: 1,918

Rep: Reputation: Disabled
so, yes, this is due to the new structure similar to the original slackware, this one-time momentary updates are fine.
and yes initrd itself is not built when installing the kernel.
Last edited by sndwvs; 02-05-2021 at 06:43 AM.
 
1 members found this post helpful.
Old 02-05-2021, 03:18 PM   #177
cycojesus
Member
 
Registered: Dec 2005
Location: Lyon, France
Distribution: Slackware-current
Posts: 116

Rep: Reputation: 79
Quote:
Originally Posted by wowbaggerHU View Post
Hi sndwvs,

Okay, the image built fine with your latest modifications.

After booting a base image from the SD card reader, I was able to chroot into the original installation, and fix the /boot partition.
What was wrong:
- /boot/dtb was an empty directory rather than a symlink to the dtb-KERNELVERSION directory
- I had to build a new initrd
- I had to clean up some leftover files

Now the system works fine once again.
I had no such trouble, upgrading from 5.9.15-mara to 5.10.11-mara went fine.
 
  


Reply
Page 12 of 12 « First 21011 12



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Destination Linux 131 - Endeavour OS, Deepin, OnlyOffice, Silverblue, Pinebook Pro, Ubuntu Mate, GPD LXer Syndicated Linux News 0 07-25-2019 06:41 AM
LXer: Linux 5.2, Debian 10, Pinebook Pro, Mageia, Whonix, GRUB, Valve, Zorin, Mint | This Week in Linux 73 LXer Syndicated Linux News 0 07-10-2019 06:43 AM
Video : New PINE64 Products. PineBook Pro, PinePhone, PineCam, PineH64 NicoD SBC Linux - Embedded & Single-board computer 2 02-06-2019 04:37 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM

All times are GMT -5. The time now is 09:28 AM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration