X shouts

[Sharfuddin]

Hi to All
whenever I start X-server(startx), I receive following error messages if I press ctrl+Alt+F1 (i.e. on console tty1)

Following error messages are received when I used KDE


/lib/modules/2.4.18-14/kernel/drivers/video/sis/sisfb.o: init_module:NO such device

/lib/modules/2.4.18-14/kernel/drivers/video/sis/sisfb.o: insmod /lib/modules/2.4.18-14/kernel
/drivers/video/sis/sisfb.o failed

[drm]failed to load kernel module "sis"
(EE)SIS(0):[dri]DRIScreenInit failed Disabling DRI

DCOPServer up & running

>>running as realtime process now(priority 50)
Mutex Destroy failed: Device or resource bussy
mcop warning:user defined signal found for SIS_PIPE, overriding

QWidget::setMinimumSize: The smallest allowed size is (0,0)
QWidget::setMaximumSize: (unamed/PlainClock) NegativeSizes(53,-4)are not possible

QWidget::setMinimumSize: The smallest allowed size is (0,0)
QWidget::setMaximumSize: (unamed/PlainClock)


klipper is already running

QObject::connect:No such slot KWrited::block_in(const cha 8, int)
QObject::connect:(sendername:'unamed')
QObject::connect:(receivername:'unamed')

And when I logout from x-server(KDE session) following error receives:

QFont::setPixelSize:Pixel size < = 0(-1)


Error of failed request: 25(X_SendEvent)
Resource id in failed request:(0x1000005)
Serial number of failed request: 1720
Current serail number in output stream:1836

kde init: Fatal IO error: client killed
kde init: Sending SIGHUP to children

KLauncher: Exiting on signal 1

warning: leaving MCOP Dispatcher & still 74 types alive

waiting for X server to shutdown
[ ]#Kde init: sending SIGTERM to children
kdeinit: Exit


Following error messages are received when I used GNOME:


/lib/modules/2.4.18-14/kernel/drivers/video/sis/sisfb.o: init_module:NO such device

/lib/modules/2.4.18-14/kernel/drivers/video/sis/sisfb.o: insmod /lib/modules/2.4.18-14/kernel
/drivers/video/sis/sisfb.o failed

[drm]failed to load kernel module "sis"

(EE)SIS(0):[dri]DRIScreenInit failed Disabling DRI

SESSION_MANAGER=local/Linux101:/tmp/.ICE-unix/1289

Loaded background '0x8095e08

AUDIT:Fri Feb 27 17:28:13 2004: 1282 x:

client 5 rejected from local host


Now I issued a command(#xpdf filename) from Xterminal, to see what happens, I receive the following error message, although xpdf works quite fine

LTK Error: Cannot connect to X server:0

and when I logout from x-server(GNOME session)

(nautilus:1340): Gtk_CRITICAL ** : file
gtkwidget.c: line 2933(gtkwidget_event):assetion 'WIDGET_REALIZED_FOREVENT(widget,event)' failed
gtkwidget.c: line 2933(gtkwidget_event):assetion 'WIDGET_REALIZED_FOREVENT(widget,event)' failed
gtkwidget.c: line 2933(gtkwidget_event):assetion 'WIDGET_REALIZED_FOREVENT(widget,event)' failed
gtkwidget.c: line 2933(gtkwidget_event):assetion 'WIDGET_REALIZED_FOREVENT(widget,event)' failed

waiting for x server to shutdown The application 'gnome-panel' lost its connection to the
display :0:0;
most likely the X-server was shutdown or you killed/destroyed the application

Please let me know why I receves those errors and what should i do to get rid of these errors/warnings

Note:- Although I recevies those errors at console(via alt+ctrl+F1), I never feel any prolem running X.
Thanks in anticipation

Regards
Sharf

[Mark Grant · Accepted solution]

You can safely ignore most of these messages. It's basically just information taht helps debugging if you do have a problem. Some of the messages are things like, "failed to do something this way, I'll try it another way" and that way succeeds.

THe only one I find a bit odd is

/lib/modules/2.4.18-14/kernel/drivers/video/sis/sisfb.o

Looks like you have framebuffer access set up but with the wrong driver. Again this isn't really a problem.

When your machine boots, do you get a small penguin in the top left of your screen?

[Sharfuddin]

Hi Mark
Thanks for reply asap, I really appreciate u people, thnx again.
No I dont see any Penguin when machine boots

[Mark Grant]

I would guess then, that your boot manager (lilo or grub) is passing a "VESA" argument to the kernel making it try and use the framebuffer.

You could try and fix it but, to be honest, I don't think it's worth the bother.

Regards



Mark