On 2024-07-07 09:36, mick.crane wrote:
On [cough] Trixie, just how do I change the video driver.
I'm using driver xserver-xorg-video-nvidia-tesla-470 on older kernel
There must have been a reason, likely the available resolution.
With kernel 6.9.7-amd64 have to "startx" and the
On [cough] Trixie, just how do I change the video driver.
I'm using driver xserver-xorg-video-nvidia-tesla-470 on older kernel
There must have been a reason, likely the available resolution.
With kernel 6.9.7-amd64 have to "startx" and then the available displays
in Xfce are
On Wed, 2024-07-03 at 23:24 +0200, Hans wrote:
> I believe I got a solution. However, you may not be happy with it,
> but maybe it will work.
Thanks to Hans for the detailed list, which I was not able to use
successfully. I had probably either broken something first, or didn't
follow the instructi
This should not have been happened. Maybe you dis something in a wrong way?
I treid myself and it did not deinstall kde.
It is important, not to do any upgrade while the entry for sid is in
sources.list.
Just install both packages (as told in the wiki), then after this install
remove the si
On Thu, Jul 04, 2024 at 01:24:21PM -0700, Van Snyder wrote:
> On Wed, 2024-07-03 at 23:24 +0200, Hans wrote:
> > Hi van Snyder,
> >
> > I believe I got a solution. However, you may not be happy with it,
> > but maybe it will work.
>
> The solution did indeed allow to install the driver. But i
On Wed, 2024-07-03 at 23:24 +0200, Hans wrote:
> Hi van Snyder,
>
> I believe I got a solution. However, you may not be happy with it,
> but maybe it will work.
The solution did indeed allow to install the driver. But it removed
at least KDE, and now it won't enter run level 5. I added
nouvea
Tried again, somehow there was no subject sent with my last mail.
So, well, I believe I got a solution. However, not everyone might be happy with
it, but maybe it
will work.
I am running the kernel 6.7.12+bpo-amd64 on my system. This is a backport
kernel, but
it might also work with other
On Wed, Jul 03, 2024 at 11:29:43AM -0700, Van Snyder wrote:
> On Wed, 2024-07-03 at 08:03 +, Andrew M.A. Cater wrote:
> > Resolve never to buy Nvidia again :)
>
> 1) On my brother's antique Dell Vostro 1700 laptop, the NVidia G68M
> (GeForce 8400M GS) is soldered to the motherboard.
>
As abo
Hi van Snyder,
I believe I got a solution. However, you may not be happy with it, but maybe it
will work.
I am running the kernel 6.7.12+bpo-amd64 on my system. This is a backport
kernel, but it
might also work with other kernels, too.
You also need to install the build environment, the eas
On Wed, 2024-07-03 at 08:03 +, Andrew M.A. Cater wrote:
> Resolve never to buy Nvidia again :)
1) On my brother's antique Dell Vostro 1700 laptop, the NVidia G68M
(GeForce 8400M GS) is soldered to the motherboard.
2)I'm running NVidia in two desktops because my erstwhile SA gave them
to me wh
On Wed, Jul 03, 2024 at 02:16:20AM -0400, Felix Miata wrote:
> Van Snyder composed on 2024-06-07 13:29 (UTC-0700):
>
> > The messages I found said "Support for it ended in 2019. Use nouveau."
>
This is support from Nvidia, with official Nvidia proprietary drivers
> > been able to install the dr
Van Snyder composed on 2024-06-07 13:29 (UTC-0700):
> Has anybody been able to install the NVidia 340.108 video driver in
> Debian 12?
> The messages I found said "Support for it ended in 2019. Use nouveau."
It should have said more. Some of what it should have included
Hans:
Thanks for the note. It seems that nouveau is a bit more stable in
Debian 12.5 than it had been in Debian 10.1. At least I hope it is. So
far, it hasn't crashed.
MfG,
Van
On Mon, 2024-06-10 at 10:11 +0200, Hans wrote:
> No, the NV6800M needs 340xx driver, not 390xx as I prior posted. Howev
> In real life no one wants to care of it! Nvidia not, because this
> costs money and the developers not, because this is Nvidia and
> proprietrary (what is not quite correct, because the kernel-module,
> which is the part, that can not be build, is open-source).
Since you say it's "open source
No, the NV6800M needs 340xx driver, not 390xx as I prior posted. However, I
have a GF-119 in my Lenovo T520, where nvidia-detect says, it needs 340xx.
But, although I got 340xx compiled for the kernel, it did not start.
I then build 390xx, which worked like a charm. This happened on my notebook
On Mon, 2024-06-10 at 01:13 +0200, Toni Mas Soler wrote:
> El Fri, 07 Jun 2024 14:56:23 -0700Van Snyder <
> van.sny...@sbcglobal.net> va escriure el següent:
> > On Fri, 2024-06-07 at 22:47 +0200, Hans wrote:
> > > Just a hint: Sometimes the nvidia-config module says, you
> > > need340.xx, but this
El Fri, 07 Jun 2024 14:56:23 -0700
Van Snyder va escriure el següent:
> On Fri, 2024-06-07 at 22:47 +0200, Hans wrote:
> > Just a hint: Sometimes the nvidia-config module says, you need
> > 340.xx, but this is not always true. My card (with th eolder
> > kernel) was running 390.xx, although th es
On 08/06/2024 03:29, Van Snyder wrote:
Has anybody been able to install the NVidia 340.108 video driver in
Debian 12?
I am not aware of current state of affairs. Several years ago it was
possible to rebuild the .deb package (that uses DKMS) with additional
patches to make the code compatible
On Fri, 2024-06-07 at 22:47 +0200, Hans wrote:
> Just a hint: Sometimes the nvidia-config module says, you need 340.xx, but
> this is not always true. My card (with th eolder kernel) was running 390.xx,
> although th esystem told me, I have to use 340.xx. 390.xx was running like a
> charm, 340.x
to install the NVidia 340.108 video driver in
> Debian 12?
>
> The messages I found said "Support for it ended in 2019. Use nouveau."
>
> But I seem to have trouble with nouveau. When I was running Debian 10
> on a Dell Vostro 1700 laptop with NVidia GeForce 8400M graphic
Has anybody been able to install the NVidia 340.108 video driver in
Debian 12?
The messages I found said "Support for it ended in 2019. Use nouveau."
But I seem to have trouble with nouveau. When I was running Debian 10
on a Dell Vostro 1700 laptop with NVidia GeForce 8400M graphics,
k
to get your kernel to list the modes your video bios supports. 796 (0x31C)
likely can provide yet smaller text in 8 bit color, 798 (0x31E) in 16, 799
(0x31F) in 24. I've yet to observe a use for more than 8 bit color in a vtty.
Note that vga= only works in the framebuffers because KMS has b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Jul 25, 2017 at 01:15:48PM -0600, D. R. Evans wrote:
> Felix Miata wrote on 07/23/2017 08:26 PM:
>
> >
> >> I tried this solution (for Arch; I saw some posts about Debian, but nothing
> >> that seemed to be a definitive solution):
> >
> >> h
Felix Miata wrote on 07/23/2017 08:26 PM:
>
>> I tried this solution (for Arch; I saw some posts about Debian, but nothing
>> that seemed to be a definitive solution):
>
>> https://wiki.archlinux.org/index.php/GRUB/Tips_and_tricks#Setting_the_framebuffer_resolution
>
[material elided]
> The c
On Mon, 24 Jul 2017, Greg Wooledge wrote:
> On Mon, Jul 24, 2017 at 02:20:08PM +0100, Darac Marjal wrote:
> > You'd need some sort of system logging daemon. Something which runs with
> > the privileges necessary to write to the log file, and which can accept
> > log messages from unprivileged proce
On Mon, Jul 24, 2017 at 02:20:08PM +0100, Darac Marjal wrote:
> You'd need some sort of system logging daemon. Something which runs with
> the privileges necessary to write to the log file, and which can accept
> log messages from unprivileged processes, perhaps by listening on a UNIX
> socket.
Li
On Mon, Jul 24, 2017 at 08:59:56AM -0400, Greg Wooledge wrote:
On Sat, Jul 22, 2017 at 04:27:42PM -0400, Felix Miata wrote:
I don't often here fail to find a current /var/log/Xorg.0.log. I think what's
happening is the one in .local/share/ is getting copied to /var/log/ so that it
remains availa
On Sat, Jul 22, 2017 at 04:27:42PM -0400, Felix Miata wrote:
> I don't often here fail to find a current /var/log/Xorg.0.log. I think what's
> happening is the one in .local/share/ is getting copied to /var/log/ so that
> it
> remains available in the location people historically expect, where Goo
D. R. Evans composed on 2017-07-23 17:52 (UTC-0600):
> D. R. Evans wrote:
>> I am 99+% sure that the proprietary driver is being used, because the screen
>> looks quite different during the boot sequence, and slightly different once I
> I have discovered that if I open a console after switching
On Sun 23 Jul 2017 at 17:52:19 (-0600), D. R. Evans wrote:
> D. R. Evans wrote on 07/22/2017 11:48 AM:
>
> > I am 99+% sure that the proprietary driver is being used, because the screen
> > looks quite different during the boot sequence, and slightly different once
> > I
>
> I have discovered th
D. R. Evans wrote on 07/22/2017 11:48 AM:
> I am 99+% sure that the proprietary driver is being used, because the screen
> looks quite different during the boot sequence, and slightly different once I
I have discovered that if I open a console after switching to the NVIDIA
driver, the text is hug
haracters to type.
> Kind of a roundabout, teach a fish to fly kind of thing, but Reco is
> twisted.
> Actually just kidding.
> How 'bout
> grep -B2 'Module class: X.Org Video Driver' /var/log/Xorg.0.log
Is a mere mortal going to know, seeing the following
message indicates the OP is using the proprietary
driver, for which KMS must be enabled manually.
Kind of a roundabout, teach a fish to fly kind of thing, but Reco is
twisted.
Actually just kidding.
How 'bout
grep -B2 'Module class: X.Org Video Driver' /var/log/Xorg.0.log
But t
D. R. Evans composed on 2017-07-22 13:06 (UTC-0600):
> Reco wrote:
>> grep -i glx ~/.local/share/xorg/Xorg.[0-9]*.log
> [HN:~] grep -i glx ~/.local/share/xorg/Xorg.[0-9]*.log
> grep: /home/n7dr/.local/share/xorg/Xorg.[0-9]*.log: No such file or directory
> [HN:~]
>
I don't know why he suggeste
Hans wrote on 07/22/2017 11:55 AM:
> Maybe try to add a file /etc/X11/xorg.conf (ask google, how it has to look),
> and in it set the driver "nvidia".
>
nvidia-xconfig created such a file, and the driver in it is set to "nvidia",
so I think that is indeed the confirmation I was looking for.
Tha
Reco wrote on 07/22/2017 12:37 PM:
> grep -i glx ~/.local/share/xorg/Xorg.[0-9]*.log
[HN:~] grep -i glx ~/.local/share/xorg/Xorg.[0-9]*.log
grep: /home/n7dr/.local/share/xorg/Xorg.[0-9]*.log: No such file or directory
[HN:~]
Doc
--
Web: http://enginehousebooks.com/drevans
signature.asc
De
Hi.
On Sat, 22 Jul 2017 11:48:42 -0600
"D. R. Evans" wrote:
> As my old thread has been hijacked, I thought that I'd better start a new one.
>
> Teemu Likonen wrote on 07/17/2017 03:09 PM:
> > D. R. Evans [2017-07-17 14:19:32-06] wrote:
> >
> >> Beginning a couple of weeks ago, I starte
Maybe try to add a file /etc/X11/xorg.conf (ask google, how it has to look),
and in it set the driver "nvidia".
Make sure, the nouveau kernel driver is blacklisted.
BTW: Is the proprietrary driver compatible with latest xserver-xorg again?
Best regards
Hans
> Thanks to people for their helpfu
As my old thread has been hijacked, I thought that I'd better start a new one.
Teemu Likonen wrote on 07/17/2017 03:09 PM:
> D. R. Evans [2017-07-17 14:19:32-06] wrote:
>
>> Beginning a couple of weeks ago, I started to experience occasional freezes
>> or
>> sudden blank screens on my 64-bit jess
On Tue 18 Jul 2017 at 16:05:48 -0400, Fungi4All wrote:
> From: to...@tuxteam.de
> >Because there"s more control by civil society of the tools shaping
> >our future?
> What control does society have over science and technology? None!
Bollocks. We no longer have the chariot or leeches.
> What cont
On Tue 18 Jul 2017 at 21:20:42 +0200, to...@tuxteam.de wrote:
> On Tue, Jul 18, 2017 at 01:25:34PM -0500, Doug wrote:
> [...]
>
> > My point is that most of the folks who complain about code not being
> > free to modify are not capable of modifying it, so why do they
> > complain?
>
> Because th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Jul 18, 2017 at 04:05:48PM -0400, Fungi4All wrote:
> From: to...@tuxteam.de
> >Because there"s more control by civil society of the tools shaping
> >our future?
> What control does society have over science and technology? None!
> What control
From: to...@tuxteam.de
>Because there"s more control by civil society of the tools shaping
>our future?
What control does society have over science and technology? None!
What control does society have over religious beliefs? None!
What control does society have over media and information? None!
Wha
On Tue, Jul 18, 2017 at 01:25:34PM -0500, Doug wrote:
>
> On 07/18/2017 05:52 AM, RavenLX wrote:
> > On 07/18/2017 01:43 AM, Brad Rogers wrote:
> > > On Mon, 17 Jul 2017 22:38:55 -0500
> > > Doug wrote:
> > >
> > > Hello Doug,
> > >
> > > > I get so sick of this! Did you PAY for your nvidia sof
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Jul 18, 2017 at 01:25:34PM -0500, Doug wrote:
[...]
> My point is that most of the folks who complain about code not being
> free to modify are not capable of modifying it, so why do they
> complain?
Because they sympathize with those who can
On Tue, 18 Jul 2017 13:25:34 -0500
Doug wrote:
Hello Doug,
>My point is that most of the folks who complain about code not being
>free to modify are not capable of modifying it, so why do they complain?
For the same reason people take an idealogical stance on anything -
Ability to act on their
Doug [2017-07-18 13:25:34-05] wrote:
> My point is that most of the folks who complain about code not being
> free to modify are not capable of modifying it, so why do they
> complain?
Free software has the advantage that it does not depend on just one
company and its interests. A free software c
On 07/18/2017 05:52 AM, RavenLX wrote:
On 07/18/2017 01:43 AM, Brad Rogers wrote:
On Mon, 17 Jul 2017 22:38:55 -0500
Doug wrote:
Hello Doug,
I get so sick of this! Did you PAY for your nvidia software? No? then
Anyone that buys an nVidia chipset GFX card pays for the nVidia
drivers -
wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Jul 18, 2017 at 01:09:53PM +0100, Brad Rogers wrote:
> On Tue, 18 Jul 2017 06:52:05 -0400
> RavenLX wrote:
>
> Hello RavenLX,
>
> >This poses an interesting question: Why would a company keep something
> >proprietary such as a driver?
>
>
On Tue, 18 Jul 2017 06:52:05 -0400
RavenLX wrote:
Hello RavenLX,
>This poses an interesting question: Why would a company keep something
>proprietary such as a driver?
Control. And the (misguided?) belief that they'll end up fielding tech
support questions for driver modifications they didn't
On 07/18/2017 01:43 AM, Brad Rogers wrote:
On Mon, 17 Jul 2017 22:38:55 -0500
Doug wrote:
Hello Doug,
I get so sick of this! Did you PAY for your nvidia software? No? then
Anyone that buys an nVidia chipset GFX card pays for the nVidia drivers -
whether they use them, or not.
it was FREE!
On Mon, 17 Jul 2017 22:38:55 -0500
Doug wrote:
Hello Doug,
>I get so sick of this! Did you PAY for your nvidia software? No? then
Anyone that buys an nVidia chipset GFX card pays for the nVidia drivers -
whether they use them, or not.
>it was FREE!
No, it wasn't. Cost is hidden, but is still
On 07/17/2017 04:09 PM, Teemu Likonen wrote:
D. R. Evans [2017-07-17 14:19:32-06] wrote:
Beginning a couple of weeks ago, I started to experience occasional freezes or
sudden blank screens on my 64-bit jessie system.
Jul 17 13:58:23 homebrew kernel: [24262.075187] nouveau E[ DRM] GPU locku
D. R. Evans [2017-07-17 14:19:32-06] wrote:
> Beginning a couple of weeks ago, I started to experience occasional freezes or
> sudden blank screens on my 64-bit jessie system.
> Jul 17 13:58:23 homebrew kernel: [24262.075187] nouveau E[ DRM] GPU lockup
> - switching to software fbcon
>
> I do
On 2017-07-17 14:19 -0600, D. R. Evans wrote:
> Beginning a couple of weeks ago, I started to experience occasional freezes or
> sudden blank screens on my 64-bit jessie system.
>
> It just happened again, and this time the following appeared in the syslog:
> Jul 17 13:55:05 homebrew kernel: [24
D. R. Evans composed on 2017-07-17 14:19 (UTC-0600):
> Beginning a couple of weeks ago, I started to experience occasional freezes or
> sudden blank screens on my 64-bit jessie system.
> It just happened again, and this time the following appeared in the syslog:
> Jul 17 13:55:05 homebrew kerne
Beginning a couple of weeks ago, I started to experience occasional freezes or
sudden blank screens on my 64-bit jessie system.
It just happened again, and this time the following appeared in the syslog:
Jul 17 13:55:05 homebrew kernel: [24064.296254] nouveau E[
PFIFO][:01:00.0] write fault
Hi...OP here...
Does anyone have any suggestions on the original problem with video on the
Intel drivers on this Dell laptop?
Thanks,
--b
On Thu, May 22, 2014 at 6:22 AM, Brian wrote:
> On Thu 22 May 2014 at 12:49:43 +0300, Pertti Kosunen wrote:
>
> > On 22.5.2014 11:15, Tom H wrote:
> > >You
On Thu 22 May 2014 at 12:49:43 +0300, Pertti Kosunen wrote:
> On 22.5.2014 11:15, Tom H wrote:
> >You must've missed the recent thread about systemd-sysv being pulled
> >in by certain dependencies and replacing sysvinit with systemd.
>
> What was the name of this thread?
https://lists.debian.org
On 22.5.2014 11:15, Tom H wrote:
You must've missed the recent thread about systemd-sysv being pulled
in by certain dependencies and replacing sysvinit with systemd.
What was the name of this thread?
Must be some desktop related packages, my few headless systems still
have only sysv stuff?
On Wed, May 21, 2014 at 6:52 AM, Pertti Kosunen
wrote:
> On 21.5.2014 2:43, Brad Alexander wrote:
>>
>> I apologize, I thought I had specified, the machine in question is
>> running a relatively recent version of sid. I have not been upgrading as
>> much until some of this chaos with systemd settl
On 21.5.2014 2:43, Brad Alexander wrote:
I apologize, I thought I had specified, the machine in question is
running a relatively recent version of sid. I have not been upgrading as
much until some of this chaos with systemd settles down.
You can upgrade safely, systemd will not replace already
Thanks Filip,
On Tue, May 20, 2014 at 2:08 AM, Filip wrote:
> On Mon, 19 May 2014 19:18:38 -0400
>
> Intel video is normally working out of the box, but for newer
> hardware you also need up to date software.
>
> So if you are on 7.5, try upgrading Jessie.
>
I apologize, I thought I had specifi
On Mon, 19 May 2014 19:18:38 -0400
Brad Alexander wrote:
> I hope I don't run afoul of the self-imposed list monitors or
> otherwise fan a flame war...:)
>
> I have been using nvidia cards in my computers for so long that I
> haven't really kept up with the state of Intel...
>
> My problem is t
I hope I don't run afoul of the self-imposed list monitors or otherwise fan
a flame war...:)
I have been using nvidia cards in my computers for so long that I haven't
really kept up with the state of Intel...
My problem is that when I try to play a video on this machine, either with
mplayer or vl
On Wed, 13 Jul 2011 13:01:36 -0700, Tech wrote in message
:
> In Debian Lenny, X server use to correctly load the video driver
> (mach64_drv.so) for my VGA card:
> debian:~# lspci -v | grep VGA
> 00:01.0 VGA compatible controller: ATI Technologies Inc Rage Mobility
> P/M (rev
Tech:
>Yes, I am aware of that, except that, in this case X does not detect
>the correct driver automagically...:)
You can create one w/ default options w/
X -configure
then specify only those options You need. For others will be loaded by
the server automatically - for now-days it works pretty
On Wednesday 13 July 2011 12:07:56 pm Tech Geek wrote:
> >There isn't one 'cos X nowadays automagically detect everything - when
> > it does.
>
> Yes, I am aware of that, except that, in this case X does not detect
> the correct driver automagically...:)
You can still use an 'xorg.conf' file. You
>There isn't one 'cos X nowadays automagically detect everything - when
> it does.
Yes, I am aware of that, except that, in this case X does not detect
the correct driver automagically...:)
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble
On Wed, Jul 13, 2011 at 21:01, Tech Geek wrote:
> So how do I tell X to load the ati driver? Explicitly specify it in
> xorg.conf file? Currently, I there is no such file in /etc/X11
> directory.
>
There isn't one 'cos X nowadays automagically detect everything - when
it does. Create one. See man
In Debian Lenny, X server use to correctly load the video driver
(mach64_drv.so) for my VGA card:
debian:~# lspci -v | grep VGA
00:01.0 VGA compatible controller: ATI Technologies Inc Rage Mobility
P/M (rev 64) (prog-if 00 [VGA controller])
After upgrading to Squeeze, X server defaults to vesa
On Sat, 11 Sep 2010 15:41:11 -0700, Arthur Barlow wrote:
> Ever since Debian went to the "nouveau" video driver for Nvidia, I have
> not been able to adjust my horizontal screen position with xvidtune. The
> application runs, but when I try to reset the "HSyncStart"
Oops. Wrong list originally
-- Forwarded message --
From: Arthur Barlow
Date: Sat, Sep 11, 2010 at 2:05 PM
Subject: xvidtune and nouveau video driver
To: freebsd-questi...@freebsd.org
Ever since Debian went to the "nouveau" video driver for Nvidia, I have not
be
I reply myself
It is a known probem:
http://groups.google.co.kr/group/fa.linux.kernel/browse_thread/thread/000eb65f2fbe06a8
So I guess I must wait for it to be fixed.
Thierry
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
rom 2.6.28 to 2.6.30, backlight
setting does not work any longer, and the brightness seems to be set at random
level at boot time. My laptop is an aspire 5715Z.
dmesg gives:
dmesg |grep video
[7.161248] acer-wmi: Brightness must be controlled by generic video driver
[ 27.366381] ACPI Er
Solved. Xorg was outdated. Updated with dselect, and the nvidia
driver works now. Thanks to Lennart Sorensen for pointing me in
the right direction!
Original Message
Subject:Nvidia video driver problem
Resent-Date:Thu, 11 Sep 2008 16:17:41 + (UTC)
Resent-From
On Thu, Sep 11, 2008 at 11:16:00AM -0500, Russ Cook wrote:
> I'm running an amd64, with 64bit linux (Sid), with evga 8800gts graphics
> card.
> I did apt-get update && upgrade today.
> Then I downloaded latest linux source 2.6.26.5 from kernel.org, and
> downloaded
> the latest nvidia-kernel-sour
I'm running an amd64, with 64bit linux (Sid), with evga 8800gts graphics
card.
I did apt-get update && upgrade today.
Then I downloaded latest linux source 2.6.26.5 from kernel.org, and
downloaded
the latest nvidia-kernel-source using apt-get.
I compiled a custom kernel and latest nvidia-kernel
On Fri, Aug 18, 2006 at 14:41:43 +0100, George Borisov wrote:
> Florian Kulzer wrote:
> >
> > 3) "make-kpkg --initrd --append-to-version=-custom1 --revision=00
> >kernel_image" will compile the kernel and build a .deb package in
> >/usr/src. You can of course choose your own name for "-cus
Florian Kulzer wrote:
>
> 3) "make-kpkg --initrd --append-to-version=-custom1 --revision=00
>kernel_image" will compile the kernel and build a .deb package in
>/usr/src. You can of course choose your own name for "-custom1"and if
>you compile more than once (with different configuratio
On Fri, 18 Aug 2006, Florian Kulzer wrote:
1) After you have untarred the linux source, cd to its directory and run
either "make menuconfig" or "make oldconfig". This will import the
kernel configuration of the currently running kernel. (You could also
copy the config file manually from /b
Brandon Kuczenski wrote:
...
Thanks for your reply. I decided to upgrade my kernel since it was old
anyway. I used make-kpkg on the source tree that comes with the debian
package linux-source-2.6.16 (My apt-get can't find a 2.6.17 version),
which seemed to work. However, my resulting kernel
On Thu, Aug 17, 2006 at 18:34:57 -0400, Brandon Kuczenski wrote:
> On Wed, 16 Aug 2006, Florian Kulzer wrote:
>
> >On Wed, Aug 16, 2006 at 04:29:08 -0400, Brandon Kuczenski wrote:
> >>I am running debian-testing on linux 2.6.8 on an IBM T23 laptop. This
> >>...
> >>...
> >>I searched the computer
On Wed, 16 Aug 2006, Florian Kulzer wrote:
On Wed, Aug 16, 2006 at 04:29:08 -0400, Brandon Kuczenski wrote:
I am running debian-testing on linux 2.6.8 on an IBM T23 laptop. This
...
...
I searched the computer and savage.ko is nowhere to be found. What's the
best way to obtain this module und
On Wed, Aug 16, 2006 at 04:29:08 -0400, Brandon Kuczenski wrote:
> I am running debian-testing on linux 2.6.8 on an IBM T23 laptop. This
> system has been running for about 2 years. I recently upgraded XFree86 to
> Xorg (running 7.0.0) and now my video card direct rendering has stopped
> worki
Brandon Kuczenski wrote:
I am running debian-testing on linux 2.6.8 on an IBM T23 laptop. This
system has been running for about 2 years. I recently upgraded XFree86
to Xorg (running 7.0.0) and now my video card direct rendering has
stopped working. I extracted the following lines from my Xo
I am running debian-testing on linux 2.6.8 on an IBM T23 laptop. This
system has been running for about 2 years. I recently upgraded XFree86 to
Xorg (running 7.0.0) and now my video card direct rendering has stopped
working. I extracted the following lines from my Xorg logfile:
...
drmOpenD
Henrique Rennó wrote:
> One more question.
>
> When I boot my system directly to X (passing 5 at inittab) it stops at
> a login screen and it enters in blackbox (the X manager that I am
> using) but without running bbkeys. I've put the "/usr/bin/bbkeys &"
> command in the /etc/X11/xinit/xinitrc fi
One more question.
When I boot my system directly to X (passing 5 at inittab) it stops at
a login screen and it enters in blackbox (the X manager that I am
using) but without running bbkeys. I've put the "/usr/bin/bbkeys &"
command in the /etc/X11/xinit/xinitrc file before "/usr/bin/blackbox"
but
Hello!!!
I have an Acer Aspire 3002LCI laptop with Debian Sarge 3.1 installed
on it and I'm using the VESA driver which gives me a resolution of
640x480. I want to know what driver I must choose when running
xf86config to get better resolutions.
My lscpi (just what is related to video):
:00:
I love my debian system, but I seem to have a problem with the video being
really slow. I can see the screen being drawn each time I log in. I am
running testing with kernel 2.6.12-1-686
I seem to have two xservers installed, apt-cache showpkg xserver-XFree86
6.8.2.dfsg.1-11
4.3.0.dfsg.1-14sarg
On torsdag 15 september 2005, 16:40, michael bailey wrote:
> Running Debian Sarge on an Intel P3 machine, twice in
> the past two weeks the screen has frozen completely
> and the Caps Lock and Scroll Lock green lights have
> started flashing rapidly. The mouse and keyboard then
> both don't work a
On Thursday 15 September 2005 09:40, michael bailey wrote:
> Is Sarge poosibly incompatible with the video driver
>in the Matrox G200 SD card that is used ?
Anything is possible, but i have Sarge running with a Matrox G200 on a
dual processor P-II 450 at home and it is perfectly stable. Th
here are some xterms open and a couple of Mozilla
windows. There are no programs running and the
websites in the Mozilla browsers are basic, such as
cnn.com, nothing with any complicated movies or
anything like that.
Is Sarge poosibly incompatible with the video driver
in the Matrox G200
On Monday 06 October 2003 16:08, Ogulla, Alphonse wrote:
> -Original Message-
> From: Nicos Gollan [mailto:[EMAIL PROTECTED]
> Sent: 06 October 2003 13:17
> To: [EMAIL PROTECTED]
> Subject: Re: Xv video driver expires after xfree86 upgrade
>
> On Monday 06 October
On Monday 06 October 2003 18:18, Roberto Sanchez wrote:
> Is it a laptop? I had a problem with my laptop where if the X server
> was started while I had video output going to an external monitor Xv
> playback would bluescreen. If I started the X server with video to the
> builtin LCD it worked fi
Alphonse Ogulla wrote:
What graphics driver are you using (what video card)? Ist the XVideo
extension
listed in xdpyinfo?
onboard Intel 810e graphics adaptor.
xdpyinfo lists XVideo amongst 27 other extensions
Is it a laptop? I had a problem with my laptop where if the X server
was started whil
> On Monday 06 October 2003 11:21, Alphonse Ogulla wrote:
> > Up to very recently, I could watch vcd movies on my box using xine video
> > player with Xv as the video driver. However, I came to discover yesterday
> > that Xv video driver had become inoperative after either
On Monday 06 October 2003 11:21, Alphonse Ogulla wrote:
> Up to very recently, I could watch vcd movies on my box using xine video
> player with Xv as the video driver. However, I came to discover yesterday
> that Xv video driver had become inoperative after either upgrading xfree86
>
Hi all,
Up to very recently, I could watch vcd movies on my box using xine video
player with Xv as the video driver. However, I came to discover yesterday
that Xv video driver had become inoperative after either upgrading xfree86
from version 4.1.0 to 4.2.1 using the deb package or installation
1 - 100 of 108 matches
Mail list logo
