topic title: Problem installing antiX-13.1-full
Posts: 4
HenkKoorn
Joined: 20 Sep 2013
#1
Would you help me please.
I have an HP Thin Client T5520 and I want Anrix-13.1 to install.
Processor Speed​​: 800 MHz, Memory: 64Mb Flash, 128Mb Ram
I use an external USB CD player with a liveCD antiX-13.1_386-full.iso.
The system appears to boot the ISO fine. I get the screen where I can set the options for the live boot.
However, after setting an option, does not matter which option, also from-all, I have problems.

Below is the output of my welcome screen. This happens regardless of the boot settings.

Welcome to antiX-13.1 Luddite!
Current bootcodes:
automount=usb quiet antiX=MLX from=all
Scanning all devices for antiX/linuxfs
retrying ..........
=================================================================
Fatal Error
Could not find limux file:"antiX/linuxfs".
=================================================================

-----------------------------------------------------------------
p = power off
r = reboot
-----------------------------------------------------------------
select p or r then hit (enter)


Here is the output of lspci -k

00:00.0 Host bridge: VIA Technologies, Inc. VT8623 [Apollo CLE266]
Subsystem: VIA Technologies, Inc. VT8623 [Apollo CLE266]
Kernel driver in use: agpgart-via
00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP]
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
Kernel driver in use: uhci_hcd
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
Kernel driver in use: uhci_hcd
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
Subsystem: VIA Technologies, Inc. USB 2.0
Kernel driver in use: ehci_hcd
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
Subsystem: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
Subsystem: VIA Technologies, Inc. VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE
Kernel driver in use: pata_via
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
Subsystem: VIA Technologies, Inc. K7VT2 motherboard
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
Subsystem: VIA Technologies, Inc. VT6102 [Rhine II] Embeded Ethernet Controller on VT8235
Kernel driver in use: via-rhine
01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics (rev 03)
Subsystem: VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics

and lspci -n

00:00.0 0600: 1106:3123
00:01.0 0604: 1106:b091
00:10.0 0c03: 1106:3038 (rev 80)
00:10.1 0c03: 1106:3038 (rev 80)
00:10.3 0c03: 1106:3104 (rev 82)
00:11.0 0601: 1106:3177
00:11.1 0101: 1106:0571 (rev 06)
00:11.5 0401: 1106:3059 (rev 50)
00:12.0 0200: 1106:3065 (rev 74)
01:00.0 0300: 1106:3122 (rev 03)

This is not my native language, sorry for the mistakes.
Thanks for the help!
Posts: 765
rust collector
Joined: 27 Dec 2011
#2
Well, when I get the

Code: Select all

Fatal Error
Could not find limux file:"antiX/linuxfs".
I just make a new usb-stick (as I don't use cd/dvd's)

I think it might be a bad burn?

In the boot menu, can you select the"check md5" (or similar) in the f4, or f5 submenu?

But wait for someone else to comment as well, as I am useless.
Posts: 2,238
dolphin_oracle
Joined: 16 Dec 2007
#3
I would try to make a bootable usb stick first.

I think this is a re-emergence of an old problem with odd usb hardware. Once the handoff to the antix init system takes place, sometimes odd usb hardware (like your CD drive) don't always get picked up. It seems to be more of a problem on slower hardware, like netbooks and your thin client.

BitJam knows more about the boot process than almost anyone. I'll drop him a note to check out this post.
Posts: 4
HenkKoorn
Joined: 20 Sep 2013
#4
With a USB stick it works, and the boot option 'from = all'.
only with the full version, the base version is still the same
and I want to use the base version. which is smaller
thanks
Posts: 4,164
rokytnji
Joined: 20 Feb 2009
#5
HenkKoorn wrote:With a USB stick it works, and the boot option 'from = all'.
only with the full version, the base version is still the same
and I want to use the base version. which is smaller
thanks
I would md5sum check the base iso first if full works ok.
Posts: 4
HenkKoorn
Joined: 20 Sep 2013
#6
With a USB stick now it works sometimes, but not always, I use the language option and"from = all '. maybe it's a timing issue?
thanks
Posts: 850
fatmac
Joined: 26 Jul 2012
#7
Try adding 'rootdelay=10' to the grub boot 'kernel' line.
Posts: 4
HenkKoorn
Joined: 20 Sep 2013
#8
fatmac wrote:Try adding 'rootdelay=10' to the grub boot 'kernel' line.
where? In the ISO? When? Did you read my first post?
Posts: 2,238
dolphin_oracle
Joined: 16 Dec 2007
#9
On the grub boot menu, there is a box with the cheat codes in it. You can add the 'rootdelay=10" line there.
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#10
I apologize for my absence. Thank you for the PMs. I don't get email messages (anymore?) when I get PMs and I don't know how to enable that feature. I suppose they might be getting swallowed up by a spam filter somewhere along the way.

AFAIK the rootdelay option no longer works. It certainly doesn't work here. The good news is that the new retry mechanism is an improvement. You can adjust the number of retries with the retry= option.
HenkKoorn wrote:With a USB stick now it works sometimes, but not always, I use the language option and"from = all '. maybe it's a timing issue?
We've run into this situation before with very old hardware and never got to a conclusive answer. The two basic tools at your disposal are increased verbosity and breakpoints that drop you down to a shell.

You can increase (or decrease) the verbosity with the"verb=" boot parameter. The default value is 5. The max value is 9. Usually"verb=7" or"verb=8" will tell you everything interesting but I doubt it will help with your problem.

You can set one or more breakpoints with the"bp=" boot parameter. You can get a list of all breakpoints using"bp=?". I suggest you use"bp=2,e" which will give you a shell at breakpoint-2 right before we try to mount the boot device and find the /antiX/linuxfs file. It will also give you a shell again on an error (such as not finding the /antiX/linuxfs file).

One problem we've seen is that there is a conflict between high-speed and low-speed usb buses. An easy way to look for this problem is in the output of the"dmesg" command:

Code: Select all

   dmesg | less
   dmesg | grep usb  | less
   dmesg | grep _hcd | less
TIP Use the"vga=" boot parameter to get more text displayed on the screen. Here are some common resolutions:

Code: Select all

    1024×768   vga=792  
    1152×720   vga=872  
    1280×800   vga=864  
   1280×1024   vga=795
   interactive vga=ask
If it boots some times and not others, this may be due to the wrong usb bus connecting to your LiveUSB. You can check this (from a breakpoint) with"ls /sys/bus/pci/drivers/*_hcd/" Example:

Code: Select all

ls /sys/bus/pci/drivers/*_hcd/
/sys/bus/pci/drivers/ehci_hcd/:
0000:00:12.2@  0000:00:13.2@  bind  module@  new_id  remove_id  uevent  unbind

/sys/bus/pci/drivers/ohci_hcd/:
0000:00:12.0@  0000:00:13.0@  0000:00:14.5@  new_id     uevent
0000:00:12.1@  0000:00:13.1@  bind           remove_id  unbind

/sys/bus/pci/drivers/uhci_hcd/:
bind  module@  new_id  remove_id  uevent  unbind

/sys/bus/pci/drivers/xhci_hcd/:
bind  module@  new_id  remove_id  uevent  unbind
The symlinks (marked with the trailing"@" sign will be different on your system.

I suggest you write down the symlinks locations (or take a picture!) when it works and when it doesn't. If they are in different places when it works and when it doesn't work then this is the problem. The next version of our initrd has a boot code that tries to address and fix this problem. I can email it to you.

Another possible solution is to use a different *speed* usb stick. If the stick you are using is usb-2.0, then (if it is easy) try using a usb-1.1 (or usb-1.0) stick instead (or vice versa).

I sent you a PM with my email address so we can continue this discussion via email.

Edit: I gave slightly more detailed instructions here:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://forum.mepiscommunity.org/viewtopic.php?p=320041#p320041"
linktext was:"http://forum.mepiscommunity.org/viewtop ... 41#p320041"
====================================


Edit-2: Changed bp-3 --> bp-2.
Posts: 1
bernie
Joined: 14 Feb 2014
#11
To BitJam. I tried installing MX-14 Beta 2.0 from a DVD disc on my desktop (running on Windows Vista). All I get is a message;"could not find file" antiX/linuxfs", contact Bitjam at
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"antix.freeforu ms.org"
linktext was:"antix.freeforu ms.org"
====================================
. Help! I'm too embarrassed to go back to my supplier just yet. What can I do next?
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#12
Bernie, you should start a new thread with this problem because it is unlikely to be related to HenkKoorn's problem. In fact, I suggest you start a new thread over in the
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://forum.mepiscommunity.org/viewforum.php?f=91"
linktext was:"Mepis Forums"
====================================
. But since you were properly following the instructions, I will give you my first response here and not leave you hanging. First, *you* should not be embarrassed if our software fails. If anyone should be embarrassed it is us.

Next, which version of MX-14 are you using? The first beta had many booting problems but the 2nd beta worked for almost everyone. You can tell which version you have by the highlighted text at the top of the bootloader menu:
  • 1st beta: MX-14_13.97_386-xfce (22 January 2014)
  • 2nd beta: MX-14_13.98_386-xfce (30 January 2014)
If your are using the first beta then you need to
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.mepiscommunity.org/mx"
linktext was:"upgrade to the second beta"
====================================
. There is no other choice (except possibly waiting for the next release which might come out within the next few days). If the version you are using is not the problem then I will need to put my thinking cap on.