| | |
Debian Linux xserver configuration
![]() |
I tried installing debian again and this time I've managed to configure my x server but now I am having problem with the sound when I start it gives the message could not initialize dsp... I have a AC97 on board soundcard and since it got detected automaticaly in RedHat I tried installing sndconfig but even that is'nt detecting my sound card. I tried searching for a driver but couldnt find one... 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
•
•
•
•
Originally Posted by TheOgre
Nice. We're supposed to be assisting people, not browbeating them because something they were trying didn't work.
Now, you decided not to be a quitter, good! It will be worth it in the long run........and with that said I'm going to rest.
*edit I approve your post for not quitting
cheers ,mate
•
•
•
•
Originally Posted by WEATHER CHANNEL
That always brings them back to try again.....it's a slap to the face.
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
freeman - try (as root) chmod 755 /dev/dsp
If you want to start Debian in commandline mode, remove gdm (Gnome Display Manager) or prevent it from starting up by removing it's +x attribute.
When you installed Debian, did it skip the part about detecting and (possibly) installing the sound module? If you don't remember, that's fine. Another thing to do is to examine the dmesg output and search for ac97:
Paste me the output (if any) from that so I can see what's going on at boottime.
If you want to start Debian in commandline mode, remove gdm (Gnome Display Manager) or prevent it from starting up by removing it's +x attribute.
When you installed Debian, did it skip the part about detecting and (possibly) installing the sound module? If you don't remember, that's fine. Another thing to do is to examine the dmesg output and search for ac97:
user@host$ dmesg > ~/dmesg_today.txt user@host$ cat ~/dmesg_today.txt | grep ac97
Paste me the output (if any) from that so I can see what's going on at boottime.
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
Look, I think your taking this personally now,(maybe because of my comments made on SyS admins,where I quoted you in another thread)
I don't know & quite frankly I could careless.
You can contact me via PM if you would like
I just fill this tension building within you......you know!
The last thing I want to start is a agrument,mate!
Cheers
I don't know & quite frankly I could careless.
You can contact me via PM if you would like

I just fill this tension building within you......you know!
The last thing I want to start is a agrument,mate!
Cheers
I'm not taking anything personally, and there's no tension building within me. I'm not starting an arguement, either. What I *am* doing is letting you know that the way you spoke to freeman2381 was uncalled for and unprofessional. That's 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
I did exactly as you said the chmod thing didnt work but I did hear a beep sound when I was tweeking around I was over joyed for a second but too bad it did'nt last long anyway I have the result of the dmesg below and thanks I learnt something new(dmesg)
Intel 810 + AC97 Audio, version 0.17, 11:53:11 Apr 20 2002 PCI: Increasing latency timer of device 00:fd to 64 i810: Intel ICH2 found at IO 0xe000 and 0xdc00, IRQ 12 ac97_codec: AC97 Audio codec, vendor id1: 0x414c, id2: 0x4710 (Unknown) i810_audio: Found 1 audio device(s)
Please keep this thread on track by helping freeman and others - I'm sure those with help would appreciate not having to sift through bickering to find an answer to their questions. Rants can be made in the Geek's Lounge or via PM. Thanks
![]() |
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 |
age android apple busybox canonical cell computer cool dell design desktop desktops developers distributions facebook fedora free fsf gadgets gfvs gio gnome gnu google gui hardware incomprehensible interface 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 operating-system operatingsystems os oswars pc pclinuxos phones program programmers programming qt shuttleworth software steveballmer super survey twitter ubuntu user verizon vfs virtualization webbased windowmanagers windows xfce xui xwnidow youtube






