AntiX 15 b3-V - Page 13

skidoo · posted: 2015-06-14 05:24

iso-snapshot

isosnapshot.ui
line 276
<string>You can also exclude certain directories by ticking the common choices below, or by clicking on the button to directly edit /usr/lib/iso-snapshot/snapshot-exclude.list.</string>

? add a symlink there, in order to reconcile the onscreen help with the actual antix path
(From memory, clicking when the app offered/prompted to do so does, in fact, open the correct file in (?leadpad?geany) for editing.)

wishlist item: Within the runtime workflow, similarly prompt/offer user an opportunity to edit"initrd-modules.list"

couldn't locate it in the code, but from my notes:
typo/omission"Creating 4.0 filesystem..."
(apparently, it should be"ext 4.0 filesystem") (does it matter? pRoBaBlY nOt)

SamK

Re: sisimedia failure to load

BitJam wrote:... boot with the"load=all" option and then attach (or send me) the /var/log/live/initrd.log file...

Attached as requested.

SamK · posted: 2015-06-14 10:32

Re: sisimedia failure to load

BitJam wrote:...if you are running a LiveUSB you can add this option to your bootloader by editing the file /live/boot-dev/boot/syslinux/options.men. Add a line like this:
Code: Select all
sis graphics    `xorg=sisimedia

Confirming OK.

GRUB boot screen-->F4 Options-->sis graphics
Boots to GUI (X) desktop via sisimedia

Presumably this is what was meant by this comment

anticapitalista wrote:Excellent! So it does work, but not automatically. I guess having F4 SIS option might be useful

I am approaching this matter from the perspective of a user who might be new to antiX who possess limited technical skills and abilities. The above procedure is highly likely to be beyond their appreciation even if they knew how to access the information to attempt it.

Until the sisimedia driver can be automatically loaded by antiX, the most user friendly way to handle this is for antiX to ship with the above built in to the ISO. It is not ideal but it is probably the best compromise in the current circumstances. Hopefully an automated loading will mean it can eventually be removed.

BitJam wrote:To make F8-Save work with this entry, you will also have to edit the gfxsave.cfg file...

I did not test this. Here antiX live is used almost exclusively as an installation tool, and never as a day-to-day working environment.

SamK · posted: 2015-06-14 11:00

search-bar-icon

This is either started automatically or not started at all depending on the desktop that is used. When it is started, it can be closed via the quit option (right click on icon).

Once it is closed, or when it has not been started, there is no way to invoke it from the menu.

A .desktop launcher will complement the utility and make it easier for a user to control.

skidoo · posted: 2015-06-14 19:43

/usr/local/bin/persist-save
Semi-automatic mode is offered, and is used, because the user may sometimes/often wish the session changes to NOT persist.
Currently, the script forces the user to wait while it performs checks... prior to offering an opportunity to choose"no".
I've modded my installed copy of the script so that it accommodates"no" w/o unnecessary wait ~~ without ill side effects (AFAIK).
If this change isn't safe/wise, please lemme know. If you agree that it is safe, please consider adding this early noisy_yes_no_box to the distributed script.

Code: Select all

main()
. . .
    start_logging   {------- LINE 40 ----------

    noisy_yes_no_box                              \
       "$(gt"Shall we begin?")"                 \
        || vexit"Stopping at user's request"

    trap clean_up EXIT

The text"Shall we begin" displays in a dialogbox titled"antiX Save Peresistent Root".
Perhaps a bit terse, but it should suffice, and avoids the introduction of yet-another translatable string (same string is already used elsewher in the script).

SamK · posted: 2015-06-15 17:58

Clock in Taskbar IceWM

Booted live with persistence

When the bootup completes the clock is frozen at +1 hour ahead of local time.
It remains in this frozen state (no increments for minutes) until IceWM is restarted via menu-->Logout-->Restart IceWM
Wheh the restart of the WM has completed the fault is corrected,the clock is synchronised to the correct local time and advances in the expected manner.

anticapitalista · posted: 2015-06-15 21:38

SamK wrote:Clock in Taskbar IceWM

Booted live with persistence

When the bootup completes the clock is frozen at +1 hour ahead of local time.
It remains in this frozen state (no increments for minutes) until IceWM is restarted via menu-->Logout-->Restart IceWM
Wheh the restart of the WM has completed the fault is corrected,the clock is synchronised to the correct local time and advances in the expected manner.

You have mentioned this before IIRC and IIRC others who responded do not see this (including me). Maybe it is due to the (old) hardware needing a longer sleep time to start the wm and desktop apps. Whether we like it or not, jessie base is quite a bit heavier than wheezy.

BitJam · posted: 2015-06-15 21:52

skidoo wrote:/usr/local/bin/persist-save
Semi-automatic mode is offered, and is used, because the user may sometimes/often wish the session changes to NOT persist.
Currently, the script forces the user to wait while it performs checks... prior to offering an opportunity to choose"no".
I've modded my installed copy of the script so that it accommodates"no" w/o unnecessary wait ~~ without ill side effects (AFAIK).

Thanks! Good idea. I will make the change. So you think the user should be asked twice? In my test that wait is very short but if it is long I can see why you would want to short-circuit it.

PS: You can test my/your change by downloading persist-save from here:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://github.com/BitJam/Persist-Scripts/tree/master/bin"
linktext was:"https://github.com/BitJam/Persist-Scrip ... master/bin"
====================================

BitJam · posted: 2015-06-15 23:26

SamK wrote:search-bar-icon

This is either started automatically or not started at all depending on the desktop that is used. When it is started, it can be closed via the quit option (right click on icon).

Once it is closed, or when it has not been started, there is no way to invoke it from the menu.

A .desktop launcher will complement the utility and make it easier for a user to control.

Thanks! I added a .desktop file for search-bar and for search-bar-icon.

I've attached a screen shot of what the search-bar app looks like. I have two monitors and I have a search-bar on each one. I turn the window border off. I use them constantly. Of course YMMVG.

dolphin_oracle · posted: 2015-06-15 23:37

old sony install. the ram usage while running iceweasel with one tab is about 170mb.

Code: Select all

dolphin@oldsony:~
$ inxi -F
System:    Host: oldsony Kernel: 4.0.0-antix.1-486-smp i686 (32 bit)
           Desktop: IceWM 1.3.8
           Distro: antiX-15-beta3-V_386-full Killah P 31 May 2015
Machine:   System: Sony product: PCG-FXA32(UC) v: 01
           Mobo: Sony model: Q3-Project v: 1A
           Bios: Sony v: R0107K5 date: 09/17/2001
CPU:       Single core AMD Duron (-UP-) cache: 64 KB speed/max: 549/899 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Rage Mobility AGP 2x Series
           Display Server: X.Org 1.16.4 driver: vesa
           Resolution: 1024x768@61.00hz
           GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits)
           GLX Version: 3.0 Mesa 10.3.2
Audio:     Card VIA VT82C686 AC97 Audio Controller driver: snd_via82xx
           Sound: Advanced Linux Sound Architecture v: k4.0.0-antix.1-486-smp
Network:   Card-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
           driver: 8139too
           IF: eth0 state: down mac: 08:00:46:2f:ab:44
           Card-2: Ralink RT2561/RT61 802.11g PCI driver: rt61pci
           IF: wlan0 state: up mac: 00:11:50:dc:46:66
Drives:    HDD Total Size: 15.1GB (23.6% used)
           ID-1: /dev/sda model: HITACHI_DK23CA size: 15.1GB
Partition: ID-1: / size: 3.9G used: 2.4G (65%) fs: ext3 dev: /dev/sda1
           ID-2: swap-1 size: 1.07GB used: 0.00GB (0%) fs: swap dev: /dev/sda6
Sensors:   System Temperatures: cpu: 24.2C mobo: 24.2C
           Fan Speeds (in rpm): cpu: 0 fan-2: 0
Info:      Processes: 93 Uptime: 1 min Memory: 75.4/498.3MB
           Client: Shell (bash) inxi: 2.2.16 
dolphin@oldsony:~

dolphin_oracle · posted: 2015-06-15 23:43

same old sony install. I noticed that the inxi output above said I was using the vesa driver. This was unplanned. So I checked and sure enough there was an xorg.conf file left over from somwhere. deleted that and got an ati driver (but not the mach64 driver, which I think is what got used in earlier antiX's).

Code: Select all

dolphin@oldsony:~
$ inxi -F
System:    Host: oldsony Kernel: 4.0.0-antix.1-486-smp i686 (32 bit)
           Desktop: IceWM 1.3.8
           Distro: antiX-15-beta3-V_386-full Killah P 31 May 2015
Machine:   System: Sony product: PCG-FXA32(UC) v: 01
           Mobo: Sony model: Q3-Project v: 1A
           Bios: Sony v: R0107K5 date: 09/17/2001
CPU:       Single core AMD Duron (-UP-) cache: 64 KB speed/max: 550/900 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Rage Mobility AGP 2x Series
           Display Server: X.Org 1.16.4 drivers: ati (unloaded: fbdev,vesa) FAILED: mach64
           Resolution: 1024x768@87.00hz
           GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits)
           GLX Version: 3.0 Mesa 10.3.2
Audio:     Card VIA VT82C686 AC97 Audio Controller driver: snd_via82xx
           Sound: Advanced Linux Sound Architecture v: k4.0.0-antix.1-486-smp
Network:   Card-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
           driver: 8139too
           IF: eth0 state: down mac: 08:00:46:2f:ab:44
           Card-2: Ralink RT2561/RT61 802.11g PCI driver: rt61pci
           IF: wlan0 state: up mac: 00:11:50:dc:46:66
Drives:    HDD Total Size: 15.1GB (23.6% used)
           ID-1: /dev/sda model: HITACHI_DK23CA size: 15.1GB
Partition: ID-1: / size: 3.9G used: 2.4G (65%) fs: ext3 dev: /dev/sda1
           ID-2: swap-1 size: 1.07GB used: 0.00GB (0%) fs: swap dev: /dev/sda6
Sensors:   System Temperatures: cpu: 24.2C mobo: 23.9C
           Fan Speeds (in rpm): cpu: 0 fan-1: 0
Info:      Processes: 96 Uptime: 1 min Memory: 75.4/498.3MB
           Client: Shell (bash) inxi: 2.2.16 
dolphin@oldsony:~
$

masinick · posted: 2015-06-15 23:56

I now have two instances of antiX 15 b3. Here is one of them on the Gateway:

Code: Select all

$ inxi -Fzx
Resuming in non X mode: glxinfo not found. For package install advice run: inxi --recommends
System:    Host: antixCore Kernel: 4.0.0-gnu-antix.1-486-smp i686 (32 bit gcc: 4.9.2) Desktop: IceWM 1.3.8
           Distro: antiX-15-beta3-V_386-core-libre Killah P 1 June 2015
Machine:   System: Gateway product: MX8738 v: 3408450R
           Mobo: Gateway model: N/A v: 72.15 Bios: Phoenix v: 72.15 date: 04/16/2007
CPU:       Dual core Intel T2080 (-MCP-) cache: 1024 KB flags: (nx pae sse sse2 sse3) bmips: 6916 
           clock speeds: max: 1733 MHz 1: 1333 MHz 2: 1333 MHz
Graphics:  Card: Intel Mobile 945GM/GMS 943/940GML Express Integrated Graphics Controller bus-ID: 00:02.0
           Display Server: X.org 1.16.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 177x53
Audio:     Card Intel NM10/ICH7 Family High Definition Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0
           Sound: Advanced Linux Sound Architecture v: k4.0.0-gnu-antix.1-486-smp
Network:   Card-1: Broadcom BCM4311 802.11b/g WLAN driver: b43-pci-bridge bus-ID: 03:00.0
           IF: N/A state: N/A mac: N/A
           Card-2: Intel PRO/100 VE Network Connection driver: e100 v: 3.5.24-k2-NAPI port: 4000 bus-ID: 04:08.0
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 160.0GB (3.4% used) ID-1: /dev/sda model: WDC_WD1600BEVS size: 160.0GB
Partition: ID-1: / size: 13G used: 3.2G (28%) fs: ext4 dev: /dev/sda10
           ID-2: swap-1 size: 2.05GB used: 0.00GB (0%) fs: swap dev: /dev/sda3
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 101 Uptime: 1 min Memory: 62.3/2010.9MB Init: SysVinit runlevel: 5 Gcc sys: N/A
           Client: Shell (bash 4.3.301) inxi:.

BitJam · posted: 2015-06-16 00:21

dolphin_oracle wrote:same old sony install. I noticed that the inxi output above said I was using the vesa driver. This was unplanned. So I checked and sure enough there was an xorg.conf file left over from somwhere. deleted that and got an ati driver (but not the mach64 driver, which I think is what got used in earlier antiX's).

We are now auto-generating an xorg.conf for systems that don't have a KMS video driver. The fact that xorg.conf was auto-generated should be clearly marked in a header like this:

Code: Select all

#----------------------------------------------------------------------
# xorg.conf file
#
# Generated by make-xorg-conf sometime around Mon Jun 15 17:45:31 MDT 2015
#
# If you want to save customizations, delete the line above or this
# file will get automatically deleted on the next live boot.
#----------------------------------------------------------------------

Maybe your machine has a non-KMS video driver(s) that you want to use or we have some other bug.

One difficulty is there are two kinds of drivers: the kernel drivers under /lib/modules/4.0.0-antix.1-486-smp/kernel/drivers/gpu/ and the the xorg modules under /usr/lib/xorg/modules/drivers/. I know how to search for which kernel modules your hardware supports but I don't know how to search for which xorg drivers your hardware supports.

Here is a list of kernel video drivers that AFAIK don't have KMS:

Code: Select all

i810
mga
r128
savage
sil164
sis
tdfx
ttm
via

If you have one of these kernel modules loaded (use lsmod to find out) then we can easily change our code so if the hardware supports any kernel video module then we won't create a default xorg.conf.

I apologize for this seemingly unnecessary complication. It results from us trying to run the latest Xorg on older hardware. For example, the new Xorg works great OOTB when booting via UEFI. But if we want:

To be able to boot via BIOS as well as UEFI, and
Have the xorg fbdev driver present, and
Have decent resolution on the consoles via the framebuffer, and
Have decent resolution in X

Then we have to play this game of detecting video drivers and creating a default xorg.conf if no (KMS) video driver is found. I hope your system has one of the kernel videos drivers in the list above (or maybe even a kernel video driver that didn't make it onto my list of all video drivers). If so, the fix is very easy. We won't make a default xorg.conf if hardware for any kernel video driver is detected.

I do not want to get into a discussion about this strategy. Several of us spent a lot of time and energy to work this out. I don't have the time and energy now to get other people up to speed. The final strategy we were forced to use was not obvious from the start. If you think you could do better please do not post questions or suggestions here. The only question at this point is whether we use only KMS video modules or all video modules to disable the creation of a default xorg.conf. Even if you had a better strategy, we don't have the time to work on it and debug it now.

skidoo · posted: 2015-06-16 01:09

re: persist save
"So you think the user should be asked twice? In my test that wait is very short"

In comparison to waiting (each test.reboot.test session), just being asked twice is a blessing.
Among the (my) variable factors likely affecting delay:
-- the testing PC lacks USB 3.0 ports
-- some of my pendrives are older (Class4)
-- most of my testing pendrives are vfat

The delay becomes more pronounced over time (expected), until I perform a snapshot and move to another pendrive.
Although BitJam explained why vfat is such a comparatively poor choice, I'm still mired in dual-boot winXP usage here.

BitJam · posted: 2015-06-16 01:25

skidoo wrote:just being asked twice is a blessing.

The new version that does this is in the git-hub repo if you want to try it and make sure it works.