Since the iwi driver has been MFC'd, I cannot build a kernel any more. I
csupped my src/sys to RELENG_6 a couple of hours ago. Everything
compiles fine, but when linking the kernel, make barfs:
linking kernel
if_iwi.o(.text+0x29c4): In function `iwi_getfw':
: undefined reference to
I was just fightened by all this make.conf stuff! If everything is in
my kernel file in /usr/src/sys/i386/conf/MINIMUM_PPS, can I just
ignore make.conf?
Your MINIMUM_PPS file contains the entire kernel configuration and
unless you want to tweak additional options (compiler flags and
monitor are wider than taller, why restrain horizontal space ?
A fixed width design is very fashionable these days and you see it creeping up
everywhere. It's what's considered professional these days, so I can't really
blame anybody trying to appear professional for choosing it. But I still
now, when i think of it, i suspect the reason might be CPUTYPE=pentium-m
The relevant bug is 75898, which I filed almost a year ago. It has been
fixed and MFC'd though, so it should not be affecting 6.0-release (I am
using CPUTYPE=pentium-m on 6.0 myself). Most likely, something else went
loader.old??? AFAIK loader is not rebuilt while compiling kernel and
there is no such file like loader.old created!
It is installed with world and not kernel then. Sorry for getting that
wrong, I didn't check. But it makes no difference to the original poster
because he reinstalled both world
I'd say the Dell's video is more likely to work (even 3d).
Well, not quite yet. X.Org 6.8 doesn't have any 3D support for modern
Radeon chips and the forthcoming 6.9/7.0 will have experimental
support. But 2D is working just fine (I am typing this on an Inspiron
8600C with ATI Radeon).
Mmm, the radeon man page claims Radeon 9000's are supported without caveats.
Oops, I sent my initial reply off-list. To summarize for everybody else:
Yes, you're right; I was thinking the Radeon 9000 was a newer chip,
while it is an oder one (an rv250), which has been fully supported for a
Or, can the touch pads be disabled in the bios?
I have a Dell Inspiron 8600C, which only has a touch pad. *But* its
immediate predecessor, the 8600, had a track pad and one of those little
pink joysticks (what are they called anyway?) and I know for a fact that
the keyboard and wrist rest in
It's so much better than the standard 1024x768 that you have to see
it to understand.
At least in my experience, it also makes people call you nuts all the
time. I am using tiny fonts for things that are not as important (like
menu bars, for example) and bit fonts for text that I really want
thanks, but the issue is with the loader itself
Telling it to use loader.old should definitely work around that problem.
Unless, of course, the problem lies within something that starts even
earlier. In this case, you could always use a 6.0 CD to restore the
original, working, files.
-
I've used portdowngrade for that purpose. My GF3 is not supported
by 97xx as well.
The x11/nvidia-driver port has a WITH_LEGACY_GPU_SUPPORT knob that
downgrades it all the way to version 7184, which supports many older GPUs.
- Bartosz
___
So my question is, should i pass the makefile options only when running
make to compile the program (that would make sence wouldnt it?) or should
i use them everytime i run make as in both when doing make and make
install clean.
I think your experience already showed you that the options have
/usr/ports/www/linuxpluginwrapper/pkg-message says:
Firefox has a double free problem wih Flash7. So I don't
support it. Please don't send me a report about firefox.
Of course, I always welcome to recieve fixed problems report.
That's kept me away from trying it.
Yes, Flash 7 doesn't seem
i have read that were some problems compiling the kernel and the
loader with pentium-m in CPUTYPE. are they fixed now?
I'm the one who filed the original bug report:
http://www.freebsd.org/cgi/query-pr.cgi?pr=75898
Since it hasn't been touched yet by anybody, my guess is that the problems
Are you saying, all we need to do is commit this diff to make everyone's
environment happy?
Obviously, I can't speak for everyone. For me, your patch fixes the kernel.
But the loader still causes an exception. That's of course because your patch
only affects the kernel itself and not the loader.
Can you try with just -mno-sse2? I'd like to litter the compile command
line as little as possible.
I just tried. -mno-sse2 indeed is all that's required to make the kernel
work. The same flag also makes the loader run again:
--- /usr/src/sys/boot/i386/loader/Makefile.old Tue Mar 15 18:03:13
That last patch was reversed. Sorry:
--- /usr/src/sys/boot/i386/loader/Makefile.old Tue Mar 15 18:03:13 2005
+++ /usr/src/sys/boot/i386/loader/Makefile Fri Feb 27 15:10:09 2004
@@ -40,7 +40,7 @@
CLEANFILES=vers.c loader loader.bin loader.help
-CFLAGS+= -Wall
+CFLAGS+= -Wall
Hi
Some commit in the last few weeks has broken the malloc() debug flags on RELENG_5. According to the
man page, a call to free() or realloc() with a modified pointer should cause a warning. Setting the
A flag in either /etc/malloc.conf or MALLOC_OPTIONS should turn this into an error.
However,
You're not running as root, are you? The A flag is always set for
root or setuid processes as a security measure.
No, I am running as a normal user.
There hasn't been any changes to the malloc code in 5.x since 5.3.
I realize there shouldn't have been any changes and I also cannot find
The actual test in the malloc code reads:
if (malloc_abort || issetugid() || getuid() == 0 || getgid() == 0)
wrterror(p)
, so it may also trigger if your primary groupid is 0 (wheel). Just
being a member of the wheel group won't trigger it.
Thank you very much for pointing this out. I
Hi list,
I am having trouble with 5-stable on an Intel Centrino notebook. The
system was installed from scratch using 5.3-release CDs and is updated
every few days to the latest 5-stable. The output of uname -a is:
FreeBSD takahe.local 5.3-STABLE FreeBSD 5.3-STABLE #6: Fri Nov 19
00:42:30 CET
Apparently, the CPU type changes have some unintended side effects. For
me, they render the system unbootable. I have been investigating what
broke my system between a 10th December cvsup and a 20th December one
and it boils down to bsd.cpu.mk. I am on a Centrino laptop, which uses a
Pentium M
Hi list,
I posted this question a few days ago, but it got lost in a thread I fear.
With the recent changes to bsd.cpu.mk, the setting CPUTYPE=pentium-m
in make.conf now gets picked up and leads to GCC flags being set
accordingly. Unfortunately, something gets enabled that the Pentium M
Hi list,
I am still having the problems with instant reboots that I reported [1]
a couple of weeks ago. I have a bit more info now and hope that someone
can lead me in the right direction.
The problem is that setting CPUTYPE=pentium-m in make.conf leads to a
corrupt boot loader and a corrupt
I use the athlon-xp switch on 3 boxes with no problems all of them running 5.3
What CFLAGS are you using? I have CFLAGS=-O -pipe in my make.conf. Maybe
you have optimization turned off and that's making a difference?
- Bartosz
___
Replying to myself, I have found the problem and filed a but report:
http://www.freebsd.org/cgi/query-pr.cgi?pr=75898
Thanks for all the help everybody,
- Bartosz
___
freebsd-stable@freebsd.org mailing list
Note that I only see the problem when building the loader as part of a
buildworld. Compiling just the boot stuff in /usr/src/sys/boot/ (i.e.,
without a bootstrapped gcc) results in a loader that works fine.
Curious. Either what you are seeing is a different problem then or it
somehow shows in a
I am running or not, what I am doing or not.
Any ideas on how to debug this? How can I find the guilty process?
Thanks for any and all input,
- Bartosz Fabianowski
PS: According to sysctl, DMA is enabled on both ata and atapi so that is
not the issue
top -qbSs 1 -d max /var/tmp/somefile
Thank you, that helped. Although top did not tell me which process was
guilty directly, it allowed me to track it down. For the record:
The process hogging the entire CPU was Xorg, which in turn was being
pushed by the KDE World Clock. At my screen
but i need a working OS, not a bata !
If you don't like using a beta (nothing wrong with that), you definitely
should not be using -stable either. There are even less promises
regarding the reliability and quality of -stable than there are of a
beta. After all, during the prerelease and beta
I am running a Dell D600 Latitude laptop [...] Here in FreeBSD, my
fans are running FULL SPEED all of the time and also seems to be
hotter than many conventional ovens.
I'm on a Dell Inspiron 8600C (which is the cheaper consumer-grade
version of your laptop) and it runs nice and cool for me.
# The exception above was detected in native code outside the VM
#
# Java VM: Java HotSpot(TM) Client VM (1.4.2-p8-rmvg_08_feb_2006_22_56 mixed
mode)
This problem has been fixed in revision 1.4.2p8_3 of java/jdk14,
committed on 11th February. Upgrade your JDK to the current revision and
try
resulted in a quite broken (and *un*stable) 5.5-PRERELEASE
RELENG_5 is 5.x-STABLE *most* of the time. When a release is nearing,
the first few steps of preparation happen directly on the stable branch,
so it will become 5.y-PRERELEASE (and IIRC even 5.y-BETA1). Then, when
the new release
re-instate the previous userbase (including those that applications
create). How would I best use mergemaster to accomplish this?
Just copy your customized files to /etc/passwd, /etc/group and then run
mergemaster to pick them up.
- Bartosz
___
/usr/src # make installworld
ERROR: Required audit group is missing, see /usr/src/UPDATING.
*** Error code 1
You probably forgot to run mergemaster -p before make installworld.
/usr/src # grep audit /usr/src/UPDATING
The note is there in -current. It
I filed a bug report for this in January of 2005:
http://www.freebsd.org/cgi/query-pr.cgi?pr=75898
- Bartosz
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL
Setting sendmail_enable to no in rc.conf does not work
Did you remember to set it to NONE, not just NO? This distinction
was introduced a long time ago and sendmail_enable=NONE has always
done the trick for me since then.
- Bartosz
___
sendmail_enable=NONE has been deprecated and will disappear in a
future release.
Thanks for pointing that out. According to /etc/rc.d/sendmail,
sendmail_enable=NONE corresponds to the following settings:
sendmail_enable=NO
sendmail_submit_enable=NO
sendmail_outbound_enable=NO
I am experiencing the exact same problem with 6.1-RC and iwi trying to
connect to an OpenWrt wireless router.
- Bartosz
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail
You wrote that Giant is needed in 6.0 and now you write it has been
removed.
In 4.x, every UFS write requires the Giant lock. In 6.x, Giant is not
normally required, making file system operations faster. When you enable
QUOTA, you basically get back to the 4.x behavior where Giant is needed
If a port is depend on others ports, during the
deinstall it will deinstall and all dependencies?
No. Only the one port you specify will be deinstalled. If you want to
remove dependencies that are no longer needed, use ports-mgmt/pkg_cutleaves.
- Bartosz
Hi list
A 2.5 USB hard disk I recently got has been giving me a lot of trouble.
When using the disk, I routinely get panics or random data corruption.
This happens with two separate machines, both running 6-STABLE. I found
that one file residing on the disk, when read, always makes the kernel
With the help of some folks in #freebsd on freenode, I have since been
able to fix this problem. Here is the solution for future reference:
There is a bug in GELI that makes it corrupt data and panic kernels when
certain non-standard settings are used. I had set the GELI sector size
to 8192
/home/obj/src/sys/dev/em/if_em.c: In function `em_allocate_intr':
/home/obj/src/sys/dev/em/if_em.c:2647: warning: passing arg 6 of
`bus_setup_intr' from incompatible pointer type
/home/obj/src/sys/dev/em/if_em.c:2647: error: too many arguments to function
`bus_setup_intr'
This has just been
can you upgrade from the test releases of 7 available now to the
final release when ready? Or do you have to wipe?
Some machines out there have been continuously upgraded since the
FreeBSD 2.x days. So yes, by all means, FreeBSD can be upgraded without
wiping.
iwicontrol is not used on 7 any more. You can use sysctl to query the
hardware switch instead:
sysctl dev.iwi.0.radio
- Bartosz
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send
I'd say that's the mork database format [1,2], as used by Mozilla
products, for example in the Firefox history.dat file.
- Bartosz
[1] http://www.mozilla.org/mailnews/arch/mork/primer.txt
[2] http://www.jwz.org/hacks/mork.pl
___
I think that this is related to some changes on the rsync end,
specifically their New USB stack with limited capability.
The new USB stack is not enabled by default. Rockbox still reboots the
iPod into emergency disk mode when USB is plugged in, just like it
always did.
That said, Apple's
the same device that FreeBSD used to identify as IPOD is now
identified as Rockbox
The Rockbox USB code keeps changing with each build - it used to request
power (using its own USB stack) until very recently for me, but as of a
couple of days ago, reboots into the original firmware again.
Can anyone verify that sdhci is compatible with FreeBSD 8?
I loaded mmc, mmcsd, and sdhci when I first installed FreeBSD 8.0
without any problems. Since then, I have updated to -STABLE and put
these three devices in my kernel configuration file. No problems either.
It must be very recent
I just noticed this thread a day after my own fight with powerd and load
percentages that did not seem to make any sense.
The patch I came up with is attached. It modifies powerd to use the load
percentage of the busiest core. This reduces the range of values back to
0%...100% also for
On my Core i7 setup here, the change seems to work well.
... in your specific workload. And you haven't described how you
measured system performance to prove that it haven't decreased.
My measure of performance is entirely unscientific: This is a desktop
box. Performance is good if KDE
including the outputs of vmstat -c 2 and iostat -c 2 in the hope
that these may shed some light on this.
Thanks,
- Bartosz Fabianowski
vmstat -c 2
procs memory pagedisks faults
cpu
r b w avmfre flt re pi pofr sr ad0 cd0 in sy
cs us sy
Just for an experiment, try to disable powerd and look if things improve.
Or just bump it to maximum, temporarily.
I have tried both now. The results are as follows:
* With powerd disabled and the CPU clocked down, the computer is
responsive when almost nothing is going on but becomes very
did you test the caches? I've seen such a behavior when cpu cache was
disabled.
The Dell BIOS setup is very minimalistic and would not even allow me to
turn off caches. So unless the FreeBSD boot loader somehow turned them
off, the caches should be active. Is there some tool I can use to
I don't know which i7 you have, but the intel datasheet for the i7-870 states
that the maximum case temperature is 72.7C.
I have a Core i7 Q740 with a native speed of 1.73GHz. My previous Dell
had a Q730. Both were exhibiting the same problems.
Since this is a laptop, I would expect
As the processor gets hotter, internal clocks and so on are throttled
within the hardware to try and stabilise the temperature (to keep the
thermal trip point being reached, re: emergency shutdown), which
greatly decreases performance. I'm not sure if there's a way to
detect this, but I would
dev.cpu.X.freq does reflect the current frequency; I don't know whether
or how any internal clock throttling might be exposed.
From what I have seen, dev.cpu.X.freq always retains the value I set it
to. Internal CPU throttling does not seem to be reported this way.
a bit of hunting found
I am not sure tz0 is the real thermal zone, especially given values
of _tc1, _tc2 and _tsp. Temperature value (3001) looks suspicious as
well.
I agree. tz0 looks entirely bogus. There is no second fan to control for
it and I have no idea what it is supposed to be monitoring.
Can you, by
Sorry to hear none of that helped. It seems a very serious problem, and
it would be useful to know if it behaves any better under linux or not.
I am still on the hunt for a bootable Linux distribution. I am in the
unfortunate situation of having no CD-Rs at hand. And because it is
Easter,
Try Knoppix, or Ubuntu LiveCD. I tend to use the former for rescue
situations:
Thanks. I am aware of both - but neither boots from USB (and I have no
CD-Rs at hand). I am running UNetbootin under Windows XP in VirtualBox
right now to try and get Xubuntu 10.04 onto a USB key. It is really sad
Please , see the site
http://www.mandriva.com/en/linux/
Thanks for the link. It looks like this a USB with a preinstalled
Mandriva Linux on it that you have to buy for €50 though. I am looking
for an image that I can just download.
- Bartosz
___
click the link 2009 Rescue iso , which will lead to
http://dl1.mandriva.com/flash/rescue/2009.0/
Thanks. There is no mention anywhere on the page that the ISO files can
be treated as USB boot images as well. Hence, I did not realize they
would suit my needs.
Also you may see :
GRML ISOs (from grml.org) can be dd-ed directly to a USB stick and
should then boot with any reasonable current BIOS.
Thanks. It is great to see that so many ISOs can be dd-ed to USB keys. I
wish the distributions would make it clearer which ISOs work as USB
images and which do not. I am
If you boot into another operating system such as Linux or Windows, do
you see the same overall behaviour? Linux might be easier and might
have some built-in way to get at CPU temperatures (via /proc?).
I finally found a working USB Linux image and have run some tests:
Linux power management
Please , see :
http://cdimage.debian.org/debian-cd/6.0.1-live/amd64/
http://cdimage.debian.org/debian-cd/6.0.1-live/i386/
By using dd , you may copy a hybrid .iso to USB stick .
Thanks. I downloaded the amd64 image. It booted perfectly after copying
to a USB key via dd.
- Bartosz
As several have either discovered or pointed out, the dev.cpu.X.freq is
telling you what FreeBSD is requesting, not what the CPU is actually
doing. Particularly, if high temperatures cause TCC to kick in, this
will not show up.
Yes, this is what I thought as well.
IF you really want to
I could be wrong, but in my experience this really sounds like it is
a hardware problem with the cooling system, and a very serious one at
that. I would encourage you to take this up with Dell at once.
Yes, I will. They have exchanged a lot of components already though
(including the whole
Have you tried just using dd to copy the iso image of a Ubuntu / Linux
LiveCD to a suitably sized USB memory stick?
It has worked for me in the past.
As per Mehmet's tip, I did just that with a Debian image. If it works
for Ubuntu images as well then I really wonder why the only documented
The specified maximum CPU temperature is usually the same at the ACPI
_CRT, not _PSV. That is the temperature when an ACPI shutdown should be
triggered, but TCC should kick in at some point below this.
This laptop is a replacement for an earlier one that had similar
overheating issues. On
Did you try to set OS override to any of the values, recognized by
your BIOS, with most interesting being Windows 2001 SP2, Windows
2006 and Windows 2009.
Yes, I tried this a while ago, before messing with the DSDT. I figured
it was unlikely that Dell shipped a DSDT which leads to 0°C
This appears to be a different issue from the one I am seeing. The
system is very responsive at first and only under load (and with rising
temperatures) becomes extremely sluggish. As load (and temperatures)
drop, the system becomes usable again. Also, there is no difference
between Qt and Gtk
Once you have a port installed, pkg_info -R gconf\* will tell you.
- Bartosz
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
PS/2 or USB keyboard?
The same is happening on my system.
My keyboard has a DIN connector plugged into a PS/2 adapter plugged into
a USB adapter plugged into a powered USB hub plugged into the FreeBSD box.
- Bartosz
___
freebsd-stable@freebsd.org
My laptop has a Radeon HD 5470. Xorg and consoles work perfectly. There
is little or no hardware acceleration though. This means no 3D games for
sure. I remember videos being rather jerky in full screen as well but
with the most recent version of the ati driver, even full HD videos seem
to run
75 matches
Mail list logo
