Andrei Popov [EMAIL PROTECTED] writes:
There's something fishy with Xkb in 4.3: whenever I try cyrillic
layouts (e.g. ru, bg, ua, etc.), I cannot type a thing (and yes,
cyrillic fonts are listed in font path).
Running xev shows that event is there. Anyone seen the same
behavior/knows what
On Sat, 15 Feb 2003 23:56:50 +0100
Simon 'corecode' Schubert [EMAIL PROTECTED] wrote:
Lately Bruce Evans wrote:
This change makes such opens bogusly time out after 1 second (unless
there is already a writer).
There seems to be a race in fifo_open(): opens for read don't
terminate
In message [EMAIL PROTECTED], Alexander Leiding
er writes:
On Sat, 15 Feb 2003 23:56:50 +0100
Simon 'corecode' Schubert [EMAIL PROTECTED] wrote:
Lately Bruce Evans wrote:
This change makes such opens bogusly time out after 1 second (unless
there is already a writer).
There seems to be
I'n not shure if this is still the place to drop these???
I haven't seen may off these lately on the list...
Found in my dmesg of yesterday, system is now 5 days up:
/usr/src5/sys/kern/kern_lock.c:243: could sleep with buf queue lock locked from
/usr/src5/sys/kern/vfs_bio.c:2104
freebee# uname
Please try setting the locale:
export LC_CTYPE=ru_RU.KOI8-R
or
setenv LC_CTYPE ru_RU.KOI8-R
Yow! Worked -- which is a bit strange: with 4.2 nothing like this was
necessary...
--
Alexander Pohoyda
[EMAIL PROTECTED]
Thanks,
-- Andrei
__
On Sun, 9 Mar 2003, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Alexander Leiding
er writes:
On Sat, 15 Feb 2003 23:56:50 +0100
Simon 'corecode' Schubert [EMAIL PROTECTED] wrote:
Lately Bruce Evans wrote:
This change makes such opens bogusly time out after 1 second (unless
In message [EMAIL PROTECTED], Bruce Evans writes:
I'm sort of expecting Bruce to commit his own patch ?
I'm sort of expecting Poul-Henning to report whether it fixes the
sendmail problem :-). Also, since I don't normally run -current,
changes to it are hard to test properly.
Ahh, my report
From my observations (yes, please correct me if I am wrong), that modules define what
to support in their respective makefiles in the form of
SRC= aaa.c bbb.c opt_*.h
Where opt_*.h are automagically generated if they are not in machine@ (and the
generated files are just empty files that
In article local.mail.freebsd-current/[EMAIL PROTECTED] you write:
From my observations (yes, please correct me if I am wrong), that
modules define what to support in their respective makefiles in the form
of
SRC= aaa.c bbb.c opt_*.h
Where opt_*.h are automagically generated if they are not in
Starting today I noticed this warning at bootup:
WARNING: Driver mistake: make_dev(console) called before SI_SUB_DRIVERS
Is there more info I should supply?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
In message [EMAIL PROTECTED], walt writes:
Starting today I noticed this warning at bootup:
WARNING: Driver mistake: make_dev(console) called before SI_SUB_DRIVERS
Is there more info I should supply?
Ooops. No, that is plenty. I'll fix it.
--
Poul-Henning Kamp | UNIX since Zilog Zeus
Hi, the current -current ata driver panics at boot
when using the CS5530 (National GX1, ex-cyrix).
This driver worked in the past on -current, likely
up until the major rework that appears to be
underway as of 20-Feb-2003 (that is, the creation
of ata-chipset.c, etc.)
Routine
It seems Bruce R. Montague wrote:
I'll look into it, thanks for reporting!
Hi, the current -current ata driver panics at boot
when using the CS5530 (National GX1, ex-cyrix).
This driver worked in the past on -current, likely
up until the major rework that appears to be
underway as of
It seems Bruce R. Montague wrote:
Routine ata_cyrix_setmode() in ata-chipset.c
appears to be assuming that channel-dma has a
valid pointer to a struct ata_dma_funcs, and
that channel-r_bmio is a valid bus resource
id. This is not the case, both channel-dma and
channel-r_bmio (bus master
Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], walt writes:
Starting today I noticed this warning at bootup:
WARNING: Driver mistake: make_dev(console) called before SI_SUB_DRIVERS
Is there more info I should supply?
Ooops. No, that is plenty. I'll fix it.
Yes, fixed now. Thanks.
Hi, re the ata driver and CS5530, Soren Schmidt asked:
Could you please dump the pci reg 0x20 (with pciconf) and
verify that it is endeed 0 ?
Ok (it's _not_ 0):
-
geode# pciconf -r pci0:18:2 0x20
fc01
geode# pciconf -r pci0:18:2 32
fc01
-
Is this 0x20 on F2, F2BAR4? Is
Hi
I didn;t see the original problem, just the reply..
Just one thing to be aware of when using the 5530.
I used a 5530 on the Interjet-II.
It has a terrible bug where it fails if the data being transferred
to/from the disk by DMA is not alligned on a 16 byte boundary. programs
such as newfs
At 7:37 PM +0100 3/5/03, Marcin CIEÂLAK wrote:
See the patches enclosed to emulators/rtc
and emulators/vmware2 ports.
Tested only for -current with:
#define __FreeBSD_version 500104
This does get it so the vmware module will load correctly at
system startup, and I think
Tinderbox FAQ: http://people.FreeBSD.org/~mike/tinderbox.html
--
Rebuilding the temporary build tree
--
stage 1: bootstrap tools
Hi, regarding the CS5530 driver initialization
(ata cyrix) panic, the problem of channel dma
and r_bmio fields being 0 is due to the hardware
PCI config cmd register not having the expected
value. In ata-pci.c / ata_pci_attach() the code
fragment:
/* is busmastering supported ? */
if ((cmd
It seems Bruce R. Montague wrote:
/* is busmastering supported ? */
if ((cmd (PCIM_CMD_PORTEN | PCIM_CMD_BUSMASTEREN)) ==
(PCIM_CMD_PORTEN | PCIM_CMD_BUSMASTEREN)) {
failed because cmd was 0x01 instead of 0x05 (the
PORTEN | BUSMASTEREN is 0x05). The 5530 datasheet
(well, SC1200
Many programs (from ports too) defines _ISOC99_SOURCE to get C99
functions, but we don't sense this define currently. Here is the fix for
review:
--- cdefs.h.bak Wed Oct 23 05:04:06 2002
+++ cdefs.h Mon Mar 10 09:11:01 2003
@@ -360,6 +360,9 @@
#define__POSIX_VISIBLE 198808
In message: [EMAIL PROTECTED]
Garance A Drosihn [EMAIL PROTECTED] writes:
:driver vmmon used unreserved major device number 200
Actually, major numbers 200-253 are 'reserved for local use' and
shouldn't be assigned autmatically.
Warner
To Unsubscribe: send mail to [EMAIL
Soeren Schmidt wrote:
the following patch should solve that:
Yes, it does, Thanks!
All's well that... ends.
- bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
24 matches
Mail list logo
