** Changed in: linux
Status: In Progress => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/294123
Title:
2.6.27 SATA drives not accessible at boot time, 2.6.24 working
To manage notif
This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Seems that the reset issued by the driver on init somehow "disconnects" the
drives. At least, that's my interpretation of the fact that
"libata.force=1:norst" makes it work...
Does anyone have a more technically funded explanation of this? Maybe one of
the developers of ata_piix ?
--
2.6.27 SA
Problem persists for Lucid, see updated description above
** Tags added: 10.04 2.6.32-22-generic 2.6.32-22-server jaunty karmic
lucid
** Description changed:
System info:
Hardware:
Mainboard MSI 965P Neo2, Intel 965 chipset, ICH8 southbridge, chipset 82801H,
One SATA Samsung Harddisk 3
Hi All,
I have the same problem on a Dell Inspiron 6400 with an Intel SATA
controller 82801G (ICH7 Family) on a Seagate SATA Disk ST96812AS.
i'm gonna write here my experience, hoping that this can help having
this bad bug solved as soon as possible
yesterday i executed the dist-upgrade from kub
Same bug.
Installed Ubuntu 9.10 through wubi in a Dell Latitude D520.
I've booted with no acpi options and I could boot.
How to do it:
- In grub, select the option "Ubuntu, Linux 2.6.31-14-generic"
- Edit the options
- Erase 'quiet splash'
- Add 'noapic nolapic noacpi acpi=off apic=off' (some of
I just found a workaround for 2.6.31-14:
with the kernel parameter
libata.force=1:norst,2:norst,3:norst,4:norst
all the disks come up working with the ata_piix driver.
During boot, there is an error message from the kernel, but this doesn't
seem to hurt...
--
2.6.27 SATA drives not accessible
I just did som investigation of the source code of ata_piix.c and although I'm
not familiar with driver programming I think the issue is that ata_piix sees my
sata controller, which is in IDE mode, and cannot be switched to AHCI, as a
controller in AHCI mode.
In the dmesg output I see
MAP [P0
linux-kernel-bugs #12470 IMHO describes a different issue (timeout),
when you look at the dmesg output, you will find that in #12470 the
controller responds with a message that the drives are slow to respnd,
whilc in this bug here the controller doesn't even make an attempt to
connecto to a drive a
Also affects Karmic beta with kernel 2.6.31-14-generic - exactly the
dame results and dmesg output. Also, all_generic_ide doesn't work for
this distribution, so the only known workaround doesn't work anymore...
** Tags added: 2.6.31 2.6.31-14-generic 9.10
** Description changed:
System info:
** Tags removed: needs-upstream-testing
** Description changed:
System info:
Hardware:
Mainboard MSI 965P Neo2, Intel 965 chipset, ICH8 southbridge, chipset 82801H,
One SATA Samsung Harddisk 300GB, One SATA optical drive, both connected to the
chipset's SATA channels 3 and 4 (behaviour
Yes, this issue still exists in 9.04 with kernel 2.6.28-13
Plus: The all_generic_ide option isn't supported anymore, maybe the generic ide
driver was excluded from the standard kernel build.
Kinda annoying this issue...
--
2.6.27 SATA drives not accessible at boot time, 2.6.24 working
https://bu
Unfortunately it seems this bug is still an issue. Can you confirm this
issue exists with the most recent Jaunty Jackalope 9.04 release -
http://www.ubuntu.com/news/ubuntu-9.04-desktop . If the issue remains
in Jaunty, Please run the following command from a Terminal
(Applications->Accessories->T
Forgot to say. This is a computer with an Intel Corporation 82371
AB/EB/MB PIIX4 IDE (rev01) IDE controller, and a single ATA (not SATA)
hard disk, a CDROM drive, and a floppy drive.
--
2.6.27 SATA drives not accessible at boot time, 2.6.24 working
https://bugs.launchpad.net/bugs/294123
You rece
I've encountered this problem after upgrading from 8.04 to 8.10.
The 2.6.27-11-generic and 2.6.27-9-generic kernels installed by 8.10
fails in exactly the manner described in this bug report, while the
2.6.24-23-generic kernel installed by 8.04 works.
--
2.6.27 SATA drives not accessible at boot
My kernel is the 2.6.27-10-generic from the latest intrepid update... It
was like this from 2.6.27-7-generic onward, and the same with a custom
compiled 2.6.26 "vanilla" kernel. A custom compiled 2.6.25 worked,
however, as well as the standard intrepid "linux-ports-2.6.25".
--
2.6.27 SATA drives
** Changed in: linux
Status: Unknown => In Progress
--
2.6.27 SATA drives not accessible at boot time, 2.6.24 working
https://bugs.launchpad.net/bugs/294123
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
What kernel version? 2.6.27.10_generic or custom compiled? This is very
strange...
--
2.6.27 SATA drives not accessible at boot time, 2.6.24 working
https://bugs.launchpad.net/bugs/294123
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Sorry that I dare to express my disagreement with your analysis, Morgan. I
think we're in fact seeing two different issues here.
When I look into the dmesg output you posted to the kernel bug report, I can
see "SRST failed" messages from the kernel driver, which - as you wrote - in
fact seem to
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=12470
Importance: Unknown
Status: Unknown
--
2.6.27 SATA drives not accessible at boot time, 2.6.24 working
https://bugs.launchpad.net/bugs/294123
You received this bug notification because you are a member of Ubun
I also filed a bug report for this bug.
This bug: http://bugzilla.kernel.org/show_bug.cgi?id=12470
Root delay bug: http://bugzilla.kernel.org/show_bug.cgi?id=12452
--
2.6.27 SATA drives not accessible at boot time, 2.6.24 working
https://bugs.launchpad.net/bugs/294123
You received this bug notif
By the way, I filed a bug report for 2.6.28 on the rootdelay problem. If
they acknowledge it, which I've found that others are having the same
problem, hopefully they'll make a patch up to 2.6.28-1 once they have
enough fixes. If 2.6.28 STILL doesn't work once the rootdelay thing is
sorted out (whi
The transfer rates are reasonable, but I noticed my system seems to run
really slow...
I got it working without all_generic_ide or ata_piix though!
Delete all_generic_ide and increase your rootdelay= to 240. It takes a
little longer to boot (negligible) with no all_generic_ide, but seems to
run f
Sorry, I must make a correction to my last statement: After having done some
tests with bonnie, and looking at the hdparm output, it really doesn't seem to
make too much difference whether all_generic_ide or ata_piix is used.
hdparm also shows that most features of the hard drives are enabled, an
Thank you Morgan for the description of the workaround. I also got my
system up and running with the "all_generic_ide" option, but it feels
substantially slower than under the 2.6.24 or 2.6.25 kernel, where
ata_piix takes care of it At boot time, the disk ist "noisier", it
sounds as if there ar
And also:
"Per a decision made by the Ubuntu Kernel Team, bugs will longer be
assigned to the ubuntu-kernel-team in Launchpad as part of the bug
triage process. The ubuntu-kernel-team is being unassigned from this bug
report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more
informat
Kind of an update here-
I tried using the second-latest release of the Linux kernel - version
2.6.27.10. I compiled from source and installed. It works with the following
boot options:
all_generic_ide
rootdelay=240
It does work, but takes longer to boot up. The all_generic_ide option doesn't
ap
Additional info:
It seems to be between kernel versions 2.6.25 and 2.6.26 where it stops
working. I am tied to ata_piix, since my ICH8 chipset is a "non-raid" version,
which doesn't support AHCI mode, so I have to run the controller in IDE mode.
I already tried a patch to force the chipset into A
Thank you for the hint to bug 289754 .
Unfortunately, however, the issue isn't solved with 2.6.27-10-generic for me.
Also, it seems that bug 289754 is about an issue with the driver for the nvidia
chipset SATA controller, where in my case it is the intel ICH8 chipset driver
(ata_piix)...
Also, i
Cool. When I get back from the mountains I'll upgrade. Does it show up
in aptitude or need to be downloaded somewhere else?
--
2.6.27 SATA drives not accessible at boot time, 2.6.24 working
https://bugs.launchpad.net/bugs/294123
You received this bug notification because you are a member of Ubunt
I had this problem too as i reported in bug 289754 . Stable kernel fixes this
issues from 2.6.27.5 and 2.6.28-rc3
Today i have installed 2.6.27-10-generic that solves the issue :)
--
2.6.27 SATA drives not accessible at boot time, 2.6.24 working
https://bugs.launchpad.net/bugs/294123
You receive
Yeah, I'm having this problem too. Does anyone have their system working
with 2.6.27-9?
--
2.6.27 SATA drives not accessible at boot time, 2.6.24 working
https://bugs.launchpad.net/bugs/294123
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Could anyone post here as soon as the problem has been reproduced by
someone else? I'm feeling a bit lost currently, and I'm not sure whether
the "all_generic_ide" option is a fully viable solution rather than just
a workaround to get it up and running at all...
--
2.6.27 SATA drives not accessib
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
Status: Incomplete => Triaged
--
2.6.27 SATA drives not accessible at boot time, 2.6.24 working
https://bugs.launchpad.net/bugs/294123
You received this b
Thank you, I just checked the bug and the workaround, but my bug seems to be a
bit different, also the workaround didn't work for me...
However, I found that when I boot wit "all_generic_ide", the system comes up.
But why is this only necessary on 2.6.27 and not on 2.6.24? Also, the network
hard
Hi mklemm,
This may be related to or even a duplicate of bug 290153 . Care to take
a look. There's a workaround mentioned there that you may want to try.
Thanks.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
2.6.27 SATA drives not accessible at boot time, 2.6.24 working
ht
Ifound the following thread on the interet, which seems to be related:
http://linux.derkeiler.com/Mailing-Lists/Kernel/2008-04/msg05440.html
But for the problem they mention there, they already put in a patch for
2.6.25, so maybe if similar symptoms are still there in 2.6.27,. it is
soemthing els
** Tags added: piix
** Changed in: linux (Ubuntu)
Sourcepackagename: None => linux
--
2.6.27 SATA drives not accessible at boot time, 2.6.24 working
https://bugs.launchpad.net/bugs/294123
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
And here is the dmesg output from a WORKING 2.6.24 kernel, just for
comparison. We can see that there are no really interesting differences
besides the "ata3: SATA link down" and "ata4: SATA link down" messages.
** Attachment added: "dmesg output from running 2.6.24-19-generic kernel"
http://la
Here is the dmesg output captured from the initramfs shell. Note: the
sda disk correctly initialized and mounted in this listing is only the
USB flash memory storage device which i plugged in to capture the dmesg
output... The internal drives are still unusable.
** Attachment added: "dmesg output
** Attachment added: "lspci-2.6.24-19-generic.txt"
http://launchpadlibrarian.net/19385352/lspci-2.6.24-19-generic.txt
--
2.6.27 SATA drives not accessible at boot time, 2.6.24 working
https://bugs.launchpad.net/bugs/294123
You received this bug notification because you are a member of Ubuntu
41 matches
Mail list logo
