F96-CE_4 Latest Stable Release

Moderator: Forum moderators

fr-ke
Posts: 107
Joined: Mon Nov 07, 2022 3:18 pm
Has thanked: 4 times
Been thanked: 35 times

Re: F96-CE_4 Latest Stable Release

Post by fr-ke »

After installing a number of additional programs and taking over the adrv from the F96CE3 (save file replacement). Everything works great so far.
Since I don't need the applications in ydrv I left this one out.

I noticed one little thing:

The applications blueman and bluez are built into base.sfs, but the necessary libraries are in ydrv.sfs.
Bluetooth therefore does not work without ydrv.

The affected libraries are:
ydrv_fossapup64_9.6.sfs/usr/lib/x86_64-linux-gnu/libbluetooth.so.3
ydrv_fossapup64_9.6.sfs/usr/lib/x86_64-linux-gnu/libbluetooth.so.3.19.1

retiredt00
Posts: 222
Joined: Fri Sep 04, 2020 12:11 pm
Has thanked: 11 times
Been thanked: 35 times

Re: F96-CE_4 Latest Stable Release - new wl .pet

Post by retiredt00 »

ozsouth wrote: Tue Apr 04, 2023 12:35 pm

F96CE-4 seems to not like my standard blacklisting, nor via command line.

My wl driver pets always have the attached pinstall and puninstall script and most important, the 30-BC-wl script that is placed in /etc/init.d/ and starts wl very reliably (in F64_CE too) on boot up
If I remember correctly originally are based on an old Fatdog pet or script.
It might be of help for your next wl pet

Attachments
30-BC-wl.gz
(417 Bytes) Downloaded 71 times
puninstall.sh.gz
(211 Bytes) Downloaded 61 times
pinstall.sh.gz
(301 Bytes) Downloaded 77 times
Clarity
Posts: 3850
Joined: Fri Jul 24, 2020 10:59 pm
Has thanked: 1634 times
Been thanked: 528 times

Re: F96-CE_4 Latest Stable Release

Post by Clarity »

@radky and @rockedge, the more I play around with this, the more I find favor with the OOTB experience this provides any user! :thumbup2:

There's little to do, once a pristine occurs and a save session.

As soon as I can add the nifty combination of PETs from @ETP, this will become my 2023 replacement for FossaPUP64.

What's not to love! ... Congrats to all of the combined work of everyone and especially you too (no pun intended :) )

ozsouth
Posts: 1574
Joined: Sun Jul 12, 2020 2:38 am
Location: S.E. Australia
Has thanked: 242 times
Been thanked: 707 times

Re: F96-CE_4 Latest Stable Release

Post by ozsouth »

@retiredt00 - thanks for those scripts - pretty much what I'm now doing (& did with skiplisting 5 years ago) - except the on-bootup one, which ensures difficult systems don't backtrack earlier changes. That shouldn't be necessary if the pinstall succeeds, but is insurance.

User avatar
gychang
Posts: 591
Joined: Fri Aug 28, 2020 4:51 pm
Location: San Diego, CA
Has thanked: 206 times
Been thanked: 64 times

internal card reader troubles

Post by gychang »

F96CE-4.iso is a very good distro. I am unable to use the internal card reader. Although the terminal command lsusb "sees" the card (Genesys Logic, Inc. All-in-One Cardreader), pmount and gparted do not.
root@main ~
--> lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 0461:4d65 Primax Electronics, Ltd USB Optical Mouse
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 258a:002a SINO WEALTH Gaming KB
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 003: ID 05e3:0748 Genesys Logic, Inc. All-in-One Cardreader
Bus 009 Device 002: ID 05e3:0626 Genesys Logic, Inc. USB3.1 Hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@main ~
-->

is there a fix for this, ?driver issue?

Attachments
2023-04-04-161709.jpg
2023-04-04-161709.jpg (34.93 KiB) Viewed 4320 times

======

Puppy Bytes, utube videos
https://www.youtube.com/channel/UCg-DUU ... u62_iqR-MA

======

User avatar
bigpup
Moderator
Posts: 7008
Joined: Tue Jul 14, 2020 11:19 pm
Location: Earth, South Eastern U.S.
Has thanked: 916 times
Been thanked: 1532 times

Re: F96-CE_4 Latest Stable Release

Post by bigpup »

Sorry but I have to ask.

You do have some type of card plugged in a slot, when you try to see it with Pmount or Gparted?

What type card?

Pmount will not see it if it is not partitioned and formatted.
There are some formats Puppy does not support.

Does the card come from being used in a camera?

The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected :o

User avatar
gychang
Posts: 591
Joined: Fri Aug 28, 2020 4:51 pm
Location: San Diego, CA
Has thanked: 206 times
Been thanked: 64 times

Re: F96-CE_4 Latest Stable Release

Post by gychang »

bigpup wrote: Wed Apr 05, 2023 10:34 am

You do have some type of card plugged in a slot, when you try to see it with Pmount or Gparted?

What type card?

Does the card come from being used in a camera?

Have 4 different SD cards that I had used in previous older pups for storage purposes and possible puppy booter, all ext4. None is detected when inserted. :cry:
tried in upup-22.04-jrb-C2.iso and vanilladpup-9.3.14.iso with same - no detection.

Last edited by gychang on Wed Apr 05, 2023 12:36 pm, edited 1 time in total.

======

Puppy Bytes, utube videos
https://www.youtube.com/channel/UCg-DUU ... u62_iqR-MA

======

User avatar
gychang
Posts: 591
Joined: Fri Aug 28, 2020 4:51 pm
Location: San Diego, CA
Has thanked: 206 times
Been thanked: 64 times

Re: F96-CE_4 Latest Stable Release

Post by gychang »

bigpup wrote: Wed Apr 05, 2023 10:34 am

You do have some type of card plugged in a slot, when you try to see it with Pmount or Gparted?

What type card?

Does the card come from being used in a camera?

Have 4 different SD cards that I had used in previous older pups for storage purposes and possible puppy booter, all ext4. None is detected when inserted. :cry:

======

Puppy Bytes, utube videos
https://www.youtube.com/channel/UCg-DUU ... u62_iqR-MA

======

dimkr
Posts: 2429
Joined: Wed Dec 30, 2020 6:14 pm
Has thanked: 53 times
Been thanked: 1203 times

Re: F96-CE_4 Latest Stable Release

Post by dimkr »

@gychang Do you see it in fdisk -l or dmesg output?

User avatar
gychang
Posts: 591
Joined: Fri Aug 28, 2020 4:51 pm
Location: San Diego, CA
Has thanked: 206 times
Been thanked: 64 times

Re: F96-CE_4 Latest Stable Release

Post by gychang »

dimkr wrote: Wed Apr 05, 2023 12:59 pm

@gychang Do you see it in fdisk -l or dmesg output?

@dimkr
I don't see the card reader. Ran the command with a valid SD card inserted.

Code: Select all

root@main ~
-->  fdisk -l
Disk /dev/ram0: 13.51 MiB, 14155776 bytes, 27648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram1: 13.51 MiB, 14155776 bytes, 27648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram2: 13.51 MiB, 14155776 bytes, 27648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram3: 13.51 MiB, 14155776 bytes, 27648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram4: 13.51 MiB, 14155776 bytes, 27648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram5: 13.51 MiB, 14155776 bytes, 27648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram6: 13.51 MiB, 14155776 bytes, 27648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram7: 13.51 MiB, 14155776 bytes, 27648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram8: 13.51 MiB, 14155776 bytes, 27648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram9: 13.51 MiB, 14155776 bytes, 27648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram10: 13.51 MiB, 14155776 bytes, 27648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram11: 13.51 MiB, 14155776 bytes, 27648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram12: 13.51 MiB, 14155776 bytes, 27648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram13: 13.51 MiB, 14155776 bytes, 27648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram14: 13.51 MiB, 14155776 bytes, 27648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram15: 13.51 MiB, 14155776 bytes, 27648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/loop0: 96.52 MiB, 101199872 bytes, 197656 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 39.27 MiB, 41168896 bytes, 80408 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 26.68 MiB, 27963392 bytes, 54616 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 228.11 MiB, 239190016 bytes, 467168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Crucial_CT500MX2
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xe99f9ee3

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1  *         2048    411647    409600   200M  b W95 FAT32
/dev/sda2          411648   6555647   6144000     3G 83 Linux
/dev/sda3         6555648 129435647 122880000  58.6G 83 Linux
/dev/sda4       129435648 870008831 740573184 353.1G 83 Linux




Disk /dev/sdb: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model:                 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xa7acb089

Device     Boot   Start        End    Sectors   Size Id Type
/dev/sdb3       1249280 1953525167 1952275888 930.9G 83 Linux
root@main ~
--> 

Code: Select all

[    0.036379] PM: Registered nosave memory: [mem 0x9e8f0000-0x9eff0fff]
[    0.036380] PM: Registered nosave memory: [mem 0x9f000000-0xfebfffff]
[    0.036381] PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
[    0.036381] PM: Registered nosave memory: [mem 0xfec01000-0xfec0ffff]
[    0.036381] PM: Registered nosave memory: [mem 0xfec10000-0xfec10fff]
[    0.036382] PM: Registered nosave memory: [mem 0xfec11000-0xfecfffff]
[    0.036382] PM: Registered nosave memory: [mem 0xfed00000-0xfed00fff]
[    0.036382] PM: Registered nosave memory: [mem 0xfed01000-0xfed7ffff]
[    0.036383] PM: Registered nosave memory: [mem 0xfed80000-0xfed8ffff]
[    0.036383] PM: Registered nosave memory: [mem 0xfed90000-0xfeffffff]
[    0.036384] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
[    0.036384] PM: Registered nosave memory: [mem 0x100000000-0x100000fff]
[    0.036386] [mem 0x9f000000-0xfebfffff] available for PCI devices
[    0.036389] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns
[    0.036396] setup_percpu: NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:4 nr_node_ids:1
[    0.036994] percpu: Embedded 42 pages/cpu s133848 r8192 d29992 u524288
[    0.037000] pcpu-alloc: s133848 r8192 d29992 u524288 alloc=1*2097152
[    0.037001] pcpu-alloc: [0] 0 1 2 3 
[    0.037023] Built 1 zonelists, mobility grouping on.  Total pages: 1856077
[    0.037024] Policy zone: Normal
[    0.037025] Kernel command line: BOOT_IMAGE=/FP64/vmlinuz pmedia=atahd pdrv=pups psubdir=/FP64 psave=SAV:/save/ pfix=fsck,fsckp,trim TZ=PST8PDT,M3.2.0,M11.1.0
[    0.039124] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear)
[    0.040125] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
[    0.040149] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.090945] Memory: 7272564K/7542256K available (14339K kernel code, 855K rwdata, 3636K rodata, 1036K init, 2048K bss, 269692K reserved, 0K cma-reserved)
[    0.091008] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.091067] rcu: Preemptible hierarchical RCU implementation.
[    0.091068] rcu: 	RCU restricting CPUs from NR_CPUS=32 to nr_cpu_ids=4.
[    0.091069] 	Tasks RCU enabled.
[    0.091070] rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies.
[    0.091070] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.091080] NR_IRQS: 4352, nr_irqs: 456, preallocated irqs: 16
[    0.091386] Console: colour dummy device 80x25
[    0.091391] printk: console [tty0] enabled
[    0.091403] ACPI: Core revision 20190816
[    0.091517] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484873504 ns
[    0.091531] APIC: Switch to symmetric I/O mode setup
[    0.091922] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.096531] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x6a77ae6a7c5, max_idle_ns: 881590899274 ns
[    0.096536] Calibrating delay loop (skipped), value calculated using timer frequency.. 7386.18 BogoMIPS (lpj=3693090)
[    0.096538] pid_max: default: 32768 minimum: 301
[    0.098601] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.098636] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.098850] Last level iTLB entries: 4KB 512, 2MB 1024, 4MB 512
[    0.098851] Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 512, 1GB 0
[    0.098854] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[    0.098855] Spectre V2 : Mitigation: Full AMD retpoline
[    0.098856] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[    0.098857] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp
[    0.099046] Freeing SMP alternatives memory: 48K
[    0.201629] smpboot: CPU0: AMD A10-6700 APU with Radeon(tm) HD Graphics (family: 0x15, model: 0x13, stepping: 0x1)
[    0.207551] Performance Events: Fam15h core perfctr, AMD PMU driver.
[    0.207557] ... version:                0
[    0.207558] ... bit width:              48
[    0.207558] ... generic registers:      6
[    0.207559] ... value mask:             0000ffffffffffff
[    0.207560] ... max period:             00007fffffffffff
[    0.207560] ... fixed-purpose events:   0
[    0.207560] ... event mask:             000000000000003f
[    0.209544] rcu: Hierarchical SRCU implementation.
[    0.213543] smp: Bringing up secondary CPUs ...
[    0.221555] x86: Booting SMP configuration:
[    0.221556] .... node  #0, CPUs:      #1 #2 #3
[    0.240567] smp: Brought up 1 node, 4 CPUs
[    0.240567] smpboot: Max logical packages: 1
[    0.240567] smpboot: Total of 4 processors activated (29544.72 BogoMIPS)
[    0.241205] devtmpfs: initialized
[    0.241640] PM: Registering ACPI NVS region [mem 0x9c72b000-0x9ca87fff] (3526656 bytes)
[    0.241640] PM: Registering ACPI NVS region [mem 0x9dde1000-0x9dfe6fff] (2121728 bytes)
[    0.241675] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
[    0.241675] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.241675] xor: automatically using best checksumming function   avx       
[    0.241675] pinctrl core: initialized pinctrl subsystem
[    0.241737] NET: Registered protocol family 16
[    0.241896] cpuidle: using governor ladder
[    0.241896] cpuidle: using governor menu
[    0.241896] ACPI: bus type PCI registered
[    0.241896] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[    0.241896] PCI: not using MMCONFIG
[    0.241896] PCI: Using configuration type 1 for base access
[    0.241896] PCI: Using configuration type 1 for extended access
[    0.649355] raid6: sse2x4   gen()  6781 MB/s
[    0.666358] raid6: sse2x4   xor()  6291 MB/s
[    0.683358] raid6: sse2x2   gen() 10875 MB/s
[    0.700358] raid6: sse2x2   xor()  8183 MB/s
[    0.717357] raid6: sse2x1   gen()  7578 MB/s
[    0.734359] raid6: sse2x1   xor()  5373 MB/s
[    0.734360] raid6: using algorithm sse2x2 gen() 10875 MB/s
[    0.734360] raid6: .... xor() 8183 MB/s, rmw enabled
[    0.734361] raid6: using ssse3x2 recovery algorithm
[    0.734538] ACPI: Added _OSI(Module Device)
[    0.734538] ACPI: Added _OSI(Processor Device)
[    0.734538] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.734538] ACPI: Added _OSI(Processor Aggregator Device)
[    0.734538] ACPI: Added _OSI(Linux-Dell-Video)
[    0.734538] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[    0.734538] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[    0.738311] ACPI: 3 ACPI AML tables successfully acquired and loaded
[    0.739304] ACPI: Interpreter enabled
[    0.739323] ACPI: (supports S0 S3 S4 S5)
[    0.739325] ACPI: Using IOAPIC for interrupt routing
[    0.739347] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[    0.739379] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
[    0.739389] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.739532] ACPI: Enabled 10 GPEs in block 00 to 1F
[    0.744087] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[    0.744092] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3]
[    0.744214] acpi PNP0A03:00: _OSC: platform does not support [PME LTR]
[    0.744327] acpi PNP0A03:00: _OSC: OS now controls [AER PCIeCapability]
[    0.744474] PCI host bridge to bus 0000:00
[    0.744476] pci_bus 0000:00: root bus resource [io  0x0000-0x03af window]
[    0.744477] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7 window]
[    0.744478] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df window]
[    0.744479] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
[    0.744480] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
[    0.744481] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000dffff window]
[    0.744482] pci_bus 0000:00: root bus resource [mem 0xd0000000-0xffffffff window]
[    0.744483] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.744492] pci 0000:00:00.0: [1022:1410] type 00 class 0x060000
[    0.744604] pci 0000:00:01.0: [1002:990c] type 00 class 0x030000
[    0.744617] pci 0000:00:01.0: reg 0x10: [mem 0xd0000000-0xdfffffff pref]
[    0.744622] pci 0000:00:01.0: reg 0x14: [io  0xf000-0xf0ff]
[    0.744627] pci 0000:00:01.0: reg 0x18: [mem 0xfeb00000-0xfeb3ffff]
[    0.744649] pci 0000:00:01.0: enabling Extended Tags
[    0.744657] pci 0000:00:01.0: BAR 0: assigned to efifb
[    0.744679] pci 0000:00:01.0: supports D1 D2
[    0.744742] pci 0000:00:07.0: [1022:1417] type 01 class 0x060400
[    0.744771] pci 0000:00:07.0: enabling Extended Tags
[    0.744802] pci 0000:00:07.0: PME# supported from D0 D3hot D3cold
[    0.744897] pci 0000:00:10.0: [1022:7812] type 00 class 0x0c0330
[    0.744925] pci 0000:00:10.0: reg 0x10: [mem 0xfeb46000-0xfeb47fff 64bit]
[    0.745034] pci 0000:00:10.0: PME# supported from D0 D3hot D3cold
[    0.745130] pci 0000:00:10.1: [1022:7812] type 00 class 0x0c0330
[    0.745158] pci 0000:00:10.1: reg 0x10: [mem 0xfeb44000-0xfeb45fff 64bit]
[    0.745267] pci 0000:00:10.1: PME# supported from D0 D3hot D3cold
[    0.745362] pci 0000:00:11.0: [1022:7801] type 00 class 0x010601
[    0.745381] pci 0000:00:11.0: reg 0x10: [io  0xf140-0xf147]
[    0.745390] pci 0000:00:11.0: reg 0x14: [io  0xf130-0xf133]
[    0.745398] pci 0000:00:11.0: reg 0x18: [io  0xf120-0xf127]
[    0.745406] pci 0000:00:11.0: reg 0x1c: [io  0xf110-0xf113]
[    0.745414] pci 0000:00:11.0: reg 0x20: [io  0xf100-0xf10f]
[    0.745423] pci 0000:00:11.0: reg 0x24: [mem 0xfeb4d000-0xfeb4d7ff]
[    0.745524] pci 0000:00:12.0: [1022:7807] type 00 class 0x0c0310
[    0.745543] pci 0000:00:12.0: reg 0x10: [mem 0xfeb4c000-0xfeb4cfff]
[    0.745663] pci 0000:00:12.2: [1022:7808] type 00 class 0x0c0320
[    0.745682] pci 0000:00:12.2: reg 0x10: [mem 0xfeb4b000-0xfeb4b0ff]
[    0.745757] pci 0000:00:12.2: supports D1 D2
[    0.745758] pci 0000:00:12.2: PME# supported from D0 D1 D2 D3hot
[    0.745835] pci 0000:00:13.0: [1022:7807] type 00 class 0x0c0310
[    0.745851] pci 0000:00:13.0: reg 0x10: [mem 0xfeb4a000-0xfeb4afff]
[    0.745970] pci 0000:00:13.2: [1022:7808] type 00 class 0x0c0320
[    0.745989] pci 0000:00:13.2: reg 0x10: [mem 0xfeb49000-0xfeb490ff]
[    0.746064] pci 0000:00:13.2: supports D1 D2
[    0.746065] pci 0000:00:13.2: PME# supported from D0 D1 D2 D3hot
[    0.746141] pci 0000:00:14.0: [1022:780b] type 00 class 0x0c0500
[    0.746257] pci 0000:00:14.2: [1022:780d] type 00 class 0x040300
[    0.746279] pci 0000:00:14.2: reg 0x10: [mem 0xfeb40000-0xfeb43fff 64bit]
[    0.746341] pci 0000:00:14.2: PME# supported from D0 D3hot D3cold
[    0.746410] pci 0000:00:14.3: [1022:780e] type 00 class 0x060100
[    0.746543] pci 0000:00:14.4: [1022:780f] type 01 class 0x060401
[    0.746648] pci 0000:00:14.5: [1022:7809] type 00 class 0x0c0310
[    0.746665] pci 0000:00:14.5: reg 0x10: [mem 0xfeb48000-0xfeb48fff]
[    0.746785] pci 0000:00:15.0: [1022:43a0] type 01 class 0x060400
[    0.746828] pci 0000:00:15.0: enabling Extended Tags
[    0.746872] pci 0000:00:15.0: supports D1 D2
[    0.746956] pci 0000:00:15.3: [1022:43a3] type 01 class 0x060400
[    0.747000] pci 0000:00:15.3: enabling Extended Tags
[    0.747044] pci 0000:00:15.3: supports D1 D2
[    0.747125] pci 0000:00:18.0: [1022:1400] type 00 class 0x060000
[    0.747191] pci 0000:00:18.1: [1022:1401] type 00 class 0x060000
[    0.747253] pci 0000:00:18.2: [1022:1402] type 00 class 0x060000
[    0.747316] pci 0000:00:18.3: [1022:1403] type 00 class 0x060000
[    0.747384] pci 0000:00:18.4: [1022:1404] type 00 class 0x060000
[    0.747445] pci 0000:00:18.5: [1022:1405] type 00 class 0x060000
[    0.747690] pci 0000:01:00.0: [1969:1091] type 00 class 0x020000
[    0.747921] pci 0000:01:00.0: reg 0x10: [mem 0xfea00000-0xfea3ffff 64bit]
[    0.747960] pci 0000:01:00.0: reg 0x18: [io  0xe000-0xe07f]
[    0.749012] pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[    0.749573] pci 0000:00:07.0: PCI bridge to [bus 01]
[    0.749577] pci 0000:00:07.0:   bridge window [io  0xe000-0xefff]
[    0.749579] pci 0000:00:07.0:   bridge window [mem 0xfea00000-0xfeafffff]
[    0.749592] pci_bus 0000:02: extended config space not accessible
[    0.749646] pci 0000:00:14.4: PCI bridge to [bus 02] (subtractive decode)
[    0.749654] pci 0000:00:14.4:   bridge window [io  0x0000-0x03af window] (subtractive decode)
[    0.749655] pci 0000:00:14.4:   bridge window [io  0x03e0-0x0cf7 window] (subtractive decode)
[    0.749656] pci 0000:00:14.4:   bridge window [io  0x03b0-0x03df window] (subtractive decode)
[    0.749657] pci 0000:00:14.4:   bridge window [io  0x0d00-0xffff window] (subtractive decode)
[    0.749658] pci 0000:00:14.4:   bridge window [mem 0x000a0000-0x000bffff window] (subtractive decode)
[    0.749659] pci 0000:00:14.4:   bridge window [mem 0x000c0000-0x000dffff window] (subtractive decode)
[    0.749660] pci 0000:00:14.4:   bridge window [mem 0xd0000000-0xffffffff window] (subtractive decode)
[    0.749698] pci 0000:00:15.0: PCI bridge to [bus 03]
[    0.749761] pci 0000:04:00.0: [1814:3290] type 00 class 0x028000
[    0.749786] pci 0000:04:00.0: reg 0x10: [mem 0xfe910000-0xfe91ffff]
[    0.749902] pci 0000:04:00.0: PME# supported from D0 D3hot
[    0.749982] pci 0000:04:00.1: [1814:3298] type 00 class 0x0d1100
[    0.750007] pci 0000:04:00.1: reg 0x10: [mem 0xfe900000-0xfe90ffff]
[    0.750123] pci 0000:04:00.1: supports D1
[    0.750124] pci 0000:04:00.1: PME# supported from D0 D1 D3hot
[    0.750222] pci 0000:00:15.3: PCI bridge to [bus 04]
[    0.750228] pci 0000:00:15.3:   bridge window [mem 0xfe900000-0xfe9fffff]
[    0.750480] ACPI: PCI Interrupt Link [LNKA] (IRQs 4 5 7 10 11 14 15) *0
[    0.750562] ACPI: PCI Interrupt Link [LNKB] (IRQs 4 5 7 10 11 14 15) *0
[    0.750615] ACPI: PCI Interrupt Link [LNKC] (IRQs 4 5 7 10 11 14 15) *0
[    0.750666] ACPI: PCI Interrupt Link [LNKD] (IRQs 4 5 7 10 11 14 15) *0
[    0.750707] ACPI: PCI Interrupt Link [LNKE] (IRQs 4 5 7 10 11 14 15) *0
[    0.750739] ACPI: PCI Interrupt Link [LNKF] (IRQs 4 5 7 10 11 14 15) *0
[    0.750770] ACPI: PCI Interrupt Link [LNKG] (IRQs 4 5 7 10 11 14 15) *0
[    0.750802] ACPI: PCI Interrupt Link [LNKH] (IRQs 4 5 7 10 11 14 15) *0
[    0.750963] iommu: Default domain type: Translated 
[    0.750975] pci 0000:00:01.0: vgaarb: setting as boot VGA device
[    0.750975] pci 0000:00:01.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
[    0.750975] pci 0000:00:01.0: vgaarb: bridge control possible
[    0.750975] vgaarb: loaded
[    0.750975] SCSI subsystem initialized
[    0.750975] libata version 3.00 loaded.
[    0.750975] ACPI: bus type USB registered
[    0.750975] usbcore: registered new interface driver usbfs
[    0.750975] usbcore: registered new interface driver hub
[    0.750975] usbcore: registered new device driver usb
[    0.750975] Registered efivars operations
[    0.751571] PCI: Using ACPI for IRQ routing
[    0.759840] PCI: pci_cache_line_size set to 64 bytes
[    0.760031] e820: reserve RAM buffer [mem 0x99c58000-0x9bffffff]
[    0.760033] e820: reserve RAM buffer [mem 0x9c435000-0x9fffffff]
[    0.760034] e820: reserve RAM buffer [mem 0x9dde1000-0x9fffffff]
[    0.760035] e820: reserve RAM buffer [mem 0x9e13e000-0x9fffffff]
[    0.760036] e820: reserve RAM buffer [mem 0x9e8f0000-0x9fffffff]
[    0.760037] e820: reserve RAM buffer [mem 0x9f000000-0x9fffffff]
[    0.760193] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[    0.760196] hpet0: 3 comparators, 32-bit 14.318180 MHz counter
[    0.761586] clocksource: Switched to clocksource tsc-early
[    0.761656] pnp: PnP ACPI init
[    0.761754] system 00:00: [mem 0xe0000000-0xefffffff] has been reserved
[    0.761759] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
[    0.761809] system 00:01: [mem 0xa0000000-0xcfffffff] has been reserved
[    0.761812] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.761973] system 00:02: [io  0x04d0-0x04d1] has been reserved
[    0.761974] system 00:02: [io  0x040b] has been reserved
[    0.761975] system 00:02: [io  0x04d6] has been reserved
[    0.761976] system 00:02: [io  0x0c00-0x0c01] has been reserved
[    0.761977] system 00:02: [io  0x0c14] has been reserved
[    0.761979] system 00:02: [io  0x0c50-0x0c51] has been reserved
[    0.761980] system 00:02: [io  0x0c52] has been reserved
[    0.761981] system 00:02: [io  0x0c6c] has been reserved
[    0.761982] system 00:02: [io  0x0c6f] has been reserved
[    0.761983] system 00:02: [io  0x0cd0-0x0cd1] has been reserved
[    0.761984] system 00:02: [io  0x0cd2-0x0cd3] has been reserved
[    0.761985] system 00:02: [io  0x0cd4-0x0cd5] has been reserved
[    0.761986] system 00:02: [io  0x0cd6-0x0cd7] has been reserved
[    0.761987] system 00:02: [io  0x0cd8-0x0cdf] has been reserved
[    0.761988] system 00:02: [io  0x0800-0x089f] has been reserved
[    0.761990] system 00:02: [io  0x0b20-0x0b3f] has been reserved
[    0.761992] system 00:02: [io  0x0900-0x090f] has been reserved
[    0.761993] system 00:02: [io  0x0910-0x091f] has been reserved
[    0.761996] system 00:02: [io  0xfe00-0xfefe] has been reserved
[    0.761998] system 00:02: [mem 0xfec00000-0xfec00fff] could not be reserved
[    0.761999] system 00:02: [mem 0xfee00000-0xfee00fff] has been reserved
[    0.762000] system 00:02: [mem 0xfed80000-0xfed8ffff] has been reserved
[    0.762002] system 00:02: [mem 0xfed61000-0xfed70fff] has been reserved
[    0.762003] system 00:02: [mem 0xfec10000-0xfec10fff] has been reserved
[    0.762004] system 00:02: [mem 0xfed00000-0xfed00fff] could not be reserved
[    0.762006] system 00:02: [mem 0xff000000-0xffffffff] has been reserved
[    0.762008] system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.762080] system 00:03: [io  0x0600-0x060f] has been reserved
[    0.762083] system 00:03: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.762137] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.762157] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
[    0.762199] system 00:06: [io  0x04d0-0x04d1] has been reserved
[    0.762202] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.762332] pnp: PnP ACPI: found 7 devices
[    0.763785] thermal_sys: Registered thermal governor 'fair_share'
[    0.763786] thermal_sys: Registered thermal governor 'bang_bang'
[    0.763787] thermal_sys: Registered thermal governor 'step_wise'
[    0.763787] thermal_sys: Registered thermal governor 'user_space'
[    0.768320] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[    0.768350] pci 0000:00:07.0: PCI bridge to [bus 01]
[    0.768353] pci 0000:00:07.0:   bridge window [io  0xe000-0xefff]
[    0.768356] pci 0000:00:07.0:   bridge window [mem 0xfea00000-0xfeafffff]
[    0.768361] pci 0000:00:14.4: PCI bridge to [bus 02]
[    0.768372] pci 0000:00:15.0: PCI bridge to [bus 03]
[    0.768381] pci 0000:00:15.3: PCI bridge to [bus 04]
[    0.768384] pci 0000:00:15.3:   bridge window [mem 0xfe900000-0xfe9fffff]
[    0.768391] pci_bus 0000:00: resource 4 [io  0x0000-0x03af window]
[    0.768392] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7 window]
[    0.768393] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df window]
[    0.768394] pci_bus 0000:00: resource 7 [io  0x0d00-0xffff window]
[    0.768395] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff window]
[    0.768396] pci_bus 0000:00: resource 9 [mem 0x000c0000-0x000dffff window]
[    0.768397] pci_bus 0000:00: resource 10 [mem 0xd0000000-0xffffffff window]
[    0.768398] pci_bus 0000:01: resource 0 [io  0xe000-0xefff]
[    0.768399] pci_bus 0000:01: resource 1 [mem 0xfea00000-0xfeafffff]
[    0.768400] pci_bus 0000:02: resource 4 [io  0x0000-0x03af window]
[    0.768401] pci_bus 0000:02: resource 5 [io  0x03e0-0x0cf7 window]
[    0.768402] pci_bus 0000:02: resource 6 [io  0x03b0-0x03df window]
[    0.768402] pci_bus 0000:02: resource 7 [io  0x0d00-0xffff window]
[    0.768403] pci_bus 0000:02: resource 8 [mem 0x000a0000-0x000bffff window]
[    0.768404] pci_bus 0000:02: resource 9 [mem 0x000c0000-0x000dffff window]
[    0.768405] pci_bus 0000:02: resource 10 [mem 0xd0000000-0xffffffff window]
[    0.768406] pci_bus 0000:04: resource 1 [mem 0xfe900000-0xfe9fffff]
[    0.768458] NET: Registered protocol family 2
[    0.768566] tcp_listen_portaddr_hash hash table entries: 4096 (order: 4, 65536 bytes, linear)
[    0.768583] TCP established hash table entries: 65536 (order: 7, 524288 bytes, linear)
[    0.768696] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear)
[    0.768965] TCP: Hash tables configured (established 65536 bind 65536)
[    0.769020] UDP hash table entries: 4096 (order: 5, 131072 bytes, linear)
[    0.769056] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes, linear)
[    0.769131] NET: Registered protocol family 1
[    0.769275] RPC: Registered named UNIX socket transport module.
[    0.769276] RPC: Registered udp transport module.
[    0.769276] RPC: Registered tcp transport module.
[    0.769277] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.769290] pci 0000:00:01.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
[    0.793945] pci 0000:00:12.0: quirk_usb_early_handoff+0x0/0x5ec took 23719 usecs
[    0.794104] pci 0000:00:12.2: PME# does not work under D3, disabling it
[    0.816945] pci 0000:00:13.0: quirk_usb_early_handoff+0x0/0x5ec took 22291 usecs
[    0.817104] pci 0000:00:13.2: PME# does not work under D3, disabling it
[    0.839933] pci 0000:00:14.5: quirk_usb_early_handoff+0x0/0x5ec took 22272 usecs
[    0.839955] pci 0000:01:00.0: set MSI_INTX_DISABLE_BUG flag
[    0.840024] PCI: CLS 64 bytes, default 64
[    0.840072] Trying to unpack rootfs image as initramfs...
[    0.854689] Freeing initrd memory: 1344K
[    0.854692] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    0.854694] software IO TLB: mapped [mem 0x9534f000-0x9934f000] (64MB)
[    0.854756] amd_uncore: AMD NB counters detected
[    0.854855] LVT offset 0 assigned for vector 0x400
[    0.854922] perf: AMD IBS detected (0x000000ff)
[    0.855224] Initialise system trusted keyrings
[    0.855285] workingset: timestamp_bits=40 max_order=21 bucket_order=0
[    0.856486] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.856628] NFS: Registering the id_resolver key type
[    0.856634] Key type id_resolver registered
[    0.856634] Key type id_legacy registered
[    0.856636] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    0.856880] Key type cifs.idmap registered
[    0.856882] ntfs: driver 2.1.32 [Flags: R/W].
[    0.856908] fuse: init (API version 7.31)
[    0.856983] SGI XFS with security attributes, realtime, no debug enabled
[    0.857384] aufs 5.4-20200622
[    0.860577] async_tx: api initialized (async)
[    0.860579] Key type asymmetric registered
[    0.860580] Asymmetric key parser 'x509' registered
[    0.860587] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[    0.861153] efifb: probing for efifb
[    0.861165] efifb: framebuffer at 0xd0000000, using 1984k, total 1984k
[    0.861166] efifb: mode is 800x600x32, linelength=3328, pages=1
[    0.861167] efifb: scrolling: redraw
[    0.861168] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[    0.861253] Console: switching to colour frame buffer device 100x37
[    0.862029] fb0: EFI VGA frame buffer device
[    0.862079] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
[    0.864986] ACPI: Power Button [PWRB]
[    0.865050] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
[    0.865852] ACPI: Power Button [PWRF]
[    0.874689] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.875098] Linux agpgart interface v0.103
[    0.876960] brd: module loaded
[    0.878463] loop: module loaded
[    0.880044] mtip32xx Version 1.3.1
[    0.880087] usbcore: registered new interface driver rtsx_usb
[    0.880386] ahci 0000:00:11.0: version 3.0
[    0.880611] ahci 0000:00:11.0: AHCI 0001.0300 32 slots 2 ports 6 Gbps 0x5 impl SATA mode
[    0.880614] ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part 
[    0.880907] scsi host0: ahci
[    0.881010] scsi host1: ahci
[    0.881102] scsi host2: ahci
[    0.881141] ata1: SATA max UDMA/133 abar m2048@0xfeb4d000 port 0xfeb4d100 irq 27
[    0.881141] ata2: DUMMY
[    0.881143] ata3: SATA max UDMA/133 abar m2048@0xfeb4d000 port 0xfeb4d200 irq 27
[    0.881672] Fusion MPT base driver 3.04.20
[    0.881673] Copyright (c) 1999-2008 LSI Corporation
[    0.881676] Fusion MPT SPI Host driver 3.04.20
[    0.881687] Fusion MPT FC Host driver 3.04.20
[    0.881701] Fusion MPT SAS Host driver 3.04.20
[    0.881717] Fusion MPT misc device (ioctl) driver 3.04.20
[    0.881756] mptctl: Registered with Fusion MPT base driver
[    0.881757] mptctl: /dev/mptctl @ (major,minor=10,220)
[    0.881758] Fusion MPT LAN driver 3.04.20
[    0.881792] VFIO - User Level meta-driver version: 0.3
[    0.881817] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    0.881818] ehci-pci: EHCI PCI platform driver
[    0.881911] QUIRK: Enable AMD PLL fix
[    0.881928] ehci-pci 0000:00:12.2: EHCI Host Controller
[    0.881933] ehci-pci 0000:00:12.2: new USB bus registered, assigned bus number 1
[    0.881938] ehci-pci 0000:00:12.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
[    0.881946] ehci-pci 0000:00:12.2: debug port 1
[    0.881978] ehci-pci 0000:00:12.2: irq 17, io mem 0xfeb4b000
[    0.888807] ehci-pci 0000:00:12.2: USB 2.0 started, EHCI 1.00
[    0.888853] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
[    0.888854] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.888855] usb usb1: Product: EHCI Host Controller
[    0.888856] usb usb1: Manufacturer: Linux 5.4.53 ehci_hcd
[    0.888857] usb usb1: SerialNumber: 0000:00:12.2
[    0.888985] hub 1-0:1.0: USB hub found
[    0.888990] hub 1-0:1.0: 5 ports detected
[    0.889294] ehci-pci 0000:00:13.2: EHCI Host Controller
[    0.889298] ehci-pci 0000:00:13.2: new USB bus registered, assigned bus number 2
[    0.889300] ehci-pci 0000:00:13.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
[    0.889310] ehci-pci 0000:00:13.2: debug port 1
[    0.889333] ehci-pci 0000:00:13.2: irq 17, io mem 0xfeb49000
[    0.895806] ehci-pci 0000:00:13.2: USB 2.0 started, EHCI 1.00
[    0.895849] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
[    0.895850] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.895851] usb usb2: Product: EHCI Host Controller
[    0.895852] usb usb2: Manufacturer: Linux 5.4.53 ehci_hcd
[    0.895853] usb usb2: SerialNumber: 0000:00:13.2
[    0.895981] hub 2-0:1.0: USB hub found
[    0.895986] hub 2-0:1.0: 5 ports detected
[    0.896224] ehci-platform: EHCI generic platform driver
[    0.896243] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    0.896251] ohci-pci: OHCI PCI platform driver
[    0.896354] ohci-pci 0000:00:12.0: OHCI PCI host controller
[    0.896358] ohci-pci 0000:00:12.0: new USB bus registered, assigned bus number 3
[    0.896380] ohci-pci 0000:00:12.0: irq 18, io mem 0xfeb4c000
[    0.951863] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.04
[    0.951865] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.951867] usb usb3: Product: OHCI PCI host controller
[    0.951867] usb usb3: Manufacturer: Linux 5.4.53 ohci_hcd
[    0.951868] usb usb3: SerialNumber: 0000:00:12.0
[    0.951987] hub 3-0:1.0: USB hub found
[    0.951995] hub 3-0:1.0: 5 ports detected
[    0.952221] ohci-pci 0000:00:13.0: OHCI PCI host controller
[    0.952225] ohci-pci 0000:00:13.0: new USB bus registered, assigned bus number 4
[    0.952251] ohci-pci 0000:00:13.0: irq 18, io mem 0xfeb4a000
[    1.007845] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.04
[    1.007848] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.007849] usb usb4: Product: OHCI PCI host controller
[    1.007850] usb usb4: Manufacturer: Linux 5.4.53 ohci_hcd
[    1.007850] usb usb4: SerialNumber: 0000:00:13.0
[    1.007978] hub 4-0:1.0: USB hub found
[    1.007985] hub 4-0:1.0: 5 ports detected
[    1.008219] ohci-pci 0000:00:14.5: OHCI PCI host controller
[    1.008222] ohci-pci 0000:00:14.5: new USB bus registered, assigned bus number 5
[    1.008244] ohci-pci 0000:00:14.5: irq 18, io mem 0xfeb48000
[    1.063832] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.04
[    1.063833] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.063835] usb usb5: Product: OHCI PCI host controller
[    1.063835] usb usb5: Manufacturer: Linux 5.4.53 ohci_hcd
[    1.063836] usb usb5: SerialNumber: 0000:00:14.5
[    1.063952] hub 5-0:1.0: USB hub found
[    1.063959] hub 5-0:1.0: 2 ports detected
[    1.064057] ohci-platform: OHCI generic platform driver
[    1.064067] uhci_hcd: USB Universal Host Controller Interface driver
[    1.064211] xhci_hcd 0000:00:10.0: xHCI Host Controller
[    1.064214] xhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 6
[    1.064371] xhci_hcd 0000:00:10.0: hcc params 0x014042c3 hci version 0x96 quirks 0x0000000000000608
[    1.064565] usb usb6: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
[    1.064566] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.064567] usb usb6: Product: xHCI Host Controller
[    1.064568] usb usb6: Manufacturer: Linux 5.4.53 xhci-hcd
[    1.064569] usb usb6: SerialNumber: 0000:00:10.0
[    1.064665] hub 6-0:1.0: USB hub found
[    1.064672] hub 6-0:1.0: 2 ports detected
[    1.064759] xhci_hcd 0000:00:10.0: xHCI Host Controller
[    1.064761] xhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 7
[    1.064763] xhci_hcd 0000:00:10.0: Host supports USB 3.0 SuperSpeed
[    1.067809] usb usb7: We don't know the algorithms for LPM for this host, disabling LPM.
[    1.067827] usb usb7: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.04
[    1.067828] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.067829] usb usb7: Product: xHCI Host Controller
[    1.067830] usb usb7: Manufacturer: Linux 5.4.53 xhci-hcd
[    1.067831] usb usb7: SerialNumber: 0000:00:10.0
[    1.067919] hub 7-0:1.0: USB hub found
[    1.067926] hub 7-0:1.0: 2 ports detected
[    1.068066] xhci_hcd 0000:00:10.1: xHCI Host Controller
[    1.068070] xhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 8
[    1.176903] xhci_hcd 0000:00:10.1: hcc params 0x014042c3 hci version 0x96 quirks 0x0000000000000608
[    1.177085] usb usb8: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
[    1.177086] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.177087] usb usb8: Product: xHCI Host Controller
[    1.177088] usb usb8: Manufacturer: Linux 5.4.53 xhci-hcd
[    1.177089] usb usb8: SerialNumber: 0000:00:10.1
[    1.177182] hub 8-0:1.0: USB hub found
[    1.177189] hub 8-0:1.0: 2 ports detected
[    1.177275] xhci_hcd 0000:00:10.1: xHCI Host Controller
[    1.177277] xhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 9
[    1.177279] xhci_hcd 0000:00:10.1: Host supports USB 3.0 SuperSpeed
[    1.180340] usb usb9: We don't know the algorithms for LPM for this host, disabling LPM.
[    1.180357] usb usb9: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.04
[    1.180358] usb usb9: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.180359] usb usb9: Product: xHCI Host Controller
[    1.180360] usb usb9: Manufacturer: Linux 5.4.53 xhci-hcd
[    1.180361] usb usb9: SerialNumber: 0000:00:10.1
[    1.180467] hub 9-0:1.0: USB hub found
[    1.180473] hub 9-0:1.0: 2 ports detected
[    1.180565] fotg210_hcd: FOTG210 Host Controller (EHCI) Driver
[    1.180566] Warning! fotg210_hcd should always be loaded before uhci_hcd and ohci_hcd, not after
[    1.180630] usbcore: registered new interface driver uas
[    1.180653] usbcore: registered new interface driver usb-storage
[    1.180660] usbcore: registered new interface driver ums-alauda
[    1.180666] usbcore: registered new interface driver ums-cypress
[    1.180673] usbcore: registered new interface driver ums-datafab
[    1.180679] usbcore: registered new interface driver ums_eneub6250
[    1.180685] usbcore: registered new interface driver ums-freecom
[    1.180691] usbcore: registered new interface driver ums-isd200
[    1.180696] usbcore: registered new interface driver ums-jumpshot
[    1.180703] usbcore: registered new interface driver ums-karma
[    1.180709] usbcore: registered new interface driver ums-onetouch
[    1.180716] usbcore: registered new interface driver ums-realtek
[    1.180722] usbcore: registered new interface driver ums-sddr09
[    1.180729] usbcore: registered new interface driver ums-sddr55
[    1.180734] usbcore: registered new interface driver ums-usbat
[    1.180752] i8042: PNP: No PS/2 controller found.
[    1.180752] i8042: Probing ports directly.
[    1.315557] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    1.315578] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    1.323540] usb 4-1: new low-speed USB device number 2 using ohci-pci
[    1.435561] usb 3-5: new full-speed USB device number 2 using ohci-pci
[    1.484827] usb 4-1: New USB device found, idVendor=0461, idProduct=4d65, bcdDevice= 2.00
[    1.484829] usb 4-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[    1.484830] usb 4-1: Product: USB Optical Mouse
[    1.597845] usb 3-5: New USB device found, idVendor=258a, idProduct=002a, bcdDevice=90.36
[    1.597847] usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    1.597849] usb 3-5: Product: Gaming KB 
[    1.597850] usb 3-5: Manufacturer: SINO WEALTH
[    1.715860] ata3.00: ATAPI: hp       CDDVDW SH-216BB, HE50, max UDMA/100
[    1.715877] ata1.00: supports DRM functions and may not be fully accessible
[    1.715921] i8042: Can't read CTR while initializing i8042
[    1.715934] i8042: probe of i8042 failed with error -5
[    1.716030] mousedev: PS/2 mouse device common for all mice
[    1.716165] rtc_cmos 00:05: RTC can wake from S4
[    1.716305] rtc_cmos 00:05: registered as rtc0
[    1.716306] rtc_cmos 00:05: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
[    1.716311] i2c /dev entries driver
[    1.716410] device-mapper: ioctl: 4.41.0-ioctl (2019-09-16) initialised: dm-devel@redhat.com
[    1.716421] sdhci: Secure Digital Host Controller Interface driver
[    1.716422] sdhci: Copyright(c) Pierre Ossman
[    1.716438] wbsd: Winbond W83L51xD SD/MMC card interface driver
[    1.716438] wbsd: Copyright(c) Pierre Ossman
[    1.716466] VUB300 Driver rom wait states = 1C irqpoll timeout = 0400
[    1.716595] usbcore: registered new interface driver vub300
[    1.716597] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.716681] EFI Variables Facility v0.08 2004-May-17
[    1.717080] ata1.00: ATA-10: Crucial_CT500MX200SSD1, MU02, max UDMA/133
[    1.717082] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 32), AA
[    1.719876] ata3.00: configured for UDMA/100
[    1.720997] ata1.00: supports DRM functions and may not be fully accessible
[    1.725864] ata1.00: configured for UDMA/133
[    1.725992] scsi 0:0:0:0: Direct-Access     ATA      Crucial_CT500MX2 MU02 PQ: 0 ANSI: 5
[    1.726145] ata1.00: Enabling discard_zeroes_data
[    1.726210] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[    1.726216] sd 0:0:0:0: [sda] 4096-byte physical blocks
[    1.726224] sd 0:0:0:0: [sda] Write Protect is off
[    1.726225] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    1.726264] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.726389] ata1.00: Enabling discard_zeroes_data
[    1.726682]  sda: sda1 sda2 sda3 sda4
[    1.726914] ata1.00: Enabling discard_zeroes_data
[    1.727019] sd 0:0:0:0: [sda] Attached SCSI disk
[    1.728228] hidraw: raw HID events driver (C) Jiri Kosina
[    1.728287] scsi 2:0:0:0: CD-ROM            hp       CDDVDW SH-216BB  HE50 PQ: 0 ANSI: 5
[    1.732126] input: USB Optical Mouse as /devices/pci0000:00/0000:00:13.0/usb4/4-1/4-1:1.0/0003:0461:4D65.0001/input/input2
[    1.732216] hid-generic 0003:0461:4D65.0001: input,hidraw0: USB HID v1.11 Mouse [USB Optical Mouse] on usb-0000:00:13.0-1/input0
[    1.735122] input: SINO WEALTH Gaming KB  as /devices/pci0000:00/0000:00:12.0/usb3/3-5/3-5:1.0/0003:258A:002A.0002/input/input3
[    1.770371] sr 2:0:0:0: [sr0] scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2 cdda tray
[    1.770374] cdrom: Uniform CD-ROM driver Revision: 3.20
[    1.770550] sr 2:0:0:0: Attached scsi CD-ROM sr0
[    1.786676] hid-generic 0003:258A:002A.0002: input,hidraw1: USB HID v1.11 Keyboard [SINO WEALTH Gaming KB ] on usb-0000:00:12.0-5/input0
[    1.791482] input: SINO WEALTH Gaming KB  System Control as /devices/pci0000:00/0000:00:12.0/usb3/3-5/3-5:1.1/0003:258A:002A.0003/input/input4
[    1.842680] input: SINO WEALTH Gaming KB  Consumer Control as /devices/pci0000:00/0000:00:12.0/usb3/3-5/3-5:1.1/0003:258A:002A.0003/input/input5
[    1.842747] input: SINO WEALTH Gaming KB  Keyboard as /devices/pci0000:00/0000:00:12.0/usb3/3-5/3-5:1.1/0003:258A:002A.0003/input/input6
[    1.842837] hid-generic 0003:258A:002A.0003: input,hiddev96,hidraw2: USB HID v1.11 Keyboard [SINO WEALTH Gaming KB ] on usb-0000:00:12.0-5/input1
[    1.842863] usbcore: registered new interface driver usbhid
[    1.842864] usbhid: USB HID core driver
[    1.842865] exFAT: Version 1.3.0
[    1.842932] x86/pm: family 0x15 cpu detected, MSR saving is needed during suspending.
[    1.842999] NET: Registered protocol family 17
[    1.843076] Key type dns_resolver registered
[    1.843359] microcode: CPU0: patch_level=0x06001119
[    1.843364] microcode: CPU1: patch_level=0x06001119
[    1.843370] microcode: CPU2: patch_level=0x00000000
[    1.843375] microcode: CPU3: patch_level=0x00000000
[    1.843404] microcode: Microcode Update Driver: v2.2.
[    1.843410] IPI shorthand broadcast: enabled
[    1.843416] sched_clock: Marking stable (1843205148, 195449)->(1867088508, -23687911)
[    1.843476] registered taskstats version 1
[    1.843476] Loading compiled-in X.509 certificates
[    1.843496] Key type ._fscrypt registered
[    1.843497] Key type .fscrypt registered
[    1.843678] Btrfs loaded, crc32c=crc32c-generic
[    1.844373] Key type big_key registered
[    1.844675] Key type encrypted registered
[    1.844845] rtc_cmos 00:05: setting system clock to 2023-04-05T16:53:10 UTC (1680713590)
[    1.844950] acpi_cpufreq: overriding BIOS provided _PSD data
[    1.845357] Freeing unused kernel image memory: 1036K
[    1.851564] tsc: Refined TSC clocksource calibration: 3693.097 MHz
[    1.851572] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x6a77b97c529, max_idle_ns: 881590553545 ns
[    1.851592] clocksource: Switched to clocksource tsc
[    1.854567] Write protecting the kernel read-only data: 20480k
[    1.855121] Freeing unused kernel image memory: 2008K
[    1.855290] Freeing unused kernel image memory: 460K
[    1.855292] Run /init as init process
[    1.933789] usb 9-2: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[    1.952989] usb 9-2: New USB device found, idVendor=05e3, idProduct=0626, bcdDevice= 6.55
[    1.952991] usb 9-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    1.952992] usb 9-2: Product: USB3.1 Hub
[    1.952993] usb 9-2: Manufacturer: GenesysLogic
[    1.954762] hub 9-2:1.0: USB hub found
[    1.955362] hub 9-2:1.0: 4 ports detected
[    2.061559] usb 8-2: new high-speed USB device number 2 using xhci_hcd
[    2.193117] usb 8-2: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice= 6.55
[    2.193119] usb 8-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.193120] usb 8-2: Product: USB2.1 Hub
[    2.193121] usb 8-2: Manufacturer: GenesysLogic
[    2.194276] hub 8-2:1.0: USB hub found
[    2.194863] hub 8-2:1.0: 4 ports detected
[    2.254896] usb 9-2.3: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[    2.270484] usb 9-2.3: New USB device found, idVendor=152d, idProduct=1561, bcdDevice= 2.04
[    2.270487] usb 9-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.270488] usb 9-2.3: Product: SABRENT
[    2.270489] usb 9-2.3: Manufacturer: SABRENT
[    2.270490] usb 9-2.3: SerialNumber: DB9876543214E
[    2.275895] scsi host3: uas
[    2.276409] scsi 3:0:0:0: Direct-Access     SABRENT                   0204 PQ: 0 ANSI: 6
[    2.277697] sd 3:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[    2.277699] sd 3:0:0:0: [sdb] 4096-byte physical blocks
[    2.277859] sd 3:0:0:0: [sdb] Write Protect is off
[    2.277861] sd 3:0:0:0: [sdb] Mode Sense: 53 00 00 08
[    2.278165] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.278491] sd 3:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
[    2.278778] random: fast init done
[    2.280091]  sdb: sdb3
[    2.281410] sd 3:0:0:0: [sdb] Attached SCSI disk
[    2.342271] usb 9-2.4: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd
[    2.361742] usb 9-2.4: New USB device found, idVendor=05e3, idProduct=0748, bcdDevice=12.10
[    2.361744] usb 9-2.4: New USB device strings: Mfr=3, Product=4, SerialNumber=5
[    2.361745] usb 9-2.4: Product: USB Storage
[    2.361746] usb 9-2.4: Manufacturer: Generic
[    2.361746] usb 9-2.4: SerialNumber: 000000001210
[    2.363545] usb-storage 9-2.4:1.0: USB Mass Storage device detected
[    2.363665] scsi host4: usb-storage 9-2.4:1.0
[    2.594059] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[    3.388785] scsi 4:0:0:0: Direct-Access     Generic  MassStorageClass 1210 PQ: 0 ANSI: 6
[    3.390307] scsi 4:0:0:1: Direct-Access     Generic  MassStorageClass 1210 PQ: 0 ANSI: 6
[    3.391165] sd 4:0:0:0: [sdc] Attached SCSI removable disk
[    3.393570] scsi 4:0:0:2: Direct-Access     Generic  MassStorageClass 1210 PQ: 0 ANSI: 6
[    3.394406] sd 4:0:0:1: [sdd] Attached SCSI removable disk
[    3.395943] scsi 4:0:0:3: Direct-Access     Generic  MassStorageClass 1210 PQ: 0 ANSI: 6
[    3.397714] scsi 4:0:0:4: Direct-Access     Generic  MassStorageClass 1210 PQ: 0 ANSI: 6
[    3.399653] sd 4:0:0:2: [sde] Attached SCSI removable disk
[    3.402649] sd 4:0:0:3: [sdf] Attached SCSI removable disk
[    3.405404] sd 4:0:0:4: [sdg] Attached SCSI removable disk
[    3.753723] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[    5.845495] udevd[921]: starting version 3.2.9
[    5.862556] random: udevd: uninitialized urandom read (16 bytes read)
[    5.862604] random: udevd: uninitialized urandom read (16 bytes read)
[    5.862612] random: udevd: uninitialized urandom read (16 bytes read)
[    5.878878] udevd[922]: starting eudev-3.2.9
[    6.957141] urandom_read: 4 callbacks suppressed
[    6.957144] random: udevd: uninitialized urandom read (16 bytes read)
[    7.120821] input: HP WMI hotkeys as /devices/virtual/input/input7
[    7.121764] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20190816/psparse-529)
[    7.121775] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20190816/psparse-529)
[    7.291825] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0
[    7.291838] piix4_smbus 0000:00:14.0: Using register 0x2e for SMBus port selection
[    7.293458] piix4_smbus 0000:00:14.0: Auxiliary SMBus Host Controller at 0xb20
[    7.294690] [drm] radeon kernel modesetting enabled.
[    7.294749] radeon 0000:00:01.0: remove_conflicting_pci_framebuffers: bar 0: 0xd0000000 -> 0xdfffffff
[    7.294752] radeon 0000:00:01.0: remove_conflicting_pci_framebuffers: bar 2: 0xfeb00000 -> 0xfeb3ffff
[    7.294754] checking generic (d0000000 1f0000) vs hw (d0000000 10000000)
[    7.294755] fb0: switching to radeondrmfb from EFI VGA
[    7.295002] Console: switching to colour dummy device 80x25
[    7.295139] radeon 0000:00:01.0: vgaarb: deactivate vga console
[    7.295610] [drm] initializing kernel modesetting (ARUBA 0x1002:0x990C 0x103C:0x2AE0 0x00).
[    7.295648] ATOM BIOS: 113
[    7.295713] radeon 0000:00:01.0: VRAM: 768M 0x0000000000000000 - 0x000000002FFFFFFF (768M used)
[    7.295716] radeon 0000:00:01.0: GTT: 1024M 0x0000000030000000 - 0x000000006FFFFFFF
[    7.295722] [drm] Detected VRAM RAM=768M, BAR=256M
[    7.295723] [drm] RAM width 32bits DDR
[    7.297094] [TTM] Zone  kernel: Available graphics memory: 3661646 KiB
[    7.297095] [TTM] Zone   dma32: Available graphics memory: 2097152 KiB
[    7.297097] [TTM] Initializing pool allocator
[    7.297105] [TTM] Initializing DMA pool allocator
[    7.297130] [drm] radeon: 768M of VRAM memory ready
[    7.297132] [drm] radeon: 1024M of GTT memory ready.
[    7.297146] [drm] Loading ARUBA Microcode
[    7.316881] [drm] Internal thermal controller without fan control
[    7.316937] == power state 0 ==
[    7.316938] 	ui class: none
[    7.316938] 	internal class: uvd
[    7.316940] 	caps:
[    7.316941] 	uvd    vclk: 72381 dclk: 60800
[    7.316944] 		power level 0    sclk: 63334 vddc: 1249
[    7.316945] 		power level 1    sclk: 84445 vddc: 1274
[    7.316946] 	status:
[    7.316946] == power state 1 ==
[    7.316947] 	ui class: none
[    7.316947] 	internal class: uvd_mvc
[    7.316948] 	caps:
[    7.316949] 	uvd    vclk: 72381 dclk: 60800
[    7.316950] 		power level 0    sclk: 63334 vddc: 1249
[    7.316951] 		power level 1    sclk: 84445 vddc: 1274
[    7.316952] 	status:
[    7.316953] == power state 2 ==
[    7.316953] 	ui class: performance
[    7.316954] 	internal class: none
[    7.316954] 	caps:
[    7.316955] 	uvd    vclk: 0 dclk: 0
[    7.316957] 		power level 0    sclk: 30400 vddc: 999
[    7.316958] 		power level 1    sclk: 63334 vddc: 1249
[    7.316960] 		power level 2    sclk: 84445 vddc: 1274
[    7.316960] 	status:
[    7.316961] == power state 3 ==
[    7.316962] 	ui class: none
[    7.316962] 	internal class: boot
[    7.316963] 	caps:
[    7.316964] 	uvd    vclk: 0 dclk: 0
[    7.316965] 		power level 0    sclk: 20000 vddc: 1274
[    7.316965] 	status: c r b
[    7.316967] == power state 4 ==
[    7.316967] 	ui class: none
[    7.316968] 	internal class: thermal
[    7.316968] 	caps:
[    7.316969] 	uvd    vclk: 0 dclk: 0
[    7.316971] 		power level 0    sclk: 20000 vddc: 999
[    7.316971] 	status:
[    7.317077] [drm] radeon: dpm initialized
[    7.342307] [drm] Found VCE firmware/feedback version 50.0.1 / 17!
[    7.342320] [drm] GART: num cpu pages 262144, num gpu pages 262144
[    7.375336] [drm] PCIE GART of 1024M enabled (table at 0x00000000001D6000).
[    7.375459] radeon 0000:00:01.0: WB enabled
[    7.375462] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000030000c00 and cpu addr 0x(____ptrval____)
[    7.375847] radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0x(____ptrval____)
[    7.396057] radeon 0000:00:01.0: fence driver on ring 6 use gpu addr 0x0000000030000c18 and cpu addr 0x(____ptrval____)
[    7.396061] radeon 0000:00:01.0: fence driver on ring 7 use gpu addr 0x0000000030000c1c and cpu addr 0x(____ptrval____)
[    7.396062] radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000030000c04 and cpu addr 0x(____ptrval____)
[    7.396064] radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000030000c08 and cpu addr 0x(____ptrval____)
[    7.396066] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000030000c0c and cpu addr 0x(____ptrval____)
[    7.396067] radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000030000c10 and cpu addr 0x(____ptrval____)
[    7.396070] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    7.396070] [drm] Driver supports precise vblank timestamp query.
[    7.396072] radeon 0000:00:01.0: radeon: MSI limited to 32-bit
[    7.396118] radeon 0000:00:01.0: radeon: using MSI.
[    7.396142] [drm] radeon: irq initialized.
[    7.415071] [drm] ring test on 0 succeeded in 2 usecs
[    7.415080] [drm] ring test on 3 succeeded in 4 usecs
[    7.415086] [drm] ring test on 4 succeeded in 3 usecs
[    7.453077] udevd[1965]: '/bin/sh -c 'echo add_0000:00:14.2_pci_0x1022_0x780d_pci:v00001022d0000780Dsv0000103Csd00002AE0bc04sc03i00 >> /tmp/udevtrace.log'' [3097] terminated by signal 1 (Hangup)
[    7.461980] [drm] ring test on 5 succeeded in 1 usecs
[    7.482015] [drm] UVD initialized successfully.
[    7.491127] snd_hda_codec_idt hdaudioC0D3: autoconfig for 92HD73E1X5: line_outs=4 (0xc/0xf/0x10/0x11/0x0) type:speaker
[    7.491130] snd_hda_codec_idt hdaudioC0D3:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    7.491132] snd_hda_codec_idt hdaudioC0D3:    hp_outs=1 (0xa/0x0/0x0/0x0/0x0)
[    7.491133] snd_hda_codec_idt hdaudioC0D3:    mono: mono_out=0x0
[    7.491135] snd_hda_codec_idt hdaudioC0D3:    dig-out=0x22/0x0
[    7.491136] snd_hda_codec_idt hdaudioC0D3:    inputs:
[    7.491138] snd_hda_codec_idt hdaudioC0D3:      Front Mic=0xb
[    7.491139] snd_hda_codec_idt hdaudioC0D3:      Rear Mic=0xe
[    7.491140] snd_hda_codec_idt hdaudioC0D3:      Line=0xd
[    7.504121] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:14.2/sound/card0/input8
[    7.504193] input: HD-Audio Generic Front Mic as /devices/pci0000:00/0000:00:14.2/sound/card0/input9
[    7.504254] input: HD-Audio Generic Rear Mic as /devices/pci0000:00/0000:00:14.2/sound/card0/input10
[    7.504314] input: HD-Audio Generic Line as /devices/pci0000:00/0000:00:14.2/sound/card0/input11
[    7.504379] input: HD-Audio Generic Speaker Front as /devices/pci0000:00/0000:00:14.2/sound/card0/input12
[    7.504456] input: HD-Audio Generic Speaker Surround as /devices/pci0000:00/0000:00:14.2/sound/card0/input13
[    7.504525] input: HD-Audio Generic Speaker CLFE as /devices/pci0000:00/0000:00:14.2/sound/card0/input14
[    7.504606] input: HD-Audio Generic Speaker Side as /devices/pci0000:00/0000:00:14.2/sound/card0/input15
[    7.504659] input: HD-Audio Generic Front Headphone as /devices/pci0000:00/0000:00:14.2/sound/card0/input16
[    7.678995] [drm] ring test on 6 succeeded in 17 usecs
[    7.679006] [drm] ring test on 7 succeeded in 3 usecs
[    7.679006] [drm] VCE initialized successfully.
[    7.679191] [drm] ib test on ring 0 succeeded in 0 usecs
[    7.679248] [drm] ib test on ring 3 succeeded in 0 usecs
[    7.679302] [drm] ib test on ring 4 succeeded in 0 usecs
[    7.761331] alx 0000:01:00.0 eth0: Qualcomm Atheros AR816x/AR817x Ethernet [78:e3:b5:c2:aa:97]
[    7.800959] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    7.826358] input: PC Speaker as /devices/platform/pcspkr/input/input17
[    7.843254] Error: Driver 'pcspkr' is already registered, aborting...
[    7.853197] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    7.907239] rt2800pci 0000:04:00.0: enabling device (0100 -> 0102)
[    7.907372] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3290, rev 0015 detected
[    7.910914] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 3290 detected
[    7.910941] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[    8.211587] [drm] ib test on ring 5 succeeded
[    8.739711] [drm] ib test on ring 6 succeeded
[    9.244165] [drm] ib test on ring 7 succeeded
[    9.245097] [drm] Radeon Display Connectors
[    9.245099] [drm] Connector 0:
[    9.245099] [drm]   DP-1
[    9.245100] [drm]   HPD1
[    9.245101] [drm]   DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 0x653c
[    9.245102] [drm]   Encoders:
[    9.245103] [drm]     DFP1: INTERNAL_UNIPHY2
[    9.245104] [drm] Connector 1:
[    9.245104] [drm]   VGA-1
[    9.245105] [drm]   HPD2
[    9.245106] [drm]   DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548 0x654c 0x654c
[    9.245106] [drm]   Encoders:
[    9.245107] [drm]     CRT1: INTERNAL_UNIPHY2
[    9.245108] [drm]     CRT1: NUTMEG
[    9.245108] [drm] Connector 2:
[    9.245109] [drm]   DVI-D-1
[    9.245109] [drm]   HPD3
[    9.245110] [drm]   DDC: 0x6550 0x6550 0x6554 0x6554 0x6558 0x6558 0x655c 0x655c
[    9.245111] [drm]   Encoders:
[    9.245111] [drm]     DFP2: INTERNAL_UNIPHY
[    9.298145] switching from power state:
[    9.298147] 	ui class: none
[    9.298148] 	internal class: boot
[    9.298149] 	caps:
[    9.298150] 	uvd    vclk: 0 dclk: 0
[    9.298153] 		power level 0    sclk: 20000 vddc: 1274
[    9.298154] 	status: c b
[    9.298156] switching to power state:
[    9.298157] 	ui class: performance
[    9.298157] 	internal class: none
[    9.298158] 	caps:
[    9.298159] 	uvd    vclk: 0 dclk: 0
[    9.298160] 		power level 0    sclk: 30400 vddc: 999
[    9.298162] 		power level 1    sclk: 63334 vddc: 1249
[    9.298163] 		power level 2    sclk: 84445 vddc: 1274
[    9.298164] 	status: r
[    9.403176] [drm] fb mappable at 0xD03E9000
[    9.403178] [drm] vram apper at 0xD0000000
[    9.403179] [drm] size 4325376
[    9.403180] [drm] fb depth is 24
[    9.403181] [drm]    pitch is 5632
[    9.403259] fbcon: radeondrmfb (fb0) is primary device
[    9.501244] Console: switching to colour frame buffer device 170x48
[    9.503812] radeon 0000:00:01.0: fb0: radeondrmfb frame buffer device
[    9.510020] [drm] Initialized radeon 2.50.0 20080528 for 0000:00:01.0 on minor 0
[   14.975104] random: dbus-uuidgen: uninitialized urandom read (12 bytes read)
[   14.976542] random: ln: uninitialized urandom read (6 bytes read)
[   16.078865] alx 0000:01:00.0 eth0: NIC Up: 1 Gbps Full
[   16.467162] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
[   16.522376] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[   17.500577] radeon_dp_aux_transfer_native: 74 callbacks suppressed
[   21.313887] random: crng init done
root@main ~
--> 

======

Puppy Bytes, utube videos
https://www.youtube.com/channel/UCg-DUU ... u62_iqR-MA

======

dimkr
Posts: 2429
Joined: Wed Dec 30, 2020 6:14 pm
Has thanked: 53 times
Been thanked: 1203 times

Re: F96-CE_4 Latest Stable Release

Post by dimkr »

@gychang Can you repeat this in a Puppy that recognizes the card properly, and also share the output of lsmod?

User avatar
gychang
Posts: 591
Joined: Fri Aug 28, 2020 4:51 pm
Location: San Diego, CA
Has thanked: 206 times
Been thanked: 64 times

Re: F96-CE_4 Latest Stable Release

Post by gychang »

dimkr wrote: Thu Apr 06, 2023 6:59 am

@gychang Can you repeat this in a Puppy that recognizes the card properly, and also share the output of lsmod?

@dimkr I only have 2 PCs with pups that do not recognize the sd cards...

======

Puppy Bytes, utube videos
https://www.youtube.com/channel/UCg-DUU ... u62_iqR-MA

======

User avatar
wiak
Posts: 4082
Joined: Tue Dec 03, 2019 6:10 am
Location: Packing - big job
Has thanked: 65 times
Been thanked: 1208 times
Contact:

Re: F96-CE_4 Latest Stable Release

Post by wiak »

gychang wrote: Thu Apr 06, 2023 11:07 am
dimkr wrote: Thu Apr 06, 2023 6:59 am

@gychang Can you repeat this in a Puppy that recognizes the card properly, and also share the output of lsmod?

@dimkr I only have 2 PCs with pups that do not recognize the sd cards...

I think it is more meaningful if you can show the sd cards being recognised when running a Pup you feel they work with, but must be "in same machine". If you instead only tried them as working with different Pup on a different PC then the interface could be different type. Though they are SD cards it could be that that card reader is actually working like a usb stick interface at the end of the day whereas some PCs have special SD card slots (mmc dev types) that don't look like usb sticks (such as sdb and so on) if you see what I mean.
Anyway, are you able to boot some other Pup on that same computer and see if the SD cards are recognised? However, since usb sticks shouldn't be a problem would seem to me maybe a mmc (SD card interface) driver issue (PCI bus?).

Maybe(?) modules: sdhci sdhci-pci sdhci-acpi (EDIT: No. I think upup has the first two of these built in and that's all mmc needs if PCI bus I believe. Must be something else and seems to be seen as usb so would expect likes of sdb, sdc and so on - but maybe usb version module missing - like usb 1.1 or 2 or 3 or whatever?). EDIT2: actually it is a bit weird. All of ohci, ehci, uhci and xhci modules also seem to be built in kernel used by upup.

EDIT3: I gather ohci and ehci can clash in some way or other. Found this: https://www.linuxquestions.org/question ... ts-244761/
Then again maybe solution is just to remove modules for all but xhci since that is supposed to support all of usb types?

What does: lspci -v | grep USB
reveal?

https://www.tinylinux.info/
DOWNLOAD wd_multi for hundreds of 'distros' at your fingertips: viewtopic.php?p=99154#p99154
Αξίζει να μεταφραστεί;

User avatar
gychang
Posts: 591
Joined: Fri Aug 28, 2020 4:51 pm
Location: San Diego, CA
Has thanked: 206 times
Been thanked: 64 times

Re: F96-CE_4 Latest Stable Release

Post by gychang »

wiak wrote: Thu Apr 06, 2023 11:52 am
gychang wrote: Thu Apr 06, 2023 11:07 am

@gychang Can you repeat this in a Puppy that recognizes the card properly, and also share the output of lsmod?

What does: lspci -v | grep USB
reveal?

Code: Select all

root@main ~
-->  lspci -v | grep USB
00:10.0 USB controller: Advanced Micro Devices, Inc. 
	Subsystem: Hewlett-Packard Company FCH USB XH
00:10.1 USB controller: Advanced Micro Devices, Inc. 
	Subsystem: Hewlett-Packard Company FCH USB XH
00:12.0 USB controller: Advanced Micro Devices, Inc. 
	Subsystem: Hewlett-Packard Company FCH USB OH
00:12.2 USB controller: Advanced Micro Devices, Inc. 
	Subsystem: Hewlett-Packard Company FCH USB EH
00:13.0 USB controller: Advanced Micro Devices, Inc. 
	Subsystem: Hewlett-Packard Company FCH USB OH
00:13.2 USB controller: Advanced Micro Devices, Inc. 
	Subsystem: Hewlett-Packard Company FCH USB EH
00:14.5 USB controller: Advanced Micro Devices, Inc. 
--> 
Last edited by rockedge on Thu Apr 06, 2023 3:09 pm, edited 1 time in total.
Reason: fixed orphaned quote tag

======

Puppy Bytes, utube videos
https://www.youtube.com/channel/UCg-DUU ... u62_iqR-MA

======

dimkr
Posts: 2429
Joined: Wed Dec 30, 2020 6:14 pm
Has thanked: 53 times
Been thanked: 1203 times

Re: F96-CE_4 Latest Stable Release

Post by dimkr »

gychang wrote: Thu Apr 06, 2023 11:07 am

@dimkr I only have 2 PCs with pups that do not recognize the sd cards...

I can fix this in all woof-CE kernels and this fix will propagate into most Puppy releases over time, but you'll need to help me help you. Sorry, I don't have this hardware and can't isolate the problem myself.

fr-ke
Posts: 107
Joined: Mon Nov 07, 2022 3:18 pm
Has thanked: 4 times
Been thanked: 35 times

Re: F96-CE_4 Latest Stable Release

Post by fr-ke »

The built-in GUI to Qemu, /usr/bin/qemu_gui, does not recognize kvm if it is a built-in kernel module.

As a result, there is an indication of a lack of bios settings and hardware support is not applied.
I have extended line 29 to query for a built-in kernel module kvm.

Code: Select all

if [ "`lsmod | grep kvm_`" ] || [ "`cat /lib/modules/$(uname -r)/modules.builtin | grep kvm`" ]; then

Works for me

However, my scripting skills are extremely limited. Mainly copy and paste and try.
So maybe more of a hint than a solution.

Clarity
Posts: 3850
Joined: Fri Jul 24, 2020 10:59 pm
Has thanked: 1634 times
Been thanked: 528 times

Re: F96-CE_4 Latest Stable Release

Post by Clarity »

fr-ke wrote: Sat Apr 08, 2023 6:21 am

The built-in GUI to Qemu, /usr/bin/qemu_gui, does not recognize kvm if it is a built-in kernel module.

As a result, there is an indication of a lack of bios settings and hardware support is not applied.
I have extended line 29 to query for a built-in kernel module kvm.

Code: Select all

if [ "`lsmod | grep kvm_`" ] || [ "`cat /lib/modules/$(uname -r)/modules.builtin | grep kvm`" ]; then

...

Thanks.

I believe @norgo produced a solution to this aptly named "qemu_ready" that (I think) addresses this.

I have appealed to the WoofCE developers for considering including this tiny nifty utility. If it is ever included, the steps for 1st use of QEMU, after installation, on any PC is

  1. install QEMU packaging (current version is v7.3)

  2. Run 'qemu_ready' to fulfill setup with an alarm if not

  3. Run QEMU taking advantage of KVM acceleration
    Note: Only needs to ever be run once to ready a PC. Also could be useful in status checking to insure the PC has it active.

The utility is meaningful and helpful such that a user would KNOW front-ended that his PCs has the VM acceleration active should QEMU calls to use it.

Maybe someone who has GIT WoofCE access would also request they review. Other forum distros could also consider this tiny inclusion. It is beneficial to all QEMU users no matter the PC they have.

Hope this is helpful.

fr-ke
Posts: 107
Joined: Mon Nov 07, 2022 3:18 pm
Has thanked: 4 times
Been thanked: 35 times

Re: F96-CE_4 Latest Stable Release

Post by fr-ke »

von Clarity » Sa Apr 08, 2023 6:01 pm

fr-ke hat geschrieben: ↑Sa Apr 08, 2023 7:21 am

The built-in GUI to Qemu, /usr/bin/qemu_gui, does not recognize kvm if it is a built-in kernel module.

As a result, there is an indication of a lack of bios settings and hardware support is not applied.
I have extended line 29 to query for a built-in kernel module kvm.

Code: Alles auswählen

if [ "`lsmod | grep kvm_`" ] || [ "`cat /lib/modules/$(uname -r)/modules.builtin | grep kvm`" ]; then

...

Thanks.

I believe @norgo produced a solution to this aptly named "qemu_ready" that (I think) addresses this.

I have appealed to the WoofCE developers for considering including this tiny nifty utility. If it is ever included, the steps for 1st use of QEMU, after installation, on any PC is

install QEMU packaging (current version is v7.3)

Run 'qemu_ready' to fulfill setup with an alarm if not

Run QEMU taking advantage of KVM acceleration
Note: Only needs to ever be run once to ready a PC. Also could be useful in status checking to insure the PC has it active.

The utility is meaningful and helpful such that a user would KNOW front-ended that his PCs has the VM acceleration active should QEMU calls to use it.

Maybe someone who has GIT WoofCE access would also request they review. Other forum distros could also consider this tiny inclusion. It is beneficial to all QEMU users no matter the PC they have.

Hope this is helpful.

@Clarity
Adding another small program doesn't change the negative user experience when the GUI for Qemu, /usr/bin/qemu_gui, doesn't work properly.
The call works, but it runs extremely slowly without kvm, although it is integrated in the kernel.

Clarity
Posts: 3850
Joined: Fri Jul 24, 2020 10:59 pm
Has thanked: 1634 times
Been thanked: 528 times

Re: F96-CE_4 Latest Stable Release

Post by Clarity »

Hello @fr-ke
Did you notice GUI messages on that same thread this?

Not sure what your above post is saying. Was either of the items mentioned helpful?

Also, @Jasper has a great solution, today. You might want to try his package in your PUP.

fr-ke
Posts: 107
Joined: Mon Nov 07, 2022 3:18 pm
Has thanked: 4 times
Been thanked: 35 times

Re: F96-CE_4 Latest Stable Release

Post by fr-ke »

Hello @Clarity

I usually start qemu from the console or make a .desktop to start it with one click. In F96-CE_4 everything works to my satisfaction and super fast.

As a test I tried the qemu_qui integrated in F96-CE_4 and found that it runs without kvm support. So very slowly.

I then found out that qemu_gui only checks the subsequently loaded modules and does not recognize the ones already integrated in the kernel and incorrectly assumes that kvm support is missing.

With my post viewtopic.php?p=86378#p86378 I just wanted to point out that F96-CE_4 with the delivered kernel leads to unexpected results in this regard.

Unfortunately, my scripting skills aren't good enough to make a good suggestion on github about woof-CE, so I just pointed it out.

Just related to testing features in F96-CE which is getting better and better and I use it with great pleasure.

Clarity
Posts: 3850
Joined: Fri Jul 24, 2020 10:59 pm
Has thanked: 1634 times
Been thanked: 528 times

Re: F96-CE_4 Latest Stable Release

Post by Clarity »

I see now what you were sharing. Thanks for the follow-up.

You are VERY right, as @rockedge did this community a great help by allowing the kernel to take over that feature releasing a system user to search/add it via modprobe. This offers an advantage as it and the many others in the kernel is a key reason we use forum distros, today.

I knew of his update but my FossaPUP64 QEMU HOST that I test ISOs on is the same for past few years and does NOT have that kernel, thus that test for kernel presence was not tested by me. You are sharing that, unlike my old FossaPUP64, F96CE is using the latest kernel which has the feature built-in.

Thanks for bringing this to forum's attention. @norgo's 'qemu_ready' utility made available to the forum will need to be tested to see if an update is needed addressing the kernel presence. The utility tests and updates the HOST for system presence versus kernel presence, IIRC.

Please test, it you can, on your PC to see if qemu_ready detects KVM presence when your F96CE is the HOST. Report back, please. I will compare on my end with the test PCs I have.

This is a consideration as the kernel update is recent in PUPs.

Many of this forum community use QEMU KVM for the ability to run a single physical PC as if it were 2 or more PCs. When I use a VM, I usually run it in a single 'virtual' desktop allowing me to JUMP from things I run in the HOST PC and things that are being done in a VM. This way the ability to jump acts EXACTLY as a physical KVM device. Thusly, I have 2 or more PCs in front of me on my single physical FossaPUP, each merely a mouse-click away.

This is a major productivity gain in affording the testing of PUPs I do. I assume that other forum members who are developers use something similar when building and testing their application behaviors-compiling or their distro development...virtually and separately from their HOST system.

Running at over 98% of bare-metal is crazy fast for these forum distros.

fr-ke
Posts: 107
Joined: Mon Nov 07, 2022 3:18 pm
Has thanked: 4 times
Been thanked: 35 times

Re: F96-CE_4 Latest Stable Release

Post by fr-ke »

F64-CE_4 on bare metal without any adaptation, except installing gemu-7.1.50-fossapup-x86_64.pet:
Processor: Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz

qemu_gui reports missing BIOS settings and starts without KVM support.

qemu-ready-0.3.1-x86_64.pet installed and started gives "ready for QEMU"

I had this problem a few weeks ago on a ThinkPad T580 Core i5-8350U. From memory I had to reload a module so that qemu-ready-0.3.1-x86_64.pet recognized the KVM support. Unfortunately I won't have this laptop in the near future.

User avatar
rockedge
Site Admin
Posts: 6561
Joined: Mon Dec 02, 2019 1:38 am
Location: Connecticut,U.S.A.
Has thanked: 2770 times
Been thanked: 2646 times
Contact:

Re: F96-CE_4 Latest Stable Release

Post by rockedge »

I had to reload a module so that qemu-ready-0.3.1-x86_64.pet recognized the KVM support.

Also can't remember all of the details of what it took to get the script going with KVM support. I had this GUI working but moved that system to some location somewhere on the myriad of drives I have available, and now can;t piece together what the fixes were to get it going.

Pretty sure though that the system it worked well on was a Bionic64 (upup)

Clarity
Posts: 3850
Joined: Fri Jul 24, 2020 10:59 pm
Has thanked: 1634 times
Been thanked: 528 times

Re: F96-CE_4 Latest Stable Release

Post by Clarity »

Researching this problem on bare-metal by

  1. booting F96CE4, pristine, from its ISO file using either Ventoy/SG2D

  2. adding QEMU v7+ to the pristine system

  3. checking for KVM modules loaded listing before running qemu_ready

  4. adding qemu_ready PET

  5. RUN qemu-ready

  6. checking for KVM modules loaded listing after running qemu_ready

  7. run qemu_gui for an ISO file boot

  8. look for terminal messages in the launch terminal output

Should have a report sometime tomorrow, if possible.

Before starting, does F96CE4 use the kernel with KVM built-in? If so, then this may, in fact, be something lacking in the QEMU GUI's terminal command it generates.

User avatar
gychang
Posts: 591
Joined: Fri Aug 28, 2020 4:51 pm
Location: San Diego, CA
Has thanked: 206 times
Been thanked: 64 times

Re: F96-CE_4 Latest Stable Release

Post by gychang »

Clarity wrote: Sat Apr 15, 2023 4:15 am

Researching this problem on bare-metal by

  1. booting F96CE4, pristine, from its ISO file using either Ventoy/SG2D

  2. adding QEMU v7+ to the pristine system

  3. checking for KVM modules loaded listing before running qemu_ready

  4. adding qemu_ready PET

  5. RUN qemu-ready

  6. checking for KVM modules loaded listing after running qemu_ready

  7. run qemu_gui for an ISO file boot

  8. look for terminal messages in the launch terminal output

Should have a report sometime tomorrow, if possible.

Before starting, does F96CE4 use the kernel with KVM built-in? If so, then this may, in fact, be something lacking in the QEMU GUI's terminal command it generates.

would be interested to know if Ventoy boots in UEFI, for me it does not.

======

Puppy Bytes, utube videos
https://www.youtube.com/channel/UCg-DUU ... u62_iqR-MA

======

Clarity
Posts: 3850
Joined: Fri Jul 24, 2020 10:59 pm
Has thanked: 1634 times
Been thanked: 528 times

Re: F96-CE_4 Latest Stable Release

Post by Clarity »

I am running into some ISO file boot issues on bare-metal. It could be hardware as this "i5 Intel" PC was recently reset to factory after an obvious firmware lost.

Progress reporting of tests I committed to is delayed while I try to work thru the issues.

geo_c
Posts: 2882
Joined: Fri Jul 31, 2020 3:37 am
Has thanked: 2208 times
Been thanked: 880 times

Re: F96-CE_4 Latest Stable Release

Post by geo_c »

So I just realized the F96 I'm running is CE_2 and we're at CE_4.

If I drop the CE_4 system files underneath my CE_2 pupsave will that that be problematic?

Should work OK, right?

I installed a bunch of stuff and don't feel like doing it again. I may if I must. Most of the CE_3 and CE_4 changes seem to be in the boot department, which is not a problem for me in CE_2. The kernel appears to be the same.

geo_c
Old School Hipster, and Such

User avatar
rockedge
Site Admin
Posts: 6561
Joined: Mon Dec 02, 2019 1:38 am
Location: Connecticut,U.S.A.
Has thanked: 2770 times
Been thanked: 2646 times
Contact:

Re: F96-CE_4 Latest Stable Release

Post by rockedge »

@geo_c it should be okay to use the save for _2 in _4

geo_c
Posts: 2882
Joined: Fri Jul 31, 2020 3:37 am
Has thanked: 2208 times
Been thanked: 880 times

Re: F96-CE_4 Latest Stable Release

Post by geo_c »

rockedge wrote: Wed May 03, 2023 4:29 am

@geo_c it should be okay to use the save for _2 in _4

Yes all working smoothly!

geo_c
Old School Hipster, and Such

Clarity
Posts: 3850
Joined: Fri Jul 24, 2020 10:59 pm
Has thanked: 1634 times
Been thanked: 528 times

Re: F96-CE_4 Latest Stable Release

Post by Clarity »

Finally got back to the "ISO file boot problem" discovered last week when booting via boot loaders.

Scenario:

  • PC is a desktop, circa 2015, i5 with 8GB

  • Desktop HOST is KLA_CE v1.9 with QEMU v8 installed

  • Ventoy v1.0.88 secure-boot turned off during USB create of the boot-loader

  • USB's "BOOTISOS" folder has 9 ISO files added including this F96CE ISO

  • This report is done with ALL test within a VM

    • The tests were done with 2 different soundcard definitions (BUT found NO difference as ALL audio is successful with either definition)

      • -device AC97

      • -audio driver=alsa,model=hda

    • The tests are also done with 2 different videocard definitions (AND, these make a difference is distro's desktop)

      • -vga cirrus

      • -vga std

  • All TESTS are done booting the Ventoy USB in the VM/
    Note: This methods is traditionally used. It reflects what I will see when booting the same USB on bare-metal. It is usually a DIRECT mapping of what will be seen in bare-metal tests using the old 64bit PCs I use for testing. On rare occasions, I will see case #2 below as the video cards are different by distro builds.

Case 1 - Ventoy USB booted in the VM ... Successful

  1. Open terminal and start QEMU as follows:

    Code: Select all

    qemu-system-x86_64 -enable-kvm -vga cirrus -m 2G -smp 2  -device AC97 -hda /dev/sdb
  2. Ventoy Menu, select F96CE

    V1.jpg
    V1.jpg (25.7 KiB) Viewed 4073 times
  3. Ventoy then ask if you want Normal or GRUB2, as in my past, I always choose GRUB2

    V2.jpg
    V2.jpg (23.29 KiB) Viewed 4073 times
  4. F96CE Menu emerges, I let the Menu default to its automatic start using its 1st stanza

    V3.jpg
    V3.jpg (16.29 KiB) Viewed 4073 times

F96CE boots to desktop and ALL distro subsystem perform as expected without ANY issues.

Case 2 - Ventoy USB booted in the VM ... UNsuccessful to desktop, but success to F96 console.

  • Use this QEMU stanza to see results...while ALL other steps are the same leading to F96's console
    This stanza is using -vga std

    Code: Select all

    qemu-system-x86_64 -enable-kvm -vga std -m 2G -smp 2  -device AC97 -hda /dev/sdb

Cannot start the desktop and stops at F96 Console.

Case 3&4 - Ventoy USB booted in VM ... Unsucessful as it traps after F96 attempts to boot.

  • The same VM stanza from both Case 1 and Case 2 were used.

  • BUT, after F96 chosen from Ventoy list, I chose the NORMAL option. This option leads to F96 trap/abend after the F96 default Menu start attempting to boot.

Summary results

  • Case 1 works for this distro straight away. GRUB2 selection WORKS!

  • Case 2 needs to find a way to start the desktop at the F96 console

  • Case 3&4 are native Ventoy use which doesn't work for most forum distros as well as this WoofCE PUP. NORMAL selection does NOT work,

These F96CE tests ONLY address Ventoy use without SG2D.

Hope this is clearly stated for easy to follow and/or replicate findings by development, if need.

Post Reply

Return to “F96-CE”