Am Donnerstag, 25. November 2004 22:27 schrieb Joerg Friedrich:
> After searching a while I found a solution. gentoo had a patch, so it
> should work now. the patch should appear on
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=250619 soon :-)
This one?
+# Building the devicelist:
+# Kernel
On Thu, Nov 25, 2004 at 11:17:00PM +0100, Joerg Friedrich wrote:
> Admar Schoonen schrieb am Donnerstag, 25. November 2004 um 23:04:45 +0100:
> > On Thu, Nov 25, 2004 at 10:27:41PM +0100, Joerg Friedrich wrote:
> > > One last question: anone using devfs or udev?
> > > How are the framebuffer-device
Admar Schoonen schrieb am Donnerstag, 25. November 2004 um 23:04:45 +0100:
> On Thu, Nov 25, 2004 at 10:27:41PM +0100, Joerg Friedrich wrote:
> > One last question: anone using devfs or udev?
> > How are the framebuffer-devices named?
>
> $ ls -l /dev/fb*
> crw-rw 1 root video 29, 0 Nov 25 08
On Thu, Nov 25, 2004 at 10:27:41PM +0100, Joerg Friedrich wrote:
> One last question: anone using devfs or udev?
> How are the framebuffer-devices named?
$ ls -l /dev/fb*
crw-rw 1 root video 29, 0 Nov 25 08:42 /dev/fb0
crw-rw 1 root video 29, 1 Nov 25 08:42 /dev/fb1
$
At least, that's o
Joerg Friedrich schrieb am Donnerstag, 25. November 2004 um 21:37:21 +0100:
> Hi,
>
> I have two issues after switching from kernel 2.4.x to 2.6.x
>
> Second: Problem with afbinit, which is needed to use AFB-based graphics
> adaptor. /etc/init.d/afbinit tries to parse the output of dmesg to
> det
Hi,
I have two issues after switching from kernel 2.4.x to 2.6.x
First: Keymap. this issue is known,
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=269405
For 2.6 a workaround is not to load any keymap.
2.4 I was not able to test due to because I ran into a problem with the
silo.conf (http://bu
At Wed, 24 Nov 2004 22:14:02 -0800 (PST),
<[EMAIL PROTECTED]> wrote:
>
> I think you will find my bug at the following URL to be relevant to
> your situation. Please have a look at my strace64 output and let me
> know what you think. Also, please add any potentially relevant comments
> to the dock
On Wed, 24 Nov 2004 [EMAIL PROTECTED] wrote:
The scan code by which Magic SysRq can be activated is hackable. Please
have a look at linux/Documentation/sysrq.txt (or whereever it is in
there) to find out how to alter the scancodes in the SysRq driver.
On a serial line things are slightly more
I think you will find my bug at the following URL to be relevant to
your situation. Please have a look at my strace64 output and let me
know what you think. Also, please add any potentially relevant comments
to the docket. Hopefully if multiple users report this, the X Strike
Force will finally tak
Clearly this indicates some kind of boot order dependency is not being
satisfied. I suggest you investigate what thing that X requires to have
been started is either (A) not started in time for the display
manager's X server to find it or (B) not done starting in time for the
display manager's X se
The scan code by which Magic SysRq can be activated is hackable. Please
have a look at linux/Documentation/sysrq.txt (or whereever it is in
there) to find out how to alter the scancodes in the SysRq driver.
--- Jurij Smakov <[EMAIL PROTECTED]> wrote:
> On Tue, 23 Nov 2004, Martin Habets wrote:
>
11 matches
Mail list logo
