antiX-14R-a4-a5 patch - Page 5

thriftee · posted: 2015-02-03 15:14

I made a 14r5 cd and have my Dual PIII machine running on it, but USB won't work. Look for the word"fail" in the dmesg log. According to the BIOS screen before Grub2, the USB is on Irq 9. I can boot it again on MX14 or any other OS you want if you want to see info from somewhere else.

I posted the machine details and logs here, not realizing at first that it was a 14r5 problem. It works fine with MX14 and Knoppix 7.05

post39411.html#p39411

Other than the USB problem it runs very well on that machine.

rokytnji · posted: 2015-02-03 21:39

Double checked before posting and I still cannot find it.

Where is unmount drive like in Icewm toolbar but in Fluxbox? I could not find a menu entry for that in Fluxbox.

rokytnji · posted: 2015-02-03 22:11

Poking around. I found in rox file manager. If I go into media>my sd card folder

Right click folder and pick eject from rox menu. It gives a failed error, but the sd card folder is gone.
So I am guessing eject worked OK in rox file manager. But someone else might wanna test my findings
in case I am wrong.

I am still talking in Fluxbox.

SamK · posted: 2015-02-07 09:16

antiX-14-a4-R_386-full.iso patched with a4-a5.delta

Tests conducted booting live USB without persistence, selecting CLI install (init 3) in order to use live system in console mode i.e. X is not required nor used.

Test 1
Boot param appended: None
System defaults to using the fall-back of the lowest possible resolution

Code: Select all

inxi -c0 -G
Graphics:  Card: Silicon Integrated Systems [SiS] 65x/M650/740 PCI/AGP VGA Display Adapter
           Display Server: X.org 1.16.2.901 driver: N/A
           tty size: 80x25 Advanced Data: N/A out of X

Although the boot completes successfully the result is pretty much unusable at this resolution.

Test 2
Boot param appended: vga=789 (800x600 lowest resolution given in F1-->F7 Console & Splash)
Boot-up fails. The value is too great for a successful boot to be achieved.

Test 3
Boot param appended: vga=788 (800x600)
System accepts param as valid and uses it

Code: Select all

inxi -c0 -G
Graphics:  Card: Silicon Integrated Systems [SiS] 65x/M650/740 PCI/AGP VGA Display Adapter
           Display Server: X.org 1.16.2.901 driver: N/A
           tty size: 100x37 Advanced Data: N/A for root out of X

The boot completes successfully. The result is an improved display and a usable system is produced at this resolution.

789 v 788
Ostensibly these both produce the same height and width dimensions. The difference is in the colour depth which plays an essential role.

789 uses 24bit colour
788 uses 16bit colour

In most day-to-day circumstances the on-screen results are virtually indistinguishable.

As mentioned in previous posts re resolution, I have used 788 for many years, on a great number (100s?) of systems, and cannot recall an instance where it failed to work. Evidently this is not the case for 789.

Suggestion 1
788 (800x600x16) be adopted as the lowest resolution value in the F1-->F7 list in order to automatically obtain a usable system across the widest range of hardware.

Suggestion 2
The current fall-back resolution is too low to produce a system of any real value or usefulness. 788 (800x600x16) does produce a usable system and should be adopted as the fall-back resolution for antiX. 788 will work on the same number of systems as the current fall-back resolution.

DeepDayze · posted: 2015-02-07 15:04

@Samk, the color depth at a given resolution is constrained by the amount of video RAM in the device, but driver limitations can also constrain the resolution and color depth.

SamK · posted: 2015-02-07 16:25

I'm not sure I fully understand the points you are making, so the following might not hit your mark.

DeepDayze wrote:...driver limitations can also constrain the resolution and color depth.

My understanding is that antiX uses only framebuffer when booting all types of hardware into console only mode. This effectively eliminates the vagaries of ensuring a suitable driver is installed whenever X is used (which is not the case for these tests).

antiX uses framebuffer when booting the test kit

Code: Select all

cat /sys/class/graphics/fb0/virtual_size
800,600

As I mentioned in other posts, it is quite common to find kit that fails to boot using a vga resolution greater than 800x600. This is acknowledged by its inclusion in the console modes available in the antiX live boot screen.

The tests I ran demonstrate the mode is most effective when it is 800x600x16 because this works on a greater range of kit. It is simply a way of avoiding unnecessary failures when following the current guidance by ensuring a usable system is booted in as many cases as possible.

DeepDayze · 07 Feb 2015, 23:07 #67 2015-02-07 23:07

@SamK, you mean booting to a console and not X is where you have the issues?

SamK · posted: 2015-02-08 06:51

DeepDayze wrote:...you mean booting to a console and not X is where you have the issues?

Perhaps you skipped over this part of my post reporting the matter (three posts back on Sat Feb 07).

SamK wrote:Tests conducted booting live USB without persistence, selecting CLI install (init 3) in order to use live system in console mode i.e. X is not required nor used.

The vga=xxx parameter only affects console mode. It is irrelevant to, and does not affect GUI (X-server) mode. However, because antiX boots initially to console and (when a GUI is wanted) subsequently hands over to X, an inappropriate vga=xxx parameter will cause a boot failure in both modes.

DeepDayze · posted: 2015-02-08 15:25

SamK wrote:
DeepDayze wrote:...you mean booting to a console and not X is where you have the issues?
Perhaps you skipped over this part of my post reporting the matter (three posts back on Sat Feb 07).
SamK wrote:Tests conducted booting live USB without persistence, selecting CLI install (init 3) in order to use live system in console mode i.e. X is not required nor used.
The vga=xxx parameter only affects console mode. It is irrelevant to, and does not affect GUI (X-server) mode. However, because antiX boots initially to console and (when a GUI is wanted) subsequently hands over to X, an inappropriate vga=xxx parameter will cause a boot failure in both modes.

OK thanks for the clarification so this vga=xxx parameter could use a tweak to be able to cover more hardware including older machines with limited VRAM.

SamK · posted: 2015-02-09 06:30

antiX-14-a4-R_386-full.iso patched with a4-a5.delta

Test conducted booting live USB without persistence, selecting CLI install (init 3) in order to use live system in console mode i.e. X is not required nor used.

Test
Boot param appended: vga=788 (800x600x16)
System accepts param as valid and uses it
Console decoration is automatically not used on tty1 (ALT+F1)

Code: Select all

inxi -c0 -G
Graphics:  Card: Silicon Integrated Systems [SiS] 65x/M650/740 PCI/AGP VGA Display Adapter
           Display Server: X.org 1.16.2.901 driver: N/A
           tty size: 100x37 Advanced Data: N/A for root out of X

All other consoles (ALT+F2-->F6 inclusive) automatically use console decoration.

Code: Select all

inxi -c0 -G
Graphics:  Card: Silicon Integrated Systems [SiS] 65x/M650/740 PCI/AGP VGA Display Adapter
           Display Server: X.org 1.16.2.901 driver: N/A
           tty size: 95x31 Advanced Data: N/A for root out of X

Note the difference in tty size compared to ALT+F1

Comparing the two results it is evident that there is less than 80% usable screen space when the eye candy decoration is displayed.

In cases where a system must employ a low resolution in order to successfully boot to a usable console, this is a huge reduction and the loss is very obvious. The result is an unnecessary (but enforced) constraint is placed on usability in console mode.

Suggestion
Console decoration be treated consistently for all console screens (tty1-->6 inclusive). It should be an optional feature that the user purposely chooses to switch on to suit a personal preference for decoration. In this way the user is able to control whether any of their available screen space is given over to eye candy.

jdmeaux1952 · posted: 2015-02-09 14:22

SamK wrote:antiX-14-a4-R_386-full.iso patched with a4-a5.delta

Comparing the two results it is evident that there is less than 80% usable screen space when the eye candy decoration is displayed.

.

Here I thought it was just my eyes playing tricks on me again. I'm glad it was the resolution instead. Well, not glad. Not happy. But reassured it wasn't me physically.

SamK · posted: 2015-02-11 07:01

antiX-14-a4-R_386-full.iso patched with a4-a5.delta

Test conducted booting live USB without persistence, GUI mode using shipped defaults

Test 1
Boot param appended: vga=788 (800x600x16) i.e. maximum value this system can use
System accepts param as valid and uses it

Code: Select all

inxi -c0 -G
Graphics:  Card: Silicon Integrated Systems [SiS] 65x/M650/740 PCI/AGP VGA Display Adapter
           Display Server: X.Org 1.16.2.901 drivers: fbdev (unloaded: vesa)
           Resolution: 800x600@75.00hz
           GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits)
           GLX Version: 3.0 Mesa 10.3.2

Note the driver and resolution.

Test conducted booting antiX-13.2-Full-Stable (Wheezy) shipped ISO burned to CD-ROM.

Test 2
Boot param appended: vga=788 (800x600x16) i.e. maximum value this system can use
System accepts param as valid and uses it

Code: Select all

inxi -c0 -G
Graphics:  Card: Silicon Integrated Systems [SiS] 65x/M650/740 PCI/AGP VGA Display Adapter
           Display Server: X.Org 1.12.4 drivers: sis (unloaded: fbdev,vesa)
           Resolution: 1280x1024@60.0hz
           GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 0x209)
           GLX Version: 2.1 Mesa 8.0.5

Note the driver and resolution.

Comparing the two results it is evident that a4-a5 fails to handle the vga=788 value correctly, whereas 13.2 handles it correctly and produces the expected result.

a4-a5 fails to use the X mode graphics driver which results in a GUI resolution of 800x600.
13.2 successfully uses the X mode graphics driver which produces the greatly improved GUI resolution of 1280x1024.

Something has been introduced in a4-a5 that is preventing the system operating optimally.

dolphin_oracle · posted: 2015-02-11 12:02

Test 1
Boot param appended: vga=788 (800x600x16) i.e. maximum value this system can use
System accepts param as valid and uses it
Code:
inxi -c0 -G
Graphics: Card: Silicon Integrated Systems [SiS] 65x/M650/740 PCI/AGP VGA Display Adapter
Display Server: X.Org 1.16.2.901 drivers: fbdev (unloaded: vesa)
Resolution: 800x600@75.00hz
GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits)
GLX Version: 3.0 Mesa 10.3.2
Note the driver and resolution.

The problem may be xserver-xorg-video-sis, which is present in wheezy and antix-13.2, and not present in jessie/antix-14/15. It doesn't look available at all for debian.

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://launchpad.net/debian/jessie/+source/xserver-xorg-video-sis"
linktext was:"https://launchpad.net/debian/jessie/+so ... -video-sis"
====================================

there is a version in"unstable" but not in"jessie" . its the same version as in wheezy from the looks of the version numbers.

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://packages.debian.org/search?keywords=xserver-xorg-video-sis"
linktext was:"https://packages.debian.org/search?keyw ... -video-sis"
====================================

SamK · posted: 2015-02-16 09:48

antiX-14-a4-R_386-full.iso patched with a4-a5.delta
comparison against
antiX-13.2-Full-Stable Wheezy as shipped ISO

Recording symptoms only (not investigated)

Test conducted booting live USB without persistence, selecting CLI install (init 3) in order to use live system in console mode i.e. X is not required nor used.

Code: Select all

mplayer -vo fbdev2 test.mp4
alpha5
Warning unknown option stopxscreensaver at line 5
MPlayer2 2.0-728-g2c378c7-4+b1 (C) 2000-2012 MPlayer Team
Cannot open file '/home/demo/.mplayer/input.conf': No such file or directory
Failed to open /home/demo/.mplayer/input.conf.
Cannot open file '/ etc/mplayer/input.conf': No such file or directory
Failed to open / etc/mplayer/input.conf.

Playing test.mp4.
Detected file format: QuickTime / MOV (libavformat)
[lavf] stream 0: video (h264), -vid 0
[lavf] stream 1: audio (aac), -aid 0, -alang eng
Clip info:
 major_brand: mp42
 minor_version: 0
 compatible_brands: mp42isomavc1
 creation_time: 2010-03-20 21:29:11
 encoder: HandBrake 0.9.4 2009112300
Load subtitles in .
Error opening/initializing the selected video_out (-vo) device.
Selected audio codec: AAC (Advanced Audio Coding) [libavcodec]
AUDIO: 48000 Hz, 1 ch, floatle, 83.0 kbit/5.41% (ratio: 10381->192000)
AO: [pulse] Init failed: Connection refused
AO: [alsa] 48000Hz 1ch floatle (4 bytes per sample)
Video: no video
Starting playback...
Exiting... (End of file)
13.2
MPlayer svn r34540 (Debian), built with gcc-4.7 (C) 2000-2012 MPlayer Team

Playing test.mp4.
libavformat version 53.21.1 (external)
Mismatching header version 53.19.0
libavformat file format detected.
[lavf] stream 0: video (h264), -vid 0
[lavf] stream 1: audio (aac), -aid 0, -alang eng
VIDEO:  [H264]  560x320  24bpp  30.000 fps  465.6 kbps (56.8 kbyte/s)
Clip info:
 major_brand: mp42
 minor_version: 0
 compatible_brands: mp42isomavc1
 creation_time: 2010-03-20 21:29:11
 encoder: HandBrake 0.9.4 2009112300
Load subtitles in ./
==========================================================================
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
libavcodec version 53.35.0 (external)
Mismatching header version 53.32.2
Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
==========================================================================
==========================================================================
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 48000 Hz, 1 ch, s16le, 83.0 kbit/10.81% (ratio: 10381->96000)
Selected audio codec: [ffaac] afm: ffmpeg (FFmpeg AAC (MPEG-2/MPEG-4 Audio))
==========================================================================
AO: [alsa] 48000Hz 1ch s16le (2 bytes per sample)
Starting playback...
Could not find matching colorspace - retrying with -vf scale...
Opening video filter: [scale]
Movie-Aspect is undefined - no prescaling applied.
[swscaler @ 0xb6c59560]using unscaled yuv420p -> bgra special converter
VO: [fbdev2] 560x320 => 560x320 BGRA 
A:   0.0 V:   0.0 A-V:  0.047 ct:  0.000   0/  0 ??% ??% ??,?% 0 0
A:   0.1 V:   0.0 A-V:  0.034 ct:  0.003   0/  0 ??% ??% ??,?% 0 0
A:   0.1 V:   0.1 A-V:  0.028 ct:  0.009   0/  0 ??% ??% ??,?% 0 0
[...]
A:   5.5 V:   5.5 A-V:  0.000 ct:  0.034   0/  0 10%  6%  0.5% 0 0
A:   5.5 V:   5.5 A-V:  0.000 ct:  0.034   0/  0 10%  6%  0.5% 0 0
Exiting... (End of file)

In alpha5
audio play successful
video play fail

In 13.2
audio play successful
video play successful

Code: Select all

cat /sys/class/graphics/fb0
alpha5
1280x800
13.2
1280x800

Code: Select all

inxi -c0 -G
alpha5
Graphics:  Card: Intel Mobile 915GM/GMS/910GML Express Graphics Controller
           Display Server: X.org 1.16.2.901 driver: N/A tty size: 160x50 Advanced Data: N/A out of X
13.2
Graphics:  Card: Intel Mobile 915GM/GMS/910GML Express Graphics Controller 
           X.org: 1.12.4 driver: N/A tty size: 160x50 Advanced Data: N/A out of X

Working assumption; at boot-up there is an issue loading the framebuffer driver correctly

Addendum
The reported behaviour is due to a change in MPlayer
post39994.html#p39994

Edit: added addendum

SamK · posted: 2015-02-17 09:42

antiX-14-a4-R_386-full.iso patched with a4-a5.delta

Comparison of selecting desktop in boot screen (F6) on networking

Recording symptoms only (not investigated)

Tests conducted booting live USB without persistence, GUI mode using shipped defaults

Test 1
Boot param appended: None
Using Desktop=Rox-IceWM in boot screen (i.e. making manual selection)
Network cable connected to system (i.e. wired and wireless)

Code: Select all

ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:14:22:89:f8:ce brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.106/24 brd 192.168.2.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::214:22ff:fe89:f8ce/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:13:ce:b9:90:bb brd ff:ff:ff:ff:ff:ff
inxi -c0 -n
Network:   Card-1: Broadcom BCM4401-B0 100Base-TX driver: b44
           IF: eth0 state: up speed: 100 Mbps duplex: full
           mac: 00:14:22:89:f8:ce
           Card-2: Intel PRO/Wireless 2200BG [Calexico2] Network Connection
           driver: ipw2200
           IF: eth1 state: down mac: 00:13:ce:b9:90:bb

Result
Wired networking automatically set up and working correctly
Wireless networking not automatically set up

Test 2
Boot param appended: None
Using Desktop=Default in boot screen (i.e. making no selection)
Network cable connected to system (i.e. wired and wireless)

Code: Select all

ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
    link/ether 00:13:ce:b9:90:bb brd ff:ff:ff:ff:ff:ff
    inet6 fe80::213:ceff:feb9:90bb/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:14:22:89:f8:ce brd ff:ff:ff:ff:ff:ff
inxi -c0 -n
Network:   Card-1: Broadcom BCM4401-B0 100Base-TX driver: b44
           IF: eth1 state: down mac: 00:14:22:89:f8:ce
           Card-2: Intel PRO/Wireless 2200BG [Calexico2] Network Connection driver: ipw2200
           IF: eth0 state: unknown mac: 00:13:ce:b9:90:bb

Result
Wired networking not automatically set up
Wireless networking not automatically set up

Test 3
Boot param appended: None
Using Desktop=Rox-IceWM in boot screen (i.e. making manual selection)
Network cable not connected to system (i.e. wireless only)

Code: Select all

ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 00:14:22:89:f8:ce brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:13:ce:b9:90:bb brd ff:ff:ff:ff:ff:ff
inxi -c0 -n
Network:   Card-1: Broadcom BCM4401-B0 100Base-TX driver: b44
           IF: eth0 state: down mac: 00:14:22:89:f8:ce
           Card-2: Intel PRO/Wireless 2200BG [Calexico2] Network Connection
           driver: ipw2200
           IF: eth1 state: down mac: 00:13:ce:b9:90:bb

Result
Wireless networking not automatically set up

Test 4
Boot param appended: None
Using Desktop=Default in boot screen (i.e. making no selection)
Network cable not connected to system (i.e. wireless only)

Code: Select all

ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
    link/ether 00:13:ce:b9:90:bb brd ff:ff:ff:ff:ff:ff
    inet6 fe80::213:ceff:feb9:90bb/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:14:22:89:f8:ce brd ff:ff:ff:ff:ff:ff
inxi -c0 -n
Network:   Card-1: Broadcom BCM4401-B0 100Base-TX driver: b44
           IF: eth1 state: down mac: 00:14:22:89:f8:ce
           Card-2: Intel PRO/Wireless 2200BG [Calexico2] Network Connection
           driver: ipw2200
           IF: eth0 state: unknown mac: 00:13:ce:b9:90:bb

Result
Wireless networking not automatically set up

Summary
Wired networking: automatic set up fails depending on desktop selected at boot up
Wireless networking: automatic set up fails in all tests

Note
In all cases of failure ceni can be used to manually set up networking.