On 4/7/07, Patrick Ale <[EMAIL PROTECTED]> wrote:
And my "patch" is made obsolete :P
Jan Engelhard from the netfilter list made patch set within the
patch-o-matic tree.
Cheers Jan :D
Patrick
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On 4/7/07, Patrick Ale <[EMAIL PROTECTED]> wrote:
Hi lads,
Oh! And! I don't want to take credit for things I didn't write, which
is this exactly.
I merely got the ip_tables.h header from 2.6.20 and filtered out what
I needed to get things work.
So, the actual credit for the code in the
Hi lads,
I had some problems compiling the external netfilter modules due to
missing definitions.
I googled a lot, saw a lot of people having the same problems but no
real answer to how to fix it.
So.. I made a little patch which make things work for me, at least.
Modules that work after
Hi lads,
I had some problems compiling the external netfilter modules due to
missing definitions.
I googled a lot, saw a lot of people having the same problems but no
real answer to how to fix it.
So.. I made a little patch which make things work for me, at least.
Modules that work after
On 4/7/07, Patrick Ale [EMAIL PROTECTED] wrote:
Hi lads,
Oh! And! I don't want to take credit for things I didn't write, which
is this exactly.
I merely got the ip_tables.h header from 2.6.20 and filtered out what
I needed to get things work.
So, the actual credit for the code in the patch
On 4/7/07, Patrick Ale [EMAIL PROTECTED] wrote:
And my patch is made obsolete :P
Jan Engelhard from the netfilter list made patch set within the
patch-o-matic tree.
Cheers Jan :D
Patrick
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
On 3/5/07, Tejun Heo <[EMAIL PROTECTED]> wrote:
Dale Blount wrote:
This will probably included in the next -stable iteration. Thanks.
--
tejun
I can confirm that sata_sil is working great under 2.6.21-rc1.
I have an onboard Silicon Image SATA RAID controller and a PCI Add-on
card, also
On 3/5/07, Lee Revell <[EMAIL PROTECTED]> wrote:
Hi all,
Sorry for the confusion :)
I saw an email from an Intel guy here on this list a couple of weeks
ago if I recall correctly regarding the Interl drivers for this
specific card, with a URL, thats why I assumed this was the place to
look for.
On 3/5/07, Lee Revell [EMAIL PROTECTED] wrote:
Hi all,
Sorry for the confusion :)
I saw an email from an Intel guy here on this list a couple of weeks
ago if I recall correctly regarding the Interl drivers for this
specific card, with a URL, thats why I assumed this was the place to
look for.
On 3/5/07, Tejun Heo [EMAIL PROTECTED] wrote:
Dale Blount wrote:
This will probably included in the next -stable iteration. Thanks.
--
tejun
I can confirm that sata_sil is working great under 2.6.21-rc1.
I have an onboard Silicon Image SATA RAID controller and a PCI Add-on
card, also
On 3/4/07, Patrick Ale <[EMAIL PROTECTED]> wrote:
Hi,
I just downloaded the latest kernel drivers, daemon and microcode for
my Intel Wireless card. everything built correctly, the microcode is
placed in /lib/firmware and when running /etc/init.d/ipw3945d-start I
get the following dmesg
Hi,
I just downloaded the latest kernel drivers, daemon and microcode for
my Intel Wireless card. everything built correctly, the microcode is
placed in /lib/firmware and when running /etc/init.d/ipw3945d-start I
get the following dmesg
ieee80211_crypt: registered algorithm 'NULL'
ieee80211:
Hi,
I just downloaded the latest kernel drivers, daemon and microcode for
my Intel Wireless card. everything built correctly, the microcode is
placed in /lib/firmware and when running /etc/init.d/ipw3945d-start I
get the following dmesg
ieee80211_crypt: registered algorithm 'NULL'
ieee80211:
On 3/4/07, Patrick Ale [EMAIL PROTECTED] wrote:
Hi,
I just downloaded the latest kernel drivers, daemon and microcode for
my Intel Wireless card. everything built correctly, the microcode is
placed in /lib/firmware and when running /etc/init.d/ipw3945d-start I
get the following dmesg
Extra
On 2/26/07, Neil Brown <[EMAIL PROTECTED]> wrote:
ARRAY /dev/md1 UUID=x:x:Xx:x
and it should find the right devices and assemble them without
problems.
That's my point, this is the *only* way working at the moment when
using mdadm --assemble , since /dev/disk/by-id* tells me
Hi,
I posted this a while ago aswell :)
MD can't start anymore when /etc/mdadm.conf uses /dev/disk/by-id/* ,
it bluntly tells you there are no suiteable drives.
Since libata tends to mangle my drive order by every reboot since I
use 3 controllers and the drivers dont generate uevents always in
On 2/24/07, Patrick Ale <[EMAIL PROTECTED]> wrote:
On 2/24/07, Michael-Luke Jones <[EMAIL PROTECTED]> wrote:
One more question regarding this, I am aware its not *really* kernel
related but answering this question now will save yourself a lot of
bogus emails from me about MD
On 2/24/07, Patrick Ale [EMAIL PROTECTED] wrote:
On 2/24/07, Michael-Luke Jones [EMAIL PROTECTED] wrote:
One more question regarding this, I am aware its not *really* kernel
related but answering this question now will save yourself a lot of
bogus emails from me about MD oopses later and all
Hi,
I posted this a while ago aswell :)
MD can't start anymore when /etc/mdadm.conf uses /dev/disk/by-id/* ,
it bluntly tells you there are no suiteable drives.
Since libata tends to mangle my drive order by every reboot since I
use 3 controllers and the drivers dont generate uevents always in
On 2/26/07, Neil Brown [EMAIL PROTECTED] wrote:
ARRAY /dev/md1 UUID=x:x:Xx:x
and it should find the right devices and assemble them without
problems.
That's my point, this is the *only* way working at the moment when
using mdadm --assemble , since /dev/disk/by-id* tells me
On 2/24/07, Michael-Luke Jones <[EMAIL PROTECTED]> wrote:
But using 'fakeraid' (i.e. BIOS RAID) together with dmraid is
generally discouraged in favour of using the more stable and well
supported Linux Software RAID functionality.
Michael-Luke
I think I actually used dmraid, and the problem I
, the raid is done in the
driver, which is why you need this fancy boot disk before installing
Windows on your RAID set.
Or would you suggest me to stick with MD devices?
Cheers,
Patrick Ale
[EMAIL PROTECTED]
"kun kasvan isoksi, halun olla poro"
-
To unsubscribe from this list: send t
is done in the
driver, which is why you need this fancy boot disk before installing
Windows on your RAID set.
Or would you suggest me to stick with MD devices?
Cheers,
Patrick Ale
[EMAIL PROTECTED]
kun kasvan isoksi, halun olla poro
-
To unsubscribe from this list: send the line unsubscribe linux
On 2/24/07, Michael-Luke Jones [EMAIL PROTECTED] wrote:
But using 'fakeraid' (i.e. BIOS RAID) together with dmraid is
generally discouraged in favour of using the more stable and well
supported Linux Software RAID functionality.
Michael-Luke
I think I actually used dmraid, and the problem I
Hi All!
For my work I am using a Huawei E620 HSDPA/UMTS card, and I would like
to use it under Linux :)
Before this I had a card with only UMTS/GPRS functions and as soon as
I inserted the card some /dev/ttyUSB nodes were created, with this
card this doesnt happen, eventho the different fora
Hi All!
For my work I am using a Huawei E620 HSDPA/UMTS card, and I would like
to use it under Linux :)
Before this I had a card with only UMTS/GPRS functions and as soon as
I inserted the card some /dev/ttyUSB nodes were created, with this
card this doesnt happen, eventho the different fora
On 2/22/07, Paul Rolland <[EMAIL PROTECTED]> wrote:
Hello,
hey all,
using 2.6.21-rc1 now, all seems to work great,
thanks!
patrick
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On 2/22/07, Paul Rolland <[EMAIL PROTECTED]> wrote:
Hello,
I dont think there is one or that this reply of yours could cause it :P
Just to add my $0.02 on this point : this could also be one of the problem
I'm facing on my machine right now, but the point is that Windows supports
it
On 2/22/07, Paul Rolland [EMAIL PROTECTED] wrote:
Hello,
please no flame war
I dont think there is one or that this reply of yours could cause it :P
Just to add my $0.02 on this point : this could also be one of the problem
I'm facing on my machine right now, but the point is that
On 2/22/07, Paul Rolland [EMAIL PROTECTED] wrote:
Hello,
hey all,
using 2.6.21-rc1 now, all seems to work great,
thanks!
patrick
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Hi,
And now, for something completely different, no libata ;-)
I was wondering if any of you ever got the sky2 driver working
(gigabit network card found in most Siemens E laptops).
Which kernel I am trying, 2.6.17-gentoo (the kernel on the install
CD), 2.6.20, the latest gits, nothing works.
On 2/21/07, Patrick Ale <[EMAIL PROTECTED]> wrote:
On 2/21/07, Vincent Legoll <[EMAIL PROTECTED]> wrote:
In the latter case it might explain why you see one master connected
to one bus and a slave to the other. If you use legacy SATA mode you
should just see drive 0 and d
On 2/21/07, Vincent Legoll <[EMAIL PROTECTED]> wrote:
Argh I think I screwed the mail threading, I was refering to:
http://ussg.iu.edu/hypermail/linux/kernel/0702.1/1060.html
From: Patrick Ale
Date: Sun Feb 11 2007 - 05:28:21 EST
Sorry
Yea, I know.. I mail too much.. too much time at
On 2/21/07, Vincent Legoll [EMAIL PROTECTED] wrote:
Argh I think I screwed the mail threading, I was refering to:
http://ussg.iu.edu/hypermail/linux/kernel/0702.1/1060.html
From: Patrick Ale
Date: Sun Feb 11 2007 - 05:28:21 EST
Sorry
Yea, I know.. I mail too much.. too much time at hands
On 2/21/07, Patrick Ale [EMAIL PROTECTED] wrote:
On 2/21/07, Vincent Legoll [EMAIL PROTECTED] wrote:
In the latter case it might explain why you see one master connected
to one bus and a slave to the other. If you use legacy SATA mode you
should just see drive 0 and drive 1.
Oh
Hi,
And now, for something completely different, no libata ;-)
I was wondering if any of you ever got the sky2 driver working
(gigabit network card found in most Siemens E laptops).
Which kernel I am trying, 2.6.17-gentoo (the kernel on the install
CD), 2.6.20, the latest gits, nothing works.
On 2/18/07, Patrick Ale <[EMAIL PROTECTED]> wrote:
Hi all,
I just tried to compile Torvald's upstream-linus and ran into a compile error.
Disregard, I ran make oldconfig again, didnt get prompted for any
configuration options, and now it does compile.
Patrick
-
To unsubscribe from thi
Hi all,
I just tried to compile Torvald's upstream-linus and ran into a compile error.
CC arch/i386/kernel/time.o
In file included from include/asm-i386/mach-default/do_timer.h:5,
from arch/i386/kernel/time.c:75:
include/asm/i8253.h: In function `pit_interrupt_hook':
Hi all,
I just tried to compile Torvald's upstream-linus and ran into a compile error.
CC arch/i386/kernel/time.o
In file included from include/asm-i386/mach-default/do_timer.h:5,
from arch/i386/kernel/time.c:75:
include/asm/i8253.h: In function `pit_interrupt_hook':
On 2/18/07, Patrick Ale [EMAIL PROTECTED] wrote:
Hi all,
I just tried to compile Torvald's upstream-linus and ran into a compile error.
Disregard, I ran make oldconfig again, didnt get prompted for any
configuration options, and now it does compile.
Patrick
-
To unsubscribe from this list
Allrighy,
Since somebody up there hates me and passed me a cool fever with a
body temperature of 39C I'll stay in bed, of course.
But I wouldnt be me if I would be stopped by some inferior fever this weekend.
So I am going to install my HP Pavilion dv8373 laptop with Linux.
Two SATA disks
Allrighy,
Since somebody up there hates me and passed me a cool fever with a
body temperature of 39C I'll stay in bed, of course.
But I wouldnt be me if I would be stopped by some inferior fever this weekend.
So I am going to install my HP Pavilion dv8373 laptop with Linux.
Two SATA disks
On 2/15/07, Ioan Ionita <[EMAIL PROTECTED]> wrote:
All clear now?
Yes sir, sorry.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
On 2/15/07, Tejun Heo <[EMAIL PROTECTED]> wrote:
Yeah and about the libsata/libata thingy, it is libata of course :)
libsata I will test later on, so be prepared allready for more ranting for me.
I even bought a cool sata controller with sata disk so I can mess around :D
Patrick
-
To
On 2/15/07, Tejun Heo <[EMAIL PROTECTED]> wrote:
I appreciate the testing. One interesting but tedious test would be
suspend tests (both to disk and ram). Most libata drivers using new EH
should be ready for them. Oh, well, there's should and there's reality.
I will do these tests when I
On 2/15/07, Patrick Ale <[EMAIL PROTECTED]> wrote:
Good morning all,
Now, when I boot up, I miss two drives, exactly the two connected to
this promise card.
I have another onboard Promise controller which works just fine, so
the driver gets loaded properly, and since i see all my other
Good morning all,
Yesterday I replaced a Sil680 PCI add-on card for a Promise 2027x PCI
add-on card.
Now, when I boot up, I miss two drives, exactly the two connected to
this promise card.
I have another onboard Promise controller which works just fine, so
the driver gets loaded properly, and
Good morning all,
Yesterday I replaced a Sil680 PCI add-on card for a Promise 2027x PCI
add-on card.
Now, when I boot up, I miss two drives, exactly the two connected to
this promise card.
I have another onboard Promise controller which works just fine, so
the driver gets loaded properly, and
On 2/15/07, Patrick Ale [EMAIL PROTECTED] wrote:
Good morning all,
Now, when I boot up, I miss two drives, exactly the two connected to
this promise card.
I have another onboard Promise controller which works just fine, so
the driver gets loaded properly, and since i see all my other disks
On 2/15/07, Tejun Heo [EMAIL PROTECTED] wrote:
I appreciate the testing. One interesting but tedious test would be
suspend tests (both to disk and ram). Most libata drivers using new EH
should be ready for them. Oh, well, there's should and there's reality.
I will do these tests when I am
On 2/15/07, Tejun Heo [EMAIL PROTECTED] wrote:
Yeah and about the libsata/libata thingy, it is libata of course :)
libsata I will test later on, so be prepared allready for more ranting for me.
I even bought a cool sata controller with sata disk so I can mess around :D
Patrick
-
To
On 2/15/07, Ioan Ionita [EMAIL PROTECTED] wrote:
All clear now?
Yes sir, sorry.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
On 2/14/07, Ramy M. Hassan <[EMAIL PROTECTED]> wrote:
Hello,
We got the following xfs internal error on one of our production servers:
Hi, I want firstly to make a disclaimer that I am not an XFS or kernel
guru, what I am writing now is purely my experience, since I use XFS
on all my machines,
On 2/14/07, Ramy M. Hassan [EMAIL PROTECTED] wrote:
Hello,
We got the following xfs internal error on one of our production servers:
Hi, I want firstly to make a disclaimer that I am not an XFS or kernel
guru, what I am writing now is purely my experience, since I use XFS
on all my machines,
>
Just out of curiosity, why did you do this in such a manual way instead
of just using the UUID? I would think every time you replace a failed
drive you would have to go edit the files all over again.
Oh, there is a very simple reason for that.
These md arrays exist for a year of three
Hi chaps,
I just came home, rebooted my box to git8 and *gasp* a problem :)
I can't start my MD devices anymore by defining /dev/disk/by-id/*
devices in /etc/mdadm.conf.
When I do a: mdadm --assemble /dev/md/1 it tells me "No devices found
for /dev/md/1"
When I edit the file /etc/mdadm.conf
On 2/13/07, Jeff Garzik <[EMAIL PROTECTED]> wrote:
/That/ sounds like a qemu bug.
Allright, I will make sure tonight by testing it on a native PIIX
mainboard without anything connected to the second PATA controller :)
I thought for a second it was a similar "abnorma statel" error I got
On 2/13/07, Patrick Ale <[EMAIL PROTECTED]> wrote:
Hi,
Little errata, I only pulled Jeff's GIT at 15:00GMT , Linus' GIT was
from two days ago.
I just pulled linux-2.6-git8, same behaviour tho, it complains when
nothing is attached to the second channel.
Patrick
-
To unsubscrib
authentication, yadayada).
I didnt have time yet to install Linux on my HP Pavilion dv8373 and on
my Dual P2 400Mhz with Intel 440BX motherboard, but I hope to do this
soon.
Have a joyfull day and i hope you have better weather than we have
here in Amsterdam.
Patrick Ale
Not even the best coder
authentication, yadayada).
I didnt have time yet to install Linux on my HP Pavilion dv8373 and on
my Dual P2 400Mhz with Intel 440BX motherboard, but I hope to do this
soon.
Have a joyfull day and i hope you have better weather than we have
here in Amsterdam.
Patrick Ale
Not even the best coder
On 2/13/07, Patrick Ale [EMAIL PROTECTED] wrote:
Hi,
Little errata, I only pulled Jeff's GIT at 15:00GMT , Linus' GIT was
from two days ago.
I just pulled linux-2.6-git8, same behaviour tho, it complains when
nothing is attached to the second channel.
Patrick
-
To unsubscribe from this list
On 2/13/07, Jeff Garzik [EMAIL PROTECTED] wrote:
/That/ sounds like a qemu bug.
Allright, I will make sure tonight by testing it on a native PIIX
mainboard without anything connected to the second PATA controller :)
I thought for a second it was a similar abnorma statel error I got
earlier
Hi chaps,
I just came home, rebooted my box to git8 and *gasp* a problem :)
I can't start my MD devices anymore by defining /dev/disk/by-id/*
devices in /etc/mdadm.conf.
When I do a: mdadm --assemble /dev/md/1 it tells me No devices found
for /dev/md/1
When I edit the file /etc/mdadm.conf and
Just out of curiosity, why did you do this in such a manual way instead
of just using the UUID? I would think every time you replace a failed
drive you would have to go edit the files all over again.
Oh, there is a very simple reason for that.
These md arrays exist for a year of three
On 2/12/07, Patrick Ale <[EMAIL PROTECTED]> wrote:
Hi folks,
Disregard, I found the problem.
CONFIG_NEW_LED=Y , so I have to do a make and boot from the produced image.
Which brings me to another question.
If a dependent driver is selected as module (for reasons you dont want
to
Hi folks,
I am looking for a half day now and I can't find the dependency for
NEW_LED I am missing.
Can anyone point me to what I am missing?
80211: Unknown symbol led_trigger_unregister
80211: Unknown symbol led_trigger_register
80211: Unknown symbol led_trigger_event
80211: Unknown symbol
Hi folks,
I am looking for a half day now and I can't find the dependency for
NEW_LED I am missing.
Can anyone point me to what I am missing?
80211: Unknown symbol led_trigger_unregister
80211: Unknown symbol led_trigger_register
80211: Unknown symbol led_trigger_event
80211: Unknown symbol
On 2/12/07, Patrick Ale [EMAIL PROTECTED] wrote:
Hi folks,
Disregard, I found the problem.
CONFIG_NEW_LED=Y , so I have to do a make and boot from the produced image.
Which brings me to another question.
If a dependent driver is selected as module (for reasons you dont want
to reboot and all
On 2/11/07, Henrique de Moraes Holschuh <[EMAIL PROTECTED]> wrote:
On Sun, 11 Feb 2007, Robert Hancock wrote:
> Then in that case you should set the remaining drive as master. That's
> just the way PATA is. A lot of BIOSes won't even detect a drive that's
> set as slave with no master present.
On 2/11/07, Robert Hancock <[EMAIL PROTECTED]> wrote:
Patrick Ale wrote:
> On 2/11/07, Robert Hancock <[EMAIL PROTECTED]> wrote:
>> Patrick Ale wrote:
Then in that case you should set the remaining drive as master. That's
just the way PATA is. A lot of BIOSes won't even dete
On 2/11/07, Robert Hancock <[EMAIL PROTECTED]> wrote:
Patrick Ale wrote:
> Something unrelated to the tests I am doing.
>
> I found out that the libsata driver doesn't really cope or likes the
> idea that you might have a controller without a master drive
> configured.
>
Hi,
Something unrelated to the tests I am doing.
I found out that the libsata driver doesn't really cope or likes the
idea that you might have a controller without a master drive
configured.
In this case on ATA2 I have a CDROM drive, connected as slave.
ATA: abnormal status 0x7F on port 0x177
Hi,
Something unrelated to the tests I am doing.
I found out that the libsata driver doesn't really cope or likes the
idea that you might have a controller without a master drive
configured.
In this case on ATA2 I have a CDROM drive, connected as slave.
ATA: abnormal status 0x7F on port 0x177
On 2/11/07, Robert Hancock [EMAIL PROTECTED] wrote:
Patrick Ale wrote:
Something unrelated to the tests I am doing.
I found out that the libsata driver doesn't really cope or likes the
idea that you might have a controller without a master drive
configured.
In this case on ATA2 I have
On 2/11/07, Robert Hancock [EMAIL PROTECTED] wrote:
Patrick Ale wrote:
On 2/11/07, Robert Hancock [EMAIL PROTECTED] wrote:
Patrick Ale wrote:
Then in that case you should set the remaining drive as master. That's
just the way PATA is. A lot of BIOSes won't even detect a drive that's
set
On 2/11/07, Henrique de Moraes Holschuh [EMAIL PROTECTED] wrote:
On Sun, 11 Feb 2007, Robert Hancock wrote:
Then in that case you should set the remaining drive as master. That's
just the way PATA is. A lot of BIOSes won't even detect a drive that's
set as slave with no master present.
And again, for something completely different.
I am hammering my second machine now, a cool Siemens/Fujitsu laptop
(named elisabeth) with ICH7 ATA chipset and controller.
Currently the ATA controller is in "SATA" mode (ICH7 chipsets allow
you to run in native SATA mode or compatible mode, for
On 2/10/07, Alan <[EMAIL PROTECTED]> wrote:
Right umm "Your honor the gentleman is human, this is not acceptable" ?
Human and a looney who wishes Monty Python's Flying Circus still
existed so he could be a main character and having a great excuse to
act weird.
Beating the crap out of it
On 2/10/07, Randy Dunlap <[EMAIL PROTECTED]> wrote:
Hi,
What are the libsata tests and where are they, please?
No where, I just compile the drivers, see if my system boots up and
then I run some I/O intensive stuff, like bonnie++, emerge -e world at
the same time.
So you are testing libata
Hi,
And now for something completely different.
I started the libsata tests on one of the four machines I'll be doing
these tests on.
At the moment I'm testing on 'lilith', which is my multi-harddisk
server and playground.
At the moment I am hammering /dev/sda5, which is an ext4dev partition
And again, for something completely different.
I am hammering my second machine now, a cool Siemens/Fujitsu laptop
(named elisabeth) with ICH7 ATA chipset and controller.
Currently the ATA controller is in SATA mode (ICH7 chipsets allow
you to run in native SATA mode or compatible mode, for the
Hi,
And now for something completely different.
I started the libsata tests on one of the four machines I'll be doing
these tests on.
At the moment I'm testing on 'lilith', which is my multi-harddisk
server and playground.
At the moment I am hammering /dev/sda5, which is an ext4dev partition
On 2/10/07, Randy Dunlap [EMAIL PROTECTED] wrote:
Hi,
What are the libsata tests and where are they, please?
No where, I just compile the drivers, see if my system boots up and
then I run some I/O intensive stuff, like bonnie++, emerge -e world at
the same time.
So you are testing libata
On 2/10/07, Alan [EMAIL PROTECTED] wrote:
Right umm Your honor the gentleman is human, this is not acceptable ?
Human and a looney who wishes Monty Python's Flying Circus still
existed so he could be a main character and having a great excuse to
act weird.
Beating the crap out of it using
Do you know if these drives were advertising less capability
than they were spec-ed at? Do you recall if the IDE driver without
kernel arguments printed its rationale for reverting to the slower
setting?
I can only speak for myself of course.
On boot time the libsata driver detected my
Do you know if these drives were advertising less capability
than they were spec-ed at? Do you recall if the IDE driver without
kernel arguments printed its rationale for reverting to the slower
setting?
I can only speak for myself of course.
On boot time the libsata driver detected my
\
Userspace PIO mode changes are NOT a good idea,
and I doubt that libata would want to support that feature.
The "-d" flag (enable/disable DMA) is currently not implemented
by libata, though there may be a /sys/.. attribute for it (?).
Okay but... the driver itself does implement the calls,
On 2/5/07, Robert Hancock <[EMAIL PROTECTED]> wrote:
Patrick Ale wrote:
The southbridge usually runs the PCI bus connected to the slots, so it's
possible that PCI bus issues were causing problems..
Explains a lot then yeah... okay, if the error occures again I will
let you know, I am b
Hi,
It is working since I enabled this ATA_PIIX driver. :)
Appearantly "old" has nothing to do with the age of the mainboard and
it's capabilities.
an UDMA33 board works with the "new" driver even :)
Thanks a lot, next beer/slivovica/palinka is on me :)
Patrick
-
To unsubscribe from this
Good morning all,
About the reason as of why it drops to PIO mode, I might have found
the reason for this, I am just not sure if what i found is related.
When I opened my Athlon XP machine, took the cables out and replaced
them for new cables, I found out that my southbridge fan wasnt
spinning
Good morning all,
About the reason as of why it drops to PIO mode, I might have found
the reason for this, I am just not sure if what i found is related.
When I opened my Athlon XP machine, took the cables out and replaced
them for new cables, I found out that my southbridge fan wasnt
spinning
Hi,
It is working since I enabled this ATA_PIIX driver. :)
Appearantly old has nothing to do with the age of the mainboard and
it's capabilities.
an UDMA33 board works with the new driver even :)
Thanks a lot, next beer/slivovica/palinka is on me :)
Patrick
-
To unsubscribe from this list:
On 2/5/07, Robert Hancock [EMAIL PROTECTED] wrote:
Patrick Ale wrote:
The southbridge usually runs the PCI bus connected to the slots, so it's
possible that PCI bus issues were causing problems..
Explains a lot then yeah... okay, if the error occures again I will
let you know, I am booting up
\
Userspace PIO mode changes are NOT a good idea,
and I doubt that libata would want to support that feature.
The -d flag (enable/disable DMA) is currently not implemented
by libata, though there may be a /sys/.. attribute for it (?).
Okay but... the driver itself does implement the calls,
It's working, thanks :)
I was confused by this ATA_PIIX driver needing to be enabled, I
genuinly thought and read it was the SATA driver.
Thanks :)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On 2/4/07, Patrick Ale <[EMAIL PROTECTED]> wrote:
On 2/4/07, Alan <[EMAIL PROTECTED]> wrote:
\
> OLDPIIX is for "old" PIIX devices only - from pentium era. It does not
> cover the later chips at all
Just to make sure, this is a P2 SMP board, Slot A, doesnt eve
On 2/4/07, Alan <[EMAIL PROTECTED]> wrote:
\
OLDPIIX is for "old" PIIX devices only - from pentium era. It does not
cover the later chips at all
Well, neither driver works, as you can see in my config I have the
"OLD" driver and the "new" driver, neither driver makes my controller
being
On 2/4/07, Patrick Ale <[EMAIL PROTECTED]> wrote:
Amm,
not to sound like a wise guy but... CONFIG_ATA_PIIX is the SATA
driver, not the PATA driver.. atleast that is what menuconfig tells me
when I select "Help" when I look at the config options
-
To unsubscribe from this lis
On 2/4/07, Alan <[EMAIL PROTECTED]> wrote:
PATA_OLDPIIX drives the PIIX (the original not PIIX3,4, etc)
People do find that confusing so if there is any rewording for
Configure.help that would have made it easier and more obvious let me know
Okay so.. what do I define now to use libsata
On 2/4/07, Alistair John Strachan <[EMAIL PROTECTED]> wrote:
Which for a PIIX4 chipset is what you want. Somewhat confusingly:
CONFIG_PATA_MPIIX=y
CONFIG_PATA_OLDPIIX=y
Should be "n", I've been told.
What? No, this cant be. CONFIG_PATA_OLDPIIX is supposed to be the
libsata version for the
1 - 100 of 128 matches
Mail list logo
