antiX-bullseye-a2-runit_x64-full.iso available

Forum Forums antiX-development Development antiX-bullseye-a2-runit_x64-full.iso available

  • This topic has 148 replies, 15 voices, and was last updated May 14-4:49 pm by skidoo.
Viewing 15 posts - 31 through 45 (of 149 total)
  • Author
    Posts
  • #57273
    Moderator
    ModdIt
    Helpful
    Up
    0
    :D

    Slight user irritation due Applications tab showing twice in menu.

    The expected entry with majority of applications.

    Second entry in lower part of menu has sub tabs for setup Firewall and Partimage manual links.
    Maybe best to move that to man pages entry sub menu, I did just that.

    • This reply was modified 2 months, 1 week ago by ModdIt.
    #57330
    Moderator
    ModdIt
    Helpful
    Up
    0
    :D

    a2 Bullseye Runit
    conky always showing time as AM. It is evening here my time is set to EU Berlin
    Displayed Conky time is 09:15

    Present setting for time display in /home/username/.conkyrc line 104 is ${time %I:%M}

    Changing that time display string to: ${time %H:%M} Displays 21:21
    Correct for time now in 24 Hour format.

    #57336
    Member
    skidoo
    Helpful
    Up
    0
    :D

    .

    Belatedly, I realized there’s another file, for users of the newer conky version…

    dpkg -S /etc/skel/.conkyrc-lua
    ^–v
    desktop-defaults-core-antix: /etc/skel/.conkyrc-lua

    hopefully Moddit will be suitably motivated to followup and edit+mergerequest that file

    • This reply was modified 2 months, 1 week ago by skidoo.
    #57337
    Member
    calciumsodium
    Helpful
    Up
    0
    :D

    1. Both the antiX-bullseye-a2-runit_x64-full and the antiX-bullseye-a2-runit_x64-full-legacy kernel do not boot up in my HP 6730b system with an intel core 2 duo processor (2.4 GHz) with 2 GB ram.

    2. Both the antiX-bullseye-a2-runit_x64-full and the antiX-bullseye-a2-runit_x64-full-legacy kernel do not boot up in my HP 6730b system with a Centrino processor (2.4 GHz) with 4 GB ram.

    For both systems, booting leads only to a blank screen freeze.

    This is surprising, since both these systems work really well with antiX 19.X.
    These tests were done using a live USB created with the antiX-bullseye-a2-runit_x64-full.iso file successfuly created by the live USB maker.

    #57338
    Member
    calciumsodium
    Helpful
    Up
    0
    :D

    However, the live USB, created with the antiX-bullseye-a2-runit_x64-full.iso file successfuly created by the live USB maker, boots up well on an HP 6550b system with an i3 processor with 4 GB of ram.

    Some initial questions/findings:
    1. Under Control Centre > Drivers, there is no Windows Wireless Drivers program anymore. I actually use this in my antiX 19.X systems for some of the older wireless hardware. Any chance that this program can be included?
    2. For Themes, when I change from the Clearview Blue Medium theme to the Default, I no longer see the Minimize, Maximize, Close icons on the top right of the windows. I only see blank boxes.

    #57339
    Member
    calciumsodium
    Helpful
    Up
    0
    :D

    I would like to test how WINE works on antiX-bullseye-a2-runit_x64,
    but package installer does not work.

    Also, I cannot update

    I get this error. Do I have to wait until the mirror gets updated?
    sudo apt update
    Get:1 http://ftp.us.debian.org/debian bullseye InRelease [142 kB]
    Get:2 http://la.mxrepo.com/antix/bullseye bullseye InRelease [27.2 kB]
    Reading package lists… Done
    E: Release file for http://ftp.us.debian.org/debian/dists/bullseye/InRelease is not valid yet (invalid for another 1h 3min 56s). Updates for this repository will not be applied.
    E: Release file for http://la.mxrepo.com/antix/bullseye/dists/bullseye/InRelease is not valid yet (invalid for another 3h 48min 23s). Updates for this repository will not be applied.

    #57340
    Member
    skidoo
    Helpful
    Up
    0
    :D

    not valid yet (invalid for another 1h 3min 56s).

    Check (and adjust) your system time.
    That error message is typically thrown due to due incorrect clock.

    #57341
    Member
    skidoo
    Helpful
    Up
    0
    :D

    Under Control Centre > Drivers, there is no Windows Wireless Drivers program anymore. I actually use this in my antiX 19.X systems for some of the older wireless hardware. Any chance that this program can be included?

    Of course there’s “any chance”…
    but right now, the “runit” offering is a toy, an experiment.

    #57342
    Member
    skidoo
    Helpful
    Up
    0
    :D

    when I change from the Clearview Blue Medium theme to the Default

    Hmm, I thought “Clearview Blue Medium” _was_ the default theme.

    checking the other medium themes…

    Truth ice: the layout has the set of 3 buttons displayed on the lefthand side
    ( I’m guessing that’s normal/expected )

    in my testing, all these display 3 buttons at righthand side:
    Simplest black Medium
    SunnyDay Medium
    quiescent Medium
    PinkyandtheBrain Medium
    Korstro
    KorstroDark
    IceClearLooks
    IceGil
    IceNoir
    Groove
    FauxGlass
    EcdoGreen
    ClearviewGlass
    ClearviewOrange
    BlueCrystal
    BlueDay

    metal 2: 4 buttons at right side

    Breathe: all buttons hidden until hovered

    BreatheYellow: all buttons except minimize hidden until hovered

    Possibly the behavior of the 2 Breathe variants indicates a glitch… or their behavior might just represent a style/design choice.

    FWIW, for all of the themes tested, right-clicking the window titlebar did correctly expose the context menu. All button actions, plus additional actions, are available from that context menu.

    #57345
    Member
    calciumsodium
    Helpful
    Up
    0
    :D

    Hi @skidoo,
    In my testing, when you click on the Themes menu, there is a Default at the very bottom of the Themes menu. That was the Default that I was selecting. I will check on the system clock. My computers are set to local CST time.

    Any suggestions on how to modify options on the boot menus to get the antiX-bullseye-a2-runit_x64 testing to work on my
    HP 6730 systems? They should be strong enough and have enough RAM to work. I just used the defaults.

    #57346
    Member
    skidoo
    Helpful
    Up
    0
    :D

    Looks like the package installer is also failing to install codec packages
    terminal window disappears so Fast I am unable to see any messages.

    Hey, here’s an idea for ya
    ;^)

    sudo cat /var/log/mxpi.log
    or
    sudo leafpad /var/log/mxpi.log

    #57353
    Moderator
    ModdIt
    Helpful
    Up
    0
    :D

    Hi calciumsodium,
    regarding: Any suggestions on how to modify options on the boot menus to get the antiX-bullseye-a2-runit_
    x64 testing to work on my HP 6730 systems? They should be strong enough and have enough RAM to work.
    I just used the defaults.

    have you tried using bios defaults on those devices, a2 runit “toy experiment” runs fine on anything I have
    played with to date. Core 2 duo runs ok with 1 Gig ram, was rarely swapping.
    BIOS was the key on a stubborn fujitsu device I was given a couple of weeks ago.

    As a first step you could also try booting with failsafe.

    #57367
    Member
    calciumsodium
    Helpful
    Up
    0
    :D

    Thank you @Moddit,
    the failsafe boot options works great for my HP 6730b Core 2 Duo and Centrino systems!

    It seems like the a2 runit “toy experiment” boots up a lot faster than the antiX 19.X versions. While booting, the a2 runit toy experiment does not print out on the screen as many options/lines as the antiX 19.X. Is this meant to be this way? The faster boot time is very nice.

    #57371
    Forum Admin
    anticapitalista
    Helpful
    Up
    0
    :D

    While booting, the a2 runit toy experiment does not print out on the screen as many options/lines as the antiX 19.X. Is this meant to be this way? The faster boot time is very nice.

    Yes it is meant to be that way.

    Philosophers have interpreted the world in many ways; the point is to change it.

    antiX with runit - leaner and meaner.

    #57373
    Member
    calciumsodium
    Helpful
    Up
    0
    :D

    Hi @skidoo,
    I was able to adjust system clock and am now able to do sudo apt update.

    However, I am not able to install WINE.

    Here is my error message and how do I go about overcoming this. Thanks.

    Preconfiguring packages …
    (Reading database … 175307 files and directories currently installed.)
    Preparing to unpack …/libc6_2.31-11_amd64.deb …
    ERROR: Your kernel version indicates a revision number
    of 255 or greater. Glibc has a number of built in
    assumptions that this revision number is less than 255.
    If you\’ve built your own kernel, please make sure that any
    custom version numbers are appended to the upstream
    kernel number with a dash or some other delimiter.

    dpkg: error processing archive /var/cache/apt/archives/libc6_2.31-11_amd64.deb (–unpack):
    new libc6:amd64 package pre-installation script subprocess returned error exit status 1
    Selecting previously unselected package libc6:i386.
    Preparing to unpack …/libc6_2.31-11_i386.deb …
    De-configuring libc6:amd64 (2.31-10) …
    ERROR: Your kernel version indicates a revision number
    of 255 or greater. Glibc has a number of built in
    assumptions that this revision number is less than 255.
    If you\’ve built your own kernel, please make sure that any
    custom version numbers are appended to the upstream
    kernel number with a dash or some other delimiter.

    dpkg: error processing archive /var/cache/apt/archives/libc6_2.31-11_i386.deb (–unpack):
    new libc6:i386 package pre-installation script subprocess returned error exit status 1
    Errors were encountered while processing:
    /var/cache/apt/archives/libc6_2.31-11_amd64.deb
    /var/cache/apt/archives/libc6_2.31-11_i386.deb
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    demo@antix1:~

Viewing 15 posts - 31 through 45 (of 149 total)
  • You must be logged in to reply to this topic.