Bluetooth still does not work. Whatever the cause, I can't find a solution. So I'll stay with ASCII.

Thanks everyone.

u2 is your ear-plug device. As I have told you I am not using bluetooth myself on linux so I have limited experience with this, but I know linux quite well mostly because I have been using it for more than 20+ years (I am getting old and long in the tooht :-)). But I can see it often is a hit and miss with bluetooth what works and what does not, because many devices are hidden by default. Blueman is a graphical manager used to pair bluetooth devices. Read more here https://www.maketecheasier.com/setup-bl … -in-linux/ You can as well use bluetooth-agent or hcitool from the commandline https://wiki.debian.org/BluetoothUser.

Hope this is to some help. And have a nice day

Hi

What bluetooth manager are you using. Blueman ?? What does "rfkill list" say.

Have a nice day

Thanks, u2.

rfkill list
0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
1: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no

What bluetooth manager are you using. Blueman ?? What does "rfkill list" say.

Have a nice day

lafat wrote:

since I have erased Beowulf 3 RC partitions cos GRUB wouldn't install (waited for 20 min, nothing), I'll just post "parted --list" here if it's of any use.

Did the installer ask you on which disk or partition to place the bootloader? If it did then it was trying to install in non-UEFI mode, which won't work without a BIOS boot partition.

You have a GPT disk and a UEFI Windows system so you will have to make sure that the installer is booted in UEFI mode if you want to see a menuentry for Windows. Switch to a TTY and check for /sys/firmware/efi to confirm this (it will only exist if the system is booted in UEFI mode).

@admin: would it be possible to split this problem out into it's own thread?

Thanks, I'll give it a try this weekend, with netinstall and livedisk, will split the thread if the problem persists.

Hi

No sound. That is a common problem. Has nothing to do with bluetooth. Look in the proposed release notes or for instance here https://dev1galaxy.org/viewtopic.php?id=3541. In this case it might be needed to go the pulseaudio route.

Havce a nice day
Lars H

No no, it's not "no sound." It always says No bluetooth controller/device found. Bluetooth manager won't even load.

since I have erased Beowulf 3 RC partitions cos GRUB wouldn't install (waited for 20 min, nothing), I'll just post "parted --list" here if it's of any use.

Did the installer ask you on which disk or partition to place the bootloader? If it did then it was trying to install in non-UEFI mode, which won't work without a BIOS boot partition.

You have a GPT disk and a UEFI Windows system so you will have to make sure that the installer is booted in UEFI mode if you want to see a menuentry for Windows. Switch to a TTY and check for /sys/firmware/efi to confirm this (it will only exist if the system is booted in UEFI mode).

@admin: would it be possible to split this problem out into it's own thread?

The bios not installing might also a common problem for some bios implementations on devuan (and debian) installs. Use the installer-iso (NOT live one), and choose expert install. Do the install. When asked to "force the grub install on bios" choose YES. This should hopefully solve your problem with grub

Have a nice day.
Lars H

No sound. That is a common problem. Has nothing to do with bluetooth. Look in the proposed release notes or for instance here https://dev1galaxy.org/viewtopic.php?id=3541. In this case it might be needed to go the pulseaudio route.

Havce a nice day
Lars H

lafat wrote:

Installing GRUB on UEFI/GPT still hangs. MBR no problem.

Can we have a separate thread for this? I wouldn't mind digging into that issue.

Thanks, since I have erased Beowulf 3 RC partitions cos GRUB wouldn't install (waited for 20 min, nothing), I'll just post "parted --list" here if it's of any use. Note, I had a 300GB EXT4  partition (#5) on and a swap (#6) for about 8gb on the Intel SSD (GPT, with Win10. Asus X370-Pro as listed above). Both erased and now only Win10 NTFS.

sudo parted --list
Model: ATA INTEL SSDSC2BA80 (scsi)
Disk /dev/sda: 800GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End    Size    File system  Name                          Flags
1      1049kB  524MB  523MB   ntfs         Basic data partition          hidden, diag
2      524MB   629MB  105MB   fat32        EFI system partition          boot, esp
3      629MB   646MB  16.8MB               Microsoft reserved partition  msftres
4      646MB   800GB  800GB   ntfs         Basic data partition          msftdata

Model: Lexar USB Flash Drive (scsi)
Disk /dev/sdb: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number  Start   End     Size    Type     File system  Flags
1      1049kB  16.0GB  16.0GB  primary  fat32        boot, lba

Model: ATA TOSHIBA DT01ABA3 (scsi)
Disk /dev/sdc: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start  End     Size    File system  Name                  Flags
1      135MB  3001GB  3000GB  ntfs         Basic data partition  msftdata

Hi

Thank you for info

What does a terminal "service bluetooth status" say. I know this might be stupid, but it might be the service that is not running. Maybe have a look here https://wiki.debian.org/BluetoothUser/. I do not have any bluetooth serrvices running on my system (although I can see a hci0 device), but the more information available, chances are that somebody have the solution.

Have a nice day
Lars H

Hi Lars thanks.

devuan@devuan:~$ sudo service bluetooth status
[ ok ] bluetooth is running.

I had looked at the Debian wiki before coming here. It didn't help. Bluetooth works with other distros, incl Debian Buster. Bluetooth is important to me because I need to use headphones (only bluetooth, no wire) to block out noise. I have very noisy neighbors.

Installing GRUB on UEFI/GPT still hangs. MBR no problem.

Can we have a separate thread for this? I wouldn't mind digging into that issue.

Thank you for info

What does a terminal "service bluetooth status" say. I know this might be stupid, but it might be the service that is not running. Maybe have a look here https://wiki.debian.org/BluetoothUser/. I do not have any bluetooth serrvices running on my system (although I can see a hci0 device), but the more information available, chances are that somebody have the solution.

Have a nice day
Lars H

OS - Beowulf RC Live ISO

lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1480
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Device 1481
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1482
00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1483
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1482
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1482
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1483
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1482
00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1482
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1482
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1484
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1482
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1484
00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1484
00:08.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1484
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1440
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1441
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1442
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1443
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1444
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1445
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1446
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1447
01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43b9 (rev 02)
01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] Device 43b5 (rev 02)
01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b0 (rev 02)
02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
02:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
02:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
02:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
02:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
06:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller
07:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
09:00.0 VGA compatible controller: NVIDIA Corporation GP108 (rev a1)
09:00.1 Audio device: NVIDIA Corporation GP108 High Definition Audio Controller (rev a1)
0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 148a
0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 1485
0b:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Device 1486
0b:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Device 149c
0b:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Device 1487
0c:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
0d:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)

lsusb
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 005 Device 004: ID 1b1c:1b2f Corsair
Bus 005 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 005 Device 002: ID 046d:c24d Logitech, Inc. G710 Gaming Keyboard
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 05dc:a838 Lexar Media, Inc. JumpDrive Tough
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lspci -nnk | grep -iA2 net
07:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03)
    Subsystem: ASUSTeK Computer Inc. I211 Gigabit Network Connection [1043:85f0]
    Kernel driver in use: igb
    Kernel modules: igb

sudo dmesg | grep Blue
[    8.133938] Bluetooth: Core ver 2.22
[    8.134566] Bluetooth: HCI device and connection manager initialized
[    8.135089] Bluetooth: HCI socket layer initialized
[    8.135636] Bluetooth: L2CAP socket layer initialized
[    8.136189] Bluetooth: SCO socket layer initialized
[   15.267264] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   15.267580] Bluetooth: BNEP filters: protocol multicast
[   15.267875] Bluetooth: BNEP socket layer initialized

hciconfig --all
hci0:    Type: Primary  Bus: USB
    BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
    UP RUNNING
    RX bytes:1220 acl:0 sco:0 events:72 errors:0
    TX bytes:2303 acl:0 sco:0 commands:72 errors:0
    Features: 0xff 0xff 0x8f 0xfe 0xdb 0xff 0x5b 0x87
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
    Link policy: RSWITCH HOLD SNIFF PARK
    Link mode: SLAVE ACCEPT
    Name: 'BlueZ 5.50'
    Class: 0x000104
    Service Classes: Unspecified
    Device Class: Computer, Desktop workstation
    HCI Version: 4.0 (0x6)  Revision: 0x22bb
    LMP Version: 4.0 (0x6)  Subversion: 0x22bb
    Manufacturer: Cambridge Silicon Radio (10)