jodef Posted October 2, 2004 Share Posted October 2, 2004 On boot up I get an error no /dev/dsp device I run alsaconf which correctly identifies my card. However on trying to run alsamixer or any mixer for that matter I get the following error : alsamixer: function snd_ctl_open failed for default: No such file or directory # --- BEGIN: Generated by ALSACONF, do not edit. ---# --- ALSACONF verion 1.0.5 ---alias snd-card-0 snd-intel8x0alias sound-slot-0 snd-intel8x0# --- END: Generated by ALSACONF, do not edit. --- root@darkstar:/home/johann# lsmodModule Size Used byppp_deflate 4576 0zlib_deflate 21560 1 ppp_deflatezlib_inflate 20864 1 ppp_deflatebsd_comp 5280 0ppp_async 9440 1snd_pcm_oss 47560 0snd_mixer_oss 16032 1 snd_pcm_ossnls_iso8859_1 3648 1vfat 11200 1fat 38624 1 vfatsg 28736 0sd_mod 15520 0ide_scsi 13156 0pcnet32 23396 0mii 3744 1 pcnet32crc32 3776 1 pcnet32snd_ymfpci 54756 0snd_ac97_codec 61316 1 snd_ymfpcisnd_pcm 81160 2 snd_pcm_oss,snd_ymfpcisnd_opl3_lib 8064 1 snd_ymfpcisnd_timer 20228 3 snd_ymfpci,snd_pcm,snd_opl3_libsnd_hwdep 6692 1 snd_opl3_libsnd_page_alloc 8712 2 snd_ymfpci,snd_pcmgameport 3488 1 snd_ymfpcisnd_mpu401_uart 5728 1 snd_ymfpcisnd_rawmidi 19204 1 snd_mpu401_uartsnd 45412 10 snd_pcm_oss,snd_mixer_oss,snd_ymfpci,snd_ac97_codec,snd_pcm,snd_opl3_lib,snd_timer,snd_hwdep,snd_mpu401_uart,snd_rawmidisoundcore 6944 1 sndusb_storage 60032 0usbcore 95136 1 usb_storageagpgart 26728 0 How do I begin to solve this problem? Quote Link to comment Share on other sites More sharing options...
Bruno Posted October 2, 2004 Share Posted October 2, 2004 Hi JohannCould you check if "aumix" is installed ? . . . also check: # ls -al /dev/dsp# ls -al /dev/sound And the files that link to those two. Bruno Quote Link to comment Share on other sites More sharing options...
jodef Posted October 2, 2004 Author Share Posted October 2, 2004 Aumix is installed but here's the range of errors : root@darkstar:/home/johann# alsamixeralsamixer: function snd_ctl_open failed for default: No such file or directoryroot@darkstar:/home/johann# aumixaumix: error while loading shared libraries: libatk-1.0.so.0: cannot open shared object file: No such file or directoryroot@darkstar:/home/johann# ls -al /dev/dspls: /dev/dsp: No such file or directoryroot@darkstar:/home/johann# ls -al /dev/soundls: /dev/sound: No such file or directory Quote Link to comment Share on other sites More sharing options...
Bruno Posted October 2, 2004 Share Posted October 2, 2004 Hi JohannCould you try to start the alsamixer with: "alsamixer -c 1" . . . ( is for the second card, for if the onboard one is not disabled properly )Also, another intel8x0 problem with alsaconf, have a look here ( you did run alsaconf ? ):http://www.linuxforum.com/forums/index.php?showtopic=104639 Bruno Quote Link to comment Share on other sites More sharing options...
jodef Posted October 2, 2004 Author Share Posted October 2, 2004 Bruno I apologise I ran off to reinstall minislack since on the previous occassion I did a custom install. I never learn. Moral : When installing Slack and Slack based distros always always do a full install. Custom installs always lead to problems.Some other stuff to sort out though :1. I have a Lite-On Cdrom and Lite-On CDRW I need help setting them up correctly johann@darkstar:~$ ls -l /dev/hdcbrw-rw-rw- 1 root cdrom 22, 0 2004-10-02 04:02 /dev/hdcjohann@darkstar:~$ ls -l /dev/cdromlrwxrwxrwx 1 root root 3 2004-10-02 04:02 /dev/cdrom -> hdd /dev/cdrom actually points to the CDWriter not the CDRom I want to correctly set up the devices so /dev/cdrom points to /dev/hdc the CDRom drive then I need to setup the CDRW links correctly.2.The install of Slack and Minislack don't detect the nvidia card instead the Vesa drivers are installed. Quote Link to comment Share on other sites More sharing options...
Peachy Posted October 2, 2004 Share Posted October 2, 2004 Bruno I apologise I ran off to reinstall minislack since on the previous occassion I did a custom install. I never learn. Moral : When installing Slack and Slack based distros always always do a full install. Custom installs always lead to problems.Some other stuff to sort out though :1. I have a Lite-On Cdrom and Lite-On CDRW I need help setting them up correctly johann@darkstar:~$ ls -l /dev/hdcbrw-rw-rw- 1 root cdrom 22, 0 2004-10-02 04:02 /dev/hdcjohann@darkstar:~$ ls -l /dev/cdromlrwxrwxrwx 1 root root 3 2004-10-02 04:02 /dev/cdrom -> hdd /dev/cdrom actually points to the CDWriter not the CDRom I want to correctly set up the devices so /dev/cdrom points to /dev/hdc the CDRom drive then I need to setup the CDRW links correctly.2.The install of Slack and Minislack don't detect the nvidia card instead the Vesa drivers are installed. Johann,You may need to install the ide-cdrom module in order to get both CD-ROMs detected properly. Perhaps run modprobe -dep and see if it installs. Or try loading the driver itself with insmod ide-cdrom . Since you have a CD-RW you will need to make sure ide-scsi is also installed. Quote Link to comment Share on other sites More sharing options...
Bruno Posted October 2, 2004 Share Posted October 2, 2004 Hi JohanThis is the NOTE that Slackware posts for the scsi CD-RW's: You can also pass the hdc=ide-scsi option on a bootdisk command line ( include in the appendline of lilo ). Once you do this, your CD-RW device will appear as a SCSI device (/dev/scd0) rather than an IDE device (/dev/hdc). If this is the only CD-ROM type device in the machine (there's no DVD drive, for instance), then you'll probably also want to change your /dev/cdrom symbolic link to point to the new SCSI device instead of the old IDE device: cd /dev rm cdrom ln -sf scd0 cdromAfter that if you want hdc to point to /dev/cdrom you need to adapt your fstab ( was hdd your writer ? ) Bruno Quote Link to comment Share on other sites More sharing options...
jodef Posted October 2, 2004 Author Share Posted October 2, 2004 Again late response I had to take an afternoon nap must be getting old. Minslack uses the 2.6 kernel Bruno and Peachy so no need to pass the ide-scsi option.Just need to get the links pointing to the right devices.hdc -> cdrom and hdd -> cdwriter. Is it only the fstab I need to modify? Quote Link to comment Share on other sites More sharing options...
Bruno Posted October 2, 2004 Share Posted October 2, 2004 The 2.6 kernel ?? . . that is good !Yep only change the fstab . . ( and see to it that the correct directories are in /mnt )After that "mount -a" should do but a reboot is betterB) Bruno Quote Link to comment Share on other sites More sharing options...
jodef Posted October 2, 2004 Author Share Posted October 2, 2004 Ok Bruno a little more help req'd fstab currently looks like this: dev/hda5 swap swap defaults 0 0/dev/hda9 / ext3 defaults 1 1/dev/hda10 /home ext3 defaults 1 2/dev/hda8 /mnt/data vfat auto,uid=johann 1 0/dev/cdrom /mnt/cdrom iso9660 noauto,owner,ro 0 0/dev/fd0 /mnt/floppy auto noauto,owner 0 0devpts /dev/pts devpts gid=5,mode=620 0 0proc /proc proc defaults 0 0 Only one device in there what am I changing exactly? Quote Link to comment Share on other sites More sharing options...
Bruno Posted October 2, 2004 Share Posted October 2, 2004 (edited) Well according to your info a few posts back, /dev/cdrom is a link to /dev/hdd so: # mkdir /mnt/cdwriter And these 2 lines in fstab: /dev/cdrom    /mnt/cdwriter    iso9660   noauto,owner,ro  0  0/dev/hdc    /mnt/cdrom    iso9660   noauto,owner,ro  0  0 ( First line can be /dev/hdd too ) Bruno Edited October 2, 2004 by Bruno Quote Link to comment Share on other sites More sharing options...
jodef Posted October 2, 2004 Author Share Posted October 2, 2004 Bruno worked perfectly Now can I trouble you for one more piece of advice : Section "Monitor" Identifier "My Monitor"# HorizSync is in kHz unless units are specified.# HorizSync may be a comma separated list of discrete values, or a# comma separated list of ranges of values.# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S# USER MANUAL FOR THE CORRECT NUMBERS. HorizSync 31.5 - 50.0# HorizSync 30-64 # multisync# HorizSync 31.5, 35.2 # multiple fixed sync frequencies# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies# VertRefresh is in Hz unless units are specified.# VertRefresh may be a comma separated list of discrete values, or a# comma separated list of ranges of values.# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S# USER MANUAL FOR THE CORRECT NUMBERS. VertRefresh 40-90EndSection # Graphics device section# **********************************************************************# Any number of graphics device sections may be presentSection "Device" Identifier "VESA Framebuffer" Driver "vesa" #VideoRam 4096 # Insert Clocks lines here if appropriateEndSection Minislack and Slackware both use the VESA driver instead of the NVIDIA driver. How do I correct this? Quote Link to comment Share on other sites More sharing options...
Bruno Posted October 2, 2004 Share Posted October 2, 2004 Hi Johann,Now, first: Have you got the NVidia drivers installed ??If you have . . . . . here is my /etc/X11/xorg.conf file: ( Slackware ) copy over the relevant sections:Before you start: MAKE A BACKUP OF YOUR CURRENT FILE !!!! . . so you can put it back on the commandline if this fails. # File generated by xf86config.## Copyright © 1999 by The XFree86 Project, Inc.## Permission is hereby granted, free of charge, to any person obtaining a# copy of this software and associated documentation files (the "Software"),# to deal in the Software without restriction, including without limitation# the rights to use, copy, modify, merge, publish, distribute, sublicense,# and/or sell copies of the Software, and to permit persons to whom the# Software is furnished to do so, subject to the following conditions:# # The above copyright notice and this permission notice shall be included in# all copies or substantial portions of the Software.# # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE# SOFTWARE.# # Except as contained in this notice, the name of the XFree86 Project shall# not be used in advertising or otherwise to promote the sale, use or other# dealings in this Software without prior written authorization from the# XFree86 Project.## **********************************************************************# Refer to the XF86Config(4/5) man page for details about the format of # this file.# **********************************************************************# NOTE: This is a NEW IMPROVED version of XF86Config-fbdev that uses the vesa# driver instead of the fbdev driver. Thanks to Kenneth Fanyo who pointed# this out to me. # This XF86Config file is designed for use with the VESA framebuffer.# This generic interface should work with nearly all video cards# (although not every card will support every resolution).# With the new driver, it should no longer be required to have frame buffer# support in the kernel, or to run it on the console.## Enjoy! # -- volkerdi@slackware.com## **********************************************************************# Module section -- this section is used to specify# which dynamically loadable modules to load.# **********************************************************************#Section "Module"# This loads the DBE extension module. Load "dbe" # Double buffer extension# This loads the miscellaneous extensions module, and disables# initialisation of the XFree86-DGA extension within that module. SubSection "extmod" Option "omit xfree86-dga" # don't initialise the DGA extension EndSubSection# This loads the font modules Load "type1" Load "freetype"# Load "speedo"# This loads the GLX module Load "glx" <===================EndSection# **********************************************************************# Files section. This allows default font and rgb paths to be set# **********************************************************************Section "Files"# The location of the RGB database. Note, this is the name of the# file minus the extension (like ".txt" or ".db"). There is normally# no need to change the default. RgbPath "/usr/X11R6/lib/X11/rgb"# Multiple FontPath entries are allowed (which are concatenated together),# as well as specifying multiple comma-separated entries in one FontPath# command (or a combination of both methods)# # If you don't have a floating point coprocessor and emacs, Mosaic or other# programs take long to start up, try moving the Type1 and Speedo directory# to the end of this list (or comment them out).# FontPath "/usr/X11R6/lib/X11/fonts/local/" FontPath "/usr/X11R6/lib/X11/fonts/misc/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/CID/" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/"# ModulePath can be used to set a search path for the X server modules.# The default path is shown here.# ModulePath "/usr/X11R6/lib/modules"EndSection# **********************************************************************# Server flags section.# **********************************************************************Section "ServerFlags"# Uncomment this to cause a core dump at the spot where a signal is# received. This may leave the console in an unusable state, but may# provide a better stack trace in the core dump to aid in debugging# Option "NoTrapSignals"# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence# (where n is 1 through 12). This allows clients to receive these key# events.# Option "DontVTSwitch"# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence# This allows clients to receive this key event.# Option "DontZap"# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching# sequences. This allows clients to receive these key events.# Option "DontZoom"# Uncomment this to disable tuning with the xvidtune client. With# it the client can still run and fetch card and monitor attributes,# but it will not be allowed to change them. If it tries it will# receive a protocol error.# Option "DisableVidModeExtension"# Uncomment this to enable the use of a non-local xvidtune client.# Option "AllowNonLocalXvidtune"# Uncomment this to disable dynamically modifying the input device# (mouse and keyboard) settings.# Option "DisableModInDev"# Uncomment this to enable the use of a non-local client to# change the keyboard or mouse settings (currently only xset).# Option "AllowNonLocalModInDev"# Set the basic blanking screen saver timeout.# Option "blank time" "10" # 10 minutes# Set the DPMS timeouts. These are set here because they are global# rather than screen-specific. These settings alone don't enable DPMS.# It is enabled per-screen (or per-monitor), and even then only when# the driver supports it.# Option "standby time" "20"# Option "suspend time" "30"# Option "off time" "60"# On some platform the server needs to estimate the sizes of PCI# memory and pio ranges. This is done by assuming that PCI ranges# don't overlap. Some broken BIOSes tend to set ranges of inactive# devices wrong. Here one can adjust how aggressive the assumptions# should be. Default is 0.# Option "EstimateSizesAggresively" "0"EndSection# **********************************************************************# Input devices# **********************************************************************# **********************************************************************# Core keyboard's InputDevice section# **********************************************************************Section "InputDevice" Identifier "Keyboard1" Driver "kbd"# For most OSs the protocol can be omitted (it defaults to "Standard").# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),# uncomment the following line.# Option "Protocol" "Xqueue"# Set the keyboard auto repeat parameters. Not all platforms implement# this.# Option "AutoRepeat" "500 5"# Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)).# Option "Xleds" "1 2 3"# To disable the XKEYBOARD extension, uncomment XkbDisable.# Option "XkbDisable"# To customise the XKB settings to suit your keyboard, modify the# lines below (which are the defaults). For example, for a European# keyboard, you will probably want to use one of:## Option "XkbModel" "pc102"# Option "XkbModel" "pc105"## If you have a Microsoft Natural keyboard, you can use:## Option "XkbModel" "microsoft"## If you have a US "windows" keyboard you will want:## Option "XkbModel" "pc104"## Then to change the language, change the Layout setting.# For example, a german layout can be obtained with:## Option "XkbLayout" "de"## or:## Option "XkbLayout" "de"# Option "XkbVariant" "nodeadkeys"## If you'd like to switch the positions of your capslock and# control keys, use:## Option "XkbOptions" "ctrl:swapcaps"# These are the default XKB settings for X.Org## Option "XkbRules" "xorg"# Option "XkbModel" "pc101"# Option "XkbLayout" "us"# Option "XkbVariant" ""# Option "XkbOptions" ""EndSection# **********************************************************************# Core Pointer's InputDevice section# **********************************************************************Section "InputDevice"# Identifier and driver Identifier "Mouse1" Driver "mouse"# On platforms where PnP mouse detection is supported the following# protocol setting can be used when using a newer PnP mouse:# Option "Protocol" "Auto"# The available mouse protocols types that you can set below are:# Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2# Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2# MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse# ThinkingMouse ThinkingMousePS/2 Xqueue Option "Protocol" "IMPS/2"# The mouse device. The device is normally set to /dev/mouse,# which is usually a symbolic link to the real device.# Option "Device" "/dev/mouse" Option "Device" "/dev/psaux"# Option "Device" "/dev/ttyS0"# Option "Device" "/dev/ttyS1" Option "Resolution" "300" Option "ZAxisMapping" "4 5" Option "Buttons" "3" # When using XQUEUE, comment out the above two lines, and uncomment# the following line.# Option "Protocol" "Xqueue"# Baudrate and SampleRate are only for some Logitech mice. In# almost every case these lines should be omitted.# Option "BaudRate" "9600"# Option "SampleRate" "150"# Emulate3Buttons is an option for 2-button Microsoft mice# Emulate3Timeout is the timeout in milliseconds (default is 50ms)# Option "Emulate3Buttons"# Option "Emulate3Timeout" "50"# ChordMiddle is an option for some 3-button Logitech mice# Option "ChordMiddle"EndSection# Some examples of extended input devices# Section "InputDevice"# Identifier "spaceball"# Driver "magellan"# Option "Device" "/dev/cua0"# EndSection## Section "InputDevice"# Identifier "spaceball2"# Driver "spaceorb"# Option "Device" "/dev/cua0"# EndSection## Section "InputDevice"# Identifier "touchscreen0"# Driver "microtouch"# Option "Device" "/dev/ttyS0"# Option "MinX" "1412"# Option "MaxX" "15184"# Option "MinY" "15372"# Option "MaxY" "1230"# Option "ScreenNumber" "0"# Option "ReportingMode" "Scaled"# Option "ButtonNumber" "1"# Option "SendCoreEvents"# EndSection## Section "InputDevice"# Identifier "touchscreen1"# Driver "elo2300"# Option "Device" "/dev/ttyS0"# Option "MinX" "231"# Option "MaxX" "3868"# Option "MinY" "3858"# Option "MaxY" "272"# Option "ScreenNumber" "0"# Option "ReportingMode" "Scaled"# Option "ButtonThreshold" "17"# Option "ButtonNumber" "1"# Option "SendCoreEvents"# EndSection# **********************************************************************# Monitor section# **********************************************************************# Any number of monitor sections may be presentSection "Monitor" Identifier "My Monitor" <============== See remark below # HorizSync is in kHz unless units are specified.# HorizSync may be a comma separated list of discrete values, or a# comma separated list of ranges of values.# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S# USER MANUAL FOR THE CORRECT NUMBERS. HorizSync 31.5 - 50.0# HorizSync 30-64 # multisync# HorizSync 31.5, 35.2 # multiple fixed sync frequencies# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies# VertRefresh is in Hz unless units are specified.# VertRefresh may be a comma separated list of discrete values, or a# comma separated list of ranges of values.# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S# USER MANUAL FOR THE CORRECT NUMBERS. VertRefresh 40-90EndSection# **********************************************************************# Graphics device section# **********************************************************************# Any number of graphics device sections may be presentSection "Device" Identifier "device1" <============== See remark below VendorName "nVidia Corporation" <=================== BoardName "NVIDIA GeForce2 DDR (generic)" <=================== Driver "nvidia" <=================== Option "DPMS" <=================== Option "IgnoreEDID" "1" <=================== #VideoRam 4096 # Insert Clocks lines here if appropriateEndSection# **********************************************************************# Screen sections# **********************************************************************# Any number of screen sections may be present. Each describes# the configuration of a single screen. A single specific screen section# may be specified from the X server command line with the "-screen"# option.Section "Screen" Identifier "Screen 1" Device "device1" <=========== Has to match Divice above Monitor "My Monitor" <========= Has to match Monitor above # If your card can handle it, a higher default color depth (like 24 or 32)# is highly recommended.# DefaultDepth 8# DefaultDepth 16 DefaultDepth 24# DefaultDepth 32# "1024x768" is also a conservative usable default resolution. If you# have a better monitor, feel free to try resolutions such as# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your# card/monitor can produce) Subsection "Display" Depth 8 Modes "1024x768" "800x600" "640x480" EndSubsection Subsection "Display" Depth 16 Modes "1024x768" "800x600" "640x480" EndSubsection Subsection "Display" Depth 24 Modes "1024x768" "800x600" "640x480" EndSubsection Subsection "Display" Depth 32 Modes "1024x768" "800x600" "640x480" EndSubsectionEndSection# **********************************************************************# ServerLayout sections.# **********************************************************************# Any number of ServerLayout sections may be present. Each describes# the way multiple screens are organised. A specific ServerLayout# section may be specified from the X server command line with the# "-layout" option. In the absence of this, the first section is used.# When now ServerLayout section is present, the first Screen section# is used alone.Section "ServerLayout"# The Identifier line must be present Identifier "Simple Layout"# Each Screen line specifies a Screen section name, and optionally# the relative position of other screens. The four names after# primary screen name are the screens to the top, bottom, left and right# of the primary screen. In this example, screen 2 is located to the# right of screen 1. Screen "Screen 1"# Each InputDevice line specifies an InputDevice section name and# optionally some options to specify the way the device is to be# used. Those options include "CorePointer", "CoreKeyboard" and# "SendCoreEvents". InputDevice "Mouse1" "CorePointer" InputDevice "Keyboard1" "CoreKeyboard"EndSection Bruno Quote Link to comment Share on other sites More sharing options...
Bruno Posted October 2, 2004 Share Posted October 2, 2004 PART 2Johann . . an additional note: I do not know if you play \music CDs on your computer . . .but KsCD will still point to /dev/cdrom . . . you will have to change that to the /dev you are using for the CD-Rom ;) Bruno Quote Link to comment Share on other sites More sharing options...
jodef Posted October 2, 2004 Author Share Posted October 2, 2004 PART 2Johann . . an additional note: I do not know if you play \music CDs on your computer . . .but KsCD will still point to /dev/cdrom . . . you will have to change that to the /dev you are using for the CD-Rom BrunoWay ahead of you on this one everything there OK Now on to the nvidia install. When you installed NVIDIA drivers did you get a message about kernel being compiled with fbdev and could cause problems with NVIDIA driver? Quote Link to comment Share on other sites More sharing options...
Bruno Posted October 2, 2004 Share Posted October 2, 2004 Yep . . the RIVA FB . . . no worries . . just ignore it !( Just don't let the installer download the kernel from Nvidia . . you have the correct one in /usr/src and it will find it ) BrunoPS: What 2.6 kernel ???? There are problems with 2.6.8 !!! . . the solution is here on the forum . . http://forums.scotsnewsletter.com/index.ph...ndpost&p=106744 Quote Link to comment Share on other sites More sharing options...
jodef Posted October 2, 2004 Author Share Posted October 2, 2004 Minislack uses 2.6.7-1 kernel only thing no kernel sources on CD will I have to download the sources? Quote Link to comment Share on other sites More sharing options...
Bruno Posted October 2, 2004 Share Posted October 2, 2004 In that case see if Nvidia has the sources and let the installer download it from their site . . . if they do not have it you will have to find it at MiniSlack's site . . Bruno Quote Link to comment Share on other sites More sharing options...
minislack Posted October 8, 2004 Share Posted October 8, 2004 Hi, For your information, I had some problems with Intel snd-intel8x0 driver , loaded as secondary mixer device (/dev/dsp1) in Minislack0.2To prevent this : rename or delete the snd-intel8x0m.ko module (modem) from /lib/modules/2.6.7-1/kernel/sound/pci/Then alsa will load snd-intel8x0 's mixer as /dev/dsp , and alsamixer will work without -c option.Note : this is really a problem only in KDERegardsJP Quote Link to comment Share on other sites More sharing options...
teacher Posted October 8, 2004 Share Posted October 8, 2004 JPThanks for the input. Would you by chance be the JP of the Mini-Slack team??? Welcome to our little forum. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.