topic title: antiX-16-b2.1-full available
Posts: 1,028
SamK
Joined: 21 Aug 2011
#16
Re: Error Messages Reported During Boot Up

The system boots to GUI OK.
Switch to CTL+ALT+F1 to see last few boot messages shows the following:

Code: Select all

...
live-restore-services: restoring service links
network-manager: unrecognized service
network-manager: unrecognized service
[FAIL] startpar: service(s) returned failure: rc.local ... failed!
...
This was originally reported for 16-b1
Remains unchanged in 16-b2.1
Posts: 1,028
SamK
Joined: 21 Aug 2011
#17
Re: antiX-16b1 only partially working OOTB

These also apply in 16-b2.1

Test environment
Booted live CD
Boot command

Code: Select all

cat /proc/cmdline
desktop=space-icewm vga=791 lang=en_GB quiet splash=off disable=lx
Wired networking not working OOTB. Works after set up via Ceni or WICD.

Conky does not display network monitors after network set up

Mouse invisible at start up
The change of mouse cursor colour has not fixed this problem
Additional info
Boot to desktop completes normally
The mouse is not visible but is working i.e. a right-click on the desktop displays the menu but not the mouse cursor
Waiting many minutes does not show the mouse cursor

The mouse cursor can be cajoled into showing by using the keyboard to open the menu and an app window (e.g. Control Center). At that point the mouse cursor becomes visible and remains so thereafter.
Posts: 1,028
SamK
Joined: 21 Aug 2011
#18
Confirming fixes working in 16-b2.1

The task bar icon for volumeicon is almost invisible.
Much much more visible and good choice of simple icon


Geany with the text edit area of white text on a black background
Reverting to the Geany default of black text on a white background works well
anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007
#19
Unetbootin is the problem since it appears that it is not deleting/overwriting all of the files/folders on the usb stick.
Either reformat the stick using gparted before using unetbootin or use the antix2usb app.
Posts: 1,028
SamK
Joined: 21 Aug 2011
#20
anticapitalista wrote:Either reformat the stick using gparted before using unetbootin.
That has been done to the partition before each failed test.
anticapitalista wrote:or use the antix2usb app.
Does that write to the entire stick rather than just a partition on the stick? This stick has two partitions and if possible I would prefer to keep both of them.
anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007
#21
Does that write to the entire stick rather than just a partition on the stick? - It will overwrite the whole stick.

Maybe the problem is on the partition you have not reformatted?
Posts: 1,028
SamK
Joined: 21 Aug 2011
#22
anticapitalista wrote:Maybe the problem is on the partition you have not reformatted?
I suppose anything is possible but I think that is unlikely. Partition1 is ext4 and holds (will hold) antiX, partition2 is FAT32 and holds data files only, it is not $HOME nor is it associated with antiX in any way.

I'll try deleting and recreating and formatting partition1 to see if that works.
anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007
#23
Only other issue I can think of is a failing usb stick.
Posts: 1,028
SamK
Joined: 21 Aug 2011
#24
anticapitalista wrote:Only other issue I can think of is a failing usb stick.
The stick is fine. It's quite new. Although that alone is no guarantee of it working, it has never been worked hard.

I managed to get it to boot 16b2.1 by handling some elements manually with fdisk on partition1.
Destroyed partition
Created partition
Aligned start of partition to 2048
Set up an ext4 file system with the command

Code: Select all

mkfs.ext4 -b 4096 -E stride=128,stripe-width=128 -m 0 -O ^has_journal -L USB-YELLOW /dev/sdb1
Then installed antiX using unetbootin

Booted successfully using USB stick
Posting now from booted USB

When installing the bootloader, unetbootin again found the following files and asked for confirmation to overwrite them:
.../boot/syslinux/
menu.c32
libutil.c32
libcom32.c32
Clearly these were destroyed by the manual preparation of partition1. Are these unpacked when the ISO is extracted from archive and then found when unetbootin installs the bootloader?
Posts: 2,238
dolphin_oracle
Joined: 16 Dec 2007
#25
SamK wrote: When installing the bootloader, unetbootin again found the following files and asked for confirmation to overwrite them:
.../boot/syslinux/
menu.c32
libutil.c32
libcom32.c32
Clearly these were destroyed by the manual preparation of partition1. Are these unpacked when the ISO is extracted from archive and then found when unetbootin installs the bootloader?

this has been an issue for a while with unetbootin. don't know why. as far as i can tell, it doens't matter how you answer the question.
Posts: 2,238
dolphin_oracle
Joined: 16 Dec 2007
#26
SamK wrote:Re: Error Messages Reported During Boot Up

The system boots to GUI OK.
Switch to CTL+ALT+F1 to see last few boot messages shows the following:

Code: Select all

...
live-restore-services: restoring service links
network-manager: unrecognized service
network-manager: unrecognized service
[FAIL] startpar: service(s) returned failure: rc.local ... failed!
...
This was originally reported for 16-b1
Remains unchanged in 16-b2.1
sam,

I think what you are seeing is some leftover code. there is now a script in play that tries to figure out which broadcom driver to use for a given part. The script was originally written for MX, which does use network-manager.

On a liveUSB with persistence, please try the following.

Open /usr/local/bin/BroadcomStartup as root and comment out all entries for

service network-manager stop
service network-manager start


there are 3 of each.


Then delete

etc/bcm-ckd

and reboot. I think you'll see those error message go away. If so, this will be an easy tweak for the guys to make.
Posts: 2,238
dolphin_oracle
Joined: 16 Dec 2007
#27
samk,

could you post the output of

udevadm info --query=property /sys/class/net/eth1

and

udevadm info --query=property /sys/class/net/eth0
Posts: 1,028
SamK
Joined: 21 Aug 2011
#28
dolphin_oracle wrote:could you post the output of

Code: Select all

udevadm info --query=property /sys/class/net/eth1
COMMENT=PCI device 0x14e4:0x170c (b44)
DEVPATH=/devices/pci0000:00/0000:00:1e.0/0000:02:00.0/ssb0:0/net/eth1
ID_BUS=pci
ID_MODEL_FROM_DATABASE=BCM4401-B0 100Base-TX
ID_MODEL_ID=0x170c
ID_NET_DRIVER=b44
ID_NET_NAME_MAC=enx00142289f8ce
ID_OUI_FROM_DATABASE=Dell Inc
ID_PATH=pci-0000:02:00.0
ID_PATH_TAG=pci-0000_02_00_0
ID_PCI_CLASS_FROM_DATABASE=Network controller
ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
ID_VENDOR_FROM_DATABASE=Broadcom Corporation
ID_VENDOR_ID=0x14e4
IFINDEX=3
INTERFACE=eth1
MATCHADDR=00:14:22:89:f8:ce
MATCHDEVID=0x0
MATCHIFTYPE=1
SUBSYSTEM=net
USEC_INITIALIZED=690059

Code: Select all

udevadm info --query=property /sys/class/net/eth0
COMMENT=PCI device 0x8086:0x4220 (ipw2200)
DEVPATH=/devices/pci0000:00/0000:00:1e.0/0000:02:03.0/net/eth0
DEVTYPE=wlan
ID_BUS=pci
ID_MODEL_FROM_DATABASE=PRO/Wireless 2200BG [Calexico2] Network Connection (Dell Latitude D600)
ID_MODEL_ID=0x4220
ID_NET_DRIVER=ipw2200
ID_NET_NAME_MAC=wlx0013ceb990bb
ID_NET_NAME_PATH=wlp2s3
ID_OUI_FROM_DATABASE=Intel Corporate
ID_PATH=pci-0000:02:03.0
ID_PATH_TAG=pci-0000_02_03_0
ID_PCI_CLASS_FROM_DATABASE=Network controller
ID_PCI_SUBCLASS_FROM_DATABASE=Network controller
ID_VENDOR_FROM_DATABASE=Intel Corporation
ID_VENDOR_ID=0x8086
IFINDEX=2
INTERFACE=eth0
MATCHADDR=00:13:ce:b9:90:bb
MATCHDEVID=0x0
MATCHIFTYPE=1
SUBSYSTEM=net
USEC_INITIALIZED=288182
Posts: 2,238
dolphin_oracle
Joined: 16 Dec 2007
#29
Ok, I need to test some more, but this line seems to be key:

Code: Select all

DEVTYPE=wlan
this line does not appear on any of the wired systems I've tried so far, and only appears on the wireless systems I'v tried so far. I need to try more chipsets, but given this information, it might be actually possible to configure conky to display the network monitors aftera connection is made. We could possibly set the network interface with a little use of sed to make some string changes.

sam, Out of curiosity, does eth0 show up in wicd preferences as a wireless card? and does eth1 show as wired?

Or you know, just include more network monitor entires (eth1, wlan1, etc...)
anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007
#30
This is the etc/network/interfaces I'm thinking of using on next test iso. Would it work better?

Code: Select all

# interfaces(5) file used by ifup(8) and ifdown(8)

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp

allow-hotplug eth1
iface eth1 inet dhcp

allow-hotplug eth2
iface eth2 inet dhcp

allow-hotplug eth3
iface eth3 inet dhcp

allow-hotplug eth4
iface eth4 inet dhcp

allow-hotplug eth5
iface eth5 inet dhcp