I recently put together a new machine with Ubuntu 9.10 I couldn't boot it even live (or any live distro for that). It wound up being either a ACPI or APM setting in the BIOS that got it to boot, I say either because I spent probably 10 hours in there turning things on and off until it worked. It was about 4am so my memory of it ain't that great. TO get up to date, I was adding a HDD and having some issues with it being detected right. So back in the BIOS I was and accidentally loaded the defaults! Now I can't figure out what I did last time I've been at it for hours with no luck.
If I jump into grub b4 it boots and add the acpi=off the system boots up but with the side effects of no pwr mgmt. I need it to be able to sleep and shut itself off. I've always had good luck with Ubuntu in other machines so I'm not that great in there, and honestly don't know the difference between apm/acpi. The MOBO is an ASUS P4C800 Deluxe, AMI Bios. I'm gunna keep at it in the mean time, if by any chance I figure it out I'll post what it was (after I write it down).
When I run OpenSUSE from the Live CD using normal settings, booting stops with a blank screen a moment after the kernel is loaded. When running it with ACPI disabled, it works, but direct rendering is disabled, even though it detects my video card (Mobility Radeon HD 5650) correctly Here's the Xorg.0.log file: my xorg log - [URL]
I changed something in the BIOS which causes a kernel panic, if my card is installed (Ultra ATA/133 PCI-to-ATA Host Controller). I had it working fine til a month ago, when I installed some Linux on a HD on that card. That booted fine too, and I did some disk switching. Still all was well, but yesterday I tried to boot XP (2nd IDE master)(GRUB is Ubuntu/2nd IDE slave), and XP wouldn't load. I clicked here, and clicked there, and now XP and Ubuntu boot, ONLY if the RAIDbus card is Out. Put the card in, and I get a kernel panic/lockup. This HAS to be a BIOS function - nothing is different on the disks, including GRUB menu.
i am trying to install the new openSUSE 11.3 version but i can't install it without setting the ACPI mode to OFF. Is the new kernel support this hardware? (Toshiba Satellite A505-s6033) i had this problem already with Ubuntu 10.4 LTS and i had have to recompile the kernel with this patch: Some buggy BIOS may modify DSDT memory when acpi enabled. So we copy DSDT for safe.
I thought the 2.6.34 kernel already have this patch but it seems i was wrong... So if i will install the system with ACPI on OFF mode i will be need to recompile the kernel with this patch to get things working?
Having trouble rebooting a system. Have a Ubuntu 9.10 (2.6.31-16 generic-pae) build on a VMWare installation. The system was fine until I rebooted after an update. Now I get the above message and the system halts loading. Have tried to Grub acpi=off and acpi=force to no avail.
I want to go back to Windows. However I can't uninstall Ubuntu since I can't boot up from CD nor USB no matter how I change the BIOS setting. I chose CD or USB but it will go straight to Ubuntu. How can I get rid of it without taking out the hard drive and have it formatted from another computer.
While building my new server I grinded ta hold shortly after inserting the FDR10 DVD.
Hardware: Chenbro es34069 Albatron KI690-AM2 AMD Athlon X2 64 4850E IDE 2.5" HD (master) IDE Slimline DVD (slave) 4x SATA II swap (still empty)
It stops at the message "net: Registered protocol family 2" but in one of my desperate attempts I changed almost every setting in my BIOS (updated to 1.07) and all of a sudden it passed on. Stupid enough I figured it would be a small effort to find the setting and figure out the problem, so I changed them one at a time after loading the defaults....
I have a Dell Windows7 PC configured with BIOS RAID1. I want to install SLES10 and configure it with Software RAID1. My question is: Do I need to reconfigure the BIOS RAID setting and if so What should it be.
I would like to be able to change my BIOS setting to enable me to access a live cd or dvd to try some Linux Distros. At the moment ,when I access the BIOs ,it willl not stay as adjusted ,it ignores the settings ,it goes to default.
I haven't been able to use linux for like 6 months I've tried Fedora 14, Debian Testing, Ubuntu 10.04 and now Mint KDE.
Whenever I boot any distro my laptop acts randombly, it gets to GDM and it freezes, or it lets me login and then freezes or works really slow, even through the shell.
The only thing I could figured is to insert acpi=off on the boot commands googling around, and there it boots.
My problem is that it gets overheated, I can't use any porcessor policy and I can't suspend my laptop with that boot line.
I have random X freezes (suddenly keyboard and mouse stop to react). Xorg.O.log is error and warnings free. The only problems I see in syslog/ dmesg are related to ACPI.
I have Asus P5E3 Deluxe motherboard. Slackware 13.1
Linux vareg 2.6.33.4-smp #2 SMP Wed May 12 22:47:36 CDT 2010 i686 Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz GenuineIntel GNU/Linux
Code:
Code:
I ahve also today upgraded my BIOS to 1303 version. Still no difference.
My openSuse install can't boot/login with ACPI enabled. I disabled ACPI and have been using it for a while, but would like to get ACPI working.
When I did the install from the livecd it would hang when loading the kernel. I would see the progress indicator get to 99% and then my computer froze. I disabled ACPI from the options and was able to install.
But I never got any error messages or any other output so I don't know what module was causing the problem when being loaded.
I've built several computers and installed Ubuntu on each one, and I've never had problems until my latest build. Here are the problems:The computer requires acpi=off to boot, and it won't boot with acpi=ht. I've searched for this, and there's a widely reproduced acpi troubleshooting guide that says that this means that there's something wrong with the acpi tables themselves, but I haven't found any fixes.If I go ahead and use acpi=off, then the computer works fine, but it hangs on shutdown. I've searched for this too, and the consensus seems to be to remove acpi=off from the boot options. This, of course, is not an option for me.
I have an old laptop (asus M6 ca. 6 year old) with dual boot linux windows. Untill Saturday linux=suse 11.0, Saturday I have made an upgrade to opensuse11.4. I have boot up/down many times almot everything was working properly except the battery status ... I have thought .. "I'll think about it later".
Then out of the blue on sunday my laptop does not boot anymore, the boot hangs. I then have realized taht the failsafe boot was working properly.... ok I have remembered the wrong battery signal and tried the normal boot + acpi=off .. and .. it boots!
OK, the acpi is the problem. I have never made an update of my BIOS (this means it is now old), but I do not really want to update it now. with suse 11.0 the acpi was working properly, I have never have touched the acpi boot option and I had all acpi functionality working (battery, suspend .. etc)
how to let acpi work (at least for the main features .. batetry, fan speed, HT ... etc)?
It can be that the old kernel boot was using some "specific flags", (an installation is cleverer than an upgrade ..?!?!) but unfortunatelly it looks to me that nothing has remained from the old installation .. so I do not know ...
It's only been a couple of days since I formatted my toshiba laptop's hard drive (i was running fedora without significant problems) and installed slackware 13.1 32bit. I did a network install because the dvd drive is not functioning properly. everything installed fine with the hugesmp kernel, but I started not being able to boot the laptop every single time I wanted to (especially after a reboot but also after a power up).
my observations:
-the pc might freeze in the very first toshiba logo screen (where you are prompted to press F2 to enter BIOS)
-or it might freeze when I get the lilo boot loader (not even the count down to choose kernel starts) - but i CAN use the arrows and press 'enter' to choose to load a kernel manually
-or just after it loads the kernel and the bios checks
-or during boot after in loads ACPI thermal zone
-or a little later during boot when the dhcpcd if broadcasting for a dhcp lease.
the first 3 are freezes, the last 2 are resets. especially if i need to reboot (or get the resets of the 2 last case), I will surely get stack in one of the first 3 cases afterwards! i have observed that rarely, after such a reset, if it actually gets stack in the toshiba logo, i might be able - pressing the poiwer buttonj repeatedly to actually overcome the 'freezing' there at which time i'll get to the lilo loader (the count down timer will not.. count down), but i can press 'enter' and I will finally get stack after loading the kernel and bios checks
So I have to powerdown the laptop and start all over again. Sometimes the whole boot process will proceed smoothly. and i'll get to a login prompt, and when I do I can keep the laptop up and running for virtually ever. that is it doesn't seem to be slackware related... Hwever the problems started after I installed slackware. I didn't have any problem with the fedora installation and i wonder if it has something to do with the network boot.... additional note, with feodra i didn't have a problem restarting or shutting down the laptop. now if i restart, the pc will go through the process of shutting down, but it will never actually reboot - i'll have to do it manually..
I just installed Fedora 12. When I boot, only the following three lines are printed: pnp 00:09: can't evaluate _CRS: 12298 ACPI: Expecting a [Reference] package element, found type 0 Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) I first installed Fedora using a RAID 1 setup that mirrored each partition, so I thought the problem was coming from GRUB and confusion from what to boot off of. However, I reinstalled Fedora using a simple single drive setup (left the second drive without any partition), and the same error was returned. Is this an ACPI issue with this particular motherboard/BIOS? Any ideas for how I can fix this?
I've got two laptops running Ubuntu. Both have had Lucid installed from the live cd. I have upgraded one of them to Maverick. Both distributions are running great after they boot up, but I haven't experienced any faster boot times with either distibution. Both boot to Bios and then the screen goes black with a blinking cursor in upper left corner of the screen. The black screen remains for 30 to 45 seconds and then I get the Ubuntu splash screen for maybe 5 seconds, and then desktop. Why am I not seeing faster boot times? I realize 45 to 60 seconds is good compared to other os's, but I anticipated much faster boot times. Shut down on the other hand is quite fast at maybe 5 to 10 seconds. Does anyone else get this black screen on boot? Seems like wasted time cause I can't tell what's going on during the time there is a black screen. This is not a real big deal breaker, as I don't reboot very often, but I just wonder why bootup isn't faster.
Well today I decided that I couldn't wait for the offical release of 10.04 LTS, so I upgraded from 9.10 to 10.04 LTS Beta 2. After realizing that many problems had come with that update, I decided to just format my Ubuntu partition and reinstall it. Somehow my GRUB stopped working from when I formatted Ubuntu, so I whipped out the old Toshiba recovery disk for Windows Vista 32bit. After many attempts to have the recovery portion of the disk fix all of my problems and seeing no results, I decided that reinstalling Ubuntu (and GRUB) might make everything all better. Well it didn't. Grub shows my Windows partition but fails to boot it. After selecting it, it goes to a blank screen and stops responding. And to add to all of my problems, my BIOS has changed slightly. It no longer shows/or responds to F2 or F12 when I tried to give another try at that Toshiba recovery disk. That kinda sucks since I can't choose what to boot. Please help me!! I really don't want to have to format my entire hard drive and try to install Windows Vista again (Not that Vista is anything anyone should love) I have many expensive programs that can only be activated a certain amount of times. I don't even think that I could reinstall Vista since my BIOS won't let me boot the CD/DVD drive.
In configuring CNC controller system, latency-test must be run to find maximum jitter of the system. It counts about 17,000 ns for few minutes, then it suddenly rise to 260,000 ns. It is impossible to control CNC with such large jitter.
In tracing this problem, I found that Award BIOS setting "Delay Prior to Thermal" is firmly engaged in making a problem. When I set this setting to 4 minutes, it makes large jitter periodically with exact 4min 15sec period. When I changed this setting to 8 minutes, its jitter is 8min 15sec period.
But, there is no option to disable this BIOS setting.
I heard that ACPI enabled OS can take over the ACPI function of the BIOS (which may include this "thermal" setting), but RTAI tuned kernel don't include ACPI modules.
Is there any solution to this problem ? If I recompile kernel with RTAI with ACPI processor module enabled, would it be a another problem maker ?
I have installed Ubuntu 10.10 Minimal on a 2GB USB using CLI and it is working very well after adding a few applications. But this USB will be used only on machines other than my own - likely with Windows as the only OS. And it is not comfortable for me to go into the BIOS of a strange machine to change the order of booting and afterwards go back to reset the order , especially with the owner looking on, obviously worried, and wandering whether his machine will still be working!
So my question: Is there any way to boot from a USB without having to go into the BIOS? code...
I installed Debian 5.03 Lenny successfully on my machine. I got this error during boot: ACPI : invalid PBLK length [5]. After that the Operating System boots properly and starts normally. What does this error statement mean? Is it safe to work with this installation despite this error?
I've had FC11 x86_64 running for awhile based on an upgrade from FC10. I powered down one night then when I tried to boot the next day the system just sat at the BIOS prompt "Verifying DMI pool data...". I opened the case to check all cables - all fine. I've run a memtest, also fine. I then suspected a bad HDD so I ran the Seagate tools from the Ultimate Boot CD (fast test) and both HDDs came up fine. BIOS can see both disks fine, too. I stuffed around with fixmbr and fixboot and got one step further, with it sitting at "invalid operating system" or something like that. I was able to use Linux rescue mode to mount the old filesystems fine.
Today I've completely blown away all my old partitions and started from scratch. After successfully completing an install with custom disk layout (identical to old layout) it still just sits at "Verifying DMI pool data..". Do I have a bad sector in my boot block? Possible BIOS issue? Is there some tool to re-write the boot block?
