I have been running a dual-boot, Windows 7 and Ubuntu 10.10 system with the disks set for IDE with no problems. I have just attempted to change the disk system to AHCI and, whilst I can boot into Windows 7, I am unable to boot into Linux and get the error: "Alert! /dev/disk/by-uuid/5d773307-a046-40fa-ba29-728611bc7eed does not exist" I am new to Linux so am unsure where to go from here. I have reverted to IDE for the moment and it boots Ok.
I'm doing a clean install on a new machine, and when I tried to boot the install DVD, ISOLinux gave me the following error:
Code: Could not find kernel image: linux After some experimentation, I found that switching the SATA mode in the BIOS from AHCI to Native IDE solved the problem and installation is proceeding normally.
However, I want AHCI enabled. (I think, unless someone has a compelling reason why I shouldn't.) My web-searching suggests that if the system is installed in IDE mode, it won't boot if I switch to AHCI afterwards. Is this a common problem? Is there a workaround? Is it a motherboard issue?
Here is my problem: In short, it takes forever (6 min), and lots of prodding to get Ubuntu to boot. Im running a Toshiba NB305 netbook (Bios 1.40), set up for dual boot with 10.04 UNR. Windows partitions boot fine. Can boot 10.04 from USB stick.
Here how I try to boot: From grub menu select "Ubuntu, with Linux 2.6.32-22-generic" If it doesn't work, I run the recovery version, and then run the regular one again. Somehow that resets stuff.
Yesterday I was on my Windows computer doing homework. Once Football came on, I hit the Standby button on my keyboard and walked out of my room. Came back at halftime to discover that my system never went into Standby. I turned on my monitor and saw a bunch of code repeating. I don't remember it all, but it was something to this effect
Super Block not compatible with current BIOS scanning for *insert system file here*.... not found scanning for floppy drive... not found scanning for cdrom1... not found
So I hit the restart button on my tower. When it restarted, I was brought back to the same screen. So I unplugged the power cord from my computer and counted to 10. I plugged it back in and this time I got my mobo logo screen and the system appeared to start up fine, until I got to the SATA drive scanning screen. When my computer would scan for my SATA hard drive, it would idle for several minutes, during which a series of periods (".") would show up until eventually I get a message that says: WARNING! - Something wrong with your hardware!
I have troubleshooted a number of things so far: 1) I took my SATA Hard Drive out of my computer and plugged it into my Linux computer and the system booted fine! I used the same SATA cord, so I know both the drive and the cord ARE WORKING! 2) I tested the power cord from the power supply that runs to my HD and it is working just fine. 3) I plugged the HD back into my Windows computer (the original one it was in when I started having this problem) and I ran GParted. When the GUI came on, I could not see any drives and there was a message at the bottom of the window saying that no devices could be found. This was no surprise to me because I watched the verbose mode as GParted booted and it gave error messages when it tried scanning for my hard drive. 4) I have also tried plugging it into the other SATA ports on my motherboard. 5) I tried flashing the mobo BIOS. The flash worked just fine (or at least it appeared so), but the HD is still not being found on the system boot scan.
Bottom line, I know the hard drive is fine because it worked in my Linux computer. So I am thinking it has to be the motherboard. But before I go out and buy a new Mobo and CPU (and possibly new RAM), I wanted to quickly jump on here.
Using a Eee 900A netbook by Asus. By pressing Fn + F2, I can disable or enable the wireless chip on the netbook, a blue LED indicates the status. I've been able to connect to wireless networks just fine with this netbook. However, if the wireless chip ever becomes disabled, I have to reboot to get my network connection back. This generally happens when suspending. For some reason the LED will be off and I have to hit Fn + F2 for it to light up again.
However, after doing so, Linux will not reconnect to the network. It simply changes the wireless status from "wireless is disabled" to "device not ready". Even worse, I've recently had issues with the chip being enabled at boot, thus making it nearly impossible to get connected. I've searched around on-line but haven't found much of anything useful on this. This happens on all kinds of different distros including Ubuntu 9.10 Netbook, EeeBuntu 4 beta, Jolicloud and Ubuntu 10.04 Netbook.
I have a USB stick with a mechanical write protection (a small switch that disables writing on the stick). I have installed Ubuntu 10.04.1 on this device usung the startup drive creator. If the switch is in the position that allows writing, Ubuntu boots as expected. But if I switch to write protection, I only see a blinking cursur. Because it is a live system on the stick I expected that it should work as well, because nothing should be written to the stick. Does anyone have an idea why it behaves like this and how I can change it?
I'm struggling with my computer to get it to run a Windows 7 x64 machine as domU with VGA passthrough using Xen and Fedora 14 as dom0.
The problem is that when I enable IOMMU in BIOS, it simply freezes during boot. If booting with the dom0 pvops kernel via Xen it stops at the "IOMMU enabled" message. If I boot the regular unpatched kernel without the Xen; all I see is naught but a blinking cursor at the upper left corner.
I tried booting from the Fedora 14 liveCD and the lubuntu 10.04 liveCD and they booth freeze in a simlar fashion afer I get past their bootloaders.
The Windows 7 partition boots just fine and I can do all sorts of stuff in it (such as conducting computationally intensive tasks) without problems.
I have 4GB of memory but i just found that if i enable Software/Hardware remapping in the bios the bios will then show all 4GB usable from 2.5GB but then Ubuntu refuses to boot up saying a kmiser type message but it will if i disable those 2 options. is there any way to fix it apart from reinstalling ubuntu?
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 ...
This affects any version of Linux I have managed to put my hands on, 32 bit as well as 64 bit, except XenServer 5.6. This does not affect Windows 7 x64, GRUB bootloaders and FreeDOS/MSDOS based boot CDs. Also, Linux boots fine with the BIOS IOMMU feature disabled.What happens is that the 64-bit Linux install, bootCD, installCD, liveCD or USB hangs almost immediately after GRUB with naught but a blinking cursor at the upper left corner. Some liveCDs manage to show some kind of boot splash before it hangs. USB peripherals such as the mouse and the USB stick gets severed at the moment of the hang. The num-lock led is on but the keyboard is irresponsive to *-lock toggles.
In the 32-bit version it takes a little longer before the hang and the USB peripherals stay on at the event of the hang, but the keyboard is irrespnsive in the same manner. It also spits out error messages.
I recently decided to install Ubuntu 11.04 on a 320gb hitachi sata hard drive. This is going into a new system with an Asus MB, AMD Proc, not sure if this matters. Anyway I can not set the bios to use ahci and see the sata drive. I can only use IDE mode with sata enabled. Asus support says to install ahci for os. If I boot into the USB install key and attempt to the install OS I receive a read/write error. I have another drive on IDE that has 11.04 on it and if I try to format the new drive and partition it with Disk Utility it fails with "Error formatting drive: error creating partition table: helper exited with exit code 1: error calling fsync(2) on /dev/sdb: Input/output error". I have tried to use dd and fdisk but I don't believe I need these until I do something else first just not sure how or where to look.
If I change my sata mode from IDE to AHCI grub won't show (cursor goes to top left) when I power on my system. After that, I press the reset button and my grub shows ok.
So, to use AHCI I always have to use the reset switch button.
Using Ubuntu 10.10 with 2.6.35-23-generic - 64bits
I have a Fedora 11 PC, which I want to connect to the ldap server at my organisation. When my /etc/ldap.conf file is in place, the machine will not boot past "starting system messagebus" and just hangs there. I have to press the reset button, and boot it into single user mode, and remove /etc/ldap.conf, and only then will it boot. The ldap.conf file is fine, I think, because if you boot the machine up without ldap.conf, then log in.
I can put ldap.conf in place and immediately I can see all the user accounts etc. from the ldap server. If I then reboot, with ldap.conf in place, it hangs on boot again. I found a bug report for FC5 which stated this problem, but there was no solution. There was a workaround, making messagebus starting later in the boot process (move it from S22 to S27 in rc3/5.d), but that didn't help in my case.
My ldap.conf contains this (I've removed my actual ldap info): host my.server.ip.addr base dc=my,dc=dn uri ldap://ldap.mydomain.com ssl no tls_cacertdir /etc/openldap/cacerts pam_password md5 bind_policy soft
As I say, I think the ldap config is fine, because you can start it manually once the machine has booted up without an ldap.conf in place. I lifted it from a Centos client, which works fine and doesn't have the same problem with booting that Fedora does.
In order for TRIM to work on an SSD with encryption, I need to make sure to "select the AHCI option before installing the operating system."Does anybody know how to do this? I have no idea what this is talking about. I'll be installing 11.04 with no dual-boot. Just Ubuntu alone.
I am about to do a clean install of 10.04 (64-bit) on a ThinkPad X201. The machine will only be running Ubuntu (i.e., no dual-boot). Is there any reason to use compatibility mode for the SATA boot drive, or will AHCI work fine?
/sbin/udevd --daemon eats about 10-15% of cpu which is quite high. I found out that it is caused by AHCI. If I turn it off in bios, udev takes only about 0-1% of cpu (which I consider normal). However turning AHCI off is deadly for Windows Vista (I have dual boot) - it always ends up with BSOD. Actually, I don't even know what AHCI does. Of course I found some information on the net but I didn't found whether there are some advantages for me. Is it worth 10-15% of cpu (consequently shorter battery life)? On the other hand, I have no interest in changing my bios settings every time I boot to Windows so it would be much confortable to have it turned on all the time. The best solution would be to find out why AHCI does this and how to configure udev to avoid it. And I don't know how.I have OpenSuse 11.2, kernel 2.6.31.12
How can I force my kernel to use the ahci driver when both the ahci & sata_nv are built into the kernel.?
My MSI board bios doesn't have an option for "AHCI MODE". The only sata option that it has is "called "On Chip Sata" & is located under "Integrated Peripherals. Also, the only values available for "On Chip Sata" are enabled or disabled. If I choose the disabled option, the sata drives arn't found & bootup fails.
I tried to tell the kernel to use the ahci driver by appending kernel options to my Grub2 bootloader but they all failed.
The only thing I can think of that is left to do is to re-build my kernel with CONFIG_SATA_NV as a loadable module & CONFIG_AHCI as a build-in driver. With only the ahci driver available at boot, the kernel will have to use it or fail to boot.
One more thing I want to say is that my other computer with the ASUS motherboard uses the ahci driver & I have both the sata_via & the ahci drivers built into the kernel. However, it has a bios option for AHCI MODE.
(eg.) Southbridge VT8251 Serial ATA IDE Controller <AHCI>
I am using openSuSE 11.2 on a VGN-AR41L. I have also erased the preinstalled Home Vista (what a pleasure). Now to my problem. My system boots correctly but if I press the <ESC> key while booting I can see the following messages:
"Doing fast boot FATAL: mbcache module not found FATAL: ahci module not found " and the boot process continues normally.
Why this happens? Does this mean that I have a problem that I haven't discovered yet? Is it something that I can ignore? I am using SUSE Linux from version SUSE Linux 8 personal and although I am not a power user I have done my two desertions on this system and I am very happy with SUSE. I have bought SUSE Linux 8 Personal and SUSE Linux 10 all the other versions until today have been downloaded.
I have a HP Pavilion dv7-2230sa During boot I get a series of errors about ACPI and AHCI Conflicts, the result of which I have to dissable ACPI with acpi=off. However when acpi=off my wireless Broadcom b43 series refuses to enable the wifi. I just can't press the button that would enable / dissable the wifi.
The wifi is detected, the drivers and firmware are installed, however the light remains firmly in the RED.the ethernet works, sound works fine, There also seems to be an issue with the ATi/Radeon Driver being missing which is causing fatal errors at boot time and also some memory conflicts again causing fatal errors.
I have tried this laptop under opensuse 11.2 and now under opensuse 11.3M5 without sucsess - however to my dislike Ubuntu have managed to resolve this by accident between 9.4 and 9.10 but i wanna use opensuse not ubuntu i have asked them to tell me how they fixed it to share it with you but I am still plowing my way through their forum!
I want to run my Debian install in AHCI mode on my computer. It runs perfectly fine, all drivers etc work perfectly also. The computer itself is in RAID mode but with all 4 RAID channels disabled (I refuse to use any RAID arrays because I simply don't like them). However, my computer (Acer Aspire m3640/m5640, motherboard MCP73PV/630i) has greyed out the option for me to change the option from RAID mode to either IDE or AHCI. Since I do not use RAID at all, I want to change to AHCI but it is greyed out in the BIOS. This option wasn't greyed out before as far as I remember.
I also have Vista x64 installed on a SATA drive along with Debian all partitioned. I also have an empty IDE drive attached which will be used for another operating system AFTER I have changed to AHCI mode. The SATA drive has the boot flag. I use GRUB to boot the operating system. My BIOS version from American Megatrends is R01-A3 (not the latest one, but the one I need to use). My question is this, how could one possibly go about as to changing it to AHCI mode from RAID with the BIOS greying the option out. how to make the BIOS ungrey the option (if there is another option preventing it from being changed or if the harddrives need configuring etc). I am not particularly concerned if the drives need to be wiped.
I realized after spending some time performance tuning my mini Linux server that the hard drive is stuck in IDE mode, and I can't get the controller to be discovered in AHCI mode.EDIT: I should add that I'm running Vector Linux 6.0 Lite, which is based on Slackware 13.0. The Kernel version is 2.6.27.12.
The mobo in question is actually a small mini-ITX board from Foxconn. Here is a links to the specs:url.I use it for a media server, and so far the drive I'm using (Hitachi HDE721010SLA330) is working fine in IDE mode (apparently).
I have a strong suspicion that the crappy Foxconn BIOS supplied with the board is not initializing the Intel 945GC controller in AHCI mode. There is a BIOS entry for setting the controller to "Advanced", but I don't think it's doing the job.
I am using Centos 5.4 on an Intel DG451D Main Board. Two SATA drives in RAID1 mode via the main board's built in AHCI controller. It seems to work just fine but I would like to be able to monitor the state of my drives and controller, especially during a re-build and make configuration changes etc if possible, so new drives can be added etc from within the OS. Is there a way to do this within Centos or am I stuck with using just the BIOS configuration system? Apologies if this is a stupid question - I am pretty new to this and have spent several hours trying to find a solution to my question but to no avail.
Server has DQ35JO board, 8GB memory, multiple SATA hard drives. It was happily running Fedora 10, and Fedora 9 before that. I downloaded and burned the F11 DVD, booted it, did an install which is:
-- delete the LVMs -- create a 200 MB /boot on ext3, the rest of /dev/sda on ext3 as / -- reformat the swap partition on /dev/sdb1 -- leave the other file systems alone (they are all ext3)
I chose no optional packages and let it install. It finished normally and got to the "click to reboot" screen. Now, my server is completely bricked. When I power it up I get a blank screen with a blinking cursor. I cannot even get to the BIOS, or boot my Fedora DVD, much less boot the boot drive.
I have successfully installed a dual boot system with Fedora 14 on drive sdb and WIN7 on drive sda, with Fedora 14 being the major (default) OS. The system is an AM3 with a quad core CPU and all SATA drives. The drives are set to IDE mode, and I am wondering:-
1. What are the benefits of AHCI - will it improve the speed and responsiveness of my system? And
2. If it is worth installing, do I have to do a complete re-install of the OS, or is there some way of updating the installed Fedora to include and operate with AHCI mode drives?
I'm quite happy with the system as it is now, but if there is a way to squeeze extra speed out of it I'm willing to give it a go. And never having been involved with SATA drives and Linux previously, I'm completely ignorant on the subject.
