Forum › Forums › News › Announcements › antiX-19-b2-full (64 and 32 bit) available
Tagged: 19 b2 install to usb stick
- This topic has 205 replies, 24 voices, and was last updated Aug 21-4:47 pm by rej.
-
AuthorPosts
-
July 13, 2019 at 11:58 am #24423Forum Admin
anticapitalista
Our second beta build of the upcoming antiX-19 release, based on Debian Buster and systemd-free.
Changes since beta1.
* Inclusion of connman-bluetooth-firmware
* New app – App Select – Quickly find all installed apps.
* 4.9.182 ‘Sack Panic’ patched kernel
* New ‘antiX’ category added to menu
* New themes, icons and wallpaper
* Various bugfixes.For a full list of what is on antiX-19, see this post.
antix-19-b1-full-64-and-32-bit-available
isos, zsync and xdelta patches here
- This topic was modified 1 year, 6 months ago by anticapitalista.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
July 13, 2019 at 12:08 pm #24425Moderatorfatmac
Thanks, anti & team, downloading now. 🙂
Linux (& BSD) since 1999
July 13, 2019 at 3:16 pm #24428ModeratorBobC
Hi anti, I got my Dual P III 750 running on the 32 bit version.
I’ve noticed lots of good fixes. I was able to connect to WiFi by going to the Control Centre, Network tab and WiFi Connect. No issues there now. The only suggestion I would add there would be if there is no connection when it comes up, bring up Connman to offer to connect.
IceWM WinArrange now working, CPU and Network Monitors working. Conky and Xorg and IceWm all combined under 1% CPU,. Calcurse appointment calendar working on clock click. Connman working on Network click.
LxTask didn’t get installed, so we either need to change the CPU click back to HTop or include LxTask in full and base. I installed it and if installed it works on CPU click.
FireFox is slow to write to the screen on this old thing, but I doubt there is much we can do about that other than run something else.
I liked the new boot. On older machines that should speed up the boot process.
Its looking quite good. I will try the 64 bit on my main system next…
THANKS EVERYONE!
PS: We should assign a key for App-Select. I assigned it to Ctrl+Space and even running from DVD it comes up quick after the first time, and worked like I would expect. Great job Dave!
July 13, 2019 at 4:06 pm #24429Memberentropyfoe
For my main problem, the same as beta1 – no sound.
This is working out of the box on MX -18 and antix 16,17.
Still in the live session on USB,The sound test in the control center hardware section just flashes by in less than a second.
Then if I edit /etc/asound.conf, un-commenting and changing the 0 to 1:# ***** Defaults *******************************************************
# Audio card/chip and device to use and control
# In most cases these settings should remain commented (#)
# When commented, card and device 0 are usually automatically selected
# When uncommented, the item corresponding to the number is selected
defaults.pcm.card 1
defaults.pcm.device 1
defaults.ctl.card 1Then the sound test shows the tones and channels on the terminal, but there is no sound from the speaker.
I tried the also mixer next,
It shows correctly
Card HD-Audio Generic
Chip Realtek GenericAll the slider are up with numbers 97, 94, 88, 100 ….
inxi -FAudio: Device-1: NVIDIA GK208 HDMI/DP Audio driver: snd_hda_intel Device-2: AMD Family 17h HD Audio driver: snd_hda_intel Sound Server: ALSA v: k4.9.182-antix.1-amd64-smp
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 soundJuly 13, 2019 at 4:30 pm #24430Memberskidoo
this post contains feedback regarding the a19beta2 liveboot help menu
F1: —} : General Help
———————————–
TIP: press [F12] to see all the currently selected boot options
(noted: F12 is unavailable while F1 menu is displpayed)
SUGGEST: this “tip” bears repeating, as a sentence added to
the “save” bullet displayed in the “F8: Save Bootloader Settings” pageF2: Select Language
———————————–
keyboard layout and timezone. —} timezone and keyboard layout.
-=-
The default language is American English.
lang=[en_US] {— consider inserting a line showing the associated default lang codeF3: Select Timezone
———————————–
[^ ]The menu is an easy {— superfluous beginning-of-line spaceF4: Miscellaneious Options
———————————–
You can select only one of these options.
^—> You can select only one of these options via the popup menu.
SUGGEST
move the hwclock= lines to the end of the list (unseen unless page is scrolled)
to shift the other, arguably more important, items into immediate viewF5: Persist Details
———————————–
SUGGEST
add an additional bullet item ‘OFF’ to the tailend of the page
explaining that during any given boot session, “off” can be selected in order to forego persistence (ala TailsLinux)F5 (and elsewhere):
file-system —} filesystemF7:
wide screen —} widescreen
Virtual Box —} VirtualBoxF6: Select Desktop Program
———————————–
There is also the option to set the font-size.
^—v
{b}F6{/b} also includes options to set TTY console font size.F8: Save Bootloader Settings
———————————–
(as suggested earlier in this post)
TIP: prior to saving, you can press [F12] to see all the currently selected boot options..
v— is this a newly-added feature?
pressing ESC when F1 nor any popups active, raises a Cancel/Halt/Reboot popup___________________________________________
When requesting help, pasting the output from inxi -Fxr command will provide important relevant details:
antiX version//edition ~~ stable vs testing repos ~~ live vs installed vs virtualbox ~~ hardware specsJuly 13, 2019 at 4:43 pm #24431Memberskidoo
The sound test in the control center hardware section just flashes by in less than a second
(scusa if already mentioned in prior topics and I didn’t notice)
The launchstring for “Test Sound” item seen in controlCenter is
urxvt -e speaker-test –channels 2 –test wav –nloops 3Have you tried executing that command from terminal, to check for any error messages displayed?
Hmm, unsure whether this matters, but I noticed that the package libpulse0
in antiX17 was an “0nosystemd” version… but plain ol’ v12 (from debian repository) is present in antiX19_beta2___________________________________________
When requesting help, pasting the output from inxi -Fxr command will provide important relevant details:
antiX version//edition ~~ stable vs testing repos ~~ live vs installed vs virtualbox ~~ hardware specsJuly 13, 2019 at 6:38 pm #24435Memberentropyfoe
From the b1 section over on the MX linux forum: antiX-19-b1-full64 -feedback
https://forum.mxlinux.org/viewtopic.php?f=40&t=50923&start=90#p514563#99
Post by entropyfoe » 11 Jul 2019 20:52
The beta1 is fast running from USB and installing.In the installer, I think the grub options, at least on my machine/USB, come up too soon, while it is installing, causing the user (me) to think it was going to install to mbr.
This would be over my day-to -ay MX 18.3 install. So I aborted and restarted. It should show after the install progress bar stops moving, at least that’s how I remember it. The grub is after the installation, right?As noted above, in the live toram did not work
The nvidia installer in the control panel did not work because ddm-mx was not installed. (This may have been fixed as synaptic installed it upon my reinstall)
My biggest problem is no sound. I tried many things, got advice from the oracle, anti, antix-Dave.
I read a detailed Arch manual page, I could not make it work. I tried a reinstalling. My only clue comes from an inxi-F from the beta and the working mx-18.From the beta1
Audio:
Device-1: NVIDIA GK208 HDMI/DP Audio driver: snd_hda_intel
Device-2: AMD Family 17h HD Audio driver: snd_hda_intel
Sound Server: ALSA v: k4.9.176-antix.1-amd64-smpFrom the working mx-18
Audio: Device-1: NVIDIA GK208 HDMI/DP Audio driver: snd_hda_intel
Device-2: AMD driver: snd_hda_intel
Sound Server: ALSA v: k4.19.18-antix.1-amd64-smpInterestingly, the system profiler in mx 18 says only
Multimedia
Audio Adapter HDA-Intel – HDA NVidia
Audio Adapter HDA-Intel – HD-Audio GenericIt is almost like the beta1 in the hardware detection is over detecting or incorrectly detecting the audio hardware on this on board (Asus motherboard) audio chip.
When the Ryzen came out 2 years ago, I think the audio driver was still marginal under linux, and it was antiX 17 I think, where I first tried it , and it just worked ! The reason linux support took so long, is that it was a new audio chip, the The Realtek S1220A. Yet all the above, including on the working mx18, the Realtek is not mentioned, it is called generic or amd, and all use the snd_hda_intel driver.Re: antiX-19-b1-full64 -feedback
#99
Post by entropyfoe » 11 Jul 2019 20:52
The beta1 is fast running from USB and installing.In the installer, I think the grub options, at least on my machine/USB, come up too soon, while it is installing, causing the user (me) to think it was going to install to mbr.
This would be over my day-to -ay MX 18.3 install. So I aborted and restarted. It should show after the install progress bar stops moving, at least that’s how I remember it. The grub is after the installation, right?As noted above, in the live toram did not work
The nvidia installer in the control panel did not work because ddm-mx was not installed. (This may have been fixed as synaptic installed it upon my reinstall)
My biggest problem is no sound. I tried many things, got advice from the oracle, anti, antix-Dave.
I read a detailed Arch manual page, I could not make it work. I tried a reinstalling. My only clue comes from an inxi-F from the beta and the working mx-18.Code: Select all
From the beta1
Audio:
Device-1: NVIDIA GK208 HDMI/DP Audio driver: snd_hda_intel
Device-2: AMD Family 17h HD Audio driver: snd_hda_intel
Sound Server: ALSA v: k4.9.176-antix.1-amd64-smpFrom the working mx-18
Audio: Device-1: NVIDIA GK208 HDMI/DP Audio driver: snd_hda_intel
Device-2: AMD driver: snd_hda_intel
Sound Server: ALSA v: k4.19.18-antix.1-amd64-smpInterestingly, the system profiler in mx 18 says only
Multimedia
Audio Adapter HDA-Intel – HDA NVidia
Audio Adapter HDA-Intel – HD-Audio GenericIt is almost like the beta1 in the hardware detection is over detecting or incorrectly detecting the audio hardware on this on board (Asus motherboard) audio chip.
When the Ryzen came out 2 years ago, I think the audio driver was still marginal under linux, and it was antiX 17 I think, where I first tried it , and it just worked ! The reason linux support took so long, is that it was a new audio chip, the The Realtek S1220A. Yet all the above, including on the working mx18, the Realtek is not mentioned, it is called generic or amd, and all use the snd_hda_intel driver.- This reply was modified 1 year, 6 months ago by entropyfoe. Reason: deleted redundant and updated signature
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 soundJuly 13, 2019 at 6:48 pm #24436Memberskidoo
perhaps intentional, or perhaps overlooked:
Press F1 to select available desktop sessions
text is missing from the SLiM logn screen================================
(testing 64bit beta2, in VirtualBox)
cannot drag-resize the panes of the synaptic package manager UI.
Wondering if it’s an issue related to the default theme, I switched to Adwaita. Same result___________________________________________
When requesting help, pasting the output from inxi -Fxr command will provide important relevant details:
antiX version//edition ~~ stable vs testing repos ~~ live vs installed vs virtualbox ~~ hardware specsJuly 13, 2019 at 7:48 pm #24439Memberskidoo
(same result, tested w/ both iceWM and fluxbox)
When RoxPanel is active, clicking its fileManager or webBrowser icon results in the titlebar of the launched application being hidden, inaccessible, under/behind the RoxPanel.
Toggling the “do not cover panel” preference has no effect toward resolving the problem.
Changing the placement to left-edge (ala MX Linux) isn’t a workable solution b/c the RoxPanel would then partially obscure the iceWM toolbar Menu button.noted: The problem doesn’t occur if those same applications are launched via desktop menu or otherwise.
noted: The problem doesn’t occur if I install my custom version (rox-filer_2.14-ski) into antiX 19.
noted: The problem didn’t occur (neither with stock version, nor my custom version) when using RoxPanel in antiX 17.___________________________________________
When requesting help, pasting the output from inxi -Fxr command will provide important relevant details:
antiX version//edition ~~ stable vs testing repos ~~ live vs installed vs virtualbox ~~ hardware specsJuly 14, 2019 at 12:19 am #24449Memberskidoo
multiple recent inquiries // help requests have indicated “Refresh Menu” would be a preferable label
(to avoid confusion, ambiguity vs the MX panel item related to apt updates)___________________________________________
When requesting help, pasting the output from inxi -Fxr command will provide important relevant details:
antiX version//edition ~~ stable vs testing repos ~~ live vs installed vs virtualbox ~~ hardware specsJuly 14, 2019 at 12:37 am #24450Memberskidoo
The rox-filer package installs html helpdocs locally (en, plus fr and it translated versions).
The menu help link(s) could point to these, rather than leading to the sourceforge -hosted English only webpage.___________________________________________
When requesting help, pasting the output from inxi -Fxr command will provide important relevant details:
antiX version//edition ~~ stable vs testing repos ~~ live vs installed vs virtualbox ~~ hardware specsJuly 14, 2019 at 12:50 am #24451Memberskidoo
(the icewm-common package does install a manual, but it is outdated ~v1.42)
AFAIK, these help links should be updated to:
https://ice-wm.org/manual/
https://ice-wm.org/FAQ/___________________________________________
When requesting help, pasting the output from inxi -Fxr command will provide important relevant details:
antiX version//edition ~~ stable vs testing repos ~~ live vs installed vs virtualbox ~~ hardware specsJuly 14, 2019 at 1:03 am #24452Memberskidoo
EDIT:
When I posted earlier, I had neglected to notice that this menu entry isn’t a “redundant” item.The label (ambiguous with submenu named “Other Desktops”), and its current placement under “accessories”, is unintuitive and fails to convey “hey, let’s run /usr/local/lib/desktop-session/desktop-session-menu-window and see if we can get ya goin’ with yer newly-installed “other” (aka alternative) wm//desktopEnvironment“
- This reply was modified 1 year, 6 months ago by skidoo.
___________________________________________
When requesting help, pasting the output from inxi -Fxr command will provide important relevant details:
antiX version//edition ~~ stable vs testing repos ~~ live vs installed vs virtualbox ~~ hardware specsJuly 14, 2019 at 1:23 am #24453Memberskidoo
Desktop Menu –} Applications –} Preferences
The items “Windows Wireless Drivers” and “Additional Drivers” seem out-of-place here.
The “Software & Updates” item, izzit displayed intentionally? If so, its placement would be more appropriate under “System”, alongside the packageinstaller and synaptic items.
______________________________Desktop Menu –} Applications –} System
headscratch: “ROXTerm” and “Midnight Commander” here, but “RVXT Terminal” is displayed under Accessories
______________________________Desktop Menu –} Help –} antiX
suggest adding a separator after “ROX Manual” and adding items linking to:Announcements ( https://www.antixforum.com/forums/forum/news/announcements/ )
antixforum.com ( https://www.antixforum.com )
https://antixlinux.com/archive/
bug tracker ( https://us-bz3.devzing.com/mx_antix/buglist.cgi?chfield=%5BBug%20creation%5D&chfieldfrom=30d )
MX/antiX Wiki ( https://mxlinux.org/wiki/ )___________________________________________
When requesting help, pasting the output from inxi -Fxr command will provide important relevant details:
antiX version//edition ~~ stable vs testing repos ~~ live vs installed vs virtualbox ~~ hardware specsJuly 14, 2019 at 6:11 am #24454Forum AdminDave
Then if I edit /etc/asound.conf, un-commenting and changing the 0 to 1:
Audio: Device-1: NVIDIA GK208 HDMI/DP Audio driver: snd_hda_intel Device-2: AMD Family 17h HD Audio driver: snd_hda_intel Sound Server: ALSA v: k4.9.182-antix.1-amd64-smp
Did you try select sound card in the control centre?
Also are you meaning to get hdmi audio? If not you probably need to set the asound.conf file to specify card 2 not 1
Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
-
AuthorPosts
- You must be logged in to reply to this topic.