soundblaster live
hi, im trying to configure a soundblaster live with kernel 2.2.10 in slink. i have a dual celeron and the kernel is compiled with smp i tried the driver emu10k1 but the only think i can get is: e3-0138:~# modprobe emu10k1 /lib/modules/2.2.10/misc/emu10k1.o: unresolved symbol remap_page_range /lib/modules/2.2.10/misc/emu10k1.o: unresolved symbol request_region /lib/modules/2.2.10/misc/emu10k1.o: unresolved symbol __wake_up /lib/modules/2.2.10/misc/emu10k1.o: unresolved symbol __generic_copy_from_user /lib/modules/2.2.10/misc/emu10k1.o: unresolved symbol unregister_sound_dsp /lib/modules/2.2.10/misc/emu10k1.o: unresolved symbol tq_immediate /lib/modules/2.2.10/misc/emu10k1.o: unresolved symbol bh_active /lib/modules/2.2.10/misc/emu10k1.o: unresolved symbol kmalloc /lib/modules/2.2.10/misc/emu10k1.o: unresolved symbol release_region /lib/modules/2.2.10/misc/emu10k1.o: unresolved symbol pci_read_config_byte /lib/modules/2.2.10/misc/emu10k1.o: unresolved symbol __get_free_pages /lib/modules/2.2.10/misc/emu10k1.o: unresolved symbol vfree /lib/modules/2.2.10/misc/emu10k1.o: unresolved symbol unregister_sound_midi /lib/modules/2.2.10/misc/emu10k1.o: unresolved symbol pcibios_present /lib/modules/2.2.10/misc/emu10k1.o: unresolved symbol free_irq what's wrong? Benoit Joly
Re: Install on Poweredge 2300
This may b e a bit late... but we had the same issues with later model poweredge servers Check out this link... they make custom Debian ISOs for use with PE servershttp://wiki.osuosl.org/display/LNX/Debian+on+Dell+Servers?focusedCommentId=2956Maybe that will help you.On May 26, 2005, at 3:37 AM, Ian Tobin wrote: Hi, when I try and install Debian on the poweredge 2300 i get the message that it can't find any hard disks. It has a mega raid scsi controller so I would assume I need a driver disk. Has anyone else managed to install Debian on a 2300? if so could you help? thanks in advance Ian __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
Gnome hangs at startup (gnome-session)
Hi everyone, I had installed a sarge snapshot that used to work fine, about 2 months ago. I upgraded my dist to etch as I would like to appreciate the new (if any) features, but now my gnome-session hangs when I try to login. Actually, active sessions also hang. I've searched some bug/lists archives and didn't found anything that seemed to be a common problem. Gnome is 2.8.3. Strangely, it only happens when I'm connected to the Internet via modem (ipv6 kernel module loaded, and also lt_modem and lt_serial for a Lucent 56K modem). Most of gnome applications (nautilus and gedit, for instance) actually become non-responsive, and take a very long time to load (10min). No matters which dialer I may use (wvdial or pon). Any system misconfiguration? That problem used to happen the first time I installed sarge, but vanished when I first upgraded it. Sorry if I've provided too few information. It's the first time I post here. As I don't know the versions of each gnome dependant package, I should say my system has been update yesterday (19 Jun), and so all packages of interest must be considered the last version. Thanks in advance, Erick. ___ Yahoo! Acesso Grátis - Internet rápida e grátis. Instale o discador agora! http://br.acesso.yahoo.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Sarge - postfix/saslauthd issues
Dear List:
Note: This is more for reference in the event that someone is
searching for info on this stuff.
I haven't had to touch my Postfix setup in quite a while, since it
has been running lovely. However, last time I configured it, I had a
lot of issues... that I hoped would be resolved this time.
Unfortunately I had the same problems today as I tried to configure
Postfix/saslauthd. It may very well be ME that is the problem, but I
thought I would seek some other opinions.
System: Debian Sarge
postfix2.1.5-9
sasl2-bin2.1.19-1.5
libsasl22.1.19-1.5
libsasl2-modules2.1.19-1.5
PROBLEM 1:
The first problem is is that Postfix can't connect to the saslauthd
socket. The reason appears to be because it is running in a chroot
environment (by default) and the socket is outside of the jail by
default.
These what the vars in the "/etc/init.d/saslauthd" script looks like:
NAME=saslauthd
DAEMON="/usr/sbin/${NAME}"
DESC="SASL Authentication Daemon"
DEFAULTS=/etc/default/saslauthd
PWDIR=/var/run/saslauthd
PIDFILE="/var/run/${NAME}/saslauthd.pid"
The saslauthd socket is created as "$PWDIR/mux". However, Postfix
looks for it as "/var/spool/postfix/var/run/saslauthd/mux".
Errors without /var/spool/postfix/var/run/saslauthd/mux (/var/log/
mail.log):
postfix/smtpd[7663]: warning: SASL authentication failure: cannot
connect to saslauthd server: No such file or directory
postfix/smtpd[7663]: warning: SASL authentication failure: Password
verification failed
postfix/smtpd[7663]: warning: SASL PLAIN authentication failed
To fix it I removed "/var/run/saslauthd", and then recreated it as a
soft link to "/var/spool/postfix/var/run/saslauthd" (make sure that
postfix or whatever the postfix user is, is a part of the sasl group).
This fixes the problem for me, but Is there anything I'm missing? I
really didn't find anything in the documentation for saslauthd that
led to this. Just want to make sure I didn't waste hours of my life
for no reason. ;)
PROBLEM 2:
When installing "saslauthd", the following directory is created: "/
etc/postfix/sasl". However, out of the box i can't seem to
authenticate with saslauthd unless I manually create the file
"smtpd.conf".
Errors without /etc/postfix/sasl/smtpd.conf:
/var/log/mail.log:
postfix/smtpd[7501]: warning: SASL authentication problem: unable to
open Berkeley db /etc/sasldb2: No such file or directory
postfix/smtpd[7501]: warning: SASL authentication problem: unable to
open Berkeley db /etc/sasldb2: No such file or directory
postfix/smtpd[7501]: warning: SASL authentication failure: Password
verification failed
postfix/smtpd[7501]: warning: SASL PLAIN authentication failed
/var/log/auth.log:
postfix/smtpd[7501]: OTP unavailable because can't read/write key
database /etc/opiekeys: No such file or directory
Logs obviously show that its not finding an AUTH mechanism. I
thought that "/etc/defaults/saslauthd" or something else held the
info for authentication mechanisms. however, unless I create
"smtpd.conf" with the following in it:
pwcheck_method: saslauthd
mech_list: plain login
is there any reason that this file isn't create when apt-get
installing postfix/saslauthd? I've found info on the net that
mentions this file in "/usr/lib/sasl/smtpd.conf" or "/usr/lib/sasl2/
smtpd.conf" but never in "/etc/postfix/sasl/smtpd.conf". Maybe its
just me.
Regardless, its working. Maybe this info can help someone else, or
maybe someone out there has a bit more knowledge to help me
understand why this seemed so difficult.
Thanks
p.s. - my postfix config -
---
mail:/# cat /etc/postfix/main.cf
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no
myhostname = mail.mydomain.com
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
myorigin = /etc/mailname
mydestination =
localhost,
mail.mydomain.com,
mydomain.com
relayhost =
mynetworks =127.0.0.0/8
home_mailbox = Maildir/
mailbox_size_limit = 0
recipient_delimiter = +
smtpd_recipient_restrictions =
permit_mynetworks,
permit_sasl_authenticated,
reject_unauth_destination,
permit
# SASL AUTH
smtpd_sasl_auth_enable = yes
broken_sasl_auth_clients = yes
smtpd_sasl_security_options = noanonymous
---
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
KDE 3.1 installation complains about kmidi
KDE 3.1 installation complains about kmidi I'm not sure whether this has been brought up before, but I searched the mailing list archives and couldn't quite find anything that seemed relevant to my situation. I gave Debian (Woody) a try a few days ago -- installed it from scratch, and then grabbed XFree86 from the official stable package distribution. So far so good. Then, in order to get KDE 3.1, I changed to unstable and used apt-get install on each of the KDE packages. I immediately got an error message when I tried getting kdemultimedia -- it said something about unresolved dependancies (unfortunatately I'm at work and can't check the exakt message), listing only kmidi, and then said it couldn't be installed. I then went ahead with all of the other packages, and then it went just fine. When all was done, I wanted to get kdemultimedia again -- but the problem was the same, apt-get still would refuse to get it, complaining about kmidi. I then used dselect and selected the kdemultimedia package. This time I got some kind of dependancy list suggestion, which I accepted. Then to my horror it starts downloading very large amounts of data, replacing such things as my gcc with gcc 3.x, installing new C/C++ libraries and all sorts of packages from unstable that I didn't think were directly related, and that I'd really prefer not be replaced. I thought at first I had done something wrong, and repeated the whole scenario again yesterday -- including reformatting the partitions and installing Debian again. Same result! I would be very grateful for any advice. I'd really like to continue running Debian as I like the package management system from what I have seen, but this is a real show-stopper for me and surely there must be others who stumbled upon this, or who successfully installed KDE 3.1 from scratch in Woody? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
