USB prevents system from powering off and ucom prevents usb from being unloaded - ideas?
Subject line is the executive summary of my problem: I have a box with an Intel 945GC A2 chipset that will not poweroff on shutdown if the usb kernel module is loaded (or statically compiled into the kernel). Unloading the usb kernel modules sometime during shutdown (I hacked the usbd rc script for this) to work around the problem helped until I needed to hook up another device which uses ucom(4) to the machine. On kldunload, ucom claims to detach, but remains loaded and subsequent kldunload attempts trigger the error kldunload: attempt to unload file that was loaded by the kernel. The stuck ucom in turn prevents usb from getting unloaded and the machine cannot poweroff. I have already tried disabling EHCI, but it does not help. Any ideas on either getting uhci to properly detach on shutdown or getting rid of ucom? Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: This is a digitally signed message part.
Re: Various problems with re(4) on a PCIe 8168/8111B onboard NIC
On Tuesday, 31. July 2007, Pyun YongHyeon wrote: On Tue, Jul 31, 2007 at 01:31:59AM +0200, Michael Nottebrock wrote: On Monday, 30. July 2007, Pyun YongHyeon wrote: Thanks for reporting. I don't have these hardware models so I couldn't verify the issue. After reading the vendor's code I've made attached patch. I don't know whether it works or not, it's just guess work. Works fine here! Since HEAD is in code freeze I guess minimal patch would be more preferable. Would you try attached patch again? That one works, too. Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: This is a digitally signed message part.
Re: Various problems with re(4) on a PCIe 8168/8111B onboard NIC
On Monday, 30. July 2007, Pyun YongHyeon wrote: Thanks for reporting. I don't have these hardware models so I couldn't verify the issue. After reading the vendor's code I've made attached patch. I don't know whether it works or not, it's just guess work. Works fine here! Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: This is a digitally signed message part.
Various problems with re(4) on a PCIe 8168/8111B onboard NIC
After recently updating the windows drivers (I dual-boot Windows XP on the machine the NIC is in), I hit this problem: http://gentoo-wiki.com/HARDWARE_RTL8168#Troubleshooting which affects re(4) like it does the Linux drivers described in the above link. I already wrote the Realtek technical support about it since their own FreeBSD driver (a hacked rl(4) that does not support any of the chip's advanced features) does not manage to power up the PHY on its own either - neither does the motherboard's BIOS when trying to netboot. The other problem is that I have at least two applications misbehaving when rxcsum/txcsum is enabled: - The Linux Second Life client (yes, yes, I know, but it is nice for showing off GLX and it is really really good at generating network traffic) will cease to receive data after about a minute or so - turning off rcxsum/txcsum will mend it on the spot. - A Fedora Core 4 running in Qemu, networked with bridge(4) and tap(4), cannot receive an ip address via DHCP. Interestingly, this even occurs if rxcsum/txcsum was already turned off before launching Qemu - to make it work, I have to cycle rxcsum/txcsum once. Might be related to promiscuous mode. I realise that both of these make awful test cases, but so far they are the only applications I found to expose those problems. This is on FreeBSD kiste 6.2-STABLE FreeBSD 6.2-STABLE #4: Sat Jul 28 14:11:23 CEST 2007 root@:/usr/obj/usr/src/sys/KISTE-SMP i386. The kernel sources are up to date as of 2007-07-27. The NIC is re0: RealTek 8168/8111B PCIe Gigabit Ethernet port 0xd800-0xd8ff mem 0xfbfff000-0xfbff irq 36 at device 0.0 on pci3 / [EMAIL PROTECTED]:0:0: class=0x02 card=0x81681849 chip=0x816810ec rev=0x01 hdr=0x00. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: This is a digitally signed message part.
Re: Various problems with re(4) on a PCIe 8168/8111B onboard NIC
On Sunday, 29. July 2007, Kent Stewart wrote: Have you looked at /var/log/messages? I would be surprised if you have not had a number of Jul 27 00:55:32 ruby kernel: re0: watchdog timeout Jul 27 00:55:32 ruby kernel: re0: link state changed to DOWN Jul 27 00:55:35 ruby kernel: re0: link state changed to UP In fact I have and I haven't had any such messages (except link down/up when I switched rxcsum/txcsum, but that is expected - no watchdog timeouts at all). I also should mention that the interface never completely goes dead either. People have complained a long time ago and basically given up on getting it fixed. I saw that yongari@ has been busy trying to brush up re(4) recently, that's why I thought I'd pipe up. :) Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: This is a digitally signed message part.
Re: powerd freeze with amd 5000 X2 but not with lower cpus
JoaoBR schrieb: On Friday 27 July 2007 12:31:55 Nate Lawson wrote: JoaoBR wrote: Hi when I enable powerd with default flags (and any other also) the computer freezes some seconds after powerd is started. It does not reach login. Nothing in the logs. This is with amd 5000 X2 Am2 When i stick into the same computer a 4600 or 4200 it runs fine and smooth. I thought it is MB related and did the same and again the 5000 cpu freeze, the smaller ones not. Any idea what I should do? I use releng_6 amd and i386 same story and cpufreq and acpi is compiled. Disable powerd again and boot normally. Try changing the frequency with sysctl dev.cpu, etc. and see if any of the levels freeze for you. ok, this is what I get dev.cpu.0.freq_levels: 2600/10 2400/85596 2200/72544 2000/60778 1800/50237 1000/25535 no need to say but the fan levels obviously are wrong And now the interesting part I shift to 2400 or any other and immediately freeze, that from kde konsole in single user mode I can shift up and down between all speeds and nothing happens [Jumping in from the thread started on -stable - http://lists.freebsd.org/pipermail/freebsd-stable/2007-July/036395.html - see there for system details] Same here - in single user mode, even powerd works fine - like it does with SMP disabled - but no go in multiuser. I see some similar discussion on stable but I can not match with everything there because I have the problem only with the athlon 5000 cpu The CPU difference is interesting - exactly what model is your X2 4600+? Mine is a stepping F, model 4B, rev BH-F2 (Energy Efficient with 65W TDP). Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: OpenPGP digital signature
Re: powerd freeze with amd 5000 X2 but not with lower cpus
JoaoBR schrieb: On Saturday 28 July 2007 04:21:39 Michael Nottebrock wrote: JoaoBR schrieb: On Friday 27 July 2007 12:31:55 Nate Lawson wrote: JoaoBR wrote: Hi when I enable powerd with default flags (and any other also) the computer freezes some seconds after powerd is started. It does not reach login. Nothing in the logs. This is with amd 5000 X2 Am2 When i stick into the same computer a 4600 or 4200 it runs fine and smooth. I thought it is MB related and did the same and again the 5000 cpu freeze, the smaller ones not. Any idea what I should do? I use releng_6 amd and i386 same story and cpufreq and acpi is compiled. Disable powerd again and boot normally. Try changing the frequency with sysctl dev.cpu, etc. and see if any of the levels freeze for you. ok, this is what I get dev.cpu.0.freq_levels: 2600/10 2400/85596 2200/72544 2000/60778 1800/50237 1000/25535 no need to say but the fan levels obviously are wrong And now the interesting part I shift to 2400 or any other and immediately freeze, that from kde konsole in single user mode I can shift up and down between all speeds and nothing happens [Jumping in from the thread started on -stable - http://lists.freebsd.org/pipermail/freebsd-stable/2007-July/036395.html - see there for system details] Same here - in single user mode, even powerd works fine - like it does with SMP disabled - but no go in multiuser. I see some similar discussion on stable but I can not match with everything there because I have the problem only with the athlon 5000 cpu The CPU difference is interesting - exactly what model is your X2 4600+? Mine is a stepping F, model 4B, rev BH-F2 (Energy Efficient with 65W TDP). seems to be the same but I have better news and seems my first idea was right, the MB is it I found a tech info on the manufactor's support site telling cpu support up to 4600+ and found a bios for newer cpus including my 5000+ so I upgraded the bios and my CPU now works with smp + cpufreq + powerd on both amd64 and i386 Good to hear. Unfortunately my Mobo's BIOS is already up-to-date, the CPU is officially supported and Cool'n'Quiet works dandy in Windows XP ... =/ Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: OpenPGP digital signature
Re: powerd freeze with amd 5000 X2 but not with lower cpus
JoaoBR schrieb: On Saturday 28 July 2007 07:10:21 Michael Nottebrock wrote: JoaoBR schrieb: On Saturday 28 July 2007 04:21:39 Michael Nottebrock wrote: JoaoBR schrieb: On Friday 27 July 2007 12:31:55 Nate Lawson wrote: JoaoBR wrote: Hi when I enable powerd with default flags (and any other also) the computer freezes some seconds after powerd is started. It does not reach login. Nothing in the logs. This is with amd 5000 X2 Am2 When i stick into the same computer a 4600 or 4200 it runs fine and smooth. I thought it is MB related and did the same and again the 5000 cpu freeze, the smaller ones not. Any idea what I should do? I use releng_6 amd and i386 same story and cpufreq and acpi is compiled. Disable powerd again and boot normally. Try changing the frequency with sysctl dev.cpu, etc. and see if any of the levels freeze for you. ok, this is what I get dev.cpu.0.freq_levels: 2600/10 2400/85596 2200/72544 2000/60778 1800/50237 1000/25535 no need to say but the fan levels obviously are wrong And now the interesting part I shift to 2400 or any other and immediately freeze, that from kde konsole in single user mode I can shift up and down between all speeds and nothing happens [Jumping in from the thread started on -stable - http://lists.freebsd.org/pipermail/freebsd-stable/2007-July/036395.html - see there for system details] Same here - in single user mode, even powerd works fine - like it does with SMP disabled - but no go in multiuser. I see some similar discussion on stable but I can not match with everything there because I have the problem only with the athlon 5000 cpu The CPU difference is interesting - exactly what model is your X2 4600+? Mine is a stepping F, model 4B, rev BH-F2 (Energy Efficient with 65W TDP). seems to be the same but I have better news and seems my first idea was right, the MB is it I found a tech info on the manufactor's support site telling cpu support up to 4600+ and found a bios for newer cpus including my 5000+ so I upgraded the bios and my CPU now works with smp + cpufreq + powerd on both amd64 and i386 Good to hear. Unfortunately my Mobo's BIOS is already up-to-date, the CPU is officially supported and Cool'n'Quiet works dandy in Windows XP ... =/ my ok msg was too fast, after some time my video starts flickering and stays so and the PC is freezed up, disabling powerd and works stable Meanwhile I found a workaround for my system: I had SCHED_ULE configured in my kernel - switching to SCHED_4BSD gets rid of the freezes. Should have thought of that sooner, ISTR having problems with powerd and SCHED_ULE even on single cpu P4s. Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: OpenPGP digital signature
Re: powerd freeze with amd 5000 X2 but not with lower cpus
Kris Kennaway schrieb: On Sat, Jul 28, 2007 at 03:46:15PM +0200, Michael Nottebrock wrote: Meanwhile I found a workaround for my system: I had SCHED_ULE configured in my kernel - switching to SCHED_4BSD gets rid of the freezes. Should have thought of that sooner, ISTR having problems with powerd and SCHED_ULE even on single cpu P4s. I see you've now learned a reason why no-one should be using SCHED_ULE on FreeBSD 7 ;-) ... and with SCHED_ULE being obsoleted by SCHED_SMP in 7+, it might actually become the scheduler nobody was ever supposed to be using? It might still be worthwhile doing some experimenting with powerd and the different schedulers in -CURRENT, just in case 4BSD ever gets knocked from GENERIC. :) Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: OpenPGP digital signature
Hang with powerd/powernow with SMP enabled
The machine will freeze hard a few seconds after powerd is started up by the rc script. With kern.smp.disabled=1, everything seems to work fine. This is with today's 6-STABLE/i386. I see that a fix for that sort of thing was only recently MFC'd, unfortunately I cannot say whether the problem was already there before it went in - the box is brand new. Various debugging information: sysctl -a | grep cpu: http://people.freebsd.org/~lofi/cpu_nosmp.txt http://people.freebsd.org/~lofi/cpu_smp.txt sysctl -a | grep acpi: http://people.freebsd.org/~lofi/acpi_nosmp.txt http://people.freebsd.org/~lofi/acpi_smp.txt dmesg -v (SMP) http://people.freebsd.org/~lofi/dmesg_smp.txt acpidump -dt: http://people.freebsd.org/~lofi/acpidump.txt Let me know if I can provide more information. Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: OpenPGP digital signature
Re: Hang with powerd/powernow with SMP enabled
Uwe Laverenz schrieb: On Fri, Jul 27, 2007 at 05:27:45PM +0200, Michael Nottebrock wrote: The machine will freeze hard a few seconds after powerd is started up by the rc script. With kern.smp.disabled=1, everything seems to work fine. This is with today's 6-STABLE/i386. I see that a fix for that sort of thing was only recently MFC'd, unfortunately I cannot say whether the problem was already there before it went in - the box is brand new. I have the same problem with a dual Opteron (RELENG_6_2, i386 and amd64), in my case the following workaround helped: from /boot/loader.conf: hint.acpi_throttle.0.disabled=1 Thanks! Unfortunately it does not help here - but with that, it takes a few seconds longer for the freeze to occur. Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: OpenPGP digital signature
Re: Problems with named default configuration in 6-STABLE
On Tuesday, 17. July 2007, Yuri Pankov wrote:
On Mon, Jul 16, 2007 at 11:19:41PM +0200, Michael Nottebrock wrote:
I finally updated my desktop from 5.5-RELEASE to 6-STABLE. This got me a
new named.conf, which I modified to run named as a local resolver, like I
had before:
listen-on { 127.0.0.1; };
listen-on-v6{ ::1; };
forward only;
forwarders {
192.168.8.1;
};
Everything else is default. However, with this default configuration,
named will not resolve any hosts of my local domain (my.domain), which
uses addresses in the 192.168.8 subnet. My dns server on 192.168.8.1,
running 6.2-RELEASE, has a very simple dynamic dns setup: a zone
my.domain and a reverse zone 8.168.192.in-addr.arpa which are both
dynamically updated by dhcpd.
To make this work again, I had to delete everything in the default
named.conf from /* Slaving the following zones from the root [...]
to zone ip6.int { type master;
file master/empty.db; };.
I'm a DNS n00b, but I suspect that such drastic measures shouldn't be
required and somehow my setup is flawed. What can I do to make this work
right?
Cheers,
--
,_, | Michael Nottebrock | [EMAIL PROTECTED]
(/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
\u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org
Hi Michael,
If I understood you correctly, you can't resolve 8.168.192.in-addr.arpa
anymore, and the line below (from default named.conf) is the cause:
zone 168.192.in-addr.arpa { type master; file master/empty.db; };
Yes - and this:
zone . {
type slave;
file slave/root.slave;
masters {
192.5.5.241;// F.ROOT-SERVERS.NET.
192.228.79.201; // B.ROOT-SERVERS.NET.
192.33.4.12;// C.ROOT-SERVERS.NET.
192.112.36.4; // G.ROOT-SERVERS.NET.
193.0.14.129; // K.ROOT-SERVERS.NET.
};
notify no;
};
prevents me from resolving hostnames in my.domain. What I'm still wondering
though, is this an oversight or by design? I can't imagine setups like mine
are very rare. Doug?
--
,_, | Michael Nottebrock | [EMAIL PROTECTED]
(/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
\u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org
signature.asc
Description: This is a digitally signed message part.
Re: Problem with KDM not passing to Xorg/KDE after login
On Tuesday, 17. July 2007, Kim Attree wrote: Michael Nottebrock wrote: On Monday, 16. July 2007, Kim Attree wrote: Mike, I had an 'exec bash' in my $HOME/.profile and removing this allowed me to run ./Xsession default and push me into KDE ! KDM though - still refuses to pass to KDE I'm reluctant to give up on the shell angle already - can you try setting your user's shell to /bin/csh or /bin/sh just for kicks and check if KDM still doesn't work? Mike, I set the user shell to /bin/sh in passwd using vipw, ran clone_root to propogate the change to the diskless root, rebooted the client and that did'nt work. It's really strange - I'm starting to think maybe its a PAM thing, since after I put in the user/pass in KDM, it sits for about 45-60 seconds before going back to the KDM login screen again. Any Thoughts ? Right now, I have run out of ideas - I have never run a diskless configuration myself and cannot easily make one here either, so I am probably missing a good deal of possible failure modes here. You could try using some other display manager for logging in instead, like xdm or gdm. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: This is a digitally signed message part.
Re: Problems with named default configuration in 6-STABLE
On Tuesday, 17. July 2007, Volker wrote:
On 07/17/07 09:20, Michael Nottebrock wrote:
On Tuesday, 17. July 2007, Yuri Pankov wrote:
On Mon, Jul 16, 2007 at 11:19:41PM +0200, Michael Nottebrock wrote:
I finally updated my desktop from 5.5-RELEASE to 6-STABLE. This got me
a new named.conf, which I modified to run named as a local resolver,
like I had before:
listen-on { 127.0.0.1; };
listen-on-v6{ ::1; };
forward only;
forwarders {
192.168.8.1;
};
Everything else is default. However, with this default configuration,
named will not resolve any hosts of my local domain (my.domain), which
uses addresses in the 192.168.8 subnet. My dns server on 192.168.8.1,
running 6.2-RELEASE, has a very simple dynamic dns setup: a zone
my.domain and a reverse zone 8.168.192.in-addr.arpa which are both
dynamically updated by dhcpd.
To make this work again, I had to delete everything in the default
named.conf from /* Slaving the following zones from the root
[...] to zone ip6.int { type master;
file master/empty.db; };.
I'm a DNS n00b, but I suspect that such drastic measures shouldn't be
required and somehow my setup is flawed. What can I do to make this
work right?
Cheers,
--
,_, | Michael Nottebrock | [EMAIL PROTECTED]
(/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
\u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org
Hi Michael,
If I understood you correctly, you can't resolve 8.168.192.in-addr.arpa
anymore, and the line below (from default named.conf) is the cause:
zone 168.192.in-addr.arpa { type master; file master/empty.db; };
Yes - and this:
zone . {
type slave;
The root zone MUST be of type hint. You do not want to be a slave of
the root... don't you? ;)
The new default configuration of named wants me to be.
But now that you've mentioned it, I finally saw the following lines in the
default named.conf:
---
If you do not wish to slave these zones from the root servers
use the entry below instead.
zone . { type hint; file named.root; };
---
I scanned over that before, but being a DNS n00b, I didn't understand what it
meant. So, that solves that. Still, quite a bit of editing required:
Commenting out the slaved root zone, moving out the root servers hint out of
a comment and commenting out the empty zone for my private use network to
make reverse lookups work again.
I think at least an UPDATING entry and maybe some more verbose and less
technical commenting in named.conf itself is warranted.
--
,_, | Michael Nottebrock | [EMAIL PROTECTED]
(/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
\u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org
signature.asc
Description: This is a digitally signed message part.
Re: Problems with named default configuration in 6-STABLE
On Tuesday, 17. July 2007, Heiko Wundram (Beenic) wrote:
On Tuesday 17 July 2007 09:20:16 Michael Nottebrock wrote:
Yes - and this:
zone . {
type slave;
file slave/root.slave;
masters {
192.5.5.241;// F.ROOT-SERVERS.NET.
192.228.79.201; // B.ROOT-SERVERS.NET.
192.33.4.12;// C.ROOT-SERVERS.NET.
192.112.36.4; // G.ROOT-SERVERS.NET.
193.0.14.129; // K.ROOT-SERVERS.NET.
};
notify no;
};
prevents me from resolving hostnames in my.domain. What I'm still
wondering though, is this an oversight or by design? I can't imagine
setups like mine are very rare. Doug?
This is natural, unless you specifically enter the zones for 192.168.8.*
(forward and reverse) in your client DNS server (as slave or forward zones,
see the bind manual for the latter, which I'd recommend in your case).
Ah, I'm (re)-learning more about DNS here than I ever thought I would. Indeed,
with forward and reverse slave zones, I don't need to comment out anything
anymore from the default config. I guess that solves my problems and the list
audience will be saved from yet more DNS talk. :)
Cheers,
--
,_, | Michael Nottebrock | [EMAIL PROTECTED]
(/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
\u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org
signature.asc
Description: This is a digitally signed message part.
Re: Problem with KDM not passing to Xorg/KDE after login
On Monday, 16. July 2007, Kim Attree wrote: Michael Nottebrock wrote: On Thursday, 12. July 2007, Kim Attree wrote: Michael Nottebrock wrote: On Monday, 9. July 2007, Kim Attree wrote: I made Root's $HOME point to /var/db (touched to make sure it's writable on the diskless workstation - it is) and the KDM still refuses to pass to Xorg/KDE. Any Other Ideas ??? Make sure you have a hostname set (in rc.conf or via dhcp) and localhost is resolvable. Mike, I've checked rc.conf and the hostname is defined and a 'hostname' command on the workstation confirms this. I've added a /etc/hosts file on the workstation (through the /conf/default directory on diskless server) with the following: 127.0.0.1 localhost 196.31.157.162 diskless02.csc.jnb6.za.uu.net (server) 196.31.157.130 csc01.csc.jnb6.za.uu.net (workstation) confirmed that localhost resolves to 127.0.0.1 on the workstation. KDM still refuses to pass to Xorg. Just to make sure - you cannot launch any session type from kdm, not even failsafe? What happens if you try to run Xsession manually, i.e.: $ X [switch back to VTY] $ env DISPLAY=:0 /usr/local/share/config/kdm/Xsession default [switch back to X11] Does KDE start? If not, try running Xsession as above but with shell tracing enabled like $ env DISPLAY=:0 sh -x /usr/local/share/config/kdm/Xsession default to see where it hangs/exits. Cheers, Mike, Did what you asked: 1. Started background process of X as root 2. Switched VTY's and ran the Xsession Result: KDE Ran as expected Then as a normal user, left the Xorg process running in background as root. Changed VTY, logged in as a normal user, ran the command, and also with shell tracing. Both times just drops back to command prompt with no the following: snip csc01$ sh -x /usr/local/share/config/kdm/Xsession default + session=kde/Xsession + [ -z ] + exec /usr/local/bin/bash /usr/local/share/config/kdm/Xsession default csc01$ snip So as root Xsession works but as your user it does not, right? I suspect it might have something to do with your user's shell - for root, it's probably csh, whereas for your normal user it seems to be set to bash. You can try unsetting the SHELL environment variable or setting it to /bin/csh or /bin/sh before running Xsession as your normal user (or just temporarily change your shell altogether) and see if that fares any better. To debug Xsession with bash, try editing the Xsession script: Change the line [ -z $BASH ] exec $SHELL $0 $@ to [ -z $BASH ] exec $SHELL -x $0 $@ This should get you more debug output. Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: This is a digitally signed message part.
Re: Problem with KDM not passing to Xorg/KDE after login
On Monday, 16. July 2007, Kim Attree wrote: Mike, I had an 'exec bash' in my $HOME/.profile and removing this allowed me to run ./Xsession default and push me into KDE ! KDM though - still refuses to pass to KDE I'm reluctant to give up on the shell angle already - can you try setting your user's shell to /bin/csh or /bin/sh just for kicks and check if KDM still doesn't work? -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: This is a digitally signed message part.
Problems with named default configuration in 6-STABLE
I finally updated my desktop from 5.5-RELEASE to 6-STABLE. This got me a new
named.conf, which I modified to run named as a local resolver, like I had
before:
listen-on { 127.0.0.1; };
listen-on-v6{ ::1; };
forward only;
forwarders {
192.168.8.1;
};
Everything else is default. However, with this default configuration, named
will not resolve any hosts of my local domain (my.domain), which uses
addresses in the 192.168.8 subnet. My dns server on 192.168.8.1, running
6.2-RELEASE, has a very simple dynamic dns setup: a zone my.domain and a
reverse zone 8.168.192.in-addr.arpa which are both dynamically updated by
dhcpd.
To make this work again, I had to delete everything in the default named.conf
from /* Slaving the following zones from the root [...]
to zone ip6.int { type master;
file master/empty.db; };.
I'm a DNS n00b, but I suspect that such drastic measures shouldn't be required
and somehow my setup is flawed. What can I do to make this work right?
Cheers,
--
,_, | Michael Nottebrock | [EMAIL PROTECTED]
(/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
\u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org
signature.asc
Description: This is a digitally signed message part.
Re: Problem with KDM not passing to Xorg/KDE after login
On Thursday, 12. July 2007, Kim Attree wrote: Michael Nottebrock wrote: On Monday, 9. July 2007, Kim Attree wrote: I made Root's $HOME point to /var/db (touched to make sure it's writable on the diskless workstation - it is) and the KDM still refuses to pass to Xorg/KDE. Any Other Ideas ??? Make sure you have a hostname set (in rc.conf or via dhcp) and localhost is resolvable. Mike, I've checked rc.conf and the hostname is defined and a 'hostname' command on the workstation confirms this. I've added a /etc/hosts file on the workstation (through the /conf/default directory on diskless server) with the following: 127.0.0.1 localhost 196.31.157.162 diskless02.csc.jnb6.za.uu.net (server) 196.31.157.130 csc01.csc.jnb6.za.uu.net (workstation) confirmed that localhost resolves to 127.0.0.1 on the workstation. KDM still refuses to pass to Xorg. Just to make sure - you cannot launch any session type from kdm, not even failsafe? What happens if you try to run Xsession manually, i.e.: $ X [switch back to VTY] $ env DISPLAY=:0 /usr/local/share/config/kdm/Xsession default [switch back to X11] Does KDE start? If not, try running Xsession as above but with shell tracing enabled like $ env DISPLAY=:0 sh -x /usr/local/share/config/kdm/Xsession default to see where it hangs/exits. Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: This is a digitally signed message part.
Re: Problem with KDM not passing to Xorg/KDE after login
On Monday, 9. July 2007, Kim Attree wrote: I made Root's $HOME point to /var/db (touched to make sure it's writable on the diskless workstation - it is) and the KDM still refuses to pass to Xorg/KDE. Any Other Ideas ??? Make sure you have a hostname set (in rc.conf or via dhcp) and localhost is resolvable. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: This is a digitally signed message part.
Re: vietnamese input
On Tuesday, 1. May 2007, vuthecuong wrote: Is there a utility to allow input vietnamese? Currently I'm using Scim-anthy for Japanese input. I heared that m17n can be used to input about 17 languages including Vietnamese. Xvnkb (http://xvnkb.sourceforge.net/) is available in ports under vietnamese/xvnkb. HTH, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpmZiT8MLSKU.pgp Description: PGP signature
Re: k3b problem
On Wednesday, 25. April 2007, Thomas Quinot wrote: * Ganbold, 2007-04-25 : With this revision of atapi-cam.c k3b application hangs on splash screen and I had to use power button only to restart the machine. I am confused. Is your *application* hanging, or is the *whole system* hanging People have reported system hangs, reboots and kernel panics. See http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034556.html and the messages referenced in that message, as well as followups (I personally don't run a recent enough FreeBSD to get the problem). Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpBYyapUNbGS.pgp Description: PGP signature
Re: [kde-freebsd] problem hal - k3b ?
On Wednesday, 18. April 2007, Beni wrote: Hi List, I think I have a problem with hal(d) and k3b (version 1.0 from ports) : my whole system freezes when starting up k3b. I get the splash screen and then it all stops and a ctrl-alt-del is the only way out. Other people have reported kernel panics. It looks to me like k3b's device probing and hald's device probing at the same time manages to tickle a bug in ata(4). Ref: http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070753.html http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034486.html I'm afraid a true kernel hacker will have to inconvenince themselves with running k3b and hal in order to have this one fixed. FWIW, I haven't seen in happening on 5.5. Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpxWXd0rPazw.pgp Description: PGP signature
Re: [kde-freebsd] problem hal - k3b ?
I forwarded my mail to gnome@ (the HAL maintainers) after sending it and Joe Marcus Clarke from gnome@ had this to say on the issue: --- snip This should have been fixed a while ago by jylefort when he set the default device for ATAPI access to be the ATAPICAM device (as opposed to the ATA device). Assuming you have not undone that change, and are running the latest version of HAL, these panics should not be occurring. Even still, you're right that these are not HAL bugs, but rather an issue in the kernel. I use nautilus-cd-burner to burn CDs in GNOME, and I have never had such a panic on 6-STABLE. n-c-b uses cdrecord, cdrao, and dvd-utils under the covers to do the actual device work. Not sure what k3b is using, but maybe it diddles something it shouldn't. Joe --- snip Beni, Robert, Ganbold, are you all in fact running the latest version of the hal port and do you all have atapicam enabled in your kernel? If not, making sure of both might help avoiding the problem. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org ---BeginMessage--- Michael Nottebrock wrote: I forgot to cc gnome@ on my reply. I don't think this is a HAL bug, but just FYI. Subject: Re: [kde-freebsd] problem hal - k3b ? From: Michael Nottebrock [EMAIL PROTECTED] Date: Thu, 19 Apr 2007 18:12:46 +0200 To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: Beni [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] On Wednesday, 18. April 2007, Beni wrote: Hi List, I think I have a problem with hal(d) and k3b (version 1.0 from ports) : my whole system freezes when starting up k3b. I get the splash screen and then it all stops and a ctrl-alt-del is the only way out. Other people have reported kernel panics. It looks to me like k3b's device probing and hald's device probing at the same time manages to tickle a bug in ata(4). Ref: http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070753.html http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034486.html I'm afraid a true kernel hacker will have to inconvenince themselves with running k3b and hal in order to have this one fixed. FWIW, I haven't seen in happening on 5.5. This should have been fixed a while ago by jylefort when he set the default device for ATAPI access to be the ATAPICAM device (as opposed to the ATA device). Assuming you have not undone that change, and are running the latest version of HAL, these panics should not be occurring. Even still, you're right that these are not HAL bugs, but rather an issue in the kernel. I use nautilus-cd-burner to burn CDs in GNOME, and I have never had such a panic on 6-STABLE. n-c-b uses cdrecord, cdrao, and dvd-utils under the covers to do the actual device work. Not sure what k3b is using, but maybe it diddles something it shouldn't. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: [EMAIL PROTECTED] FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ---End Message--- pgpMnseiiYv2q.pgp Description: PGP signature
Re: sysctl segfaulting
On Saturday, 24. February 2007 15:27, Volker wrote: Your problem with libelf reminded me to one thing: Have you done a `make check-old' in /usr/src already? I didn't find it in the docs but while reading the Makefile.incl and have not been aware of that check procedure but it clearly showed I've had some elder binaries in my system. Please forgive me if that hint has already been posted. No need to apologize, I appreciate every suggestion. However, by now I'm reasonably sure this isn't some kind of mismatch/stale software problem - there is indeed nothing stale left as far as the base system is concerned on that box at all. Given the strange nature of the error there might even be hardware failure involved (bad memory, possibly), I still need to check on that front. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpY9yeNYYoSB.pgp Description: PGP signature
Re: sysctl segfaulting
Does anybody have any further ideas on this? Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpMSrQTzOtvt.pgp Description: PGP signature
Re: sysctl segfaulting
On Friday, 23. February 2007 18:47, Oliver Fromme wrote:
Michael Nottebrock wrote:
Does anybody have any further ideas on this?
I've had a quick look at the source. According to your
debugging info, an invalid pointer is passed to the
S_clockinfo() function, but it's beyond me how that
could happen. The code in show_var() which calls that
function looks perfectly OK.
It's also interesting that you seem to be the only one
experiencing the problem. Are you using any special
compiler options, anything unusual in /etc/make.conf
or /etc/malloc.conf? Do you use a non-default locale
environment (i.e. are any of the LC_* or LANG variables
set)?
LANG is set (but LANG=C makes no difference) and otherwise, the only setting
out of the ordinary is kern.hz=2000 in loader.conf. The values reported by
the FreeBSD 5 sysctl binary for kern.clockrate are
kern.clockrate: { hz = 2000, tick = 500, profhz = 1333, stathz = 266 }
--
,_, | Michael Nottebrock | [EMAIL PROTECTED]
(/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
\u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org
pgpdNekoUOSOX.pgp
Description: PGP signature
sysctl segfaulting
I have a strange problem on one of my computers: sysctl segfaults when querying kern.clockrate (and more annoyingly when trying to print kern.clockrate when run with -a). I cannot tell for sure when this problem appeared, the last things I did to the system was putting in an sata harddisk and enabling geli, which required me to rebuild the kernel to add a few kernel modules (crypto cryptodev geom/geom_eli zlib). [EMAIL PROTECTED]:0:~ sysctl -a kern.ostype: FreeBSD kern.osrelease: 6.2-RELEASE kern.osrevision: 199506 kern.version: FreeBSD 6.2-RELEASE #4: Sat Feb 17 09:23:50 CET 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LOFI.4BSD kern.maxvnodes: 35372 kern.maxproc: 4004 kern.maxfiles: 102400 kern.argmax: 262144 kern.securelevel: -1 kern.hostname: lofi.dyndns.org kern.hostid: 0 kern.clockrate: Segmentation fault (core dumped) I've attached the ktrace output of 'sysctl kern.clockrate' to this message. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org 3167 ktrace RET ktrace 0 3167 ktrace CALL execve(0xbfbfe670,0xbfbfebb4,0xbfbfebc0) 3167 ktrace NAMI /sbin/sysctl 3167 ktrace NAMI /libexec/ld-elf.so.1 3167 sysctl RET execve 0 3167 sysctl CALL mmap(0,0xf40,0x3,0x1000,0x,0,0,0) 3167 sysctl RET mmap 671563776/0x28074000 3167 sysctl CALL munmap(0x28074000,0xf40) 3167 sysctl RET munmap 0 3167 sysctl CALL __sysctl(0xbfbfe958,0x2,0x28070b58,0xbfbfe954,0,0) 3167 sysctl RET __sysctl 0 3167 sysctl CALL mmap(0,0x8000,0x3,0x1002,0x,0,0,0) 3167 sysctl RET mmap 671563776/0x28074000 3167 sysctl CALL issetugid 3167 sysctl RET issetugid 0 3167 sysctl CALL open(0x2806ac48,0,0x1b6) 3167 sysctl NAMI /etc/libmap.conf 3167 sysctl RET open 3 3167 sysctl CALL fstat(0x3,0xbfbfe070) 3167 sysctl RET fstat 0 3167 sysctl CALL read(0x3,0x28078000,0x1000) 3167 sysctl GIO fd 3 read 124 bytes # /etc/libmap.conf # # candidate mapping # libpthread.so.2 libthr.so.2 # Everything uses libthr libpthread.so libthr.so 3167 sysctl RET read 124/0x7c 3167 sysctl CALL read(0x3,0x28078000,0x1000) 3167 sysctl GIO fd 3 read 0 bytes 3167 sysctl RET read 0 3167 sysctl CALL close(0x3) 3167 sysctl RET close 0 3167 sysctl CALL open(0x28069ea0,0,0) 3167 sysctl NAMI /var/run/ld-elf.so.hints 3167 sysctl RET open 3 3167 sysctl CALL read(0x3,0xbfbfe920,0x80) 3167 sysctl GIO fd 3 read 128 bytes 0x 4568 6e74 0100 8000 b300 |Ehnt..| 0x0012 b200 |..| 0x0024 |..| 0x0036 |..| 0x0048 |..| 0x005a |..| 0x006c |..| 0x007e |..| 3167 sysctl RET read 128/0x80 3167 sysctl CALL lseek(0x3,0,0x80,0,0) 3167 sysctl RET lseek 128/0x80 3167 sysctl CALL read(0x3,0x28076100,0xb3) 3167 sysctl GIO fd 3 read 179 bytes /lib:/usr/lib:/usr/lib/compat:/usr/X11R6/lib:/usr/local/lib:/usr/local/lib/c\ ompat/pkg:/usr/local/lib/compat:/usr/local/lib/mysql:/usr/local/lib/courier-\ authlib:/usr/local/lib/pth\0 3167 sysctl RET read 179/0xb3 3167 sysctl CALL close(0x3) 3167 sysctl RET close 0 3167 sysctl CALL access(0x2807a000,0) 3167 sysctl NAMI /lib/libc.so.6 3167 sysctl RET access 0 3167 sysctl CALL open(0x280750c0,0,0) 3167 sysctl NAMI /lib/libc.so.6 3167 sysctl RET open 3 3167 sysctl CALL fstat(0x3,0xbfbfe960) 3167 sysctl RET fstat 0 3167 sysctl CALL read(0x3,0x2806faa0,0x1000) 3167 sysctl GIO fd 3 read 4096 bytes 0x 7f45 4c46 0101 0109 0300 |.ELF..| 0x0012 0300 0100 80ea 0100 3400 7c0f 0e00 |..4...|...| 0x0024 3400 2000 0300 2800 1e00 1d00 0100 |4. ...(...| 0x0036 f28e 0c00 |..| 0x0048 f28e 0c00 0500 0010 0100 0090 |..| 0x005a 0c00 0090 0c00 0090 0c00 7050 a4b7 0100 |..pP..| 0x006c 0600 0010 0200 c4cc 0c00 c4cc |..| 0x007e 0c00 c4cc 0c00 a800 a800 0600 |..| 0x0090 0400 0508 210b 8105 3108
Re: sysctl segfaulting
On Saturday, 17. February 2007 10:09, Rink Springer wrote: Hi Michael, On Sat, Feb 17, 2007 at 09:47:45AM +0100, Michael Nottebrock wrote: I've attached the ktrace output of 'sysctl kern.clockrate' to this message. Hmm, could you try to rebuild sysctl manually and give that one a try? Maybe there's not something in sync. Something like: # cd /usr/src/sbin/sysctl # make # ./sysctl kern.clockrate Would work. If this fails, could you build a debugging version (eg. make CFLAGS=-g) and use gdb(1) to find out exactly where it crashes? I already tried both, but to little avail, which is why I went with ktrace in my initional mail instead. But for reference: [EMAIL PROTECTED]:0:/usr/src/sbin/sysctl # make clean make depend env CFLAGS=-g make make install rm -f sysctl sysctl.o sysctl.8.gz sysctl.8.cat.gz cc -g -c /usr/src/sbin/sysctl/sysctl.c cc -g-o sysctl sysctl.o gzip -cn /usr/src/sbin/sysctl/sysctl.8 sysctl.8.gz install -s -o root -g wheel -m 555 sysctl /sbin install -o root -g wheel -m 444 sysctl.8.gz /usr/share/man/man8 [EMAIL PROTECTED]:0:/usr/src/sbin/sysctl # cd [EMAIL PROTECTED]:1:~ # exit [EMAIL PROTECTED]:1:~ rm sysct [EMAIL PROTECTED]:1:~ gdb sysctl GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd...(no debugging symbols found)... (gdb) set args kern.clockrate (gdb) run Starting program: /sbin/sysctl kern.clockrate (no debugging symbols found)...(no debugging symbols found)...kern.clockrate: Program received signal SIGSEGV, Segmentation fault. 0x08049696 in ?? () (gdb) bt #0 0x08049696 in ?? () #1 0xbfbfe238 in ?? () #2 0x28050b29 in _rtld_bind_start () from /libexec/ld-elf.so.1 #3 0x28077000 in ?? () #4 0x0118 in ?? () #5 0x0010 in ?? () #6 0x0010 in ?? () #7 0x0002 in ?? () #8 0xbfbfeba4 in ?? () #9 0x0804e000 in ?? () #10 0xbfbfe238 in ?? () #11 0x0804a5f2 in ?? () #12 0x0014 in ?? () #13 0x0804e000 in ?? () #14 0x0804b133 in ?? () #15 0xbfbfd990 in ?? () #16 0x0001 in ?? () #17 0x0012 in ?? () #18 0x28052863 in find_symdef () from /libexec/ld-elf.so.1 Previous frame inner to this frame (corrupt stack?) (gdb) -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpGoNjvozGd3.pgp Description: PGP signature
Re: sysctl segfaulting
I experimented some more and found something even more funny: A sysctl binary copied over from a FreeBSD 5.5 machine works (the FreeBSD 6 box with the segfaulting sysctl has the 5.x compat libraries installed). So I tried recompiling libc with debug cflags (-g3 -O -pipe), but this only makes the backtrace in gdb much longer, but still without any function names. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp5J1t6Ustx3.pgp Description: PGP signature
Re: Very slow umass in 6.2-RC2
Has anyone ever managed to get some USB 2.0 - like speeds out of ehci anyway? I'm not seeing quite such abysmal performance as Kevin did, but I don't even need to benchmark to be certain that Windows does *much* better with the devices I own. Here are some numbers: First up, the controller: ehci0: VIA VT6202 USB 2.0 controller mem 0xdfffbd00-0xdfffbdff irq 21 at device 16.4 on pci0 usb4: VIA VT6202 USB 2.0 controller on ehci0 usb4: USB revision 2.0 To be sure the umass device is actually a child of the ehci device: dev.umass.0.%parent: uhub4 dev.uhub.4.%parent: usb4 This is a Panasonic Pro High Speed series 512mb SD-CARD, which theoretically supports burst transfer rates up to 20MB/s on a USB 2.0 multi card reader: da2 at umass-sim0 bus 0 target 0 lun 2 da2: Hama CardReaderMMC/SD 1.9C Removable Direct Access SCSI-0 device da2: 40.000MB/s transfers da2: 472MB (967680 512 byte sectors: 64H 32S/T 472C) vmstat while running bonnie -s 472 (I don't have bonnie results, since it would have taken forever to finish): Disks ad0 ad4 da0 da1 da2 da3 pass0 KB/t 16.00 0.00 0.00 0.00 12.01 0.00 0.00 tps 1 0 0 0 154 0 0 MB/s 0.02 0.00 0.00 0.00 1.80 0.00 0.00 % busy0 0 0 099 0 0 This is a Trekstor Vibez portable music player, which comes with an 8GB microdrive and an USB 2.0 interface, again with bonnie: umass0: TrekStor vibez, rev 2.00/1.10, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: TrekStor vibez 2 Removable Direct Access SCSI-4 device da0: 40.000MB/s transfers da0: 7613MB (15592237 512 byte sectors: 255H 63S/T 970C) Disks ad0 ad4 da0 pass0 KB/t 12.73 0.00 4.00 0.00 tps 2 0 339 0 MB/s 0.03 0.00 1.32 0.00 % busy1 0 100 0 -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp7ZOpyYyZxU.pgp Description: PGP signature
Re: sysctl segfaulting
On Saturday, 17. February 2007 11:39, Rink Springer wrote:
Hi Michael,
On Sat, Feb 17, 2007 at 11:36:46AM +0100, Michael Nottebrock wrote:
So I tried recompiling libc with debug cflags (-g3 -O -pipe), but this
only makes the backtrace in gdb much longer, but still without any
function names.
Hmm, 'make install' appears to strip the debugging info.
Duh, I keep forgetting that.
Please try
gdb-ing /usr/obj/usr/src/sbin/sysctl/sysctl instead (assuming you use
default the /usr/obj path like I do)
I recompiled/reinstalled both sysctl and libc with CFLAGS=-g3 and STRIP= and
now I get:
[EMAIL PROTECTED]:0:~ gdb /sbin/sysctl
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as i386-marcel-freebsd...
(gdb) set args kern.clockrate
(gdb) run
Starting program: /sbin/sysctl kern.clockrate
kern.clockrate:
Program received signal SIGSEGV, Segmentation fault.
0x08049696 in S_clockinfo (l2=20, p=0x804e000)
at /usr/src/sbin/sysctl/sysctl.c:333
333 printf(hflag ? { hz = %'d, tick = %'d, profhz = %'d, stathz
= %'d } :
(gdb) bt
#0 0x08049696 in S_clockinfo (l2=20, p=0x804e000)
at /usr/src/sbin/sysctl/sysctl.c:333
#1 0x0804a5f2 in show_var (oid=0xbfbfea80, nlen=2)
at /usr/src/sbin/sysctl/sysctl.c:690
#2 0x08049093 in parse (string=0xbfbfecb1 kern.clockrate)
at /usr/src/sbin/sysctl/sysctl.c:208
#3 0x08048e77 in main (argc=0, argv=0xbfbfeba0)
at /usr/src/sbin/sysctl/sysctl.c:152
(gdb) list
328 struct clockinfo *ci = (struct clockinfo*)p;
329 if (l2 != sizeof(*ci)) {
330 warnx(S_clockinfo %d != %d, l2, sizeof(*ci));
331 return (0);
332 }
333 printf(hflag ? { hz = %'d, tick = %'d, profhz = %'d, stathz
= %'d } :
334 { hz = %d, tick = %d, profhz = %d, stathz = %d },
335 ci-hz, ci-tick, ci-profhz, ci-stathz);
336 return (0);
337 }
(gdb) print ci-hz
Error accessing memory address 0x804e000: Bad address.
(gdb) print ci-tick
Error accessing memory address 0x804e004: Bad address.
(gdb) print ci-profhz
Error accessing memory address 0x804e010: Bad address.
(gdb) print ci-stathz
Error accessing memory address 0x804e00c: Bad address.
(gdb) print ci
$1 = (struct clockinfo *) 0x804e000
(gdb) print p
$2 = (void *) 0x804e000
(gdb) print l2
$3 = 20
--
,_, | Michael Nottebrock | [EMAIL PROTECTED]
(/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
\u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org
pgpwU6wvpf7d9.pgp
Description: PGP signature
Re: Very slow umass in 6.2-RC2
Michael Nottebrock schrieb: Has anyone ever managed to get some USB 2.0 - like speeds out of ehci anyway? I'm not seeing quite such abysmal performance as Kevin did, but I don't even need to benchmark to be certain that Windows does *much* better with the devices I own. Actually let me backpedal just a bit there - the SD-Card doesn't do much better, looks like the crappy card reader is the bottleneck (or Panasonic rigged their highspeed cards to require special readers for true high speed). But the Vibez flies - 6-7 MB/s on Windows 2000. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: OpenPGP digital signature
Re: pppd crashes, was: kde-freebsd] Question about KPPP on FreeBSD
On Sunday, 11. February 2007 02:43, Bruce M. Simpson wrote: So far so good. The problem is that the BSD magicians and the KDE GUI magicians are not sharing their spell-books, and thus, their models of how the code operates; the communities have to intersect somehow. That could be you, y'know. Human bridges are just as, if not more, important as ISO/OSI Layer 2 devices. :^) Quite true. However, this particular human bridge between developer communities is running at capacity already. We need some trunking here. Redundant links, y'know. When I said someone, I *do* mean someone who isn't me (and whose idea of communication isn't yelling at developers in bugzilla). :) -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpLeeG7cwMsu.pgp Description: PGP signature
Re: Desired behaviour of ifconfig -alias
On Saturday, 10. February 2007 12:17, JoaoBR wrote: On Saturday 10 February 2007 01:54, Ian Smith wrote: Secondly, pardon my ignorance, but what does 'NS' refer to here? That string / term occurs nowhere else in ifconfig(8). nameserver I think this actually refers to XNS. You can tell that manpage has quite a history. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpVS4gWPqo8T.pgp Description: PGP signature
Re: pppd crashes, was: kde-freebsd
On Friday, 9. February 2007 22:48, John Walthall wrote: Because of known problems with PPPD, KPPP should provide at least the option of using user land PPP. You may of course differ from this view. However, unless a large outcry arises, I will not close the bug. I think that it is, in-fact a bug. Bugs are sometimes a bit subjective. The KPPP Developers can always ignore me. No, bugs are not 'a bit subjective'. With just a little actual analysis and straight thinking it is very easy to determine what is a bug and where the bug is. The fact that KPPP does not support ppp(8) is not a bug, it is a missing feature. If you want to request a feature, you open a wish, not a bug, you word it nicely and preferably attach some code that implements that feature, because this is how community-driven open source development works. Did it ever cross your mind that the KPPP developer(s) might not even use FreeBSD? The fact that machines panic or freeze when KPPP is used is not a bug in KPPP either, because KPPP is nothing but a front-end to the software that causes the problem. By principle, a kernel panic or freeze is never an application's fault, because the kernel should never panic and never freeze, no matter what an application does. Therefore, the bug report needs to go into FreeBSD's bugtracker (someone else already filed one, see my previous mails for the URL), not KDE's. All that your bug report accomplishes is broadcasting your bad and uninformed attitude to an even bigger audience. It is in your own and the FreeBSD community's best interest to backtrack before anyone gets to form a negative opinion on both. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp7bVJV0CANM.pgp Description: PGP signature
Re: pppd crashes, was: kde-freebsd] Question about KPPP on FreeBSD
On Saturday, 10. February 2007 07:34, Ian Smith wrote: Since once trying (and failing) to debug or even comprehend a spaghetti of scripts and configs behind a dialout-only linux pppd setup some years ago, compared to the much more straightforward ppp with mgetty setup for both dialout and some dialin modem lines I'd built pretty much from the FreeBSD Handbook even at 2.2.6 with nary a problem, regressing for sake of 'compatibility' with a linux-based sub-application seems silly. Well, kppp makes configuring dialout easy. Or attempts to, at least. :) I agree with you about this not being a KPPP bug (though searching KDE bugs for 'kppp' provides no shortage of hits!) and appreciate that KDE people have no interest in catering for user ppp, since it's not linux, despite or perhaps because of its obvious superiority to FreeBSD people. Maybe at least the KPPP 'documentation', such as it is, could at least mention that it doesn't support FreeBSD's ppp over tun devices, to avoid the expectation that it should work that gave rise to this thread. It kinda does. It says right in the about dialog and in the very first line of its online help: A dialer and front end for pppd. And yes, if pppd is broken and won't be fixed, it should disappear. And when that happens, so will kppp (it won't build once the if_ppp.h header is gone). Which of course would solve the problem in a way. In any case: I dragged this issue onto -stable precisely to attract attention to the problem and hopefully motivate someone to get down and write some code, whether for pppd or kppp, I really don't care much. Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpyYiQbYxsIy.pgp Description: PGP signature
Re: pppd crashes, was: kde-freebsd
On Thursday, 8. February 2007 23:16, John Walthall wrote: Ok, now an editorial: I should not really dignify this rant by replying to it, but: We have a fundamental design difference from Linux here. We chose this difference because we believed that it was better. Why would we go back now because the developers of a third-party interface to our systems did a clumsy job? KPPP is not an interface to 'our' systems. It's an interface to *pppd*, which happens to be available for a wide range of Unices and Unix-like systems. We should adjure them to implement the new and better system. This is not actually an appropriate place for this discussion. It should be directed to [EMAIL PROTECTED] and/or http://bugs.kde.org. Because it is a KDE problem and *not* a FreeBSD Problem. (I have already submitted it to the KDE Bugzilla) A kernel panic/freeze triggered by a badly maintained driver is most certainly not any application's problem. You should probably close that bug yourself. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpC06TnsA434.pgp Description: PGP signature
Re: Possibility for FreeBSD 4.11 Extended Support
On Friday, 22. December 2006 03:59, Garrett Wollman wrote: [EMAIL PROTECTED] writes: -5.x was never really for production use, in the same way 3.x never was. Why do people continue to say this? Because everybody knows that odd numbered releases aren't stable. Just like .0 and .1 releases are rushed out the door after a few months of mad hackfest and patches being rushed back and forth on kernel.org. Smirk. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp9eLXAnQTYb.pgp Description: PGP signature
Re: nvidia-driver related (?) panic on 5.5-RELEASE
On Wednesday, 14. June 2006 18:26, Michael Nottebrock wrote: On Tuesday, 13. June 2006 01:03, Michael Nottebrock wrote: I'm getting similar kernel panics even when running (and quitting) much simpler applications than secondlife in wine - for instance, this is a panic I got quitting foobar2000 (a very unfancy Windows audio player): #0 doadump () at pcpu.h:160 #1 0xc04edd29 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:412 #2 0xc04ee04d in panic (fmt=0xc0697a7d %s: interrupts disabled) at /usr/src/sys/kern/kern_shutdown.c:568 #3 0xc064d6eb in pmap_invalidate_range (pmap=0xc07065a0, sva=3684024320, eva=3684040704) I'm getting this on FreeBSD 6.0 as well. Can't anybode else reproduce this? It is a little alarming that a mere userland application can reliably down the system like that. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp6eORKqJcIp.pgp Description: PGP signature
Re: nvidia-driver related (?) panic on 5.5-RELEASE
On Tuesday, 13. June 2006 01:03, Michael Nottebrock wrote:
I'm getting similar kernel panics even when running (and quitting) much
simpler applications than secondlife in wine - for instance, this is a panic
I got quitting foobar2000 (a very unfancy Windows audio player):
#0 doadump () at pcpu.h:160
#1 0xc04edd29 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:412
#2 0xc04ee04d in panic (fmt=0xc0697a7d %s: interrupts disabled)
at /usr/src/sys/kern/kern_shutdown.c:568
#3 0xc064d6eb in pmap_invalidate_range (pmap=0xc07065a0, sva=3684024320,
eva=3684040704)
at /usr/src/sys/i386/i386/pmap.c:636
#4 0xc064df0d in pmap_qremove (sva=3684024320, count=0)
at /usr/src/sys/i386/i386/pmap.c:1013
#5 0xc0533530 in vfs_vmio_release (bp=0xd694a188)
at /usr/src/sys/kern/vfs_bio.c:1600
#6 0xc0532ab1 in brelse (bp=0xd694a188) at /usr/src/sys/kern/vfs_bio.c:1382
#7 0xc0541d9c in vtruncbuf (vp=0xc6951420, cred=0xc3cf0e00, td=0xc3be1780,
length=0,
blksize=0) at /usr/src/sys/kern/vfs_subr.c:1150
#8 0xc05e5a36 in ffs_truncate (vp=0xc6951420, length=0, flags=2048,
cred=0xc3cf0e00,
td=0xc3be1780) at /usr/src/sys/ufs/ffs/ffs_inode.c:400
#9 0xc0601b47 in ufs_setattr (ap=0x0) at /usr/src/sys/ufs/ufs/ufs_vnops.c:566
#10 0xc0604e73 in ufs_vnoperate (ap=0x0)
at /usr/src/sys/ufs/ufs/ufs_vnops.c:2827
#11 0xc04f2d65 in coredump (td=0xc3be1780) at vnode_if.h:364
#12 0xc04f2647 in sigexit (td=0xc3be1780, sig=10)
at /usr/src/sys/kern/kern_sig.c:2414
#13 0xc04f0a51 in trapsignal (td=0xc3be1780, sig=10, code=30)
at /usr/src/sys/kern/kern_sig.c:1531
#14 0xc0652da0 in trap (frame=
{tf_fs = 2080248359, tf_es = -1083375569, tf_ds = -1083375569, tf_edi =
2080208384, tf_esi = 0, tf_ebp = 2080260028, tf_isp = -368837276, tf_ebx
= -1678306116, tf_edx = 2080228352, tf_ecx = 0, tf_eax = 0, tf_trapno = 9,
tf_err = 0, tf_eip = -1678318765, tf_cs = 31, tf_eflags = 2097686, tf_esp =
2080259968, tf_ss = 47})
at /usr/src/sys/i386/i386/trap.c:632
#15 0xc0640fea in calltrap () at /usr/src/sys/i386/i386/exception.s:140
I'm not really sure anymore whether the nvidia driver has any part in this - I
cannot rule it out however, since the nv driver doesn't recognize my graphics
card and wine refuses to work with the vesa driver. The panics do go away
with SMP disabled.
--
,_, | Michael Nottebrock | [EMAIL PROTECTED]
(/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
\u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org
pgpGwp5x95UVk.pgp
Description: PGP signature
nvidia-driver related (?) panic on 5.5-RELEASE
I've been trying to run Second Life (http://www.secondlife.com) in WINE and
get a reproducable kernel panic when I try to quit the application. WINE is
able to run Second Life quite well otherwise for a while, but will eventually
crash accompanied by kernel trap 9 with interrupts disabled kernel
messages.
The kernel panic message is:
pmap_invalidate_range: interrupts disabled
Here's a backtrace of a crash dump I got:
#0 doadump () at pcpu.h:160
160 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) bt
#0 doadump () at pcpu.h:160
#1 0xc04edd29 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:412
#2 0xc04ee04d in panic (fmt=0xc0697a7d %s: interrupts disabled)
at /usr/src/sys/kern/kern_shutdown.c:568
#3 0xc064d6eb in pmap_invalidate_range (pmap=0xc07065a0, sva=3614474240,
eva=3614490624)
at /usr/src/sys/i386/i386/pmap.c:636
#4 0xc064df0d in pmap_qremove (sva=3614474240, count=0)
at /usr/src/sys/i386/i386/pmap.c:1013
#5 0xc0533530 in vfs_vmio_release (bp=0xd6787680)
at /usr/src/sys/kern/vfs_bio.c:1600
#6 0xc0532ab1 in brelse (bp=0xd6787680) at /usr/src/sys/kern/vfs_bio.c:1382
#7 0xc0541d9c in vtruncbuf (vp=0xc3f99420, cred=0xc3a8e480, td=0xc41e9d80,
length=0,
blksize=0) at /usr/src/sys/kern/vfs_subr.c:1150
#8 0xc05e5a36 in ffs_truncate (vp=0xc3f99420, length=0, flags=2048,
cred=0xc3a8e480,
td=0xc41e9d80) at /usr/src/sys/ufs/ffs/ffs_inode.c:400
#9 0xc0601b47 in ufs_setattr (ap=0x0) at /usr/src/sys/ufs/ufs/ufs_vnops.c:566
#10 0xc0604e73 in ufs_vnoperate (ap=0x0)
at /usr/src/sys/ufs/ufs/ufs_vnops.c:2827
#11 0xc04f2d65 in coredump (td=0xc41e9d80) at vnode_if.h:364
#12 0xc04f2647 in sigexit (td=0xc41e9d80, sig=10)
at /usr/src/sys/kern/kern_sig.c:2414
#13 0xc04f0a51 in trapsignal (td=0xc41e9d80, sig=10, code=30)
at /usr/src/sys/kern/kern_sig.c:1531
#14 0xc0652da0 in trap (frame=
{tf_fs = 2035999, tf_es = 19857455, tf_ds = -1091174353, tf_edi =
2079350784, tf_esi = 0, tf_ebp = 2079371196, tf_isp = -371511964, tf_ebx
= -1678306116, tf_edx = 2079343616,---Type return to continue, or q
return to quit---
# tf_ecx = 0, tf_eax = 0, tf_trapno = 9, tf_err = 0, tf_eip = -1678318765,
tf_cs = 31, tf_eflags = 2097686, tf_esp = 2079371136, tf_ss = 47})
at /usr/src/sys/i386/i386/trap.c:632
#15 0xc0640fea in calltrap () at /usr/src/sys/i386/i386/exception.s:140
... and finally, my kernel config is attached.
Cheers,
--
,_, | Michael Nottebrock | [EMAIL PROTECTED]
(/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
\u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org
#
# GENERIC -- Generic kernel configuration file for FreeBSD/i386
#
# For more information on this file, please read the handbook section on
# Kernel Configuration Files:
#
#
http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
#
# The handbook is also available locally in /usr/share/doc/handbook
# if you've installed the doc distribution, otherwise always see the
# FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
# latest information.
#
# An exhaustive list of options and more detailed explanations of the
# device lines is also present in the ../../conf/NOTES and NOTES files.
# If you are in doubt as to the purpose or necessity of a line, check first
# in NOTES.
#
# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.413.2.6.2.2 2004/10/24 18:02:52
scottl Exp $
machine i386
cpu I686_CPU
ident KISTE-SMP
# To statically compile in device wiring instead of /boot/device.hints
#hints GENERIC.hints # Default places to look for devices.
makeoptions DEBUG=-g
options SMP # Symmetric MultiProcessor Kernel
#optionsSCHED_ULE # ULE scheduler
options SCHED_4BSD # 4BSD scheduler
options INET# InterNETworking
options INET6 # IPv6 communications protocols
options FFS # Berkeley Fast Filesystem
options SOFTUPDATES # Enable FFS soft updates support
options UFS_ACL # Support for access control lists
options UFS_DIRHASH # Improve performance on big directories
options MD_ROOT # MD is a potential root device
options NFSCLIENT # Network Filesystem Client
options NFSSERVER # Network Filesystem Server
options NFS_ROOT# NFS usable as /, requires NFSCLIENT
options MSDOSFS # MSDOS Filesystem
options CD9660 # ISO 9660 Filesystem
options PROCFS # Process filesystem (requires PSEUDOFS)
options PSEUDOFS# Pseudo-filesystem framework
options GEOM_GPT# GUID Partition Tables.
options COMPAT_43 # Compatible with BSD 4.3 [KEEP
Re: KDE 3.5
Roger Grosswiler schrieb: Hey, where can i get it from with pkg_add ?? http://www.freebsd.org/doc/en/books/handbook/packages-using.html Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: OpenPGP digital signature
Re: KDE 3.5
Kris Kennaway schrieb: Unfortunately, now we are back to square 1, since you just committed KDE 3.5.1 :-) 'S okay - patience is a virtue and package users are the most virtuous bunch of them all. And as for square one, expat2 got bumped. :O Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: OpenPGP digital signature
Re: KDE 3.5.0 seems much chubbier than 3.4.2
Daniel O'Connor schrieb: I just updated to KDE 3.5.0 and it seems considerably more memory hungry that 3.4.2, for example.. PID USERNAME THR PRI NICE SIZERES STATETIME WCPU COMMAND 1126 darius 5 200 213M 50816K kserel 13:09 0.73% amarokapp 1119 darius 3 200 260M 67180K kserel 40:04 0.00% kdeinit 1153 darius 3 200 137M 51080K kserel 17:08 0.00% kmail 1118 darius 3 200 119M 7324K kserel 6:03 0.00% kopete 1050 darius 1 960 77228K 10140K select 3:37 0.00% kdeinit 1090 darius 1 960 98476K 12680K select 1:20 0.00% kdeinit 1110 darius 1 960 73292K 5136K select 1:14 0.00% kdeinit 1089 darius 1 960 91168K 6084K select 0:47 0.00% kdeinit 1082 darius 1 960 122M 7268K select 0:40 0.00% kdeinit No wonder my system is thrashing :) Does anyone know why 3.5.0 seems to be using so much more memory? I did recently update to the latest -current (ie new malloc implementation) but the the sluggish behaviour was still present prior to that (although maybe not as bad) Not to suggest you're imagining things, but someone else just posted on freebsd-current@ that other applications show greatly increased memory usage as well, so it probably is a -current specific problem after all. Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: OpenPGP digital signature
Re: timecounter and Hz quality in kern RELENG_6
On Monday, 7. November 2005 17:10, Oliver Fromme wrote: Michael Schuh [EMAIL PROTECTED] wrote: i be very surprised about the performance of RELENG_6. Congratulations to the entire Team for this very good work. Now i have 2 Machines installed with 6.0-RC1, and i have seen that on both machines the Hz is differntly with GENERIC-Kernel. sysctl kern.clockrate tells you the HZ value. In FreeBSD 6 the dafult is 1000, unless you change it via options HZ=x in your kernel configuration. ... or via the kern.hz loader tunable. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpwaIEvNrLHP.pgp Description: PGP signature
OT: Failure notices from blogger.com
I recently started to get failure notices from [EMAIL PROTECTED] when I post on the freebsd-stable mailing list. What is that all about? Is somebody redirecting all mail on the list to a blog via post-by-mail? If so, FYI: blogger.com does not like pgp signatures and it insists on telling me about it again and again. I'm not particularly amused. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpYh2s5PAPCL.pgp Description: PGP signature
Re: burncd and dvd-drives
On Friday, 4. November 2005 09:18, Dick Hoogendijk wrote: I was and am a great fan of the burncd utility. Very fast, simple and cli.. But as almost any new computer is supplied with a dvd drive this nice program has become quit useless. It does not support those drives. My question is: will it ever do? Burncd could use an additional dedicated maintainer - sos@ probably has his hands full enough with maintaining the actual ata driver. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpmsmWGO34vC.pgp Description: PGP signature
Re: HFS/HFS+ support in 5.4 Stable
On Sunday, 30. October 2005 11:14, edward wrote: Hi, I need to mount an iPod mini formatted in HFS+. I don't believe this file system is supported in 5.4 Stable, at least not on a standard kernel. I get : # ls /sbin/mount_* /sbin/mount_cd9660 /sbin/mount_msdosfs /sbin/mount_std /sbin/mount_devfs /sbin/mount_nfs /sbin/mount_udf /sbin/mount_ext2fs /sbin/mount_nfs4/sbin/mount_umapfs /sbin/mount_fdescfs /sbin/mount_ntfs/sbin/mount_unionfs /sbin/mount_linprocfs /sbin/mount_nullfs /sbin/mount_mfs /sbin/mount_procfs The following page offers a HFS/HFS+ kernel module based on Darwin code. But it seems kind of out of date (2003) : http://people.freebsd.org/~yar/hfs/ What would be the best way of building HFS/HFS+ support into my kernel ? You will need to add options GEOM_APPLE to your kernel configuration and use the filesystem driver from the URL you quoted. FreeBSD currently does not ship with hfs filesystem support. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp24my0qD8wG.pgp Description: PGP signature
Re: 6.0 release date and stability
On Thursday, 20. October 2005 21:20, Vivek Khera wrote: personally, I don't see the point of doing that. just let your ports naturally get replaced as they are upgraded due to version bumps and such. That is dangerous, see other replies in this thread for the reasons why. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpZBBO7Qwq9a.pgp Description: PGP signature
Re: linking problems with heimdal in base (ports version works)
On Sunday, 16. October 2005 09:06, Igor Pokrovsky wrote: On Fri, Oct 14, 2005 at 09:49:51PM +0200, Michael Nottebrock wrote: On Friday, 14. October 2005 21:11, Igor Pokrovsky wrote: Still, isn't it strange that the kerberos libs don't have any dependencies registered? A quick check shows that they are almost the only libs in /usr/lib that have zero output from ldd. Probably they are statically linked. No, static libraries don't come with an .so extension. :-) No, you missed my point. I mean that kerberos libs are dynamic but linked against other libraries statically. If they were, there would be no problem in the first place. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp7dhgifPldu.pgp Description: PGP signature
Re: 6.0 release date and stability
On Sunday, 16. October 2005 18:34, Ronald Klop wrote: There are a couple of options: 1. Do not remove old (5.4) libraries. All 5.4 libs wil still be found. 2. Remove old libraries and install ports/misc/compat5x. All 5.4 lib wil still be found. 3. Remove old libraries and use /etc/libmap.conf to map the old libs on the new ones. 4. Recompile every port, so all dependencies are the 6.0 libs. 1. and 2. are not an option if you plan on eventually compiling new ports after the upgrade - you will most certainly get mixed linkage, which will result in runtime errors. Compat5x should only be used for leaf-ports (i.e, applications and libraries which aren't linked to anything else) - for example software that is distributed as dynamically linked binaries only. Option 4 is certainly the safest thing to do (and you could just upgrade from binary packages instead of recompiling). -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpdx8CqRe2PP.pgp Description: PGP signature
Re: linking problems with heimdal in base (ports version works)
On Friday, 14. October 2005 16:04, Palle Girgensohn wrote: This gives me problems. I maintain the postgresql ports, and postgresql supports Kerberos. Problem is, when installing the heimdal port, everything works fine, but when using the base heimdal, I can't get programs linking with postgresq's libpq.so to link, since the configure scripts cannot find symbols that are in for example libasn1.so. Most ports seem to only pick up the -lkrb5, not all the other libs needed. Then those ports are buggy. The respective configure scripts should run krb5-config --libs and use that output to determine which additional libraries need to be linked in. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpW46uFRcP5W.pgp Description: PGP signature
Re: linking problems with heimdal in base (ports version works)
On Friday, 14. October 2005 17:29, Michael Nottebrock wrote:
On Friday, 14. October 2005 16:04, Palle Girgensohn wrote:
This gives me problems. I maintain the postgresql ports, and postgresql
supports Kerberos. Problem is, when installing the heimdal port,
everything works fine, but when using the base heimdal, I can't get
programs linking with postgresq's libpq.so to link, since the configure
scripts cannot find symbols that are in for example libasn1.so. Most
ports seem to only pick up the -lkrb5, not all the other libs needed.
Then those ports are buggy. The respective configure scripts should run
krb5-config --libs and use that output to determine which additional
libraries need to be linked in.
FWIW: As a stop-gap solution until this can be fixed in the upstream sources,
you probably can do something like this in the port Makefile:
HEIMDAL_CFLAGS!=krb5-config --cflags
HEIMDAL_LDFLAGS!=krb5-config --libs
CONFIGURE_ARGS+=CFLAGS=${HEIMDAL_CFLAGS} LDFLAGS=${HEIMDAL_LDFLAGS}
--
,_, | Michael Nottebrock | [EMAIL PROTECTED]
(/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
\u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org
pgplW66PDEMUM.pgp
Description: PGP signature
Re: linking problems with heimdal in base (ports version works)
On Friday, 14. October 2005 19:08, Palle Girgensohn wrote: I'm actually doing that already, but postgresql build process bugs out somehow. I'll have to dedicate some time to this, I guess. Still, isn't it strange that the kerberos libs don't have any dependencies registered? I don't think so - after all, the main purpose of the krb5-config utility is to record the dependencies. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpycrC3j5uT8.pgp Description: PGP signature
Re: linking problems with heimdal in base (ports version works)
On Friday, 14. October 2005 21:11, Igor Pokrovsky wrote: Still, isn't it strange that the kerberos libs don't have any dependencies registered? A quick check shows that they are almost the only libs in /usr/lib that have zero output from ldd. Probably they are statically linked. No, static libraries don't come with an .so extension. :-) -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpDqR3JRKBMU.pgp Description: PGP signature
Re: Advice sought on upgrading from 4.11-R to 5.4...
On Thursday, 22. September 2005 00:23, Brad Knowles wrote: At 11:34 PM +0200 2005-09-21, Erik Trulsson wrote: And you should of course also read /usr/src/UPDATING as usual. That's the current version of the file from the 5.x tree, right? Is there any obvious way to see what this is without going ahead and downloading all the source anyway? http://www.freebsd.org/cgi/cvsweb.cgi/src/UPDATING?rev=1.342.2.30content-type=text/x-cvsweb-markuponly_with_tag=RELENG_5 -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp8woGWeaH05.pgp Description: PGP signature
Re: Memory requirements between releases
On Saturday, 13. August 2005 10:32, Peter Jeremy wrote: 24MB should be adequate as a SOHO wireless router/NAT box but doing compilations will stress it significantly (as you've noticed). Probably stating the obvious here, but that's where those fine binary packages FreeBSD builds from ports are really convenient. :) -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpBJxYs3doej.pgp Description: PGP signature
Re: [RELENG_6] idle thread statistics not correct?
On Friday, 12. August 2005 15:43, John Baldwin wrote: [ Grrr, stupid kmail smart quoting always screws up formatted output, wish I could turn it off ] Actually you can: Settings/Configure Kmail/Composer, on the General tab. I guess what you really want to turn off (sometimes) is Word Wrap at ... (on the same tab). -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpFfplegNeSA.pgp Description: PGP signature
Re: need help linking??
On Tuesday, 26. July 2005 17:06, Eriq Lamar wrote: A programmer needs your help to get his program to compile properly on freebsd. Presently he has no problems in Linux and winblows, but I could not get it running in 4.11. This is important to me because it is the strongest free chess program available and he is even giving the source! and so can be made into a port some day. [...] I just tried fruit_21_linux.zip and had no problems with linking whatsoever. There's a little compile-time glitch on 4.x due to to 4.x being overly sensitive to include-order, the attached patch fixes it. On 5.x, it compiles out of the box. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --- posix.cpp.orig Tue Jul 26 21:00:15 2005 +++ posix.cpp Tue Jul 26 21:00:35 2005 @@ -12,11 +12,11 @@ #if defined(_WIN32) || defined(_WIN64) # include windows.h #else // assume POSIX -# include sys/resource.h // # include sys/select.h # include sys/time.h # include sys/types.h # include unistd.h +# include sys/resource.h #endif #include posix.h pgpQODvwtdS3n.pgp Description: PGP signature
Re: dangerous situation with shutdown process
On Friday, 15. July 2005 21:14, Matthias Buelow wrote: Why am I arguing in an uphill battle here? important to the FreeBSD community? Such issues should not even have to be discussed at all! I completely agree, and there's really no point in arguing with people who are happy to throw dollars at the problem rather than fixing it either. At this point, code is needed. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpF1Rh0vZeFA.pgp Description: PGP signature
Panic: don't do that ... while unloading snd_ich.ko
Readily reproducable, 5.4-STABLE as of last week. Kernel messages prior to panic (from memory): pcm0: unregister: mixer busy WARNING: Driver mistake: destroy_dev on 30/3 Backtrace: GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd. #0 0xc04ea796 in doadump () at pcpu.h:160 160 __asm __volatile(movl %%fs:0,%0 : =r (td)); (kgdb) bt #0 0xc04ea796 in doadump () at pcpu.h:160 #1 0xc04eacc0 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:413 #2 0xc04eaf54 in poweroff_wait (junk=0xc067dd2a, howto=-1066935045) at /usr/src/sys/kern/ker #3 0xc04c455a in idestroy_dev (dev=0xc337e190) at /usr/src/sys/kern/kern_conf.c:563 #4 0xc04c4684 in destroy_dev (dev=0xc06d3428) at /usr/src/sys/kern/kern_conf.c:612 #5 0xc07a0f6c in ?? () #6 0xc06d3428 in devt_stash () #7 0xc2379980 in ?? () #8 0xc2379980 in ?? () #9 0xc2324200 in ?? () #10 0xe96c2c18 in ?? () #11 0xc07b0d7e in ?? () #12 0xc2379980 in ?? () #13 0xc2379980 in ?? () #14 0xc2379980 in ?? () #15 0xe96c2c30 in ?? () #16 0xc04feb37 in device_detach (dev=0xc23b65e0) at /usr/src/sys/kern/subr_bus.c:2301 Previous frame inner to this frame (corrupt stack?) -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpHeBuBxl3zW.pgp Description: PGP signature
Re: kpdf crashes with LIBPTHREAD_SYSTEM_SCOPE set (Was: Re: FreeBSD MySQL still WAY slower than Linux)
On Tuesday, 28. June 2005 06:43, Daniel Eischen wrote: I can't reproduce it in -current. -bash-2.05b$ uname -a FreeBSD orion 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Thu May 5 13:29:41 EDT 2005 Yeah, you already said that before. So where do we go from here? Should I try to get a backtrace of the crash? With gdb? Ktrace? Should I compile libpthread of other parts of the system with special debug flags? Should I report this on freebsd-threads instead? Or should I just let the issue go? -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgplrvZCQCI9J.pgp Description: PGP signature
Re: libstdc++ version bump.
On Tuesday, 28. June 2005 18:21, Scot Hetzel wrote: Are you sure that the problem is with libstdc++ and not the above libraries? Yes, it's a well known-fact. In fact there might have been a break of ABI backwards-compatibility between gcc 3.3 and 3.4, too, but I'm not sure. Was there any changes to libstdc++ between 5.4 5.3? No. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpsX0HPTyYqs.pgp Description: PGP signature
Re: kpdf crashes with LIBPTHREAD_SYSTEM_SCOPE set (Was: Re: FreeBSD MySQL still WAY slower than Linux)
On Monday, 20. June 2005 19:17, Daniel Eischen wrote: Works here on a month or two old -current. I'm using /usr/local/ant/docs/appendix_e.pdf as a test (it's 60 pages or so). Crashes for me: [EMAIL PROTECTED]:127:~ env LIBPTHREAD_SYSTEM_SCOPE=1 kpdf 'http://drtc.isibang.ac.in/%7Eprachi/apache-ant-1.5.4/docs/appendix_e.pdf ' Bus error [EMAIL PROTECTED]:1:~ kpdf 'http://drtc.isibang.ac.in/%7Eprachi/apache-ant-1.5.4/docs/appendix_e.pdf ' [EMAIL PROTECTED]:0:~ I don't have a -CURRENT machine to test. Try -stable. I just retried with today's 5.4-STABLE - still crashes. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp2LUSMeYtz6.pgp Description: PGP signature
Re: Portupgrade in Xfree86 pkg failed
On Sunday, 26. June 2005 01:18, Ted Mittelstaedt wrote: If there was significant product differentiation between xfree86 and xorg, then there would be a reason to keep both. Right now there is not and with the difficulty in X development, there won't soon be. There's already quite a delta on the video driver level. Here's the litmus test - would you pull a popular port if it breaks on 4 but not on 5? 'nuff said. What does that prove? It wouldn't get pulled if it would break the other way around either, but be marked BROKEN for the appropriate branch. The FreeBSD project agrees with me, if they did not then they would have rewritten the installer to make it optional which one to pick. If it were possible to run software from binary packages built against Xorg on XFree86 (or vice-versa) hassle-free, that would be an option. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpe7lpvWQDSc.pgp Description: PGP signature
Re: update libpthread
On Tuesday, 21. June 2005 17:30, Khanh Cao Van wrote: I find the libpthread in the src/lib/libpthread on the cvs server , but I could not get only that source code to my PC . In the cvs file I edited : *default host=cvsup.freebsd.org *default base=/usr *default prefix=/usr/local *default release=cvs tag=RELENG_4 *default delete use-rel-suffix # If your network link is a T1 or faster, comment out the following line. *default compress ## Ports Collection. # # The easiest way to get the ports tree is to use the ports-all # mega-collection. It includes all of the individual ports-* # collections, ports-all src-all and the src-all will get all the sourcecode down . I did not want this happend , just the sourcecode of my expecial packet only . How could I get only the libpthread down ? You don't need libpthread, you need libc_r. I suggest you follow the advice from the jdk port Makefile and upgrade the complete FreeBSD 4.7 sources to a 4-STABLE after February 2003: *default host=cvsup.freebsd.org *default base=/usr *default prefix=/usr/local *default release=cvs tag=RELENG_4 *default date=2003.03.01.00.00.00 *default delete use-rel-suffix Then cd /usr/src and make buildworld and make installworld. I'd personally recommend to make and install a new kernel as well to be on the safe side, but that's your call. The jdk port should build after that. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpqciK7ecXAR.pgp Description: PGP signature
kpdf crashes with LIBPTHREAD_SYSTEM_SCOPE set (Was: Re: FreeBSD MySQL still WAY slower than Linux)
On Saturday, 11. June 2005 17:05, Daniel Eischen wrote: You can set the environment variable LIBPTHREAD_SYSTEM_SCOPE to force libpthread to use system scope. I've played around with that variable (set it in .xsession) and found that kpdf (from graphics/kdegraphics3) will reproducably crash if it is set. Unsetting it in a shell running on top of a KDE started with mentioned .xsession and launching kpdf from there will remedy the problem. The backtrace I get is probably useless, let me know if (and how) I should recompile libpthread or other system libraries with debug symbols ... This is on 5.4-STABLE, two-three weeks old. Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp75sKZRZku1.pgp Description: PGP signature
Re: kpdf crashes with LIBPTHREAD_SYSTEM_SCOPE set (Was: Re: FreeBSD MySQL still WAY slower than Linux)
On Monday, 20. June 2005 18:53, Daniel Eischen wrote: Works here on a month or two old -current. I'm using /usr/local/ant/docs/appendix_e.pdf as a test (it's 60 pages or so). Crashes for me: [EMAIL PROTECTED]:127:~ env LIBPTHREAD_SYSTEM_SCOPE=1 kpdf 'http://drtc.isibang.ac.in/%7Eprachi/apache-ant-1.5.4/docs/appendix_e.pdf' Bus error [EMAIL PROTECTED]:1:~ kpdf 'http://drtc.isibang.ac.in/%7Eprachi/apache-ant-1.5.4/docs/appendix_e.pdf' [EMAIL PROTECTED]:0:~ I don't have a -CURRENT machine to test. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpwHbXsgShVs.pgp Description: PGP signature
Re: hw.ata.atapi_dma in 5.4-RELEASE-p1
On Sunday, 22. May 2005 17:29, Janet Sullivan wrote: I am unable to get my DVD or CD drives out of PIO4 mode on two machines. One has an ICH3 controller, the other is Nforce2 based. When I put hw.ata.atapi_dma=1 in /boot/loader.conf and reboot, I'm still stuck in PIO4. What am I doing wrong? The drives probably don't support any UDMA modes. WDMA modes aren't enabled for atapi devices because there's a very large number of devices which don't implement them right or not at all, yet claim to support them. You can enable whatever DMA modes those drives support with the atacontrol utility after the kernel has booted up. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpqUzN9MX1Hu.pgp Description: PGP signature
Re: *bsd games.
On Thursday, 28. April 2005 05:03, None wrote: now this is where the plan comes in - what about some upgrade to the default bsd world? FreeBSD seems like the BSD that could support it. Almost all of the 44BSD-Lite games were removed from FreeBSD 5-CURRENT over two years ago to save space and development resources for more important things - that ship has sailed I'm afraid. FreeBSD 5 only ships a select few of the 44BSD-Lite games, notably those which are more utilities than games (like fortune, caesar, factor, primes, morse ...). -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpLKulPxrTtl.pgp Description: PGP signature
Re: USB mouse troubles
On Thursday, 7. April 2005 14:08, Jilles Tjoelker wrote: On Tue, Apr 05, 2005 at 09:17:55PM +0200, Michael Nottebrock wrote: FreeBSD 5.x has had funky issues with usb mice for as long as I've been using a usb mouse with it, but since it almost works ok with the default configuration, I never got around to complain about it. ;-) AFAIK FreeBSD 4.x has the same issues and some more, e.g. systems with more than one USB bus require a manual MAKEDEV for hotplugging to work correctly (as only /dev/usb0 is created by default). FreeBSD 4 (with device nodes existing, granted) does at least not have the problem with the mouse going dead when returning from single user mode. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpzeMb2VjjMH.pgp Description: PGP signature
Re: FreeBSD mpd PPTP client connection to SnapGearLITE+
On Tuesday, 5. April 2005 16:12, Walentyn wrote: patches to give ppp MMPE functionality. From the quoted manual section, it seems that it has rudimentary functionality if you compile it yourself. (I prefer NOT to roll my own.) No, DES is enabled by default. The manpage mentions it because the NO_OPENSSL/NOCRYPT switches can turn it off. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpwf0HicQkyF.pgp Description: PGP signature
USB mouse troubles
FreeBSD 5.x has had funky issues with usb mice for as long as I've been using a usb mouse with it, but since it almost works ok with the default configuration, I never got around to complain about it. ;-) However: In various sitations and configurations, USB mice are not picked up. - With a GENERIC kernel and all of the usb support in the kernel, usb mice are usually recognized on boot, but they will cease to work after going single user and back to multiuser again. The /dev/ums0 device doesn't even get removed, but the mouse is dead. Unplugging and replugging usually gets it going again. - With all of usb compiled as modules and usbd enabled in rc.conf, ums usually doesn't even get loaded, but usbdevs will show the mouse plugged in. Even subsequent unplugging and replugging will not get ums loaded. Manually loading ums doesn't get the mouse working either, an unplug/replug is necessary first. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpfAq8VXrTd4.pgp Description: PGP signature
Re: kdelibs portupgrade prob
On Tuesday, 22. March 2005 12:26, Warren wrote: === kdelibs-3.4.0 conflicts with installed package(s): kdebase-3.3.2_2 Read /usr/ports/UPDATING -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp9N33caUr9w.pgp Description: PGP signature
Re: binary update problem with portupgrade
On Monday, 14. March 2005 11:27, Matej Ornest wrote: Hi, I'm trying to upgrade my FreeBSD-5.3-Release installation to the latest version with portupgrade, but I don't want to compile all those megamonsters like KDE, so I'd like to use packages for upgrade. But portupgrade cannot find appropriate packages for upgrade. It looks for them on ftp://ftp.freebsd.org/pub/freebsd/ports/i386/packages-5.3-release/All/ which is wrong... Run portupgrade like this: env PACKAGESITE=ftp://ftp.mirror.freebsd.org/pub/FreeBSD/ports/i386/packages-5-stable/Latest portupgrade -Pa And replace mirror with an appropriate country code (like cz). -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp9PQlYNDBlu.pgp Description: PGP signature
Re: binary update problem with portupgrade
On Tuesday, 15. March 2005 10:28, Michael Nottebrock wrote: Run portupgrade like this: env PACKAGESITE=ftp://ftp.mirror.freebsd.org/pub/FreeBSD/ports/i386/packages- 5-stable/Latest portupgrade -Pa ^ / - don't forget the trailing slash like I did And replace mirror with an appropriate country code (like cz). -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp9dHhSU0bON.pgp Description: PGP signature
Re: Atheros chip support in 4.11 updated if_rl.c code location?
On Saturday, 12. March 2005 03:28, Geraghty, Dewayne wrote: Has anyone performed an Atheros wireless port to 4.11. I noted the ath chip is described in the 5.3 man page with a version date of 4.11. Consequently I purchased two atheros wireless devices, and upgraded my 4.8 boxes to 4.11. Unfortunately there is no Atheros (if_ath) support in 4.11. (My purchase decision was based on the 5.3 man page. Silly me) Also I've noted that the if_rl code has been updated and submitted for 5.4. Can someone please point me to the incarnation to pull this code, so I can install it on my 4.x series. Backports of device drivers to FreeBSD 4 are, in general, very VERY unlikely (FreeBSD 4 is a dead-end branch now) and nontrivial to do due the massive differences between FreeBSD 5 and FreeBSD 4. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgps47asmUR42.pgp Description: PGP signature
Re: Xorg 6.8.1
On Monday, 28. February 2005 03:25, Gary Kline wrote: On Sun, Feb 27, 2005 at 11:36:43AM +1030, Daniel O'Connor wrote: On Sun, 27 Feb 2005 09:12, Gary Kline wrote: How about adjusting the configuration then? There is utterly no xorg.conf file; the xorg probes set the resolution to the max (1600x1200), and the display `quivers' --for lack of a better word. So far my attemps with xorgcfg and xorgconfig work with startx only. And the display is off-center (leftward). Try (as root) X -configure cp /root/xorg.conf /usr/X11R6/lib/X11/xorg.conf Then edit /usr/X11R6/lib/X11/xorg.conf Look up the 'Section Screen' part and add 'DefaultDepth 24' in it then edit the Modes line to have the resolution you want there. FYI X.Org should have just used your XF86-4 config file by default. XF86Config bombed instantly, even with startx. Try looking at /var/log/Xorg.0.log to find out what's bombing. It might just be the keyboard driver, IIRC it got renamed from keyboard to kbd. The config format is completely compatible. I'm still having troubl getting the Horz and Vert sync numbers right. That's easy: Just find the manual of your CRT and copy over the numbers from the technical data page. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpJnQl29BISd.pgp Description: PGP signature
Re: Xorg 6.8.1
On Sunday, 27. February 2005 02:06, Daniel O'Connor wrote: On Sun, 27 Feb 2005 09:12, Gary Kline wrote: How about adjusting the configuration then? There is utterly no xorg.conf file; the xorg probes set the resolution to the max (1600x1200), and the display `quivers' --for lack of a better word. So far my attemps with xorgcfg and xorgconfig work with startx only. And the display is off-center (leftward). Try (as root) X -configure cp /root/xorg.conf /usr/X11R6/lib/X11/xorg.conf Then edit /usr/X11R6/lib/X11/xorg.conf Or try xorgcfg -textmode -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpufEF7Z9kCp.pgp Description: PGP signature
Re: nice: Badly formed number
On Sunday, 27. February 2005 23:54, Lefteris Tsintjelis wrote: Is nice broken? FreeBSD 5.4-PRERELEASE #0: Sat Feb 26 14:17:21 EET 2005 # nice -n 5 date nice: Badly formed number. csh has a builtin nice command, with a different syntax than nice(1). -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpNyRAx9jIgK.pgp Description: PGP signature
Re: Xorg 6.8.1
On Saturday, 26. February 2005 13:05, Godwin Stewart wrote: On Sat, 26 Feb 2005 22:25:24 +1030, Daniel O'Connor [EMAIL PROTECTED] wrote: You don't need to update a port just because it depends on Xorg. The X API is quite stable so you can update just Xorg without expecting any problems. (I did XFree86 - Xorg with zero problems for example) No, the problem's the other way round. Every time I want to portupgrade something else, portupgrade also wants to upgrade Xorg. edit /usr/local/etc/pkgtools.conf, find the HOLD_PKGS = [ line and change it to HOLD_PKGS = [ 'bsdpan-*', 'xorg-*', 'imake-*', ] I've been using that for a long time now, since Xorg 6.8.1 breaks vt-switching for me. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpjaefiDvlRf.pgp Description: PGP signature
Re: Xorg 6.8.1
On Saturday, 26. February 2005 22:19, Gary Kline wrote: On Sat, Feb 26, 2005 at 09:49:00PM +0100, Michael Nottebrock wrote: On Saturday, 26. February 2005 13:05, Godwin Stewart wrote: On Sat, 26 Feb 2005 22:25:24 +1030, Daniel O'Connor [EMAIL PROTECTED] wrote: You don't need to update a port just because it depends on Xorg. The X API is quite stable so you can update just Xorg without expecting any problems. (I did XFree86 - Xorg with zero problems for example) No, the problem's the other way round. Every time I want to portupgrade something else, portupgrade also wants to upgrade Xorg. edit /usr/local/etc/pkgtools.conf, find the HOLD_PKGS = [ line and change it to HOLD_PKGS = [ 'bsdpan-*', 'xorg-*', 'imake-*', ] I've been using that for a long time now, since Xorg 6.8.1 breaks vt-switching for me. Tweaking pkgtools.conf may help me if I move back to XFree, and it's looking like I have no choice. xorg autoconfigs itself to run at too high a res and nothing I do fixes it. How about adjusting the configuration then? So, without highjacking this thread _too_ much, can anybody give me the cmds to get back to XFree-4 on my 5.3 install? You really don't want to do that except you're absolutely desparate (and the above problem doesn't fit that category). Using XFree86 on 5.3 will make your system incompatible with binary packages for 5.3 and for 5-STABLE. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgprVxFKXNECK.pgp Description: PGP signature
Re: Problems installing ruby18-1.8.2_2
On Tuesday, 22. February 2005 15:42, Mike Jakubik wrote: Mike said: On Tue, 22 Feb 2005, Mike Jakubik wrote: Hello, There seems to be a problem installing ruby18 on 5-STABLE AMD64. It compiles cleanly however. No special flags in make.conf. I've had this problem for 2 weeks now on my AMD64.. After ctrl-c on the make install, miniruby is still running. I finally gave up and grabbed the package off ftp.freebsd.org. Great.. I have emailed the port maintainer and cc'd ports yesterday. But no replys, thought id try here :P Ehm, you got a *lot* of replies on ports@, including patches to test (the first person to reply cut you from cc however). You might want to check the archives. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpe9EYrfPWca.pgp Description: PGP signature
Re: 5.2.1 - Freenet6 TSPC Client dumps core
On Friday, 11. February 2005 00:25, Karl M. Joch wrote: Hello, i had the verion 1 of the freenet6 client running for a long time. now, after upgrading to 2.1.1 on a 5.2.1 box the tspc client dumps core. Works fine on a 5.2.1 box of mine, FWIW. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpsuNirUGU6K.pgp Description: PGP signature
Re: Feb 2005 Snapshots for FreeBSD available
On Tuesday, 15. February 2005 17:29, Nate Lawson wrote: Michael Nottebrock wrote: On Tuesday, 15. February 2005 07:28, Nate Lawson wrote: Are there any tags for these? That may be too heavyweight but at least publishing the exact UTC date for the build would be good. That would help us track down in bug reports what code the user has, especially when it's from areas that are under active development. The snapshots on snapshots.[jp|se].freebsd.org are date-suffixed (however, those servers don't build snaps for all platforms). I'm talking hour/min./second, thanks. Well, the builds on jp are always generated from source of 15:00 UTC of that date. The se machine probably uses a fixed time as well, but I can't look it up at the moment (hardware troubles at the se site). -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0KQg38mtlv.pgp Description: PGP signature
Re: Feb 2005 Snapshots for FreeBSD available
On Tuesday, 15. February 2005 17:41, Michael Nottebrock wrote: On Tuesday, 15. February 2005 17:29, Nate Lawson wrote: Michael Nottebrock wrote: On Tuesday, 15. February 2005 07:28, Nate Lawson wrote: Are there any tags for these? That may be too heavyweight but at least publishing the exact UTC date for the build would be good. That would help us track down in bug reports what code the user has, especially when it's from areas that are under active development. The snapshots on snapshots.[jp|se].freebsd.org are date-suffixed (however, those servers don't build snaps for all platforms). I'm talking hour/min./second, thanks. Well, the builds on jp are always generated from source of 15:00 UTC of that date. The se machine probably uses a fixed time as well, but I can't look it up at the moment (hardware troubles at the se site). And thinking about it, so probably does the snapbuilder which produces those snaps on ftp.freebsd.org ... Scott? :-) -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpCiMnMUbSE3.pgp Description: PGP signature
Re: ULE status
On Tuesday, 8. February 2005 13:07, Mipam wrote: Hi, I saw several changes to sched_ule.c in the 5 stable branch. Beneath is one of them: http://lists.freebsd.org/pipermail/cvs-src/2005-February/039863.html Is the ULE scheduler still far from stable in RELENG_5 or not? You can now compile a kernel with options SCHED_ULE again. How well it works is for yourself to determine :-) (I've been using it on my UP machine here since yesterday only). -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp7jI1hiX1Wv.pgp Description: PGP signature
Re: ULE status
On Tuesday, 8. February 2005 13:38, Mipam wrote: Okay, so then the ULE sched is fairly stable then? But it's still not the default scheduler? It will never become the default scheduler in 5.x again. 5.x went into -STABLE mode with 4BSD, and that's why the default will remain 4BSD. Is it safe to use right now under RELENG_5 or not? As already said, you need to try *yourself*. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp2wMMDSHfNd.pgp Description: PGP signature
Re: ULE status
On Tuesday, 8. February 2005 13:43, Ion-Mihai Tetcu wrote: There used to be a panic when using rtprio to raise the priority of a running process, do you know if it's fix ? I never got any panics with ULE back when it was available, so I can't tell. If you care about ULE, turn it on and see for yourself - more testers make better testing. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpOaCVkIwxdC.pgp Description: PGP signature
Re: ULE status
On Tuesday, 8. February 2005 14:02, Mipam wrote: Okay clear, but the fact that it's in 5-stable suggests the it's stable to use, else why would it be in 5-stable. The changes that have been merged to stable have been tested for some time in 6-CURRENT, so they're not completely experimental, yes. Maybe i'm completly wrong in this interpretation? I'm not sure what your interpretation is. If you go by your own definition (what's in -stable should be safe to use), why do you ask at all? In any case, the ULE MFC commits are only a few days old, so there's naturally not much feedback available, good or bad. If you want to play it safe, wait a week or a month and monitor this lists for complaints before trying it yourself. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp1zRaPb8J3h.pgp Description: PGP signature
Re: ULE status
On Tuesday, 8. February 2005 14:22, Ion-Mihai Tetcu wrote: On Tue, 8 Feb 2005 14:51:17 +0200 (EET) Viktor Ivanov [EMAIL PROTECTED] wrote: On Tue, Ôåâðóàðè 8, 2005 14:43, Ion-Mihai Tetcu êàçà: Could you tell us again after a week ? There used to be a panic when using rtprio to raise the priority of a running process, do you know if it's fix ? I never had those, and I usually run mplayer with rtprio 30... Though mplayer never uses much CPU, only when playing WMV9. Sorry I can't test the new patches too 'cause the WS is not available now. On changing, not running from the beginning rtprio 31 -mpayer_pid Works for me (with 0, too). -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpTlAYdkU2b7.pgp Description: PGP signature
Re: 5.x concerns
On Sunday, 6. February 2005 16:01, Chris wrote: 4 - compatiblity, I remember using 5.2.1 and pretty much all software worked well in that and then they did the bind defaulting to base and libs version jump, why wasnt this done in 5.0 I personally told lots and lots of people to NOT use 5.2.1-Release and wait for 5.x to become a stable branch instead, but it still got installed far more often than it really should have. 5.2.1 was still a Technology Preview release - it was a snapshot of FreeBSD 5-CURRENT, just as 5.0-RELEASE, 5.1-RELEASE and 5.2-RELEASE were before. In retrospect, there probably should have been more warning signs on the website and the documentation to point out that fact. Also, there probably should have been more feature and driver backports to FreeBSD 4, so less people would have been tempted by the better hardware support and general friendlyness of FreeBSD 5-CURRENT. Too late to change now, but perhaps something that should be remembered for the next time FreeBSD goes through a similar transition period. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpKs53pog7eE.pgp Description: PGP signature
Re: sometimes 5.3-RELEASE-p5 is stuck at the last steps of shutdown
On Thursday, 27. January 2005 10:04, Rostislav Krasny wrote: --- Michael Nottebrock [EMAIL PROTECTED] wrote: Rostislav Krasny wrote: Hello all. I use FreeBSD 5.3-RELEASE-p5 on i386. Sometimes my system is stuck at the last steps of shutdown. Following quoting is what I saw yesterday when my system was stuck again (the last lines): init: some processes would not die; ps axl advised You should try to find out what's causing that. I personally got this a few times, too, when a mount command got badly stuck because trouble with the hdd. I don't know how could I find, during the shutdown, what are those unkillable processes. I didn't find anything suspicious in /var/log/messages. Could init(8) be configured/patched to print/log a list of such unkillable processes during the shutdown? Probably, but doing shutdown now (i.e., going into single user) instead of an actual power-down might also work. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpfMgVOAtzpq.pgp Description: PGP signature
Re: Linking problems with gcc 3.4.2 and glibc on 5.3-stable
On Wednesday, 26. January 2005 13:03, Chris wrote: there is also a bug which prevents compiling of ezbounce and psybnc, I wonder how much testing went into the new gcc compiler or was it just bundled into the release, considering this is the reccommended release for production server's now this is a bad oversight, I think the gcc should be changed in the next patch level back to 3.3.6. Not gonna happen (would break binary compat). If you think you have found bugs in gcc, try to get them fixed upstream, preferably in the gcc-branch -STABLE is currently using (i.e., right now 3.4). Updates of the base-gcc within the same branch are possible if warranted. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpI3PJqHWkoP.pgp Description: PGP signature
Re: sometimes 5.3-RELEASE-p5 is stuck at the last steps of shutdown
Rostislav Krasny wrote: Hello all. I use FreeBSD 5.3-RELEASE-p5 on i386. Sometimes my system is stuck at the last steps of shutdown. Following quoting is what I saw yesterday when my system was stuck again (the last lines): init: some processes would not die; ps axl advised You should try to find out what's causing that. I personally got this a few times, too, when a mount command got badly stuck because trouble with the hdd. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: correct value for LANG variable
On Saturday, 22. January 2005 16:52, Björn König wrote: I am a bit confused. Neither de_DE.ISO-8859-1 nor de_DE.ISO8859-1 work properly in all cases. setenv LANG de_DE.ISO8859-1 echo abcdef uvwxyz | tr '[a-z]' '[A-Z]' ABCDEF ÚWXYÝ] This is the correct locale name, but don't use tr like that, you can't rely on that to work correctly with charsets which aren't symmetric in loweruppercase characters (it used to work at some point for the ISO8859-1 [5] locales but ceased after a POSIX related modification to tr). Use tr [:lower:] [:upper:] instead. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpILG8oAmJGV.pgp Description: PGP signature
Re: cannot su?
On Sunday, 16. January 2005 01:07, Ivan Voras wrote: What could be the reasons for su root to not work? I have a user that's in wheel group. Logging in as root works on the console, but su-ing from the user just writes 'Sorry', like the password's wrong. There are no clues in log files. Make sure /usr/sbin/su is suid root (and /usr isn't mounted nosuid). -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp7JevHKBYyG.pgp Description: PGP signature
Re: fsck: broken file system with background check remains broken after bootup
On Wednesday, 5. January 2005 04:29, Wilkinson, Alex wrote: 0n Tue, Jan 04, 2005 at 02:01:22PM +0100, Oliver Fromme wrote: By the way, you can map a key combination (Ctrl-Alt-Del or something else) to the »halt« or »power-down« functions, using kbdcontrol, so it's very easy and intuitive to shut down the machine properly. See the kbdmap(5) manpage for details. This inspires me to ask this question: Is it possible to set up FreeBSD to do a clean shutdown upon a pressing the power button ? It already does out of the box. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpxrjgx3AfpI.pgp Description: PGP signature
Re: libmap.conf and ports
On Wednesday, 5. January 2005 10:33, [EMAIL PROTECTED] wrote: Hi all, I have major problems to compile gpgme-1.0.1 on *some* machines (see below). Before all the compile/link-errors one major question: What about /etc/libmap.conf and the mapping of libc_r to libpthread? It was once recommended and I never heard anything about it. Is it still recommended? Is it mandatory? Or forbidden? Or simply no longer necessary? Depends. If you have ports installed which still link to libc_r, it's better to have the mapping in place. However, it's much preferrable to not have anything linking to libc_r left. The easiest method of finding out is simply moving libc_r out of /usr/lib. If stuff fails, recompile it. Once your system is clean of all references, you can put NOLIBC_R=true into make.conf and avoid compiling/installing it during upgrades completely. And now for the port: I get the following errors during the compilation of gpgme-1.0.1 in the context of a KDE-upgrade: ** t-thread1.o(.text+0x857): In function `main': : undefined reference to `pthread_create' t-thread1.o(.text+0x87a): In function `main': : undefined reference to `pthread_create' t-thread1.o(.text+0x88b): In function `main': : undefined reference to `pthread_join' t-thread1.o(.text+0x89c): In function `main': : undefined reference to `pthread_join' Try experimenting with the PTH option on the machines that give you trouble. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpqw8jzMtWgG.pgp Description: PGP signature
