Re: Unfortunate dynamic linking for everything
On Wed, Nov 19, 2003 at 09:27:55PM -0800, Tim Kientzle wrote: Richard Coleman wrote: It seems /bin/sh is the real sticking point. There is a problem here: Unix systems have historically used /bin/sh for two somewhat contradictory purposes: * the system script interpreter * as a user shell The user shell must be dynamically linked in order to support centralized administration. I personally see no way around that. Given that many users do rely on /bin/sh, it seems that /bin/sh must be dynamically linked. There are good reasons to want the system script interpreter statically linked. Maybe it's time to separate these two functions? I would be content to have a static /sbin/sh that is used as the system script interpreter for rc scripts, etc. And /usr/bin/sh as a user shell? --Stijn -- I'm not under the alkafluence of inkahol that some thinkle peep I am. It's just the drunker I sit here the longer I get. pgp0.pgp Description: PGP signature
xl0: couldn't map interrupt w/ device apic
Hi, I just upgraded from a ~week old -CURRENT, added 'device apic' and 'device acpi' to my kernel config and rebooted. No joy -- my network card (3com xl model) disappeared. The same kernel without 'device apic' works. Message on the console is: xl0: 3Com 3c905C-TX Fast Etherlink XL port 0xb400-0xb47f mem 0xed00-0xed7f irq 22 at device 10.0 on pci2 pcib2: device xl0 requested decoded memory range 0xed00-0xed7f xl0: using memory mapped I/O xl0: couldn't map interrupt device_probe_and_attach: xl0 attach returned 6 Kernel config and complete verbose boot logs from kernels both with and without 'device apic' (otherwise unchanged) at http://sandcat.nl/~stijn/freebsd/xl2003/ I would be glad to supply other information if asked. --Stijn -- Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music. -- Kristian Wilson, Nintendo, Inc., 1989 pgp0.pgp Description: PGP signature
Re: xl0: couldn't map interrupt w/ device apic
On Tue, Nov 11, 2003 at 12:42:38PM -0500, John Baldwin wrote: On 11-Nov-2003 Stijn Hoop wrote: I would be glad to supply other information if asked. Do you have ACPI enabled? If so, a probable fix will be committed shortly. Yes I have. Turning it off made the problem disappear, but then again the 'device apic' didn't appear to be probed either. I'll wait for the fix, thanks. --Stijn -- I'm not under the alkafluence of inkahol that some thinkle peep I am. It's just the drunker I sit here the longer I get. pgp0.pgp Description: PGP signature
Re: APM not working on Dell Latitude D600
On Mon, Nov 03, 2003 at 06:37:26PM +0100, Andreas Klemm wrote: Cc'd to Stijn [EMAIL PROTECTED]. Many thanks Stijn, for making that patch available! No problem, but I'd like it if you also thank Mark Santcroos for making that patch in the first place -- I'm just the messenger here... So now I can happily confirm that this procedure works for: - Dell Latitude D600 (BIOS Revision A06) Added, along with about a dozen other submissions in my queue. Thanks to all submitters for reporting! --Stijn -- Coca-Cola is solely responsible for ensuring that people - too stupid to know not to tip half-ton machines on themselves - are safe. Forget parenting - the blame is entirely on the corporation for designing machines that look so innocent and yet are so deadly. -- http://www.kuro5hin.org/?op=displaystory;sid=2001/10/28/212418/42 pgp0.pgp Description: PGP signature
Re: Initial list of ports that fail due to -pthread
On Wed, Sep 24, 2003 at 01:49:50AM -0400, Daniel Eischen wrote: If FreeBSD wants to take the simple approach and only support one thread library in ports (-pthread == -lpthread) and not make it selectable via PTHREAD_LIBS, then its not a problem. It would be nice to be able to support all our thread libraries, but I grow weary. Just an idea (I hope this hasn't been said before in the mega thread but at least I didn't get it this way): - fix all ports to respect PTHREAD_LIBS _ON THE LINKING STAGE_ (so no global search replace, for it shouldn't be used in compile command lines) - keep '-pthread' as a compiler option, which maps to a NOOP for compiling and '-lpthread' (aka libkse) for linking - set PTHREAD_LIBS to the default value of -pthread - allow PTHREAD_LIBS to be set to something other, e.g. '-lthr', in /etc/make.conf (or the make command line) What is the problem with this approach? You get both a 'standard' -pthread knob, _and_ the ability to select your threads library using ports. Third party apps that use -pthread will work. The only case in which some work has to be done by a FreeBSD user is when they want to link a non-ported third-party app with a library other than libpthread (libkse). --Stijn -- Linux has many different distributions, meaning that you can probably find one that is exactly what you want (I even found one that looked like a Unix system). -- Mike Meyer, from a posting at [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Re: Initial list of ports that fail due to -pthread
On Wed, Sep 24, 2003 at 02:11:53AM -0400, Daniel Eischen wrote: On Wed, 24 Sep 2003, Stijn Hoop wrote: Just an idea (I hope this hasn't been said before in the mega thread but at least I didn't get it this way): - fix all ports to respect PTHREAD_LIBS _ON THE LINKING STAGE_ (so no global search replace, for it shouldn't be used in compile command lines) This sounds nice, but I don't know that there really is much difference in changes needed. Well it avoids gcc warnings in case PTHREAD_LIBS == '-lkse'. That's about the only reason I can think of to make the distinction between compiling linking. - keep '-pthread' as a compiler option, which maps to a NOOP for compiling and '-lpthread' (aka libkse) for linking That's already the case; -pthread never did anything on the compile, only the link. OK, but let's keep it that way then. Isn't the removal of -pthread that started all this? - set PTHREAD_LIBS to the default value of -pthread - allow PTHREAD_LIBS to be set to something other, e.g. '-lthr', in /etc/make.conf (or the make command line) This is already the path that ports is going down :-) Well, great. Let's go and fix some ports then, and everybody will be happy :) But if this is really the way to go, we probably need some hack to bsd.port.mk to make PTHREAD_LIBS standard because otherwise every port that needs a threads library needs to have PTHREAD_LIBS hacks. --Stijn -- Help Wanted: Telepath. You know where to apply. pgp0.pgp Description: PGP signature
Re: Text file busy
On Thu, Sep 04, 2003 at 08:02:50AM -0700, Scott M. Likens wrote: That's like trying to reinstall X while running in X. You're just asking for problems. This has worked for me many times in the past :) Of course it's on a (essentially) single user desktop, and I do a restart after portupgrade -frRa finishes... --Stijn -- I wish there was a knob on the TV to turn up the intelligence. There's a knob called `brightness', but it doesn't work. -- Gallagher pgp0.pgp Description: PGP signature
Re: DellMod
On Wed, Jun 25, 2003 at 03:44:02AM +, Sebastian Yepes [ESN] wrote: Hi all you FreeBSD dell freack.. xD I have just put in my webpaga the src of the dellmod to control the dell i8500 www.x123.info docs-i8500 - ACPI Great work, but could you please state on your page also that this module is derived from GPL sources? I would not want people to get confused. Furthermore I'd still like to find out whether the 8500 also has some sort of signature for the BIOS version, like my 4150 has. Thanks! --Stijn -- My server has more fans than Britney. -- Steve Warwick, from a posting at [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Re: acpi patch for dell laptop?
On Sun, Jun 22, 2003 at 09:35:32PM -0600, Kenneth D. Merry wrote: On Sat, Jun 21, 2003 at 00:13:10 +0200, Stijn Hoop wrote: On Fri, Jun 20, 2003 at 05:29:30PM -0400, Mike Sturdee wrote: Where can I find the latest, greatest patch that fixes this? Try this URL: http://sandcat.nl/~stijn/freebsd/dell.php and let me know if it works. It seems to work for me. The ACPI warnings about zero length buffers go away at least. Great. Do you also have working battery status now? I've got a Dell Inspirion 8500, A03 BIOS. I've added this model to the confirmed working model list on the page. I've also added the models from the rest of the reports. Thanks to all the people who submitted their report! Maybe it is time to think about an integrated kernel database of bad ACPI hardware, so that people won't have to search on the mailing lists/web to get their laptop to work? --Stijn -- Tact, n.: The unsaid part of what you're thinking. pgp0.pgp Description: PGP signature
Re: acpi patch for dell laptop?
On Mon, Jun 23, 2003 at 11:03:34AM -0600, Kenneth D. Merry wrote: On Mon, Jun 23, 2003 at 08:52:20 +0200, Stijn Hoop wrote: On Sun, Jun 22, 2003 at 09:35:32PM -0600, Kenneth D. Merry wrote: On Sat, Jun 21, 2003 at 00:13:10 +0200, Stijn Hoop wrote: http://sandcat.nl/~stijn/freebsd/dell.php It seems to work for me. The ACPI warnings about zero length buffers go away at least. Great. Do you also have working battery status now? How do I figure that out? Via the ACPI sysctls, or some other method? ACPI sysctls was the method that didn't work without the patch on my Inspiron. When I unplug the power: - hw.acpi.battery.state goes from 0 - 1 - hw.acpi.battery.time goes from 0 to 152 - hw.acpi.battery.life starts to go down That looks like correct behaviour. The battery time can't be determined when on AC power. Is there some tool that'll show battery info? I don't know of one that uses the ACPI sysctls, maybe someone else? Also, what units are the temperature in? 1/10 Kelvin I've been led to believe. HTH, --Stijn -- My server has more fans than Britney. -- Steve Warwick, from a posting at [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Re: acpi patch for dell laptop?
On Fri, Jun 20, 2003 at 05:29:30PM -0400, Mike Sturdee wrote: Where can I find the latest, greatest patch that fixes this? Try this URL: http://sandcat.nl/~stijn/freebsd/dell.php and let me know if it works. --Stijn -- Man had always assumed that he was more intelligent than dolphins because he had achieved so much... the wheel, New York, wars, and so on, whilst all the dolphins had ever done was muck about in the water having a good time. But conversely the dolphins believed themselves to be more intelligent than man for precisely the same reasons. -- Douglas Adams, The Hitchhikers Guide To The Galaxy pgp0.pgp Description: PGP signature
Re: who has the ACPI BAD PARAMETER patch?
On Wed, Jun 18, 2003 at 09:14:53PM -0700, Julian Elischer wrote: My Dell is exhibiting this error message all over the place.. At USENIX I was told someone had a fix.. http://sandcat.nl/~stijn/freebsd/dell.php As of yet still untested instructions how to patch your ASL, let me know if they work. --Stijn -- This sentence contradicts itself -- no actually it doesn't. -- Hofstadter pgp0.pgp Description: PGP signature
Re: ACPI issues on ThinkPad T21 + Dock
On Thu, Jun 19, 2003 at 09:33:41AM +0200, Eirik Oeverby wrote: - When booted with ACPI enabled (docked), the machine will at some point simply power itself off. I have seen people complaining about similiar machines powering themselves *on* after a power-off, but in my case it's the opposite. Out of nothing, with no warning (that I can see), it simply powers off. It's not suspend either, or hibernation or anything. Just a shot in the dark, but might it be heat? Most laptops/PCs turn themselves off to prevent them from overheating. Maybe ACPI doesn't turn on the fans when docked or something like that. --Stijn -- Nostalgia ain't what it used to be. pgp0.pgp Description: PGP signature
Re: ACPI Regression in -CURRENT?
On Wed, Jun 11, 2003 at 08:18:26PM +0200, Harald Hanche-Olsen wrote: + Stijn Hoop [EMAIL PROTECTED]: | Hi Thorsten, | | On Tue, Jun 10, 2003 at 03:42:18PM +0200, Thorsten Greiner wrote: | some time ago several people (including me) reported ACPI related problems | on various Dell laptops resulting in error messages of the form | | ACPI-0293: *** Warning: Buffer created with zero length in AML | | During the 5.1 release process these problems have been temporarily fixed. | | This is due to the Dell laptops having an invalid ACPI table in the BIOS. | The only way to avoid these messages is to tell FreeBSD ACPI to override | the vendor supplied table with a correct one. | | Mark Santcroos developed a patch which worked on his C640 and my Inspiron | 4150, which you can find attached. Here are the steps to use it: [...] I tried that on my Inspiron 4150 with 5.1-RELEASE. The patch failed, but only for trivial reasons like different placment of braces. Note that you have to patch the output of iasl -d, *NOT* the .asl file that acpidump generates. There is a difference although they look alike. Don't ask me what the meaning of all this is, I'm just the messenger :) So I applied it by hand and followed directions, but the warning messages did not go away. I know my efforts did *something* though, as I find this in dmesg output: Preloaded acpi_dsdt /boot/acpi_dsdt.aml at 0xc055c1cc. [...] ACPI: DSDT was overridden. ACPI-0375: *** Info: Table [DSDT] replaced by host OS That's ok, but I think you patched compiled the wrong file. I *know* it works because I also have an Inspiron 4150. Also, I still cannot suspend the machine: acpiconf -s number results in a variety of interesting behaviour, always ending with the machine in a useless state (except acpiconf -s 5, which does what it should - like halt -p). acpiconf -s 4 works, now that I have reinstalled the laptop with a suspend partition as the first primary partition. You need the Dell utility mks2d.exe for this, available somewhere on the Dell website. Actually, acpiconf -s 3 seems to almost work: The screen goes blank, and the machine turns itself off - only to turn back on immediately, but with the screen remaining blank. So I hit Fn-F8 a couple of times, and lo and behold the screen is alive again and the machine is responsive once more. I did this from a console, but when I do Ctrl-Alt-F9 the X server is hosed: Wrong colours, garbage in the top of the screen, and zero response to any keypresses. According to Mark, this actually should work from within X -- something to do with DPMS. I haven't gotten around to testing it after my reinstall though (*cough*Zelda:WW*cough* :) Can you suspend yours? Any more clever tricks? (Hmm, I suppose we should discuss this on -mobile, but since the thread started here...) The ACPI thing got more coverage on -current, but the suspend stuff is probably -mobile topic, yeah :) HTH, --Stijn -- Diane, 2:15 in the afternoon, November 14. Entering town of Twin Peaks. Five miles south of the Canadian border, twelve miles west of the state line. Never seen so many trees in my life. As W.C. Fields would say, I'd rather be here than Philadelphia. -- Special Agent Dale Cooper, Twin Peaks pgp0.pgp Description: PGP signature
Re: ACPI Regression in -CURRENT?
On Thu, Jun 12, 2003 at 12:46:32AM +0200, Harald Hanche-Olsen wrote: + Stijn Hoop [EMAIL PROTECTED]: | I tried that on my Inspiron 4150 with 5.1-RELEASE. The patch failed, | but only for trivial reasons like different placment of braces. | | Note that you have to patch the output of iasl -d, *NOT* the .asl file | that acpidump generates. There is a difference although they look alike. Aha. But the diff you included clearly indicated it was a patch for insp4150.asl. When I told patch to patch insp4150.dsl instead, using your patch, it applied cleanly, and moreover the fix now works to the extent that I don't get those error messages anymore. To be precise, I followed your exact instructions with this difference: # patch insp4150.dsl insp4150.patch I'm sorry, like I wrote the earlier procedure was typed off of the top of my head, and wasn't verified. I should have done that. | Actually, acpiconf -s 3 seems to almost work: [...] | | According to Mark, this actually should work from within X -- | something to do with DPMS. Still doesn't for me. Same result. Maybe I should learn what DPMS stands for. Something with display power management. But maybe it's something else then. Glad to hear the ACPI messages got sorted out at least :) --Stijn -- I wish there was a knob on the TV to turn up the intelligence. There's a knob called `brightness', but it doesn't work. -- Gallagher pgp0.pgp Description: PGP signature
Re: ACPI Regression in -CURRENT?
On Tue, Jun 10, 2003 at 11:38:18PM -0700, Terry Lambert wrote: Stijn Hoop wrote: This is due to the Dell laptops having an invalid ACPI table in the BIOS. The only way to avoid these messages is to tell FreeBSD ACPI to override the vendor supplied table with a correct one. Alternately, since Microsoft works just peachy with this thing, it's somewhat apparent that the Derefof() and Refof() can be implied by the types of the values being passed, Not that I can read one bit of ASL, but I fail to see how this is apparent. If it is, is it still as apparent to an interpreter? and the ACPI table parsing code should be changed to work like Microsoft's does, at least until FreeBSD displaces the 70% marketshare and can dictate defacto implementation standards, where Intel can't. That would be great except probably nobody knows why this laptop works with Windows without a hitch -- it could very well be that the Dell drivers implement their own battery management and completely ignore the fact that it's broken in their ACPI table. Yeah, I know that it's better to be correct than Microsoft compatible, but it's also better to work with hardware as shipped by vendors. Unless you think you can get Dell to rev their BIOS... That would be great, but I don't have the contacts at Dell. Anybody reading this who does? --Stijn -- This sentence contradicts itself -- no actually it doesn't. -- Hofstadter pgp0.pgp Description: PGP signature
Re: ACPI Regression in -CURRENT?
Hi Thorsten,
On Tue, Jun 10, 2003 at 03:42:18PM +0200, Thorsten Greiner wrote:
some time ago several people (including me) reported ACPI related problems
on various Dell laptops resulting in error messages of the form
ACPI-0293: *** Warning: Buffer created with zero length in AML
During the 5.1 release process these problems have been temporarily fixed.
At least I have a 5.1-BETA kernel built on June 1st which does not exhibit
these problems.
Today I tried a 5.1-CURRENT kernel and found that these problems have
reappeared. This made me wonder wether this is an intended behaviour or a
regression.
This is due to the Dell laptops having an invalid ACPI table in the BIOS.
The only way to avoid these messages is to tell FreeBSD ACPI to override
the vendor supplied table with a correct one.
Mark Santcroos developed a patch which worked on his C640 and my Inspiron
4150, which you can find attached. Here are the steps to use it:
# cd /usr/ports/devel/acpicatools make install
# acpidump -o insp4150.dsdt insp4150.asl
# iasl -d insp4150.dsdt
# patch -p0 insp4150.patch
# iasl insp4150.dsl
# cp DSDT.aml /boot/acpi_dsdt.aml
# vi /boot/loader.conf
add the lines
acpi_dsdt_load=YES
acpi_dsdt_name=/boot/acpi_dsdt.aml
Then reboot.
You might need to improvise, and/or edit the patch headers to specify the file
to patch. I'm recalling this procedure from memory / older emails, but this
should be the gist of it.
HTH,
--Stijn
--
An Orb is for life, not just for Christmas.
--- insp4150_orig.asl Wed May 14 02:07:27 2003
+++ insp4150.aslTue May 27 22:18:14 2003
@@ -120,9 +120,9 @@
Method (SXX5, 2, NotSerialized)
{
-If (LLess (Arg1, SizeOf (Arg0)))
+If (LLess (Arg1, SizeOf (DerefOf(Arg0
{
-CreateByteField (Arg0, Arg1, SX20)
+CreateByteField (DerefOf(Arg0), Arg1, SX20)
SXX6 (0x7C, SX20)
}
}
@@ -133,16 +133,16 @@
Store (0x00, Local0)
While (LLess (Local0, SXX2))
{
-SXX5 (SXX0, Local0)
+SXX5 (RefOf(SXX0), Local0)
Increment (Local0)
}
}
Method (SXX8, 2, NotSerialized)
{
-If (LLess (Arg1, SizeOf (Arg0)))
+If (LLess (Arg1, SizeOf (DerefOf (Arg0
{
-CreateByteField (Arg0, Arg1, SX20)
+CreateByteField (DerefOf(Arg0), Arg1, SX20)
Store (SXX6 (0x7D, 0x00), SX20)
}
}
@@ -153,7 +153,7 @@
While (LLess (Local0, SXX3))
{
Add (SXX2, Local0, Local1)
-SXX8 (SXX0, Local1)
+SXX8 (RefOf (SXX0), Local1)
Increment (Local0)
}
}
@@ -217,9 +217,9 @@
Method (SX43, 2, NotSerialized)
{
-If (LLess (Arg1, SizeOf (Arg0)))
+If (LLess (Arg1, SizeOf (DerefOf(Arg0
{
-CreateByteField (Arg0, Arg1, SX20)
+CreateByteField (DerefOf(Arg0), Arg1, SX20)
Store (SX40 (), SX20)
}
}
@@ -238,7 +238,7 @@
{
Store (SX40 (), Local0)
Name (SX23, Buffer (Local0) {})
-SX44 (SX23, Local0)
+SX44 (Refof(SX23), Local0)
Return (SX23)
}
@@ -277,7 +277,7 @@
SX30 (Arg0)
SX11 ()
Name (PGET, Buffer (SXX3) {})
-SX44 (PGET, SXX3)
+SX44 (RefOf(PGET), SXX3)
SX12 ()
Return (PGET)
}
pgp0.pgp
Description: PGP signature
Re: FBSD 5.1b2 Inst. Results on Dell i8500
On Tue, May 27, 2003 at 10:28:32PM +0200, Mark Santcroos wrote: On Thu, May 22, 2003 at 11:05:03PM +0200, Mark Santcroos wrote: The same here, that's what I mentioned earlier, that I need to investigate this. Hope to have that fixed before 'de haan kraait' tomorrow morning ;-) Can you send me your whole asl, I'm curious how close it is to mine. Hrm, a bit later than anticipated, got ill after skipping too many nights, had to take a break :-) However, with the following patch, fdc, sio, and ppc attach under acpi instead of isa again! Great work! I'm off to test this right now! With a stock kernel and patched dsdt I have a fully working system again. All Dell laptop users with problems might want to give this a look as at least Stijn's Inspirion 8500 has exactly the same dsdt as mine (Latitude C640). It's in Inspiron 4150 FWIW, but there is enough reason to believe that most Dell laptops use the same code, yes. I'll report back ASAP. --Stijn -- Oh good, my dog found the chainsaw. -- Lilo, Disney's Lilo Stitch pgp0.pgp Description: PGP signature
Re: FBSD 5.1b2 Inst. Results on Dell i8500
On Tue, May 27, 2003 at 10:55:11PM +0200, Stijn Hoop wrote: On Tue, May 27, 2003 at 10:28:32PM +0200, Mark Santcroos wrote: With a stock kernel and patched dsdt I have a fully working system again. All Dell laptop users with problems might want to give this a look as at least Stijn's Inspirion 8500 has exactly the same dsdt as mine (Latitude C640). I'll report back ASAP. Success on my Inspiron 4150. After unsuccesfully trying to apply the patch to the asl dumped by acpidump I got to my senses and tried to apply it to the iasl disassembled version. That worked in one shot. Thanks for all the hard work, Mark! --Stijn -- In the force if Yoda's so strong, construct a sentence with words in the proper order then why can't he? pgp0.pgp Description: PGP signature
Re: libthr and 1:1 threading.
On Mon, Mar 31, 2003 at 10:54:45PM -0500, Jeff Roberson wrote: I have commited libthr. To try this out you'll need to do the following I know very very little about threads, but I'm interested as to what the purpose is of this library. Is there a document available somewhere that describes the relationships between this, KSE, libc_r, pthreads, the Giant-unwinding-make-SMP-work-better project and some of the other threads and SMP related libraries and terminology? --Stijn -- ...I like logs. They give me a warm fuzzy feeling. I've been known to keep logs for 30 months at a time (generally when I thought I was rotating them daily, but was actually rotating them once a month). -- Michael Lucas, in Big Scary Daemons article 'Controlling Bandwidth' pgp0.pgp Description: PGP signature
Re: mdmfs broken?
On Wed, Mar 05, 2003 at 05:36:45PM +0100, Ralf S. Engelschall wrote:
In article [EMAIL PROTECTED] you wrote:
What's the correct syntax in 5-CURRENT to have a memory disk for /tmp
in your /etc/fstab?
[...]
Create a symlink:
lrwxr-xr-x 1 root wheel 5 Feb 13 13:28 /sbin/mount_mfs - mdmfs
and use in /etc/fstab something like:
md0 /tmp mfs rw,-s128m,noatime,nosuid,nodev 0 0
Thanks! Any reason why there is no {sym,hard}link by default? The
manpage even mentions the compat-behaviour:
COMPATIBILITY
Full compatibility is enabled with the -C flag, or by starting mdmfs with
the name mount_mfs or mfs (as returned by getprogname(3)).
--Stijn
--
Nostalgia ain't what it used to be.
pgp0.pgp
Description: PGP signature
md disk not unmountable
Hi, I got an 'md' error while doing a 'make release' on a -CURRENT machine; the release process couldn't unmount the boot floppy staging area from /mnt. Testing by hand, I experienced the following: Script started on Thu Mar 6 16:28:31 2003 [EMAIL PROTECTED] ~ mount | grep /mnt /dev/md1c on /mnt (ufs, local) [EMAIL PROTECTED] ~ sudo umount /mnt umount: unmount of /mnt failed: Invalid argument [EMAIL PROTECTED] ~ sudo mdconfig -l -u 1 md1 vnode 2880 KBytes [EMAIL PROTECTED] ~ sudo mdconfig -l md1 md0 [EMAIL PROTECTED] ~ sudo mdconfig -l -u 0 md0 swap262144 KBytes [EMAIL PROTECTED] ~ sudo mdconfig -d -u 1 mdconfig: ioctl(/dev/mdctl): Device busy [EMAIL PROTECTED] ~ df -h /mnt FilesystemSize Used Avail Capacity Mounted on /dev/ad0s1a 252M78M 154M34%/ Script done on Thu Mar 6 16:31:42 2003 I think something is confused as to what is on /mnt somewhere. Restarting the release (with 'make rerelease') successfully completed, using md2. Unfortunately I don't have the exact log of the first release build handy. This is all on FreeBSD 5.0-CURRENT #1: Thu Mar 6 10:54:17 CET 2003 [EMAIL PROTECTED]:/local/freebsd/CURRENT/obj/local/freebsd/CURRENT/src/sys/JMWP424 Any clues? --Stijn -- The rain it raineth on the just And also on the unjust fella, But chiefly on the just, because The unjust steals the just's umbrella. pgp0.pgp Description: PGP signature
Re: md disk not unmountable
On Thu, Mar 06, 2003 at 04:35:53PM +0100, Stijn Hoop wrote: I got an 'md' error while doing a 'make release' on a -CURRENT machine; the release process couldn't unmount the boot floppy staging area from /mnt. [snip] I think something is confused as to what is on /mnt somewhere. Restarting the release (with 'make rerelease') successfully completed, using md2. Doh, found a first clue: [EMAIL PROTECTED] /local/freebsd/dist sudo umount mnt umount: mnt not found in mount table, unmounted it anyway [EMAIL PROTECTED] /local/freebsd/dist sudo umount dev umount: dev not found in mount table, unmounted it anyway So something *was* confused but I was too -- I should have tried the chrootdir also of course :( Anyway, how can a mount become 'lost', like what happened here? --Stijn -- Man had always assumed that he was more intelligent than dolphins because he had achieved so much... the wheel, New York, wars, and so on, whilst all the dolphins had ever done was muck about in the water having a good time. But conversely the dolphins believed themselves to be more intelligent than man for precisely the same reasons. -- Douglas Adams, The Hitchhikers Guide To The Galaxy pgp0.pgp Description: PGP signature
mdmfs broken?
Hi, What's the correct syntax in 5-CURRENT to have a memory disk for /tmp in your /etc/fstab? It seems that mdmfs is broken somehow, or else I'm not reading the instructions right: FreeBSD pcwin352.win.tue.nl 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Tue Mar 4 17:32:19 CET 2003 [EMAIL PROTECTED]:/local/freebsd/CURRENT/obj/local/freebsd/CURRENT/src/sys/PCWIN352 i386 Script started on Wed Mar 5 15:22:20 2003 pcwin352# mdmfs md /tmp mdmfs: mdconfig (attach) exited with error code 1 pcwin352# mdmfs md0 /tmp mdmfs: mdconfig (attach) exited with error code 1 pcwin352# mdconfig -a -t swap -s 256M md0 pcwin352# newfs -U md0 /dev/md0: 256.0MB (524288 sectors) block size 16384, fragment size 4096 using 4 cylinder groups of 64.02MB, 4097 blks, 4224 inodes. with soft updates super-block backups (for fsck -b #) at: 32, 131136, 262240, 393344 pcwin352# mount /dev/md0 /tmp pcwin352# chmod 1777 /tmp pcwin352# exit Script done on Wed Mar 5 15:23:03 2003 So by hand it works. Suggestions? --Stijn -- From the moment I picked your book up until I laid it down I was convulsed with laughter. Some day I intend reading it. -- Groucho Marx pgp0.pgp Description: PGP signature
GEOM problems when installing 5.0-RELEASE
Hi all, please point me to the right list if this isn't the right one, but I'm running into what appears to be GEOM trouble when installing 5.0-RELEASE. [btw, the below uses MSDOS terminology for partitions, sorry] The setup is a fairly straight athlon 700 with IDE 2 harddisks, a primary master of 13 G and primary slave of 6 G. BIOS detects both fine, I have Windows XP installed in the first primary partion of ad0, and an extra FAT logical partition in the extended partion on the same drive, resulting in ad0s1, ad0s2 and ad0s5. This disk is fine. The other however, is not. I first tried to install FreeBSD when I still had a primary FAT partition with Win98 on it. Booting from floppy doing an FTP install went fine, but on reboot, the kernel couldn't mount the root partition. Even worse, after rebooting in XP, it turned out that my Win98 partition was unrecognizable (fortunately nothing was lost). I thought it might be due to my 'unusual' (for me) setup of having 2 primary partitions, 1 win98 and 1 BSD, so I tried again, this time allocating the whole 6 G disk to BSD. Retried the install, once again went fine until the reboot, when the kernel still couldn't find the root partition. Handtyping ad1s1 didn't work, ad1 wasn't listed in the boot devices list, no go. I booted from floppy once again and tried the fixit floppy. And I think I found out where the problem was (forgive any typos, this is transcribed as I don't have a serial console): Fixit# ls -l /dev/ad* crw-r- 1 root operator4, 4 Mar 3 20:07 /dev/ad0 crw-r- 1 root operator4, 5 Mar 3 20:07 /dev/ad0s1 crw-r- 1 root operator4, 6 Mar 3 20:07 /dev/ad0s2 crw-r- 1 root operator4, 8 Mar 3 20:07 /dev/ad0s5 crw-r- 1 root operator4, 7 Mar 3 20:07 /dev/ad1 There is no ad1s1 device! No wonder the kernel can't find it's root if it doesn't detect the correct partition. Am I doing something wrong here? Unfortunately I'm not able to get at sysctl output so I can't find GEOM debugging output there. Is there any way I can provide more information on this? Has anyone else run into this? --Stijn -- Fairy tales do not tell children that dragons exist. Children already know dragons exist. Fairy tales tell children the dragons can be killed. -- G.K. Chesterton pgp0.pgp Description: PGP signature
Re: HEADS UP: cvsup cvs-supfile users!
On Tue, Mar 04, 2003 at 11:10:45AM -0800, Peter Wemm wrote: Anybody who uses the cvs-supfile example to get the repository should add cvsroot-all to their supfile. This is in addition to src-all, ports-all, doc-all etc. This is *ONLY* for the folks getting the CVS ,v files via cvsup. If you use tag=. or tag=RELENG_4, then you are not affected by this. I have updated cvs-supfile in -current but not RELENG_4 yet. Just to be doubly sure, this goes for cvsup mirrors as well, I assume? So I have to edit /usr/local/etc/cvsup/supfile to include it? If so, then you might want to update ports/net/cvsup-mirror/files/supfile also. --Stijn -- An adult is a child who has more ethics and morals, that's all. -- Shigeru Miyamoto pgp0.pgp Description: PGP signature
Re: HEADS UP: cvsup cvs-supfile users!
On Tue, Mar 04, 2003 at 11:45:18AM -0800, Peter Wemm wrote: No, people who use cvs-all are already getting this stuff. If you use the cvsup-mirror port yourself, you do not need to change anything either. Mirrors who use cvs-all (official and unofficial) do not need to change anything. OK, thanks for the clarification. --Stijn -- ...I like logs. They give me a warm fuzzy feeling. I've been known to keep logs for 30 months at a time (generally when I thought I was rotating them daily, but was actually rotating them once a month). -- Michael Lucas, in Big Scary Daemons article 'Controlling Bandwidth' pgp0.pgp Description: PGP signature
Re: SCM Microsystems Inc. eUSB SmartMedia Adapter
On Wed, Dec 11, 2002 at 07:38:11PM +0100, Bernd Walter wrote: On Wed, Dec 11, 2002 at 07:03:36PM +0100, Stijn Hoop wrote: On Wed, Dec 11, 2002 at 06:12:21PM +0100, Bernd Walter wrote: On Wed, Dec 11, 2002 at 08:58:12AM +0100, Stijn Hoop wrote: On Tue, Dec 10, 2002 at 10:13:49PM -0500, Brad Hughes wrote: Try to remove device ugen from your kernel; it is a bit agressive when 'claiming' USB devices. I had the same problem with an USB gamepad and uhid devices. This shouldn't be possible. Can you show an example when this happens? It used to happen with my Thrustmaster Firestorm Wireless gamepad. At the time I had both uhid ugen in my kernel, it also happened when I used uhid as a loadable module. It finally worked when I removed ugen from my kernel configuration file, and used the uhid module. I never tested to see whether using uhid in a kernel configuration file (instead of a module) worked because I was happy to get it to play nicely. If the device is attached with only ugen available then of course ugen gets it. When you load a module later, then the decision about the driver for that device has already been made. Yes I understand. But I don't see how this could happen if you already have uhid in the kernel. Well I thought it did -- but upon retesting with an up-to-date -CURRENT, it works now. Sorry for the false alarm. --Stijn -- The rain it raineth on the just And also on the unjust fella, But chiefly on the just, because The unjust steals the just's umbrella. msg48643/pgp0.pgp Description: PGP signature
Re: SCM Microsystems Inc. eUSB SmartMedia Adapter
On Wed, Dec 11, 2002 at 06:12:21PM +0100, Bernd Walter wrote: On Wed, Dec 11, 2002 at 08:58:12AM +0100, Stijn Hoop wrote: On Tue, Dec 10, 2002 at 10:13:49PM -0500, Brad Hughes wrote: Try to remove device ugen from your kernel; it is a bit agressive when 'claiming' USB devices. I had the same problem with an USB gamepad and uhid devices. This shouldn't be possible. Can you show an example when this happens? It used to happen with my Thrustmaster Firestorm Wireless gamepad. At the time I had both uhid ugen in my kernel, it also happened when I used uhid as a loadable module. It finally worked when I removed ugen from my kernel configuration file, and used the uhid module. I never tested to see whether using uhid in a kernel configuration file (instead of a module) worked because I was happy to get it to play nicely. I can try and test some more later. BTW this was all on 4-STABLE (4.6-STABLE / 4.7-RC IIRC), maybe that matters? --Stijn -- Nostalgia ain't what it used to be. msg48532/pgp0.pgp Description: PGP signature
Re: SCM Microsystems Inc. eUSB SmartMedia Adapter
On Tue, Dec 10, 2002 at 10:13:49PM -0500, Brad Hughes wrote: Hey everyone, I have a question, when i try to plugin my eUSB SmartMedia USB adapter, umass doesnt recognize it. Darius over at #freebsdhelp@efnet suggested me to send a mail to the questions/current mailing lists. Thanks to him :). When i plug in my Adapter, in my dmesg it states: ugen0: SCM Microsystems Inc. eUSB SmartMedia Adapter, rev 1.10/2.18, addr 2 When i unplug it, it reports: ugen0: at uhub0 port 1 (addr 2) disconnected ugen0: detached Any suggestions? Any help is appreciated, thanks in advance. Try to remove device ugen from your kernel; it is a bit agressive when 'claiming' USB devices. I had the same problem with an USB gamepad and uhid devices. Using modules for the usb stuff makes testing things like this easier, I've found. --Stijn -- The rain it raineth on the just And also on the unjust fella, But chiefly on the just, because The unjust steals the just's umbrella. msg48508/pgp0.pgp Description: PGP signature
Re: cvs commit: src/sys/fs/specfs spec_vnops.c
On Mon, Nov 04, 2002 at 08:48:01AM +0100, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Doug Barton writes: Kirk, I'm adding a bunch of people to the list who were involved in a thread on -current on this topic. I also tried this change and noticed that things did seem a tiny bit snappier (although my system is slow enough that it could have just been my imagination). All things considered, I think we should just pla to leave it this way for 5.0-R. Until now people were used to wait for fsck to finish, at least now they can do something in while it runs. Well... like I indicated earlier in the thread on -CURRENT, things were definitely *slow*. I also said I would try to provide benchmarks if people told me how to do that (and what to time). In any case, as a rough measurement, starting X on -CURRENT took about 2-3 seconds vs. about half a second on -STABLE on the exact same hardware. It was even measurable on a simple 'ls' in a large directory. I think if this is left in as is, people 'new' to FreeBSD will think it's dead slow, and move on elsewhere. I belive GEOM provides the framework where we can properly tag I/O requests with a priority, propagate that priority down to the device drivers and act accordingly in the disksort disk-scheduling code. If that's the case, I'd like to see it in 5.0R. That would allow us to address not only the bgfsck but also things like silly-seek-syndrome and other sub-optimal issues in our current I/O system. That would be great. --Stijn -- The right half of the brain controls the left half of the body. This means that only left handed people are in their right mind. msg46035/pgp0.pgp Description: PGP signature
Re: cvs commit: src/sys/fs/specfs spec_vnops.c
On Mon, Nov 04, 2002 at 09:49:06AM +0100, Stijn Hoop wrote: On Mon, Nov 04, 2002 at 08:48:01AM +0100, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Doug Barton writes: Kirk, I'm adding a bunch of people to the list who were involved in a thread on -current on this topic. I also tried this change and noticed that things did seem a tiny bit snappier (although my system is slow enough that it could have just been my imagination). All things considered, I think we should just pla to leave it this way for 5.0-R. Until now people were used to wait for fsck to finish, at least now they can do something in while it runs. Well... like I indicated earlier in the thread on -CURRENT, things were definitely *slow*. I also said I would try to provide benchmarks if people told me how to do that (and what to time). In any case, as a rough measurement, starting X on -CURRENT took about 2-3 seconds vs. about half a second on -STABLE on the exact same hardware. It was even measurable on a simple 'ls' in a large directory. I think if this is left in as is, people 'new' to FreeBSD will think it's dead slow, and move on elsewhere. Whoops, monday morning brain fart. Ignore my previous mail, I didn't get the fact that the switch defaulted to *off*. Am I reading it correctly now, that the ioslow sleep is therefore also not enabled by default? --Stijn -- The most reliable proof that there are extraterrestrial intelligent lifeforms out there is that nobody actually tries to get in contact with us. -- Dirk Mueller msg46045/pgp0.pgp Description: PGP signature
Re: speed of -CURRENT [was: questions about the state of current]
On Wed, Oct 30, 2002 at 07:48:14AM -0500, Alexander Kabaev wrote:
I am experiencing a really noticable slower startup time on my very
recent-CURRENT laptop for almost all programs. The problem seems to be
in getting info in the cache, because it disappears when I start the
same program again.
This almost certainly is caused by the 'ioslow' addition to
specfs_vnops.c. Find a block in specfs_strategy function which goes into
tsleep for niced processes and comment it out. Let us know if that helps
:)
Yes, that's it. -CURRENT actually feels snappier than -STABLE now :)
Below is the diff that I used. Will something other than I/O for
niced processes break using this?
Thanks!
--Stijn
--- spec_vnops.c.orig Mon Oct 28 08:07:49 2002
+++ spec_vnops.cWed Oct 30 14:22:01 2002
-530,17 +530,19
struct mount *mp;
int error;
struct cdevsw *dsw;
- struct thread *td = curthread;
+/* struct thread *td = curthread; */
/*
* Slow down disk requests for niced processes.
*/
+/* XXX: per Alexander Kabaev mail 2002/10/30 07:48 -5
if (td td-td_ksegrp-kg_nice 0) {
mtx_lock(strategy_mtx);
msleep(strategy_mtx, strategy_mtx,
PPAUSE | PCATCH | PDROP, ioslow,
td-td_ksegrp-kg_nice);
}
+*/
bp = ap-a_bp;
vp = ap-a_vp;
if (bp-b_iocmd == BIO_WRITE) {
msg45645/pgp0.pgp
Description: PGP signature
Re: Please install and test the GDB 5.2 port
Sorry to step in but this jumped out at me and might save you a bit of time: On Thu, Jun 27, 2002 at 07:00:13AM -0700, Mark Peek wrote: At 7:50 AM +0200 6/27/02, Joerg Wunsch wrote: As Mark Peek wrote: Hmm, so how to debug a kernel coredump? You need to update your gdb52 port. I can't find a newer one in CVS: j@uriah 85% pkg_info -I gdb-\* gdb-5.2_2 GNU GDB 5.2 developmental snapshot Very odd...here's what I get on my -current system: # pkg_info -I gdb-\* gdb-5.2_2 GNU GDB 5.2 developmental snapshot current# gdb -k GNU gdb 4.18 ^^ you're probably running /usr/bin/gdb instead of /usr/local/bin/gdb. HTH, --Stijn -- This sentence contradicts itself -- no actually it doesn't. -- Hofstadter msg40039/pgp0.pgp Description: PGP signature
Re: cdrecord for ATAPI burners available..
On Tue, Mar 19, 2002 at 03:58:01PM +0100, Søren Schmidt wrote: It seems Thomas Quinot wrote: Le 2002-03-19, Søren Schmidt écrivait : ftp://freebsd.dk/pub/ATA/cdrtools-1.10-ATA.tgz On -stable it needs the ATA driver update I did a yesterday. It does *not* need CAM or the atapicam patches, it uses the ATA driver directly.. Alternatively, for those who'd like to use stock issue cdr tools (or any other tool that manipulates CAM devices) there also is a new release of the ATAPI/CAM patches at http://www.cuivre.fr.eu.org/~thomas/atapicam/ that resolves the 'hang at boot' issue reported by several testers with Toshiba units. Oh yes, I forgot, there is also a cdrdao on: ftp://freebsd.dk/pub/ATA/cdrdao-1.1.5-ATA.tgz Again no CAM or atapicam needed :) You and Thomas rock! Any chance of a cdparanoia-ATA.tgz ? :) --Stijn -- Nostalgia ain't what it used to be. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cdrecord for ATAPI burners available..
On Tue, Mar 19, 2002 at 04:28:27PM +0100, Søren Schmidt wrote: It seems Stijn Hoop wrote: You and Thomas rock! Any chance of a cdparanoia-ATA.tgz ? :) No idea what it is, I cant seem to find it in ports either... It's a CDDA extractor, much like cdda2wav. It has much better error correction though. It's only been ported to NetBSD, but they aren't using CAM, are they? So it's not going to be a straight port I'm afraid :( URL ? http://www.xiph.org/paranoia/ I admit that it's a bit old, but it always rips better on a Linux box then any other CDDA extractor I could find. Does it work on FreeBSD already with CAM or ? Nope (afaik), see above. --Stijn -- The very powerful and the very stupid have one thing in common. Instead of altering their views to fit the facts, they alter the facts to fit their views ... which can be very uncomfortable if you happen to be one of the facts that needs altering. -- Doctor Who, Face of Evil msg36347/pgp0.pgp Description: PGP signature
Re: ports/34908: libpng port makes bad dynamic library on -CURRENT
Hi -current, I ventured into this brave new world a few days ago and ran into this very problem. Alexander's patch (along with a make install in /usr/src/gnu/usr.bin/binutils) fixed it, as advertised. Maybe this can now be committed? --Stijn -- Help Wanted: Telepath. You know where to apply. msg34978/pgp0.pgp Description: PGP signature
Re: Patch sets to date and timing tests with Giant out of userret.
On Tue, Feb 19, 2002 at 04:12:48PM +0100, Dag-Erling Smorgrav wrote: I'm working on porting the latest beta release of Subversion, which does all that and more, and has much better diff support than Perforce. After using Perforce for my PAM work, I've come to the conclusion that although it's a big step forward from CVS in one direction (change management branching), it's a big step backward in almost every other direction. I can't comment on Perforce, but I can add that I liked subversion even when it wasn't self hosting; it appears promising to say the least. As for your port, there already is a /usr/ports/devel/subversion; it points you to the port skeleton for version r909. Is yours better/different? --Stijn -- I'm not under the alkafluence of inkahol that some thinkle peep I am. It's just the drunker I sit here the longer I get. msg34924/pgp0.pgp Description: PGP signature
Re: sound/pci/ich drvr hang on Dell OptiPlex 150
Hi, On Fri, Dec 14, 2001 at 12:15:54PM +0530, Bruce Montague wrote: Two solid problems occur with the sound/pci/ich driver for the ICH2 (Intel 82801BA I/O Controller Hub) on Dell Optiplex 150 PCs. One problem (a fatal hang) occurs under 4.4-RELEASE, 4.4-STABLE, and 5.0-CURRENT (as of yesterday). I have a temporary fix for the fatal hang, but don't claim to understand the Intel ICH2 enough to know if it is universal (e.g., the right thing.). I doubt it's comprehensive enough. Problems: 1) Systems hang on boot (perhaps half the time) due to a never-cleared interrupt condition. The audio device sometimes comes up with an initial error condition (X_SR_DCH); this interrupt is never dismissed/cleared by the ich_intr() interrupt handler; ich_intr() livelocks (runs constantly). I have a quick ugly work-around fix (listed below) for this. Maybe the real fix would involve the device init routine. Cool! This may be a fix for PR kern/29769. 2) Microphone input doesn't work, the error pcm0: record interrupt timeout, channel dead always occurs (it doesn't look like any channel other than PCM_PLAY is ever even triggered in the 4.4-RELEASE or 4.4-STABLE code). The microphone works OK in 5.0-CURRENT. This problem is just due to the phase-in of the features in the sound/pci/ich driver code and appears to be expected behavior when looked at long enough... I haven't tested my microphone input yet. The hang-on boot problem is potentially serious because it is difficult to identify and precludes unattended reboot (in normal use one can just attempt reboot until the device comes up without the DCH error, i.e., clean). Indeed. However nobody seems to mind much (Jonathan Lemon pointed out an errata in the ICH2/ICH2-M specification, which was probably the cause; however I don't understand the code enough to fix the bug). Here is how I kludge/fixed the hang on boot problem (again, I'm not claiming this is the right fix, but the systems have never hung on boot with it in, and without it they hang about half to a third the time). I'll try your fix on monday (4.4-STABLE). --Stijn -- Q: Why is Batman better than Bill Gates? A: Batman was able to beat the Penguin. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: SCSI-IDE
Just curious, but how is the patch progressing? Can I try this out on a -STABLE system somehow? --Stijn -- I used to think I was indecisive, but now I'm not so sure. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -CURRENT and XFree86 4.0.2 problem
On Tue, Jan 23, 2001 at 10:12:00AM +0700, John Indra wrote: Running -CURRENT with world and kernel of: Thu Jan 18 13:04:05 JAVT 2001 Blew away all /usr/X11R6 and /usr/local to have fresh ports on my system. Then, I install XFree86-4.0.2_5. Now, whenever I enter X (using startx) and try to go to console (Ctrl+Alt+Fx) and then try to get back to X (Alt+F9), X died :( I suspect (from the error log) that this has something to do with Intel 810 chipset and -CURRENT agp module. FWIW, I have the same problem with a -STABLE from jan. 20th. So the bug is probably also in the -STABLE agp module, or else it is XFree86-4.0.2_5 (I also blew away /usr/local and /usr/X11R6 before installing it). --Stijn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildkernel broken?
On Thu, Sep 21, 2000 at 10:00:59AM -0400, Donn Miller wrote:
On Thu, 21 Sep 2000, Neil Blakey-Milner wrote:
On Thu 2000-09-21 (08:48), Donn Miller wrote:
An example of what I get when I try to do a make buildkernel. I have set
KERNEL=CUSTOM in /etc/make.conf, so I should be alright there.
{standard input}:2342: Error: Subtraction of two symbols in different sections
".data" {.data section} - "KERNBASE" {*UND* section} at file address 928.
Do you have a populated /usr/obj? (ie, with nm)
I've been doing "make buildkernel installkernel" in /usr/src without doing
a "make buildworld" first. Is this OK? I guess the buildkernel created a
/usr/obj, but I deleted it and tried buildkernel again with the same
results.
- Donn
FWIW, I have the same problem on 4.1-STABLE cvsupped 10 mins ago from
cvsup.nl.freebsd.org.
I noticed these lines in the build log:
...
cd /usr/obj/usr/src/sys/PCWIN002; MAKEOBJDIRPREFIX=/usr/obj
COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin
LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib
OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec
PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.00503 DESTDIR=/usr/obj/usr/src/i386
INSTALL="sh /usr/src/tools/install.sh"
PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
MACHINE=i386 make KERNEL=kernel depend
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/../include -D_KERNEL -include
opt_global.h -elf -mpreferred-stack-boundary=2 /usr/src/sys/i386/i386/genassym.c
sh /usr/src/sys/kern/genassym.sh genassym.o assym.s
nm: could not exec elf/nm in /usr/obj/usr/src/i386/usr/libexec: No such file or
directory
rm -f param.c
cp /usr/src/sys/conf/param.c .
perl5 /usr/src/sys/kern/vnode_if.pl -h /usr/src/sys/kern/vnode_if.src
...
Especially:
nm: could not exec elf/nm in /usr/obj/usr/src/i386/usr/libexec: No such file or
directory
Which is quite correct since I blew away /usr/obj after my last buildworld
(FreeBSD 4.1-STABLE #0: Wed Sep 13 14:45:31 CEST 2000). Is this a problem?
Should I have done a buildworld before a buildkernel now?
--Stijn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Large disks (was Re: bin/19635: add -c for grand total to df(1))
On Thu, Jul 06, 2000 at 12:58:27PM +0200, Brad Knowles wrote: [whole discussion about df -h output snipped] You're ignoring the fact that "Size" is the total physical size of the device, while "Used", "Avail", and "Capacity" take into account the 10% (or whatever) overhead that is typically left unallocated for performance reasons. Maybe this isn't the right list to ask, but stepping into this: I bought a 30G drive recently, and I was wondering if the 10% 'rule' for performance is still really needed. I mean, I lose 3 _gigs_ of storage space, and otherwise the performance detoriates? That doesn't make sense to me. I am running now with reserved set to 2% (on my /home, not on smaller / /usr of course) and haven't noticed anything of performance loss; of course I haven't managed to fill that ~27G in the short time I have this setup ;) Which also leads me to the question: is it desirable, given those large disks, to have a finer grain of control over reserved space, for example setting reserved space to 2.5% or whatever? Or can this be done already? In the hopes that someone can enlighten me... --Stijn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: world broken?
Hi, ignore this for now please - I am getting past this on the same sources with a second buildworld. I suspect a hardware problem :( --Stijn On Wed, Jul 05, 2000 at 12:31:59AM +0200, Stijn Hoop wrote: Hi, Trying to build world, source just cvssup'ed, clean builddir and I get this error: Script started on Wed Jul 5 00:14:00 2000 firsa# make buildworld [...snip...] -- stage 3: cross tools -- [...snip...] cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr/obj/usr/src/i386/usr\" -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc.295 -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc.295/config -DTARGET_NAME=\"i386-unknown-freebsd\" -DIN_GCC -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc.295/fold-const.c -o fold-const.o /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc.295/fold-const.c: In function `add_double': /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc.295/fold-const.c:245: argument `hv' doesn't match prototype /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc.295/rtl.h:1576: prototype declaration /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc.295/fold-const.c:252: invalid type argument of `unary *' *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc_int. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. firsa# Script done on Wed Jul 5 00:23:08 2000 This is on FreeBSD 5.0-2701-CURRENT #0: Sat Jul 1 11:53:52 GMT 2000 (a -current snapshot from current.FreeBSD.org, GENERIC kernel). Anyone know what's up? --Stijn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
world broken?
Hi, Trying to build world, source just cvssup'ed, clean builddir and I get this error: Script started on Wed Jul 5 00:14:00 2000 firsa# make buildworld [...snip...] -- stage 3: cross tools -- [...snip...] cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr/obj/usr/src/i386/usr\" -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc.295 -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc.295/config -DTARGET_NAME=\"i386-unknown-freebsd\" -DIN_GCC -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc.295/fold-const.c -o fold-const.o /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc.295/fold-const.c: In function `add_double': /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc.295/fold-const.c:245: argument `hv' doesn't match prototype /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc.295/rtl.h:1576: prototype declaration /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc.295/fold-const.c:252: invalid type argument of `unary *' *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc_int. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. firsa# Script done on Wed Jul 5 00:23:08 2000 This is on FreeBSD 5.0-2701-CURRENT #0: Sat Jul 1 11:53:52 GMT 2000 (a -current snapshot from current.FreeBSD.org, GENERIC kernel). Anyone know what's up? --Stijn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
On Fri, Jun 23, 2000 at 11:04:10PM -0700, Kelly Yancey wrote:
Can you guys post the output of:
$ ipcs -bmo | awk -- '/^m/ {num++;total+=$7*$8}; END {print num,(total/4096)}'
taken while you are experiencing the problem. The first number is the total
number of shared memory segments currently active and the second should be the
total number of shared memory pages in use. Thanks,
Kelly
Hi,
just FYI, I don't know whether this is much but my machine is definitely
more lagged compared to when I just started X.
FreeBSD 5.0-CURRENT #6: Mon Jun 5 17:06:37 CEST 2000
(yeah it's a bit out of date...)
$ ipcs -bmo | awk -- '/^m/ {num++;total+=$7*$8}; END {print num,(total/4096)}'
47 1362
Running GNOME 1.2, XFree4 with the ati driver (Dell Optiplex onboard chip).
--Stijn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Anyone else seeing jumpy mice?
Just one more "problem" report: I see those messages, however I do not have any problems mousing afterwards. I'm using a switchview, which at least resets the mouse when I switch. On Sun, May 21, 2000 at 08:41:57PM -0700, Mike Smith wrote: Um, if you don't see the above message but see erratic mouse behavior, then there may be a configuration problem (for moused or X), or a hardware problem. My configuration works fine, the mouse worked without messages until I installed 5.0-current. You can also get this if you have moused running but have configured X to point to the physical mouse device rather than /dev/sysmouse. I do have /dev/psm0 in my XF86Config. You're saying it is better to use /dev/sysmouse, Protocol moused? BTW, it's a standard Logitech PS/2 3-button mouse. --Stijn -- FreeBSD: | Antonym, n.: The opposite of the word you're trying to The power to serve | think of. www.freebsd.org | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Stale modules (Re: panic in the morning)
On Wed, Apr 19, 2000 at 06:15:55PM -0700, Kris Kennaway wrote:
On Wed, 19 Apr 2000, Christoph Kukulies wrote:
I cvsup'ed, built world and kernel. Hhmm, actually I see no reason why
there should be a problem since everything should be done by make world.
make world doesn't build a kernel. Making a kernel doesn't build
modules. This bit me again the other day when updating, as well - panic at
boot when loading a stale linux.ko.
\begin{newbie question}
So why aren't the modules built with the kernel instead of with the world?
\end{newbie question}
--Stijn
--
FreeBSD: | When I was in school, I cheated on my metaphysics exam: I
The power to serve | looked into the soul of the boy sitting next to me. --
www.freebsd.org | Woody Allen
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
