I believe the problem comes from an incompatibility between FGLRX
version 12-4-1 and xorg 1.12.
I've had the same symptoms and solved it by downgrading xorg to
1.11.4-1. Make sure to downgrade the input packages too.
Thanks for the feedback. Will try out and feedback the result.
Hi Issa
On 06/11/2012 06:01 AM, Issam Mehssani wrote:
I believe the problem comes from an incompatibility between FGLRX
version 12-4-1 and xorg 1.12.
I've had the same symptoms and solved it by downgrading xorg to
1.11.4-1. Make sure to downgrade the input packages too.
Thanks for the feedback. Wil
Hi,
I believe the problem comes from an incompatibility between FGLRX version
12-4-1 and xorg 1.12.
I've had the same symptoms and solved it by downgrading xorg to 1.11.4-1.
Make sure to downgrade the input packages too.
Hi,
Is this bug (Bug#665000: SUMO2: blank screen after load "radeon" module)
related to my issue? As I am using Sumo chip too AMD Llano A6-3670 APU
with Radeon(tm) HD Graphics stepping 00
root@szechuan:~#: dmesg | grep -i sumo
[ 7.451590] [drm] initializing kernel modesetting (SUMO 0x1002:0x9
On Mon, May 21, 2012 at 09:27:32AM +0800, Hor Jiun Shyong wrote:
> >grep -v \^# /etc/inittab
[output same as mine]
Can't see anything different there.
--
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the
oppr
grep -v \^# /etc/inittab
id:2:initdefault:
si::sysinit:/etc/init.d/rcS
~~:S:wait:/sbin/sulogin
l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6
z6:6:res
On Mon, May 21, 2012 at 01:34:59AM +1200, Chris Bannister wrote:
> On Thu, May 17, 2012 at 11:37:54AM +0800, Hor Jiun Shyong wrote:
> > I checked and noticed the default runlevel under inittab is 5. (I
> > must have changed it for reason I can't remember now).I have
> > changed it back to run
On Thu, May 17, 2012 at 11:37:54AM +0800, Hor Jiun Shyong wrote:
> I checked and noticed the default runlevel under inittab is 5. (I
> must have changed it for reason I can't remember now).I have
> changed it back to run level 2 and will try the ati driver again to
> see if the problem still p
On Thu, 17 May 2012 12:14:01 +0800, Hor wrote in message
<4fb47b09.9080...@gmail.com>:
> Is amd-driver-installer-12-4-x86.x86_64.run driver the same with the
> non free debianised fglrx driver ?
> amd-driver-installer-12-4-x86.x86_64.run uses fglrx version 8.961
..I dunno, I only use the fre
Is amd-driver-installer-12-4-x86.x86_64.run driver the same with the
non free debianised fglrx driver ?
amd-driver-installer-12-4-x86.x86_64.run uses fglrx version 8.961
lspci result under amd-driver-installer-12-4-x86.x86_64.run driver:
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VG
On 05/16/2012 01:23 AM, Indulekha wrote:
Maybe something (like /etc/inittab) got edited, and tty7
was repurposed for a getty? It's important to leave tty7
alone or X won't run.
Also if inittab did get edited, could be you're calling a getty
that isn't installed...
I checked and noticed the
Hi,
..this isn't a kernel panic?
What happens _immediately_before_ your blinking dash?
Kernel is able to boot up.
..this is relevant only if it was written between your boot and your
blinking dash.
Yes it is so.
..your Xorg log is "gnome 3 under fallback mode"?
Yes
..first
On Tue, 15 May 2012 21:03:12 +0800, Hor wrote in message
<4fb25410.5050...@gmail.com>:
> Hi All,
>
> Would be grateful if anyone could provide feedback on the below,
> thanks.
>
> After installing proprietary driver
> amd-driver-installer-12-4-x86.x86_64.run on Sid amd64, both console
> and X
On Tue, May 15, 2012 at 12:01:58PM -0500, Indulekha wrote:
> On Tue, May 15, 2012 at 04:55:15PM +, Camaleón wrote:
> > On Tue, 15 May 2012 21:03:12 +0800, Hor Jiun Shyong wrote:
> >
> > > Hi All,
> >
> > Hi... but there's no need to send this twice and please, no html posts :-)
> >
> > > Wou
On Tue, May 15, 2012 at 04:55:15PM +, Camaleón wrote:
> On Tue, 15 May 2012 21:03:12 +0800, Hor Jiun Shyong wrote:
>
> > Hi All,
>
> Hi... but there's no need to send this twice and please, no html posts :-)
>
> > Would be grateful if anyone could provide feedback on the below, thanks.
>
>
On Tue, 15 May 2012 21:03:12 +0800, Hor Jiun Shyong wrote:
> Hi All,
Hi... but there's no need to send this twice and please, no html posts :-)
> Would be grateful if anyone could provide feedback on the below, thanks.
Okay, let's see if I can give you some hints. There are usually X gurus
aro
Hello
Scott Barlow (<[EMAIL PROTECTED]>) wrote:
> I am a reasonable newbie to Debian and have been trying unsucceffully
> to get X (specifically kde) working on my box. I have modified the
> XF86Config-4 file through the dpkg-reconfigure xserver-xfree86 command
> but am having no luck.
> [...]
On Wed, 06 Oct 2004 16:01:06 +1000, Scott Barlow
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> I am a reasonable newbie to Debian and have been trying unsucceffully to get
> X
> (specifically kde) working on my box. I have modified the XF86Config-4 file
> through the dpkg-reconfigure xserver-xfree86 comman
Hello
Gruessle (<[EMAIL PROTECTED]>) wrote:
> I get this
>
> Fatal server error:
> no screens found
>
> Trying to start startx
If you want to ask a question on the list, please write a new mail from
scratch instead of answering to an existing message.
If you want help, you must supply the nec
"Gruessle" <[EMAIL PROTECTED]> said on Sun, 14 Dec 2003 23:34:16 -0800:
>
>
> I get this
>
> Fatal server error:
> no screens found
>
> Trying to start startx
>
> Thank you
That's OK.
Um, thank me for what exactly?
Oh, BTW - you might want to investigate the "New message" function of
you
Nermind, problem solved.
Thank you for your help,
(==timothy==)
=
I copied the file to the /etc/X11/
directory, renamed it, and made gdm my
default display manager by running:
dpkg-reconfigure gdm
Now, X starts via gdm. I had xdm as
the default dm but it kep
I copied the file to the /etc/X11/
directory, renamed it, and made gdm my
default display manager by running:
dpkg-reconfigure gdm
Now, X starts via gdm. I had xdm as
the default dm but it kept booting kde.
Small problem: X is running at 640x480,
I can't CNTRL+ALT+[+], and the
/etc/X11/XF86Confi
On Mon, Mar 11, 2002 at 01:23:31PM -0500, timothy bauscher wrote:
>x-window-system and gnome-session are installed. xdm is the default display
>manager. I am using the nv driver for my RIVA TNT2, and have just completed a
>fresh install of unstable.
>
>When xdm (or gdm) are launched, they display
On Mon, Mar 11, 2002 at 01:23:31PM -0500, timothy bauscher wrote:
>
> I have run xf86config and xf86cfg with different resolutions and color
> depths, but I still end up with the same error.
>
> Any help would be appreciated, I have run out of ideas.
>
Make sure you have xserver-xfree86 insta
High,
On Wed, 9 Jan 2002, Sebastian Canagaratna wrote:
> Hi:
>
> I am having a fatal server error with XFree86 4.1.0 with my
> Number Nine Imagine I128 Card.
>
> Section "Device"
> ### Available Driver options are:-
> ### Values: : integer, : float, : "True"/"False",
> #
on Sun, May 13, 2001 at 05:34:32PM -0500, James Jackson ([EMAIL PROTECTED])
wrote:
> I recently purchased a copy of Debian linux and installed it on my computer.
> After installing I tryed "startX and ended up with this error:
> System: '/usr/X11R6/lib/X11/xkb/xkbcomp -w 1 -R/usr/X11R6/lib/X11/xk
Originally sent to debian-powerpc, trouble getting X up on iMac. Startx log and
XF86Config attached. Any ideas?
Thanks,
Joe
-- Original Message --
From: Michel Dänzer <[EMAIL PROTECTED]>
Date: Fri, 09 Feb 2001 11:13:19 +0100
>Joe Paxton wrote:
>>
>> Whe
-Original Message-
From: Bob Nielsen <[EMAIL PROTECTED]>
To: rod peters <[EMAIL PROTECTED]>
Cc: debian
Date: Saturday, January 30, 1999 2:10 PM
Subject: Re: fatal server error!
>X was split up into more packages, which don't get installed during an
>upgrade (th
X was split up into more packages, which don't get installed during an
upgrade (this is going to be fixed before the official release of slink.)
>From changelog.Debian.gz:
* the Great Reorganization -- changes too numerous to list here, but almost
every maintainer and build script was rewritt
On Mon, 16 Feb 1998, K.Y.Lo wrote:
: Hi
:
: I have a problem with X-windows setup.
:
: Fatal Server error:
: Cannot open mouse (I/O error)
:
: Help me!
:
: I have MS mouse (serial port). Should I use insmod to set mouse on?
Did you configure X correctly? And does the device for you
"K.Y.Lo" wrote:
>Hi
>
>I have installed Debian 1.3.1.r6 with X-windows package.
>
>install xbase,xlib6,xfntbase, xserver-svga into harddisc. done
>and set up xf86config. it went bummer.
>
>Fatal server error:
>No valid modes found.
>
>what does that mean? it is something miss
On Fri, 5 Sep 1997 [EMAIL PROTECTED] wrote:
> Karsten Bolding writes:
> >
> > Hi
> >
> > Just installed a new machine and updated my old one, so same versions on
> > both.
> >
> > When I try to start x (startx) as a normal user on the new machine I get:
> [snip]
> > Fatal server error:
> > xf
On Fri, 05 Sep 1997 08:36:27 EDT [EMAIL PROTECTED] wrote:
> Karsten Bolding writes:
> >
> > When I try to start x (startx) as a normal user on the new machine I get:
> [snip]
> > Fatal server error:
> > xf86OpenConsole: Server must be run as root
>
> Easily fixed. Go into /usr/X11R6/bin and ...
Karsten Bolding writes:
>
> Hi
>
> Just installed a new machine and updated my old one, so same versions on both.
>
> When I try to start x (startx) as a normal user on the new machine I get:
[snip]
> Fatal server error:
> xf86OpenConsole: Server must be run as root
>
>
> When reporting a pro
Check out /etc/X11/Xserver. The second line in this file will be either:
RootOnly, Console, or Anybody. This line defines who can start the server.
RootOnly is pretty self evident, Console allows anyone logged into the
console to start the server, while Anybody allows any attempt (even from
outside
> Fatal server error:
> xf86OpenConsole: Server must be run as root
[EMAIL PROTECTED](p2):bhmit1$ find /usr/X11R6 -perm +4000
/usr/X11R6/bin/xterm
/usr/X11R6/bin/X
/usr/X11R6/bin/rxvt-xpm
/usr/X11R6/bin/rxvt-debian
I'd check /usr/X11R6/bin/X first, but I'd be extremely surprised if
the maintainer
It sounds to me like you're using a window manager that has a sound module
but sound isn't in your kernel. Go through the *rc file for the window
manager and comment out the sound module portion. Then try again to see
if that is the only problem.
Look for something like this.
# Start the Audio
37 matches
Mail list logo
