On 08/02/2007 03:03 PM, Yan Seiner wrote:
HAH! Success!
Congrats :-)
Here's the magic incantations on a Compaq Armada 1700, ess1869 chipset,
and 2.6.21 kernel:
boot with noapic acpi=off pci=biosirq
I doubt the noapic makes a difference?
acpi *must* be enabled in the bios, and
Rene Herman napsal(a):
On 08/01/2007 04:07 PM, Yan Seiner wrote:
From the various threads I've found on this, it appears that the
driver broke sometime fairly recently, and that it may indeed work
with older kernels. Perhaps the fault is with the acpi system
changes in recent kernels.
On 08/01/2007 02:57 AM, Troy Heidner wrote:
Thanks for the help!
Sure, but please always keep existing CCs intact on these kinds of messages.
Otherwise the next poor sod that googles for the same problem hits on these
first few messages of a conversation, but not the solution since that was
Rene Herman napsal(a):
The ESS0009 is the chip's CTRL port but I assume from the single
ESS1869 already present there that it's okay without.
If you are upto applying the attached patch and rebuilding the kernel
please do so, but assuming you are not, you can work-around the driver
not
Yan Seiner napsal(a):
Rene Herman napsal(a):
The ESS0009 is the chip's CTRL port but I assume from the single
ESS1869 already present there that it's okay without.
If you are upto applying the attached patch and rebuilding the kernel
please do so, but assuming you are not, you can
Yan Seiner napsal(a):
Yan Seiner napsal(a):
Hi Rene:
I've also been trying to get this chip to work. This exchange gives me
new hope. Here's what I have:
debian:~# cat /sys/bus/pnp/devices/00:*/id | grep ESS
ESS0006
ESS1869
debian:~# cd /sys/bus/pnp/devices/00:05
On 08/01/2007 04:07 PM, Yan Seiner wrote:
From the various threads I've found on this, it appears that the driver
broke sometime fairly recently, and that it may indeed work with older
kernels. Perhaps the fault is with the acpi system changes in recent
kernels.
The fact that the driver
Rene Herman wrote:
On 08/01/2007 04:07 PM, Yan Seiner wrote:
From the various threads I've found on this, it appears that the
driver broke sometime fairly recently, and that it may indeed work
with older kernels. Perhaps the fault is with the acpi system changes
in recent kernels.
Rene,
Holy crap, I've got sound! :)
You were right, that modprobe line did it. The state= line in the
resources file was already set to active. A couple of the resources were
different than you listed, but when I plugged the appropriate values into
the modprobe line, everything worked! The
On 08/01/2007 08:52 PM, Troy Heidner wrote:
Holy crap, I've got sound! :)
Good to hear. I'll submit the little patch for inclusion and (hopefully, it
didn't really get tested, but oh well) future drivers should work a little
better directly (that is, without you needing to specify the
On 07/31/2007 05:44 AM, Troy Heidner wrote:
I'm new to the list here, and I'm fairly new to linux as well. I have
an older Gateway Solo 5150 laptop computer that I'm trying to run Fedora
Core 6 on. It's a PII-400 with 288MB of RAM. I have gotten nearly
EVERYTHING working splendidly with
11 matches
Mail list logo
