Booting with USB video adapter - blank screen flashing cursor (Watchguard XTM-5)

[aksala]

For starters, I tried to fix this without making a post so I searched and tried all the tricks I could find. I dont have a VGA port so I have a USB video adaptor. I cant see the boot screen because (I think) the usb video doesnt come alive until it starts booting so I cant select boot options. so it boots fine until XORG starts and then blinking cursor. CTRL-ALT-bkspc and I get a prompt. can ping internet and grep around. I think im either close, or its impossible. any pointers or suggestions would be great.

FYI
my linux knowledge - 3/10
personal intelligence - firmly midwit
stubbornness and motivation - 8/10

Watchguard XTM-5 (lol)
512M CF - flashed to this card and boots from this card
BIOS locked so I cant boot off USB
Celeron E3400 2.6G
2G Ram

console cable to serial port displays bios startup messages but then nothing afterwards
less /proc/sys/tty/driver/serial
0: uart:16550A port 00003F8 irq 4 tx:126 rx:0

report-video
VGA compatible controller Intel Corp 4 series chipset integrated graphics controller
kernel driver in use: i915
kernel modules: i915
modules requested to be loaded glx
drivers requested intel
probing xorg
driver loaded and in use intel
loaded modules dri2 dri3 glx present

Monitor: card1-DVI-I-1
Model Dell P190S
wxH cm 30x30

xorgwizard:
set video automatic, vesa, modesetting, fbdev, specified 'intel' (all with no success)

lsmod | grep 915
i915 1429504 0
i2c_algo_bit 16384 1 i915
drm_kms_heper 139264 2 udl, i915
drm 368640 4 udl,,drm_kms_helper, i915

less Xorg.0.log | grep 915
(II) intel(0) using kernel mode setting driver: i915, version 1.6.0 20190822

less xorg.conf
Section "Device"
Identifier "Card 0"
Driver "intel" #card0driver
BusID "0:2:0" #card0busid

lspci | grep VGA
VGA compatible controller: Intel Corp 4 series chipset integrated graphics controller rev 03

ls /etc/modprobe.d/
alsa-base.conf alsa.conf apm.conf ath9k.conf blacklist.conf puppy.conf radeon-dpn-conf

less sys/module/i915/parameters/modeset
-1

[rockedge]

to the forum!
Which Puppy Linux are you using?

You could try while at the console type in command: xorgwizard

This should start a wizard to help manage selecting a graphics driver and getting the Xorg server started.

[aksala]

Thanks! I downloaded fossapup64-9.5 and burned it to the CF with rufus.

trying xorgwizard I'm running through every option including specifying intel for driver. I get a couple different results, from blank screen blinking cursor. blank screen no blinking cursor, and the monitor shutting off. I can break out of all of them back to the command prompt with ctrl-alt-bkspc.

I am wondering if, for instance, VESA shuts off the monitor. perhaps it is working but sending video to the wrong destination (NOT the usb video adaptor) im currently working on seeing if I can get SSH working so I can interact with the device while its in a blind state.

[Jasper]

Why are using a USB video adaptor?

What is your device?

The i915 gfx driver is common place and readily supported in linux kernels.

[aksala]

its a watchguard firewall im goofing around with lol. theres no vga or display ports. basically I just want to run lcdproc and mess with the LCD panel but also it would be neat to get puppy working on it. I think im pretty close.

[Jasper]

So goofing around,what do you want to achieve?

What is the end game?

[aksala]

To play doom obviously. And not the ascii text based hahah. Seriously, to help me learn more about linux. Ive already put ubuntu on a Barracuda firewall but that was too easy. I would like to get a gui working, browse the internet a bit, install lcdproc, print hello world to the built in LCD screen. Rdp from/to it. Maybe run a minecraft server. I dont know. Im just learning.

[Flash]

What do you mean, the BIOS is locked? Do you mean you need a password to get into the BIOS? If that's the case, you might be able to reset the BIOS to its original factory settings, which don't require a password.

[aksala]

As far as I can tell, there isnt anywhere to even put a password in. Every option is read only. Reading on the pfsense forums says you could potentially flash the bios but its risky.

[rockedge]

currently working on seeing if I can get SSH working so I can interact with the device while its in a blind state.

try Dropbear for a ssh server

[Jasper]

Why is 'flashing' the BIOS risky?

It is a common practice for lots of devices from motherboards, Gfx cards, CD/DVDs, Android devices, routers etc.......

All that you should do is ensure that you have the correct firmware for your device and most importantly, 'Backup' the firmware when you begin the process.

This way if you do brick it, then you can reflash the original firmware back to the device.

So, the earlier attempt with Ubuntu was 'headless' ie no desktop environment?

If you can gather information regarding the components contained within the device, maybe build a custom kernel would be the way forward? This would minimise the overheads as you are using a CF card to hold the data.

You could try using Buildroot to achieve this:

https://buildroot.org/

[Flash]

So you can actually get into the BIOS, you just can't change any of the settings?

[aksala]

So you can actually get into the BIOS, you just can't change any of the settings?

seems to be. I went through every menu and sub-menu and theres no place to enter a password. to change the password is locked and displays "read only" I can change certain things like the parallel port and other stuff. not a huge deal I think, the CF is working fine. I just found a 1G and flashed pup onto it and booted off of that to give me a little more space for activities.

Why is 'flashing' the BIOS risky?

so this is where I am getting outside of my wheelhouse a bit. Im fairly technical Ive been working with routers and switches and firewalls for 10 years which is why I have a pile of old firewalls I can play with. Im worried I flash the bios, screw something up and then wont be able to figure out how to reflash the bios even back to stock. Im just not to that level of desperation yet.

So, the earlier attempt with Ubuntu was 'headless' ie no desktop environment?

nah the barracuda is happy over on my bench running ubuntu, if thats what you mean. I didnt attempt ubuntu on this watchguard... unless you mean the "Ubuntu Focal 64 x86_64 64-bit FossaPup64 9.5" which im not sure why it says ubuntu. please be patient with me, im midwit.

try Dropbear for a ssh server

nice. got ssh access into the puppy - going to probe around while its in blinking cursor state... and now I can cut paste log text and not manually type it to upload it here.

thanks for everyones help btw

[aksala]

okey

Code: Select all

#  lspci | grep vga -i
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)


/sys/devices/pci0000:00/0000:00:02.0
# ls
-r--r--r-- 1 root root      4096 Apr  7 21:01 ari_enabled
-r--r--r-- 1 root root      4096 Apr  7 20:20 boot_vga
-rw-r--r-- 1 root root      4096 Apr  7 21:01 broken_parity_status
-r--r--r-- 1 root root      4096 Apr  8  2024 class
-rw-r--r-- 1 root root       256 Apr  8  2024 config
-r--r--r-- 1 root root      4096 Apr  7 21:01 consistent_dma_mask_bits
-rw-r--r-- 1 root root      4096 Apr  7 21:01 d3cold_allowed
-r--r--r-- 1 root root      4096 Apr  8  2024 device
-r--r--r-- 1 root root      4096 Apr  7 21:01 dma_mask_bits
lrwxrwxrwx 1 root root         0 Apr  7 21:01 driver -> ../../../bus/pci/drivers/i915
-rw-r--r-- 1 root root      4096 Apr  7 21:01 driver_override
drwxr-xr-x 4 root root         0 Apr  8  2024 drm
-rw-r--r-- 1 root root      4096 Apr  7 21:01 enable
lrwxrwxrwx 1 root root         0 Apr  7 21:04 firmware_node -> ../../LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:1e
drwxr-xr-x 4 root root         0 Apr  8  2024 i2c-0
drwxr-xr-x 4 root root         0 Apr  8  2024 i2c-1
drwxr-xr-x 4 root root         0 Apr  8  2024 i2c-2
drwxr-xr-x 4 root root         0 Apr  8  2024 i2c-3
drwxr-xr-x 4 root root         0 Apr  8  2024 i2c-4
drwxr-xr-x 4 root root         0 Apr  8  2024 i2c-5
-r--r--r-- 1 root root      4096 Apr  8  2024 irq
-r--r--r-- 1 root root      4096 Apr  7 21:01 local_cpulist
-r--r--r-- 1 root root      4096 Apr  7 21:01 local_cpus
-r--r--r-- 1 root root      4096 Apr  8  2024 modalias
-rw-r--r-- 1 root root      4096 Apr  7 21:01 msi_bus
-rw-r--r-- 1 root root      4096 Apr  7 21:01 numa_node
drwxr-xr-x 2 root root         0 Apr  7 21:01 power
--w--w---- 1 root root      4096 Apr  7 21:01 remove
--w------- 1 root root      4096 Apr  7 21:01 rescan
--w------- 1 root root      4096 Apr  7 21:01 reset
-r--r--r-- 1 root root      4096 Apr  8  2024 resource
-rw------- 1 root root   4194304 Apr  7 21:01 resource0
-rw------- 1 root root 268435456 Apr  7 21:01 resource2
-rw------- 1 root root 268435456 Apr  7 21:01 resource2_wc
-rw------- 1 root root         8 Apr  7 21:01 resource4
-r--r--r-- 1 root root      4096 Apr  7 20:20 revision
-rw------- 1 root root    131072 Apr  7 21:01 rom
lrwxrwxrwx 1 root root         0 Apr  8  2024 subsystem -> ../../../bus/pci
-r--r--r-- 1 root root      4096 Apr  7 20:20 subsystem_device
-r--r--r-- 1 root root      4096 Apr  7 20:20 subsystem_vendor
-rw-r--r-- 1 root root      4096 Apr  8  2024 uevent
-r--r--r-- 1 root root      4096 Apr  8  2024 vendor




some output from Xorg log

[  1640.994] (**) ModulePath set to "/usr/lib/xorg/modules"
[  1640.994] (II) The server relies on udev to provide the list of input devices.
        If no devices become available, reconfigure udev or disable AutoAddDevices.
[  1640.994] (II) Loader magic: 0x5576057ea020
[  1640.994] (II) Module ABI versions:
[  1640.994]    X.Org ANSI C Emulation: 0.4
[  1640.994]    X.Org Video Driver: 24.1
[  1640.994]    X.Org XInput driver : 24.1
[  1640.994]    X.Org Server Extension : 10.0
[  1640.994] (--) using VT number 3

[  1640.994] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[  1640.995] (II) xfree86: Adding drm device (/dev/dri/card0)
[  1640.995] (II) xfree86: Adding drm device (/dev/dri/card1)
[  1641.001] (--) PCI:*(0@0:2:0) 8086:2e32:8086:2e32 rev 3, Mem @ 0xfe000000/4194304, 0xd0000000/268435456, I/O @ 0x00006800/8, BIOS @ 0x????????/131072
[  1641.001] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[  1641.001] (II) LoadModule: "glx"
[  1641.002] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  1641.003] (II) Module glx: vendor="X.Org Foundation"
[  1641.003]    compiled for 1.20.8, module version = 1.0.0
[  1641.003]    ABI class: X.Org Server Extension, version 10.0
[  1641.003] (==) Matched modesetting as autoconfigured driver 0
[  1641.003] (==) Matched fbdev as autoconfigured driver 1
[  1641.003] (==) Matched vesa as autoconfigured driver 2
[  1641.003] (==) Assigned the driver to the xf86ConfigLayout
[  1641.003] (II) LoadModule: "modesetting"
[  1641.004] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[  1641.016] (II) Module modesetting: vendor="X.Org Foundation"
[  1641.016]    compiled for 1.20.8, module version = 1.20.8
[  1641.016]    Module class: X.Org Video Driver
[  1641.017]    ABI class: X.Org Video Driver, version 24.1
[  1641.017] (II) LoadModule: "fbdev"
[  1641.017] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[  1641.017] (II) Module fbdev: vendor="X.Org Foundation"
[  1641.017]    compiled for 1.20.1, module version = 0.5.0
[  1641.017]    Module class: X.Org Video Driver
[  1641.017]    ABI class: X.Org Video Driver, version 24.0
[  1641.017] (II) LoadModule: "vesa"
[  1641.017] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[  1641.033] (II) Module vesa: vendor="X.Org Foundation"
[  1641.033]    compiled for 1.20.4, module version = 2.4.0
[  1641.033]    Module class: X.Org Video Driver
[  1641.033]    ABI class: X.Org Video Driver, version 24.0
[  1641.033] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[  1641.034] (II) FBDEV: driver for framebuffer: fbdev
[  1641.034] (II) VESA: driver for VESA chipsets: vesa
[  1641.036] (II) modeset(0): using drv /dev/dri/card0
[  1641.036] (WW) Falling back to old probe method for fbdev
[  1641.036] (II) Loading sub module "fbdevhw"
[  1641.036] (II) LoadModule: "fbdevhw"
[  1641.037] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[  1641.057] (II) Module fbdevhw: vendor="X.Org Foundation"
[  1641.057]    compiled for 1.20.8, module version = 0.0.2
[  1641.057]    ABI class: X.Org Video Driver, version 24.1
[  1641.057] (II) modeset(G0): using drv /dev/dri/card1
[  1641.057] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[  1641.057] (==) modeset(0): RGB weight 888
[  1641.057] (==) modeset(0): Default visual is TrueColor
[  1641.057] (II) Loading sub module "glamoregl"
[  1641.057] (II) LoadModule: "glamoregl"
[  1641.057] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[  1641.136] (II) Module glamoregl: vendor="X.Org Foundation"
[  1641.136]    compiled for 1.20.8, module version = 1.0.1
[  1641.136]    ABI class: X.Org ANSI C Emulation, version 0.4
[  1641.333] (II) modeset(0): glamor X acceleration enabled on Mesa DRI Intel(R) G41 (ELK)
[  1641.333] (II) modeset(0): glamor initialized
[  1641.347] (II) modeset(0): Output VGA-1 using monitor section Monitor0
[  1641.363] (II) modeset(0): EDID for output VGA-1
[  1641.364] (II) modeset(0): Output VGA-1 disconnected
[  1641.364] (WW) modeset(0): No outputs definitely connected, trying again...
[  1641.364] (II) modeset(0): Output VGA-1 disconnected
[  1641.364] (WW) modeset(0): Unable to find connected outputs - setting 1024x768 initial framebuffer
[  1641.364] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[  1641.364] (==) modeset(0): DPI set to (96, 96)
[  1641.364] (II) Loading sub module "fb"
[  1641.364] (II) LoadModule: "fb"
[  1641.364] (II) Loading /usr/lib/xorg/modules/libfb.so
[  1641.383] (II) Module fb: vendor="X.Org Foundation"
[  1641.383]    compiled for 1.20.8, module version = 1.0.0
[  1641.383]    ABI class: X.Org ANSI C Emulation, version 0.4
[  1641.384] (==) modeset(G0): Depth 24, (==) framebuffer bpp 32
[  1641.384] (==) modeset(G0): RGB weight 888
[  1641.384] (==) modeset(G0): Default visual is TrueColor
[  1641.384] (II) Loading sub module "glamoregl"
[  1641.384] (II) LoadModule: "glamoregl"
[  1641.384] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[  1641.384] (II) Module glamoregl: vendor="X.Org Foundation"
[  1641.384]    compiled for 1.20.8, module version = 1.0.1
[  1641.384]    ABI class: X.Org ANSI C Emulation, version 0.4
[  1643.023] (II) modeset(G0): Refusing to try glamor on llvmpipe
[  1643.024] (EE) modeset(G0): glamor initialization failed
[  1643.024] (II) modeset(G0): ShadowFB: preferred NO, enabled NO
[  1643.105] (II) modeset(G0): Output DVI-I-1-1 using monitor section Monitor0
[  1643.186] (II) modeset(G0): EDID for output DVI-I-1-1
[  1643.186] (II) modeset(G0): Manufacturer: DEL  Model: 405b  Serial#: 1112946515
[  1643.186] (II) modeset(G0): Year: 2009  Week: 37
[  1643.186] (II) modeset(G0): EDID Version: 1.3
[  1643.186] (II) modeset(G0): Digital Display Input
[  1643.186] (II) modeset(G0): Max Image Size [cm]: horiz.: 38  vert.: 30
[  1643.186] (II) modeset(G0): Gamma: 2.20
[  1643.186] (II) modeset(G0): DPMS capabilities: StandBy Suspend Off
[  1643.186] (II) modeset(G0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[  1643.186] (II) modeset(G0): Default color space is primary color space
[  1643.186] (II) modeset(G0): First detailed timing is preferred mode
[  1643.186] (II) modeset(G0): redX: 0.640 redY: 0.330   greenX: 0.300 greenY: 0.600
[  1643.186] (II) modeset(G0): blueX: 0.150 blueY: 0.060   whiteX: 0.313 whiteY: 0.329
[  1643.186] (II) modeset(G0): Supported established timings:
[  1643.186] (II) modeset(G0): 720x400@70Hz
[  1643.186] (II) modeset(G0): 640x480@60Hz
[  1643.186] (II) modeset(G0): 640x480@75Hz
[  1643.186] (II) modeset(G0): 800x600@60Hz
[  1643.186] (II) modeset(G0): 800x600@75Hz
[  1643.186] (II) modeset(G0): 1024x768@60Hz
[  1643.186] (II) modeset(G0): 1024x768@75Hz
[  1643.186] (II) modeset(G0): 1280x1024@75Hz
[  1643.186] (II) modeset(G0): Manufacturer's mask: 0
[  1643.186] (II) modeset(G0): Supported standard timings:
[  1643.186] (II) modeset(G0): #0: hsize: 1152  vsize 864  refresh: 75  vid: 20337
[  1643.186] (II) modeset(G0): #1: hsize: 1280  vsize 1024  refresh: 60  vid: 32897
[  1643.186] (II) modeset(G0): Supported detailed timing:
[  1643.186] (II) modeset(G0): clock: 108.0 MHz   Image Size:  376 x 301 mm
[  1643.186] (II) modeset(G0): h_active: 1280  h_sync: 1328  h_sync_end 1440 h_blank_end 1688 h_border: 0
[  1643.186] (II) modeset(G0): v_active: 1024  v_sync: 1025  v_sync_end 1028 v_blanking: 1066 v_border: 0
[  1643.186] (II) modeset(G0): Serial No: RNMH699CBV7S
[  1643.186] (II) modeset(G0): Monitor name: DELL P190S
[  1643.186] (II) modeset(G0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 81 kHz, PixClock max 145 MHz
[  1643.186] (II) modeset(G0): EDID (in hex):
[  1643.186] (II) modeset(G0):  00ffffffffffff0010ac5b4053375642
[  1643.186] (II) modeset(G0):  2513010380261e78eeee95a3544c9926
[  1643.186] (II) modeset(G0):  0f5054a54b00714f8180010101010101
[  1643.186] (II) modeset(G0):  010101010101302a009851002a403070
[  1643.186] (II) modeset(G0):  1300782d1100001e000000ff00524e4d
[  1643.186] (II) modeset(G0):  4836393943425637530a000000fc0044
[  1643.186] (II) modeset(G0):  454c4c2050313930530a2020000000fd
[  1643.186] (II) modeset(G0):  00384c1e510e000a2020202020200027
[  1643.186] (II) modeset(G0): Not using mode "640x480" (hsync out of range)
[  1643.186] (II) modeset(G0): Not using mode "720x400" (hsync out of range)
[  1643.186] (II) modeset(G0): Printing probed modes for output DVI-I-1-1
[  1643.186] (II) modeset(G0): Modeline "1280x1024"x60.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
[  1643.186] (II) modeset(G0): Modeline "1280x1024"x75.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[  1643.186] (II) modeset(G0): Modeline "1152x864"x75.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[  1643.186] (II) modeset(G0): Modeline "1024x768"x75.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[  1643.186] (II) modeset(G0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[  1643.186] (II) modeset(G0): Modeline "800x600"x75.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[  1643.186] (II) modeset(G0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[  1643.186] (II) modeset(G0): Modeline "640x480"x75.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[  1643.186] (==) modeset(G0): Using gamma correction (1.0, 1.0, 1.0)
[  1643.186] (==) modeset(G0): DPI set to (96, 96)
[  1643.186] (II) Loading sub module "fb"
[  1643.186] (II) LoadModule: "fb"
[  1643.186] (II) Loading /usr/lib/xorg/modules/libfb.so
[  1643.186] (II) Module fb: vendor="X.Org Foundation"
[  1643.186]    compiled for 1.20.8, module version = 1.0.0
[  1643.186]    ABI class: X.Org ANSI C Emulation, version 0.4
[  1643.186] (II) UnloadModule: "fbdev"
[  1643.186] (II) Unloading fbdev
[  1643.186] (II) UnloadSubModule: "fbdevhw"
[  1643.186] (II) Unloading fbdevhw
[  1643.186] (II) UnloadModule: "vesa"
[  1643.186] (II) Unloading vesa
[  1643.324] (==) modeset(0): Backing store enabled
[  1643.324] (==) modeset(0): Silken mouse enabled
[  1643.325] (II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
[  1643.325] (==) modeset(0): DPMS enabled
[  1643.325] (II) modeset(0): [DRI2] Setup complete
[  1643.325] (II) modeset(0): [DRI2]   DRI driver: i965
[  1643.325] (II) modeset(0): [DRI2]   VDPAU driver: va_gl
[  1643.325] (==) modeset(G0): Backing store enabled
[  1643.325] (==) modeset(G0): Silken mouse enabled
[  1643.325] (II) modeset(G0): Initializing kms color map for depth 24, 8 bpc.
[  1643.325] (==) modeset(G0): DPMS enabled
[  1643.325] (II) Initializing extension Generic Event Extension
[  1643.326] (II) Initializing extension SHAPE
[  1643.326] (II) Initializing extension MIT-SHM
[  1643.326] (II) Initializing extension XInputExtension
[  1643.326] (II) Initializing extension XTEST
[  1643.327] (II) Initializing extension BIG-REQUESTS
[  1643.327] (II) Initializing extension SYNC
[  1643.327] (II) Initializing extension XKEYBOARD
[  1643.327] (II) Initializing extension XC-MISC
[  1643.328] (II) Initializing extension SECURITY
[  1643.328] (II) Initializing extension XFIXES
[  1643.328] (II) Initializing extension RENDER
[  1643.328] (II) Initializing extension RANDR
[  1643.329] (II) Initializing extension COMPOSITE
[  1643.329] (II) Initializing extension DAMAGE
[  1643.329] (II) Initializing extension MIT-SCREEN-SAVER
[  1643.329] (II) Initializing extension DOUBLE-BUFFER
[  1643.329] (II) Initializing extension RECORD
[  1643.330] (II) Initializing extension DPMS
[  1643.330] (II) Initializing extension Present
[  1643.330] (II) Initializing extension DRI3
[  1643.330] (II) Initializing extension X-Resource
[  1643.331] (II) Initializing extension XVideo
[  1643.331] (II) Initializing extension XVideo-MotionCompensation
[  1643.331] (II) Initializing extension SELinux
[  1643.331] (II) SELinux: Disabled on system
[  1643.331] (II) Initializing extension GLX
[  1643.340] (II) AIGLX: Loaded and initialized i965
[  1643.340] (II) GLX: Initialized DRI2 GL provider for screen 0
[  1643.340] (II) Initializing extension XFree86-VidModeExtension
[  1643.341] (II) Initializing extension XFree86-DGA
[  1643.341] (II) Initializing extension XFree86-DRI
[  1643.341] (II) Initializing extension DRI2
[  1643.343] (II) modeset(G0): Damage tracking initialized
[  1643.346] (II) modeset(0): Damage tracking initialized

[rockedge]

nice. got ssh access into the puppy - going to probe around while its in blinking cursor state... and now I can cut paste log text and not manually type it to upload it here.

To make it really easy to work on a ssh terminal from a remote machine:
install mc_4.8.24 (midnight commander) from the repo into the Puppy Linux on the console command line ->

Code: Select all

pkg repo-update
pkg add mc_4.8.24

then try in the ssh termnal mc this makes navigating, managing, viewing and editing files easy.

Screenshot(3).jpg (124.99 KiB) Viewed 885 times

[aksala]

then try in the ssh termnal mc this makes navigating, managing, viewing and editing files easy.

done. thats really sassy-pants I like it thanks

[aksala]

maybe an issue with xorg vs the usb adaptor

device is a displaylink - i heard it was linux compatible.

# dmesg | grep usb
[ 1.574173] usb 1-2: new high-speed USB device number 3 using ehci-pci
[ 1.702351] usb 1-2: New USB device found, idVendor=17e9, idProduct=0059, bcdDevice= 1.02
[ 1.702355] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1.702358] usb 1-2: Product: IOGEAR External DVI
[ 1.702361] usb 1-2: Manufacturer: DisplayLink
[ 1.702364] usb 1-2: SerialNumber: 000176
[ 1.881478] usb 1-1.3: new low-speed USB device number 4 using ehci-pci

ok so thats good.

I *THINK* its this
# ls /dev | grep fb
fb0

# less /proc/fb
0 udldrmfb

# less /var/log/Xorg.0.log | grep fb
[ 1641.003] (==) Matched fbdev as autoconfigured driver 1
[ 1641.017] (II) LoadModule: "fbdev"
[ 1641.017] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 1641.017] (II) Module fbdev: vendor="X.Org Foundation"
[ 1641.034] (II) FBDEV: driver for framebuffer: fbdev
[ 1641.036] (WW) Falling back to old probe method for fbdev
[ 1641.036] (II) Loading sub module "fbdevhw"
[ 1641.036] (II) LoadModule: "fbdevhw"
[ 1641.037] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 1641.057] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 1641.364] (II) Loading sub module "fb"
[ 1641.364] (II) LoadModule: "fb"
[ 1641.364] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 1641.383] (II) Module fb: vendor="X.Org Foundation"
[ 1643.186] (II) Loading sub module "fb"
[ 1643.186] (II) LoadModule: "fb"
[ 1643.186] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 1643.186] (II) Module fb: vendor="X.Org Foundation"
[ 1643.186] (II) UnloadModule: "fbdev"
[ 1643.186] (II) Unloading fbdev
[ 1643.186] (II) UnloadSubModule: "fbdevhw"
[ 1643.186] (II) Unloading fbdevhw

[aksala]

ok I modified my xorg.conf
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 35-81
VertRefresh 59-76
#UseModes "Modes0" #monitor0usemodes
# Option "PreferredMode" "1024x768" #monitor0prefmode
EndSection

Section "Modes"
Identifier "Modes0"
#modes0modeline0
EndSection

Section "Device"
Identifier "DisplaylinkDevice"
driver "displaylink"
Option "fbdev" "/dev/fb0"
Endsection

Section "Device"
Identifier "Card0"
Driver "intel" #card0driver
BusID "0:2:0" #card0busid
EndSection

Section "Screen"
Identifier "Screen0"
# Device "DisplaylinkDevice"
Monitor "Monitor0"
# DefaultDepth 16
EndSection

then in xorgwizard I specified driver intel

Code: Select all

xorg log


[  8966.141] (II) xfree86: Adding drm device (/dev/dri/card0)
[  8966.141] (II) xfree86: Adding drm device (/dev/dri/card1)
[  8966.147] (--) PCI:*(0@0:2:0) 8086:2e32:8086:2e32 rev 3, Mem @ 0xfe000000/4194304, 0xd0000000/268435456, I/O @ 0x00006800/8, BIOS @ 0x????????/131072
[  8966.147] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[  8966.147] (II) LoadModule: "glx"
[  8966.147] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  8966.148] (II) Module glx: vendor="X.Org Foundation"
[  8966.148]    compiled for 1.20.8, module version = 1.0.0
[  8966.148]    ABI class: X.Org Server Extension, version 10.0
[  8966.148] (II) LoadModule: "displaylink"
[  8966.149] (WW) Warning, couldn't open module displaylink
[  8966.149] (EE) Failed to load module "displaylink" (module does not exist, 0)
[  8966.149] (II) LoadModule: "intel"
[  8966.149] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[  8966.150] (II) Module intel: vendor="X.Org Foundation"
[  8966.150]    compiled for 1.20.8, module version = 2.99.917
[  8966.150]    Module class: X.Org Video Driver
[  8966.150]    ABI class: X.Org Video Driver, version 24.1
[  8966.150] (==) Matched modesetting as autoconfigured driver 0
[  8966.150] (==) Matched fbdev as autoconfigured driver 1
[  8966.150] (==) Matched vesa as autoconfigured driver 2
[  8966.150] (==) Assigned the driver to the xf86ConfigLayout
[  8966.150] (II) LoadModule: "modesetting"
[  8966.150] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[  8966.150] (II) Module modesetting: vendor="X.Org Foundation"
[  8966.150]    compiled for 1.20.8, module version = 1.20.8
[  8966.150]    Module class: X.Org Video Driver
[  8966.150]    ABI class: X.Org Video Driver, version 24.1
[  8966.150] (II) LoadModule: "intel"
[  8966.150] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[  8966.150] (II) Module intel: vendor="X.Org Foundation"
[  8966.150]    compiled for 1.20.8, module version = 2.99.917
[  8966.150]    Module class: X.Org Video Driver
[  8966.150]    ABI class: X.Org Video Driver, version 24.1
[  8966.150] (II) UnloadModule: "intel"
[  8966.150] (II) Unloading intel
[  8966.150] (II) Failed to load module "intel" (already loaded, 0)
[  8966.150] (II) LoadModule: "fbdev"
[  8966.151] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[  8966.151] (II) Module fbdev: vendor="X.Org Foundation"
[  8966.151]    compiled for 1.20.1, module version = 0.5.0
[  8966.151]    Module class: X.Org Video Driver
[  8966.151]    ABI class: X.Org Video Driver, version 24.0
[  8966.151] (II) LoadModule: "vesa"
[  8966.151] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[  8966.151] (II) Module vesa: vendor="X.Org Foundation"
[  8966.151]    compiled for 1.20.4, module version = 2.4.0
[  8966.151]    Module class: X.Org Video Driver
[  8966.151]    ABI class: X.Org Video Driver, version 24.0
[  8966.151] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
        i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
        915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
        Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
        GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[  8966.151] (II) intel: Driver for Intel(R) HD Graphics
[  8966.151] (II) intel: Driver for Intel(R) Iris(TM) Graphics
[  8966.151] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics
[  8966.151] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[  8966.151] (II) FBDEV: driver for framebuffer: fbdev
[  8966.151] (II) VESA: driver for VESA chipsets: vesa
[  8966.153] (II) intel(G0): Using Kernel Mode Setting driver: i915, version 1.6.0 20190822
[  8966.153] (II) intel(G0): SNA compiled: xserver-xorg-video-intel 2:2.99.917+git20200226-1 (Timo Aaltonen <timo.aaltonen@canonical.com>)
[  8966.153] (II) intel(G0): SNA compiled for use with valgrind
[  8966.165] (WW) Falling back to old probe method for modesetting
[  8966.165] (WW) Falling back to old probe method for fbdev
[  8966.165] (II) Loading sub module "fbdevhw"
[  8966.165] (II) LoadModule: "fbdevhw"
[  8966.165] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[  8966.165] (II) Module fbdevhw: vendor="X.Org Foundation"
[  8966.165]    compiled for 1.20.8, module version = 0.0.2
[  8966.165]    ABI class: X.Org Video Driver, version 24.1
[  8966.166] (WW) Falling back to old probe method for modesetting
[  8966.166] (WW) Falling back to old probe method for fbdev
[  8966.166] (II) Loading sub module "fbdevhw"
[  8966.166] (II) LoadModule: "fbdevhw"
[  8966.166] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[  8966.166] (II) Module fbdevhw: vendor="X.Org Foundation"
[  8966.166]    compiled for 1.20.8, module version = 0.0.2
[  8966.166]    ABI class: X.Org Video Driver, version 24.1
[  8966.166] (II) modeset(G1): using drv /dev/dri/card1
[  8966.166] (EE) No devices detected.
[  8966.166] (EE)
Fatal server error:
[  8966.166] (EE) no screens found(EE)
[  8966.166] (EE)
Please consult the The X.Org Foundation support

.
.
hmmm do I need displaylink driver? how am I viewing the command line through the displaylink if there is no driver though?

[aksala]

Im back at it

this must be how its able to output during bootup - why are the all xxx.py??

Code: Select all

/usr/share/apport/package-hooks/source_xf86-video-displaylink.py
/usr/share/apport/package-hooks/source_xserver-xorg-video-displaylink.py
/initrd/pup_a/usr/share/apport/package-hooks/source_xf86-video-displaylink.py
/initrd/pup_a/usr/share/apport/package-hooks/source_xserver-xorg-video-displaylink.py
/initrd/pup_ro2/usr/share/apport/package-hooks/source_xf86-video-displaylink.py
/initrd/pup_ro2/usr/share/apport/package-hooks/source_xserver-xorg-video-displaylink.py

but then I get this... how do I get it to load the displaylink module? doesnt seem to have a driver in the right place

xorglog

Code: Select all

[ 80884.290] (--) PCI:*(0@0:2:0) 8086:2e32:8086:2e32 rev 3, Mem @ 0xfe000000/4194304, 0xd0000000/268435456, I/O @ 0x00006800/8, BIOS @ 0x????????/131072

[ 80884.292] (II) LoadModule: "displaylink"
[ 80884.293] (WW) Warning, couldn't open module displaylink
[ 80884.293] (EE) Failed to load module "displaylink" (module does not exist, 0)

# ls /usr/lib/xorg/modules/drivers

Code: Select all

amdgpu_drv.so  fbdev_drv.so        nouveau_drv.so     radeon_drv.so
ati_drv.so     intel_drv.so        openchrome_drv.so  vesa_drv.so
dummy_drv.so   modesetting_drv.so  qxl_drv.so         vmware_drv.so

[aksala]

back at it. I guess im on my own twisting in the wind here.

ok so it appears the console is using udl
https://manpages.ubuntu.com/manpages/fo ... eebsd.html

# lsmod | grep udl
udl 24576 1
drm_kms_helper 139264 2 udl,i915
drm 368640 4 udl,drm_kms_helper,i915

/sys/bus/usb/drivers/udl
/sys/module/udl
/sys/module/drm_kms_helper/holders/udl
/sys/module/drm/holders/udl
/lib/modules/5.4.53/kernel/drivers/gpu/drm/udl
/initrd/pup_z/lib/modules/5.4.53/kernel/drivers/gpu/drm/udl

udl is a .ko file extension but all the xorg drivers are .so

going to try modifying xorg.conf to use the path to the udl driver but im dont think it will like the path and I dont think I can just flop the driver from its current location into the xorg directory

# ls /usr/lib/xorg/modules/
drivers input libfbdevhw.so libglamoregl.so libshadowfb.so libvbe.so libwfb.so
extensions libexa.so libfb.so libint10.so libshadow.so libvgahw.so

[rockedge]

udl is a .ko file extension but all the xorg drivers are .so

In a really basic explanation, Kernel modules (ko) run in kernel space, user modules (so) run in user space.

[aksala]

Got it working (pic attached) with arch using wayland so it is theoretically possible to make this work w puppy.

I learned a lot I had to boot off the compact flash but the CF has the installer image. So had to plug in another compact flash on usb, partition it for bios, then partition a 16g usb stick as root. Then installed and made a fstab by running genfstab twice, once for /mnt/usb and one for /mnt/boot then installed grub. Totally forgot to make a swap part so it runs like butt and I think that is why - but it displays at least.

Going to poke around in here and see how its working and see if I can translate it to xorg/puppy.

Also I have my Barracuda that boots puppy nicely im going to plug the displaylink usb into it and see if it recognizes the displaylink over there. If so I will take a peek qt how thats working and copy those settings over to the watchguard.

[aksala]

Alright got puppy going on the barracuda (not the watchguard which is the subject of this thread) , and got the dual display going. Excited with the development, I rushed to xorg.conf so I could cut and paste the "device" stanza over to the WG... and there was none. Only some entries for the vga.

So im back to scratching my head. I guess I need to google around for xrandr commands and figure out how the dual is working.

Wont have an update for a few days - have to do actual work. Any ideas appreciated

[rockedge]

Interesting for sure! I don't have the equipment to run any of these experiments on but I feel like you're getting close to a successful boot on the WatchGuard XTM-5

[aksala]

Got it. I eventually realized it was launching xwin sucessfully I just couldnt see it. I learned the menu tree blind (right click down down down down right up enter) to get to a console. Theres probably a better way but I could be sure this way. Blindly I typed in xrandr > /tmp/xrandr.txt then exit to prompt and less it at command line. Saw that it was learning the outputs. I tried all manner of xrandr --output VGA1 --noprimary blah blah. DVI-I-1-1 --primary i just finally said F it xrandr --auto and it came alive. Its really laggy with mouse clicks but the pointer moves nicely so I might try messing with some settings but this is great. lol. I think whats wrong is its setting VGA1 as primary but in my case theres no VGA. For instance its still VGA as "disconnected primary" and thr displaylink is cloning the VGA... thankfully the developers were nice enough as to allow the displaylink to piggyback off the primary even when it is off/down which makes sense.

Anyways. Cool stuff now I can mess with LCDproc. Any suggestions on speeding up the click events would be nice

[bigpup]

About laggy mouse clicks.

Menu ->Setup ->Mouse/keyboard Wizard ->Mouse properties may have a setting change that would help.

[aksala]

Thanks I tried that and didnt help much. It looks like Im running into a bug many users have reported where they close their laptop lid and xorg defaults to 1fps on the displaylink so im trying to run that down. Since I dont have a lid to open im kinda stuck since the patch is for ubuntu. So idk if I can make it work on here... might be over my skill level. I turned off picom compositor and it helped a lot.. like 20 fps now. Ok question.... how can I save all these settings and my lcdproc download and dropbear and all that?

In the meantime haha

[aksala]

ok Im stuck I think I need to start a new thread. which section would the following be appropriate?

DisplayLink displays runs at 1FPS when laptop lid is closed.
https://gitlab.freedesktop.org/xorg/xse ... ssues/1028

># Download the debian file from https://www.displaylink.com/downloads/file?d=310
>sudo dpkg -i xserver-xorg-core_1.20.8-2ubuntu2_amd64.deb

[rockedge]

Ok question.... how can I save all these settings and my lcdproc download and dropbear and all that?

Normally now a shutdown or reboot the wizard with the options to create the save folder or file and where would appear. This would store persistence of the session.

[bigpup]

I would keep all issues reported here in this topic.

Your issues are mostly about the specific hardware and how Puppy is running on it.