On Sat, 20 Sep 2003 08:14:07 +0200, Harald Schmalzbauer
<[EMAIL PROTECTED]> wrote:
Well, for weeks now I couldn't compile (almost) any port. It seems that
ports aren't tested against -current. Is that true?
Not only the -pthread removement broke countless ports (some of them are
easy to fix oth
On Sat, Sep 20, 2003 at 08:14:07AM +0200, Harald Schmalzbauer wrote:
> Well, for weeks now I couldn't compile (almost) any port. It seems that
> ports aren't tested against -current. Is that true?
No.
> Not only the -pthread removement broke countless ports (some of them are
> easy to fix other
Well, for weeks now I couldn't compile (almost) any port. It seems that
ports aren't tested against -current. Is that true?
Not only the -pthread removement broke countless ports (some of them are
easy to fix others aren't) also the entire new kde fails.
Is there no aim to have ports running on -
On Thu, Sep 18, 2003 at 08:48:57PM -0700, Will Andrews wrote:
> My -CURRENT workstation won't boot off the WD Raptor 36GB disk,
> which is on a SiI 3112A SATA-150 controller. This was working
> with a kernel in early July. {build,install}{world,kernel}
> completed. Fortunately, it seems I can st
On Fri, 19 Sep 2003, Kris Kennaway wrote:
> On Fri, Sep 19, 2003 at 07:09:03PM -0400, Daniel Eischen wrote:
> > ATA (atapicam also in kernel) doesn't seem to work after the
> > changes in the last 24 hours or so. I have a SCSI system
> > with one ATAPI CD-ROM drive, which gets probed on a good
>
On Sat, Sep 20, 2003 at 01:47:44AM +0100, Bruce M Simpson wrote:
> On Sat, Sep 20, 2003 at 02:17:21AM +0200, Marius Strobl wrote:
> > > Isn't it still a kernel bug if a user process can trigger a panic?
> >
> > Yes, it seems to be a bug in the mlockall(2) implementation. Backing
> > it out or hind
> > This became quite tricky, but the main (and the worst problem) was with ATAng.
> > I have Acer's motherboard and IBM's DTLA. Old driver were saying 'Non-ATA 66 cable
> > or device' and perfectly worked in UDMA-33 mode. New driver didn't said a word,
> > but when it tried to read something, ev
On Sat, Sep 20, 2003 at 02:17:21AM +0200, Marius Strobl wrote:
> > Isn't it still a kernel bug if a user process can trigger a panic?
>
> Yes, it seems to be a bug in the mlockall(2) implementation. Backing
> it out or hindering cdrecord to use it avoids the panic. I already
> wrote an email to bm
On Fri, Sep 19, 2003 at 04:36:32PM -0700, Kris Kennaway wrote:
> On Fri, Sep 19, 2003 at 06:21:52PM +0200, Marius Strobl wrote:
> > On Thu, Sep 18, 2003 at 05:51:25PM +0200, Jan Srzednicki wrote:
> > >
> > > Anyway, here's backtrace for atapicam panic I've mentioned. It's
> > > triggered by:
> > >
Nevermind, I switched from slave to master of CD-RW; it boots just fine
and function fine too. No more weird busy signal at all the time.
Time to use my own kernel config..
Cheers,
Mezz
On Wed, 17 Sep 2003 11:59:46 -0500, Jeremy Messenger <[EMAIL PROTECTED]> wrote:
Last night, I CVSup'ed and di
Who-hoo, it works!!! Thanks a bunch!!!
On Fri, 19 Sep 2003, Marius Strobl wrote:
> On Thu, Sep 18, 2003 at 05:51:25PM +0200, Jan Srzednicki wrote:
> >
> > Anyway, here's backtrace for atapicam panic I've mentioned. It's
> > triggered by:
> >
> > cdrecord dev=1,1,0 /some/track
> >
>
> This panic i
On Fri, Sep 19, 2003 at 06:21:52PM +0200, Marius Strobl wrote:
> On Thu, Sep 18, 2003 at 05:51:25PM +0200, Jan Srzednicki wrote:
> >
> > Anyway, here's backtrace for atapicam panic I've mentioned. It's
> > triggered by:
> >
> > cdrecord dev=1,1,0 /some/track
> >
>
> This panic isn't ATAPICAM re
On Fri, Sep 19, 2003 at 07:09:03PM -0400, Daniel Eischen wrote:
> ATA (atapicam also in kernel) doesn't seem to work after the
> changes in the last 24 hours or so. I have a SCSI system
> with one ATAPI CD-ROM drive, which gets probed on a good
> kernel as:
sos will probably ask for boot -v outpu
On Fri, 19 Sep 2003, Marius Strobl wrote:
> On Thu, Sep 18, 2003 at 05:51:25PM +0200, Jan Srzednicki wrote:
> >
> > Anyway, here's backtrace for atapicam panic I've mentioned. It's
> > triggered by:
> >
> > cdrecord dev=1,1,0 /some/track
> >
>
> This panic isn't ATAPICAM related. Could you try the
ATA (atapicam also in kernel) doesn't seem to work after the
changes in the last 24 hours or so. I have a SCSI system
with one ATAPI CD-ROM drive, which gets probed on a good
kernel as:
ata0-slave: timeout waiting for interrupt
ata0-slave: ATAPI identify failed
acd0: CDROM at ata0-master PIO4
Wa
On Fri, 19 Sep 2003, Dan Naumov wrote:
> On Fri, 2003-09-19 at 19:21, Marius Strobl wrote:
> > On Thu, Sep 18, 2003 at 05:51:25PM +0200, Jan Srzednicki wrote:
> > >
> > > Anyway, here's backtrace for atapicam panic I've mentioned. It's
> > > triggered by:
> > >
> > > cdrecord dev=1,1,0 /some/track
On Wed, 17 Sep 2003, Andrew Thompson wrote:
> Nate Lawson wrote:
> > On Wed, 17 Sep 2003, Andrew Thompson wrote:
> >
> >>111 sc_cur_scr = sc->cur_scp->index;
> >
> > For a temporary workaround, try changing line 111 to:
> > if (sc->cur_scp == NULL)
> > return (0);
> >
> > Th
On Fri, 19 Sep 2003, Soren Schmidt wrote:
> I disagree, but that another matter..
>
> How about just doing:
>
> dd if=/dev/acdXtY of=trackY bs=2352
>
> Now that cant be simpler and is already present...
>
In XMMS/XINE/cdda2wav/cdparanoia/...? Lots of programs depend on this
interface, and not j
I have a single SATA drive on an Adaptec 1210SA card.
The drive will give a write error warning a few times, then will repeatedly
give:
ad4: timeout sending command=ca
The only recovery is the reset switch, reboot single-user fsck, and then
come back up in multiuser.
These errors occur with di
FreeBSD bart 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Mon Sep 15 23:44:16 PDT
2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BART i386
I am currently having a very unusual problem with installing StarOffice
6.0 under -CURRENT. Installation in root works fine. When in normal user
install all that hap
On Fri, 2003-09-19 at 19:21, Marius Strobl wrote:
> On Thu, Sep 18, 2003 at 05:51:25PM +0200, Jan Srzednicki wrote:
> >
> > Anyway, here's backtrace for atapicam panic I've mentioned. It's
> > triggered by:
> >
> > cdrecord dev=1,1,0 /some/track
> >
>
> This panic isn't ATAPICAM related. Could
With the latest updates from Soren my server was always finding the
master drive but not the slave. This morning I decided to move
the slave drive to secondary master and see if that worked. As I was
doing that I noticed the slave was jumpered as "Cable Select". I've
never had good luck with CS an
On Thu, Sep 18, 2003 at 05:51:25PM +0200, Jan Srzednicki wrote:
>
> Anyway, here's backtrace for atapicam panic I've mentioned. It's
> triggered by:
>
> cdrecord dev=1,1,0 /some/track
>
This panic isn't ATAPICAM related. Could you try the patch below? It's
against the cdrtools-devel port but sh
On Thu, 18 Sep 2003, Scott Long wrote:
> We'd like to get a new poll on the stability and readiness of 4.9.
I hope you posted this to -stable :-)
--
Doug White| FreeBSD: The Power to Serve
[EMAIL PROTECTED] | www.FreeBSD.org
___
On Fri, Sep 19, 2003 at 08:22:13 -0700, Sam Leffler wrote:
> > Hmm. One other thing I'm seeing is that when I configure a 128 bit key
> > with ifconfig or wicontrol (wicontrol shows all 28 characters -- 0x plus
> > 26 hex characters), ifconfig still thinks it is a 104 bit key. This is
> > because
> Hmm. One other thing I'm seeing is that when I configure a 128 bit key
> with ifconfig or wicontrol (wicontrol shows all 28 characters -- 0x plus
> 26 hex characters), ifconfig still thinks it is a 104 bit key. This is
> because ireq.i_len is 13.
>
You must not have the up to date ifconfig.
I forgot to add that excessive heat and faulty ram are ruled out, I've
checked system temp and it seems to be OK, memtest has also passed all
tests completely without giving any errors. It *COULD* theoretically be
the HD going "bad", but how could I possibly check this?
Sincerely,
Dan Naumov
TB --- 2003-09-19 11:05:40 - starting CURRENT tinderbox run for sparc64/sparc64
TB --- 2003-09-19 11:05:40 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-09-19 11:07:39 - building world
TB
Hello
I am having some very annoying problems with a FreeBSD 5.1 install.
Every 4-6 hours, it either reboots by itself or locks up hard, with the
HD led being constantly lit. I've tried looking into the logs, but
nothing is written to them before the lockup/reboot, even if I choose
"boot FreeBSD w
Tinderbox <[EMAIL PROTECTED]> writes:
> /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/net/bridge.c: In function
> `bridge_in':
> /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/net/bridge.c:857: warning:
> cast from pointer to integer of different size
> *** Error code 1
Please
On Sep 19, 2003, at 1:55 AM, Christian Brueffer wrote:
On Thu, Sep 18, 2003 at 11:22:37PM -0500, David Leimbach wrote:
Hey... just looking to see what option I need to enable to get HFS+
support...
All you need should be here: http://people.freebsd.org/~yar/hfs/
Doesn't compile under CURRENT it
On Sep 19, 2003, at 5:45 AM, Terry Lambert wrote:
David Leimbach wrote:
Hey... just looking to see what option I need to enable to get HFS+
support...
I am going to try experimenting with building a ppc cross-build
environment and
try to install FreeBSD on my iPod and boot from it :)
(1) iPod's de
TB --- 2003-09-19 09:33:15 - starting CURRENT tinderbox run for ia64/ia64
TB --- 2003-09-19 09:33:15 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-09-19 09:36:34 - building world
TB --- cd /home
David Leimbach wrote:
> Hey... just looking to see what option I need to enable to get HFS+
> support...
>
> I am going to try experimenting with building a ppc cross-build
> environment and
> try to install FreeBSD on my iPod and boot from it :)
(1) iPod's default to MSDOSFS for compatabilit
On Fri, 2003-09-19 at 02:10, M. Warner Losh wrote:
> P.S. How do you handle the packlist generation? The ports system
> doesn't automatically generate these things, as far as I can tell, and
> I didn't see anything that you've added to do this.
>
> My agenda, if you will, on this is to deal with
On Fri, 2003-09-19 at 02:02, M. Warner Losh wrote:
> Why would you want to package sbin? Where do you see this work going?
> What problems do you think this will solve? Doing things a top level
> directory at a time isn't very interesting, but since it looks like a
> demo, perhaps you could sketc
Le 2003-09-19, Guillaume écrivait :
> Thanks for the patch. cd0 is faster now and ATAPICAM works great.
That's good news!
> Are you going to commit the patch?
Yes, the patch is currently being reviewed.
--
[EMAIL PROTECTED]
___
[EMAIL PROTECTED]
On Thu, Sep 18, 2003 at 11:21:20PM -0600, Scott Long wrote:
>We'd like to get a new poll on the stability and readiness of 4.9.
Last night I upgraded my laptop and it hung partway thru the boot
(immediately after the pcm0: line in the dmesg below). Powering
it off and back on made it boot normall
Strange, very strange. SOeren, you know my hardware, it is the same MB
(ASUS P4S8X or the like - off memory).
I built a couple of worlds during the past months.
But with the recent cvsups I don't get through. make world or make buildworld
both fail nearly exactly at the same place during the cle
It seems Jan Srzednicki wrote:
> > dd if=/dev/acdXtY of=trackY bs=2352
>
> Cool. ;)
Yes, and that has worked for ages...
> Could you give me a hint what to put in devd.conf to get acdXtY files
> created automatically when a CD is inserted?
You just need something to open the acdX device (so the
On Fri, Sep 19, 2003 at 08:02:31AM +0200, Soren Schmidt wrote:
> It seems Jan Srzednicki wrote:
> > > As far as problems with dagrab and cdda2wav are conserned - this is
> > > because of removal of CDIOCREADAUDIO ioctl in ATAng (see recent thread
> > > "What's happened to CDIOCREADAUDIO & friends")
41 matches
Mail list logo
