Install review (several problems)

Boot installer

Mouse not detected. Turn on bluetooth. No option to pair. No bluetooth icon in systray like you normally see. I am very familiar with KDE (daily driver for 8+ months).

Install OS. Reboot.

Cant connect to wifi. Hung on ‘waiting for authorization’ or something. Reboot again. Works this time.

  • mouse doesnt work
  • bluetooth doesnt work
  • wifi cant connect (no error)

Decide I want to use XFCE and reboot to do online installer. Reboot into installer.

Do online installer. hangs at ‘starting Calamares’ or whatever.
Google it. Do pacman -Sy. use welcome tool to pick mirrors.
Run installer again.
~5 seconds into OS install get pacman error exit status 1.
Google that some.
Try again
Get further into installer this time.
Different pacman error.
Try again.
Installer works this time.
Get into XFCE
Bluetooth is still off for some reason

Overall due to the glitches and errors is took 3x time to get this finished. Total time was ~1 hour with several installer errors and system glitches that didnt happen with other Arch based distros.

  • mouse doesnt work
  • bluetooth doesnt work
  • wifi cant connect (no error)
  • Calamares hangs with no error
  • installer pacman command crashes multiple times

This same system was using this same mouse over bluetooth in a different Arch distro with no problems.

Welcome to the forum :enos_flag: :enos_flag:
Bluetooth is not enabled by default in EOS
https://discovery.endeavouros.com/audio/bluetooth/2021/03/

Calamares may be fetching some packets to start the installation, seen that on several distros, so that would be normal behaviour.
Also some more information about your system would be welcome, so someone might help you out with the rest.https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/

2 Likes

Welcome! Just curious why reinstall and switch to EndeavourOS if you had a working installation with a different Arch-based distribution before, once installed they’re all mostly the same except for the tools installed?

The best thing to ALWAYS start with is posting your hardware output along with an explanation of your problem or problems. You can’t just carte blanche fix every problem in one fell swoop. There were obviously some issues because this isn’t the norm. Sure you can have bluetooth not working. That’s a given. Yes you can have WiFi issues … that happens depending on the hardware. Same with a mouse. It can happen albeit not often. Calamares hanging is another issue and the installer crashing multiple times is probably mirror issues. So updating the Arch mirrors first can help if you are having that issue. There have been numerous ddos attacks against arch and some of the repos. So that can have an effect also. I can tell you i can install in under 4 minutes. I don’t normally have these kinds of issues but have seen some.

As already pointed out, BT is disabled by default so this is expected.

As for your installer errors, it is hard to say what the issue was there without any logs from the installer.

“As already pointed out, BT is disabled by default so this is expected.”

new users are not going to know this and expect BT to be on.

2 Likes

“Calamares may be fetching some packets to start the installation”

I was sat for several minutes with no signs of life. And if this step is downloading stuff it needs a UI progress bar or feedback so the user does not think it’s frozen.

After I manually did pacman -Sy it was fine.

At this stage I dont need help but thanks. It’s all setup and installed now. Just a rough start. This post is just providing some feedback, and maybe if someone else has the same issues they will see you can just power through and it will work.

1 Like

I had been using Artix for ~1 yr with OpenRC. No problems with OpenRC but Artix doest have the same packages available as normal Arch. I wanted to (1) have all normal arch packages available and (2) use systemD more since that’s what my Digital Ocean server is using as well. I’ve used systemD in the past but it’s been a few years.

1 Like

Sorry, but that is not our stance on it. We believe it is better for BT to be off by default and we discuss it on our wiki.

While it is true that this occasionally trips up a new user, it has not been a major problem for us or our user base.

2 Likes

I think a rough start represents 50% of installs and/or exploring new territory in Linux. I don’t find Linux struggles alarming–I find them a little setback. A major PITA/thorn to be sure. I still expect everything to work OOTB but due to factors—which I accept are on my end or the other end out of our control—it’s Linux. No installer fits everyone, imo, always adjustments to be made.

PS—I’ve done that mirror/reflector dance during EOS installs before. Welcome to the forum, I think you will enjoy the OS.

You won the battle that is a good thing.

2 Likes

About the UI progress bar, there is none but clicking on the button on the bottom right would have shown you the progress. That is how Calamares works i believe because have seen that on almost every distro I have installed that uses Calamares.

1 Like

Sorry this was in regards to the start of the online installer. A little box popped up saying it was doing something (I forget the exact text now). It wasnt part of the normal Calamares UI. Just a little popup window before you get into the normal Calamares install.

info is king as always, its not that the ISO is not tested to work properly before releasing .. but some downsides at the very moment with archlinux in general as there is again ongoing attack on the infrastructure, causing issues with mirror ranking as of that.

On the ISO LiveSession (installer) Bluetooth should be enabled and running, but you will need to add any BT dcevice manually still it will not add any automatically without you active doing so. If there was no BT tray icon on the LiveSession something not properly working with your specific BT device.

ISO is widely tested and should work properlyon most hardware but it will never work for every hardware on the planet, some need manuay intervention others will simply not work.

In many cases it is causing also issues if install media is not properly created: https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/

And as we do aöways listen to users and taking issues serious we always like to get the installer logs or boot logs in case of hardware issues, with this we can fix issues:
https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/
Without any details on the used hardware and no logs nothing we can do.

2 Likes

Hi Joe thanks for your reply in my little thread =)

I wanted to brain dump the main post before I forgot everything. I also wanted to post here, and not reddit or youtube because the point isnt to trash Endeavour, but just to give some feedback. But as you said without more details my feedback is less useful.

Just double checked and I never posted my HW info, so here it is. I understand the link shares expire so here is the raw info.

I just tried the same ISO on a different older laptop and the bluetooth was on and enabled by default (icon in systray). I still got a long delay on ‘starting Calamares’ where it sits there for ~1+ min with no error, no output, no progress bars. Eventually I closed it, restarted it, and after ~10 seconds it starts the installer. If it’s downloading something, or whatever, seeing that console text would help the users know what is happening instead of thinking it’s frozen. Anyways, my post isnt super important, and the Endeavour OS is installed and running fine now.

I use Linux on work machines 8hrs a day ~6 days a week. Main work laptop, backup work laptop, and a spare I just kind of play with that I can experiment on.

System:
Kernel: 6.18.2-arch2-1 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
Desktop: Xfce v: 4.20.1 tk: Gtk v: 3.24.51 wm: xfwm4 dm: LightDM
Distro: EndeavourOS base: Arch Linux
Machine:
Type: Laptop System: Acer product: Aspire A14-52M v: V1.02
serial: Chassis: type: 10 serial:
Mobo: LNL model: Tiramisu_LNV v: V1.02 serial:
part-nu: 0000000000000000 Firmware: UEFI vendor: INSYDE v: 1.02
date: 01/06/2025
Battery:
ID-1: BAT1 charge: 64.7 Wh (100%) condition: 64.7/65 Wh (99.5%) volts: 13.32
min: 11.67 model: COSMX AP22ABN serial: charging: status: full
cycles: 3
Device-1: hidpp_battery_0 model: Logitech Signature M650 L
serial: charge: 5% status: discharging
CPU:
Info: 8-core model: Intel Core Ultra 7 256V bits: 64 type: MCP
arch: Lunar Lake rev: 1 cache: L1: 832 KiB L2: 14 MiB L3: 12 MiB
Speed (MHz): avg: 400 min/max: 400/4700:4800:3700 cores: 1: 400 2: 400
3: 400 4: 400 5: 400 6: 400 7: 400 8: 400 bogomips: 52838
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel Lunar Lake [Intel Arc Graphics 130V / 140V]
vendor: Acer Incorporated ALI driver: xe v: kernel arch: Xe2 ports:
active: HDMI-A-1 off: eDP-1 empty: DP-1,DP-2 bus-ID: 00:02.0
chip-ID: 8086:64a0
Device-2: Quanta ACER FHD User Facing driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 bus-ID: 3-5:3 chip-ID: 0408:4054
Display: x11 server: X.Org v: 21.1.21 compositor: xfwm4 v: 4.20.0 driver:
X: loaded: modesetting alternate: fbdev,intel,vesa dri: iris gpu: xe
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 96
Monitor-1: HDMI-A-1 mapped: HDMI-1 pos: primary model: XG27UCS
res: 2560x1440 hz: 120 dpi: 109 diag: 685mm (27")
Monitor-2: eDP-1 note: disabled model-id: CSW 0x1448 res: 2560x1440
dpi: 161 diag: 356mm (14")
API: EGL v: 1.5 platforms: device: 0 drv: iris device: 1 drv: swrast gbm:
drv: iris surfaceless: drv: iris x11: drv: iris inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.3.2-arch1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel Graphics (LNL)
device-ID: 8086:64a0
Info: Tools: api: eglinfo,glxinfo de: xfce4-display-settings
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Lunar Lake-M HD Audio vendor: Acer Incorporated ALI
driver: sof-audio-pci-intel-lnl bus-ID: 00:1f.3 chip-ID: 8086:a828
API: ALSA v: k6.18.2-arch2-1 status: kernel-api
Server-1: PipeWire v: 1.4.9 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin
Network:
Device-1: Intel BE201 320MHz driver: iwlwifi v: kernel port: N/A
bus-ID: 00:14.3 chip-ID: 8086:a840
IF: wlan0 state: up mac:
Bluetooth:
Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 bus-ID: 3-6:4 chip-ID: 8087:0033
Report: btmgmt ID: hci0 rfk-id: 2 state: up address: bt-v: 5.4
lmp-v: 13
Drives:
Local Storage: total: 953.87 GiB used: 18.04 GiB (1.9%)
ID-1: /dev/nvme0n1 vendor: Kingston model: OM8PGP41024Q-AA
size: 953.87 GiB speed: 63.2 Gb/s lanes: 4 serial: temp: 20.9 C
Partition:
ID-1: / size: 927.19 GiB used: 17.94 GiB (1.9%) fs: ext4 dev: /dev/nvme0n1p2
Swap:
ID-1: swap-1 type: partition size: 8.8 GiB used: 4 KiB (0.0%) priority: -2
dev: /dev/nvme0n1p3
Sensors:
System Temperatures: cpu: 37.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GiB note: est. available: 15.29 GiB used: 5.55 GiB (36.3%)
Processes: 376 Power: uptime: 5h 4m wakeups: 0 Init: systemd v: 259
default: graphical
Packages: pm: pacman pkgs: 997 Compilers: gcc: 15.2.1 Shell: Bash v: 5.3.9
running-in: xfce4-terminal inxi: 3.3.40

That probably indicates a problem with mirror ranking. As we have witnessed recently, the Arch web site has been under DDoS attack which occasionally causes problems to the current ranking tools.
The team is already working on improvements to mirror ranking procedure because of this.

3 Likes

Icon in system tray doesn’t mean it was actually setup. GNOME may set it up by default as per the DE it self, but if you got a working bluetooth experience OOTB from an EOS install → Now that would be something to look into. Bluetooth not working is the expected and hopeful outcome.

EOS is not directly geared/marketed towards new users. If you’re a brand new to Linux user - Mint is a fantastic place to start. You may find it more to your speed. This tends to be more for folks who are a little more seasoned and know what they want/need. I do understand that mismatched expectations can leave anyone unhappy. You expected bluetooth to work. EOS expects it not to.

3 Likes