 |  |  |  |  |  |  |  |
Debian Linux xserver configuration
 |
Hi there Ogre,
I've made some recent breakthrough....... I install the driver using "modconf" and now a get a new message "cpu over loaded" What is that suppose to mean - that my intel 1.7GHz cant handle it ?????? any idea where I am suppose to go from here
I've made some recent breakthrough....... I install the driver using "modconf" and now a get a new message "cpu over loaded" What is that suppose to mean - that my intel 1.7GHz cant handle it ?????? any idea where I am suppose to go from here
From what I was able to find, that error is the result of your CPU being overloaded with I/O requests from your soundcard. Try disabling full-duplex operation in the control panel (uncheck the box) and see if that fixes it.
If you spend more on coffee than on IT security, you will be hacked.
What's more, you deserve to be hacked.
-- former White House cybersecurity czar Richard Clarke
What's more, you deserve to be hacked.
-- former White House cybersecurity czar Richard Clarke
•
•
Join Date: Mar 2004
Posts: 209
Reputation: 
Solved Threads: 12
Posting Whiz in Training
•
•
•
•
Originally Posted by freeman2381
... and also how do I start in the command mode....I've tried changing the runlevel to all the runlevels possible but but keeps on booting in the graphical environment
There is a config file '/etc/inittab' that contains the default runlevel setting. A default inittab usually has enough comments to help you understand it. there is probably a line similar to:
id:4:initdefault:
To enable the default console-based multiuser mode, change the line to:
id:3:initdefault:
Just in case your inittab doesn't have the comments, here are the runlevels:
# 0 = halt
# 1 = single user mode
# 2 = unused (but configured the same as runlevel 3)
# 3 = multiuser mode (default Slackware runlevel)
# 4 = X11 with KDM/GDM/XDM (session managers)
# 5 = unused (but configured the same as runlevel 3)
# 6 = reboot
For the sake of everyone involved, be VERY careful when editing this file!
Every distro is a bit different, but the problem with doing a chmod -x on gdm, is that somewhere in your rc scripts it may rollover to xdm, or kdm if gdm is not found/executable.
PARANOIA:
A healthy understanding of the way the universe works.
A healthy understanding of the way the universe works.
•
•
•
•
Originally Posted by freeman2381
Thanks all of you ...... I did give a try but ahhhh no result...... I am switching back to Red Hat....Maybe I give another attempt some other time
|
Other Threads in the Window and Desktop Managers Forum
- Previous Thread: startkde command doesn't work.
- Next Thread: xserver debian on ppc
| Thread Tools | Search this Thread |
You need to join our community in order to build your list of favorite forums. You can visit the forum index for a listing of all forums.
Related Forum Features
Latest Window and Desktop Managers Posts
- Today's Posts
- Unanswered Threads
android apple busybox canonical cell computer cool dell desktop desktops developers distributions facebook fedora free fsf gadgets gfvs gio gnome gnu google gui incomprehensible ireland itunes jasonperlow karmic kde kernel2.6.25 kids koala laptop laptops linustorvalds linux livecds lxde mac madness mandriva mepis microsoft napster netbooks news opensuse operatingsystems os oswars pclinuxos phones program programmers programming qt shuttleworth software steveballmer super survey twitter ubuntu verizon vfs virtualization webbased windowmanagers windows xfce xui xwnidow youtube