antiX /usr/local conflict

Post Reply
Message
Author
mrmazda
Posts: 14
Joined: Fri May 06, 2016 8:54 pm

antiX /usr/local conflict

#1 Post by mrmazda »

In installed antiX 17.4 full from DVD in order to solve a hardware problem on an old Sony laptop. Right off the bat I got stuck, because:

Code: Select all

E: Sub-process returned an error code
and Google couldn't find me a way to fix it. The apt problem began because apt search returns too much info to be able to locate what I'm actually looking for (name and version only), so I tried to install aptitude, which returns useful search results. apt install inxi returned:

Code: Select all

sh: 1: /usr/local/lib/desktop-menu/desktop-menu-apt-update: not found
E: Problem executing scripts DPkg::Pre-Invoke '/usr/local/lib/desktop-menu/desktop-menu-apt-update set'
E: Sub-process returned an error code
During installation I used existing partition /dev/sda8 and none other. Before first boot, I repaired fstab to include the other OS and realboot partitions, plus /usr/local, which has all my apps installed from .tgzs and .zips from mozilla.org and elsewhere, as well as all my custom scripts in /usr/local/bin, and customizations in /usr/local/etc /usr/local/share.

For now I fix the apt problem with a temporary dismount of /usr/local to run apt. Is there now any way to resolve the conflict between what the installer put in /usr/local, and my /usr/local needs on a more practical long term basis? I can't have antiX OS software interfering with the four (on this SSD, more on others, some with more than 30) other installed distros that mount my /usr/local partition to /usr/local. I brought this up somewhere in this forum years ago. Bind mounting was suggested, but I never got that figured out or came up with any good solution.

There's another problem too: "Failed to execute login command" each time I try to login via the GUI on tty7. I have to umount /usr/local to work around that ahead of each login.

BTW, the problem leading to installing antiX in the first place is inability to get X to use the G86M [GeForce 8400M GT] chip ID: 10de:0426 with either the modesetting DDX or the nouveau DDX. It's stuck using VESA or FBDEV @1024x768 on a 1920x1080 display screen due to lack of device /dev/dri/card0 that web searches have failed to show me how to fix. This is the same on the other distros:

Code: Select all

# xrandr --listproviders
Providers: number : 0
# xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 0mm x 0mm
   1024x768       0.00* 
   800x600        0.00  
   640x480        0.00
# inxi -Gxxbaz
System:
  Host: vaio Kernel: 4.9.160-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc 
  v: 6.3.0 
  parameters: root=/dev/sda8 ipv6.disable=1 net.ifnames=0 noresume nomodeset 
  Console: N/A dm: SLiM 
  Distro: antiX-17.4.1_x64-full Helen Keller 28 March 2019 
  base: Debian GNU/Linux 9 (stretch) 
Machine:
  Type: Laptop System: Sony product: VGN-AR730E v: C3LR1E11 serial: <filter> 
  Chassis: type: 10 serial: N/A 
  Mobo: Sony model: VAIO serial: N/A BIOS: Phoenix v: R2090J8 
  date: 02/26/2008 
CPU:
  Dual Core: Intel Core2 Duo T8100 type: MCP arch: Penryn speed: 1200 MHz 
  min/max: 1200/2101 MHz 
Graphics:
  Device-1: NVIDIA G86M [GeForce 8400M GT] vendor: Sony driver: N/A 
  bus ID: 01:00.0 chip ID: 10de:0426 
  Display: server: X.org 1.19.2 driver: nouveau,vesa 
  unloaded: fbdev,modesetting alternate: nv tty: 80x25 
  Message: Advanced graphics data unavailable in console for root. 
Network:
  Device-1: Marvell 88E8055 PCI-E Gigabit Ethernet vendor: Sony driver: sky2 
  v: 1.30 port: 3000 bus ID: 02:00.0 chip ID: 11ab:4363 
  Device-2: Intel PRO/Wireless 4965 AG or AGN [Kedron] Network 
  driver: iwl4965 v: in-tree: port: 3000 bus ID: 06:00.0 chip ID: 8086:4229 
Drives:
  Local Storage: total: 111.79 GiB used: 24.29 GiB (21.7%) 
Info:
  Processes: 140 Uptime: 24m Memory: 2.94 GiB used: 143.6 MiB (4.8%) 
  Init: SysVinit v: 2.88 runlevel: 5 default: 5 Compilers: gcc: 6.3.0 alt: 6 
  Shell: bash v: 4.4.12 inxi: 3.0.36
# hwinfo --monitor
  32: None 00.0: 10000 Monitor
  [Created at fb.71]
  Unique ID: rdCR.EY_qmtb9YY0
  Hardware Class: monitor
  Model: "Generic Monitor"
  Vendor: "Generic"
  Device: "Monitor"
  Resolution: 1024x768@76Hz
  Year of Manufacture: 0
  Week of Manufacture: 0
  Driver Info #0:
    Max. Resolution: 1024x768
    Vert. Sync Range: 50-90 Hz
    Hor. Sync Range: 31-61 kHz
  Config Status: cfg=new, avail=yes, need=no, active=unknown
http://fm.no-ip.com/Tmp/Linux/Xorg/Nv/ has other info, such as X logs, dmesg, lspci, lsmod. e.g. http://fm.no-ip.com/Tmp/Linux/Xorg/Nv/x ... 1909140337 is the current Xorg.0.log, & http://fm.no-ip.com/Tmp/Linux/Xorg/Nv/s ... -lsmod.txt lsmod.
Multi-machine, multi-boot, so way too much time spent updating. :p

User avatar
fehlix
Developer
Posts: 10366
Joined: Wed Apr 11, 2018 5:09 pm

Re: antiX /usr/local conflict

#2 Post by fehlix »

mrmazda wrote: Sat Sep 14, 2019 4:02 am Before first boot, I repaired fstab to include the other OS and realboot partitions, plus /usr/local, which has all my apps installed from .tgzs and .zips from mozilla.org and elsewhere, as well as all my custom scripts in /usr/local/bin, and customizations in /usr/local/etc /usr/local/share.
antiX and MX do both use /usr/local. So, having you'r own /usr/local mounted will not work.
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

Post Reply

Return to “antiX”