Keyboard disabled in X
I get a strange problem when GDM is starting. My PC is an old PII with ASUS P2B motherboard, with PS/2 keyboard and mouse. The first time X (GDM) starts up, the keyboard is disabled, while it is working in the console while booting. The mouse is working fine, but I cannot type anything, nor switch to console using ctrl-alt-Fx (where x=1-6). If I click on the Actions menu, and on anything that restarts the X server (like the XDMCP chooser for example), I get the keyboard back. -- Jérôme Warnier FLOSS Consultant http://beeznest.net
Re: Applications tracing on Debian GNU/kFreeBSD
On Sun, Jul 29, 2007 at 12:04:04AM +0200, Jerome Warnier wrote: My Debian GNU/kFreeBSD machine is getting slower everyday. I would like to start some tracing of applications (of which Perl), but no tool like strace or truss seem to be available. The only tool I found is bonnie++, but I can only diagnose disk throughput with it. Am I missing something? Should I look to other tools? The equivalent of strace on GNU/kFreeBSD is ktrace. Then you have to use kdump to get the trace. -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Debian GNU/(k)NetBSD and sparc32 hardware?
[CC to debian-bsd as it's relevant there, too] On Sun, Jul 29, 2007 at 03:13:03PM +0200, Maciej Jan Broniarz wrote: Dnia 2007-07-29, o godz. 15:11:55 Ulrich Teichert [EMAIL PROTECTED] napisał(a): I tend to differ. It will be easier to fix the Linux kernel, find a maintainer for it and then get it into Debian again. We would leveraging the existing work better that way. We will agree on one issue. The main problem is the lack of people working on that port. No matter is it NetBSD or Linux. The Debian GNU/(k)NetBSD port may have a lack of people and support at the moment (I don't know the current status, though). However, it seems that the upstream development of the sparc32 code in the NetBSD kernel is _not_ halted (unlike the upstream Linux support). Can somebody confirm that? Maybe I'll just ask on the resp. NetBSD list.. In that case, a good long-term solution (IMO) would be to bring the Debian GNU/(k)NetBSD (sparc32) port up to speed (or rather: start it, I don't think it exists yet, there was only work for i386 and alpha, IIRC). That may sound like a lot of work (and it probably is), but I think it's mostly Debian-related work, and not kernel maintainence work (as that is done by upstream), so it may be a good option to keep Debian alive on sparc32 hardware. Comments? Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org signature.asc Description: Digital signature
Re: Debian GNU/(k)NetBSD and sparc32 hardware?
Uwe Hermann wrote: [CC to debian-bsd as it's relevant there, too] On Sun, Jul 29, 2007 at 03:13:03PM +0200, Maciej Jan Broniarz wrote: Dnia 2007-07-29, o godz. 15:11:55 Ulrich Teichert [EMAIL PROTECTED] napisał(a): I tend to differ. It will be easier to fix the Linux kernel, find a maintainer for it and then get it into Debian again. We would leveraging the existing work better that way. We will agree on one issue. The main problem is the lack of people working on that port. No matter is it NetBSD or Linux. The Debian GNU/(k)NetBSD port may have a lack of people and support at the moment (I don't know the current status, though). However, it seems that the upstream development of the sparc32 code in the NetBSD kernel is _not_ halted (unlike the upstream Linux support). Maybe, but NetBSD kernel does not correctly work on sun4m/SMP, like Linux. Today, no one OS can be used on sun4m/SMP workstations, and I think that it will be easier to fix linux 2.6 sparc32 kernel than work on debian/xBSD sparc32 port. Regards, JKB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian GNU/(k)NetBSD and sparc32 hardware?
Hi, On Sun, Jul 29, 2007 at 03:13:03PM +0200, Maciej Jan Broniarz wrote: Dnia 2007-07-29, o godz. 15:11:55 Ulrich Teichert [EMAIL PROTECTED] napisa=C5=82(a): I tend to differ. It will be easier to fix the Linux kernel, find a maintainer for it and then get it into Debian again. We would leveraging the existing work better that way. We will agree on one issue. The main problem is the lack of people working on that port. No matter is it NetBSD or Linux. Right. The Debian GNU/(k)NetBSD port may have a lack of people and support at the moment (I don't know the current status, though). However, it seems that the upstream development of the sparc32 code in the NetBSD kernel is _not_ halted (unlike the upstream Linux support). That's not quite true. Dave Miller is still collecting patches, Mark Fortescue, Krzysztof Helt and others are producing them. See the respective posts on [EMAIL PROTECTED] It's just that there is no real maintainer for the port. Can somebody confirm that? Maybe I'll just ask on the resp. NetBSD list.. A quick look at the mailinglist archive at http://mail-index.NetBSD.org/port-sparc/2007/07/ suggests that there is activity as well. I don't know the maintainer state of NetBSD-sparc, though. In that case, a good long-term solution (IMO) would be to bring the Debian GNU/(k)NetBSD (sparc32) port up to speed (or rather: start it, I don't think it exists yet, there was only work for i386 and alpha, IIRC). That may sound like a lot of work (and it probably is), but I think it's mostly Debian-related work, and not kernel maintainence work (as that is done by upstream), so it may be a good option to keep Debian alive on sparc32 hardware. Call me a chicken, but I still think it will be less work to just fix the issues in the kernel and use the existing stuff instead. I agree that a new debian architecture would be more fun, but splitting up the remaining debian sparc32 developers between NetBSD and Linux does not sound too healthy for me. CU, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Channel 13 Is Haunted (Hex Dispensers) 24539 Neumuenster, Germany|Is It Good Or Is It Bad? (Opération S) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian GNU/(k)NetBSD and sparc32 hardware?
Hi, BERTRAND Joël [EMAIL PROTECTED] writes: Maybe, but NetBSD kernel does not correctly work on sun4m/SMP, like Linux. Today, no one OS can be used on sun4m/SMP workstations, and I think that it will be easier to fix linux 2.6 sparc32 kernel than work on debian/xBSD sparc32 port. I had reports stating the contrary, as far as HyperSPARC SMP is concerned (which seems like the less-likely-to-work configuration): http://article.gmane.org/gmane.os.netbsd.ports.sparc/6945 http://article.gmane.org/gmane.os.netbsd.ports.sparc/6943 OTOH, there were mixed reports related to SMP with other processors: http://article.gmane.org/gmane.os.netbsd.ports.sparc/6931 http://article.gmane.org/gmane.os.netbsd.ports.sparc/6914 Thanks, Ludovic.
Re: Debian GNU/(k)NetBSD and sparc32 hardware?
Hi, Ulrich Teichert [EMAIL PROTECTED] writes: That's not quite true. Dave Miller is still collecting patches, Mark Fortescue, Krzysztof Helt and others are producing them. See the respective posts on [EMAIL PROTECTED] It's just that there is no real maintainer for the port. [...] Call me a chicken, but I still think it will be less work to just fix the issues in the kernel and use the existing stuff instead. That's the whole issue. I am under the impression (perhaps wrongfully) that Linux development is moving at a high pace, not considering support of legacy hardware as a high priority. For instance, the first 2.6 releases introduced significant regressions wrt. SPARC32 support compared to 2.4. Only now is 2.6 starting to catch up with 2.4, thanks to the work of a few people. Conversely, it seems that NetBSD values continued support more, judging from the mailing list archives of various ports (including, e.g., the still active VAX port!). It's probably following a much more conservative development approach, less biased towards newer hardware. I agree that a new debian architecture would be more fun, but splitting up the remaining debian sparc32 developers between NetBSD and Linux does not sound too healthy for me. Agreed. In the short term, it does seem easier to try and fix Linux' SPARC32 support. However, I'm wondering whether that would be a good long-term investment. Now, similar issues may also arise with other architectures, too. Thanks, Ludovic. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian GNU/(k)NetBSD and sparc32 hardware?
On Mon, Jul 30, 2007 at 12:22:04AM +0200, Ludovic Courtès wrote: Call me a chicken, but I still think it will be less work to just fix the issues in the kernel and use the existing stuff instead. That's the whole issue. I am under the impression (perhaps wrongfully) that Linux development is moving at a high pace, not considering support of legacy hardware as a high priority. For instance, the first 2.6 releases introduced significant regressions wrt. SPARC32 support compared to 2.4. Only now is 2.6 starting to catch up with 2.4, thanks to the work of a few people. That's wrong. The Linux kernel development works the same way as Debian. If some persons are working on a port, it is supported. If not it is not supported. It does not depend on the fact the hardware is old or not. -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
