Re: deb12 for amd64 can't start X

On 12/5/23 09:10, Felix Miata wrote: This commonly results from some package(s) missing, or that prevents use of available software, such as malconfiguration or software left behind by having had an NVidia card installed previously, not because your GPU or modesetting are not supported. [KMS]

Re: deb12 for amd64 can't start X

it doesn't look right even in text mode, font used is somewhat different it's really not ok with 12.2 for amd64 while it's ok with 12.0 for i386 X.Org X Server 1.21.1.7 X Protocol Version 11, Revision 0 Current Operating System: Linux bw 6.1.0-9-686-pae #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2

Re: deb12 for amd64 can't start X

hlyg composed on 2023-12-05 07:32 (UTC+0800): > 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. > [AMD/ATI] Wrestler [Radeon HD 6250] > it's ok with deb12 for i386 > i think "[KMS] drm report modesetting isn't supported" below offer clue > X.Org X Server 1.21.1.7 > X Protocol V

deb12 for amd64 can't start X

00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6250] it's ok with deb12 for i386 i think "[KMS] drm report modesetting isn't supported" below offer clue X.Org X Server 1.21.1.7 X Protocol Version 11, Revision 0 Current Operating System: Linux debi

[SOLVED] Re: [Buster]: Can't start X: no screens found(EE)

Aug 27, 2018, 12:35 PM by mrma...@earthlink.net: > These suggest you are missing a firmware package for your Radeon HD 4200. > firmware-linux & firmware-linux-non-free are meta packages. Likely you only > need > firmware-amd-graphics and/or firmware-linux-free and/or firmware-misc-nonfree. > "fi

Re: [Buster]: Can't start X: no screens found(EE)

On Mon, 27 Aug 2018 18:07:18 +0200 (CEST) local10 wrote: > Hi, > > Am trying to upgrade a Debian Wheezy PC to Buster. The PC was > successfully running Wheezy with KDE as desktop, in terms of hardware > there are no changes. Initially, sddm was intalled to start KDE but > that did not work for s

Re: [Buster]: Can't start X: no screens found(EE)

local10 composed on 2018-08-27 18:07 (UTC+0200): > # grep "(EE)" .local/share/xorg/Xorg.0.log > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > [  1102.702] (EE) open /dev/dri/card0: No such file or directory > [  1102.702] (EE) open /dev/dri/card0: No such file or directory > [  1

Re: [Buster]: Can't start X: no screens found(EE)

Attached the correct log file. [ 1102.295] X.Org X Server 1.20.1 X Protocol Version 11, Revision 0 [ 1102.295] Build Operating System: Linux 4.9.0-7-amd64 x86_64 Debian [ 1102.295] Current Operating System: Linux tstsrv 4.17.0-3-amd64 #1 SMP Debian 4.17.17-1 (2018-08-18) x86_64 [ 1102.295] K

[Buster]: Can't start X: no screens found(EE)

Hi, Am trying to upgrade a Debian Wheezy PC to Buster. The PC was successfully running Wheezy with KDE as desktop, in terms of hardware there are no changes. Initially, sddm was intalled to start KDE but that did not work for some reason, so now I starting KDE manually with startx. Any ideas?

Re: From wheezy to stretch: can't start X session when logging in from kdm

On Sun, 8/23/15, Jimmy Johnson wrote: // While kdm still works in upstream stretch/testing, I've been told it is // no longer being supported by systemd and has been replaced with sddm, // but if you want to see your desktop currently you need to follow the // instructions I gave you. For plasma

Re: From wheezy to stretch: can't start X session when logging in from kdm

On 08/23/2015 01:19 PM, Ldten K wrote: On Sun, 8/23/15, Jimmy Johnson wrote: It's a bug, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796098 It may be the same issue though I'm not sure why I was getting the error about missing /home/luser/.Xsession file. I manually copied /etc/kde4/kd

Re: From wheezy to stretch: can't start X session when logging in from kdm

On Sun, 8/23/15, Jimmy Johnson wrote: > It's a bug, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796098 It may be the same issue though I'm not sure why I was getting the error about missing /home/luser/.Xsession file. I manually copied /etc/kde4/kdm/Xsession file as /home/luser/.Xsession

Re: From wheezy to stretch: can't start X session when logging in from kdm

On 08/23/2015 02:16 AM, Ldten K wrote: Hi, Tried upgrading from wheezy to stretch, just to see how it would go. It mostly went OK though there is an issue: when trying to log in from kdm the system now complains that it's unable to start X session --- no /home/luser/.xsession file, no /home/l

From wheezy to stretch: can't start X session when logging in from kdm

Hi, Tried upgrading from wheezy to stretch, just to see how it would go. It mostly went OK though there is an issue: when trying to log in from kdm the system now complains that it's unable to start X session --- no /home/luser/.xsession file, no /home/luser/.Xsession file, no session managers,

Re: Vidio card recommendation needed (was:Re: Can't start X after upgrade to Lenny)

On Sat, Jan 24, 2009 at 16:39, Micha Feigin wrote: > On Sun, 25 Jan 2009 06:29:56 +1030 > Arthur Marsh wrote: > >> Marc Shapiro wrote, on 2009-01-25 04:50: >> > I posted this under the original thread, but since there were no >> > responses I figured that most readers had already determined that

Re: Vidio card recommendation needed (was:Re: Can't start X after upgrade to Lenny)

On 01/24/2009 05:07 PM, Marc Shapiro wrote: Ron Johnson wrote: IMNSHO, unless this is a *workstation* where you do lots of OpenGL visualization, or you are dual-booting to play Crysis, Linux users just don't *need* uber-video performance. Thus, I go for good-enough-but-silent over raw power

Re: Vidio card recommendation needed (was:Re: Can't start X after upgrade to Lenny)

On Sun, 25 Jan 2009 06:29:56 +1030 Arthur Marsh wrote: > Marc Shapiro wrote, on 2009-01-25 04:50: > > I posted this under the original thread, but since there were no > > responses I figured that most readers had already determined that they > > could not help with that problem and so did not r

Re: Vidio card recommendation needed (was:Re: Can't start X after upgrade to Lenny)

Ron Johnson wrote: IMNSHO, unless this is a *workstation* where you do lots of OpenGL visualization, or you are dual-booting to play Crysis, Linux users just don't *need* uber-video performance. Thus, I go for good-enough-but-silent over raw power which is overkill 99.999% of the time (espe

Re: Vidio card recommendation needed (was:Re: Can't start X after upgrade to Lenny)

On 01/24/2009 02:58 PM, Marc Shapiro wrote: Ron Johnson wrote: On 01/24/2009 12:20 PM, Marc Shapiro wrote: I don't think that I have actually purchased a video card separate from the PC, or motherboard since my TRS-8- Model III died and I bought my first PC compatible. That would have been abou

Re: Vidio card recommendation needed (was:Re: Can't start X after upgrade to Lenny)

Ron Johnson wrote: On 01/24/2009 12:20 PM, Marc Shapiro wrote: I don't think that I have actually purchased a video card separate from the PC, or motherboard since my TRS-8- Model III died and I bought my first PC compatible. That would have been about 26 years ago. Getting a new board might not

Re: Vidio card recommendation needed (was:Re: Can't start X after upgrade to Lenny)

On 01/24/2009 12:20 PM, Marc Shapiro wrote: I posted this under the original thread, but since there were no responses I figured that most readers had already determined that they could not help with that problem and so did not read the post. Since this is a totally different track to solving

Re: Vidio card recommendation needed (was:Re: Can't start X after upgrade to Lenny)

Marc Shapiro wrote, on 2009-01-25 04:50: I posted this under the original thread, but since there were no responses I figured that most readers had already determined that they could not help with that problem and so did not read the post. Since this is a totally different track to solving my

Vidio card recommendation needed (was:Re: Can't start X after upgrade to Lenny)

I posted this under the original thread, but since there were no responses I figured that most readers had already determined that they could not help with that problem and so did not read the post. Since this is a totally different track to solving my problem I felt a new subject was in order

Re: Can't start X after upgrade to Lenny

Florian Kulzer wrote: I would probably be tempted to buy an nvidia or ati card and dump the sis driver. I don't think that I have actually purchased a video card separate from the PC, or motherboard since my TRS-8- Model III died and I bought my first PC compatible. That would have been about

Re: Can't start X after upgrade to Lenny

>> > It worked fine in Etch and I really don't want to spend money on a new > card if I don't have to. > if it was working in etch it's well supported. I have experienced similar problems when changing Xorg versions. Finally I read a bit about the new Xorg config and fixed it myself. The wor

Re: Can't start X after upgrade to Lenny

On Wed, 21 Jan 2009 19:27:05 +0100 Florian Kulzer wrote: ... > You can use the web interface of the BTS to send a follow-up message, I know Florian knows this, but just FTR: this can also be accomplished by simply sending mail to nnn...@bugs.debian.org Celejar -- mailmin.sourceforge.net - remo

Re: Can't start X after upgrade to Lenny

Florian Kulzer wrote: On Tue, Jan 20, 2009 at 20:21:19 -0800, Marc Shapiro wrote: Florian Kulzer wrote: Maybe this is related: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=474504 This seems to be exactly the problem that I am having. If this problem has been around sin

Re: Can't start X after upgrade to Lenny

On Tue, Jan 20, 2009 at 20:21:19 -0800, Marc Shapiro wrote: > Florian Kulzer wrote: >> Maybe this is related: >> >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=474504 >> > This seems to be exactly the problem that I am having. If this problem > has been around since at least April of las

Re: Can't start X after upgrade to Lenny

Florian Kulzer wrote: Maybe this is related: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=474504 This seems to be exactly the problem that I am having. If this problem has been around since at least April of last year and had not been resolved by August, you would think that there woul

Re: Can't start X after upgrade to Lenny

On Mon, Jan 19, 2009 at 18:59:12 -0800, Marc Shapiro wrote: > Florian Kulzer wrote: >> On Mon, Jan 19, 2009 at 07:37:41 -0800, Marc Shapiro wrote: [...] >>> I have checked, and most of the xserver-xorg-video-* files are >>> installed. Specifically, xserver-xorg-video-all, >>> xserver-xorg-

Re: Can't start X after upgrade to Lenny

Florian Kulzer wrote: On Mon, Jan 19, 2009 at 07:37:41 -0800, Marc Shapiro wrote: Bibek Paudel wrote: I haven't seen your error messages in detail but I have seen a couple of similar problems after the etch-lenny upgrade. please see if the proper drivers are installed. i found that t

Re: Can't start X after upgrade to Lenny

On Mon, Jan 19, 2009 at 07:37:41 -0800, Marc Shapiro wrote: > Bibek Paudel wrote: >> I haven't seen your error messages in detail but I have seen a couple >> of similar problems after the etch-lenny upgrade. please see if the >> proper drivers are installed. i found that the xserver-xorg-video-

Re: Can't start X after upgrade to Lenny

> > I have checked, and most of the xserver-xorg-video-* files are installed. > Specifically, xserver-xorg-video-all, xserver-xorg-video-sis, and > xserver-xorg-video-vesa are all installed. How do I instruct xorg to use a > specific driver. A couple of years back, I remember xorg.conf having l

Re: Can't start X after upgrade to Lenny

Bibek Paudel wrote: I haven't seen your error messages in detail but I have seen a couple of similar problems after the etch-lenny upgrade. please see if the proper drivers are installed. i found that the xserver-xorg-video-* packages are generally missing after the upgrade. please try instal

Re: Can't start X after upgrade to Lenny

I haven't seen your error messages in detail but I have seen a couple of similar problems after the etch-lenny upgrade. please see if the proper drivers are installed. i found that the xserver-xorg-video-* packages are generally missing after the upgrade. please try installing them, esp the ones f

Re: Can't start X after upgrade to Lenny

Marc Shapiro wrote: Marc Shapiro wrote: I decided that it was time to upgrade to Lenny so that I could use Firefox 3 since I have heard that might eliminate some of the lockups that I have been having. My box has a PC Chips K8 motherboard with SiS 760GX/964 Chipset and an Athlon XP 800+ CPU.

Re: Can't start X after upgrade to Lenny

Marc Shapiro wrote: I decided that it was time to upgrade to Lenny so that I could use Firefox 3 since I have heard that might eliminate some of the lockups that I have been having. My box has a PC Chips K8 motherboard with SiS 760GX/964 Chipset and an Athlon XP 800+ CPU. This is what I have

Can't start X after upgrade to Lenny

I decided that it was time to upgrade to Lenny so that I could use Firefox 3 since I have heard that might eliminate some of the lockups that I have been having. My box has a PC Chips K8 motherboard with SiS 760GX/964 Chipset and an Athlon XP 800+ CPU. This is what I have done: changed my etc/

Re: Can't start X-Server as normal user

[EMAIL PROTECTED] wrote: # startx ...works $ startx ...does not In /home/sam/.xsession-errors I can see Xsession: X session started for sam at Fre Jul 25 09:07:21 CEST 2008 open: Permission denied Now, I saw somewhere on the web[1] that chmod 1777 /tmp might solve the problem. I remember t

Re: Can't start X-Server as normal user

> # startx ...works $ startx ...does not In > /home/sam/.xsession-errors I can see Xsession: X session started > for sam at Fre Jul 25 09:07:21 CEST 2008 open: Permission denied Now, I saw somewhere on the web[1] that chmod 1777 /tmp might solve the problem. I remember that I was not able to wr

Re: Can't start X-Server as normal user

># startx ...works >$ startx ...does not > In /home/sam/.xsession-errors I can see > Xsession: X session started for sam at Fre Jul 25 09:07:21 CEST 2008 > open: Permission denied Now, I saw somewhere on the web[1] that chmod 1777 /tmp might solve the problem. I remember that I was not able to wr

Re: Can't start X-Server as normal user

>> # startx ...works >> $ startx ...does not > I would start by looking in /etc/X11/Xwrapper.config and making sure the > "allowed_users" line equals "console". less /etc/X11/Xwrapper.config [snip] allowed_users=console nice_value=0 I also tried to post less /var/log/Xorg.0.log but failed twice

Re: Can't start X-Server as normal user

-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Can't start X-Server as normal user

>> # startx ...works >> $ startx ...does not > I would start by looking in /etc/X11/Xwrapper.config and making sure the > "allowed_users" line equals "console". less /etc/X11/Xwrapper.config # Xwrapper.config (Debian X Window System server wrapper configuration file) # # This file was generated b

Re: Can't start X-Server as normal user

-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Can't start X-Server as normal user

On Thu,24.Jul.08, 19:49:23, [EMAIL PROTECTED] wrote: > # startx ...works > $ startx ...does not It would be useful to see the error messages on that one. Also /var/log/Xorg.0.log might have some clues. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (A

Re: Can't start X-Server as normal user

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/24/08 14:49, [EMAIL PROTECTED] wrote: > Hi everyone > > > # startx ...works > $ startx ...does not > > The last thing I can remember I was doing before > the problem started was > > $ xauth extract mykey :0 > # xauth merge mykey > # fooprogra

Re: Can't start X-Server as normal user

[EMAIL PROTECTED] wrote: > Hi everyone > > > # startx ...works > $ startx ...does not I would start by looking in /etc/X11/Xwrapper.config and making sure the "allowed_users" line equals "console". -- Kent West <*)))>< http://kentwest.blogspot.com -- To UNSUBSCRIBE, email to [EMAIL PROTEC

Can't start X-Server as normal user

Hi everyone # startx ...works $ startx ...does not The last thing I can remember I was doing before the problem started was $ xauth extract mykey :0 # xauth merge mykey # fooprogramm & What I already tryed to solve the problem: (I) # aptitude --purge # aptitude --purge # aptitude --purge

Re: Can't start X

I finally fixed this last night by using Xorg 6.8. Thanks to those that tried to help!On 3/17/06, Mike Smith < [EMAIL PROTECTED]> wrote:...and stupid mmiikkee12 does the same thing again. I thought I sent that to the list.Anyway, I had X working at one time on this same computer. But then my net co

Re: Can't start X

...and stupid mmiikkee12 does the same thing again.I thought I sent that to the list.Anyway, I had X working at one time on this same computer. But then my net connection got shut off for a while and I switched back to Windows temporarily. This is my first Linux install since then. On 3/17/06, Mike

Re: Can't start X

Kent West wrote: > Mike Smith wrote: > > >>No, there's no setting in my BIOS for that. And I don't think an i810 >>has much memory anyway ;-) >> > > An i810, (in my experience at least) uses shared memory. If your BIOS > doesn't have such a setting, then the BIOS must firm-code it, which > seems

Re: Can't start X

Mike Smith wrote: > No, there's no setting in my BIOS for that. And I don't think an i810 > has much memory anyway ;-) > An i810, (in my experience at least) uses shared memory. If your BIOS doesn't have such a setting, then the BIOS must firm-code it, which seems a bit odd to me. In that case, yo

Re: Can't start X

Mike Smith wrote: > Oh, forgot to mention - the X server was crashing because of signal > 11, which according to kill -l is a segfault. (which is bad.) > > On 3/17/06, *Mike Smith* <[EMAIL PROTECTED] > > wrote: > > -Etch > -haven't checked yet, I know I have an In

Re: Can't start X

Mike Smith wrote: > No, I was not saying you're a bot. There's some thing that keeps wanting > me to confirm the messages I send to this list. Sorry for the > misunderstanding but it's getting annoying and I just subscribed 10 > minutes ago :S > No problem. Sorry I took offense. This has been a

Re: Can't start X

Mike Smith wrote: > Oh, forgot to mention - the X server was crashing because of signal 11, > which according to kill -l is a segfault. (which is bad.) > I would say that is quite significant. Please post the contents of your XFree86.0.log (though it may be called something else by X.org). -Ro

Re: Can't start X

Mike Smith wrote: > -Etch > -haven't checked yet, I know I have an Intel 810 video card. > -with dpkg-reconfigure xserver-xorg > (I tried both the i810 and vesa drivers, with and without fb.) > OK. You still have not provided the output of lspci (that would be helpful). What about the contents o

Re: Can't start X

Oh, forgot to mention - the X server was crashing because of signal 11, which according to kill -l is a segfault. (which is bad.)On 3/17/06, Mike Smith <[EMAIL PROTECTED]> wrote: -Etch-haven't checked yet, I know I have an Intel 810 video card.-with dpkg-reconfigure xserver-xorg(I tried both the i

Re: Can't start X

-Etch-haven't checked yet, I know I have an Intel 810 video card.-with dpkg-reconfigure xserver-xorg(I tried both the i810 and vesa drivers, with and without fb.)Hmm, someone needs to get rid of that stupid bot. On 3/17/06, Roberto C. Sanchez <[EMAIL PROTECTED]> wrote: Mike Smith wrote:> I installe

Re: Can't start X

Mike Smith wrote: > I installed Debian and can't get X to start. It crashes with "***INVALID > MEM ALLOCATION***" errors (can't paste exact errors, I'm in Windows > now). Googling a bit shows that it's a pretty common problem, but nobody > seems to have a solution. Anyone know why this is and how t

Can't start X

I installed Debian and can't get X to start. It crashes with "***INVALID MEM ALLOCATION***" errors (can't paste exact errors, I'm in Windows now). Googling a bit shows that it's a pretty common problem, but nobody seems to have a solution. Anyone know why this is and how to fix it? Thanks.

Re: Problems after upgrade to udev - can't start X

Hello Richard L. Halpert (<[EMAIL PROTECTED]>) wrote: > I recently upgraded from sarge to etch, and I ran into a problem that > seems to be related to udev. During the upgrade, hotplug was removed > and udev was installed. Then you also read the message that told you to purge the hotplug packa

Problems after upgrade to udev - can't start X

Hi all, I recently upgraded from sarge to etch, and I ran into a problem that seems to be related to udev.  During the upgrade, hotplug was removed and udev was installed.  Afterwards, I received the following error message when trying to log in (via gdm): Error creating the child process for this

Re: Can't start X in Sarge

On Saturday 21 May 2005 16:35, Amira Youssef wrote: > Hello, > > After I've installed Sarge thru net for the fist time. X didn't start so I > installed the XFREE86 V4 pkg I used to install over woody and configure it > same way but whenever it try to start x it give the following msg: apm: > BIOS n

Re: Can't start X in Sarge

Amira Youssef wrote: > Hello, > > After I've installed Sarge thru net for the fist time. X didn't start > so I installed the XFREE86 V4 pkg I used to install over woody and > configure it same way but whenever it try to start x it give the > following msg: apm: BIOS not found! > I've checked /va

Can't start X in Sarge

Hello,   After I've installed Sarge thru net for the fist time. X didn't start so I installed the XFREE86 V4 pkg I used to install over woody and configure it same way but whenever it try to start x it give the following msg: apm: BIOS not found! I've checked /var/log/XFREE86.log, at the end it say

Re: Can't start X apps from su

On Sun, Feb 09, 2003 at 11:31:20AM -0500, Fraser Campbell wrote: > I don't know the security implications of what I did so if you have a > multi-user system I'd suggest figuring that out first. A better alternative > may be to use gnome-sudo instead of su, like this: > > gnome-sudo gnome-ap

Re: Can't start X apps from su

Andrej Prsa wrote: > I have a very-difficult-to-reproduce-but-pertaining problem with > accessing X applications (such as nedit) when gaining access via > su from some other user's X session. If I log in as root to X, > such problem never occurs. But as I don't want to take the name > of root in v

Re: Can't start X apps from su

On Sun, Feb 09, 2003 at 01:53:10AM +0200, Johan Ehnberg wrote: > Yeah, I got annoyed because of this too. Anyway it's not a big problem. > What happens when you 'su' is that your env.vars. are changed to root's. > Thus, apps don't know where the user's X session is. What you can do is > use the

Re: Can't start X apps from su

Hello List, I have a very-difficult-to-reproduce-but-pertaining problem with accessing X applications (such as nedit) when gaining access via su from some other user's X session. If I log in as root to X, such problem never occurs. But as I don't want to take the name of root in vain, I got used

Re: Can't start X apps from su

Yeah, I got annoyed because of this too. Anyway it's not a big problem. What happens when you 'su' is that your env.vars. are changed to root's. Thus, apps don't know where the user's X session is. What you can do is use the -p flag for su. 'su -p' will preserve the user's env.vars. for the inv

Can't start X apps from su

Hello List, I have a very-difficult-to-reproduce-but-pertaining problem with accessing X applications (such as nedit) when gaining access via su from some other user's X session. If I log in as root to X, such problem never occurs. But as I don't want to take the name of root in vain, I got used t

Re: Can't start X with Nvidia

On Sun, Jan 19, 2003 at 11:18:59AM -0500, Dave W wrote: > On Sun, 2003-01-19 at 03:56, Ian D. Stewart wrote: > > NVDriver is the linux kernel module. nvidia is the X display driver. > > > I might be wrong (sure wouldn't be the first time) but I believe that > starting with 4191, the module is ca

Re: Can't start X with Nvidia [solved]

Op zo 19-01-2003, om 17:33 schreef Sridhar M.A.: > On Sun, Jan 19, 2003 at 03:56:18AM -0500, Ian D. Stewart wrote: >> On Sunday 19 January 2003 06:34, [EMAIL PROTECTED] wrote: >> > >> > My module is called nvidia and not NVdriver. I think the problem >> > is that you are loading a

Re: Can't start X with Nvidia [solved]

On Sun, Jan 19, 2003 at 03:56:18AM -0500, Ian D. Stewart wrote: > On Sunday 19 January 2003 06:34, [EMAIL PROTECTED] wrote: > > > > My module is called nvidia and not NVdriver. I think the problem > > is that you are loading a module called NVdriver and you have > > nvidia listed as

Re: Can't start X with Nvidia

On Sun, 2003-01-19 at 03:56, Ian D. Stewart wrote: > NVDriver is the linux kernel module. nvidia is the X display driver. > I might be wrong (sure wouldn't be the first time) but I believe that starting with 4191, the module is called nvidia. Prior to 4191 the module was called NVdriver. I ha

Re: Can't start X with Nvidia

* Sridhar M.A. ([EMAIL PROTECTED]) wrote: > I just got a new motherboard and cpu: asus a7n266-vm with amd xp 1800. I > currently having about 128MiB of DDRAM. In the bios I have set the agp > ram to 32MiB. The machine is currently running sarge. > > I have the same board, and ran into problems wit

Re: Can't start X with Nvidia

On Sunday 19 January 2003 06:34, [EMAIL PROTECTED] wrote: > > My module is called nvidia and not NVdriver. I think the problem is that > you are loading a module called NVdriver and you have nvidia listed as the > driver in the X config file. Maybe try changing the Driver in X to > NVdriver to s

Re: Can't start X with Nvidia

In linux.debian.user, you wrote: > > When I modprobe NVdriver, I get the following message: > > Warning: loading /lib/modules/2.4.20/kernel/drivers/video/NVdriver will > taint the kernel: non-GPL license - NVIDIA > See http://www.tux.org/lkml/#export-tainted for information about > ta

Re: Can't start X with Nvidia

On Sat, Jan 18, 2003 at 09:06:24PM +0530, Sridhar M.A. wrote: > When I modprobe NVdriver, I get the following message: > > Warning: loading /lib/modules/2.4.20/kernel/drivers/video/NVdriver will > taint the kernel: non-GPL license - NVIDIA > See http://www.tux.org/lkml/#export-tainted for

Re: Can't start X with Nvidia

On Sat, Jan 18, 2003 at 06:17:06PM +0200, Alaa The Great wrote: > > I never had a problem with my TNT but I'll make a guess. > do you have the nvidia devices in the /dev/ directory?? > on my system I get > $ ls /dev/nvidia* > nvidia0nvidia2nvidia4nvidia6nvidiactl

RE: Can't start X with Nvidia

Yea if you go to nvidias page and look under the install guide it tells you to take those out - Original Message - From: "Adam Kao" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, January 18, 2003 4:07 PM Subject: Re: Can&#

Re: Can't start X with Nvidia

I don't know if this is relevant, but when I installed X on my system I had to remove the "UseFBDev" option from the "Device" section. My system is much older and the video card is an old nVidia card that uses the "nv" driver but it's something to try and can't hurt. Adam -- To UNSUBSCRIBE, e

Re: Can't start X with Nvidia

On Sat, 18 Jan 2003 21:06:24 +0530 "Sridhar M.A." <[EMAIL PROTECTED]> wrote: > > Can someone help me to get X running on this machine? I never had a problem with my TNT but I'll make a guess. do you have the nvidia devices in the /dev/ directory?? on my system I get $ ls /dev/nvidia* nvidia0n

Can't start X with Nvidia

I just got a new motherboard and cpu: asus a7n266-vm with amd xp 1800. I currently having about 128MiB of DDRAM. In the bios I have set the agp ram to 32MiB. The machine is currently running sarge. As noted from the recent discussions on compiling nvidia modules, I followed the recommended procedu

Re: Can't start X based programs on a remote host

on Sun, Apr 07, 2002, Ralf Doppelstein ([EMAIL PROTECTED]) wrote: > Hi *, > > I have 2 woody based hosts with gnome/gdm, last update at last night. > I try to open i.e. xclock on the remote host and show on the local > host. X disables remote tcp connections by default in Debian. You can't do t

Can't start X based programs on a remote host

Hi *, I have 2 woody based hosts with gnome/gdm, last update at last night. I try to open i.e. xclock on the remote host and show on the local host. I always get the message Can't open display: :0. I do the following steps: A) localhost: xhost + ssh remotehost remotehost: export

Re: can't start x after woody upgrade {works now}

At 09:09 PM 3/10/02, Seneca Cunningham wrote: [EMAIL PROTECTED]:~$ dpkg -S startx xbase-clients: /usr/X11R6/man/man1/startx.1x.gz xbase-clients: /usr/X11R6/bin/startx [EMAIL PROTECTED]:~$ Installing that package fixed it. Thanks Seneca and Art.

Re: can't start x after woody upgrade

On Sun, Mar 10, 2002 at 08:45:19PM -0500, Chris Jenks wrote: > I know that this has been covered recently, or at least I think it has, but > I was not able to find it in the archives after 2 hours of reading > (probably just couldn't find the right thread). I went from 2.2r3 to 2.2r5 > to Woody,

Re: can't start x after woody upgrade

Chris Jenks <[EMAIL PROTECTED]> wrote: > I know that this has been covered recently, or at least I think it has, but > I was not able to find it in the archives after 2 hours of reading > (probably just couldn't find the right thread). I went from 2.2r3 to 2.2r5 > to Woody, and installed Xfree86 4.

can't start x after woody upgrade

I know that this has been covered recently, or at least I think it has, but I was not able to find it in the archives after 2 hours of reading (probably just couldn't find the right thread). I went from 2.2r3 to 2.2r5 to Woody, and installed Xfree86 4.1.0-14 after going to Woody (no x before th

Re: URGENT: sid update - now can't start X

On 18 Dec 2001, Shri Shrikumar wrote: > Hi, > > you might have to download and install nvidia_glx and nvidia_kernel > packages if you haven't done so already and change your driver from nv > to nvidia - I was stuck at that for a day or so. The reason that I updated my sid to the current sid in t

Re: URGENT: sid update - now can't start X

Hi, you might have to download and install nvidia_glx and nvidia_kernel packages if you haven't done so already and change your driver from nv to nvidia - I was stuck at that for a day or so. good luck, Shri -- --- Shri Shrikumar I.T. Consultant U R Byte Solutions

Re: URGENT: sid update - now can't start X

> Error loading keymap /var/tmp/server-0.xkm > Couldn't load XKB keymap, falling back to pre-XKB keymap > Could not init font path element ...speedo... removing from list! > Waiting for X server to shut down Those errors shouldn't stop x. You might want to look elsewhere (xfree logs, gnome logs,

URGENT: sid update - now can't start X

I've been running sid for some time now, but only update occasionally. I updated my laptop last week without problems and today did my desktop. Now I can't start gnome, or even run "startx". The last few lines that I get are: Error loading keymap /var/tmp/server-0.xkm Couldn't load XKB keymap, f

Re: help! can't start X anymore

* Andrew Kae <[EMAIL PROTECTED]> (2001-07-09 04:50): >Hi, > >I'm kinda digging up this thread from april becuause i'm having the >same problem and there didn't seem to be a definite answer to the >thread. > >I've been using xfree86-common 3.35 then decided to update to t

Re: help! can't start X anymore

Hi,   I'm kinda digging up this thread from april becuause i'm having the same problem and there didn't seem to be a definite answer to the thread.   I've been using xfree86-common 3.35 then decided to update to the testing-distribution and now i have xfree86-common 4.something   When I tried star

Re: help! can't start X anymore

I got X working !!! :) well just IceWM is working - but that's ok there are still some error messages from some programs - I don't know how to fix them! Warning: Color name "black" is not defined Warning: Color name "red3" is not defined Warning: Color name "green3" is not defined Warning: Color n

Re: help! can't start X anymore

ctually what happened. Take a look and > see. > > - > Marc Wilson > [EMAIL PROTECTED] > [EMAIL PROTECTED] > http://www.moonkingdom.net/mwilson > > -Original Message- > From: Philipp Bliedung [mailto:[EMAIL PROTECTED] > Sent: Monday, April 16, 2001 1:20 AM

(partly solved)Re: help! can't start X anymore

Thanks to everybody who replied, I got X working :) I just didn't upgrade all the XFree86 packages - that was kinda stupid, oh well... My desktop is 'working' now - but it's totally messed up! When it starts I get this message: "You are not running a GNOME Compilant Window Manager. GNOME support

  1   2   >