Puppy Linux Discussion Forum

Posted: **Fri Oct 09, 2020 9:57 am**

Fatdog has fbterm available/installed which caters for running a frambuffer, but in the default kernel build the frambuffer isn't set, so you can't for instance boot with parameters of ... nomodeset bbshell vga=ask ... and select a vesa based resolution and end up in a framebuffer. I recompiled the kernel (for Fatdog 810) to include the framebuffer, added a /dev/fb0 device into /dev, booted that and ran a statically compiled version of fbvnc - and that works very well. I vnc'd into my desktop system - that runs Fatdog from a DVD from my laptop that was setup as above and as fbvnc includes no compression it was somewhat heavy on LAN traffic flow. Setting up a ssh tunnel for the vnc connection however and where ssh compression was turned on, and that traffic flow dropped massively. A hour and a half of usage, including this posting, and less than 70MB of data transfer (as indicated by hovering the mouse over the network icon in the tray).

The addition to include framebuffer took several hours to compile on my 2 core laptop, and made next to no difference in the final vmlinuz/modules size. Perhaps a kernel .config tweak that might be made for future Fatdog versions?

I've set up my desktop system to use 640x480 resolution, and for me that's a vga=0x311 boot code (as indicated when booted with vga=ask) to have my laptop boot into the same 640x480x16 vesa resolution. At such low resolution running on both the laptop (framebuffer) and desktop (Fatdog DVD booted) the responsiveness is great, near as good as being at the desktop directly.

I actually used busybox init to boot i.e. the last command run in init is to exec /sbin/init ... where that is a sym link to busybox init, with no /etc/inittab busybox uses its own internal version that includes setting up several terminals (ctrl-alt-F1 .. F2 ...etc).

Sharing the same framebuffer is interesting if you have a vnc'd graphical session (i.e. into full Fatdog desktop on my desktop system) running a video running on say Ctrl-Alt-F1 on the laptop, and are viewing Ctrl-Alt-F2 as a terminal session - as the video 'bleeds' through, so you end up with a textual cli session, with the video also showing, wherever that might be placed in the gui session. With the version of fbvnc I compiled/used ctrl-L stops gui activity i.e. kills the 'bleed through'. Left running and not only does the video bleed through, but also any other changes, such as the clock minutes changes.

I have no actual measures, but the general feel is that fbvnc through ssh that uses compression, seems more responsive than tigervnc that uses its own compression.

With a bit of trickery, I suspect you could set up that vnc with a video showing on part of the desktop and all other fatdog items (tray etc) hidden out of view, and where that video window could be sized/positioned to 'fit' in with tmux panes being used on another terminal - so it looked like you were running a terminal/cli tmux session but where a video was playing in one of the tmux panes

Posted: **Fri Oct 09, 2020 10:18 am**

A bare laptop, maybe even without a disk, booted from a usb running Bulldog with framebuffer, ssh and fbvnc can with some tweaking be reduced down to < 10MB combined initrd and vmlinuz (I know for sure as that's what I'm currently using, excepting this laptop has a disk). Out and about and picking up 'free' wifi hotspots and you can boot, remove the USB to isolate it, then ssh tunnel vnc into your home desktop system, that might be running Fatdog from a DVD-R and also no disk. ... Very secure. IF the ssh to your home system is hacked, then a reboot has that resolved. If you lose your laptop, then there's nothing on it other than a boot to Linux cli - other than your .ssh keys folder content, which might be encrypted (I'm using ccrypt for that). No man in the middle attacks possible (or at least not without being flagged i.e. ssh keys would flag up that the servers keys had 'changed'), and even over 10Mbs wifi speeds the gui desktop experience is comfortably quick enough (and where your home based vnc server system may be pulling down web content at hard wired ethernet speeds).

I did run a quick test and ssh tunnelled from my laptop at home (London) to Germany, and then back again to my home base desktop (vnc server). The desktop experience of vnc through that two-hops did drop to 'usable' levels, not really good enough for general use. However in most cases that would be halved, from out and about to the home system, so I suspect in general the usability may generally be OK.

Posted: **Fri Oct 09, 2020 10:33 am**

Two and a half hours (that includes the likes of reading some yahoo news web pages ...etc.) and still less than 100MB (i.e. its the 'transmitted' figure from the desktop (gui) system that is a indication of the level of data/traffic flow to the laptop running the vnc client; The 'received' figure is a indicator of how much content was pulled down from the web by the vnc server (gui)). So 0.1Mbs perhaps.

: snap.jpg (75.3 KiB) Viewed 1123 times

Posted: **Fri Oct 09, 2020 3:14 pm**

Seeing a massive difference in the amount of data flow when comparing tunnelling vnc through a dropbear based ssh and when using OpenSSL's ssh tunnelling. Dropbear ssh is supposed to compress things by default, but whatever method it is using it doesn't compare to OpenSSL ssh with compression, at least not in respect to framebuffer vnc'ing.

Posted: **Fri Oct 09, 2020 4:36 pm**

rufwoof wrote: Fri Oct 09, 2020 9:57 am The addition to include framebuffer took several hours to compile on my 2 core laptop, and made next to no difference in the final vmlinuz/modules size. Perhaps a kernel .config tweak that might be made for future Fatdog versions?

Unlikely. Many framebuffer modules interfere with KMS.
But:
a) if you use KMS, you get framebuffer enabled, for free (just don't use "nomodeset"). Almost all of your framebuffer programs will work.
b) if you insist on using "nomodeset", then there is a framebuffer module included in Fatdog that you can use, it is called uvesafb.

Posted: **Sun Oct 11, 2020 8:28 am**

My laptop is AMD Radeon R2, so I suspect its not real native VESA, but still Radeons internal equivalent. It complains about a nomodeset boot parameter, but works with that, if removed then it hangs (well not really hang, rather the graphics don't show, commands can still be typed/run).

Much of graphics is a dark-art for me.

dmesg ....

Code: Select all

Linux version 4.19.149 (root@fatdog64-d37) (gcc version 7.3.0 (GCC)) #7 SMP Sun Oct 11 08:54:25 BST 2020
Command line: nomodeset video=vesa:mtrr=3,ywrap pci=nomsi,noaer vga=0x3D2
KERNEL supported cpus:
  AMD AuthenticAMD
x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
BIOS-provided physical RAM map:
BIOS-e820: [mem 0x0000000000000000-0x000000000009f3ff] usable
BIOS-e820: [mem 0x000000000009f400-0x000000000009ffff] reserved
BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
BIOS-e820: [mem 0x0000000000100000-0x00000000ba0bbfff] usable
BIOS-e820: [mem 0x00000000ba0bc000-0x00000000baabbfff] reserved
BIOS-e820: [mem 0x00000000baabc000-0x00000000bf6befff] usable
BIOS-e820: [mem 0x00000000bf6bf000-0x00000000bfabefff] reserved
BIOS-e820: [mem 0x00000000bfabf000-0x00000000bfbbefff] ACPI NVS
BIOS-e820: [mem 0x00000000bfbbf000-0x00000000bfbfefff] ACPI data
BIOS-e820: [mem 0x00000000bfbff000-0x00000000bfbfffff] usable
BIOS-e820: [mem 0x00000000bfc00000-0x00000000dfffffff] reserved
BIOS-e820: [mem 0x00000000f0800000-0x00000000f08fffff] reserved
BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
BIOS-e820: [mem 0x00000000fec00000-0x00000000fec01fff] reserved
BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
BIOS-e820: [mem 0x00000000fed80000-0x00000000fed80fff] reserved
BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
BIOS-e820: [mem 0x00000000ff800000-0x00000000ffffffff] reserved
BIOS-e820: [mem 0x0000000100000000-0x000000011effffff] usable
NX (Execute Disable) protection: active
SMBIOS 2.8 present.
DMI: Acer Aspire ES1-522/BELLEMERE_BE, BIOS V1.07 04/18/2016
tsc: Fast TSC calibration using PIT
tsc: Detected 1497.168 MHz processor
e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
e820: remove [mem 0x000a0000-0x000fffff] usable
last_pfn = 0x11f000 max_arch_pfn = 0x400000000
MTRR default type: uncachable
MTRR fixed ranges enabled:
  00000-9FFFF write-back
  A0000-BFFFF uncachable
  C0000-FFFFF write-through
MTRR variable ranges enabled:
  0 base 0000000000 mask FF80000000 write-back
  1 base 0080000000 mask FFC0000000 write-back
  2 base 00BFBA7000 mask FFFFFFF000 uncachable
  3 base 00FF800000 mask FFFF800000 write-protect
  4 disabled
  5 disabled
  6 disabled
  7 disabled
TOM2: 000000011f000000 aka 4592M
x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
last_pfn = 0xbfc00 max_arch_pfn = 0x400000000
Using GB pages for direct mapping
RAMDISK: [mem 0x7f3f6000-0x7ffeefff]
ACPI: Early table checksum verification disabled
ACPI: RSDP 0x00000000000FE020 000024 (v02 ACRSYS)
ACPI: XSDT 0x00000000BFBFE120 00009C (v01 ACRSYS ACRPRDCT 00000001      01000013)
ACPI: FACP 0x00000000BFBFC000 00010C (v05 ACRSYS ACRPRDCT 00000001 1025 00040000)
ACPI: DSDT 0x00000000BFBEC000 00B7C3 (v01 ACRSYS ACRPRDCT F0000000 1025 00040000)
ACPI: FACS 0x00000000BFB75000 000040
ACPI: UEFI 0x00000000BFBFD000 000236 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
ACPI: HPET 0x00000000BFBFB000 000038 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
ACPI: APIC 0x00000000BFBFA000 000090 (v03 ACRSYS ACRPRDCT 00000001 1025 00040000)
ACPI: MCFG 0x00000000BFBF9000 00003C (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
ACPI: ASF! 0x00000000BFBF8000 0000A5 (v32 ACRSYS ACRPRDCT 00000001 1025 00040000)
ACPI: BOOT 0x00000000BFBEB000 000028 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
ACPI: FPDT 0x00000000BFBE9000 000044 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
ACPI: MSDM 0x00000000BFBE8000 000055 (v03 ACRSYS ACRPRDCT 00000001 1025 00040000)
ACPI: SSDT 0x00000000BFBE7000 00050E (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
ACPI: SSDT 0x00000000BFBE2000 00489D (v02 ACRSYS ACRPRDCT 00000002 1025 00040000)
ACPI: SSDT 0x00000000BFBE1000 000418 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
ACPI: SSDT 0x00000000BFBDF000 0013F5 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
ACPI: SSDT 0x00000000BFBDE000 00008C (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
ACPI: SSDT 0x00000000BFBDC000 001138 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
ACPI: Local APIC address 0xfee00000
Zone ranges:
  DMA      [mem 0x0000000000001000-0x0000000000ffffff]
  DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
  Normal   [mem 0x0000000100000000-0x000000011effffff]
Movable zone start for each node
Early memory node ranges
  node   0: [mem 0x0000000000001000-0x000000000009efff]
  node   0: [mem 0x0000000000100000-0x00000000ba0bbfff]
  node   0: [mem 0x00000000baabc000-0x00000000bf6befff]
  node   0: [mem 0x00000000bfbff000-0x00000000bfbfffff]
  node   0: [mem 0x0000000100000000-0x000000011effffff]
Zeroed struct page in unavailable ranges: 9122 pages
Initmem setup node 0 [mem 0x0000000000001000-0x000000011effffff]
On node 0 totalpages: 908382
  DMA zone: 64 pages used for memmap
  DMA zone: 21 pages reserved
  DMA zone: 3998 pages, LIFO batch:0
  DMA32 zone: 12147 pages used for memmap
  DMA32 zone: 777408 pages, LIFO batch:63
  Normal zone: 1984 pages used for memmap
  Normal zone: 126976 pages, LIFO batch:31
ACPI: PM-Timer IO Port: 0x408
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
IOAPIC[0]: apic_id 4, version 33, address 0xfec00000, GSI 0-23
IOAPIC[1]: apic_id 5, version 33, address 0xfec01000, GSI 24-55
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
ACPI: IRQ0 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x10228210 base: 0xfed00000
smpboot: Allowing 4 CPUs, 2 hotplug CPUs
[mem 0xe0000000-0xf07fffff] available for PCI devices
clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370452778343963 ns
random: get_random_bytes called from start_kernel+0x89/0x411 with crng_init=0
setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:4 nr_node_ids:1
percpu: Embedded 34 pages/cpu s110232 r0 d29032 u524288
pcpu-alloc: s110232 r0 d29032 u524288 alloc=1*2097152
pcpu-alloc: [0] 0 1 2 3 
Built 1 zonelists, mobility grouping on.  Total pages: 894166
Kernel command line: nomodeset video=vesa:mtrr=3,ywrap pci=nomsi,noaer vga=0x3D2
You have booted with nomodeset. This means your GPU drivers are DISABLED
Any video related functionality will be severely degraded, and you may not even be able to suspend the system properly
Unless you actually understand what nomodeset does, you should reboot without enabling it
Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Memory: 3466500K/3633528K available (14344K kernel code, 781K rwdata, 3860K rodata, 940K init, 2256K bss, 167028K reserved, 0K cma-reserved)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
rcu: Hierarchical RCU implementation.
rcu: 	RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4.
rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
NR_IRQS: 4352, nr_irqs: 1000, preallocated irqs: 16
spurious 8259A interrupt: IRQ7.
Console: colour dummy device 80x25
console [tty0] enabled
ACPI: Core revision 20180810
clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484873504 ns
hpet clockevent registered
APIC: Switch to symmetric I/O mode setup
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x1594af4df2a, max_idle_ns: 440795240351 ns
Calibrating delay loop (skipped), value calculated using timer frequency.. 2995.10 BogoMIPS (lpj=4990560)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes)
BIOS may not properly restore RDRAND after suspend, hiding RDRAND via CPUID. Use rdrand=force to reenable.
Last level iTLB entries: 4KB 512, 2MB 8, 4MB 4
Last level dTLB entries: 4KB 512, 2MB 256, 4MB 128, 1GB 0
Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
Spectre V2 : Mitigation: Full AMD retpoline
Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp
Freeing SMP alternatives memory: 40K
smpboot: CPU0: AMD E1-7010 APU with AMD Radeon R2 Graphics (family: 0x16, model: 0x30, stepping: 0x1)
Performance Events: AMD PMU driver.
... version:                0
... bit width:              48
... generic registers:      4
... value mask:             0000ffffffffffff
... max period:             00007fffffffffff
... fixed-purpose events:   0
... event mask:             000000000000000f
rcu: Hierarchical SRCU implementation.
smp: Bringing up secondary CPUs ...
x86: Booting SMP configuration:
.... node  #0, CPUs:      #1
do_IRQ: 1.55 No irq handler for vector
smp: Brought up 1 node, 2 CPUs
smpboot: Max logical packages: 2
smpboot: Total of 2 processors activated (5991.20 BogoMIPS)
devtmpfs: initialized
PM: Registering ACPI NVS region [mem 0xbfabf000-0xbfbbefff] (1048576 bytes)
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370867519511994 ns
futex hash table entries: 1024 (order: 4, 65536 bytes)
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
cpuidle: using governor ladder
cpuidle: using governor menu
Simple Boot Flag at 0x44 set to 0x1
ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
ACPI: bus type PCI registered
PCI: Using configuration type 1 for base access
PCI: Using configuration type 1 for extended access
cryptd: max_cpu_qlen set to 1000
fbcon: Taking over console
ACPI: Added _OSI(Module Device)
ACPI: Added _OSI(Processor Device)
ACPI: Added _OSI(3.0 _SCP Extensions)
ACPI: Added _OSI(Processor Aggregator Device)
ACPI: Added _OSI(Linux-Dell-Video)
ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
ACPI: 7 ACPI AML tables successfully acquired and loaded
ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
ACPI: EC: EC started
ACPI: EC: interrupt blocked
ACPI: \_SB_.PCI0.LPC0.EC0_: Used as first EC
ACPI: \_SB_.PCI0.LPC0.EC0_: GPE=0x3, EC_CMD/EC_SC=0x66, EC_DATA=0x62
ACPI: \_SB_.PCI0.LPC0.EC0_: Used as boot DSDT EC to handle transactions
ACPI: Interpreter enabled
ACPI: (supports S0 S3 S5)
ACPI: Using IOAPIC for interrupt routing
PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
ACPI: Enabled 4 GPEs in block 00 to 1F
ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments]
acpi PNP0A08:00: _OSC: not requesting OS control; OS requires [ExtendedConfig ASPM ClockPM MSI]
acpi PNP0A08:00: ignoring host bridge window [mem 0x000cc000-0x000cffff window] (conflicts with Video ROM [mem 0x000c0000-0x000cebff])
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000c3fff window]
pci_bus 0000:00: root bus resource [mem 0x000c4000-0x000c7fff window]
pci_bus 0000:00: root bus resource [mem 0x000c8000-0x000cbfff window]
pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff window]
pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window]
pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window]
pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window]
pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff window]
pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff window]
pci_bus 0000:00: root bus resource [mem 0x000e8000-0x000ebfff window]
pci_bus 0000:00: root bus resource [mem 0x000ec000-0x000effff window]
pci_bus 0000:00: root bus resource [mem 0xe0000000-0xf7ffffff window]
pci_bus 0000:00: root bus resource [mem 0xfc000000-0xfed3ffff window]
pci_bus 0000:00: root bus resource [mem 0xfed45000-0xffffffff window]
pci_bus 0000:00: root bus resource [bus 00-ff]
pci 0000:00:00.0: [1022:1566] type 00 class 0x060000
pci 0000:00:01.0: [1002:9853] type 00 class 0x030000
pci 0000:00:01.0: reg 0x10: [mem 0xe0000000-0xefffffff 64bit pref]
pci 0000:00:01.0: reg 0x18: [mem 0xf0000000-0xf07fffff 64bit pref]
pci 0000:00:01.0: reg 0x20: [io  0x3000-0x30ff]
pci 0000:00:01.0: reg 0x24: [mem 0xf0c00000-0xf0c3ffff]
pci 0000:00:01.0: reg 0x30: [mem 0xfffe0000-0xffffffff pref]
pci 0000:00:01.0: enabling Extended Tags
pci 0000:00:01.0: supports D1 D2
pci 0000:00:01.0: PME# supported from D1 D2 D3hot
pci 0000:00:01.1: [1002:9840] type 00 class 0x040300
pci 0000:00:01.1: reg 0x10: [mem 0xf0c60000-0xf0c63fff 64bit]
pci 0000:00:01.1: enabling Extended Tags
pci 0000:00:01.1: supports D1 D2
pci 0000:00:02.0: [1022:156b] type 00 class 0x060000
pci 0000:00:02.3: [1022:1439] type 01 class 0x060400
pci 0000:00:02.3: enabling Extended Tags
pci 0000:00:02.3: PME# supported from D0 D3hot D3cold
pci 0000:00:02.4: [1022:1439] type 01 class 0x060400
pci 0000:00:02.4: enabling Extended Tags
pci 0000:00:02.4: PME# supported from D0 D3hot D3cold
pci 0000:00:08.0: [1022:1537] type 00 class 0x108000
pci 0000:00:08.0: reg 0x10: [mem 0xf0c40000-0xf0c5ffff 64bit pref]
pci 0000:00:08.0: reg 0x18: [mem 0xf0900000-0xf09fffff]
pci 0000:00:08.0: reg 0x1c: [mem 0xf0c70000-0xf0c70fff]
pci 0000:00:08.0: reg 0x24: [mem 0xf0c6a000-0xf0c6bfff]
pci 0000:00:10.0: [1022:7814] type 00 class 0x0c0330
pci 0000:00:10.0: reg 0x10: [mem 0xf0c68000-0xf0c69fff 64bit]
pci 0000:00:10.0: PME# supported from D0 D3hot D3cold
pci 0000:00:11.0: [1022:7801] type 00 class 0x010601
pci 0000:00:11.0: reg 0x10: [io  0x3118-0x311f]
pci 0000:00:11.0: reg 0x14: [io  0x3124-0x3127]
pci 0000:00:11.0: reg 0x18: [io  0x3110-0x3117]
pci 0000:00:11.0: reg 0x1c: [io  0x3120-0x3123]
pci 0000:00:11.0: reg 0x20: [io  0x3100-0x310f]
pci 0000:00:11.0: reg 0x24: [mem 0xf0c6f000-0xf0c6f3ff]
pci 0000:00:11.0: PME# supported from D3hot
pci 0000:00:12.0: [1022:7808] type 00 class 0x0c0320
pci 0000:00:12.0: reg 0x10: [mem 0xf0c6e000-0xf0c6e0ff]
pci 0000:00:12.0: supports D1 D2
pci 0000:00:12.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:13.0: [1022:7808] type 00 class 0x0c0320
pci 0000:00:13.0: reg 0x10: [mem 0xf0c6d000-0xf0c6d0ff]
pci 0000:00:13.0: supports D1 D2
pci 0000:00:13.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:14.0: [1022:780b] type 00 class 0x0c0500
pci 0000:00:14.2: [1022:780d] type 00 class 0x040300
pci 0000:00:14.2: reg 0x10: [mem 0xf0c64000-0xf0c67fff 64bit]
pci 0000:00:14.2: PME# supported from D0 D3hot D3cold
pci 0000:00:14.3: [1022:780e] type 00 class 0x060100
pci 0000:00:14.7: [1022:7813] type 00 class 0x080501
pci 0000:00:14.7: reg 0x10: [mem 0xf0c6c000-0xf0c6c0ff 64bit]
pci 0000:00:14.7: PME# supported from D3cold
pci 0000:00:18.0: [1022:1580] type 00 class 0x060000
pci 0000:00:18.1: [1022:1581] type 00 class 0x060000
pci 0000:00:18.2: [1022:1582] type 00 class 0x060000
pci 0000:00:18.3: [1022:1583] type 00 class 0x060000
pci 0000:00:18.4: [1022:1584] type 00 class 0x060000
pci 0000:00:18.5: [1022:1585] type 00 class 0x060000
pci 0000:01:00.0: [10ec:8168] type 00 class 0x020000
pci 0000:01:00.0: reg 0x10: [io  0x2000-0x20ff]
pci 0000:01:00.0: reg 0x18: [mem 0xf0b04000-0xf0b04fff 64bit]
pci 0000:01:00.0: reg 0x20: [mem 0xf0b00000-0xf0b03fff 64bit]
pci 0000:01:00.0: supports D1 D2
pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:02.3: PCI bridge to [bus 01]
pci 0000:00:02.3:   bridge window [io  0x2000-0x2fff]
pci 0000:00:02.3:   bridge window [mem 0xf0b00000-0xf0bfffff]
pci 0000:02:00.0: [168c:0036] type 00 class 0x028000
pci 0000:02:00.0: reg 0x10: [mem 0xf0a00000-0xf0a7ffff 64bit]
pci 0000:02:00.0: reg 0x30: [mem 0xffff0000-0xffffffff pref]
pci 0000:02:00.0: supports D1 D2
pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:02.4: PCI bridge to [bus 02]
pci 0000:00:02.4:   bridge window [mem 0xf0a00000-0xf0afffff]
pci_bus 0000:00: on NUMA node 0
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 10 11 12 14 15) *0
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 10 11 12 14 15) *0
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 10 11 12 14 15) *0
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 10 11 12 14 15) *0
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 10 11 12 14 15) *0
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 10 11 12 14 15) *0
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 10 11 12 14 15) *0
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 10 11 12 14 15) *0
ACPI: EC: interrupt unblocked
ACPI: EC: event unblocked
ACPI: \_SB_.PCI0.LPC0.EC0_: GPE=0x3, EC_CMD/EC_SC=0x66, EC_DATA=0x62
ACPI: \_SB_.PCI0.LPC0.EC0_: Used as boot DSDT EC to handle transactions and events
pci 0000:00:01.0: vgaarb: setting as boot VGA device
pci 0000:00:01.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
pci 0000:00:01.0: vgaarb: bridge control possible
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
ACPI: bus type USB registered
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
PCI: pci_cache_line_size set to 64 bytes
e820: reserve RAM buffer [mem 0x0009f400-0x0009ffff]
e820: reserve RAM buffer [mem 0xba0bc000-0xbbffffff]
e820: reserve RAM buffer [mem 0xbf6bf000-0xbfffffff]
e820: reserve RAM buffer [mem 0xbfc00000-0xbfffffff]
e820: reserve RAM buffer [mem 0x11f000000-0x11fffffff]
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
hpet0: 3 comparators, 32-bit 14.318180 MHz counter
clocksource: Switched to clocksource tsc-early
FS-Cache: Loaded
CacheFiles: Loaded
pnp: PnP ACPI init
system 00:00: [mem 0xfec00000-0xfec01fff] could not be reserved
system 00:00: [mem 0xfee00000-0xfee00fff] has been reserved
system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
pnp 00:01: Plug and Play ACPI device, IDs PNP0b00 (active)
pnp 00:02: Plug and Play ACPI device, IDs MSF0001 PNP0303 (active)
pnp 00:03: Plug and Play ACPI device, IDs ETD0502 PNP0f13 (active)
system 00:04: [io  0x0400-0x04cf] has been reserved
system 00:04: [io  0x04d0-0x04d1] has been reserved
system 00:04: [io  0x04d6] has been reserved
system 00:04: [io  0x0680-0x06ff] has been reserved
system 00:04: [io  0x077a] has been reserved
system 00:04: [io  0x0c00-0x0c01] has been reserved
system 00:04: [io  0x0c14] has been reserved
system 00:04: [io  0x0c50-0x0c52] has been reserved
system 00:04: [io  0x0c6c] has been reserved
system 00:04: [io  0x0c6f] has been reserved
system 00:04: [io  0x0cd0-0x0cdb] has been reserved
system 00:04: [io  0x0840-0x0847] has been reserved
system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:05: [mem 0x000e0000-0x000fffff] could not be reserved
system 00:05: [mem 0xff800000-0xffffffff] has been reserved
system 00:05: Plug and Play ACPI device, IDs PNP0c01 (active)
pnp: PnP ACPI: found 6 devices
clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
pci 0000:00:01.0: can't claim BAR 6 [mem 0xfffe0000-0xffffffff pref]: address conflict with Reserved [mem 0xff800000-0xffffffff]
pci 0000:02:00.0: can't claim BAR 6 [mem 0xffff0000-0xffffffff pref]: no compatible bridge window
pci 0000:00:01.0: BAR 6: assigned [mem 0xf0c80000-0xf0c9ffff pref]
pci 0000:00:02.3: PCI bridge to [bus 01]
pci 0000:00:02.3:   bridge window [io  0x2000-0x2fff]
pci 0000:00:02.3:   bridge window [mem 0xf0b00000-0xf0bfffff]
pci 0000:02:00.0: BAR 6: assigned [mem 0xf0a80000-0xf0a8ffff pref]
pci 0000:00:02.4: PCI bridge to [bus 02]
pci 0000:00:02.4:   bridge window [mem 0xf0a00000-0xf0afffff]
pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000c3fff window]
pci_bus 0000:00: resource 8 [mem 0x000c4000-0x000c7fff window]
pci_bus 0000:00: resource 9 [mem 0x000c8000-0x000cbfff window]
pci_bus 0000:00: resource 10 [mem 0x000d0000-0x000d3fff window]
pci_bus 0000:00: resource 11 [mem 0x000d4000-0x000d7fff window]
pci_bus 0000:00: resource 12 [mem 0x000d8000-0x000dbfff window]
pci_bus 0000:00: resource 13 [mem 0x000dc000-0x000dffff window]
pci_bus 0000:00: resource 14 [mem 0x000e0000-0x000e3fff window]
pci_bus 0000:00: resource 15 [mem 0x000e4000-0x000e7fff window]
pci_bus 0000:00: resource 16 [mem 0x000e8000-0x000ebfff window]
pci_bus 0000:00: resource 17 [mem 0x000ec000-0x000effff window]
pci_bus 0000:00: resource 18 [mem 0xe0000000-0xf7ffffff window]
pci_bus 0000:00: resource 19 [mem 0xfc000000-0xfed3ffff window]
pci_bus 0000:00: resource 20 [mem 0xfed45000-0xffffffff window]
pci_bus 0000:01: resource 0 [io  0x2000-0x2fff]
pci_bus 0000:01: resource 1 [mem 0xf0b00000-0xf0bfffff]
pci_bus 0000:02: resource 1 [mem 0xf0a00000-0xf0afffff]
NET: Registered protocol family 2
tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes)
TCP established hash table entries: 32768 (order: 6, 262144 bytes)
TCP bind hash table entries: 32768 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 32768 bind 32768)
UDP hash table entries: 2048 (order: 4, 65536 bytes)
UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
NET: Registered protocol family 1
pci 0000:00:01.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
pci 0000:00:01.1: Linked as a consumer to 0000:00:01.0
pci 0000:00:01.1: D0 power state depends on 0000:00:01.0
pci 0000:00:10.0: quirk_usb_early_handoff+0x0/0x603 took 10508 usecs
pci 0000:00:12.0: PME# does not work under D3, disabling it
pci 0000:00:13.0: PME# does not work under D3, disabling it
PCI: CLS 64 bytes, default 64
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 12260K
PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
software IO TLB: mapped [mem 0xbb6bf000-0xbf6bf000] (64MB)
amd_uncore: AMD NB counters detected
amd_uncore: AMD LLC counters detected
LVT offset 0 assigned for vector 0x400
perf: AMD IBS detected (0x000000ff)
kvm: Nested Virtualization enabled
kvm: Nested Paging enabled
Initialise system trusted keyrings
workingset: timestamp_bits=46 max_order=20 bucket_order=0
squashfs: version 4.0 (2009/01/31) Phillip Lougher
ntfs: driver 2.1.32 [Flags: R/W].
fuse init (API version 7.27)
tsc: Refined TSC clocksource calibration: 1497.191 MHz
clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x1594c522ce2, max_idle_ns: 440795237962 ns
clocksource: Switched to clocksource tsc
NET: Registered protocol family 38
Key type asymmetric registered
Asymmetric key parser 'x509' registered
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
io scheduler noop registered
io scheduler cfq registered (default)
vesafb: mode is 1366x768x16, linelength=2816, pages=6
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
vesafb: framebuffer at 0xe0000000, mapped to 0x(____ptrval____), using 4224k, total 16384k
Console: switching to colour frame buffer device 170x48
fb0: VESA VGA frame buffer device
ACPI: AC Adapter [ACAD] (on-line)
sysfs: cannot create duplicate filename '/class/power_supply/ACAD'
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.19.149 #7
Hardware name: Acer Aspire ES1-522/BELLEMERE_BE, BIOS V1.07 04/18/2016
Call Trace:
 ? dump_stack+0x50/0x63
 ? sysfs_warn_dup+0x4c/0x58
 ? sysfs_do_create_link_sd.isra.0+0x8d/0x99
 ? device_add+0x1fc/0x546
 ? __power_supply_register+0x235/0x388
 ? acpi_ac_add+0xe1/0x15c
 ? acpi_device_probe+0x4b/0xf9
 ? really_probe+0x141/0x287
 ? driver_probe_device+0x96/0xc6
 ? __driver_attach+0x88/0xb8
 ? driver_probe_device+0xc6/0xc6
 ? bus_for_each_dev+0x6c/0x9e
 ? bus_add_driver+0xe1/0x1ba
 ? set_debug_rodata+0xc/0xc
 ? driver_register+0x94/0xc6
 ? acpi_ac_init+0x86/0x8e
 ? ac_do_not_check_pmic_quirk+0xd/0xd
 ? do_one_initcall+0x6e/0x139
 ? set_debug_rodata+0xc/0xc
 ? kernel_init_freeable+0x116/0x19c
 ? rest_init+0xa0/0xa0
 ? kernel_init+0x5/0xf0
 ? ret_from_fork+0x22/0x40
ac: probe of ACPI0003:01 failed with error -17
input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
ACPI: Power Button [PWRB]
input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
ACPI: Sleep Button [SLPB]
input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2
ACPI: Lid Switch [LID]
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
ACPI: Power Button [PWRF]
ACPI: Video Device [VGA] (multi-head: yes  rom: no  post: no)
acpi device:00: registered as cooling_device0
input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input4
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
Linux agpgart interface v0.103
[drm] VGACON disable radeon kernel modesetting.
[drm:radeon_init] *ERROR* No UMS support in radeon module!
[drm:amdgpu_init] *ERROR* VGACON disables amdgpu kernel modesetting.
brd: module loaded
loop: module loaded
mtip32xx Version 1.3.1
ahci 0000:00:11.0: version 3.0
ahci 0000:00:11.0: AHCI 0001.0300 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp fbs pio slum part 
scsi host0: ahci
scsi host1: ahci
ata1: SATA max UDMA/133 abar m1024@0xf0c6f000 port 0xf0c6f100 irq 19
ata2: SATA max UDMA/133 abar m1024@0xf0c6f000 port 0xf0c6f180 irq 19
libphy: Fixed MDIO Bus: probed
r8169 0000:01:00.0: can't disable ASPM; OS doesn't have ASPM control
libphy: r8169: probed
r8169 0000:01:00.0 eth0: RTL8168g/8111g, 1c:39:47:9e:fd:af, XID 50900800, IRQ 26
r8169 0000:01:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
ath: phy0: WB335 2-ANT card detected
ath: phy0: Set BT/WLAN RX diversity capability
battery: ACPI: Battery Slot [BAT1] (battery present)
ath: phy0: Enable LNA combining
ath: phy0: ASPM enabled: 0x42
ath: EEPROM regdomain: 0x65
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: 00
ath: Regpair used: 0x65
ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
ieee80211 phy0: Atheros AR9565 Rev:1 mem=0xffffb1a800b80000, irq=27
Fusion MPT base driver 3.04.20
Copyright (c) 1999-2008 LSI Corporation
Fusion MPT SPI Host driver 3.04.20
Fusion MPT FC Host driver 3.04.20
Fusion MPT SAS Host driver 3.04.20
Fusion MPT misc device (ioctl) driver 3.04.20
mptctl: Registered with Fusion MPT base driver
mptctl: /dev/mptctl @ (major,minor=10,220)
Fusion MPT LAN driver 3.04.20
VFIO - User Level meta-driver version: 0.3
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ehci-pci 0000:00:12.0: EHCI Host Controller
ehci-pci 0000:00:12.0: new USB bus registered, assigned bus number 1
ehci-pci 0000:00:12.0: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
ehci-pci 0000:00:12.0: debug port 2
ehci-pci 0000:00:12.0: irq 18, io mem 0xf0c6e000
ehci-pci 0000:00:12.0: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 4.19.149 ehci_hcd
usb usb1: SerialNumber: 0000:00:12.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ehci-pci 0000:00:13.0: EHCI Host Controller
ehci-pci 0000:00:13.0: new USB bus registered, assigned bus number 2
ehci-pci 0000:00:13.0: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
ehci-pci 0000:00:13.0: debug port 2
ehci-pci 0000:00:13.0: irq 18, io mem 0xf0c6d000
ehci-pci 0000:00:13.0: USB 2.0 started, EHCI 1.00
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: EHCI Host Controller
usb usb2: Manufacturer: Linux 4.19.149 ehci_hcd
usb usb2: SerialNumber: 0000:00:13.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ehci-platform: EHCI generic platform driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-pci: OHCI PCI platform driver
ohci-platform: OHCI generic platform driver
uhci_hcd: USB Universal Host Controller Interface driver
xhci_hcd 0000:00:10.0: xHCI Host Controller
xhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 3
xhci_hcd 0000:00:10.0: hcc params 0x014040c3 hci version 0x100 quirks 0x0000000000000410
usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb3: Product: xHCI Host Controller
usb usb3: Manufacturer: Linux 4.19.149 xhci-hcd
usb usb3: SerialNumber: 0000:00:10.0
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
xhci_hcd 0000:00:10.0: xHCI Host Controller
xhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 4
xhci_hcd 0000:00:10.0: Host supports USB 3.0 SuperSpeed
usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19
usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb4: Product: xHCI Host Controller
usb usb4: Manufacturer: Linux 4.19.149 xhci-hcd
usb usb4: SerialNumber: 0000:00:10.0
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
fotg210_hcd: FOTG210 Host Controller (EHCI) Driver
Warning! fotg210_hcd should always be loaded before uhci_hcd and ohci_hcd, not after
usbcore: registered new interface driver uas
usbcore: registered new interface driver usb-storage
usbcore: registered new interface driver ums-alauda
usbcore: registered new interface driver ums-cypress
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums_eneub6250
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-isd200
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-karma
usbcore: registered new interface driver ums-onetouch
usbcore: registered new interface driver ums-realtek
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
usbcore: registered new interface driver ums-usbat
i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:MSE0] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mousedev: PS/2 mouse device common for all mice
rtc_cmos 00:01: RTC can wake from S4
rtc_cmos 00:01: registered as rtc0
rtc_cmos 00:01: alarms up to one month, 114 bytes nvram, hpet irqs
ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B0F (\_SB.PCI0.SMBS.SMB0) (20180810/utaddress-213)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-devel@redhat.com
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pci 0000:00:14.7: SDHCI controller found [1022:7813] (rev 1)
mmc0: SDHCI controller on PCI [0000:00:14.7] using ADMA
wbsd: Winbond W83L51xD SD/MMC card interface driver
wbsd: Copyright(c) Pierre Ossman
VUB300 Driver rom wait states = 1C irqpoll timeout = 0400
usbcore: registered new interface driver vub300
sdhci-pltfm: SDHCI platform and OF driver helper
ccp 0000:00:08.0: could not enable MSI-X (-22), trying MSI
ccp 0000:00:08.0: could not enable MSI (-22)
ccp 0000:00:08.0: initialization failed
ccp: probe of 0000:00:08.0 failed with error -22
hidraw: raw HID events driver (C) Jiri Kosina
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
acer_wmi: Acer Laptop ACPI-WMI Extras
acer_wmi: Function bitmap for Communication Button: 0x800
input: Acer WMI hotkeys as /devices/virtual/input/input6
x86/pm: family 0x16 cpu detected, MSR saving is needed during suspending.
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input5
NET: Registered protocol family 10
Segment Routing with IPv6
NET: Registered protocol family 17
8021q: 802.1Q VLAN Support v1.8
Key type dns_resolver registered
mce: Using 6 MCE banks
microcode: CPU0: patch_level=0x07030105
microcode: CPU1: patch_level=0x07030105
microcode: Microcode Update Driver: v2.2.
AVX version of gcm_enc/dec engaged.
AES CTR mode by8 optimization enabled
alg: No test for pcbc(aes) (pcbc-aes-aesni)
sched_clock: Marking stable (1982846671, 614991)->(1991316006, -7854344)
registered taskstats version 1
Loading compiled-in X.509 certificates
Key type big_key registered
Key type encrypted registered
rtc_cmos 00:01: setting system clock to 2020-10-11 09:10:48 UTC (1602407448)
acpi_cpufreq: overriding BIOS provided _PSD data
cfg80211: Loading compiled-in X.509 certificates for regulatory database
cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
cfg80211: failed to load regulatory.db
usb 1-1: new high-speed USB device number 2 using ehci-pci
usb 2-1: new high-speed USB device number 2 using ehci-pci
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ata2.00: ATAPI: HL-DT-ST DVDRAM GUE1N, 1.00, max UDMA/133
ata2.00: configured for UDMA/133
usb 1-1: New USB device found, idVendor=0438, idProduct=7900, bcdDevice= 0.18
usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
ata1.00: ATA-8: TOSHIBA MQ01ABD100, AX003J, max UDMA/100
ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 32), AA
ata1.00: configured for UDMA/100
scsi 0:0:0:0: Direct-Access     ATA      TOSHIBA MQ01ABD1 3J   PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
sd 0:0:0:0: [sda] 4096-byte physical blocks
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
scsi 1:0:0:0: CD-ROM            HL-DT-ST DVDRAM GUE1N     1.00 PQ: 0 ANSI: 5
usb 2-1: New USB device found, idVendor=0438, idProduct=7900, bcdDevice= 0.18
usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 4 ports detected
sr 1:0:0:0: [sr0] scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
cdrom: Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0
 sda: sda1 sda2 sda3 sda4
sd 0:0:0:0: [sda] Attached SCSI disk
Freeing unused kernel image memory: 940K
Write protecting the kernel read-only data: 20480k
Freeing unused kernel image memory: 2016K
Freeing unused kernel image memory: 236K
Run /init as init process
usb 1-1.2: new high-speed USB device number 3 using ehci-pci
usb 2-1.1: new high-speed USB device number 3 using ehci-pci
usb 1-1.2: New USB device found, idVendor=0781, idProduct=5581, bcdDevice= 1.00
usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1.2: Product: Ultra
usb 1-1.2: Manufacturer: SanDisk
usb 1-1.2: SerialNumber: 0501165196bf6e108e863a20c25422a9f3beb2cf9e14b50e8cbcf879c7644314f73b000000000000000000005888081200891210815581074ba6e74b
usb-storage 1-1.2:1.0: USB Mass Storage device detected
scsi host2: usb-storage 1-1.2:1.0
usb 2-1.1: New USB device found, idVendor=0bda, idProduct=0129, bcdDevice=39.60
usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1.1: Product: USB2.0-CRW
usb 2-1.1: Manufacturer: Generic
usb 2-1.1: SerialNumber: 20100201396000000
random: fast init done
usb 1-1.3: new full-speed USB device number 4 using ehci-pci
usb 1-1.3: New USB device found, idVendor=04ca, idProduct=300b, bcdDevice= 0.01
usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
usb 1-1.4: new high-speed USB device number 5 using ehci-pci
usb 1-1.4: New USB device found, idVendor=0bda, idProduct=57b3, bcdDevice= 3.21
usb 1-1.4: New USB device strings: Mfr=3, Product=1, SerialNumber=2
usb 1-1.4: Product: VGA Webcam
usb 1-1.4: Manufacturer: NC2141102N607092C3LM21
usb 1-1.4: SerialNumber: 200901010001
input: PS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio1/input/input8
scsi 2:0:0:0: Direct-Access     SanDisk  Ultra            1.00 PQ: 0 ANSI: 6
sd 2:0:0:0: [sdb] 30031872 512-byte logical blocks: (15.4 GB/14.3 GiB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 43 00 00 00
sd 2:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
 sdb: sdb1
sd 2:0:0:0: [sdb] Attached SCSI removable disk
random: crng init done
EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
usb 1-1.2: USB disconnect, device number 3
IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready[code]

Posted: **Mon Oct 12, 2020 9:48 am**

This is the fbvnc that I'm using. Fake .gz suffix - so it could be uploaded here, so just rename it to fbvnc

fbvnc.gz: (38.41 KiB) Downloaded 40 times

Booting fatdog into framebuffer cli mode for me means a grub4dos menu entry of

Code: Select all

title Bulldog 811 framebuffer
kernel /vmlinuz video=eDP-1:1366x768 nox basesfs=none savefile=none net=wpa:myssid:mypassword:wlan0:dhcp pkeys=uk
initrd /initrd

eDP-1 is the display name for my laptops lcd shown when I open Fatdog control panel, Desktop, Display, and its a 1366x768 resolution display

I connect via wifi and the net parameters specify the wireless ssid and password (that I've obviously changed here)

That basically boots into Bulldog i.e. Fatdogs initrd cli, with wifi net connected. To ensure that its running in framebuffer mode I run ... cat /dev/urandom >/dev/fb0 ... and the screen fills with random colour pixels.

Note that I've removed fd64.sfs from the initrd i.e. in rox click on initrd (after making a backup) and select fd64.sfs and delete it, then click the 'rebuild' icon to save/close that modified initrd

On my desktop system, with vnc server running (Menu, Network, X11VNC Server) where that box has a LAN IP of 192.168.1.4 (ifconfig will show that) I can then run that fbvnc program on the laptop
./fbvnc 192.168.1.4
... to vnc into the desktops Fatdog gui

That is slow compared to my pugdog (cutdown bulldog) boot however. Not too bad if I boot to 640x480 resolution i.e. change the menu.lst video parameter to video=eDP-1:640x480 ... and set the fatdog desktop system up to also be using 640x480 (you have to do quite a bit of scaling things down i.e. default global font size, theme font sizes ....etc.).

Whilst I've disabled radeon and amdgpu in my pugdog kernel to just leave a console vesa framebuffer, I think the radeon graphics card is still utilised by the kernel for that vesa framebuffer. Or perhaps its because the vesa framebuffer isn't compiled into the default Fatdog kernel (vmlinuz) - but as James has said, doing that can cause conflicts with 'normal' KMS (kernel mode setting graphics).

At the end of the day however, the above is all just purely for fun. It's better to boot into Fatdog and use TigerVNC for the client as that far better supports mouse/keys compared to fbvnc.

PS direct fbvnc in practice isn't a good idea, a bit like using telnet (insecure). More usually you'd set up a ssh tunnel. vnc uses port 5900 so a ssh command run on the laptop .. something like (change the 194.168.1.4 to your desktop vnc servers IP)

ssh -f -N -L 5900:localhost:5900 192.168.1.4

and then vnc to that ...
./fbvnc localhost

Of course ssh has to be running on the desktop server (Fatdog control panel, System, Manage Servers and Services and scan down for the sshd option and enable/start that).

Provided you're behind a router with a firewall, none of that should be accessible from outside, unless you login to the router and set up port forwarding to allow ssh traffic through to the 192.168.1.4 or whatever internal IP/box

Posted: **Mon Oct 12, 2020 10:42 am**

Ah! In my pugdog kernel build the key framebuffer entries seem to be to just have ...

CONFIG_FB=y

CONFIG_FB_SIMPLE=y

CONFIG_X86_SYSFB=y

CONFIG_FB_BOOT_VESA_SUPPORT=y

CONFIG_FB_VESA=y

defined ... so its the kernels vesa framebuffer that is being used. Don't enable the other drivers (radeon/amdgpu ...etc in my case).

With that I can boot with just

kernel /bzImage vga=0x3D2
initrd /initrd

to set 1366x768 framebuffer resolution (vga=ask will offer available vesa resolutions), and its that setup that has the framebuffer work really quick. I tracked down under /sys/class ... or some path like that and found a simple.0 reference i.e. using the kernels simple graphics driver, amongst that there were also things like rotate files, with a default entry of 0, but if I echo 1 >rotate it instantly rotated the screen through 90 degrees. 2 turned it upside down, 3 was 270 degree rotation, 0 set it back to 'normal'.

Could very well be radeon specific ??? Other gpu's might not accept being 'disabled' ???

For some fun with the framebuffer ...

https://archive.fosdem.org/2020/schedule/event/fbdev/

https://github.com/caramelli/higfxback/ ... ramebuffer

Posted: **Wed Oct 21, 2020 2:33 pm**

We tried FB_SIMPLE and X86_SYSFB back in 2013 and found out that they interfered with other drivers, so we never enabled them. The only good reason to use them is that if you use grub2 and set the grahics mode from grub2; in this case you can have a seamless transition between grub2 to kernel without ever dropping back to text mode.

We don't enable FB_VESA, we use FB_UVESA instead because supposedly it's more featureful that VESA.

Framebuffer is a understated features. Retropie, a retro gaming distro, runs completely on framebuffer. It doesn't run on Xorg at all. The main thing that Xorg does and framebuffer can't, is the multi-window feature.

Posted: **Wed Oct 28, 2020 9:32 am**

Presently I'm running a minimal boot system on my laptop (framebuffer/cli), and vnc from that through a compressed ssh tunnel into my desktop (fbvnc). On the desktop I have kvm/qemu running a modified (configured) fatdog image, that I've set to use multisession save, but having configured it I tend not to save after each use (so it starts 'clean' again at the next use). kvm/qemu does cater for copy on writes, snapshots etc, but I've opted to just use the more 'normal' method for that (i.e. fatdogs integral aufs/save (or not) layering).

When I have two vnc sessions running, both the kvm and normal (main session) desktops running, unless I turn the display off (ctrl-spacebar in fbvnc's case) before switching to the other session - then the sessions bleed over each other. Same for it I'm displaying a window in one session and using the cli in another (ctrl-alt-Fn) session. A vlc window showing a video (changing frequently) for instance will bleed over the cli session. Using that as a feature instead of a issue, you can arrange the cli session to avoid a particular screen area and align the graphical sessions active/changing window to that unused cli space, So you in effect have a cli session with a gui window such as a video on the visual 'display'.

I guess if I had a windows and linux kvm's running at the same time, each allocated one half of the screen, then the single view could see both at the same time on the frambuffer.

The main thing that Xorg does and framebuffer can't, is the multi-window feature.

I'd suggest that the framebuffer 'could' do multi-window, but be limited to not coping with overlapping windows very well. Rather than monitoring such overlaying of display regions its easier to just do it all within whatever gui session the framebuffer is displaying.

That minimal framebuffer boot (a 5.2MB frambuffer/ssh/vnc cli system in my case at present) that is used to access a full gui desktop display using vnc through a ssh compressed tunnel, works relatively well IME. Pretty secure as well i.e. a removable once booted usb boot stick at one end, and the gui desktop (fatdog) running in a kvm 'container' like environment at the other end. Where you can have multi-OS's available at the same time, and where there's even integral/native support for copy on write/snapshot (save or not) functionality.

That all aside, I did notice that the fatdog repo (gslapt) for the qemu gui program/script has a problem when you try to install it. I think the md5 may be wrong for that. i.e. doesn't 'Install' from the repo when selected to be installed (at least not for me).

Posted: **Wed Oct 28, 2020 1:29 pm**

rufwoof wrote: Wed Oct 28, 2020 9:32 am That all aside, I did notice that the fatdog repo (gslapt) for the qemu gui program/script has a problem when you try to install it. I think the md5 may be wrong for that. i.e. doesn't 'Install' from the repo when selected to be installed (at least not for me).

You mean qemu-vm-manager (qemu-vm-manager-1.3-noarch-1.txz)? I just tried to install it and it installed fine. I think you may have tried to install it at the same time we're updating the packages. Try refreshing your repo cache (slapt-get --update) and try to install it again.

Posted: **Wed Oct 28, 2020 1:33 pm**

Indeed. Just tried it and it installed fine. Thanks James.

Puppy Linux Discussion Forum

Framebuffer in Fatdog

Framebuffer in Fatdog

Re: Framebuffer

Re: Framebuffer

Re: Framebuffer

Re: Framebuffer

Re: Framebuffer

Re: Framebuffer

Re: Framebuffer

Re: Framebuffer in Fatdog

Re: Framebuffer in Fatdog

Re: Framebuffer in Fatdog

Re: Framebuffer in Fatdog