- This topic has 205 replies, 24 voices, and was last updated Aug 21-4:47 pm by rej.
-
Posts
-
christophe
BobC is right. I took the liberty of clipping a bit off the sides in mtPaint. (Which is probably what the wallpaper setter does in “fill” mode.) Maybe you like one of these? (If not, I won’t take offense.)
- This reply was modified 3 years, 9 months ago by christophe.
confirmed antiX frugaler, since 2019
Dave
Is there any way in Rox to set the wallpaper placement mode to the
equivalent of ‘fill’ or ‘zoom’?I think there is. Similar to spacefm having a gui but not a command line option. If you right click on a desktop icon you should see “backdrop” in the list.
I noticed that the Rox-Wallpaper script is packaged with wallpaper-antix. I am working on modifying the script to allow command line changing followed by the wallpaper app using this ability. If you manage to find a method of modifying the wallpaper from the command line in spacefm; do let me know. It would be nice to include the options for spacefm as well while updating the wallpaper app for rox.Edit:
Here is where the set_wallpaper command line option is set/parsed as best I can tell.
https://github.com/IgnorantGuru/spacefm/blob/e6f291858067e73db44fb57c90e4efb97b088ac8/src/main.c#L1169
Perhaps someone would like to try adding a set_wallpaper_style to parse a –set-wallpaper-style= option.
and the help information to update to state that option is found here
https://github.com/IgnorantGuru/spacefm/blob/e6f291858067e73db44fb57c90e4efb97b088ac8/src/main.c#L672I do not know enough about C to feel confident enough to make the changes.
At the same time it would be nice to not make another script to alter the wallpaper= and wallpaper_mode= declarations in ~/.config/spacefm/session . Especially seeing the top of the config files states
“# THIS FILE IS NOT DESIGNED TO BE EDITED – it will be read and OVERWRITTEN”
Though it does work…- This reply was modified 3 years, 9 months ago by Dave.
Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
BobC
Or an easy do it yourself answer is to right click the help icon, click backdrop, and on style where Stretch is selected, click Fit instead, then close.
I didn’t have the problem with the moon getting distorted when using the SpaceFM-IceWm desktop.
Anonymous
Or … just use THIS and we’re finally done with the topic.
https://www.antixforum.com/forums/topic/antix-flat-wallpaper-to-modernize/page/3/#post-24901
BitJam
As noted above, in the live toram did not work
It works here both with and without tsplash enabled, booting legacy and UEFI. In beta-1 you needed tsplash enabled for toram to work.
The error message you posted over in the MX Forums “Could not create the toram option” seems strange. When does this error message show up?
Context is worth 80 IQ points -- Alan Kay
entropyfoe
bitjam,
That comment was for the beta1.
In this forum, when I installed the beta2, I noted that the toram option worked.
My sound issues are better, but still some nagging problems.
XMMS and youtube have sound.
Audacity initially did, but I tried to use it again last night, and it had no sound.
In the preferences, it still listed pulse as the device.(I installed pulse audio per Xecure’s advice and help. It got youtube playing with sound, and XMMS continued with sound.)
- This reply was modified 3 years, 9 months ago by entropyfoe.
Asus Prime 370X-Pro
AMD Ryzen 1600X (6 cores @ 3.6 GHz)
16 Gig DDR4 3200 (G Skill)
Nvidia -MSI GeForce GT 710 fanless
Samsung 960 NVMe SSD nvme0n1 P1,P2, and P3=MX-18, P4=antiX-19 beta
2TB WD sda1= data
on-board ethernet &and soundmodel99
Bobc and Christophe,
Thank you for your feedback on my inquiry, it is appreciated.
The “image dark_city_small_gold_moon.png”, I am just using it for the
purpose of testing the beta and getting a better understanding of
how the different window manager/desktop managers options behave in
antiX.Dave,
Yes indeed, there is in Rox a “Set backdrop” option after right clicking
the Files icon and then clicking Backdrop.I set the “style” to “Fit” and I got a round moon but the change also
blew apart the right most windmill. Also, after logging off and then
logging back in, the “style” reverted back to “Stretch”.With Spacefm, The setting of the Mode (equivalent to style) is persistent.
So once it is set to “Zoom”, it stays set after changing wallpaper with
the “Choose Wallpaper” app and after logging off/on.The option to choose a mode/style in “Choose Wallpaper” when NOT using
a desktop manager(Rox or Space) is also not persistent.Example:
While in straight “Icewm” with no desktop manager, use “Choose Wallpaper”
app to set the image to
“image dark_city_small_gold_moon.png” with “fill” selected as the
mode/style.
The moon should be round.Change your desktop to “Space-Icewm”.
Use “Choose Wallpaper” app to set the image to
“lines.jpg” or anything but “image dark_city_small_gold_moon.png”.
The ability to set the mode/style is unavailable.Go back to having a straight “Icewm” session with no desktop manager desktop.
The moon will be oblong.orcrist
On the beta2 the keyboard layouts configuration is not saved between reboots. I run the system from live usb with both root and home persistence.
I can configure the keyboard layouts (in my case German QWERTY and Greek Extended), if I log out and in again the fbxkb tray icon appears, layouts are changed normally with alt_shift, everything seems to work OK. I reboot after saving both root and home persistence, but after the new boot, the layouts are unconfigured again. Strange, as it has never happened before on the 17 versions and on the 19 beta1.BitJam
On the beta2 the keyboard layouts configuration is not saved between reboots. I run the system from live usb with both root and home persistence.
I can configure the keyboard layouts (in my case German QWERTY and Greek Extended), if I log out and in again the fbxkb tray icon appears, layouts are changed normally with alt_shift, everything seems to work OK. I reboot after saving both root and home persistence, but after the new boot, the layouts are unconfigured again. Strange, as it has never happened before on the 17 versions and on the 19 beta1.My guess is you have a boot parameter that is setting the language and thus also the timezone, keyboard layout, and a few other things.
What is the output of the command:
cat /proc/cmdline
If you have a language setting, for example, in your boot parameters then that will automatically change the keyboard layout. One way around this is to also set the keyboard with boot parameters:kbd= keyboard layout kbopt= keyboard options kbvar= keyboard variantI believe all the valid values are in /usr/share/X11/xkb/rules/xorg.lst. Another approach is to remove the language boot parameter and let persistence take care of saving that. I don’t think we have a “language only” boot parameter that sets the language and nothing else. Perhaps this would be useful in some cases. Maybe use lang_only= for it. This would let you set the language for the early boot process without clobbering any other settings.
We have to let boot parameters over-ride saved settings otherwise the boot parameters would not work.
Context is worth 80 IQ points -- Alan Kay
rej
Hi-
This all has likely been addressed, but just in case:
On install GUI, checked “local time” and it installed as UTC. Changed it in Clock settings –
IceWM: un-selected UTC
Xfce: Timezone – “leave empty to use localtime”and it just remains UTC time.
Installed “timesettings” in Synaptic – that did not work after making the selections in terminal.
———————
Rox-filer and SpaceFM: text files have gear icons and if they are clicked on to “open”, and the file has a list of bash commands inside, it runs all the commands.One file contained Firejail configurations list for my browsers and when clicked on, opened the browsers listed with the various command lines automatically until they all appeared.
—————————–
Rox-Panel-Toggle covers tops of open applications whether it it set to “Do not cover panel” or not.
—————————–
Firejail needs “Firejail-profiles” installed to run.
—————————–
Menu-Help-IceWM: Only “OSNews” appears to open to anything.Thank you for all the great work put into antiX!
Xecure
and it just remains UTC time.
I have no real understanding of how “local time” works. Is it supposed to use the BIOS time?
For setting the time on my computer, I go to
Control Center > System > Set Date and Time
I configure my timezone.
Then I go to the terminal and do:
sudo ntpdate pool.ntp.orgRox-filer and SpaceFM: text files have gear icons and if they are clicked on to “open”, and the file has a list of bash commands inside, it runs all the commands.
I am not sure, but I think that happens when a file is considered “executable”. Has always happened to me.
Until someone confirms it as a bug, you could disable single-click, normal click on a file to select it, and right-click and open with your preferred Text Editor.Rox-Panel-Toggle covers tops of open applications whether it it set to “Do not cover panel” or not.
Right click on Rox Panel, ROX Filer > Options…
Got to last tab “Compatibility”, unpick “Panel stays on top”
Save and toggle Off/On the panel again and it should be fixed.The other bugs are good reports, I think.
- This reply was modified 3 years, 9 months ago by Xecure. Reason: last piece of rox panel info
antiX Live system enthusiast.
General Live Boot Parameters for antiX.On the beta2 the keyboard layouts configuration is not saved between reboots. I run the system from live usb with both root and home persistence.
I can configure the keyboard layouts (in my case German QWERTY and Greek Extended), if I log out and in again the fbxkb tray icon appears, layouts are changed normally with alt_shift, everything seems to work OK. I reboot after saving both root and home persistence, but after the new boot, the layouts are unconfigured again. Strange, as it has never happened before on the 17 versions and on the 19 beta1.My guess is you have a boot parameter that is setting the language and thus also the timezone, keyboard layout, and a few other things.
What is the output of the command:
cat /proc/cmdline
If you have a language setting, for example, in your boot parameters then that will automatically change the keyboard layout. One way around this is to also set the keyboard with boot parameters:kbd= keyboard layout kbopt= keyboard options kbvar= keyboard variantI believe all the valid values are in /usr/share/X11/xkb/rules/xorg.lst. Another approach is to remove the language boot parameter and let persistence take care of saving that. I don’t think we have a “language only” boot parameter that sets the language and nothing else. Perhaps this would be useful in some cases. Maybe use lang_only= for it. This would let you set the language for the early boot process without clobbering any other settings.
We have to let boot parameters over-ride saved settings otherwise the boot parameters would not work.
Thanks Bitjam
I have added the following boot parameters: kbd=de,el kbopt=grp:alt_shift_toggle kbvar=qwerty,extended. fbxkb now loads with the desired layouts and works as expected.
Of course I had also to save it with F8.
I haven’t yet understood how to “remove the language boot parameter and let persistence take care of saving that”
rokytnji
Asus Q302LA Touchscreen Netbook . History at MX forums: https://forum.mxlinux.org/viewtopic.php?f=107&t=50525
Long story short. Broke the internal sata connections so bios won’t see internal hard no more. So running persistent usb instead made with MX 18 and pny 8 gig usb for now.
demo@antix1:~ $ inxi -Fxz System: Host: antix1 Kernel: 4.9.182-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: IceWM 1.5.5+git20190610 Distro: antiX-19.b2_x64-full Marielle Franco 13 July 2019 base: Debian GNU/Linux 10 (buster) Machine: Type: Laptop System: ASUSTeK product: Q302LA v: 1.0 serial: <filter> Mobo: ASUSTeK model: Q302LA v: 1.0 serial: <filter> UEFI: American Megatrends v: Q302LA.203 date: 05/15/2014 Battery: ID-1: BAT0 charge: 43.7 Wh condition: 44.5/50.1 Wh (89%) model: ASUSTeK UX3-44 status: Discharging CPU: Topology: Dual Core model: Intel Core i3-4030U bits: 64 type: MT MCP arch: Haswell rev: 1 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 15165 Speed: 1800 MHz min/max: 800/1800 MHz Core speeds (MHz): 1: 1800 2: 1800 3: 1800 4: 1799 Graphics: Device-1: Intel Haswell-ULT Integrated Graphics vendor: ASUSTeK driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 18.3.6 direct render: Yes Audio: Device-1: Intel Haswell-ULT HD Audio driver: snd_hda_intel v: kernel bus ID: 00:03.0 Device-2: Intel 8 Series HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k4.9.182-antix.1-amd64-smp Network: Device-1: MEDIATEK MT7630e 802.11bgn Wireless Network Adapter vendor: Foxconn driver: mt7630e v: 2.3.8 port: f040 bus ID: 02:00.0 IF: wlan0 state: up mac: <filter> Drives: Local Storage: total: 939.12 GiB used: 193.78 GiB (20.6%) ID-1: /dev/sda type: USB vendor: PNY model: USB 2.0 FD size: 7.61 GiB ID-2: /dev/sdb type: USB vendor: Toshiba model: External USB 3.0 size: 931.51 GiB Partition: ID-1: / size: 2.89 GiB used: 88.9 MiB (3.0%) fs: overlay source: ERR-102 Sensors: System Temperatures: cpu: 43.0 C mobo: N/A Fan Speeds (RPM): cpu: 2600 Info: Processes: 162 Uptime: 50m Memory: 5.72 GiB used: 769.8 MiB (13.1%) Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.33Kernel does contain wifi modules for this laptop. So I manually added them.
demo@antix1:~ $ cd Documents demo@antix1:~/Documents $ ls MT7630E-release demo@antix1:~/DocumentsTouchscreen does not work in live mode yet. I can’t compare to MX 18 because Touchscreen worked after hard drive install. But I did not test during a love run. It is early morning here so that is it from me today. If you need any info. Instruct me. I will be happy to try and comply. My persist live usb cherry has been popped. 1st time for everything I guess. Installing the wifi driver was pretty KISS with sudo ./install as the command in the folder where the install file sits. It would not allow install without using sudo on persist usb. Learn something new every day.
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 problemsXecure
Hey, rokytnji
Touchscreen does not work in live mode yet.
There is not enough info!
First thing we need is to know what the touchscreen device is. You expect too much from us just exploring other places to try to figure out ourselfs. Fortunately, the info is in your MXforum post (but it is better to be redundant and also publish it here for the next time, instead of expecting us to go for a goose chase).
Device-4: 3-1.7:5 info: Atmel type: HID driver: hid-generic,hid-multitouch,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s chip ID: 03eb:8a41Now, check to see if the device is detected:
lsusb | grep "Atmel"If detected, check to see if the module is active. Your MX linux post indicates it may be using a generic touch driver: hid-generic,hid-multitouch,usbhid
lsmod | grep "hid-multitouch"
If this doesn’t appear, maybe check to see for “atmel” and “mxt” in case none of the above are loaded but it now uses a specific atmel_mxt_ts module.Next thing, I don’t know of anyone that has tested antiX 19b2 on touchscreen (I cannot until I get my tablet back), but there was a change between antiX 19 beta 1 and 2:
Beta 1 used: xserver-xorg-input-mtrack (Multitouch X input driver)
Beta 2 used: xserver-xorg-input-mouse (X.Org X server — mouse input driver)
So maybe you may first have to install the multitouch package (and maybe uninstall the other one) to see if touch works.If this doesn’t fix it, I searched for the device on the net (Atmel touch screen). Debian includes it in the 4.19 kernels, so (even though antiX kernels are not based on Debian), try to see if updating the kernel fixes the issue. (You will have to use the Live-USB kernel Updater after downloading the latest 4.19 antiX kernel).
Restart.
If detected, and still not working, see if there is any error message with dmesg related to the multitouch driver:
dmesg | grep "multitouch"
or
dmesg | grep "atmel"
or
dmesg | grep "hid"
Maybe a firmware is missing and not found in the expected folder. Take note of it. If it is in MX, you may be able to search for it in the specified folder in any MX machine and move it to the correct folder in you antiX persistence USB.If the module is not loaded at all, then you may have to download and build it.
I am not sure, but maybe your touchscreen is a “Atmel maXTouch”
Maybe you can find the driver module here:
https://github.com/atmel-maxtouchLet us know how it goes.
- This reply was modified 3 years, 9 months ago by Xecure. Reason: fix words
antiX Live system enthusiast.
General Live Boot Parameters for antiX.rokytnji
Let us know how it goes.
For sure!
There is not enough info!
I know. Fresh install and I was doing good to get the wifi working first. Thanks for responding. I am usually pretty good at posting details. But I am swamped today and all summer long with exterior distractions. Like being bummed out I broke the laptop.
It was not my intention to worry about touch screen yet. My post was more of a explore session in virgin territory for me.
I included the MX link for detail completion in my post. Best way I know how without copy and paste all posts from there to here.Have a great day. Break time thirty for me.
demo@antix1:~ $ su Password: root@antix1:/home/demo# cat /proc/bus/input/devices I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input0 U: Uniq= H: Handlers=kbd leds event0 B: PROP=0 B: EV=120013 B: KEY=402000000 3803078f800d001 feffffdfffefffff fffffffffffffffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor=0000 Product=0005 Version=0000 N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input5 U: Uniq= H: Handlers=event1 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor=0000 Product=0003 Version=0000 N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input6 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor=0000 Product=0001 Version=0000 N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input7 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=10000000000000 0 I: Bus=0019 Vendor=1043 Product=0000 Version=0000 N: Name="Asus Wireless Radio Control" P: Phys=asus-wireless/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/ATK4002:00/input/input8 U: Uniq= H: Handlers=kbd rfkill event4 B: PROP=0 B: EV=3 B: KEY=80000000000000 0 0 0 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card1/input13 U: Uniq= H: Handlers=event5 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0019 Vendor=0000 Product=0006 Version=0000 N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input14 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=3e000b00000000 0 0 0 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel HDMI HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input15 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel HDMI HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input16 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel HDMI HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input17 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0019 Vendor=0000 Product=0000 Version=0000 N: Name="Asus WMI hotkeys" P: Phys=asus-nb-wmi/input0 S: Sysfs=/devices/platform/asus-nb-wmi/input/input18 U: Uniq= H: Handlers=kbd rfkill event10 B: PROP=0 B: EV=100013 B: KEY=10000000c0000 0 0 0 0 81606f00900000 200027801701000 e000000000000 0 B: MSC=10 I: Bus=0011 Vendor=0002 Product=000e Version=0000 N: Name="ETPS/2 Elantech Touchpad" P: Phys=isa0060/serio4/input0 S: Sysfs=/devices/platform/i8042/serio4/input/input12 U: Uniq= H: Handlers=mouse0 event11 B: PROP=5 B: EV=b B: KEY=e420 10000 0 0 0 0 B: ABS=661800011000003 root@antix1:/home/demo# exit exit demo@antix1:~ $demo@antix1:~ $ lsusb | grep "Atmel" demo@antix1:~ $ dmesg | grep "atmel" demo@antix1:~ $ dmesg | grep "hid" [ 1.177387] hidraw: raw HID events driver (C) Jiri Kosina [ 1.177624] usbcore: registered new interface driver usbhid [ 1.177625] usbhid: USB HID core driverdemo@antix1:~ $ dmesg | grep usb [ 0.146482] usbcore: registered new interface driver usbfs [ 0.146492] usbcore: registered new interface driver hub [ 0.146511] usbcore: registered new device driver usb [ 1.162489] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 1.162491] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.162492] usb usb1: Product: EHCI Host Controller [ 1.162494] usb usb1: Manufacturer: Linux 4.9.182-antix.1-amd64-smp ehci_hcd [ 1.162495] usb usb1: SerialNumber: 0000:00:1d.0 [ 1.164187] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [ 1.164188] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.164190] usb usb2: Product: xHCI Host Controller [ 1.164191] usb usb2: Manufacturer: Linux 4.9.182-antix.1-amd64-smp xhci-hcd [ 1.164192] usb usb2: SerialNumber: 0000:00:14.0 [ 1.166454] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003 [ 1.166456] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.166457] usb usb3: Product: xHCI Host Controller [ 1.166458] usb usb3: Manufacturer: Linux 4.9.182-antix.1-amd64-smp xhci-hcd [ 1.166459] usb usb3: SerialNumber: 0000:00:14.0 [ 1.177624] usbcore: registered new interface driver usbhid [ 1.177625] usbhid: USB HID core driver [ 1.472354] usb 1-1: new high-speed USB device number 2 using ehci-pci [ 1.591817] usb 1-1: New USB device found, idVendor=8087, idProduct=8000 [ 1.591820] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 1.864349] usb 1-1.3: new high-speed USB device number 3 using ehci-pci [ 1.945714] usb 1-1.3: New USB device found, idVendor=154b, idProduct=007a [ 1.945717] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1.945719] usb 1-1.3: Product: USB 2.0 FD [ 1.945722] usb 1-1.3: Manufacturer: PNY Technologies [ 1.945723] usb 1-1.3: SerialNumber: AA00000000005453 [ 2.009340] usb 1-1.4: new high-speed USB device number 4 using ehci-pci [ 2.090660] usb-storage 1-1.3:1.0: USB Mass Storage device detected [ 2.090757] scsi host0: usb-storage 1-1.3:1.0 [ 2.090863] usbcore: registered new interface driver usb-storage [ 2.091174] usbcore: registered new interface driver uas [ 2.103084] usb 1-1.4: New USB device found, idVendor=0489, idProduct=e069 [ 2.103087] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2.103089] usb 1-1.4: Product: BT [ 2.103091] usb 1-1.4: Manufacturer: MediaTek [ 2.103093] usb 1-1.4: SerialNumber: 1.0 [ 39.031877] mtk_usb_reset [ 39.280704] usb_send_vendor_hci_cmd: return=0 [ 39.280751] usbcore: registered new interface driver mtk_bt_loader [ 39.280867] usb_vendor_hci_cmd_complete [ 39.299748] usb 1-1.4: USB disconnect, device number 4 [ 39.728929] usb 1-1.4: new high-speed USB device number 5 using ehci-pci [ 39.810479] usb 1-1.4: New USB device found, idVendor=0e8d, idProduct=763f [ 39.810483] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 39.810485] usb 1-1.4: Product: BT [ 39.810487] usb 1-1.4: Manufacturer: MediaTek [ 39.810489] usb 1-1.4: SerialNumber: 1.0 [ 47.453745] usbcore: registered new interface driver btusb demo@antix1:~ $demo@antix1:~ $ apt search multitouch Sorting... Done Full Text Search... Done libmtdev1/now 1.1.5-1+b1 amd64 [installed,local] Multitouch Protocol Translation Library - shared library demo@antix1:~ $ dmesg | grep "multitouch" demo@antix1:~ $ dmesg | grep "mxt" demo@antix1:~ $ dmesg | grep mxt demo@antix1:~ $Greping “multitouch” or multitouch returns nothing. xinput command not found.
demo@antix1:~ $ xinput --list bash: xinput: command not founddemo@antix1:~ $ cd Downloads demo@antix1:~/Downloads $ sudo dpkg -i xinput_1.6.2-1+b1_amd64\(1\).deb Selecting previously unselected package xinput. (Reading database ... 185059 files and directories currently installed.) Preparing to unpack xinput_1.6.2-1+b1_amd64(1).deb ... Unpacking xinput (1.6.2-1+b1) ... Setting up xinput (1.6.2-1+b1) ... Processing triggers for man-db (2.8.5-2) ... demo@antix1:~/Downloads $ xinpit --list bash: xinpit: command not found demo@antix1:~/Downloads $ xinput --list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpad id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Asus Wireless Radio Control id=7 [slave keyboard (3)] ↳ Video Bus id=8 [slave keyboard (3)] ↳ Sleep Button id=9 [slave keyboard (3)] ↳ Asus WMI hotkeys id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=11 [slave keyboard (3)] demo@antix1:~/DownloadsAfter checking inxi -v8 in AntiX. It does not show the same output in usb as MX did. Touchscreen is not present. But. That MX inxi -v8 was done after a full install on hard drive. Not a live run.
- This reply was modified 3 years, 9 months ago by rokytnji.
- This reply was modified 3 years, 9 months ago by rokytnji.
- This reply was modified 3 years, 9 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 problems
- You must be logged in to reply to this topic.
