Public bug reported:
In the standard oneiric 3.0.0-16 kernel, the kernel iscsi support (LIO)
cannot be activated because the fabric modules, most notably
iscsi_target_mod.ko are not part of the standard distribution, nor are
they contained in any other oneiric binary package I know of.
As I have
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
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 SATA
I think, the problem is actually in the documentation of initramfs-
tools:
the examples and explanations in the initramfs-tools man pages forget to state
that you have to source ./scripts/functions for the various functions to work.
Looking into distribution-provided initramfs scripts however
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:
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
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
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
Hmmm, I'm using Karmic beta with 2.6.31.14.27, and both mouse and
wireless bluetooth keyboard are paired and controlled OK, but the Migthy
Mous doesn't generate any input events when you click one of the
buttons. It does, however, move the cursor, and the track ball is also
working.
--
bluetooth
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
** 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
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
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 not
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 are
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,
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
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,
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
Sorry, but I still don't think it's exactly the same as in #294123. I did
exactly what you proposed, with waiting for the drives up to 5 minutes, but
they never showed up, no output in dmesg, no device nodes under /dev...
However, booting with the all_generic_ide option works, but disk access
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
Public bug reported:
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 is unchanged if connected to
channels 1 and 2).
** 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
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
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
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
** 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.
Definitely - I am having a similar problem on the 2.6.27-7-generic kernel,
whereas the 2.6.24-19-generic works fine.
The details are in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/294123
It doesn't seem to be quite the same, though, so I think it wouldn't be
fair to mark one or the
27 matches
Mail list logo
