Stefan Monnier wrote:
>
> I'm trying to read a CompactFlash card via a PCMCIA adapter (first time
> I use this PCMCIA port) and am not having much luck:
>
># dmesg|grep hda
>[ 10.372034] hda_intel: probe_mask set to 0x1 for device 17aa:2010
>[ 11.213306] hda: CF 32GB, CFA DISK dr
'noapic' solved the problem. Thanks!
On 5/11/07, Bob McGowan <[EMAIL PROTECTED]> 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 en
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
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 m
I was getting this also. The smartd daemon would trigger it but that would
simply time out. Trying to mount the thing hung the system up--big red switch
time. The Western Digital drive would click click click when this problem was
occuring which was not always but enough to be annoying.
I repla
> Also my system suspends even for a several minutes.
> Does it mean my hdd is going to crash?
try with: smartmontools
[...]
Description: control and monitor storage systems using S.M.A.R.T.
The smartmontools package contains two utility programs (smartctl and smartd)
to control and monitor storag
Michał Chruściel wrote:
on Debian I get really a lot of these messages:
hda: lost interrupt
Also my system suspends even for a several minutes.
Does it mean my hdd is going to crash?
If yes, is it hardware problem, or because of misuse of fsck or mkfs?
Did you Google for this already? On a
Michał Chruściel wrote:
on Debian I get really a lot of these messages:
hda: lost interrupt
Also my system suspends even for a several minutes.
Does it mean my hdd is going to crash?
If yes, is it hardware problem, or because of misuse of fsck or mkfs?
Did you Google for this already? On a fi
On Wed, Sep 01, 1999 at 05:25:32PM -0500, Stephen R. Gore wrote:
> Jim McCloskey wrote:
> >
> > Achim Bohnet <[EMAIL PROTECTED]> wrote about:
> >
> > |> hda: lost interrupt
> > |> hda: read_intr: status=0x50 { DriveReady SeekComplete }
> >
> ---end quoted text---
>
> This looks to me like the m
Jim McCloskey wrote:
>
> Achim Bohnet <[EMAIL PROTECTED]> wrote about:
>
> |> hda: lost interrupt
> |> hda: read_intr: status=0x50 { DriveReady SeekComplete }
>
---end quoted text---
This looks to me like the message I get when I use a kernel with
DMA enabled with a buggy mobo. Try building a
Achim Bohnet <[EMAIL PROTECTED]> wrote about:
|> hda: lost interrupt
|> hda: read_intr: status=0x50 { DriveReady SeekComplete }
I've had this error-message repeatedly over the years on a laptop that
I first got early in 1995. Then it ran Slackware with a 1.2.0 kernel;
now it runs debian (slink)
11 matches
Mail list logo
