Militantly FREE software support.
Militantly FREE software support.
NavigationUser loginWho's onlineThere are currently 1 user and 30 guests online.
Online users
Highest Users
Linux NewsClick the above for your daily dose of Linux news. Food for ThoughtWe are now making demands that will cost the nation something. You can't talk about solving the economic problem of the Negro without talking about billions of dollars. You can't talk about ending slums without first saying profit must be taken out of slums. You're really tampering and getting on dangerous ground because you are messing with folk then. You are messing with the captains of industry.... Now this means that we are treading in difficult waters, because it really means that we are saying that something is wrong ... with capitalism.... There must be a better distribution of wealth and maybe America must move toward a Democratic Socialism. Spam?See spam posts on this site? If so, please don't reply to the spam! Instead, just report the URL to the webmaster. |
SATA on kernel 2.4.27: lost interruptHope this helps someone in the same situation as I was. Felipe. *PROBLEM*: I get the following error messages *BACKGROUND*: I'm installing a SATA hard drive (Seagate ST3500630as) and *SOLUTION*: *THINGS TRIED THAT DID NOT WORK* relevant dmesg output before the problem was fixed: [1] [2] [3] [4] [6] [7] [8] -- Bookmark/Search this post with: 
|
• Debian Weekly News - Essential reading for any Debian fan. • Documentation - Debian's own authoritative documentation, including installation docs. • FAQ - Got questions about Debian GNU/Linux? • From Windows to Debian - Tips for converting from Windows to Debian GNU/Linux • Package of the Day. • Security - Security information and alerts! • Bug System - Bug tracking and instructions on reporting bugs. • CD Images - Where/how to get Debian GNU/Linux CD images. • Mailing List Subscription - Dozens of Debian-specific support mailing lists! • Mailing List Archives - Searchable archives of Debian's mailing lists. • Free Software Guidelines - Learn Debian's idea of what "free" software really is. • Package Listings - A very valuable tool: searchable, integrated with bug reports. • Apt-Get Sources - Sources for *.debs which are not official Debian packages. • Backports - Unofficial new software packages that have been "back-ported" to work with the Debian stable/official release. • Developer's Corner - Info about the people behind Debian, policies, and how to package *.deb files.
SATA on kernel 2.4.27: lost interrupt
Felipe G. Nievinski wrote:
> *PROBLEM*: I get the following error messages
> dma_timer_expiry: dma status == 0x24
> lost interrupt
> DMA interrupt recovery
> when trying to
> fdisk /dev/hde
Shouldn't *fdisk /dev/hde* have raised a flag as it is a SATA disk and
should be detected as /dev/sdX (X=a,b,...)?
/KS
--
hda: lost interrupt
Hello All,
I just installed the Debian Etch 4.0 on my system. It will not
complete bootup however. It keeps hanging on "hda: lost interrupt"
and eventually fails to boot entirely.
I previously had Debian Etch "Testing" installed. It has been working
fine for the past month up to the moment I tried installing 4.0.
I tried re-installing 4.0 three times all with the same result.
My system is an Intel Core2 Duo. I'm trying to install Debian Etch 4.0 AMD64.
Does anyone know how to recover from this error?
Thanks,
Dallas
--
hda: lost interrupt
Dallas Clement wrote:
> Hello All,
>
> I just installed the Debian Etch 4.0 on my system. It will not
> complete bootup however. It keeps hanging on "hda: lost interrupt"
> and eventually fails to boot entirely.
>
> I previously had Debian Etch "Testing" installed. It has been working
> fine for the past month up to the moment I tried installing 4.0.
>
> I tried re-installing 4.0 three times all with the same result.
>
> My system is an Intel Core2 Duo. I'm trying to install Debian Etch 4.0
> AMD64.
>
> Does anyone know how to recover from this error?
>
> Thanks,
> Dallas
>
>
My laptop Turion 64 requires using 'noapic' to boot and run. You can
add this to the kernel 'command line' (at the boot prompt) for a one
time test to see if it helps. If it does, edit your boot loader 'menu'
to append this string to the entries for your kernel. You will need to
read up on how to do these things for your particular boot loader.
Other options you might try (some that I've heard about but not tried)
are 'pci=no', 'acpi=no', 'acpi=no-idle' and 'nolapic'.
I have no information on the possible down side of using any of these,
but hey, if it lets you boot and things run, you're ahead of the game ;)
I hope this helps.
Bob
hda: lost interrupt
Bob McGowan wrote:
>
> My laptop Turion 64 requires using 'noapic' to boot and run. You can
> add this to the kernel 'command line' (at the boot prompt) for a one
> time test to see if it helps. If it does, edit your boot loader 'menu'
> to append this string to the entries for your kernel. You will need to
> read up on how to do these things for your particular boot loader.
>
> Other options you might try (some that I've heard about but not tried)
> are 'pci=no', 'acpi=no', 'acpi=no-idle' and 'nolapic'.
>
> I have no information on the possible down side of using any of these,
> but hey, if it lets you boot and things run, you're ahead of the game ;)
>
> I hope this helps.
>
> Bob
And if you succeed to boot that system, you can than install the kernel
from version that worked.
--
hda: lost interrupt
'noapic' solved the problem. Thanks!
On 5/11/07, Bob McGowan wrote:
> Dallas Clement wrote:
> > Hello All,
> >
> > I just installed the Debian Etch 4.0 on my system. It will not
> > complete bootup however. It keeps hanging on "hda: lost interrupt"
> > and eventually fails to boot entirely.
> >
> > I previously had Debian Etch "Testing" installed. It has been working
> > fine for the past month up to the moment I tried installing 4.0.
> >
> > I tried re-installing 4.0 three times all with the same result.
> >
> > My system is an Intel Core2 Duo. I'm trying to install Debian Etch 4.0
> > AMD64.
> >
> > Does anyone know how to recover from this error?
> >
> > Thanks,
> > Dallas
> >
> >
>
> My laptop Turion 64 requires using 'noapic' to boot and run. You can
> add this to the kernel 'command line' (at the boot prompt) for a one
> time test to see if it helps. If it does, edit your boot loader 'menu'
> to append this string to the entries for your kernel. You will need to
> read up on how to do these things for your particular boot loader.
>
> Other options you might try (some that I've heard about but not tried)
> are 'pci=no', 'acpi=no', 'acpi=no-idle' and 'nolapic'.
>
> I have no information on the possible down side of using any of these,
> but hey, if it lets you boot and things run, you're ahead of the game ;)
>
> I hope this helps.
>
> Bob
>
>
--