On Mon, 2004-09-20 at 11:05, Paul van Tilburg wrote:
> On Mon, Sep 20, 2004 at 10:25:11AM -0700, Adam Done wrote:
> > FATAL: Could not find 'monitor' private ioctl or use the newer style
> > 'mode monitor' command. This typically means that the drivers have not
> > been patched or the correct driv
Package: installation-reports
In addition to the already noted problems with 2.4 PowerPC boot
floppies, I have two requests for modules to be included on the
root or root-2:
1) The "change installation priority" menu item should be available
*very* early in the install process. Best would b
> I helped a local school set up a Linux computer lab. The setup uses X-
> terminals (netboot, NFS and all that stuff) on Debian unstable.
> Everything seems to work perfectly but for one "small" problem -
> changing keyboard layouts simply doesn't work. Well - in fact even the
> layout specified
On Mon, Sep 20, 2004 at 10:25:11AM -0700, Adam Done wrote:
> FATAL: Could not find 'monitor' private ioctl or use the newer style
> 'mode monitor' command. This typically means that the drivers have not
> been patched or the correct drivers are being loaded. See the
> troubleshooting section of th
I have been trying to get kismet to run on the apple's airport card and
I get this output when I run kismet as su
Server options: none
Client options: none
Starting server...
Suid priv-dropping disabled. This may not be secure.
Waiting for server to start before startuing UI...
No specific sour
This question involves Debian on my x86 machine and an oldword B&W G3
running Mac OS (8.6), but I figured people on this list would be more
knowledgeable about netatalk than the other Debian lists.
After installing netatalk via apt-get on my Sarge machine, I created a
share in /etc/netatalk/AppleV
> Here is mine, on the same powerbook, works fine.
thanks, it seems that the "VideoRam" option was the culprit, after removing it
X started up fine...
it's strange, however, that there weren't any warnings or errors in my
logfile. well, nevermind.
regards,
Georg Kaindl
> > A ghost image of whatever is on the screen, displaced by (roughly) 128
> > pixels to the left. At the refresh rate used by X, the ghost image
> > flickers so that you see it light up with a periodicity of around a cm
> > vertical, or approximately 40 pixels (that's rather harder to estimate).
>
Hi,
I helped a local school set up a Linux computer lab. The setup uses X-
terminals (netboot, NFS and all that stuff) on Debian unstable.
Everything seems to work perfectly but for one "small" problem -
changing keyboard layouts simply doesn't work. Well - in fact even the
layout specified in XF8
> > > Wait ... you are talking about console flickering or X flickering ? If
> >
> > console - X is fine until I switch to console and back.
>
> Weird... It's usually the opposite... ok, now the hard one: try to
> describe precisely what you mean by "flicker" :)
A ghost image of whatever is on the
On Mon, 2004-09-20 at 23:29, Michael Schmitz wrote:
> A ghost image of whatever is on the screen, displaced by (roughly) 128
> pixels to the left. At the refresh rate used by X, the ghost image
> flickers so that you see it light up with a periodicity of around a cm
> vertical, or approximately 40
On Mon, 2004-09-20 at 18:49, Michael Schmitz wrote:
> > > > Nope, have you hard-wired the PLL value like I do for other laptops ?
> > >
> > > Nope, the OF data are used to set up the PLL. Even feeding it utter
> > > bullshit for SCLK and MCLK does nothing at all to change the picture.
> >
> > Wait
I've a problem with X on my Mac (G4 dual processor with nVidia graphics card):
when I startx I get a black screen on the virtual console #7, and no errors
on the virtual console #1, so I assume X believes to be ok. I can kill X from
another virtual console and it exits like usual ("Waiting for X
> > > Nope, have you hard-wired the PLL value like I do for other laptops ?
> >
> > Nope, the OF data are used to set up the PLL. Even feeding it utter
> > bullshit for SCLK and MCLK does nothing at all to change the picture.
>
> Wait ... you are talking about console flickering or X flickering ? I
> > I can confirm frequent lockups on GPU load (CPU load doesn't matter,
> > that's handled fine by the thermostat). In case it matters: the OF device
> > tree seems to indicate that the two fans aren't CPU and GPU but rather
> > left and right side of the rear exhaust grille. So they need to be se
On Mon, 2004-09-20 at 18:10, Michael Schmitz wrote:
> > > I can confirm frequent lockups on GPU load (CPU load doesn't matter,
> > > that's handled fine by the thermostat). In case it matters: the OF device
> > > tree seems to indicate that the two fans aren't CPU and GPU but rather
> > > left and
16 matches
Mail list logo
