Trying to get CD-ROM established in Garuda

Issues & Assistance
1

So this may be more Linux than Garuda, though I had my CD operational when using Kubuntu. Garuda doesn't see it at all, or at least I don't see it where I would think Garuda would display something. Is this a driver issue I can resolve from command line? The computer is an HP-SLIM desktop model S01-pF1013W which uses the HP ULTRASLIM optical drive.

Hardware configuration does show "unknown device name" under Multimedia Controller...
image

Garuda-inxi is as follows:

System:
Kernel: 6.3.9-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=9a9df3d5-8a94-4c2e-8913-81e7791350ad rw rootflags=subvol=@
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.6 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 1
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: HP product: HP Slim Desktop S01-pF1xxx v: N/A
serial: <superuser required> Chassis: type: 3 serial: <superuser required>
Mobo: HP model: 8768 v: A (SMVB) serial: <superuser required> UEFI: AMI
v: F.33 date: 10/20/2022
CPU:
Info: model: Intel Core i7-10700 bits: 64 type: MT MCP arch: Comet Lake
gen: core 10 level: v3 note: check built: 2020 process: Intel 14nm family: 6
model-id: 0xA5 (165) stepping: 5 microcode: 0xF6
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 2 MiB desc: 8x256 KiB
L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 2644 high: 2900 min/max: 800/4800 scaling:
driver: intel_pstate governor: powersave cores: 1: 2900 2: 2900 3: 2900
4: 2900 5: 2900 6: 2900 7: 2900 8: 2900 9: 2900 10: 917 11: 800 12: 2900
13: 2900 14: 2900 15: 2900 16: 2900 bogomips: 92796
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel CometLake-S GT2 [UHD Graphics 630] vendor: Hewlett-Packard
driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
ports: active: DP-1,HDMI-A-1 empty: none bus-ID: 00:02.0
chip-ID: 8086:9bc5 class-ID: 0300
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.2
compositor: kwin_x11 driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 4590x3240 s-dpi: 96 s-size: 1213x856mm (47.76x33.70")
s-diag: 1485mm (58.45")
Monitor-1: DP-1 pos: bottom-r model: 100002487 serial: <filter>
built: 2021 res: 1920x1080 hz: 75 dpi: 102 gamma: 1.2
size: 476x267mm (18.74x10.51") diag: 611mm (24") ratio: 16:10, 15:9 modes:
max: 1920x1080 min: 720x400
Monitor-2: HDMI-A-1 mapped: HDMI-1 pos: primary,top-left
model: Sceptre W55 built: 2018 res: 3840x2160 hz: 30 dpi: 138
size: 708x398mm (27.87x15.67") modes: max: 3840x2160 min: 720x400
API: OpenGL v: 4.6 Mesa 23.1.2 renderer: Mesa Intel UHD Graphics 630 (CML
GT2) direct-render: Yes
Audio:
Device-1: Intel Comet Lake PCH-V cAVS vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_cnl
bus-ID: 00:1f.3 chip-ID: 8086:a3f0 class-ID: 0403
API: ALSA v: k6.3.9-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 0.3.71 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: 4000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp2s0 state: down mac: <filter>
Device-2: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter
vendor: Hewlett-Packard driver: rtw_8821ce v: N/A modules: rtw88_8821ce
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 03:00.0
chip-ID: 10ec:c821 class-ID: 0280
IF: wlp3s0 state: up mac: <filter>
Bluetooth:
Device-1: Realtek Bluetooth 4.2 Adapter driver: btusb v: 0.8 type: USB
rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-7:3 chip-ID: 0bda:b00a
class-ID: e001 serial: <filter>
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
RAID:
Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 port: 5060
bus-ID: 00:17.0 chip-ID: 8086:2822 rev: class-ID: 0104
Drives:
Local Storage: total: 5.47 TiB used: 45.98 GiB (0.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Silicon Power
model: SPCC M.2 PCIe SSD size: 476.94 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: SN07151 temp: 35.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital model: WDBNCE0010PNC
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 20RL scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: Expansion Desk
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B type: USB
rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter>
fw-rev: 0915 scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 vendor: Generic model: Compact Flash
size: 3.83 GiB block-size: physical: 512 B logical: 512 B type: USB rev: 2.0
spd: 480 Mb/s lanes: 1 mode: 2.0 tech: SSD serial: <filter> fw-rev: 1.01
scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-5: /dev/sdg maj-min: 8:96 vendor: Seagate model: ST9500325AS
size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 2.0 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: HDD rpm: 5400
serial: <filter> fw-rev: 0142 scheme: GPT
Partition:
ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 45.98 GiB (4.9%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 45.98 GiB (4.9%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 45.98 GiB (4.9%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 45.98 GiB (4.9%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.19 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 36.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 338 Uptime: 23m wakeups: 0 Memory: available: 31.19 GiB
used: 4.45 GiB (14.3%) Init: systemd v: 253 default: graphical
tool: systemctl Compilers: gcc: 13.1.1 Packages: pm: pacman pkgs: 1979
libs: 560 tools: octopi,paru Shell: fish v: 3.6.1 default: Bash v: 5.1.16
running-in: konsole inxi: 3.3.27
Garuda (2.6.16-1):
System install date:     2023-05-26
Last full system update: 2023-06-23
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       No/Undetected
Failed units:
2

Just a shot in the dark.
I remember this workaround long ago


I remember I didn’t expect it to work, but you could give it a try


3 Likes
3

Thanks filo - that unfortunately did not work. :sob: :

4

I can confirm that optical drives work. I bought a USB BluRay burner and so far I remember I had no problems, internally it's from Pioneer but with a Verbatim label.
Mine is shown in "Device Viewer" as optical drive. Could you try that? If you know from what company it is internally you might find some drivers with pacsearch.

5

nothing for optical shown.
image
All drives above are accounted for.

I will note, drive is working fine with Zorin OS on my alternate boot.

6

Not sure if it helps - but here's where I could find information on SATA controller:
00:17.0 RAID bus controller: Intel Corporation SATA Controller [RAID mode]
DeviceName: Onboard - Other
Subsystem: Hewlett-Packard Company SATA Controller [RAID mode]
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 16
Memory at b1328000 (32-bit, non-prefetchable) [size=8K]
Memory at b132c000 (32-bit, non-prefetchable) [size=256]
I/O ports at 5090 [size=8]
I/O ports at 5080 [size=4]
I/O ports at 5060 [size=32]
Memory at b132b000 (32-bit, non-prefetchable) [size=2K]
Capabilities:
Kernel driver in use: ahci

7

(via ChatGPT) Check kernel modules: CD-ROM drives typically use the "cdrom" kernel module. Run the following command to verify if it's loaded:

perlCopy code

lsmod | grep cdrom

If it doesn't return any output, try loading the module manually:

Copy code

sudo modprobe cdrom
8

(via ChatGPT) Check kernel modules: CD-ROM drives typically use the “cdrom” kernel module. Run the following command to verify if it’s loaded:

perlCopy code

lsmod | grep cdrom

If it doesn’t return any output, try loading the module manually:

Copy code

sudo modprobe cdrom

Response from this was:
╰─λ lsmod | grep cdrom
cdrom 81920 2 isofs,sr_mod

9

Hmm, in my case it shows
cdrom 81920 3 hfsplus,hfs,sr_mod
but this doesn’t look like the error.

Check for appropriate permissions: Ensure that the user trying to access the CD-ROM has appropriate permissions. Typically, users need to be a member of the “cdrom” group to access optical drives. You can check the group membership with the following command:

groups <username>

If the user is not a member of the “cdrom” group, you can add them by running:

sudo usermod -aG cdrom <username>

If this isn’t it, then you should find a way to check for a hardware defect by trying it in another device. Don’t remember if you mentioned that it works on another OS or connected to another device.

10

If the user is not a member of the “cdrom” group, you can add them by running:

sudo usermod -aG cdrom

We might be getting somewhere here. System states group ‘cdrom’ does not exist.
It did have “optical” as a group which I added my user to, but nothing came out of it.

11

Yeah, sorry, but this was leading into the wrong direction. I don't have the group cdrom either. I don't think I can help you. No idea, why no one else commented on this thread.

sys games scanner wheel input kvm lp uucp video libvirt realtime cups sambashare vboxusers myusername

12

Thanks for the attempt! It was appreciated!
Any other gurus out there with an idea?
If my alternate OS can see it (it does), must be a permission or driver issue?

13

This might be a long shot, but have you tried using a different kernel? I would guess the drivers you need are built into the kernel, but there is always a chance a bug has come down that is interfering somehow.

sudo pacman -S linux-lts linux-lts-headers

You can select an alternate kernel from the advanced boot options in the Grub menu.

3 Likes
14

you are loading a cd vid before trying to see it.

15

you are loading a cd vid before trying to see it.

Not sure what is meant here, but just to clarify - CD is completely INOP while in Garuda environment. Drive only spins up during BIOS initialization (EJECT also works at this initialization). Once Garuda is loaded, Drive is not accessible, does not spin, and EJECT button does not function.

Regards,
Mike

16

I’m nervous to do that! but I can try


17

In that case you may need to load the sg module 1st its easy to do just read the wiki.

1 Like
18

That’s a simple thing to accomplish. Just do exactly as @BluishHumility suggested. Don’t be afraid–we can provide clarification if needed, but it is very important that you learn basic Linux/Garuda/Arch basics. Remember, you wanted to run this beautiful Arch-based distribution. :smiley:

3 Likes
19

My first guess would also be a kernel regression. If testing alternate kernels does not help, then try below:

It is possible it could be a bios issue causing this, so test the following suggestions.

Try resetting your bios to the factory default, you may need to toggle a few settings such as secure boot etc to boot Garuda after a reset. Ubuntu does not require secure boot to be disabled in the bios, so that might possibly be a reason for it working differently than Garuda.

Try setting your cd/dvd drive as the first boot device in your bios.

See if you can boot from a bootable cd/dvd.

If not, try swapping your DVD's SATA cable to port 1 on your mobo. Sometimes it is difficult to juggle cables in HP desktops, so it might not be possible without a longer SATA cable.

Please post the outputs of these commands:

inxi --optical
hwinfo | grep DVD

See if any partition manager utility such as gnome disks, gparted, or KDE Partition Manager detects your DVD drive. If so try to mount your DVD drive from within the GUI partitioning utility.

Otherwise you can try to mount your DVD from the terminal, see:

https://wiki.archlinux.org/title/Optical_disc_drive

6 Likes
20

This might be a long shot, but have you tried using a different kernel? I would guess the drivers you need are built into the kernel, but there is always a chance a bug has come down that is interfering somehow.

sudo pacman -S linux-lts linux-lts-headers

You can select an alternate kernel from the advanced boot options in the Grub menu.

attempted - was unable to accomplish - received 404 errors - and it appears it only has to do with this type of update (normal garuda-update works). Will keep trying to see if error resolves.