I'll try and test it this weekend. I'm on Gutsy at the moment, so do I
need to put anything in my source list to find the package?
Let me ask you a question. But a bit of history first. This machine
used to run WinXP but one day it just froze hard. When it rebooted it
got to the end of the
fishor wrote:
Rob, please subscribe yourself to the upstream bug. Fallow the link in
my previous post.
Done!
--
--
Rob Miracle
[EMAIL PROTECTED]
http://www.robmiracle.com
--
failed to set xfer mode error.
https://bugs.launchpad.net/bugs/112132
You received this bug notification because
Ok Rob, you have WDC WD2500JD-22HBC0 attached to ICH7, this is issue for
ata_piix module.
Forwarding this to bugzilla upstream:
http://bugzilla.kernel.org/show_bug.cgi?id=9540
Regards
Alex
--
failed to set xfer mode error.
https://bugs.launchpad.net/bugs/112132
You received this bug
PLease test this kernel:
http://de.archive.ubuntu.com/ubuntu/pool/main/l/linux/linux-image-2.6.24-1-386_2.6.24-1.2_i386.deb
or find kernel according your cpu.
--
failed to set xfer mode error.
https://bugs.launchpad.net/bugs/112132
You received this bug notification because you are a member of
if you have this issue with new 2.6.24 kernel please attach your
complete dmesg. I need to know which hardware affected.
--
failed to set xfer mode error.
https://bugs.launchpad.net/bugs/112132
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
fishor wrote:
if you have this issue with new 2.6.24 kernel please attach your
complete dmesg. I need to know which hardware affected.
Considering that I can't boot the 2.6.24 kernel, I can't get a dmsg for
it. I doubt the 2.6.22 kernel is going to report any different
hardware than the
Rob Miracle schrieb:
I doubt the 2.6.22 kernel is going to report any different
hardware than the the dmesg I posted from the 2.6.15 kernel in the
thread already.
I don't have time to care about fixed hardware, it was made a lot of
work in 2.6.24.
So i need to know only hardware, not working
fishor wrote:
if you have this issue with new 2.6.24 kernel please attach your
complete dmesg. I need to know which hardware affected.
I installed the 2.6.24-1 386 kernel and when it tries to boot, it
generates the following messages:
ata3.00 qc timeout (cmd 0x27)
ata3.00 failed to read
: [Bug 112132] Re: failed to set xfer mode error.
Date: Sat, 07 Jul 2007 11:09:56 -
I have to add that it starts the normal way too, it just takes very very
long (Progressbar isn't moving for about 2 minutes)
--
failed to set xfer mode error.
https://bugs.launchpad.net/bugs/112132
You received
I'm going to check this option in the next few days.
Thanks.
From: imperius [EMAIL PROTECTED]
Reply-To: Bug 112132 [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [Bug 112132] Re: failed to set xfer mode error.
Date: Mon, 11 Jun 2007 05:24:43 -
You could try adding irqpoll to the /boot
Hi Fishor,
The livecd doesn't work, it gives thesame errors, it does install after the
errors (only tried the text mode installation of the alternate installation
cd) but after the installation it cannot set DMA mode so it tries to set it
to DMA/33 PIO, but then fschk crashes and the system
11 matches
Mail list logo
