Forum › Forums › General › Tips and Tricks › Antix installation on usb flash drive
- This topic has 15 replies, 7 voices, and was last updated Apr 12-8:02 pm by ioann.
-
AuthorPosts
-
February 16, 2022 at 4:28 pm #77544Member
ioann
First of all, I would like to thank the antix developer team and community for their great work. I’ve been using antix for the past three years and I am amazed by its speed and efficiency.
This post is about installing antix on a usb flash drive. I mean full installation on a dedicated ext4 partition and installation of the grub boot loader on the same usb stick. I use either EFI or BIOS/MBR setup according to hardware specs. I have four laptops set up like this. These systems boot fine but sometimes they have issues launching the desktop. I use JWM with zzz file manger to handle desktop icons. I have noted these issues in antix 19 and 22.
I have experienced the following after I have typed username and password:
-conky and desktop icons are not loaded, jwm taskbar is loaded but I cannot start applications from jwm taskbar.
-conky and icons are loaded but applications do not start either from desktop icons or jwm menu.
-sometimes everything is loaded and applications start but not those requiring super user authentication like synaptic.
-sometimes everything works fine.This inconsistent behavior troubled me a lot for quite some time but in the end I noticed that is related to the time I give the system to boot. If I wait 10-15 seconds before I type username and password, desktop launches perfectly. I tried to increase startup delay (STARTUP_DELAY=”xx”) in ~/.desktop-session/desktop-session.conf but this did not help.
Then I added some deleay using the sleep command in the beginning of slimski init script: /etc/init.d/slimski#!/usr/bin/sh
# Largely adapted from xdm’s init script:
# Copyright 1998-2002, 2004, 2005 Branden Robinson <branden@debian.org>.
# Copyright 2006 Eugene Konev <ejka@imfi.kspu.ru>### BEGIN INIT INFO
# Provides: slimski
# Required-Start: $local_fs $remote_fs
# Required-Stop: $local_fs $remote_fs
# Should-Start: xfs $named slapd
# Should-Stop: xfs $named slapd
# Default-Start: 2 5
# Default-Stop: 0 1 6
# Short-Description: Start daemon at boot time
# Description: Debian init script for slimski
### END INIT INFO
sleep 12test -z “$HEED_DEFAULT_DISPLAY_MANAGER” && HEED_DEFAULT_DISPLAY_MANAGER=true
DEFAULT_DISPLAY_MANAGER_FILE=/etc/X11/default-display-manager
…This delay solved the problem. It needs a little more time to boot but it boots fine. Usb flash drives seem to need a little more time to load everything before desktop is launched. I undesrstand that my solution is not perfect as my linux skills are limited. Someone with greater knowledge can suggest a more sophisticated solution. Also I understand that not many people may install antix on usb sticks but it may be useful for some. Thanks for reading and excuse my long post.
February 16, 2022 at 6:55 pm #77556Moderator
Brian Masinick
::@ioann: Thank you for sharing your observations and your solution to an issue that some people will encounter.
I have no idea where the issue originates from, but it’s quite likely that hardware detection and process initiation take time, and the software we are using is general purpose, and therefore we provide a common solution and a startup procedure that may be optimal for certain configurations and “functional”, but not necessarily optimal for others.
Being someone who has used a wide variety of hardware and software, both “old” and “new”, I readily see some things work perfectly and others only partially.
I added a few “cast off” pieces of hardware to my collection recently, and I can still get MX Linux and antiX to work on them, but on one particular piece of hardware, things work for anywhere from 10-15 minutes to perhaps an hour at most, then either the response gets erratic, or in some situations the system freezes up completely. This never happens on newer systems (anything 5-6 years or younger), and both distributions have had a GREAT track record with various Linux distributions. Therefore I attribute those issues to extremely marginal hardware that is either defective or nearly ready for a true “end of life”. In the past when I’ve had systems like that and I’ve dealt with them on a daily basis, I’ve been able to either guess or figure out which components need attention. I’ve replaced fans, network cards and disk drives with success. Sometimes I’ve had extra systems to use for parts; other times I’ve gone to an electronics store or purchased replacement parts from reputable online sources with success. But with some of the latest systems I’m not inclined to repair them; they were headed “for the dump” before I “rescued them”, so once I’m not, they will go either to a hobbyist or directly to an electronics tear down recycling center.--
Brian MasinickFebruary 16, 2022 at 6:56 pm #77557Forum Admin
rokytnji
::Was this on usb 1.1 or usb 2.0 ports. Got a
$ inxi -Fxz-rYou can post as well as a
lsub -vWith your drive plugged in.
Thanks for the thread.
- This reply was modified 1 year, 2 months ago by rokytnji.
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsFebruary 16, 2022 at 8:50 pm #77560Memberioann
::Thank you for your replies. These observations were common in four systems in total. Below I provide information about the system I am currently using, as requested. It is a relative new system. Antix runs from Transcend Jetflash usb 3 stick connected to a usb 2.0 port for better thermal behavior. The other three machines is a lenovo thinkpad E460, an asus e210ma modern n4020 celeron netbook and an old asus eee pc single core atom netbook. Oddly the old atom loads the desktop smoothly most of the times.
I attribute those issues to flash drive installation of the operating system. A flash drive is legendary slow accessing and/or writing many small files at once. I believe that a little more time is needed for every service to load and be ready before launch of graphical environment. This may also be associated with the custom nature of antix desktop construction. At least, after six months of frustration I can happily use my antix systems.$ inxi -Fxz-r System: Kernel: 5.10.88-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: JWM 2.4.0 Distro: antiX-21_x64-full Grup Yorum 31 October 2021 base: Debian GNU/Linux 11 (bullseye) Machine: Type: Laptop System: LENOVO product: 20AVA0CLGM v: ThinkPad L540 serial: <filter> Mobo: LENOVO model: 20AVA0CLGM serial: <filter> UEFI-[Legacy]: LENOVO v: J4ET93WW(1.93) date: 05/30/2018 Battery: ID-1: BAT0 charge: 24.9 Wh (76.6%) condition: 32.5/47.5 Wh (68.3%) volts: 12.0 min: 10.8 model: LGC 45N1161 status: Charging CPU: Info: Dual Core model: Intel Core i5-4210M bits: 64 type: MT MCP arch: Haswell rev: 3 cache: L2: 3 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 20752 Speed: 2594 MHz min/max: 800/3200 MHz Core speeds (MHz): 1: 2594 2: 2595 3: 2595 4: 2598 Graphics: Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: Lenovo driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Acer Integrated Camera type: USB driver: uvcvideo bus-ID: 1-1.6:4 Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 20.3.5 direct render: Yes Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:03.0 Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 Sound Server-1: ALSA v: k5.10.88-antix.1-amd64-smp running: yes Network: Device-1: Intel Wireless 7260 driver: iwlwifi v: kernel port: efa0 bus-ID: 02:00.0 IF: wlan0 state: up mac: <filter> Drives: Local Storage: total: 325.69 GiB used: 45.67 GiB (14.0%) ID-1: /dev/sda vendor: Intenso model: SSD SATAIII size: 238.47 GiB ID-2: /dev/sdb type: USB vendor: SanDisk model: Cruzer Fit size: 58.73 GiB ID-3: /dev/sdc type: USB vendor: Transcend model: JetFlash Transcend 32GB size: 28.48 GiB Partition: ID-1: / size: 23.86 GiB used: 7.65 GiB (32.1%) fs: ext4 dev: /dev/sdc1 Swap: ID-1: swap-1 type: partition size: 4.06 GiB used: 0 KiB (0.0%) dev: /dev/sdc2 Sensors: System Temperatures: cpu: 46.0 C mobo: 40.0 C Fan Speeds (RPM): cpu: 0 Repos: Packages: 1728 Active apt repos in: /etc/apt/sources.list.d/antix.list 1: deb http://mirror.telepoint.bg/mxlinux-repo/antix/bullseye/ bullseye main nosystemd nonfree Active apt repos in: /etc/apt/sources.list.d/bullseye-backports.list 1: deb http://deb.debian.org/debian bullseye-backports main contrib non-free Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 1: deb http://debian.otenet.gr/debian/ bullseye-updates main contrib non-free Active apt repos in: /etc/apt/sources.list.d/debian.list 1: deb http://debian.otenet.gr/debian/ bullseye main contrib non-free 2: deb http://security.debian.org/ bullseye-security main contrib non-free No active apt repos in: /etc/apt/sources.list.d/various.list Info: Processes: 159 Uptime: 8m Memory: 7.5 GiB used: 834.9 MiB (10.9%) Init: SysVinit runlevel: 5 Compilers: gcc: 10.2.1 Shell: Bash v: 5.1.4 inxi: 3.3.06 Bus 002 Device 003: ID 0781:5571 SanDisk Corp. Cruzer Fit Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x0781 SanDisk Corp. idProduct 0x5571 Cruzer Fit bcdDevice 1.00 iManufacturer 1 SanDisk' iProduct 2 Cruzer Fit iSerial 3 02006208121620140259 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0020 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 200mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Bus 002 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 1 Single TT bMaxPacketSize0 64 idVendor 0x8087 Intel Corp. idProduct 0x8000 Integrated Rate Matching Hub bcdDevice 0.05 iManufacturer 0 iProduct 0 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0019 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 12 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x1d6b Linux Foundation idProduct 0x0002 2.0 root hub bcdDevice 5.10 iManufacturer 3 Linux 5.10.88-antix.1-amd64-smp ehci_hcd iProduct 2 EHCI Host Controller iSerial 1 0000:00:1d.0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0019 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 Bus 001 Device 004: ID 5986:0397 Acer, Inc Integrated Camera Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 bDeviceProtocol 1 Interface Association bMaxPacketSize0 64 idVendor 0x5986 Acer, Inc idProduct 0x0397 bcdDevice 14.78 iManufacturer 1 Vimicro corp. iProduct 2 Integrated Camera iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0369 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 256mA Interface Association: bLength 8 bDescriptorType 11 bFirstInterface 0 bInterfaceCount 2 bFunctionClass 14 Video bFunctionSubClass 3 Video Interface Collection bFunctionProtocol 0 iFunction 2 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 14 Video bInterfaceSubClass 1 Video Control bInterfaceProtocol 0 iInterface 2 VideoControl Interface Descriptor: bLength 13 bDescriptorType 36 bDescriptorSubtype 1 (HEADER) bcdUVC 1.00 wTotalLength 0x004f dwClockFrequency 30.000000MHz bInCollection 1 baInterfaceNr( 0) 1 VideoControl Interface Descriptor: bLength 18 bDescriptorType 36 bDescriptorSubtype 2 (INPUT_TERMINAL) bTerminalID 1 wTerminalType 0x0201 Camera Sensor bAssocTerminal 0 iTerminal 0 wObjectiveFocalLengthMin 0 wObjectiveFocalLengthMax 0 wOcularFocalLength 0 bControlSize 3 bmControls 0x0000020e Auto-Exposure Mode Auto-Exposure Priority Exposure Time (Absolute) Zoom (Absolute) VideoControl Interface Descriptor: bLength 11 bDescriptorType 36 bDescriptorSubtype 5 (PROCESSING_UNIT) Warning: Descriptor too short bUnitID 2 bSourceID 1 wMaxMultiplier 0 bControlSize 2 bmControls 0x0000073f Brightness Contrast Hue Saturation Sharpness Gamma Backlight Compensation Gain Power Line Frequency iProcessing 0 bmVideoStandards 0x09 None SECAM - 625/50 VideoControl Interface Descriptor: bLength 9 bDescriptorType 36 bDescriptorSubtype 3 (OUTPUT_TERMINAL) bTerminalID 3 wTerminalType 0x0101 USB Streaming bAssocTerminal 0 bSourceID 2 iTerminal 0 VideoControl Interface Descriptor: bLength 28 bDescriptorType 36 bDescriptorSubtype 6 (EXTENSION_UNIT) bUnitID 4 guidExtensionCode {a917c75d-4119-11da-ae0e-000d56ac7b4c} bNumControls 9 bNrInPins 1 baSourceID( 0) 1 bControlSize 3 bmControls( 0) 0x5b bmControls( 1) 0x80 bmControls( 2) 0x82 iExtension 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 5 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 14 Video bInterfaceSubClass 2 Video Streaming bInterfaceProtocol 0 iInterface 0 VideoStreaming Interface Descriptor: bLength 15 bDescriptorType 36 bDescriptorSubtype 1 (INPUT_HEADER) bNumFormats 2 wTotalLength 0x027b bEndPointAddress 130 bmInfo 0 bTerminalLink 3 bStillCaptureMethod 2 bTriggerSupport 1 bTriggerUsage 1 bControlSize 1 bmaControls( 0) 0 bmaControls( 1) 0 VideoStreaming Interface Descriptor: bLength 27 bDescriptorType 36 bDescriptorSubtype 4 (FORMAT_UNCOMPRESSED) bFormatIndex 1 bNumFrameDescriptors 8 guidFormat {32595559-0000-0010-8000-00aa00389b71} bBitsPerPixel 16 bDefaultFrameIndex 1 bAspectRatioX 0 bAspectRatioY 0 bmInterlaceFlags 0x00 Interlaced stream or variable: No Fields per frame: 2 fields Field 1 first: No Field pattern: Field 1 only bCopyProtect 0 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) bFrameIndex 1 bmCapabilities 0x00 Still image unsupported wWidth 640 wHeight 480 dwMinBitRate 73728000 dwMaxBitRate 147456000 dwMaxVideoFrameBufferSize 614400 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666667 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) bFrameIndex 2 bmCapabilities 0x00 Still image unsupported wWidth 352 wHeight 288 dwMinBitRate 24330240 dwMaxBitRate 48660480 dwMaxVideoFrameBufferSize 202752 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666667 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) bFrameIndex 3 bmCapabilities 0x00 Still image unsupported wWidth 320 wHeight 240 dwMinBitRate 18432000 dwMaxBitRate 36864000 dwMaxVideoFrameBufferSize 153600 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666667 VideoStreaming Interface Descriptor: bLength 30 bDescriptorType 36 bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) bFrameIndex 4 bmCapabilities 0x00 Still image unsupported wWidth 800 wHeight 448 dwMinBitRate 86016000 dwMaxBitRate 86016000 dwMaxVideoFrameBufferSize 716800 dwDefaultFrameInterval 666667 bFrameIntervalType 1 dwFrameInterval( 0) 666667 VideoStreaming Interface Descriptor: bLength 30 bDescriptorType 36 bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) bFrameIndex 5 bmCapabilities 0x00 Still image unsupported wWidth 960 wHeight 544 dwMinBitRate 83558400 dwMaxBitRate 83558400 dwMaxVideoFrameBufferSize 1044480 dwDefaultFrameInterval 1000000 bFrameIntervalType 1 dwFrameInterval( 0) 1000000 VideoStreaming Interface Descriptor: bLength 30 bDescriptorType 36 bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) bFrameIndex 6 bmCapabilities 0x00 Still image unsupported wWidth 1280 wHeight 720 dwMinBitRate 147456000 dwMaxBitRate 147456000 dwMaxVideoFrameBufferSize 1843200 dwDefaultFrameInterval 1000000 bFrameIntervalType 1 dwFrameInterval( 0) 1000000 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) bFrameIndex 7 bmCapabilities 0x00 Still image unsupported wWidth 640 wHeight 360 dwMinBitRate 55296000 dwMaxBitRate 110592000 dwMaxVideoFrameBufferSize 460800 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666667 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) bFrameIndex 8 bmCapabilities 0x00 Still image unsupported wWidth 424 wHeight 240 dwMinBitRate 24422400 dwMaxBitRate 48844800 dwMaxVideoFrameBufferSize 203520 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666667 VideoStreaming Interface Descriptor: bLength 38 bDescriptorType 36 bDescriptorSubtype 3 (STILL_IMAGE_FRAME) bEndpointAddress 0 bNumImageSizePatterns 8 wWidth( 0) 640 wHeight( 0) 480 wWidth( 1) 352 wHeight( 1) 288 wWidth( 2) 320 wHeight( 2) 240 wWidth( 3) 800 wHeight( 3) 448 wWidth( 4) 960 wHeight( 4) 544 wWidth( 5) 1280 wHeight( 5) 720 wWidth( 6) 640 wHeight( 6) 360 wWidth( 7) 424 wHeight( 7) 240 bNumCompressionPatterns 0 VideoStreaming Interface Descriptor: bLength 6 bDescriptorType 36 bDescriptorSubtype 13 (COLORFORMAT) bColorPrimaries 1 (BT.709,sRGB) bTransferCharacteristics 1 (BT.709) bMatrixCoefficients 4 (SMPTE 170M (BT.601)) VideoStreaming Interface Descriptor: bLength 11 bDescriptorType 36 bDescriptorSubtype 6 (FORMAT_MJPEG) bFormatIndex 2 bNumFrameDescriptors 7 bFlags 1 Fixed-size samples: Yes bDefaultFrameIndex 1 bAspectRatioX 0 bAspectRatioY 0 bmInterlaceFlags 0x00 Interlaced stream or variable: No Fields per frame: 1 fields Field 1 first: No Field pattern: Field 1 only bCopyProtect 0 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 7 (FRAME_MJPEG) bFrameIndex 1 bmCapabilities 0x00 Still image unsupported wWidth 640 wHeight 480 dwMinBitRate 73728000 dwMaxBitRate 147456000 dwMaxVideoFrameBufferSize 614400 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666667 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 7 (FRAME_MJPEG) bFrameIndex 2 bmCapabilities 0x00 Still image unsupported wWidth 352 wHeight 288 dwMinBitRate 24330240 dwMaxBitRate 48660480 dwMaxVideoFrameBufferSize 202752 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666667 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 7 (FRAME_MJPEG) bFrameIndex 3 bmCapabilities 0x00 Still image unsupported wWidth 320 wHeight 240 dwMinBitRate 18432000 dwMaxBitRate 36864000 dwMaxVideoFrameBufferSize 153600 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666667 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 7 (FRAME_MJPEG) bFrameIndex 4 bmCapabilities 0x00 Still image unsupported wWidth 800 wHeight 448 dwMinBitRate 86016000 dwMaxBitRate 172032000 dwMaxVideoFrameBufferSize 716800 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666667 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 7 (FRAME_MJPEG) bFrameIndex 5 bmCapabilities 0x00 Still image unsupported wWidth 960 wHeight 544 dwMinBitRate 125337600 dwMaxBitRate 250675200 dwMaxVideoFrameBufferSize 1044480 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666667 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 7 (FRAME_MJPEG) bFrameIndex 6 bmCapabilities 0x00 Still image unsupported wWidth 1280 wHeight 720 dwMinBitRate 221184000 dwMaxBitRate 442368000 dwMaxVideoFrameBufferSize 1843200 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666667 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 7 (FRAME_MJPEG) bFrameIndex 7 bmCapabilities 0x00 Still image unsupported wWidth 640 wHeight 360 dwMinBitRate 55296000 dwMaxBitRate 110592000 dwMaxVideoFrameBufferSize 460800 dwDefaultFrameInterval 333333 bFrameIntervalType 2 dwFrameInterval( 0) 333333 dwFrameInterval( 1) 666667 VideoStreaming Interface Descriptor: bLength 34 bDescriptorType 36 bDescriptorSubtype 3 (STILL_IMAGE_FRAME) bEndpointAddress 0 bNumImageSizePatterns 7 wWidth( 0) 640 wHeight( 0) 480 wWidth( 1) 352 wHeight( 1) 288 wWidth( 2) 320 wHeight( 2) 240 wWidth( 3) 800 wHeight( 3) 448 wWidth( 4) 960 wHeight( 4) 544 wWidth( 5) 1280 wHeight( 5) 720 wWidth( 6) 640 wHeight( 6) 360 bNumCompressionPatterns 0 VideoStreaming Interface Descriptor: bLength 6 bDescriptorType 36 bDescriptorSubtype 13 (COLORFORMAT) bColorPrimaries 1 (BT.709,sRGB) bTransferCharacteristics 1 (BT.709) bMatrixCoefficients 4 (SMPTE 170M (BT.601)) Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 1 bNumEndpoints 1 bInterfaceClass 14 Video bInterfaceSubClass 2 Video Streaming bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 5 Transfer Type Isochronous Synch Type Asynchronous Usage Type Data wMaxPacketSize 0x0080 1x 128 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 2 bNumEndpoints 1 bInterfaceClass 14 Video bInterfaceSubClass 2 Video Streaming bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 5 Transfer Type Isochronous Synch Type Asynchronous Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 3 bNumEndpoints 1 bInterfaceClass 14 Video bInterfaceSubClass 2 Video Streaming bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 5 Transfer Type Isochronous Synch Type Asynchronous Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 4 bNumEndpoints 1 bInterfaceClass 14 Video bInterfaceSubClass 2 Video Streaming bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 5 Transfer Type Isochronous Synch Type Asynchronous Usage Type Data wMaxPacketSize 0x0b00 2x 768 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 5 bNumEndpoints 1 bInterfaceClass 14 Video bInterfaceSubClass 2 Video Streaming bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 5 Transfer Type Isochronous Synch Type Asynchronous Usage Type Data wMaxPacketSize 0x0c00 2x 1024 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 6 bNumEndpoints 1 bInterfaceClass 14 Video bInterfaceSubClass 2 Video Streaming bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 5 Transfer Type Isochronous Synch Type Asynchronous Usage Type Data wMaxPacketSize 0x1380 3x 896 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 7 bNumEndpoints 1 bInterfaceClass 14 Video bInterfaceSubClass 2 Video Streaming bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 5 Transfer Type Isochronous Synch Type Asynchronous Usage Type Data wMaxPacketSize 0x1400 3x 1024 bytes bInterval 1 Bus 001 Device 003: ID 8564:1000 Transcend Information, Inc. JetFlash Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.10 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x8564 Transcend Information, Inc. idProduct 0x1000 JetFlash bcdDevice 11.00 iManufacturer 1 JetFlash iProduct 2 Mass Storage Device iSerial 3 75364O7XJ423X0PQ bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0020 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 300mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Bus 001 Device 002: ID 8087:8008 Intel Corp. Integrated Rate Matching Hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 1 Single TT bMaxPacketSize0 64 idVendor 0x8087 Intel Corp. idProduct 0x8008 Integrated Rate Matching Hub bcdDevice 0.05 iManufacturer 0 iProduct 0 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0019 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0001 1x 1 bytes bInterval 12 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x1d6b Linux Foundation idProduct 0x0002 2.0 root hub bcdDevice 5.10 iManufacturer 3 Linux 5.10.88-antix.1-amd64-smp ehci_hcd iProduct 2 EHCI Host Controller iSerial 1 0000:00:1a.0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0019 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12February 16, 2022 at 8:59 pm #77561Forum Admin
rokytnji
::Thanks and Kudos for fitting all that in here.
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsFebruary 17, 2022 at 12:15 am #77575Memberolsztyn
::Also I understand that not many people may install antix on usb sticks but it may be useful for some.
I would like to understand how traditional install on USB stick can be useful for anyone with all the downsides of Write I/O operations, while Live USB install is so much superior – works very well and has no such downside – Write operations to flash media are practically zero.
Thanks and Regards…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersMarch 19, 2022 at 8:00 am #79369MemberPDP-8
::I’m all about running from usb-sticks – this kind of reminds me of some random things when running Porteus with errors from respawning too fast, and not shutting down properly either. Random and adding sleep commands fixed that too.
More details here (Porteus, not antix, but possibly useful for illustration)
https://forum.porteus.org/viewtopic.php?p=83744
Essentially I had to add a sleep 5 to my etc/rc.d/rc.4, and then remove slim’s lockfile in the rc.local_shutdown.
So really just a case of fine-tuning timing paramaters which can hit any distro. Sure can be frustrating to find, but once found is soooo satisfying. 🙂
March 19, 2022 at 9:17 am #79371MemberModdIt
::Below may or may not be of help in the particular issue.
Some/reports are many, jet flash USB sticks have controller issues, defective software, or software which does not
work correctly under certain conditions. To date I have been affected twice.I have two 64 GB JetFlash sticks bought several weeks apart claimed as fast USB3, before using the online repair tool
one became unusable. The second one was extremely slow in every way.
Data delivery on longer reads and worse writes at USB1 Niveau or in the end at times not at all. Reformatting made no
difference.There are many user complaints, see amazon among other places which have lead up to the online repair tool being made
available to end users. It was a support tool and (according to a support engineer) rewrites controller software to
factory standard.
The repair process is clunky and only available from windoze. I had to try severa times before my sticks were pronounced
fixed. Reward, up to now way faster than before repair and both sticks just working as they should. Or as I expect from
Transcend which is a reputable company.Repair tool under below link.
https://www.transcend-info.com/Support/Software-3/March 19, 2022 at 9:26 am #79372MemberModdIt
::olstyn wrote in post 77575
I would like to understand how traditional install on USB stick can be useful for anyone with all the downsides of Write
I/O operations, while Live USB install is so much superior – works very well and has no such downside – Write operations to flash media are practically zero.
Thanks and Regards…Me too,
I see only disadvantages with a normal installation to a USB stick. Have run as a daily driver for months on end without any installation
and without any issues. Just having my saves going to a second stick as well as live USB storage. Lesson learned due one defective stick and my
lack of care. Boot from USB2 on nearly as fast as from an internal ssd, application start same goes.System Updates are no problem whatsoever, just remaster.
March 19, 2022 at 2:18 pm #79381Moderator
Brian Masinick
::Yeah, I’ll weigh in here too: Sometimes I run in “Frugal” mode, running antiX live, but if I want any kind of PERMANENT disk installation, in that case I run the Live USB Maker to physically install antiX to the hard drive; these days most of my systems use SSD, Solid State Drive technology rather than rotating HDD Hard Disk Drive technology, and for permanent storage, that is faster and more stable than continually writing to a removable USB; on the other hand, running Live in Frugal mode, you can save the “state” of your environment, writing only a few essential details, and that conserves the number of write operations to the USB device.
--
Brian MasinickMarch 19, 2022 at 8:37 pm #79391MemberPDP-8
::I’ve been bitten by counterfeits too. Even though I look out for “too good to be true” deals, I’ve gotten nailed before.
I take AntiX and the live usb running in ram to the other extreme: I delight in running from quality micro sd-cards or eMMC found in small “mini” 64-bit pc’s, most of which have micro-sd slots as well as usb – and of course most have eMMC and not real ssd’s. So I limit the writes and run from ram when I can.
Although when I install antix to a micro-sd card, that’s usually done with a usb<>micro sd adapter at first – unless I dd directly to one.
Much of my early training was from using small SBC arm boards and using the ARMbian os on them. They’ve got some great info like this:
https://github.com/ThomasKaiser/Knowledge/blob/master/articles/A1_and_A2_rated_SD_cards.md
and
https://docs.armbian.com/User-Guide_Getting-Started/In the end, what I learned there I apply to AntiX when running from micro-sd / compact flash / eMMC etc. I tend to run from ram unless I’m doing a remaster or heavy duty upgrade. Lotsa’ life when done that way.
Guess I’m a strange one, but fortunately AntiX is superb for these storage devices too.
March 19, 2022 at 9:04 pm #79392Moderator
Brian Masinick
::Interesting; I do occasionally run my antiX images live from USB in Frugal mode, but all of my systems have enough memory to run my systems completely in RAM, so most of the time I have them installed on SSD, which is responsive, then once the OS and the images I use are loaded up they remain in memory. Most browsers load in under 1 GB RAM but even if they grow to 1.5-1.6 GB RAM that’s not a problem; I have more.
For this reason I don’t always run Frugal though it’s fun to do it!
- This reply was modified 1 year, 1 month ago by Brian Masinick.
--
Brian MasinickMarch 20, 2022 at 9:11 pm #79456Moderator
Brian Masinick
::I was *thinking* about this the other day, but I’m not sure that I expressed it, though I have probably mentioned it several times over the years, almost certainly in one of our earlier forums:
Back in the early 2000s, there was a time when many distributions were created that could run live from CD. KNOPPIX was probably one of the early ones, possibly the first. MEPIS, Morphix, Kanotix, Feather Linux, Tiny Linux, and PCLinuxOS were some of the others.
MEPIS eventually became MX Linux as the work “changed hands”, PCLinuxOS grew into predominantly a desktop oriented distribution, and KNOPPIX grew a lot too, though most of these can still initially “boot” from a removable device.
Anyway, back then I’d look around for small CD distributions that could run ENTIRELY from RAM; antiX and MEPIS could both do this in the early days.
It’s ironic that I don’t run from USB that gets “loaded 100% into RAM” very often; that is probably because MOST of my installed disk systems, though contained on fixed physical media, also run completely from RAM once initially loaded.
This is even more true of my hardware that contains solid state drive technology; it is fast to begin with, and when it can also load most, if not all, of it’s contents directly into memory and KEEP it there, rarely moving it or “swapping out”, this explains why it makes less difference where my initial boot media comes from.I’ll have to take some time and get some rough “seat of the pants” feeling of subjective performance using various USB and SSD models, including our much valued “Frugal” modes, and see what the best traits are for each use case.
Overall, using antiX, what has always struck me favorably, in addition to the lean, efficient resource management are the great number of choices – boot and run from external media, save the most commonly used settings and features in Frugal mode, create and install software, then snapshot your own custom software solution, install to disk, etc.
I probably use the snapshot method as often as anything, then install my snapshots on multiple systems that I use; I definitely love the many choices we have – and each of us can pick and choose the method or methods we prefer.
--
Brian MasinickMarch 28, 2022 at 10:04 am #80031Membersubluminal
::I always keep a USB drive with Antix installed on it. I am writing this from within Antix-21 which is installed on an old 8 Gb USB. 1.5 Gb free space left. And I have every piece of software I need or even might need installed here, including GIMP and digikam, firefox-esr, libreoffice-writer, mpv, ffmpeg and a lot more.
Updating takes longer than when I’m using SSD/HDD of course. But since updates don’t happen often, this is fine. I even used the same USB on my friend’s computer with similar hardware. Worked fine. Absolutely amazing. Thanks to all the devs of AntiX and of course, Debian.
March 28, 2022 at 12:42 pm #80035MemberModdIt
::@ PDP-8, if you are a strange one for using SD cards I stand alongside you. Most seem very reliable in long term usage.
If a card reader slot on the device can be used for boot I use it, lowered risk of damage being main reason.
Repairing board damage, when a device has been mishandled with an inserted usb stick or cable is often difficult and very time consuming.With regard to speed of running from USB, with a good stick and USB 2 faster boot and application opening than my best available comparison,
a 7200RPM desktop drive can deliver.
On my Thinkpad which has an unmarked USB3 Port next to charger socket, running antiX live without persistence feels as fast as the fitted SSD.
On a USB 3.1 port the limiting factor is definitely the USB stick. With an EMMC to USB adapter as fast as the internal hardware can handle.Regarding the remark from subluminal on portability of antiX running live, it is pretty much amazing. Only boot or install failures I have seen
were on very recent hardware.antiX is in many ways my celebrated king and queen of linux. I bow deeply to all the developers involved.
- This reply was modified 1 year, 1 month ago by ModdIt.
-
AuthorPosts
- You must be logged in to reply to this topic.