With 5.10.x, My AMD RX580 based system hang with a blank screen on
boot: no SSH access possible. There are no issues with 5.9.x. I
submitted a bug report here:
https://bugzilla.kernel.org/show_bug.cgi?id=210867
I code, therefore I am
On Sun, 12/8/13, Alex Davis wrote:
Subject: Re: [PATCH] dell-laptop: add parameter to disable the backlight
device.
To: "mj...@srcf.ucam.org" ,
"linux-kernel@vger.kernel.org" , "Levente Kurusa&quo
On Sun, 12/8/13, Levente Kurusa wrote:
> Subject: Re: [PATCH] dell-laptop: add parameter to disable the backlight
> device.
> To: "Alex Davis" , "mj...@srcf.ucam.org"
> , >"linux->ker...@vger.kernel.org&
be controlled.
This patch is against 3.10.
Signed-off-by: Alex Davis
--- dell-laptop.c.orig 2013-12-01 19:05:39.693149050 -0500
+++ dell-laptop.c 2013-12-01 17:29:27.613372482 -0500
@@ -35,6 +35,9 @@
/* This structure will be modified by the firmware when we enter
* system management mode
be controlled.
This patch is against 3.10.
Signed-off-by: Alex Davis alex14...@yahoo.com
--- dell-laptop.c.orig 2013-12-01 19:05:39.693149050 -0500
+++ dell-laptop.c 2013-12-01 17:29:27.613372482 -0500
@@ -35,6 +35,9 @@
/* This structure will be modified by the firmware when we enter
On Sun, 12/8/13, Levente Kurusa le...@linux.com wrote:
Subject: Re: [PATCH] dell-laptop: add parameter to disable the backlight
device.
To: Alex Davis alex14...@yahoo.com, mj...@srcf.ucam.org
mj...@srcf.ucam.org, linux-ker...@vger.kernel.org
I code, therefore I am
On Sun, 12/8/13, Alex Davis alex14...@yahoo.com wrote:
Subject: Re: [PATCH] dell-laptop: add parameter to disable the backlight
device.
To: mj...@srcf.ucam.org mj...@srcf.ucam.org,
linux-kernel@vger.kernel.org linux-kernel
>On Sunday, December 1, 2013 8:43 PM, Alex Davis wrote:
>I have a Dell Inspiron N7010 Laptop with Intel graphics. When the dell-laptop
>module is >loaded,
>two backlight device devices are created; dell_backlight, and intel_backlight
>from the >Intel
>graphics dr
On Sunday, December 1, 2013 8:43 PM, Alex Davis alex14...@yahoo.com wrote:
I have a Dell Inspiron N7010 Laptop with Intel graphics. When the dell-laptop
module is loaded,
two backlight device devices are created; dell_backlight, and intel_backlight
from the Intel
graphics driver
-by: Alex Davis
--- dell-laptop.c.orig 2013-12-01 19:05:39.693149050 -0500
+++ dell-laptop.c 2013-12-01 17:29:27.613372482 -0500
@@ -35,6 +35,9 @@
/* This structure will be modified by the firmware when we enter
* system management mode, hence the volatiles */
+static bool
-by: Alex Davis alex14...@yahoo.com
--- dell-laptop.c.orig 2013-12-01 19:05:39.693149050 -0500
+++ dell-laptop.c 2013-12-01 17:29:27.613372482 -0500
@@ -35,6 +35,9 @@
/* This structure will be modified by the firmware when we enter
* system management mode, hence the volatiles */
+static
I get the following Oops after 2 or so weeks of uptime:
Sep 14 04:40:16 polyergus kernel: [1664412.773070] BUG: unable to handle kernel
paging request at
virtual address b6ea34d0
Sep 14 04:40:16 polyergus kernel: [1664412.773077] printing eip:
Sep 14 04:40:16 polyergus kernel: [1664412.773079]
I get the following Oops after 2 or so weeks of uptime:
Sep 14 04:40:16 polyergus kernel: [1664412.773070] BUG: unable to handle kernel
paging request at
virtual address b6ea34d0
Sep 14 04:40:16 polyergus kernel: [1664412.773077] printing eip:
Sep 14 04:40:16 polyergus kernel: [1664412.773079]
As you are using ndiswrapper, you won't much if any help from the kernel
developers.
ndiswrapper taints the kernel as it links closed-source drivers into kernel
space.
I strongly advise you to post this question on the ndiswrapper mailing list.
Good luck.
-Alex
> Hi !
> I'm trying to use a
As you are using ndiswrapper, you won't much if any help from the kernel
developers.
ndiswrapper taints the kernel as it links closed-source drivers into kernel
space.
I strongly advise you to post this question on the ndiswrapper mailing list.
Good luck.
-Alex
Hi !
I'm trying to use a
--- Bill Davidsen <[EMAIL PROTECTED]> wrote:
> Alex Davis wrote:
> >>Please don't tell me to "care for closed-source drivers".
> >
> > ndiswrapper is NOT closed source. And I'm not asking you to "care".
> >
> >
> >&
--- Bill Davidsen [EMAIL PROTECTED] wrote:
Alex Davis wrote:
Please don't tell me to care for closed-source drivers.
ndiswrapper is NOT closed source. And I'm not asking you to care.
I don't want the pain of debugging crashes on the machines which run
unknown code
in kernel
--- Sean <[EMAIL PROTECTED]> wrote:
> On Sun, September 4, 2005 11:41 pm, Alex Davis said:
>
> > It will never be 'appropriate' if the system doesn't somehow work on Joe's
> > hardware. We currently have something that works. In my opinion it's
> &g
--- Sean <[EMAIL PROTECTED]> wrote:
> On Sun, September 4, 2005 10:29 pm, Alex Davis said:
>
> > Linux isn't just used by kernel developers. It's that attitude that
> > helps insure Linux will always have a small userbase. Lack of numbers
> > just gives th
--- Sean <[EMAIL PROTECTED]> wrote:
> On Sun, September 4, 2005 10:00 pm, Alex Davis said:
> > Dave Jones wrote:
> >>- NDISwrapper / driverloader.
> >> (Shock, horror - no-one cares).
> >
> > Shock, horror. Someone DOES care: everyone who uses ndisw
Dave Jones wrote:
>- NDISwrapper / driverloader.
> (Shock, horror - no-one cares).
Shock, horror. Someone DOES care: everyone who uses ndiswrapper or
driverloader, whether they know it or not. Are you proposing that
we punish the end-users because of the obstinence of the hardware
manufacturers?
>The NdisWrapper FAQ already tells you that you need a patch for some of
>the binary-only Windows drivers that require more than 8kB stacks.
>
>And the fact that NdisWrapper is mostly working hinders the development
>of open source drivers for this hardware.
If the hardware manufacturer won't
>Please don't tell me to "care for closed-source drivers".
ndiswrapper is NOT closed source. And I'm not asking you to "care".
>I don't want the pain of debugging crashes on the machines which run unknown
>code
>in kernel space.
I'm not asking you to debug crashes. I'm simply requesting that
Please don't tell me to care for closed-source drivers.
ndiswrapper is NOT closed source. And I'm not asking you to care.
I don't want the pain of debugging crashes on the machines which run unknown
code
in kernel space.
I'm not asking you to debug crashes. I'm simply requesting that the
kernel
The NdisWrapper FAQ already tells you that you need a patch for some of
the binary-only Windows drivers that require more than 8kB stacks.
And the fact that NdisWrapper is mostly working hinders the development
of open source drivers for this hardware.
If the hardware manufacturer won't give
Dave Jones wrote:
- NDISwrapper / driverloader.
(Shock, horror - no-one cares).
Shock, horror. Someone DOES care: everyone who uses ndiswrapper or
driverloader, whether they know it or not. Are you proposing that
we punish the end-users because of the obstinence of the hardware
manufacturers?
--- Sean [EMAIL PROTECTED] wrote:
On Sun, September 4, 2005 10:00 pm, Alex Davis said:
Dave Jones wrote:
- NDISwrapper / driverloader.
(Shock, horror - no-one cares).
Shock, horror. Someone DOES care: everyone who uses ndiswrapper or
driverloader, whether they know
--- Sean [EMAIL PROTECTED] wrote:
On Sun, September 4, 2005 10:29 pm, Alex Davis said:
Linux isn't just used by kernel developers. It's that attitude that
helps insure Linux will always have a small userbase. Lack of numbers
just gives the manufacturers another reason not to care about
--- Sean [EMAIL PROTECTED] wrote:
On Sun, September 4, 2005 11:41 pm, Alex Davis said:
It will never be 'appropriate' if the system doesn't somehow work on Joe's
hardware. We currently have something that works. In my opinion it's
pointless to take that away. The manufacturers
ndiswrapper and driverloader will not work reliably with 4k stacks.
This is because of the Windoze drivers they use, to which, obviously,
they do not have the source. Since quite a few laptops have built-in
wireless cards by companies who will not release an open-source driver,
or won't release
ndiswrapper and driverloader will not work reliably with 4k stacks.
This is because of the Windoze drivers they use, to which, obviously,
they do not have the source. Since quite a few laptops have built-in
wireless cards by companies who will not release an open-source driver,
or won't release
Problem does not exist on 2.6.8.1. Compiling your program and running
./a.out < README | diff README -
produces no output.
I tested various files ranging in size from 10 to 60k.
-Alex
=
I code, therefore I am
__
Do you Yahoo!?
Yahoo!
Problem does not exist on 2.6.8.1. Compiling your program and running
./a.out README | diff README -
produces no output.
I tested various files ranging in size from 10 to 60k.
-Alex
=
I code, therefore I am
__
Do you Yahoo!?
Yahoo!
ed.
--- check.c.saveWed Feb 21 17:50:54 2001
+++ check.c Wed Feb 21 19:49:20 2001
@@ -9,6 +9,10 @@
* contained.
*
* Added needed MAJORS for new pairs, {hdi,hdj}, {hdk,hdl}
+ *
+ * Alex Davis <[EMAIL PROTECTED]>
+ * Added code to keep /proc/partitions in sync with
+ * remova
21 17:50:54 2001
+++ check.c Wed Feb 21 19:49:20 2001
@@ -9,6 +9,10 @@
* contained.
*
* Added needed MAJORS for new pairs, {hdi,hdj}, {hdk,hdl}
+ *
+ * Alex Davis [EMAIL PROTECTED]
+ * Added code to keep /proc/partitions in sync with
+ * removable media.
*/
#include linux
35 matches
Mail list logo
