antiX-bullseye-beta1 iso files available. 64 bit only

Forum Forums News Announcements antiX-bullseye-beta1 iso files available. 64 bit only

  • This topic has 135 replies, 17 voices, and was last updated Jul 23-3:42 pm by Brian Masinick.
Viewing 15 posts - 121 through 135 (of 136 total)
  • Author
    Posts
  • #62917
    Member
    Ampersand
    Helpful
    Up
    0

    Failure. antiX-bullseye-b1-runit_x64-full (Grup Yorum 10 June 2021)
    On this PC on booting from usb:

    1. blank, black, empty as a November night screen with a lone underscore
    2. after unplugging a sata 2.5″ disk: see attached image Accidentally uplugged all even the USB pendrive, don’t mind this point, nor the attached image

    some GRUB issues?

    PS.

    1. Don’t ask me to unscrew the M.2 NVMe. I don’t participate in this kind of activities.
    2. Yes, currently partitions or smth may be screwed up, but it is my constitutional right to keep it like that
    • This reply was modified 2 weeks, 2 days ago by Ampersand.
    Attachments:

    I am not much into this linux thing...

    #62924
    Member
    Xecure
    Helpful
    Up
    0

    It seems that it goes directly to the UEFI interactive shell and doesn’t get to load grub from the USB device.

    Can you see if the USB device boots on other machines (if you have any other one available)? Or, do you know if other versions of antiX Live USB boot properly on the machine in the same conditions?

    #62930
    Moderator
    ModdIt
    Helpful
    Up
    0

    Hi Ampersand,
    did you use boot menu (often F12, keep pressing switch on computer) or set in BIOS to boot from USB before other devices.

    Black screen blinking underscore I see quite often, especially when new users are involved.

    #62933
    Member
    Ampersand
    Helpful
    Up
    0

    Can you see if the USB device boots on other machines (if you have any other one available)? Or, do you know if other versions of antiX Live USB boot properly on the machine in the same conditions?

    Twice yes:

    1. Same image on another PC
    2. 19.3 on the same (mini) PC

    I am not much into this linux thing...

    #62938
    Member
    Ampersand
    Helpful
    Up
    0

    Hi Ampersand,
    did you use boot menu (often F12, keep pressing switch on computer) or set in BIOS to boot from USB before other devices.

    Hi Moddit,
    Actually there is a jolly welcome to grub message for a few seconds before the unblinking underscore appears. This happens when the usb pendrive with the mentioned iso is in the socket and UEFI boot options start from `Linpus Linux’ in the top choice.

    I am not much into this linux thing...

    #62939
    Member
    Xecure
    Helpful
    Up
    0

    Many things changed in the grub boot loader from antiX 19.4 to the new beta for both the live init scripts and the grub menus. It is possible that one of the new changes for UEFI boot can be responsible.

    So that the devs can see if they can find anything, could you tell us:

    1. The machine that loads to “Welcome to grub” terminal screen (and then to UEFI interactive shell) is this one?
    2. Did you create the live USB with live-USB-maker or with a different tool (Rufus in Windows, balena-etcher or something else).
    3. Do you have the BIOS setting for both UEFI and Legacy (CSM) boot, or ony UEFI boot?
    4. Shouldn’t be a problem, but, do you have Secure Boot enabled? (it normally doesn’t give problems to antiX Live boot, but still may help the devs).

    Thanks for your time. Hopefully this can help the devs figure something out.

    #62950
    Member
    Ampersand
    Helpful
    Up
    0
    1. yes. But the final testimony is the unblinking underscore. efi shell only when usb lowered in boot order.
    2. Rufus in Windows. Also please see point 1
    3. no, for there is no such option in efi. Also please see point 2<
    4. no, as above. Also please see point 2

    I am not much into this linux thing...

    #63006
    Member
    Ampersand
    Helpful
    Up
    0

    Anyway, it is seems that it has already been observed.

    I am not much into this linux thing...

    #63029
    Member
    Xecure
    Helpful
    Up
    0

    BUG for desktop session “minimal-<wm>”
    Ignore the previously mentioned bug report. min-<wm> is the correct exec command.

    Rufus in Windows. Also please see point 1

    I may have time later today to test if creating the live USB with Rufus gives some kind of conflict with the new boot options. I have booted the bullseye b1 ISO on all my machines without problems (even in a small mini-pc), but I never tested creating the ISO with Rufus, so I will check.

    • This reply was modified 1 week, 5 days ago by Xecure.
    #63032
    Moderator
    Brian Masinick
    Helpful
    Up
    0

    I am using b1-runit live today:

    inxi -Fxz
    System: Host: antix1 Kernel: 4.9.0-264-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: IceWM 2.4.0
    Distro: antiX-bullseye-b1-runit_x64-full Grup Yorum 10 June 2021 base: Debian GNU/Linux 11 (bullseye)
    Machine: Type: Laptop System: Dell product: Inspiron 5558 v: 01 serial: <filter>
    Mobo: Dell model: 086DKN v: A00 serial: <filter> UEFI: Dell v: A04 date: 08/06/2015
    Battery: ID-1: BAT0 charge: 33.9 Wh condition: 33.9/41.4 Wh (82%) model: Samsung SDI DELL 07G07587587 status: Full
    CPU: Topology: Dual Core model: Intel Core i7-5500U bits: 64 type: MT MCP arch: Broadwell rev: 4 L2 cache: 4096 KiB
    flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19157
    Speed: 2400 MHz min/max: 500/3000 MHz Core speeds (MHz): 1: 2400 2: 2413 3: 2400 4: 2400
    Graphics: Device-1: Intel HD Graphics 5500 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0
    Device-2: NVIDIA GK208BM [GeForce 920M] vendor: Dell driver: N/A bus ID: 08:00.0
    Display: server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa resolution: 1366×768~60Hz
    OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 20.3.4 direct render: Yes
    Audio: Device-1: Intel Broadwell-U Audio vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:03.0
    Device-2: Intel Wildcat Point-LP High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:1b.0
    Sound Server: ALSA v: k4.9.0-264-antix.1-amd64-smp
    Network: Device-1: Intel Wireless 3160 driver: iwlwifi v: kernel port: f040 bus ID: 06:00.0
    IF: wlan0 state: up mac: <filter>
    Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: 2.3LK-NAPI port: e000
    bus ID: 07:00.0
    IF: eth0 state: down mac: <filter>
    Drives: Local Storage: total: 960.15 GiB used: 1.44 GiB (0.2%)
    ID-1: /dev/sda vendor: Seagate model: ST1000LM024 HN-M101MBB size: 931.51 GiB
    ID-2: /dev/sdb type: USB vendor: SanDisk model: Ultra size: 28.64 GiB
    Partition: ID-1: / size: 6.16 GiB used: 50.8 MiB (0.8%) fs: overlay source: ERR-102
    ID-2: swap-1 size: 7.91 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
    Sensors: System Temperatures: cpu: 61.0 C mobo: N/A sodimm: 40.0 C
    Fan Speeds (RPM): cpu: 0 fan-2: 0 fan-3: 0
    Info: Processes: 181 Uptime: 17m Memory: 7.77 GiB used: 560.3 MiB (7.0%) Init: runit runlevel: 2 Compilers: gcc: 10.2.1
    Shell: bash v: 5.1.4 inxi: 3.0.36

    No issues found with this today. Since we have newer images, I’ll either update an installed instance or download and test a newer live instance.

    Brian Masinick

    #63039
    Moderator
    Brian Masinick
    Helpful
    Up
    0

    I downloaded the image again and other than a few updates, everything is the same.

    I’ve been mostly testing installed versions; today I tried both installed and live instances. I’ve used the vmlinuz-4.9.0-264-antix.1-amd64-smp image, the vmlinuz-5.10.0-7-amd64 image, the vmlinuz-5.12.0-10.2-liquorix-amd64 and also the 5.10.*.27* amd64 image. At the moment I’m using an installed liquorix image.

    I’m running on an updated antiX runit image that originally came from the a2 testing, but I’ve been updating the software all along. This too is functioning fine.
    I’ve also experimented with zzzFM, which works great and slimski, which also works quite well. I haven’t fixed the slimski login screen with the most up-to-date improvements, but other than that, the functionality is excellent.

    I’ve tried running the test releases in both runit and sysvinit form; both are working well. I haven’t personally experienced the few issues that have been mentioned elsewhere in this thread, but frankly I use mostly Web browsing, simple commands, and occasionally file managers and alternative browsers; no issues with any of them for me.

    • This reply was modified 1 week, 5 days ago by Brian Masinick.

    Brian Masinick

    #63419
    Member
    calciumsodium
    Helpful
    Up
    0

    I have been testing antix-bullseye-b1 (sysvinit) using the 5.10.27 kernel for a good month on this HP compaq 6200 pro microtower. I am very happy with the performance.

    One thing that I have noticed more and more is that during boot, the computer pauses a good amount when trying to load rsyslogd. Every part of the boot goes very fast, except for this part.

    Is there any reason why it pauses so long at this step on this computer? Is there a way to overcome this?

    $ inxi -Fxz
    System:
      Host: jakersfan Kernel: 5.10.27-antix.1-amd64-smp x86_64 bits: 64 
      compiler: N/A Desktop: IceWM 2.4.0 
      Distro: antiX-bullseye-b1_x64-full Grup Yorum 11 June 2021 
      base: Debian GNU/Linux 11 (bullseye) 
    Machine:
      Type: Desktop System: Hewlett-Packard product: HP Compaq 6200 Pro MT PC 
      v: N/A serial: <filter> 
      Mobo: Hewlett-Packard model: 1497 serial: <filter> UEFI: Hewlett-Packard 
      v: J01 v02.15 date: 11/10/2011 
    CPU:
      Topology: Quad Core model: Intel Core i5-2400 bits: 64 type: MCP 
      arch: Sandy Bridge rev: 7 L2 cache: 6144 KiB 
      flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 24748 
      Speed: 2890 MHz min/max: 1600/3400 MHz Core speeds (MHz): 1: 2258 2: 3293 
      3: 2087 4: 3293 
    Graphics:
      Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics 
      vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 
      Display: x11 server: X.Org 1.20.11 driver: modesetting 
      unloaded: fbdev,vesa resolution: 1920x1080~60Hz 
      OpenGL: renderer: Mesa DRI Intel HD Graphics 2000 (SNB GT1) 
      v: 3.3 Mesa 20.3.4 direct render: Yes 
    Audio:
      Device-1: Intel 6 Series/C200 Series Family High Definition Audio 
      vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
      Sound Server: ALSA v: k5.10.27-antix.1-amd64-smp 
    Network:
      Device-1: Intel 82579LM Gigabit Network vendor: Hewlett-Packard 
      driver: e1000e v: kernel port: f060 bus ID: 00:19.0 
      IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
    Drives:
      Local Storage: total: 1.14 TiB used: 7.18 GiB (0.6%) 
      ID-1: /dev/sda vendor: Western Digital model: WD2500AAKX-603CA0 
      size: 232.89 GiB 
      ID-2: /dev/sdb vendor: Seagate model: ST1000DM003-1SB102 size: 931.51 GiB 
    Partition:
      ID-1: / size: 82.57 GiB used: 7.16 GiB (8.7%) fs: ext4 dev: /dev/sda5 
      ID-2: swap-1 size: 1.95 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda6 
    Sensors:
      System Temperatures: cpu: 28.0 C mobo: N/A 
      Fan Speeds (RPM): N/A 
    Info:
      Processes: 143 Uptime: 13m Memory: 7.66 GiB used: 449.5 MiB (5.7%) 
      Init: SysVinit runlevel: 5 Compilers: gcc: 10.2.1 Shell: bash v: 5.1.4 
      inxi: 3.0.36 
    
    #63425
    Moderator
    christophe
    Helpful
    Up
    0

    Also, on Legacy Boot, F8 menu (save boot changes) selecting the legacy kernel doesn’t work (at least on my tests). Could anyone else check if this also happens to them?

    I see that (on my system) the F8 menu saves the changes to Grub menu, but the syslinux/isolinux doesn’t remember them.

    I am experiencing this also when booting from live-USB & frugal-from-USB via F5 key. F8 does not save as expected, using syslinux/isolinux, with legacy bios. This is testing on bare metal, not VM.

    #63426
    Member
    vitforlinux
    Helpful
    Up
    0

    Linux kernel 5.10 and newest dont works good with vga Intel i915, like in my laptop, problem experienced also in Manjaro.
    I prefer old kernels pre 5.4 like fastest Antix 4.9 or Debian 10 standard 4.19

    Sorry for my spaghetti english, i'm italian.

    #63429
    Member
    calciumsodium
    Helpful
    Up
    0

    After reading @vitforlinux ‘s experience with the vga Intel i915, I switched from the 5.10.27 kernel to the 4.19.184 kernel and I still get the long rsyslogd pause during boot that I observed with the 5.10.27 kernel in the antix-bullseye-b1 on this HP compaq 6200 pro microtower.

    Then I switched to down to the 4.9.0-264 kernel, and a night and day difference. The boot was so fast compared to the other two kernels mentioned above. The boot went by the rsyslogd really quickly. That solves the problem. Even though there is a fast processor on this HP, the i915 graphics is limited to the legacy 4.9 kernel.

    Thank you @vitforlinux for sharing your experience so that I can solve my problem.
    Thanks.

Viewing 15 posts - 121 through 135 (of 136 total)
  • You must be logged in to reply to this topic.