Re: KDE with all dependencies now running

[Vallo Kallaste]

On Wed, Sep 04, 2002 at 11:09:20PM +0200, Martin Blapp <[EMAIL PROTECTED]> wrote:

> With these options in /etc/make.conf
> 
> NO_CPU_CFLAGS=true
> NO_CPU_COPTFLAGS=true
> 
> and kan's gcc patch:

[ripped]
> and a removal of a const value of the fam port:

[ripped]
> I was able to finished a build of kde with _ALL_ dependencies.

For awhile now (two-three months or so), I've found these CPU options
absolutely beneficial for getting my -current system somewhat stable
and minimise gcc internal errors, althought not completely. Quite
strange..
-- 

Vallo Kallaste
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

acpica-unix-20020829 patches (was Re: Lots of ACPI errors whenbooting yesterdays CURRENT

[Mitsuru IWASAKI]

Hi,

> Below is a trimmed dmesg from booting yesterdays CURRENT on my 
> SuperMicro P3TDE6 machine (RCC/ServerWorks HE-SLt chipset).
> I heven't found anything wrong with the OS, it is just that the boot 
> seems to be a bit on the chatty side :-)
> Is this caused by a bad BIOS setting or is there something strange with 
> this board/BIOS or the acpi support in CURRENT?
> I also noticed support for four acpi_cpu:s is, this as intended, the 
> board only have room for two?

Please try the latest version acpica-unix-20020829, patches for
FreeBSD at:
http://people.freebsd.org/~iwasaki/acpi/acpica-20020815-20020829-test20020905.diff

Hopefully some of the problems will be solved.
From CHANGES.txt

If the target of a Scope() operator already exists, it must
be an object type that actually opens a scope -- such as a
Device, Method, Scope, etc.  This is a fatal runtime error.
Similar error check has been added to the iASL compiler
also.

Tightened up the namespace load to disallow multiple names
in the same scope.  This previously was allowed if both
objects were of the same type.  (i.e., a lookup was the same
as entering a new name).


Thanks

> Copyright (c) 1992-2002 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
>   The Regents of the University of California. All rights reserved.
> FreeBSD 5.0-CURRENT #0: Tue Sep  3 17:41:10 CEST 2002
>  [EMAIL PROTECTED]:/usr/obj/ext/FreeBSD/CURRENT/sys/EUKLIDES
> Preloaded elf kernel "/boot/kernel/kernel" at 0xc04c7000.
> Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04c70a8.
> Timecounter "i8254"  frequency 1193182 Hz
> Timecounter "TSC"  frequency 1266068553 Hz
> CPU: Pentium III/Pentium III Xeon/Celeron (1266.07-MHz 686-class CPU)
>Origin = "GenuineIntel"  Id = 0x6b1  Stepping = 1
>  
> 
>Features=0x383fbff
> real memory  = 536805376 (524224K bytes)
> avail memory = 515674112 (503588K bytes)
> Pentium Pro MTRR support enabled
> Using $PIR table, 10 entries at 0xc00f52e0
>  ACPI-0536: *** Error: Field name [INDX] already exists in current scope
>  ACPI-0536: *** Error: Field name [DATA] already exists in current scope
>  ACPI-0536: *** Error: Field name [INDX] already exists in current scope
>  ACPI-0536: *** Error: Field name [DATA] already exists in current scope
>  ACPI-0536: *** Error: Field name [C000] already exists in current scope
>  ACPI-0536: *** Error: Field name [C010] already exists in current scope
>  ACPI-0536: *** Error: Field name [C020] already exists in current scope
>  ACPI-0685: *** Warning: NsLookup: INDX, type 1, checking for type 11
>  ACPI-0685: *** Warning: NsLookup: DATA, type 2, checking for type 11
>  ACPI-0685: *** Warning: NsLookup: INDX, type 1, checking for type 11
>  ACPI-0685: *** Warning: NsLookup: DATA, type 2, checking for type 11
>  ACPI-0685: *** Warning: NsLookup: C000, type 8, checking for type 13
>  ACPI-0685: *** Warning: NsLookup: C010, type 8, checking for type 13
>  ACPI-0685: *** Warning: NsLookup: C020, type 8, checking for type 13
> npx0:  on motherboard
> npx0: INT 16 interface
> acpi0:  on motherboard
>  ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND
>  ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND
>  ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND
>  ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND
>  ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND
>  ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND
>  ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND
>  ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND
> acpi0: power button is handled as a fixed feature programming model.
> Timecounter "ACPI-safe"  frequency 3579545 Hz
>  ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND
> --- 15 identical lines removed
> acpi_timer0: <32-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0
> acpi_cpu0:  on acpi0
> acpi_cpu1:  on acpi0
> acpi_cpu2:  on acpi0
> acpi_cpu3:  on acpi0
> acpi_button0:  on acpi0
> pcib1:  on acpi0
> pci0:  on pcib1
> pcib3:  at device 0.1 on pci0
> pci1:  on pcib3
> pci1:  at device 0.0 (no driver attached)
> nge0:  port 0xde00-0xdeff mem 
> 0xfeadb000-0xfeadbfff irq 11 at device 1.0 on pci0
> nge0: Ethernet address: 00:40:33:af:35:33
> miibus0:  on nge0
> nsgphy0:  on miibus0
> nsgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
> 1000baseT-FDX, auto
> pci0:  at device 2.0 (no driver attached)
> pcm0:  port 0xdf00-0xdf3f irq 11 at device 3.0 on pci0
> ahc_pci0:  port 0xd000-0xd0ff mem 
> 0xfeadc000-0xfeadcfff irq 5 at device 5.0 on pci0
> aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
> ahc_pci1:  port 0xd800-0xd8ff mem 
> 0xfeadf000-0xfead irq 10 at device 5.1 on pci0
> aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs
> fxp0:  port 0xd400-0xd43f mem 
> 0xfe90-0xfe9f,0xfeadd000-0xfeaddfff irq 9 a

Re: fsck cannot find superblock

[Bruce Evans]

On Thu, 5 Sep 2002, Ian Dowse wrote:

> In message <[EMAIL PROTECTED]>, Bruce Evans writes:
> >> * drop support for 4K block sizes completely, but this breaks
> >>   backwards compatibility
> >
> >I use patches like the following for the sanity checks:
>
> I think there may be other problems that are triggered by using <8k
> blocks on -current too. Last time I tried 4k blocks (pre-UFS2), the
> snapshot code would cause a panic when trying to allocate a single
> 4k block to fit the 8k superblock (the machine then got stuck in a
> reboot-fsck-panic cycle until interrupted and manually fsck'd).

I sometimes run a simple benchmark which tests most combinations of
block and fragment sizes starting with 4096-512.  This didn't show
anoy problems for 4k blocks either pre- or post-ufs2.  But it doesn't
test snapshots, actual ufs2 filesystems, or anything else that is newer
than soft updates, or full filesystems...

Bruce


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: aout support broken in gcc3

[Bakul Shah]

> You are blowing this out of proportion and not actually reading
> what people are proposing.  So far, the comments are about
> removing a.out support from the base compiler and offering
> a.out binutils and gcc _as ports_.

A port is fine -- but this was proposed much later in the
thread.

> > Unfortunately there is no such direct back-pressure in the
> > open source community and developers usually don't have a
> > long term view.
> 
> Thank you for insulting our intelligence.

Sorry you see it that way -- I certainly didn't mean to
insult anyone's intelligence.  It is just the way I see it --
programmers want to program neat new things (or "clean up"
code or make thinge more elegant, faster, more modular, more
generic and so on) and users just want to continue using what
they are comfortable with -- even when they want to play with
new and shiny things.  I believe both groups should
participate in deciding the direction FreeBSD takes.  That is
what will bring out the best without breaking old things.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: gcore/elfcore.c broken?

[Garance A Drosihn]

At 12:58 AM -0700 9/5/02, walt wrote:
>cc -O -pipe -mcpu=pentiumpro-c /usr/src/usr.bin/gcore/elfcore.c
>/usr/src/usr.bin/gcore/elfcore.c: In function `elf_coredump':
>/usr/src/usr.bin/gcore/elfcore.c:128: syntax error before "nleft"
>/usr/src/usr.bin/gcore/elfcore.c:131: `nleft' undeclared (first use 
>in this function)
>/usr/src/usr.bin/gcore/elfcore.c:131: (Each undeclared identifier is 
>reported only once
>/usr/src/usr.bin/gcore/elfcore.c:131: for each function it appears in.)

I suspect it was broken as part of the commit:

dwmalone2002/09/04 16:29:10 PDT
   Log:
   ANSIify function definitions.
   Add some constness to avoid some warnings.
   Remove use register keyword.
   Deal with missing/unneeded extern/prototypes.
   Some minor type changes/casts to avoid warnings.

   Reviewed by:md5

   Revision  ChangesPath
   ......   ...
   1.11  +10 -9 src/usr.bin/gcore/elfcore.c
   1.28  +3 -1  src/usr.bin/gcore/gcore.c
   1.6   +3 -3  src/usr.bin/gcore/md-nop.c
   ......   ...


I think it just needs to  #include 
if you want to try a quick fix so you can finish the buildworld.
-- 
Garance Alistair Drosehn=   [EMAIL PROTECTED]
Senior Systems Programmer   or  [EMAIL PROTECTED]
Rensselaer Polytechnic Instituteor  [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

i386 tinderbox failure

[Dag-Erling Smorgrav]

--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
--
>>> stage 2: rebuilding the object tree
--
>>> stage 2: build tools
--
>>> stage 3: cross tools
--
>>> stage 4: populating 
>/home/des/tinderbox/i386/obj/local0/scratch/des/src/i386/usr/include
--
>>> stage 4: building libraries
--
>>> stage 4: make dependencies
--
>>> stage 4: building everything..
--
===> usr.bin/gcore
/local0/scratch/des/src/usr.bin/gcore/elfcore.c: In function `elf_coredump':
/local0/scratch/des/src/usr.bin/gcore/elfcore.c:128: syntax error before "nleft"
/local0/scratch/des/src/usr.bin/gcore/elfcore.c:131: `nleft' undeclared (first use in 
this function)
/local0/scratch/des/src/usr.bin/gcore/elfcore.c:131: (Each undeclared identifier is 
reported only once
/local0/scratch/des/src/usr.bin/gcore/elfcore.c:131: for each function it appears in.)
*** Error code 1

Stop in /local0/scratch/des/src/usr.bin/gcore.
*** Error code 1

Stop in /local0/scratch/des/src/usr.bin.
*** Error code 1

Stop in /local0/scratch/des/src.
*** Error code 1

Stop in /local0/scratch/des/src.
*** Error code 1

Stop in /local0/scratch/des/src.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: [PATCH] 'ata_dmasetup: transfer active on this device!'problem on resume

[Mitsuru IWASAKI]

Sorry, typo...

> @@ -674,6 +712,20 @@
>   ad_start(&ch->device[MASTER]);
>   if (ch->devices & (ATA_ATA_SLAVE) && ch->device[SLAVE].driver)
>   ad_start(&ch->device[SLAVE]);
> +}
> +if (ch->devices & (ATA_ATA_MASTER) && ch->device[MASTER].driver) {
> + if (ch->device[MASTER].suspended && ch->device[MASTER].mode >= ATA_DMA) {
> + printf("%s: going to suspend, ignoring.\n", __func__);
> + splx(s);
> + return;
> +  }
> +}
> +if (ch->devices & (ATA_ATA_SLAVE) && ch->device[SLAVE].driver) {
> + if (ch->device[SLAVE].suspended && ch->device[MASTER].mode >= ATA_DMA) {
  ^^^ SLAVE

Thanks

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

[PATCH] 'ata_dmasetup: transfer active on this device!' problem onresume

[Mitsuru IWASAKI]

Hi, Soren.  I got panics with 'ata_dmasetup: transfer active on this
device!' on resume, and have made patches for this.
Problem was that certain process is accessing ATA disk via DMA
transfer on suspend, however the transfer was not completed in most cases,
then ata_dmastart() (called by ata_reinit()) got panic on resume.

My patches will do those things during suspend time;
 - wait for DMA transfer completion if it is on the way.
 - cancel new requests (yes, it's possible even during suspend
   time) for ATA disks and remain them in ATA queue.

Could you review the patches and commit them if OK?

Thanks

Index: ata-all.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v
retrieving revision 1.153
diff -u -r1.153 ata-all.c
--- ata-all.c   9 Aug 2002 20:51:53 -   1.153
+++ ata-all.c   4 Sep 2002 10:21:22 -
@@ -279,8 +279,46 @@
 }
 
 int
+ata_suspend(device_t dev)
+{
+struct ata_channel *ch;
+
+ch = device_get_softc(dev);
+
+#ifdef DEV_ATADISK
+if (ch->devices & ATA_ATA_MASTER && ch->device[MASTER].driver) {
+   ch->device[MASTER].suspended = 1;
+   if (ch->device[MASTER].mode >= ATA_DMA) {
+   ata_waitdmadone(&ch->device[MASTER]);
+   }
+}
+if (ch->devices & ATA_ATA_SLAVE && ch->device[SLAVE].driver) {
+   ch->device[SLAVE].suspended = 1;
+   if (ch->device[SLAVE].mode >= ATA_DMA) {
+   ata_waitdmadone(&ch->device[SLAVE]);
+   }
+}
+#endif
+
+return 0;
+}
+
+int
 ata_resume(device_t dev)
 {
+struct ata_channel *ch;
+
+ch = device_get_softc(dev);
+
+#ifdef DEV_ATADISK
+if (ch->devices & ATA_ATA_MASTER && ch->device[MASTER].driver) {
+   ch->device[MASTER].suspended = 0;
+}
+if (ch->devices & ATA_ATA_SLAVE && ch->device[SLAVE].driver) {
+   ch->device[SLAVE].suspended = 0;
+}
+#endif
+
 return ata_reinit(device_get_softc(dev));
 }
 
@@ -674,6 +712,20 @@
ad_start(&ch->device[MASTER]);
if (ch->devices & (ATA_ATA_SLAVE) && ch->device[SLAVE].driver)
ad_start(&ch->device[SLAVE]);
+}
+if (ch->devices & (ATA_ATA_MASTER) && ch->device[MASTER].driver) {
+   if (ch->device[MASTER].suspended && ch->device[MASTER].mode >= ATA_DMA) {
+   printf("%s: going to suspend, ignoring.\n", __func__);
+   splx(s);
+   return;
+}
+}
+if (ch->devices & (ATA_ATA_SLAVE) && ch->device[SLAVE].driver) {
+   if (ch->device[SLAVE].suspended && ch->device[MASTER].mode >= ATA_DMA) {
+   printf("%s: going to suspend, ignoring.\n", __func__);
+   splx(s);
+   return;
+}
 }
 if ((ad_request = TAILQ_FIRST(&ch->ata_queue))) {
TAILQ_REMOVE(&ch->ata_queue, ad_request, chain);
Index: ata-all.h
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-all.h,v
retrieving revision 1.53
diff -u -r1.53 ata-all.h
--- ata-all.h   18 Apr 2002 19:11:43 -  1.53
+++ ata-all.h   4 Sep 2002 06:25:24 -
@@ -189,6 +189,7 @@
 intcmd;/* last cmd executed */
 void   *result;/* misc data */
 struct ata_dmastatedmastate;   /* dma state */
+intsuspended;  /* 0 = normal  1 = suspended */
 };
 
 /* structure describing an ATA channel */
@@ -252,6 +253,7 @@
 int ata_probe(device_t);
 int ata_attach(device_t);
 int ata_detach(device_t);
+int ata_suspend(device_t);
 int ata_resume(device_t);
 
 void ata_start(struct ata_channel *);
@@ -280,6 +282,7 @@
 int ata_dmasetup(struct ata_device *, caddr_t, int32_t);
 int ata_dmastart(struct ata_device *, caddr_t, int32_t, int);
 int ata_dmastatus(struct ata_channel *);
+void ata_waitdmadone(struct ata_device *);
 int ata_dmadone(struct ata_device *);
 
 /* macros for locking a channel */
Index: ata-dma.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-dma.c,v
retrieving revision 1.100
diff -u -r1.100 ata-dma.c
--- ata-dma.c   19 Jul 2002 22:14:54 -  1.100
+++ ata-dma.c   4 Sep 2002 11:15:50 -
@@ -31,6 +31,7 @@
 #include 
 #include 
 #include 
+#include 
 #include 
 #include 
 #include  
@@ -1284,8 +1285,11 @@
 struct ata_dmastate *ds = &atadev->dmastate;
 struct ata_dmasetup_data_cb_args cba;
 
-if (ds->flags & ATA_DS_ACTIVE)
-   panic("ata_dmasetup: transfer active on this device!");
+if (ds->flags & ATA_DS_ACTIVE) {
+   printf("ata_dmastart: transfer active on this device!\n");
+   Debugger("ata_dmastart");
+   return -1;
+}
 
 cba.dmatab = ds->dmatab;
 bus_dmamap_sync(ds->cdmatag, ds->cdmamap, BUS_DMASYNC_PREWRITE);
@@ -1312,6 +1316,16 @@
 return 0;
 }
 
+void
+ata_waitdmadone(struct ata_device *atadev)
+{
+if (atadev->dmastate.flags & ATA_DS_ACTIVE) {
+   printf("%s: waiting for ata_

alpha tinderbox failure

[Dag-Erling Smorgrav]

--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
--
>>> stage 2: rebuilding the object tree
--
>>> stage 2: build tools
--
>>> stage 3: cross tools
--
>>> stage 4: populating /home/des/tinderbox/alpha/obj/var/tmp/des/src/alpha/usr/include
--
>>> stage 4: building libraries
--
>>> stage 4: make dependencies
--
>>> stage 4: building everything..
--
>>> Kernel build for GENERIC started on Wed Sep  4 18:21:56 PDT 2002
--
>>> Kernel build for GENERIC completed on Wed Sep  4 19:27:15 PDT 2002
--
>>> Kernel build for LINT started on Wed Sep  4 19:27:16 PDT 2002
--
===> LINT
config: Error: device "apm_saver" is unknown
config: Error: device "cy" is unknown
config: Error: device "cy" does not take a count
config: 3 errors
WARNING: kernel contains GPL contaminated ext2fs filesystem
FYI: static unit limits for vcoda are set: NVCODA=4
FYI: static unit limits for dgb are set: NDGB=1
FYI: static unit limits for card are set: NCARD=1
FYI: static unit limits for meteor are set: NMETEOR=1
*** Error code 1

Stop in /var/tmp/des/src.
*** Error code 1

Stop in /var/tmp/des/src.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

gcore/elfcore.c broken?

[walt]

cc -O -pipe -mcpu=pentiumpro-c /usr/src/usr.bin/gcore/elfcore.c
/usr/src/usr.bin/gcore/elfcore.c: In function `elf_coredump':
/usr/src/usr.bin/gcore/elfcore.c:128: syntax error before "nleft"
/usr/src/usr.bin/gcore/elfcore.c:131: `nleft' undeclared (first use in this function)
/usr/src/usr.bin/gcore/elfcore.c:131: (Each undeclared identifier is reported only once
/usr/src/usr.bin/gcore/elfcore.c:131: for each function it appears in.)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: installworld broken

[Kris Kennaway]

On Wed, Sep 04, 2002 at 11:27:52AM +0200, Mario Goebbels wrote:

> H. Is mergemaster really necessary? I mean when upgrading from a fresh
> 4.6 install?

No, but completely upgrading /etc most assuredly is.  If you don't use
mergemaster to do this then you'll probably find it a real PITA.

Kris



msg42632/pgp0.pgp
Description: PGP signature

Re: fsck cannot find superblock

[Ian Dowse]

In message <[EMAIL PROTECTED]>, Bruce Evans writes:
>> * drop support for 4K block sizes completely, but this breaks
>>   backwards compatibility
>
>I use patches like the following for the sanity checks:

I think there may be other problems that are triggered by using <8k
blocks on -current too. Last time I tried 4k blocks (pre-UFS2), the
snapshot code would cause a panic when trying to allocate a single
4k block to fit the 8k superblock (the machine then got stuck in a
reboot-fsck-panic cycle until interrupted and manually fsck'd).

Ian

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: KDE broken on CURRENT (with gcc3.2)

[Michael Reifenberger]

On Tue, 3 Sep 2002, Beech Rintoul wrote:

> Date: Tue, 3 Sep 2002 23:53:05 -0800
> From: Beech Rintoul <[EMAIL PROTECTED]>
> To: Michael WARDLE <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: KDE broken on CURRENT (with gcc3.2)
>
> On Tuesday 03 September 2002 09:28 pm, Michael WARDLE wrote:
> > > I have the exact same problem (even with fam-2.6.9).
> > > Can you post that patch?
> >
> > There was an error with FAM and GCC 3.1 discussed here:
> > 
> >
> > If this is the problem you are seeing, try removing the
> > "const" modifier from Scheduler.h in the FAM sources.
removing the const modifier fixes the compilation error
of fam with -current's gcc for me.

The diff is:
--- Scheduler.h.origThu Sep  5 00:20:53 2002
+++ Scheduler.h Thu Sep  5 00:21:34 2002
@@ -105,7 +105,7 @@
 //  for the corresponding I/O type.

 struct IOTypeInfo {
-   FDInfo::FDIOHandler FDInfo::*const iotype;
+   FDInfo::FDIOHandler FDInfo::* iotype;
unsigned int nbitsset;  // number of bits set in fds
fd_set fds;
IOTypeInfo(FDInfo::FDIOHandler FDInfo::* a_iotype) :


Bye!

Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis, GPS


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: KDE broken on CURRENT (with gcc3.2)

[Michael Reifenberger]

On Tue, 3 Sep 2002, Alexander Kabaev wrote:
...
>
> The patch is not mine. I extracted it from GCC FSF CVS repository.
> --
> Alexander Kabaev
Could you please commit it to -current?
It seems to do its job in that area.

Bye!

Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis, GPS


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

KDE with all dependencies now running

[Martin Blapp]

Hi,

With these options in /etc/make.conf

NO_CPU_CFLAGS=true
NO_CPU_COPTFLAGS=true

and kan's gcc patch:

RCS file: /home/ncvs/src/contrib/gcc/cp/cp-lang.c,v
retrieving revision 1.1.1.2
diff -u -r1.1.1.2 cp-lang.c
--- cp/cp-lang.c1 Sep 2002 20:38:06 -   1.1.1.2
+++ cp/cp-lang.c3 Sep 2002 00:47:05 -
@@ -122,14 +122,8 @@
 {
   if (CLASS_TYPE_P (TREE_TYPE (exp)))
 {
-  /* The backend should not be interested in the size of an expression
-of a type with both of these set; all copies of such types must go
-through a constructor or assignment op.  */
-  if (TYPE_HAS_COMPLEX_INIT_REF (TREE_TYPE (exp))
- && TYPE_HAS_COMPLEX_ASSIGN_REF (TREE_TYPE (exp)))
-   abort ();
-  /* This would be wrong for a type with virtual bases, but they are
-caught by the abort above.  */
+  /* This would be wrong for a type with virtual bases, but they should
+not get here.  */

and a removal of a const value of the fam port:

--- fam/Scheduler.h.origWed Sep  4 22:50:11 2002
+++ fam/Scheduler.h Wed Sep  4 22:49:18 2002
@@ -105,7 +105,7 @@
 //  for the corresponding I/O type.

 struct IOTypeInfo {
-   FDInfo::FDIOHandler FDInfo::*const iotype;
+   FDInfo::FDIOHandler FDInfo::*iotype;
unsigned int nbitsset;  // number of bits set in fds
fd_set fds;
IOTypeInfo(FDInfo::FDIOHandler FDInfo::* a_iotype) :

I was able to finished a build of kde with _ALL_ dependencies.

Thank you everybody who made this possible.

Alexander, will you commmit the gcc workaround ?

Martin

Martin Blapp, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
ImproWare AG, UNIXSP & ISP, Zurlindenstrasse 29, 4133 Pratteln, CH
Phone: +41 061 826 93 00: +41 61 826 93 01
PGP: 
PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E
--



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: fam broken on CURRENT (with gcc3.2)

[Martin Blapp]

Hi,

> I have upgraded fam to 2.6.9. Please check if the problem still exists.
> Thanks.

Yes it is still broken. Can you review this patch and
commit it appropriate ? This fixes the brokeness with
gcc32.

$ cat patch-Scheduler.h

--- Scheduler.h.origWed Sep  4 22:50:11 2002
+++ Scheduler.h Wed Sep  4 22:49:18 2002
@@ -105,7 +105,7 @@
 //  for the corresponding I/O type.

 struct IOTypeInfo {
-   FDInfo::FDIOHandler FDInfo::*const iotype;
+   FDInfo::FDIOHandler FDInfo::*iotype;
unsigned int nbitsset;  // number of bits set in fds
fd_set fds;
IOTypeInfo(FDInfo::FDIOHandler FDInfo::* a_iotype) :


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: fsck cannot find superblock

[Bruce Evans]

On Wed, 4 Sep 2002, Daniel Rock wrote:

> Bruce Evans schrieb:
>
> >On Tue, 3 Sep 2002, D. Rock wrote:
> >>with 'uncommon' block sizes fsck seems to have problems finding the
> >>superblock:
> >
> >fsck_ffs has no problems here with (whole) md disk of the same size.
> >Perhaps I have fixed the problem without noticing.  dumpfs or comparison
> >with a non-broken filesystem of the same size might show the problem.
>
> The problem seems to be introduced with the UFS2 import. In
> src/sbin/fsck_ffs/setup.c the sanity checks are more tightly formulated.
> Especially one check was added:
> sblock.fs_bsize >= SBLOCKSIZE
>
> this fails on 4K file systems, because fs_bsize is only 4096, but
> SBLOCKSIZE is defined as 8192. The sanity checks for searching alternate

Ah.  In fact, I have fixed this without noticing that it was so broken.
The sanity test is obviously insane, since the minimum block size (4K)
has been smaller than the maximum superblock size (SBLOCKSIZE = 8K)
forever.  I reduced the minimum block size (MINBSIZE) to 512 some time
ago and had to fix similar problems in the kernel.  The ufs2 changes
added similar problems in many utilities.

> superblocks are more relaxed (in readsb() the first if branch is
> entered, not the else branch), so during searching for alternate
> superblocks the very same sb that was rejected in the first run (at
> offset 8192) will be used.
>
> Possible solutions:
>
> * remove above sanity check
> * does SBLOCKSIZE really have to be 8192, in real it is much smaller
>   (less than 2KB)

The super block size is given by fs_sbsize, and newfs is happy to set it
to much smaller than 8192.  I tried to reduce it as much as possible.
IIRC, it gets rounded up to a multiple of the block size, so it can be
4K but no smaller when the block size is 4K.  It can be 1536 if the block
block size is 512, but no smaller since sizeof(struct fs) is 1376.  I
think the removal of rotdelay stuff makes its size always the same as
that of struct fs (rounded up).  dumpfs output:

%%%
magic   11954 (UFS1)timeThu Sep  5 06:06:17 2002
id  [ 3d7667b9 39a059fe ]
ncg 9   size8192blocks  7475
bsize   512 shift   9   mask0xfe00
^^^
fsize   512 shift   9   mask0xfe00
frag1   shift   0   fsbtodb 0
minfree 8%  optim   timesymlinklen 60
maxbpg  64  maxcontig 256   contigsumsize 16
nbfree  7474ndir1   nifree  2121nffree  0
cpg 1   bpg 937 fpg 937 ipg 236
nindir  128 inopb   4   nspf1   maxfilesize 1082202111
sbsize  1536cgsize  512 cgoffset 0  cgmask  0x

csaddr  108 cssize  512
rotdelay 0msrps 60  trackskew 0 interleave 1
nsect   937 npsect  937 spc 937
sblkno  32  cblkno  48  iblkno  49  dblkno  108
cgrotor 0   fmod0   ronly   0   clean   1
flags   none
%%%

BTW, dumpfs's error handling has been broken by conversion to libufs.
libufs in -current has slightly different insane sanity checks, and
when these fail dumpfs prints "dumpfs: /dev/md0: No such file or
directory" despite it just having opened and read from that file.  It
used to print "dumpfs: Cannot find filesystem superblock".

> * drop support for 4K block sizes completely, but this breaks
>   backwards compatibility

I use patches like the following for the sanity checks:

%%%
Index: setup.c
===
RCS file: /home/ncvs/src/sbin/fsck_ffs/setup.c,v
retrieving revision 1.38
diff -u -2 -r1.38 setup.c
--- setup.c 21 Aug 2002 18:10:28 -  1.38
+++ setup.c 22 Aug 2002 01:36:30 -
@@ -316,6 +314,6 @@
  numfrags(&sblock, sblock_try[i]))) &&
sblock.fs_ncg >= 1 &&
-   sblock.fs_bsize >= SBLOCKSIZE &&
-   sblock.fs_bsize >= sizeof(struct fs))
+   sblock.fs_bsize <= MAXBSIZE &&
+   sblock.fs_sbsize <= SBLOCKSIZE)
break;
}
%%%

Bruce


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Uncommitted dc0 fixes ...

[Mark Murray]

OK, I've grabbed these...

M

> 
> Ups, forgot to add here the PR number ...
> 
> > 3) ADMtek AN98x, enable automatically TX underrun recovery
> 
> http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34236
> 
> > Patch No3 fixes some part of link problem on EN2242 cards.
> > I've tested this patch and it makes by laptop working again with
> > cvsup.
> 
> Martin
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
-- 
o   Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: fsck cannot find superblock

[Daniel Rock]

Bruce Evans schrieb:

>On Tue, 3 Sep 2002, D. Rock wrote:
>
>  
>
>>with 'uncommon' block sizes fsck seems to have problems finding the
>>superblock:
>>
>># newfs -i 10240 -b 4096 -f 512 /dev/ad1d
>>Reduced frags per cylinder group from 26208 to 26200 to enlarge last cyl group
>>/dev/ad1d: 409.6MB (838860 sectors) block size 4096, fragment size 512
>> using 33 cylinder groups of 12.79MB, 3275 blks, 1312 inodes.
>>super-block backups (for fsck -b #) at:
>>  32, 26232, 52432, 78632, 104832, 131032, 157232, 183432, 209632, 235832,
>>  262032, 288232, 314432, 340632, 366832, 393032, 419232, 445432, 471632,
>>  497832, 524032, 550232, 576432, 602632, 628832, 655032, 681232, 707432,
>>  733632, 759832, 786032, 812232, 838432
>># fsck /dev/ad1d
>>** /dev/ad1d
>>Cannot find file system superblock
>>
>>LOOK FOR ALTERNATE SUPERBLOCKS? [yn] n
>>
>>
>
>fsck_ffs has no problems here with (whole) md disk of the same size.
>Perhaps I have fixed the problem without noticing.  dumpfs or comparison
>with a non-broken filesystem of the same size might show the problem.
>
>Bruce
>  
>

I have attached the label of the offending disk and an output of  a 
dumpfs on a freshly created file system with the following options:
newfs -b 4096 -f 4096 /dev/ad1d
newfs -b 8192 -f 8192 /dev/ad1d


The problem seems to be introduced with the UFS2 import. In 
src/sbin/fsck_ffs/setup.c the sanity checks are more tightly formulated. 
Especially one check was added:
sblock.fs_bsize >= SBLOCKSIZE

this fails on 4K file systems, because fs_bsize is only 4096, but 
SBLOCKSIZE is defined as 8192. The sanity checks for searching alternate 
superblocks are more relaxed (in readsb() the first if branch is 
entered, not the else branch), so during searching for alternate 
superblocks the very same sb that was rejected in the first run (at 
offset 8192) will be used.

Possible solutions:

* remove above sanity check
* does SBLOCKSIZE really have to be 8192, in real it is much smaller
  (less than 2KB)
* drop support for 4K block sizes completely, but this breaks
  backwards compatibility

Daniel


# /dev/ad1c:
type: ESDI
disk: ad0s1
label: 
flags:
bytes/sector: 512
sectors/track: 252
tracks/cylinder: 4
sectors/cylinder: 1008
cylinders: 2482
sectors/unit: 2501856
rpm: 4500
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0   # milliseconds
track-to-track seek: 0  # milliseconds
drivedata: 0 

8 partitions:
#size   offsetfstype   [fsize bsize bps/cpg]
  b:   462996  2038860  swap# (Cyl. 2022*- 2481*)
  c:  25018560unused0 0 # (Cyl.0 - 2481)
  d:   83886004.2BSD  512  4096 26200   # (Cyl.0 - 832*)
  e:  120   8388604.2BSD 2048  8192 48388   # (Cyl.  832*- 2022*)


magic   11954 (UFS1)timeWed Sep  4 20:33:22 2002
id  [ 3d7651f2 4b7c67bc ]
ncg 8   size104857  blocks  103972
bsize   4096shift   12  mask0xf000
fsize   4096shift   12  mask0xf000
frag1   shift   0   fsbtodb 3
minfree 8%  optim   timesymlinklen 60
maxbpg  512 maxcontig 32contigsumsize 16
nbfree  103971  ndir1   nifree  27389   nffree  0
cpg 1   bpg 13681   fpg 13681   ipg 3424
nindir  1024inopb   32  nspf8   maxfilesize 4402345721855
sbsize  4096cgsize  4096cgoffset 0  cgmask  0x
csaddr  114 cssize  4096
rotdelay 0msrps 60  trackskew 0 interleave 1
nsect   109448  npsect  109448  spc 109448
sblkno  4   cblkno  6   iblkno  7   dblkno  114
cgrotor 0   fmod0   ronly   0   clean   1
flags   none

cs[].cs_(nbfree,ndir,nifree,nffree):
(13565,1,3421,0) (13571,0,3424,0) (13571,0,3424,0) (13571,0,3424,0) 
(13571,0,3424,0) (13571,0,3424,0) (13571,0,3424,0) (8980,0,3424,0) 
cylinders in last group 1
blocks in last group 9090


cg 0:
magic   90255   tell6000timeWed Sep  4 20:33:22 2002
cgx 0   ncyl1   niblk   3424ndblk   13681
nbfree  13565   ndir1   nifree  3421nffree  0
rotor   0   irotor  0   frotor  0
frsum
sum of frsum: 0
clusters 1-8:   0   0   0   0   0   0   0   0
clusters 9-15:  0   0   0   0   0   0   0
clusters size 16 and over: 1
clusters free:  116-13680
inodes used:0-2
blks free:  116-13680

cg 1:
magic   90255   tell3577000 timeWed Sep  4 20:33:22 2002
cgx 1   ncyl1   niblk   3424ndblk   13681
nbfree  13571   ndir0   nifree  3424nffree  0
rotor   0   irotor  0   frotor  0
frsum
sum of frsum: 0
clusters 1-8:   0   0   0   1   0   0   0   0
clusters 9-15:  0   0   0   0   0   0   0
clusters size 16 and over: 1
clusters free:  0-3, 114-13680
inodes used:
blks free:  0-3, 114-13680

cg

Re: aout support broken in gcc3

[Juli Mallett]

* De: Garrett Wollman <[EMAIL PROTECTED]> [ Data: 2002-09-04 ]
[ Subjecte: Re: aout support broken in gcc3 ]
> < 
>said:
> 
> > So they need a C compiler that can generate a.out format .o files, and
> > a linker that can link a.out format .o files against an a.out format
> > executable.
> 
> Not necessarily.  There is always `objcopy', at least for static
> executables.  The version we ship doesn't support any flavor of a.out,
> but that wouldn't be too difficult to fix if it solved this particular
> problem.

Or elf2aout could be used?
-- 
Juli Mallett <[EMAIL PROTECTED]>   | FreeBSD: The Power To Serve
Will break world for fulltime employment. | finger [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

installworld failure in libncurses

[Andrew Gallatin]

When doing an installworld from srcs cvsup'ed this morning,
installworld craps out linking ncurses man pages:

===> lib/libncurses
install -C -o root -g wheel -m 444   libncurses.a /usr/lib
install -C -o root -g wheel -m 444   libncurses_p.a /usr/lib
install -s -o root -g wheel -m 444 libncurses.so.5 /usr/lib
ln -fs libncurses.so.5 /usr/lib/libncurses.so
install -C -o root -g wheel -m 444  curses.h term.h termcap.h unctrl.h
/usr/src/lib/libncurses/../../contrib/ncurses/include/ncurses_dll.h
/usr/include
/usr/include/ncurses.h -> curses.h
ln -s /usr/src/lib/libncurses/../../contrib/ncurses/man/curs_addstr.3x
curs_addstr.3
ln: curs_addstr.3: File exists
<..>

Andybody seen this?  I hate doing make -i installworld, but it seems
thats the only thing which works anymore.

Thanks,

Drew


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: aout support broken in gcc3

[Garrett Wollman]

< 
said:

> So they need a C compiler that can generate a.out format .o files, and
> a linker that can link a.out format .o files against an a.out format
> executable.

Not necessarily.  There is always `objcopy', at least for static
executables.  The version we ship doesn't support any flavor of a.out,
but that wouldn't be too difficult to fix if it solved this particular
problem.

-GAWollman


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: perl busted, spins, ignores SIGKILL

[Thomas Quinot]

Le 2002-09-03, Lamont Granquist écrivait :

> i cvsup'd last night, and now i tried portupdate -a -f and debugging
> build problems with libtool i found that on my system i can make perl spin
> and consume 100% of a CPU just by:
> 
> perl -pe s/foo/bar/g /tmp

Any chance you have a /usr/local/bin/perl pointing back to
/usr/bin/perl? Cf. PR bin/42418.

-- 
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: web browsers (was: Re: aout support broken in gcc3)

[Garrett Wollman]

< said:

> for Internet Explorer").  I would suggest to anybody still using
> Netscape 4 on a Unix platform that they try a replacement
> browser, whether that be Mozilla, Galeon, or something else
> (perhaps Opera or Konqueror).

Mozilla has an intolerable (read: Windows) user interface.
Konqueror is a dog (at least on my machine), even though you can
reprogram the user interface somewhat, and its SSL/TLS support is
barely functional.

Neither program works properly with my bank's online banking service.

I'll stick with something that works, and works fast.  I'm well aware
of the security issues, and have determined the risk to be
insignificant for the way I use a Web browser.  (And frankly, I don't
much care what lusing Web-design weenies think about it.)

-GAWollman


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Uncommitted dc0 fixes ...

[Martin Blapp]

Ups, forgot to add here the PR number ...

> 3) ADMtek AN98x, enable automatically TX underrun recovery

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34236

> Patch No3 fixes some part of link problem on EN2242 cards.
> I've tested this patch and it makes by laptop working again with
> cvsup.

Martin


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Uncommitted dc0 fixes ...

[Martin Blapp]

Hi all,

Anybody who can, please commit these PR's.

1) dc driver uses wrong case to read MAC from eeprom.

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/35482


2) Tulip ether card EN2242 (if_dc.c) use wrong multicast table

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=misc/32699


3) ADMtek AN98x, enable automatically TX underrun recovery

Patch No3 fixes some part of link problem on EN2242 cards.
I've tested this patch and it makes by laptop working again with
cvsup.

And this patch here together with patch III made the annoying messages (dc0:
failed to force tx and rx to idle mode) go away. And I can use now my card
without to replug the cable over again)

--- /usr/src/sys/pci/if_dc.cSun Jun 16 21:36:00 2002
+++ /usr/src/sys/pci/if_dc.cWed Sep  4 16:57:23 2002
@@ -1338,17 +1362,21 @@
restart = 1;
DC_CLRBIT(sc, DC_NETCFG, (DC_NETCFG_TX_ON|DC_NETCFG_RX_ON));

-   for (i = 0; i < DC_TIMEOUT; i++) {
-   isr = CSR_READ_4(sc, DC_ISR);
-   if (isr & DC_ISR_TX_IDLE &&
-   (isr & DC_ISR_RX_STATE) == DC_RXSTATE_STOPPED)
-   break;
-   DELAY(10);
-   }
+   if (DC_IS_INTEL(sc)) {
+   for (i = 0; i < DC_TIMEOUT; i++) {
+   isr = CSR_READ_4(sc, DC_ISR);
+   if (isr & DC_ISR_TX_IDLE &&
+   (isr & DC_ISR_RX_STATE)
+   == DC_RXSTATE_STOPPED)
+   break;
+   DELAY(10);
+   }

-   if (i == DC_TIMEOUT)
-   printf("dc%d: failed to force tx and "
-   "rx to idle state\n", sc->dc_unit);
+   if (i == DC_TIMEOUT) {
+   printf("dc%d: failed to force tx and "
+   "rx to idle state\n", sc->dc_unit);
+   }
+   }
}

Martin Blapp, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
ImproWare AG, UNIXSP & ISP, Zurlindenstrasse 29, 4133 Pratteln, CH
Phone: +41 061 826 93 00: +41 61 826 93 01
PGP: 
PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E
--


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: installworld broken

[Steve Kargl]

On Wed, Sep 04, 2002 at 11:27:52AM +0200, Mario Goebbels wrote:
> >
> > make buildworld
> > make buildkernel
> > make installkernel
> > mergemaster -p
> > reboot
> > make installworld
> > mergemaster
> 
> 
> H. Is mergemaster really necessary?

You don't have to use mergemaster.  No one
is holding a gun to your head :-)  Mergemaster
makes routine maintenance of /etc extremely
easy (and, yes the rc scripts do change).

-- 
Steve

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

alpha tinderbox failure

[Dag-Erling Smorgrav]

--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
--
>>> stage 2: rebuilding the object tree
--
>>> stage 2: build tools
--
>>> stage 3: cross tools
--
>>> stage 4: populating /home/des/tinderbox/alpha/obj/var/tmp/des/src/alpha/usr/include
--
>>> stage 4: building libraries
--
>>> stage 4: make dependencies
--
>>> stage 4: building everything..
--
>>> Kernel build for GENERIC started on Wed Sep  4 06:14:22 PDT 2002
--
>>> Kernel build for GENERIC completed on Wed Sep  4 07:19:24 PDT 2002
--
>>> Kernel build for LINT started on Wed Sep  4 07:19:25 PDT 2002
--
===> LINT
config: Error: device "apm_saver" is unknown
config: Error: device "cy" is unknown
config: Error: device "cy" does not take a count
config: 3 errors
WARNING: kernel contains GPL contaminated ext2fs filesystem
FYI: static unit limits for vcoda are set: NVCODA=4
FYI: static unit limits for dgb are set: NDGB=1
FYI: static unit limits for card are set: NCARD=1
FYI: static unit limits for meteor are set: NMETEOR=1
*** Error code 1

Stop in /var/tmp/des/src.
*** Error code 1

Stop in /var/tmp/des/src.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: aout support broken in gcc3

[John Baldwin]

On 04-Sep-2002 Richard Tobin wrote:
>> You are blowing this out of proportion and not actually reading
>> what people are proposing.  So far, the comments are about
>> removing a.out support from the base compiler and offering
>> a.out binutils and gcc _as ports_.
> 
> That would be sufficient for my needs (a matching gdb would be useful
> too, I'm not sure if that is part of binutils).
> 
> But I don't think my concern was misplaced: having gone back through
> the thread for the past couple of weeks, there were certainly phrases
> like
> 
>   "drop all traces of a.out support"
>   "if you need to generate new ones (?) unpack a 2.2.6 system"
> 
> with the ports solution mentioned only "if we really have to have a.out".

Well, I think what happened is that people wanted to know if others still
needed a.out and thus if ports should be created.  I guess some people
have been saying some more drastic things then that and it is hard to know
who to listen to. :-/  It is a good thing to point out user's needs but
accusing developers of never taking the long-term view (which you did not
do, I know) is not a good way to win others over to one's argument.

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: installworld broken

[David Wolfskill]

>From: "Mario Goebbels" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Date: Wed, 4 Sep 2002 11:27:52 +0200

>H. Is mergemaster really necessary? I mean when upgrading from a fresh
>4.6 install?

Note that this is posted to the -current list, so the context *I* infer
from this is that you're referring to an upgrade from 4.6 (-STABLE) to
5.x (-CURRENT).  Thus, the answer to the stated question is  assuredly
"yes."

>I usually just copied the password files and rc.conf,
>copied -CURRENTs etc files into /etc and copied the passwd files back. Seems
>to work fine, especially because I never touch the RC scripts on my running
>BSD systems.

Somehow, using mergemaster to handle all of that seems like a definite
win to me; after all, that is why is exists -- or so I thought.

Cheers,
david   (links to my resume at http://www.catwhisker.org/~david)
-- 
David H. Wolfskill  [EMAIL PROTECTED]
To paraphrase David Hilbert, there can be no conflicts between the
discipline of systems administration and Microsoft, since they have
nothing in common.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: web browsers (was: Re: aout support broken in gcc3)

[Terry Lambert]

Michael WARDLE wrote:
> The Gecko engine developed by the Mozilla Project, however seems
> to be very good.  I find Galeon quite nice, as it uses Mozilla's
> quite capable HTML rendering engine, has its own well designed
> GTK-based GUI, and has little of Mozilla's bloat.

If it isn't broken, don't fix it.

> If you're looking for a replacement Internet mail client, you
> might like to try Mutt, Balsa, Sylpheed, or Evolution.

I like my applications to have the same look-and-feel.  I like
them to use the same shortcut keys for the same functions, etc..
Unfortunately, kmail and konquerer just aren't there yet, and
even though GTK has a "style guide", no one is very religious
about following it.  Reminds me a lot of a UI person I used to
know who prototyped all her UI stuff in Visual BASIC, and then
expected us to be able to implement things like modal dialogues
in HTML, so that browser-based access to the device resembled
a Windows application.  She totally refused to be "constrained
by HTML" during the design process, even though that was what
we had to deploy on.  Made it a real pain in the ass: everyone
who has to deal with UI code was effectively painting pixels
with an 8 foot paint brush.

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: aout support broken in gcc3

[Thomas David Rivers]

Terry Lambert <[EMAIL PROTECTED]> wrote:
> 
> Bruce Evans wrote:
> > Isn't this too old and security-holed to use?  It stopped being packaged a
> > few releases ago.  4.5R has mainly:
> > 
> > /usr/local/lib/netscape-linux/communicator-linux-4.79.bin: ELF 32-bit LSB 
>executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), 
>stripped
> > 
> > and mozilla.
> 
> I personally use the FreeBSD native Netscape.

 I'd like to as well - but I found that with version 4.5 and
 later (the move to XFree86 4.x) that the FreeBSD Netscape
 refused to run.

 There is a rather long discussion of what I found in the
 -stable archives I believe...

- Dave R. -

--
[EMAIL PROTECTED]Work: (919) 676-0847
Get your mainframe programming tools at http://www.dignus.com

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: PUC_FASTINTR broken

[Bruce Evans]

On Wed, 4 Sep 2002, Poul-Henning Kamp wrote:

> In message <[EMAIL PROTECTED]>, Bruce Evans writes:
> >INTR_FAST is an option for pci devices.  It was configured (not quite right)
> >by the PUC_FASTINTR option, which should work just as well as the similar
> >but much older CY_PCI_FASTINTR option (perfectly if the interrupt is not
> >shared).
>
> It doesn't work right if the puc manages to register the interrupt as
> FAST before we realize that it is shared.

That is not a problem, since it is the configurer's responsibility to not
use PUC_FASTINTR if it would not work.  PUC_FASTINTR exists precisely to
let the configurer make the correct choice, sint the driver and new-bus
cannot.

> >This change blows away the support for that option without even removing
> >the option from conf/options, conf/NOTES or puc.4, and without even
> >noting approval of the author of the code.
>
> I have yet to clean that fluff.

Please don't.

Bruce


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: installworld broken

[Mario Goebbels]

> > > > : I've had to add ex, touch and gencat to the installworld target.
And
> > > > : I've still not manged to complete a installworld.
> > > > :
> > > > : anybody else see this?
> > > >
> > >
> > > Strange, I just did a "make buildworld ... mergermaster"
> > > sequence and I did not need the three utilities you mention.
> >
> > Why is that strange?  You're talking about everything up to but not
> > including installworld.  Warner's talking about installworld. :-)
> >
>
> Sigh.  I said '"make buildworld ... mergemaster" sequence'.
> I assume people running -current would understand the
> use of "..." and the word "sequence" to mean
>
> make buildworld
> make buildkernel
> make installkernel
> mergemaster -p
> reboot
> make installworld
> mergemaster


H. Is mergemaster really necessary? I mean when upgrading from a fresh
4.6 install? I usually just copied the password files and rc.conf,
copied -CURRENTs etc files into /etc and copied the passwd files back. Seems
to work fine, especially because I never touch the RC scripts on my running
BSD systems.

-mg


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: aout support broken in gcc3

[Richard Tobin]

> You are blowing this out of proportion and not actually reading
> what people are proposing.  So far, the comments are about
> removing a.out support from the base compiler and offering
> a.out binutils and gcc _as ports_.

That would be sufficient for my needs (a matching gdb would be useful
too, I'm not sure if that is part of binutils).

But I don't think my concern was misplaced: having gone back through
the thread for the past couple of weeks, there were certainly phrases
like

  "drop all traces of a.out support"
  "if you need to generate new ones (?) unpack a 2.2.6 system"

with the ports solution mentioned only "if we really have to have a.out".

-- Richard (running Franz Lisp since 1983)

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: PUC_FASTINTR broken

[Poul-Henning Kamp]

In message <[EMAIL PROTECTED]>, Bruce Evans writes:
>% RCS file: /home/ncvs/src/sys/dev/puc/puc.c,v
>% Working file: puc.c
>% head: 1.14
>% ...
>% 
>% revision 1.14
>% date: 2002/09/03 11:22:13;  author: phk;  state: Exp;  lines: +3 -10
>% Fix interrupt registration:
>%
>% PUC devices live on pccard or pci so INTR_FAST is never really an option.
>% Don't try to register the interrupt as fast and don't allow the children
>% to do so either.
>% 
>
>INTR_FAST is an option for pci devices.  It was configured (not quite right)
>by the PUC_FASTINTR option, which should work just as well as the similar
>but much older CY_PCI_FASTINTR option (perfectly if the interrupt is not
>shared).

It doesn't work right if the puc manages to register the interrupt as
FAST before we realize that it is shared.

>This change blows away the support for that option without even removing
>the option from conf/options, conf/NOTES or puc.4, and without even
>noting approval of the author of the code.

I have yet to clean that fluff.

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

PUC_FASTINTR broken

[Bruce Evans]

% RCS file: /home/ncvs/src/sys/dev/puc/puc.c,v
% Working file: puc.c
% head: 1.14
% ...
% 
% revision 1.14
% date: 2002/09/03 11:22:13;  author: phk;  state: Exp;  lines: +3 -10
% Fix interrupt registration:
%
% PUC devices live on pccard or pci so INTR_FAST is never really an option.
% Don't try to register the interrupt as fast and don't allow the children
% to do so either.
% 

INTR_FAST is an option for pci devices.  It was configured (not quite right)
by the PUC_FASTINTR option, which should work just as well as the similar
but much older CY_PCI_FASTINTR option (perfectly if the interrupt is not
shared).

This change blows away the support for that option without even removing
the option from conf/options, conf/NOTES or puc.4, and without even
noting approval of the author of the code.

Bruce


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: KDE broken on CURRENT (with gcc3.2)

[Beech Rintoul]

On Tuesday 03 September 2002 09:28 pm, Michael WARDLE wrote:
> > I have the exact same problem (even with fam-2.6.9).
> > Can you post that patch?
>
> There was an error with FAM and GCC 3.1 discussed here:
> 
>
> If this is the problem you are seeing, try removing the
> "const" modifier from Scheduler.h in the FAM sources.
>
> If anyone can suggest why this is a FAM bug (rather than
> a GCC bug), I might be able to make the required changes
> in FAM.
>
> Hope this helps

That problem in the archive is exactly the same as what's happening with fam 
and gcc3.2. As for the Scheduler.h my knowledge of c++ isn't up to hacking 
that file.

Beech



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Lots of ACPI errors when booting yesterdays CURRENT

[Martin Nilsson]

Below is a trimmed dmesg from booting yesterdays CURRENT on my 
SuperMicro P3TDE6 machine (RCC/ServerWorks HE-SLt chipset).
I heven't found anything wrong with the OS, it is just that the boot 
seems to be a bit on the chatty side :-)
Is this caused by a bad BIOS setting or is there something strange with 
this board/BIOS or the acpi support in CURRENT?
I also noticed support for four acpi_cpu:s is, this as intended, the 
board only have room for two?

/Martin

Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #0: Tue Sep  3 17:41:10 CEST 2002
 [EMAIL PROTECTED]:/usr/obj/ext/FreeBSD/CURRENT/sys/EUKLIDES
Preloaded elf kernel "/boot/kernel/kernel" at 0xc04c7000.
Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04c70a8.
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 1266068553 Hz
CPU: Pentium III/Pentium III Xeon/Celeron (1266.07-MHz 686-class CPU)
   Origin = "GenuineIntel"  Id = 0x6b1  Stepping = 1
 
Features=0x383fbff
real memory  = 536805376 (524224K bytes)
avail memory = 515674112 (503588K bytes)
Pentium Pro MTRR support enabled
Using $PIR table, 10 entries at 0xc00f52e0
 ACPI-0536: *** Error: Field name [INDX] already exists in current scope
 ACPI-0536: *** Error: Field name [DATA] already exists in current scope
 ACPI-0536: *** Error: Field name [INDX] already exists in current scope
 ACPI-0536: *** Error: Field name [DATA] already exists in current scope
 ACPI-0536: *** Error: Field name [C000] already exists in current scope
 ACPI-0536: *** Error: Field name [C010] already exists in current scope
 ACPI-0536: *** Error: Field name [C020] already exists in current scope
 ACPI-0685: *** Warning: NsLookup: INDX, type 1, checking for type 11
 ACPI-0685: *** Warning: NsLookup: DATA, type 2, checking for type 11
 ACPI-0685: *** Warning: NsLookup: INDX, type 1, checking for type 11
 ACPI-0685: *** Warning: NsLookup: DATA, type 2, checking for type 11
 ACPI-0685: *** Warning: NsLookup: C000, type 8, checking for type 13
 ACPI-0685: *** Warning: NsLookup: C010, type 8, checking for type 13
 ACPI-0685: *** Warning: NsLookup: C020, type 8, checking for type 13
npx0:  on motherboard
npx0: INT 16 interface
acpi0:  on motherboard
 ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND
 ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND
 ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND
 ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND
 ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND
 ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND
 ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND
 ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND
acpi0: power button is handled as a fixed feature programming model.
Timecounter "ACPI-safe"  frequency 3579545 Hz
 ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND
--- 15 identical lines removed
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0
acpi_cpu0:  on acpi0
acpi_cpu1:  on acpi0
acpi_cpu2:  on acpi0
acpi_cpu3:  on acpi0
acpi_button0:  on acpi0
pcib1:  on acpi0
pci0:  on pcib1
pcib3:  at device 0.1 on pci0
pci1:  on pcib3
pci1:  at device 0.0 (no driver attached)
nge0:  port 0xde00-0xdeff mem 
0xfeadb000-0xfeadbfff irq 11 at device 1.0 on pci0
nge0: Ethernet address: 00:40:33:af:35:33
miibus0:  on nge0
nsgphy0:  on miibus0
nsgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
1000baseT-FDX, auto
pci0:  at device 2.0 (no driver attached)
pcm0:  port 0xdf00-0xdf3f irq 11 at device 3.0 on pci0
ahc_pci0:  port 0xd000-0xd0ff mem 
0xfeadc000-0xfeadcfff irq 5 at device 5.0 on pci0
aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
ahc_pci1:  port 0xd800-0xd8ff mem 
0xfeadf000-0xfead irq 10 at device 5.1 on pci0
aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs
fxp0:  port 0xd400-0xd43f mem 
0xfe90-0xfe9f,0xfeadd000-0xfeaddfff irq 9 at device 6.0 on pci0
fxp0: Ethernet address 00:30:48:23:0e:af
inphy0:  on miibus1
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
isab0:  port 0x580-0x58f at device 15.0 on pci0
isa0:  on isab0
pci0:  at device 15.1 (no driver attached)
pci0:  at device 15.2 (no driver attached)
pcib4:  on acpi0
pcib4: duplicate bus number 0 - not probing bus
atkbdc0:  port 0x64,0x60 irq 1 on acpi0
atkbd0:  flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0:  irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
 ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND
--- 13 identical lines removed
fdc0: cmd 3 failed at out byte 1 of 3
 ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND
--- 170 identical lines removed
fdc0: cmd 3 failed at out byte 1 of 3
 ACPI-1354: *** Error: Method execution failed, AE_N

Re: web browsers (was: Re: aout support broken in gcc3)

[David Schultz]

Thus spake Michael WARDLE <[EMAIL PROTECTED]>:
> The Gecko engine developed by the Mozilla Project, however seems
> to be very good.  I find Galeon quite nice, as it uses Mozilla's
> quite capable HTML rendering engine, has its own well designed
> GTK-based GUI, and has little of Mozilla's bloat.
> 
> Netscape Navigator <= 4.? has quite bad HTML rendering, and is
> disliked greatly by most web developers I know (not to condone
> it, but it's little wonder that many web sites are now "designed
> for Internet Explorer").  I would suggest to anybody still using
> Netscape 4 on a Unix platform that they try a replacement
> browser, whether that be Mozilla, Galeon, or something else
> (perhaps Opera or Konqueror).

I quite agree that everything fell apart with the 4.x browser
wars.  The standards-compliance aspect is improving, but at the
rate browsers seem to be going, I'm going to need another
processor just to surf the web pretty soon.  I've tried Mozilla,
Opera, and Skipstone and found intolerable shortcomings and
annoyances in each.  I'm reluctant to try Galeon because I don't
have the bloat that is Gnome anymore, and if I reinstalled it all
for the sake of a web browser, I would also seriously need a
bigger hard drive.

I may go back to Skipstone.  It's minimalistic enough that if it's
been under active development since I last used it, it's probably
pretty stable.

> If you're looking for a replacement Internet mail client, you
> might like to try Mutt, Balsa, Sylpheed, or Evolution.

I already use mutt; I don't like clicky interfaces.  I wish there
were a web browser that worked as well as mutt, and I think it's
too bad that lynx is inadequate for rendering complicated web
pages these days.

Followups, if any, to -chat, where the subscribers are used to
this topic coming up all the time...

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message