Hardware Clock to GMT instead of local time
I had been using Debian since July of 1998. It had been a dual boot NT/Debian Box. At the time of installation I remember selecting something like 'Set HW Clock to Local Time'. Now that I've dumped NT completely and I want to change it to 'HW Clock set to GMT' as I believe that is the way UNIXish machines should be configured. The question is: what configuration, startup scripts am I supposed to modify so that everthing will work correctly.
Re: Fetchmail: SMTP connect to localhost failed
The fully qualified name of my linux box is evolution.bilten.metu.edu.tr Here is what I have in /etc/exim.conf local_domains = localhost:evolution:evolution.bilten.metu.edu.tr sender_host_reject_relay = * sender_host_reject_relay_except = localhost
proftpd vs wu-ftpd
I am planning to enable anonymous ftp to my linux box. I am aware of two alternatives: proftpd and wu-ftpd. Any advantages of one over another? TIA
kernel: eth0: Transmit error
Today I had to reboot my linux box by issuing CTRL-ALT-DEL The system has suddenly become unresponsive while copying some file from an smbfs mount point. The following messages were displayed on the console over and over again: kernel: eth0: Transmit error, Tx status register 90 kernel: eth0: transmit timed out, tx_status 00 status e000. ( What was actually displayed on the console may be a little bit different as I copied these messages from syslog ) I suspect it might have been a problem with the ethernet driver as the problem dissappeared after reboot. I have a PCI ethernet card, something like 3com 3c590, so I am using the 3c59x module supplied with kernel 2.2.9 I am using linux kernel 2.2.9 with kernel automounter for loading/unloading modules. So what might be the problem? I recall having faced similar problems before. The entry just before the eth error in the syslog might give a clue: Jul 15 10:09:35 evolution kernel: SMBFS: Win 95 bug fixes enabled Jul 15 10:15:08 evolution kernel: eth0: Transmit error, Tx status register 90. Jul 15 10:15:08 evolution kernel: eth0: Transmit error, Tx status register 90. Jul 15 10:15:31 evolution kernel: eth0: transmit timed out, tx_status 00 status e000. TIA
Re: Exim SMTP
Thanks for those replies from Jor-el, Gregory and Martin. But the solutions Jor-el and Gregory had proposed did not work for me, so I has to the some RTFM. THE PROBLEM I installed netscape and was trying to configure mail. I have exim installed and configured for internet site, uses SMTP. I tried to configure localhost as the outgoing smtp server. Exim kept refusing connection requests to the SMTP port from netscape, as if mail relay requests from clients on the localhost was not allowed. THE SOLUTION I decided I must allow mail relaying for localhost. Checked /etc/exim.conf and found: # The setting below locks out the use of your host as a mail relay by any # other host. See the section of the manual entitled Control of relaying # for more info. sender_host_reject_relay = * So this means mail relaying is disabled, even for the localhost ?!? So after doing some RTFM, I decided I will add the following line to /etc/exim.conf sender_host_reject_relay_except = localhost And now, finally everthing is working fine. Just wondered, is there any gain from disabling mail relaying for the localhost by default?
Exim SMTP
I am using Debian Slink with Exim, configured for an Internet Site, to receive and send mail using SMTP. Everthing is configured using default configuration paraemeters. That is relaying mail through smtp for nonlocal domains is disabled. Now the question is wether Exim rejects smtp requests from localhost. I have installed netscape communicator and as the Outgoing Mail (SMTP) server I am trying to setup localhost. When I try to send mails a dialog appears, informing me that the smtp server does not accept the connection or sth. like that. What might be causing this behaviour? Is it because of the config defaults of exim? TIA
fan speed, temp monitoring etc.
Most of the new motherboards features such as: CPU, mainboard temprature CPU, power supply fan speed Voltage level monitoring. Guess it must be quite difficult to obtain a general purpose monitoring software as the hardware implementation of such features seem to be motherboard brand specific. Just wondered if there is some piece of existing linux software for ASUS motherboards. Though I am quite new to Linux ( 1.5 years ), I have some programming experience and I am considering to start a project for mainboard monitoring software.
cdrom permissions
I have an IDE ATAPI cdrom, it is /dev/hdb I have created a soft link, that is /dev/cdrom that points to /dev/hdb eject and workman do not work\ probably due to permissions of /dev/hdb brwxrwx--x 1 root disk 3, 64 Mar 3 19:20 /dev/hdb What is the correct way to solve this problem. Some solutions I can think of are as follows: 1.Give everyone read access for /dev/hdb; does not seem so nice to allow raw access to everyone 2.chgrp cdrom /dev/hdb , and add users that will be allowed to play/eject cd's to this group 3. setuid eject and workman executables
Re: pciutils package (was: Sound blaster 16 pnp)
Hans van den Boogert wrote: That explains something I experienced before. Thanks for the tip. BTW, this pciutils package is not in the basic Debian 2.1 set up, yet with every boot up the kernel invokes lspci, which is doesn't find of course. Is this an oversight from the team who compiled the installation list, or is there a reason for omitting? Seems a bit strange to me. Hans Infact it seems to be the best thing that could have been done. PnP support is provided beginning with kernel 2.2 series and slink is by default shipped with 2.0.36 pciutils package will not work with 2.0.36, so there is no use putting it into the basic Debian 2.1 setup. Slink is a kernel 2.2 ready distribution and it is nice to have lspci invoked (without making any modifications in the boot scripts) at runtime once you have upgraded to kernel 2.2 I get to like debian more and more when I notice such design details. Byeee Onur
Re: Sound blaster 16 pnp
On Mon, 24 May 1999, Ali Onur UYAR wrote: What this means is that, as the 16-bit dma channel you have to pass another 8-bit dma channel that is instead of passing irq 5,6,7 etc. you have to pass irq 0,1,2,3 At some point an error message is displayed, something similar to Bad dma channel. Simply IGNORE THIS MSG. Everthing works fine once configuration is complete. The message is displayed because the sb module expectes one 8-bit an another 16-bit dma channel, but you have to pass teo 8-bit dma channels to the module. Then Brad wrote: Odd. All this time i've been passing dma16=5 to the sb module and everything worked fine. pnpdump (and windows, for that matter) gave the same number for 16-bit dma. insmod sb io=0x220 irq=9 dma=1 dma16=5 mpu_io=0x300 type=6 (the type=6 came from the soundcard manual, i'm not completely sure if the sb module uses it at all... or where i even got the option 'type' from) Well my answer is ( me being Ali Onur UYAR ). You have to pass to 8-bit dma channels; that is what I read in the kernel docs for kernel 2.2.9 for sound card VIBRA16, and that is what has worked for me. Passing a 16-bit dma, simply did not work. Maybe your card is not a VIBRA16, I know that mine is beacuse it is what the bios detects at boot time. The related text in the kernel doc is given below: Sound Blaster 16X Vibra addendum by Marius Ilioaea [EMAIL PROTECTED] Stefan Laudat [EMAIL PROTECTED] Sat Mar 6 23:55:27 EET 1999 Hello again, Playing with a SB Vibra 16x soundcard we found it very difficult to setup because the kernel reported a lot of DMA errors and wouldn't simply play any sound. A good starting point is that the vibra16x chip full-duplex facility is neither still exploited by the sb driver found in the linux kernel (tried it with a 2.2.2-ac7), nor in the commercial OSS package (it reports it as half-duplex soundcard). Oh, I almost forgot, the RedHat sndconfig failed detecting it ;) So, the big problem still remains, because the sb module wants a 8-bit and a 16-bit dma, which we could not allocate for vibra... it supports only two 8-bit dma channels, the second one will be passed to the module as a 16 bit channel, the kernel will yield about that but everything will be okay, trust us.
Re: strange msg in bootup
On Sat, 22 May, Graham Aston wrote: On Friday 21 May, Dan Willard wrote: The route command now requires a netmask. Just add one in to both of the route commands and it should go away. if you read the 2.2 docs in /usr/src/linux/Changes (or whatever it's called) then you should find a bit that tells you that routes for local interfaces are added automatically by the kernel. comment out the route... lines in /etc/init.d/network and the problem should go away. Thanks, the problem is solved now. The correct solution seems to be commenting out the appropriate lines in the file /etc/init.d/network
Re: Sound blaster 16 pnp
Roddie, I've just configured my SoundBlaster Vibra 16pnp card on Friday. I started off sending a posting to this newsgroup, compiled a 2.2 kernel, read plenty of docs and manuals and if you have the some card that is Vibra 16, than I guess you may be experiencing the same problems I have experienced a week before. The answer is in the kernel docs. I have installed kernel 2.2.9 and looking up ./Documentation/sound/VIBRA16 will be helpful. The following paragraph is from the mentioned file. So, the big problem still remains, because the sb module wants a 8-bit and a 16-bit dma, which we could not allocate for vibra... it supports only two 8-bit dma channels, the second one will be passed to the module as a 16 bit channel, the kernel will yield about that but everything will be okay, trust us. What this means is that, as the 16-bit dma channel you have to pass another 8-bit dma channel that is instead of passing irq 5,6,7 etc. you have to pass irq 0,1,2,3 At some point an error message is displayed, something similar to Bad dma channel. Simply IGNORE THIS MSG. Everthing works fine once configuration is complete. The message is displayed because the sb module expectes one 8-bit an another 16-bit dma channel, but you have to pass teo 8-bit dma channels to the module. Another tip that might be helpful; if you are using slink, install pciutils package, which provides lspci utility which can be invoked by pnpdump when called with the argument '-c '. Once lspci is installed pnpdump worked fine for me, I did not have to make any further modifications in /etc/isapnp.conf Before invoking pnpdump, do not forget to remove all the sound modules first. This was one of the mistakes I made. If you skip this step some of the irq's might be marked as being used. and pnpdump will not produce the correct results. Using lsmod and rmmod may be helpful. Summary Install pci utils pnpdump -c /etc/isapnp.conf Install the following modules: sb, sound. soundcore, uart401, opl3 Using insmod what I did for testing was insmod soundcore insmod sound insmod uart401 insmod sb irq=5 dma=1 dma16=3 io=0x220 mpu_io=0x330 insmod opl3 io=0x388 Then cat /dev/sndstat That's all. Send a mail, for further questions.
strange msg in bootup
I have been using Linux for a year. I started with hamm and now I am using
slink.
I was running kernel 2.0.36 until last week.
Then decided it was the time to tackle sound config.
Then I realized it might had been a bit easier if I switched to 2.2 series
kernels.
Read a great deal of docs, installed the kernel 2.2.9 using kernel-package and
it worked!
Then I configured the sound card, configuring the Soundblaster Vibra16pnp
troubled
me a great deal, but everything was fine in the end.
Now the problem is that I have recognized a strange message during boot up, and
I am not
exactly sure if it is related to this final upgrade.
Just after the local file systems are mounted, a message is displayed on the
console:
SIOCADDRT: Invalid argument
SIOCADDRT: Invalid argument
Hunted around in /etc/rcS.d for some time and discovered that the message was
displayed while
the file /etc/rcS.d/S40network was being executed.
Placing some echo commands here and there I tracked down the problem to the
invocations of
the route command.
Doesn't seem to be a serious problem, as everything seems to be working, but
what may be the
cause for such an error msg, can anybody help. I do not have any experience with
routing issues.
Following is a listing of my /etc/rcS.d/S40network file, hope it will help:
#! /bin/sh
ifconfig lo 127.0.0.1
route add -net 127.0.0.0
IPADDR=144.122.246.42
NETMASK=255.255.252.0
NETWORK=144.122.244.0
BROADCAST=144.122.247.255
GATEWAY=144.122.246.1
ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
route add -net ${NETWORK}
[ ${GATEWAY} ] route add default gw ${GATEWAY} metric 1
Sound
Hello. I've got a running Debian Slink system, I've been using Debian since Hamm had become stable. Now that I have time for it, I would like to configure sound support. I have Sounblaster 16 sound card that works properly under NT, which I use quite rarely. From some of the postings to this list I have figured that I have to use isapnp utils. pnpdump /etc/isapnp.conf Then edit /etc/isapnp.conf to set irq, dma etc. And now for the questions: What do I do next? Where do I get the sound module from? How do I install it? How do I test that sound is working before installing new software? Any pointers for information are welcome. TIA
