Newbie : boot menu

inxi :

Kernel: 5.13.9-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=4d11fe1a-136e-4bd6-8b81-3ee4eb809307 rw
rootflags=subvol=@ quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 loglevel=3
Desktop: KDE Plasma 5.22.4 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux
base: Arch Linux
Machine: Type: Laptop System: Dell product: Latitude E7470 v: N/A serial: Chassis: type: 9 serial:
Mobo: Dell model: 0DGYY5 v: A06 serial: UEFI-[Legacy]: Dell v: 1.10.4 date: 11/04/2016
Battery: ID-1: BAT0 charge: 21.1 Wh (57.5%) condition: 36.7/55.0 Wh (66.8%) volts: 7.9 min: 7.6
model: LGC-LGC3.65 DELL 242WD69 type: Li-ion serial: status: Discharging
CPU: Info: Dual Core model: Intel Core i5-6300U bits: 64 type: MT MCP arch: Skylake family: 6 model-id: 4E (78)
stepping: 3 microcode: EA cache: L2: 3 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19999
Speed: 3000 MHz min/max: 400/3000 MHz Core speeds (MHz): 1: 3000 2: 2900 3: 3000 4: 2899
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort mitigation: Clear CPU buffers; SMT vulnerable
Graphics: Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: Dell Latitude E7470 driver: i915 v: kernel bus-ID: 00:02.0
chip-ID: 8086:1916 class-ID: 0300
Device-2: Sunplus Innovation Dell Integrated HD Webcam type: USB driver: uvcvideo bus-ID: 1-2:2 chip-ID: 1bcf:28bd
class-ID: 0e02
Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: loaded: intel unloaded: modesetting
alternate: fbdev,vesa display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.7x15.0") s-diag: 777mm (30.6")
Monitor-1: eDP1 res: 2560x1440 hz: 60 dpi: 210 size: 310x170mm (12.2x6.7") diag: 354mm (13.9")
OpenGL: renderer: Mesa Intel HD Graphics 520 (SKL GT2) v: 4.6 Mesa 21.1.6 direct render: Yes
Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell Latitude E7470 driver: snd_hda_intel v: kernel
alternate: snd_soc_skl bus-ID: 00:1f.3 chip-ID: 8086:9d70 class-ID: 0403
Sound Server-1: ALSA v: k5.13.9-zen1-1-zen running: yes
Sound Server-2: JACK v: 1.9.19 running: no
Sound Server-3: PulseAudio v: 15.0 running: no
Sound Server-4: PipeWire v: 0.3.33 running: yes
Network: Device-1: Intel Ethernet I219-LM vendor: Dell Latitude E7470 driver: e1000e v: kernel port: f040 bus-ID: 00:1f.6
chip-ID: 8086:156f class-ID: 0200
IF: enp0s31f6 state: down mac:
Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel port: f040 bus-ID: 01:00.0 chip-ID: 8086:24f3
class-ID: 0280
IF: wlp1s0 state: down mac:
Drives: Local Storage: total: 238.47 GiB used: 8.12 GiB (3.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Micron model: MTFDDAV256TBN-1AR15FCHA size: 238.47 GiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: rev: 0F10 scheme: MBR
Partition: ID-1: / raw-size: 238.47 GiB size: 238.47 GiB (100.00%) used: 8.12 GiB (3.4%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-2: /home raw-size: 238.47 GiB size: 238.47 GiB (100.00%) used: 8.12 GiB (3.4%) fs: btrfs dev: /dev/sda1
maj-min: 8:1
ID-3: /var/log raw-size: 238.47 GiB size: 238.47 GiB (100.00%) used: 8.12 GiB (3.4%) fs: btrfs dev: /dev/sda1
maj-min: 8:1
ID-4: /var/tmp raw-size: 238.47 GiB size: 238.47 GiB (100.00%) used: 8.12 GiB (3.4%) fs: btrfs dev: /dev/sda1
maj-min: 8:1
Swap: Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 7.57 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors: System Temperatures: cpu: 42.0 C mobo: 37.0 C sodimm: SODIMM C
Fan Speeds (RPM): cpu: 0
Info: Processes: 173 Uptime: 8m wakeups: 1 Memory: 7.58 GiB used: 1.69 GiB (22.3%) Init: systemd v: 249 tool: systemctl
Compilers: gcc: 11.1.0 clang: 12.0.1 Packages: pacman: 1163 lib: 291 Shell: fish v: 3.3.1 default: Bash v: 5.1.8
running-in: konsole inxi: 3.3.06

sorry for my english
im new to linux and decided to start with garuda
i want to try another garuda system and
i do not know how to enter boot menu

If you include terminal outputs in your post please use the proper output format in your post.

Using "~" 3 times above and "~" 3 times below the text block will provide a readable, raw look.

:slight_smile:

IDK where is the problem. Boot menu, it opens by itself.

3 Likes

its a common question
i don't think you need inxi info..
to answer my question :disappointed:

do you even know what's a boot menu
i mean
if you have installed garuda properly the the boot menu will appear
boot menu is a screen opens up when you turn on ur computer to select which OS u wanna boot in
ok @William ?

You post your inxi, please edit your post.
It's a pain on cell phones and tablets to scroll the long inxi if the format is not correct.


Grub boot menu is

2021-09-12_19-07

3 Likes

let's imagine you have dragonized edition
on dell laptop
and you want to switch to home edition
what setups you should follow to do that

What's a "home" edition?

1 Like

what home edition??

lol maby he is talking about windows

2 Likes

its just an example :unamused:

How about the spartan edition instead?

1 Like

Last time, please edit your first post.

Everytime you take your vehicle in for engine work the first thing they request is to read your diagnostic codes from your cars electonic module. This is standard procedure for diagnosing any engine problems and they charge a pretty penny for this simple diagnostic step.

We request diagnostic outputs and do not charge hundreds of dollars to review the information. Simply put, we request this info to make support on the forum quicker for everyone involved.

7 Likes

Noted from inxi output: 2016 BIOS date

My personal bugaboo. :wink:

2 Likes