ok now for the results of my tests.
Machine DellD620. 512meg ram.
Booted with unetbootin - Had gfxboot C32 not a com32r image. When first booting into Icewm no mouse pointer is seen so CTRL ALT BACKSPACE
and booted into JWM desktop and everything was fine.
Wireless working - as are videoplayback and sound.
topic title: antiX-16-b1-full available for testing
-
Posts: 148
- Joined: 21 Apr 2011
#32
I'm perfectly happy with the somewhat stark appearance of minstall versus other distros bling; it sets us apart. If a change had to be made, I believe it should just be something like a coloured gradient.
Chris
I'm pretty sure I will be in a minority of one, but I don't like having the image in the installer pane. It's distracting, and to my tastes looks a mess.anticapitalista wrote:A question to those who have already used the installer.
Did adding a bit of colour and an image in the left pane cause any issues with visibility of the text?
Is it worth exploring 'prettyfying' the installer further or should we revert back to the 'dull' grey?
I'm perfectly happy with the somewhat stark appearance of minstall versus other distros bling; it sets us apart. If a change had to be made, I believe it should just be something like a coloured gradient.
Chris
-
Posts: 452
- Joined: 12 Sep 2007
#33
I argued for a gradient in the original MX thread, from the perspective of transportability. Transparency is equally stable, but I am also not a particular fan.
-
Posts: 1,028
- Joined: 21 Aug 2011
#34
Using transparency hinders all the above. It invariably reduces the contrast between the foreground text and the background image. There is a danger that using a colour gradient will also produce the same unwanted effect.
The solid (non gradient) colour used in antiX-16b1 is a good example of having high contrast easy to read areas.
Stick with either the vanilla scheme or replace all transparent items with the single, solid colour used in 16b1.
In essence, the plainer the better. Those with less than perfect eyesight will be grateful for the thoughtfulness.
The installer is a critically important item of the distro. It should be as clear, self evident, and easy to read as possible. If it fails in those all is lost.anticapitalista wrote:Did adding a bit of colour and an image in the left pane cause any issues with visibility of the text?
Is it worth exploring 'prettyfying' the installer further or should we revert back to the 'dull' grey?
Using transparency hinders all the above. It invariably reduces the contrast between the foreground text and the background image. There is a danger that using a colour gradient will also produce the same unwanted effect.
The solid (non gradient) colour used in antiX-16b1 is a good example of having high contrast easy to read areas.
Stick with either the vanilla scheme or replace all transparent items with the single, solid colour used in 16b1.
In essence, the plainer the better. Those with less than perfect eyesight will be grateful for the thoughtfulness.
-
Posts: 94
- Joined: 23 Apr 2014
#35
Running from live cd while preparing for install. Slow booting but all basics working ootb once it got to a desktop.
Code: Select all
demo@antix1:~
$ inxi -Fxx
System: Host: antix1 Kernel: 4.4.2-antix.2-amd64-smp x86_64 (64 bit gcc: 4.9.3)
Desktop: IceWM 1.3.8 dm: slim
Distro: antiX-16-b1_x64-full Berta Cáceres 11 April 2016
Machine: Mobo: ASUSTeK model: M5A97 LE R2.0 v: Rev 1.xx
Bios: American Megatrends v: 2601 date: 03/24/2015
CPU: Hexa core AMD FX-6300 Six-Core (-MCP-) cache: 12288 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 42138
clock speeds: min/max: 1400/3500 MHz 1: 2000 MHz 2: 2500 MHz
3: 3000 MHz 4: 2000 MHz 5: 2500 MHz 6: 1400 MHz
Graphics: Card: NVIDIA GT218 [GeForce 210] bus-ID: 01:00.0 chip-ID: 10de:0a65
Display Server: X.Org 1.16.4 drivers: nouveau (unloaded: fbdev,vesa)
Resolution: 1440x900@59.89hz
GLX Renderer: Gallium 0.4 on NVA8
GLX Version: 3.0 Mesa 10.3.2 Direct Rendering: Yes
Audio: Card-1 NVIDIA High Definition Audio Controller
driver: snd_hda_intel bus-ID: 01:00.1 chip-ID: 10de:0be3
Card-2 Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA)
driver: snd_hda_intel bus-ID: 00:14.2 chip-ID: 1002:4383
Sound: ALSA v: k4.4.2-antix.2-amd64-smp
Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
driver: r8169 v: 2.3LK-NAPI port: d000
bus-ID: 02:00.0 chip-ID: 10ec:8168
IF: eth0 state: up speed: 100 Mbps duplex: full
mac: 1c:87:2c:5a:bb:e2
Drives: HDD Total Size: 1120.2GB (0.7% used)
ID-1: /dev/sda model: KINGSTON_SV300S3 size: 120.0GB serial: 50026B7256076A16
ID-2: /dev/sdb model: WDC_WD10EZEX size: 1000.2GB serial: WD-WCC3F6XAKRLY
Partition: ID-1: / size: 13G used: 20M (1%) fs: overlay dev: N/A
ID-2: swap-1 size: 8.60GB used: 0.00GB (0%) fs: swap dev: /dev/sdb5
Sensors: System Temperatures: cpu: 17.9C mobo: N/A gpu: 34.0
Fan Speeds (in rpm): cpu: 0
Info: Processes: 182 Uptime: 11 min Memory: 284.0/15953.0MB
Init: SysVinit v: 2.88 runlevel: 5 default: 5 Gcc sys: 4.9.2
Client: Shell (bash 4.3.301 running in roxterm) inxi: 2.2.31
demo@antix1:~
-
Posts: 94
- Joined: 23 Apr 2014
#36
Install complete. No problems other than have already been mentioned.
Updated and installed several packages thru Synaptic.Switched to JWM/Rox.
On to more testing.
Updated and installed several packages thru Synaptic.Switched to JWM/Rox.
On to more testing.
Code: Select all
james@antix1:~
$ free
total used free shared buffers cached
Mem: 16335896 1246204 15089692 8096 44336 826388
-/+ buffers/cache: 375480 15960416
Swap: 8396796 0 8396796
-
Posts: 98
- Joined: 29 Jan 2016
#37
hello anticapitalista and everyone
The 16b1 Using the 64 bit iso had first time success at each step download, create media, power-on live and success first time with everything, used wicd. almost a sure bet trialing it live on this asus desktop that has been running hdd antix-15 lately. Liked new the image in the installer matching wallpaper; class act that installer; top of the industry that installer. for now live here:
the 64 bit is success and simple. using space-fluxbox, style=sleek2flux. liking the Royal-blue antix too.
The 16b1 Using the 64 bit iso had first time success at each step download, create media, power-on live and success first time with everything, used wicd. almost a sure bet trialing it live on this asus desktop that has been running hdd antix-15 lately. Liked new the image in the installer matching wallpaper; class act that installer; top of the industry that installer. for now live here:
Code: Select all
System: Host: antix1 Kernel: 4.4.2-antix.2-amd64-smp x86_64 (64 bit gcc: 4.9.3)
Desktop: Fluxbox 1.3.5 dm: slim
Distro: antiX-16-b1_x64-full Berta Cáceres 11 April 2016
Machine: Mobo: ASUSTeK model: P5L8L-SE v: Rev 1.xx
Bios: American Megatrends v: 0201 date: 10/09/2007
CPU: Single core Intel Pentium 4 (-HT-) cache: 2048 KB bmips: 6800
clock speeds: max: 3400 MHz 1: 3400 MHz 2: 3400 MHz
CPU Flags: acpi apic bts cid clflush cmov constant_tsc cx16 cx8 de ds_cpl
dtes64 dts est fpu fxsr ht lahf_lm lm mca mce mmx monitor msr mtrr nopl nx
pae pat pbe pdcm pebs pge pni pse pse36 sep ss sse sse2 syscall tm tm2 tsc
vme xtpr
Graphics: Card: Intel 82945G/GZ Integrated Graphics Controller
bus-ID: 00:02.0 chip-ID: 8086:2772
Display Server: X.Org 1.16.4 drivers: intel (unloaded: fbdev,vesa)
Resolution: 1440x900@59.89hz
GLX Renderer: Mesa DRI Intel 945G
GLX Version: 2.1 Mesa 10.3.2 Direct Rendering: Yes
Audio: Card Intel NM10/ICH7 Family High Definition Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:27d8
Sound: Advanced Linux Sound Architecture v: k4.4.2-antix.2-amd64-smp
Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
driver: r8169 v: 2.3LK-NAPI port: e800 bus-ID: 02:00.0 chip-ID: 10ec:8168
IF: eth0 state: down mac: <filter>
Card-2: Realtek RTL8191SU 802.11n WLAN Adapter
driver: r8712u usb-ID: 001-003 chip-ID: 0bda:8172
IF: wlan0 state: N/A mac: N/A
Drives: HDD Total Size: 172.5GB (1.6% used)
ID-1: /dev/sda model: WDC_WD1600YS size: 164.7GB serial: WD-WCAP03388050
ID-2: USB /dev/sdb model: DataTraveler_SE9 size: 7.8GB serial: 00187D0F5672EC70500055E0-0:0
Partition: ID-1: / size: 1.6G used: 203M (13%) fs: overlay dev: N/A
ID-2: swap-1 size: 2.18GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
Sensors: System Temperatures: cpu: 39.0C mobo: 46.0C
Fan Speeds (in rpm): cpu: 1102 sys-1: 0
Info: Processes: 125 Uptime: 44 min Memory: 150.9/1994.9MB
Init: SysVinit v: 2.88 runlevel: 5 default: 5 Gcc sys: 4.9.2
Client: Shell (bash 4.3.301 running in roxterm) inxi: 2.2.31
-
Posts: 148
- Joined: 21 Apr 2011
#38
I discovered desktop-defaults-set by accident. It's pretty neat, and appears functional. There doesn't seem to be a way to run it from the menu or control centre - will that be included in final?
Chris
Chris
-
Posts: 1,028
SamK - Joined: 21 Aug 2011
#39
On a more general idea...
If you want an item in the menu Control Center-->Menu Manager will help ypu put one in the Personal Menu.
Try Control Center-->Preferred Applicationschrispop99 wrote:I discovered desktop-defaults-set by accident. It's pretty neat, and appears functional. There doesn't seem to be a way to run it from the menu or control centre - will that be included in final?
On a more general idea...
If you want an item in the menu Control Center-->Menu Manager will help ypu put one in the Personal Menu.
-
Posts: 148
- Joined: 21 Apr 2011
#40
Chris
Thank you - how on earth did I miss that???SamK wrote:Try Control Center-->Preferred Applicationschrispop99 wrote:I discovered desktop-defaults-set by accident. It's pretty neat, and appears functional. There doesn't seem to be a way to run it from the menu or control centre - will that be included in final?
On a more general idea...
If you want an item in the menu Control Center-->Menu Manager will help ypu put one in the Personal Menu.
Chris
-
Posts: 148
- Joined: 21 Apr 2011
#41
After connecting wirelessly using wicd, a tray icon is shown.
If the option in wicd to 'Automatically connect to this network' is selected, connection occurs OK after reboot, but there is no tray icon shown.
Is there any way to have the tray icon appear every boot if a connection is made?
Chris
If the option in wicd to 'Automatically connect to this network' is selected, connection occurs OK after reboot, but there is no tray icon shown.
Is there any way to have the tray icon appear every boot if a connection is made?
Chris
-
Posts: 2,238
- Joined: 16 Dec 2007
#42
wicd-client -t
to your startup file of choice.
yes, addchrispop99 wrote:After connecting wirelessly using wicd, a tray icon is shown.
If the option in wicd to 'Automatically connect to this network' is selected, connection occurs OK after reboot, but there is no tray icon shown.
Is there any way to have the tray icon appear every boot if a connection is made?
Chris
wicd-client -t
to your startup file of choice.
-
Posts: 1,028
- Joined: 21 Aug 2011
#43
Its on its way back. It will just need to be uncommented in the start up file.
post46272.html?hilit=wicd%20client#p46272
Edit
Cross post with dolphin_oracle. He types faster than me.
It used to be present in the shipped ISO but was missed in antiX-15.chrispop99 wrote:After connecting wirelessly using wicd, a tray icon is shown.
[...]
Is there any way to have the tray icon appear every boot if a connection is made?
Its on its way back. It will just need to be uncommented in the start up file.
post46272.html?hilit=wicd%20client#p46272
Edit
Cross post with dolphin_oracle. He types faster than me.
-
Posts: 148
- Joined: 21 Apr 2011
#44
Thank you both.
Chris
Chris
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#45
Request to test out the following.
1. Test save_state on fat32 usb stick running live.
Just make a fat32 liveUSB. Use"db+" cheat so you can catch error
messages on shutdown. See if there are extraneous error messages
associated with saving state at shutdown or start up. Boot it
twice to be sure. Some may only show up on first or second boot.
Should savestate be less chatty by default?
2. Test UEFI chainload to Windows
If you boot Live via UEFI, does the"Windows" boot entry show
up? If so, does it work?
1. Test save_state on fat32 usb stick running live.
Just make a fat32 liveUSB. Use"db+" cheat so you can catch error
messages on shutdown. See if there are extraneous error messages
associated with saving state at shutdown or start up. Boot it
twice to be sure. Some may only show up on first or second boot.
Should savestate be less chatty by default?
2. Test UEFI chainload to Windows
If you boot Live via UEFI, does the"Windows" boot entry show
up? If so, does it work?