Richard Purdie <[EMAIL PROTECTED]> writes:
> I propose the following patch (I was previously waiting on James for
> this). It avoids backing out the problematic Kconfig changes but
> means a user has to explicitly enable the backlight via a kernel or
> module parameter.
>
> Can people with
Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes:
> On Fri, 02 Mar 2007, David Miller wrote:
>> Why don't we compromise for 2.6.21 by marking the Radeon backlight
>> stuff EXPERIMENTAL until the cases where IBM ACPI works and the
>> Radeon backlight stuff does not are worked out?
>
> What
Andrew Morton <[EMAIL PROTECTED]> writes:
> On Wed, 28 Feb 2007 08:32:43 -0800
> Alex Romosan <[EMAIL PROTECTED]> wrote:
>
>> the backlight on my thinkpad still (2.6.20 worked fine) doesn't come
>> on if i have the radeon backlight enabled. without it, i g
Andrew Morton [EMAIL PROTECTED] writes:
On Wed, 28 Feb 2007 08:32:43 -0800
Alex Romosan [EMAIL PROTECTED] wrote:
the backlight on my thinkpad still (2.6.20 worked fine) doesn't come
on if i have the radeon backlight enabled. without it, i guess it's
the ibm acpi modules that controls
Henrique de Moraes Holschuh [EMAIL PROTECTED] writes:
On Fri, 02 Mar 2007, David Miller wrote:
Why don't we compromise for 2.6.21 by marking the Radeon backlight
stuff EXPERIMENTAL until the cases where IBM ACPI works and the
Radeon backlight stuff does not are worked out?
What ibm-acpi
Richard Purdie [EMAIL PROTECTED] writes:
I propose the following patch (I was previously waiting on James for
this). It avoids backing out the problematic Kconfig changes but
means a user has to explicitly enable the backlight via a kernel or
module parameter.
Can people with backlight
the backlight on my thinkpad still (2.6.20 worked fine) doesn't come
on if i have the radeon backlight enabled. without it, i guess it's
the ibm acpi modules that controls the backlight and it seems to work
fine.
--alex--
--
| I believe the moment is at hand when, by a paranoiac and active |
|
the backlight on my thinkpad still (2.6.20 worked fine) doesn't come
on if i have the radeon backlight enabled. without it, i guess it's
the ibm acpi modules that controls the backlight and it seems to work
fine.
--alex--
--
| I believe the moment is at hand when, by a paranoiac and active |
|
Richard Purdie <[EMAIL PROTECTED]> writes:
> If FB_RADEON_BACKLIGHT wasn't set for 2.6.20, can you try 2.6.21-rc1
> with that option disabled?
i've disabled FB_RADEON_BACKLIGHT (FB_BACKLIGHT also got deselected)
and i managed to boot into 2.6.21-rc1 and have a working backlight.
--alex--
--
|
Richard Purdie writes:
> Can you have a look at the differences between the defconfigs for
> 2.6.20 and 2.6.21-rc1?
this is probably the relevant part:
--- config-2.6.20 2007-02-04 12:09:28.0 -0800
+++ config-2.6.21-rc1 2007-02-21 08:37:53.0 -0800
@@ -1270,16 +1302,25 @@
Richard Purdie <[EMAIL PROTECTED]> writes:
> If FB_RADEON_BACKLIGHT wasn't set for 2.6.20, can you try 2.6.21-rc1
> with that option disabled?
i don't have my laptop with me but i am pretty sure
FB_RADEON_BACKLIGHT wasn't set for 2.6.20 (i think it showed up as a
new option when i did make
Richard Purdie <[EMAIL PROTECTED]> writes:
> On Mon, 2007-02-19 at 00:04 -0800, Andrew Morton wrote:
>> On Sun, 18 Feb 2007 23:46:16 -0500 Yaroslav Halchenko <[EMAIL PROTECTED]>
>> wrote:
>> > Since the most recent successful for me kernel 2.6.19-rc6-mm1, I've
>> > tried few times to build more
Richard Purdie [EMAIL PROTECTED] writes:
On Mon, 2007-02-19 at 00:04 -0800, Andrew Morton wrote:
On Sun, 18 Feb 2007 23:46:16 -0500 Yaroslav Halchenko [EMAIL PROTECTED]
wrote:
Since the most recent successful for me kernel 2.6.19-rc6-mm1, I've
tried few times to build more recent
Richard Purdie [EMAIL PROTECTED] writes:
If FB_RADEON_BACKLIGHT wasn't set for 2.6.20, can you try 2.6.21-rc1
with that option disabled?
i don't have my laptop with me but i am pretty sure
FB_RADEON_BACKLIGHT wasn't set for 2.6.20 (i think it showed up as a
new option when i did make
Richard Purdie writes:
Can you have a look at the differences between the defconfigs for
2.6.20 and 2.6.21-rc1?
this is probably the relevant part:
--- config-2.6.20 2007-02-04 12:09:28.0 -0800
+++ config-2.6.21-rc1 2007-02-21 08:37:53.0 -0800
@@ -1270,16 +1302,25 @@
Richard Purdie [EMAIL PROTECTED] writes:
If FB_RADEON_BACKLIGHT wasn't set for 2.6.20, can you try 2.6.21-rc1
with that option disabled?
i've disabled FB_RADEON_BACKLIGHT (FB_BACKLIGHT also got deselected)
and i managed to boot into 2.6.21-rc1 and have a working backlight.
--alex--
--
| I
Jiri Slaby <[EMAIL PROTECTED]> writes:
> Alex Romosan wrote:
>> this is on a thinkpad t40, not sure if it means anything, but here it goes:
>>
>> kernel: kernel BUG at fs/buffer.c:1235!
>> kernel: invalid opcode: [#1]
>> kernel: PREEMPT
>> kern
Jiri Slaby [EMAIL PROTECTED] writes:
Alex Romosan wrote:
this is on a thinkpad t40, not sure if it means anything, but here it goes:
kernel: kernel BUG at fs/buffer.c:1235!
kernel: invalid opcode: [#1]
kernel: PREEMPT
kernel: Modules linked in: radeon drm binfmt_misc nfs sd_mod
this is on a thinkpad t40, not sure if it means anything, but here it goes:
kernel: kernel BUG at fs/buffer.c:1235!
kernel: invalid opcode: [#1]
kernel: PREEMPT
kernel: Modules linked in: radeon drm binfmt_misc nfs sd_mod scsi_mod nfsd
exportfs lockd sunrpc autofs4 pcmcia firmware_class
this is on a thinkpad t40, not sure if it means anything, but here it goes:
kernel: kernel BUG at fs/buffer.c:1235!
kernel: invalid opcode: [#1]
kernel: PREEMPT
kernel: Modules linked in: radeon drm binfmt_misc nfs sd_mod scsi_mod nfsd
exportfs lockd sunrpc autofs4 pcmcia firmware_class
under heavy network load the sky2 driver (compiled in the kernel)
locks up and the only way i can get the network back is to reboot the
machine (bringing the network down and back up again doesn't help).
this happens on an amd64 machine (athlon 3500+ processor) and the card
in question is a
under heavy network load the sky2 driver (compiled in the kernel)
locks up and the only way i can get the network back is to reboot the
machine (bringing the network down and back up again doesn't help).
this happens on an amd64 machine (athlon 3500+ processor) and the card
in question is a
Mikael Pettersson <[EMAIL PROTECTED]> writes:
> I'm no longer seeing any time jumps after resumes with the
> 2.6.11-rc1 kernel. It looks like the wall_jiffies change in
> time.c fixed the bug.
i can also confirm the that the time no longer jumps after an acpi
resume with the 2.6.11-rc1 kernel.
Mikael Pettersson [EMAIL PROTECTED] writes:
I'm no longer seeing any time jumps after resumes with the
2.6.11-rc1 kernel. It looks like the wall_jiffies change in
time.c fixed the bug.
i can also confirm the that the time no longer jumps after an acpi
resume with the 2.6.11-rc1 kernel.
Alan Cox <[EMAIL PROTECTED]> writes:
> > i came in today to find the computer completely locked up. after
> > rebooting and waiting for about an hour for fsck to finish i found the
> > following errors in the system log:
>
> What hardware. I can see its some kind of scsi setup but what
i came in today to find the computer completely locked up. after
rebooting and waiting for about an hour for fsck to finish i found the
following errors in the system log:
Feb 13 06:25:18 caliban kernel: EXT2-fs error (device sd(8,3)): ext2_readdir: bad
entry in directory #11: rec_len %% 4 != 0
i came in today to find the computer completely locked up. after
rebooting and waiting for about an hour for fsck to finish i found the
following errors in the system log:
Feb 13 06:25:18 caliban kernel: EXT2-fs error (device sd(8,3)): ext2_readdir: bad
entry in directory #11: rec_len %% 4 != 0
Alan Cox [EMAIL PROTECTED] writes:
i came in today to find the computer completely locked up. after
rebooting and waiting for about an hour for fsck to finish i found the
following errors in the system log:
What hardware. I can see its some kind of scsi setup but what interfaces ?
Gerhard Mack <[EMAIL PROTECTED]> writes:
> That looks exactly like the message I get if I tell the bios not to
> assign an interrupt to my video card.
>
unfortunately, i don't get such a choice. and if what you say is true,
isn't the message ("No IRQ known for interrupt pin A of device
Martin Mares <[EMAIL PROTECTED]> writes:
> > During boot, I get the message:
> >
> > PCI: No IRQ known for interrupt pin A of device 00:00.1. Please try
> > using pci=biosirq.
>
> Can you send me 'lspci -vvx' output, please?
>
i am not the original poster, but i get the same message (save
Alex Romosan <[EMAIL PROTECTED]> writes:
> i forgot to bring up eth0 before attempting to connect to my dsl
> provider using ppp over ethernet and i got the following oops:
>
i hate it when i do this. the correct oops follows:
ksymoops 2.3.4 on i686 2.4.0-test11. Optio
i forgot to bring up eth0 before attempting to connect to my dsl
provider using ppp over ethernet and i got the following oops:
ksymoops 2.3.4 on i686 2.4.0-test11. Options used
-V (default)
-k /proc/ksyms (specified)
-l /proc/modules (default)
-o /lib/modules/2.4.0-test11/
Alex Romosan [EMAIL PROTECTED] writes:
i forgot to bring up eth0 before attempting to connect to my dsl
provider using ppp over ethernet and i got the following oops:
i hate it when i do this. the correct oops follows:
ksymoops 2.3.4 on i686 2.4.0-test11. Options used
-V (default
Martin Mares [EMAIL PROTECTED] writes:
During boot, I get the message:
PCI: No IRQ known for interrupt pin A of device 00:00.1. Please try
using pci=biosirq.
Can you send me 'lspci -vvx' output, please?
i am not the original poster, but i get the same message (save for the
device
Gerhard Mack [EMAIL PROTECTED] writes:
That looks exactly like the message I get if I tell the bios not to
assign an interrupt to my video card.
unfortunately, i don't get such a choice. and if what you say is true,
isn't the message ("No IRQ known for interrupt pin A of device
05:00.0.
Andrew Morton <[EMAIL PROTECTED]> writes:
> Horst von Brand wrote:
> >
> > I've been using a 3com 3CCFE575CT 10/100 Eth cardbus card without any
> > trouble in 2.2.18pre and 2.4.0-test8 together with pcmcia-cs-3.1.21 (Sep 5
> > snapshot). I'm running Red Hat 6.2 on that machine (Toshiba
Andrew Morton [EMAIL PROTECTED] writes:
Horst von Brand wrote:
I've been using a 3com 3CCFE575CT 10/100 Eth cardbus card without any
trouble in 2.2.18pre and 2.4.0-test8 together with pcmcia-cs-3.1.21 (Sep 5
snapshot). I'm running Red Hat 6.2 on that machine (Toshiba Satellite Pro
Ravindra Jaju <[EMAIL PROTECTED]> writes:
> The second time, it was fine till about 2 hours, while I was writing
> *this* mail. Rebooted all of a sudden (no idea as to where the
> problem was. It was _quick_. No messages, nothing).
>
i had exactly the same problem with 2.4.0-test8. suddenly
Andrew Morton <[EMAIL PROTECTED]> writes:
> Please try this with your 3CCFE575BT. Quick test: go to another machine
> and run
>
> ping -f -s 5 name_of_3com_machine
>
>
> --- 3c575_cb.c.orig Sat Sep 9 18:56:29 2000
> +++ 3c575_cb.cSat Sep 9 18:56:20 2000
> @@ -1359,7
Andrew Morton [EMAIL PROTECTED] writes:
Please try this with your 3CCFE575BT. Quick test: go to another machine
and run
ping -f -s 5 name_of_3com_machine
--- 3c575_cb.c.orig Sat Sep 9 18:56:29 2000
+++ 3c575_cb.cSat Sep 9 18:56:20 2000
@@ -1359,7 +1359,7 @@
Ravindra Jaju [EMAIL PROTECTED] writes:
The second time, it was fine till about 2 hours, while I was writing
*this* mail. Rebooted all of a sudden (no idea as to where the
problem was. It was _quick_. No messages, nothing).
i had exactly the same problem with 2.4.0-test8. suddenly the
Andrew Morton <[EMAIL PROTECTED]> writes:
> This patch fixes some long-standing problems which people
> have been experiencing on collisiony half-duplex 10baseT LANs.
>
> It also syncs up some device names and types with the latest
> pcmcia_cs release.
>
> Many thanks to David Hinds for
"Micha³ 'CeFeK' Nazarewicz" <[EMAIL PROTECTED]> writes:
> Salve,
> That's me again :-) It looks like that I am the only person with
> Dell Latitude CPt using Linux 2.4 or nobody before wrote here -- as I
> can't find a solution to my problems via the web.
> The next problems are:
>
"Micha³ 'CeFeK' Nazarewicz" [EMAIL PROTECTED] writes:
Salve,
That's me again :-) It looks like that I am the only person with
Dell Latitude CPt using Linux 2.4 or nobody before wrote here -- as I
can't find a solution to my problems via the web.
The next problems are:
1.
Andrew Morton [EMAIL PROTECTED] writes:
This patch fixes some long-standing problems which people
have been experiencing on collisiony half-duplex 10baseT LANs.
It also syncs up some device names and types with the latest
pcmcia_cs release.
Many thanks to David Hinds for sorting all
45 matches
Mail list logo
