During booting of Antix (13.2), I have a problem that seems linked to my BIOS (message = i/o space for gpio uninitialized, more info here:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://bugzilla.kernel.org/show_bug.cgi?id=48521"
linktext was:"https://bugzilla.kernel.org/show_bug.cgi?id=48521"
====================================
)
The problem is not important, Antix boots fine.
However, the boot process becomes very long, it looks like there is a timeout of 120 seconds and it takes indees a long time (and many identical messages about aborting) before the boot continues.
Can I reduce this timeout somehow?
Thanks,
Roel
topic title: How to reduce the startup timeout of 120 seconds?
9 posts
• Page 1 of 1
-
Posts: 5
- Joined: 14 Oct 2013
-
Posts: 325
- Joined: 04 Nov 2011
#2
and attach here
Code: Select all
# cat /var/log/messages > /home/[user]/antiXStart.txt
-
Posts: 5
- Joined: 14 Oct 2013
#3
Ok, I'll do that when I get home.
Just a small question: what's the diff between your command, and
thanks,
Just a small question: what's the diff between your command, and
Code: Select all
cp /var/log/messages /home/[user]/antiXStart.txt ?
-
Posts: 2,238
- Joined: 16 Dec 2007
#4
for this purpose, the commands are equivalent, although they function differently, the end result is the same.
-
Posts: 5
- Joined: 14 Oct 2013
#5
Here is the message log, I could not find anything in there, but I'm not an expert at all...
I'm not really bothered by the cause of the slow startup. I hope there's a simple way to reduce the 120s timeout to eg. 5s.
Thanks,
Roel
I'm not really bothered by the cause of the slow startup. I hope there's a simple way to reduce the 120s timeout to eg. 5s.
Thanks,
Roel
-
Posts: 1,308
- Joined: 31 Aug 2009
#6
The log delay occurs between ACPI: Smart Battery System [SBS0]: Battery Slot [BAT0] (battery present) and Adding 2128608k swap on /dev/sda2. Priority:1 extents:1 across:2128608k. There are also consistent segfaults (accessing unallowed memory) in the gmerlin programs and on October 5th it looks like the nfs file system crashed on an invalid op code. These other errors indicate something fishy is going on. The consistency of the gmerlin errors points toward a problem with the gmerlin software but the addition of the nfs error also raises the possibility of a hardware problem.
These TravelMate laptops are know to have problems with ACPI. For starters I suggest you add the boot parameters"noacpi" and"acpi=off". At least that is very easy to try. You will lose some ACPI features when you do this. If this works and you want the features back then you will need to install an updated DSDT for your machine such as the one available
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://code.google.com/p/aceracpi/source/browse/trunk/dsdt/acer/travelmate/4500.dsl?r=367"
linktext was:"here"
====================================
.
If this doesn't help solve your problem then it would be useful if you could capture the error messages that you say get printed to the screen. They might be in a log file under /var/log/. If you have access to a digital camera then maybe you could just take a picture of the screen with the messages on it and post it here. I'm hoping they will help us pinpoint the subsystem that is acting up.
These TravelMate laptops are know to have problems with ACPI. For starters I suggest you add the boot parameters"noacpi" and"acpi=off". At least that is very easy to try. You will lose some ACPI features when you do this. If this works and you want the features back then you will need to install an updated DSDT for your machine such as the one available
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://code.google.com/p/aceracpi/source/browse/trunk/dsdt/acer/travelmate/4500.dsl?r=367"
linktext was:"here"
====================================
.
If this doesn't help solve your problem then it would be useful if you could capture the error messages that you say get printed to the screen. They might be in a log file under /var/log/. If you have access to a digital camera then maybe you could just take a picture of the screen with the messages on it and post it here. I'm hoping they will help us pinpoint the subsystem that is acting up.
-
Posts: 5
- Joined: 14 Oct 2013
#7
Thanks for looking at all these details. I also have the feeling that something fishy happens on that laptop. Antix was about the only linux I could install on it, I tried about 6 different distros before, and all installations failed.
With acpi=off as boot option, Antix boots like a charm. I'm really happy with this simple and easy solution, and I don't have the impression there are any drawbacks. What could be these 'features' I don't have anymore?
Just to make it even better: is there a way to have this boot option by default? Right now, the default boot options are root=/dev/sda1 quiet
Thanks,
Roel
With acpi=off as boot option, Antix boots like a charm. I'm really happy with this simple and easy solution, and I don't have the impression there are any drawbacks. What could be these 'features' I don't have anymore?
Just to make it even better: is there a way to have this boot option by default? Right now, the default boot options are root=/dev/sda1 quiet
Thanks,
Roel
-
Posts: 765
- Joined: 27 Dec 2011
#8
then on a line similar to this:
kernel /boot/vmlinuz-3.11.5-antix.1-486-smp root=/dev/sda1 quiet nouveau.modeset=0
just add the acpi=off , and save the file. it will be there after a reboot
Code: Select all
sudo nano /boot/grub/menu.lst
kernel /boot/vmlinuz-3.11.5-antix.1-486-smp root=/dev/sda1 quiet nouveau.modeset=0
just add the acpi=off , and save the file. it will be there after a reboot
-
Posts: 5
- Joined: 14 Oct 2013
#9
Thanks, works great! I think we can close this thread completely now.