Re: 4.2-RELEASE CD from ISO
> On Mon, Nov 27, 2000 at 10:17:01PM -0500, Bill Pechter wrote: > > However I couldn't mount it under Solaris... Any ideas what I did wrong. > > Not w/o you telling the command you used and the error(s) produced... Well... vold chokes on it and it times out on a direct mount of /cdrom -- just kind of hangs there on Solaris 8 and times out. I just put it on one of my developer's Solaris 2.6 Ultra 10's. It works fine... It mounts on FreeBSD ok and on Win98 ok... Seems to be a Solaris 8 Intel problem. Sorry folks... pass the conical hat this way... I just tested it on the Solaris8 Intel boxes before I jumped to the mailing list. Sorry. --Bill -- [EMAIL PROTECTED]| FreeBSD since 1.0.2, Linux since 0.99.10 | Unix Sys Admin since Sys V/BSD 4.2 | Windows System Administration: "Magical Misery Tour" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: httpd could not be started
Jim wrote something like: > > Jeremy Hopkins Scribled, > > > I ran into the same problem yesterday as well. What you need to do is > > recompile mod_ssl. I simple did a make from > > /usr/ports/www/apache13-modssl and then > > copy > > > /usr/ports/www/apache13-modssl/work/apache_1.3.14/src/modules/ssl/libssl.so > > over your existing libssl.so located at > > /usr/local/libexec/apache/libssl.so > > It is worth mentioning that apache13-modssl will probably not build unless > Openssl is up to date. I have had this problem. This is true. My openssl came up to date with my make world, so it was overlooked when my response was drafted. I unsafely assumed that the user in question had also updated openssl with their upgrade. Thanks for noting this. Jeremy -- Jeremy Hopkins - Systems Administrator - RTCI - Cary, NC www.rtci.com- [EMAIL PROTECTED] www.ghettoweb.net - [EMAIL PROTECTED] FreeBSD -- Makes the net go round. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: httpd could not be started
Nader Turki wrote: > > Hi there, > I just upgraded from FreeBSD 4.1.1-STABLE to FreeBSD 4.2-STABLE. > I can't start apache anymore. something is wrong and i hope you guys can > help me. > > [root@shadow]:/usr/home/dark# /usr/local/sbin/apachectl startssl > Syntax error on line 54 of /usr/local/etc/apache/apache.conf: > Cannot load /usr/local/libexec/apache/libssl.so into server: > /usr/local/libexec/apache/libssl.so: Undefined symbol > "sk_X509_NAME_value" > /usr/local/sbin/apachectl startssl: httpd could not be started > I ran into the same problem yesterday as well. What you need to do is recompile mod_ssl. I simple did a make from /usr/ports/www/apache13-modssl and then copy /usr/ports/www/apache13-modssl/work/apache_1.3.14/src/modules/ssl/libssl.so over your existing libssl.so located at /usr/local/libexec/apache/libssl.so In the meantime you can probably start apache without ssl support with an apachectl start, but that somewhat depends on your configuration. You should be back up shortly. Have fun! jeremy I Jeremy Hopkins - Systems Administrator - RTCI - Cary, NC www.rtci.com- [EMAIL PROTECTED] www.ghettoweb.net - [EMAIL PROTECTED] FreeBSD -- Makes the net go round. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ata0 problems
Adrian Penisoara wrote:
>
> Hi,
>
> Just to be sure: please post the dmesg part refering to ATA probes.
> Also please post the result of "sysctl hw.atamodes'; if it has a "dma" in
> the list then try a "sysctl -w hw.atamodes=pio,---,---,---" under root and
> check if the error appear again.
>
> I seem to remember I had this kind of problems myself too and I believe
> this is because of some issues when operating in DMA mode (either hardware
> configuration issues, like bad cable, eiher a driver problem). I solved my
> problem by forcing the controller into PIO mode ("hw=pio,---,---,---" in
> /etc/sysctl.conf).
>
> Ady (@warpnet.ro)
>
> On Fri, 24 Nov 2000, Michael wrote:
>
> > FreeBSD 4.2
> > Cyrix-166
> > ATA-66- WD 7200 2Mb cache
> >
> > On Thu, 23 Nov 2000, Corey G. wrote:
> >
> > > I saw the same error tonight. (if it is an error).
> > >
> > > FreeBSD 4.2
> > > AMD K62-450
> > > ATA-66 - Maxtor Drive
> > >
> > > ad0: WRITE command timeout tag=0 serv=0 - resetting
> > > ata0: resetting devices .. done
> > > ad0: WRITE command timeout tag=0 serv=0 - resetting
> > > ata0: resetting devices .. done
> > >
> > > On Thu, Nov 23, 2000 at 06:30:11PM +, Michael wrote:
> > > > Hello
> > > > I have problems in FreeBSD 4.2-STABLE
> > > >
> > > >
> > > > Nov 23 09:49:53 lucky /kernel: ata0: resetting devices .. done
> > > > Nov 23 09:50:44 lucky /kernel: ad0: WRITE command timeout tag=0 serv=0 -
> > > > resetting
> > > >
> > > > regards, Michael
> > > >
> > > >
> > > >
> > > > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > > > with "unsubscribe freebsd-stable" in the body of the message
> > > ---end quoted text---
> > >
> > > --
> > > Best Regards,
> > > Corey
I have this exact same problem as well, it goes away in PIO mode,
but what if we want to use DMA or UDMA?
I think the ata driver needs some fixing because DMA mode worked
fine in previouse version of FreeBSD...
4.1R I use UDMA33 without any errors, yet once upgraded to 4.2S
I have to use PIO mode or I cant access the drive.
It would seem to be that a controler and a drive that support DMA
transfers are not the problem but the driver that cant use them
properly is...
I dont see how you can blame it on faulty hardware or cables when
the EXACT same system using 4.0R and 4.1R was able to use DMA mode
with no problems...
People have said that after getting this error there drives have
been totaly hosed, unable to even boot, I find it hard to put this
down to the driver, but somehow I doubt every haivng this problem
is using dodgey equipment...
So while its possible to get around the problems using PIO mode it
seems silly to not fix a bug just because you can get around it...
We have the workaround... now lets have the fix?!
Cheers everyone,
Kal.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: ata0 problems
Hi,
Just to be sure: please post the dmesg part refering to ATA probes.
Also please post the result of "sysctl hw.atamodes'; if it has a "dma" in
the list then try a "sysctl -w hw.atamodes=pio,---,---,---" under root and
check if the error appear again.
I seem to remember I had this kind of problems myself too and I believe
this is because of some issues when operating in DMA mode (either hardware
configuration issues, like bad cable, eiher a driver problem). I solved my
problem by forcing the controller into PIO mode ("hw=pio,---,---,---" in
/etc/sysctl.conf).
Ady (@warpnet.ro)
On Fri, 24 Nov 2000, Michael wrote:
> FreeBSD 4.2
> Cyrix-166
> ATA-66- WD 7200 2Mb cache
>
> On Thu, 23 Nov 2000, Corey G. wrote:
>
> > I saw the same error tonight. (if it is an error).
> >
> > FreeBSD 4.2
> > AMD K62-450
> > ATA-66 - Maxtor Drive
> >
> > ad0: WRITE command timeout tag=0 serv=0 - resetting
> > ata0: resetting devices .. done
> > ad0: WRITE command timeout tag=0 serv=0 - resetting
> > ata0: resetting devices .. done
> >
> > On Thu, Nov 23, 2000 at 06:30:11PM +, Michael wrote:
> > > Hello
> > > I have problems in FreeBSD 4.2-STABLE
> > >
> > >
> > > Nov 23 09:49:53 lucky /kernel: ata0: resetting devices .. done
> > > Nov 23 09:50:44 lucky /kernel: ad0: WRITE command timeout tag=0 serv=0 -
> > > resetting
> > >
> > > regards, Michael
> > >
> > >
> > >
> > > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > > with "unsubscribe freebsd-stable" in the body of the message
> > ---end quoted text---
> >
> > --
> > Best Regards,
> > Corey
> >
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: 4.2-RELEASE CD from ISO
On Mon, Nov 27, 2000 at 10:17:01PM -0500, Bill Pechter wrote: > However I couldn't mount it under Solaris... Any ideas what I did wrong. Not w/o you telling the command you used and the error(s) produced... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: httpd could not be started
On Mon, Nov 27, 2000 at 11:55:47PM -0500, Nader Turki wrote: > Hi there, > I just upgraded from FreeBSD 4.1.1-STABLE to FreeBSD 4.2-STABLE. > I can't start apache anymore. something is wrong and i hope you guys can > help me. > > [root@shadow]:/usr/home/dark# /usr/local/sbin/apachectl startssl > Syntax error on line 54 of /usr/local/etc/apache/apache.conf: > Cannot load /usr/local/libexec/apache/libssl.so into server: > /usr/local/libexec/apache/libssl.so: Undefined symbol > "sk_X509_NAME_value" Try recompiling mod_ssl - I know that's non-trivial if you run a live site under it. Looks like something changed that broke ssl? Which is quite odd - ssh still works OK for me (4.0->4.2) -- Rasputin Jack of All Trades :: Master of Nuns To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: emu10k1 (soundblaster live!) still crackling.
hi, I've seen this problem on some motherboard (without sound on the mother board) but where a version of this motherboard with sound existed. In fact it appeared that the sound circuitry was partly wired and the "sound option" had to be disabled in the bios (even though the mother board was supposed to be without the sound option). (on another mother board without sound I found that only the amplifier were missing) Le Lun, 27 nov 2000, William S. Duncanson a écrit : > I get pops all the time on my SBLive! card, under FreeBSD, Win2K, and > ME. I'm starting to think that it's a hardware problem and not a > software/driver problem. It seems to be related to the CD drives spining > up (and dumping noise into the CD audio or CD digital port, maybe?) I > haven't quite gotten around to calling Creative about it, though. > > At 13:59 11/27/2000 -0600, Drew Sanford wrote: > >I haven't noticed this problem on either my SMP 4.2 machine or my UP 4.2 > >machine, both with SBLive!'s. The only time I've noticed any flaws at all > >was on the SMP machine when it was slammed and I was playing mp3's on > >xmms, there were a few glitches, but we are talking about loads of up to > >6.00 with swapping going on fairly heavily. > > > >David Lebel wrote: > > > >>Hello, > >>I'm using 4.2-STABLE on a machine that has a SoundBlaster Live! > >>soundcard. Around the time 4.0 was released, I had bunch of problems > >>with the card giving bunch of static and crackling sound when sound > >>was being played. This was apparently fixed around the 4.1 release, > >>but since the latest MFC, I still notice occasional glitches in the > >>sound (mostly pops). > >>Am I along having this problem? > >>Ciao, > >> ...David > > > > > >-- > >Drew Sanford > >Systems Administrator > >Planetwe.com > >Email: [EMAIL PROTECTED] > > > > > > > >To Unsubscribe: send mail to [EMAIL PROTECTED] > >with "unsubscribe freebsd-stable" in the body of the message > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- -- Didier Derny [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
