And there appears to be some more brokenness. I've attached my latest
(verbose) dmesg output. USB support is weird, and (not listed in dmesg)
pccardd is failing to attach my Xircom modem card (which had been working),
claiming "device not configured."
Suggestions? I could Really Use an
On Thu, 2 Dec 1999, Frank Mayhar wrote:
Suggestions? I could Really Use an ethernet connection on this
laptop; right now I have the cardbus card (3Com 575CT) and the pcmcia
card (the 574BT) sitting here, useless.
Looking at the NetBSD driver it appears that the MAC address for the 574
is
On Wed, Dec 01, 1999 at 10:18:26AM +0900, Seigo Tanimura wrote:
If you have an SB card not probed since the import of the bridge
dirvers, could you please apply the following patch, add the logical
ID of your card into sbc_ids[] and see how it works?
(I have asked peter to review the PnP part
Ok, I've checked, and in -current, userland stack boundary alignment
is useless because the stack pointer is initially only aligned on a
word-boundary.
I've also verified that the correct alignment is indeed expected to
apply to frame pointers, i.e. stored frame pointers are at aligned
stack
On Thu, 02 Dec 1999 00:54:11 CST, [EMAIL PROTECTED] wrote:
I recently noticed that ^v (the scroll down a page command in ee) must be
entered twice to scroll down once (i.e. if you hit ^v once it won't do
anything, you must hit it again) on a 4.0-CURRENT system.
Sounds like ncurses takes
Bad MNT PRC: RPC: Remote system error
Hi,
This is a RPC problem, not an NFS problem. Maybe
AIX does not support RPC_UMNTALL ? Because our
support was buggy, noone may have notified it before.
Or do you have problems with the AIX rpc.mountd ?
Can you trace mountd(8) on the AIX side and look
On Thu, 2 Dec 1999 [EMAIL PROTECTED] wrote:
I recently noticed that ^v (the scroll down a page command in ee) must be
entered twice to scroll down once (i.e. if you hit ^v once it won't do
anything, you must hit it again) on a 4.0-CURRENT system. As far as I can
recall, this has been
Hi,
I'm using non-standard 100x37 console mode on my notebook, because in 80x25
text mode letters seems too big for my 12' panel, while other modes doesn't
cover all panel size. So I've patched vidcontrol to switch to the VESA_800x600
100x37 mode (instead of default 80x25) with 8x16 font, and in
Russell Cattelan [EMAIL PROTECTED] writes:
Dag-Erling Smorgrav wrote:
I have a Soundblaster 128 PCI (labeled "MODEL:CT4810") which I can't
get to work with newpcm.
What mother board are you using?
Asus Socket 7.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail
-On [19991201 23:30], Nik Clayton ([EMAIL PROTECTED]) wrote:
On Sun, Nov 28, 1999 at 05:38:57PM +0100, F. Heinrichmeyer wrote:
i tried to make me a new handbook, so i needed jade.
But the newest C++ fashion (g++ under current) has changed to fast for
this very old 1998 heavily template based
Ville-Pertti Keinonen wrote:
Maybe alignment can even be done in the kernel...
It gets messy, it has to be done before putting the env and argv
pointers in place...
Alignment also applies to calling signal handlers...
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
Maybe alignment can even be done in the kernel...
It gets messy, it has to be done before putting the env and argv
pointers in place...
Alignment also applies to calling signal handlers...
Which is easier because sigframe has a constant size and you know what
the relationship
On 2 Dec 1999, Ville-Pertti Keinonen wrote:
...
Note that double-alignment vs. word-alignment can really have 30%
performance impact, at least on an Athlon and one meaningless floating
point microbenchmark (operations on small, fixed-sized
matrices...maybe it isn't even *that* meaningless).
On Wednesday, 1 December 1999 at 4:43:05 +1100, Bruce Evans wrote:
On Tue, 30 Nov 1999, Thomas Stromberg wrote:
[ache wrote]:
"
I see no needs of this change. I have -current dumpon/savecore work with
old entrly like /dev/wd0...
savecore understand both character and old block devices
Note that double-alignment vs. word-alignment can really have 30%
performance impact, at least on an Athlon and one meaningless floating
point microbenchmark (operations on small, fixed-sized
matrices...maybe it isn't even *that* meaningless).
I verified that the default alignment is
Ville-Pertti Keinonen wrote:
If the pessimization persists when the initial alignment is fixed,
then there's a trade-off between a small pessimization for typical
code and a big pessimization for less common (but more often
performance-critical) code.
Performance critical code should
On 2 Dec 1999, Ville-Pertti Keinonen wrote:
The times are for `time make depend; time make' after `make clean; sync;
sleep 1' (2 times for each run). The stack may have been perfectly
misaligned for the default gcc.
It depends on the command line. It took me a while to figure out what
There are other contexts for the same issues anyway. USB has devices
that go away suddenly, and it _is_ designed to be hot-removable, so
people are going to be pulling the plug on network adapters, ZIP
drives, etc. We need drivers that are capable of going away cleanly,
or at least without
Matthew N. Dodd wrote:
On Thu, 2 Dec 1999, Frank Mayhar wrote:
Suggestions? I could Really Use an ethernet connection on this
laptop; right now I have the cardbus card (3Com 575CT) and the pcmcia
card (the 574BT) sitting here, useless.
Looking at the NetBSD driver it appears that the MAC
On Thu, 2 Dec 1999, Frank Mayhar wrote:
Well, if there's _anything_ I can help with, please let me know. I did
dump the CIS using pccardc, but I didn't see the MAC address. I can even
set the laptop up with a serial console and hook it up to a system you can
log into, if that would help.
Jeroen Ruigrok/Asmodai wrote:
-On [19991201 20:01], Russell Cattelan ([EMAIL PROTECTED]) wrote:
Dag-Erling Smorgrav wrote:
I have a Soundblaster 128 PCI (labeled "MODEL:CT4810") which I can't
get to work with newpcm.
What mother board are you using?
There have been some reports of the
Tony Finch wrote:
Maxim Sobolev [EMAIL PROTECTED] wrote:
I'm using non-standard 100x37 console mode on my notebook, because in 80x25
text mode letters seems too big for my 12' panel, while other modes doesn't
cover all panel size. So I've patched vidcontrol to switch to the VESA_800x600
On 02-Dec-99 Maxim Sobolev wrote:
Tony Finch wrote:
Maxim Sobolev [EMAIL PROTECTED] wrote:
I'm using non-standard 100x37 console mode on my notebook, because
in 80x25
text mode letters seems too big for my 12' panel, while other modes
doesn't
cover all panel size. So I've patched
On Thu, 2 Dec 1999, Nick Hibma wrote:
PCMCIA has the problem that the hardware register you are talking to can
disappear on the spot, between 2 outb()s.
Can't we do something about this using bus_space? This would give us a
fair bit of overhead for PCMCIA devices as well as require us to more
In message [EMAIL PROTECTED] Nick Hibma writes:
: PCMCIA has the problem that the hardware register you are talking to can
: disappear on the spot, between 2 outb()s.
Yes. That's why one must poll the device, from time to time, to see
if it is gone. Yucky-poo.
Warner
To Unsubscribe: send
In message [EMAIL PROTECTED] "Matthew N.
Dodd" writes:
: On Thu, 2 Dec 1999, Nick Hibma wrote:
: PCMCIA has the problem that the hardware register you are talking to can
: disappear on the spot, between 2 outb()s.
:
: Can't we do something about this using bus_space? This would give us a
:
Did you do a config of your kernel after updating? opt_linux.h is
generated by config.
Nick
On Tue, 30 Nov 1999, Kenneth Culver wrote:
I tried to rebuild the linux kernel module, but it doesn't work:
Warning: Object directory not changed from original
/usr/src/sys/modules/linux
cc -c -O
The problem is that the mouse doesn't work (its not a hardware problem),
all I get whenever I move the mouse are lots of the following messages
on the console:
Discarded 7 bytes in queue
This means that your mouse is working but moused is closing while the
buffer is not empty yet. This
I agree (patches accepted), although it is hard to figure out just
exactly what is needed to "run one's system".
Maybe a "remake" entry in MAKEDEV which remakes all current entries
if possible.
cd /dev/; sh MAKEDEV *
perhaps? It is going to be one hell of a ride on your disk,
On Thu, Dec 02, 1999 at 12:22:54PM -0500, John Baldwin wrote:
On 02-Dec-99 Maxim Sobolev wrote:
Tony Finch wrote:
Maxim Sobolev [EMAIL PROTECTED] wrote:
I'm using non-standard 100x37 console mode on my notebook, because
in 80x25
text mode letters seems too big for my 12' panel,
According to Maxim Sobolev:
It is interesting. Seems like it is not only VESA modes bug. Strange that
nobody else observed this misbehaviour.
I used to see that in 132 col. mode a year or so (maybe more) and it was fixed
at that time...
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=-
I am having the following panic, with a -CURRENT system as fo CTM
cvs-cur.5868. I *think* the panic was induced by running mpg123 with a not
an mp3 file. I've had two (maybe three, something happened to the box over
night.) of these panics, but hte first was with no dump device configured.
I
On 2 Dec, John Baldwin wrote:
It is interesting. Seems like it is not only VESA modes bug. Strange
that nobody
else observed this misbehaviour.
I have seen it in 132 x anything on both -stable and -current but just
haven't been bothered enough by it to complain.
I´ve seen this once (but
In message [EMAIL PROTECTED] "Matthew N.
Dodd" writes:
: On Thu, 2 Dec 1999, Nick Hibma wrote:
: PCMCIA has the problem that the hardware register you are talking to can
: disappear on the spot, between 2 outb()s.
:
: Can't we do something about this using bus_space? This would give us
I'm using non-standard 100x37 console mode on my notebook, because in 80x25
text mode letters seems too big for my 12' panel, while other modes doesn't
cover all panel size. So I've patched vidcontrol to switch to the VESA_800x600
100x37 mode (instead of default 80x25) with 8x16 font, and in most
On Thursday, 2 December 1999 at 17:21:55 -0800, Matthew Jacob wrote:
Well, I am truly f*cked now. I read enough of this thread, saw nothing new
in UPDATING, and did the following:
alpha
kernel from today
MAKEDEV from today
(but not a make world install- the
Can't you boot from the old kernel? Or have you already wiped the
I can boot the old kernel. A MAKEDEV using the new MAKEDEV has now wiped
all block devs, so swapon, etc. ,fail.. However, this is the conundrum-
it's not safe to do a 'make installworld' on a two week old kernel, but
the new
In article [EMAIL PROTECTED],
David Scheidt [EMAIL PROTECTED] wrote:
Seeing this trying to build world, cvsup'd earlier today.
cc -O -pipe -static -DSETPROCTITLE -DSKEY -DLOGIN_CAP -DVIRTUAL_HOSTING
-Wall -I/usr/src/libexec/ftpd/../../contrib-crypto/telnet -DINTERNAL_LS
-Dmain=ls_main
hello,
I make world and new kernel with ctm source up to src-cur.4115
successfully. However, my system go to panic when I boot it with new
kernel. The error was
=== Error ===
resume IOPL = 0
interrupt mask none -- SMPXXX
trap number = 12
mp_lock = 0102 cpuid = 1
boot() call
Matthew Jacob writes:
Can't you boot from the old kernel? Or have you already wiped the
I can boot the old kernel. A MAKEDEV using the new MAKEDEV has now wiped
all block devs, so swapon, etc. ,fail.. However, this is the conundrum-
it's not safe to do a 'make installworld' on a
Sorry- maybe more of an edge case. It really has to do with 'ad' support
seemingly vanishing from the alpha. Or, rather, it's hard to say exactly
what has happened:
Mounting root from ufs:/dev/rad0a
no such device 'rad'
setrootbyname failed
ffs_mountroot: can't find rootvp
Root mount failed: 6
(removed from general list)
Slow down. You are getting screwed by a combination of things. It
isn't all phk's fault.
The bdev elimination is one factor, but the most important one (the
fsck/mount segv) is due to int/long breakage introduced version 1.85
of mount.h. This happened at
Well, I wasn't back in town until last night with 5000 messages to catch
up on. Sorry for not getting your questions first.
There are other things broken too. Oh well- I really shouldn't get wired.
*BSD will get taken as a serious effort as much as it deserves based upon
what actually
Sorry- maybe more of an edge case. It really has to do with 'ad' support
seemingly vanishing from the alpha. Or, rather, it's hard to say exactly
what has happened:
Mounting root from ufs:/dev/rad0a
no such device 'rad'
You never mount 'r' devices. That should be '/dev/ad0a', and you
I realize that I have been much more upset and unpleasant about this than
the situation warranted, and I would like to extend my apologies to all
and sundry for venting my frustration so publicly.
-matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the
On Thu, Dec 02, 1999 at 08:24:19PM -0500, Greg Lehey wrote:
Can't you boot from the old kernel? Or have you already wiped the
bdevs? If so, how about the fixit floppy/CD-ROM?
At 2MB the Alpha fixit floppy isn't very useful. Nor is there a live
files system for the Alpha. Nor can you even
Hi,
I have recently noticed that the irqs for my PCI devices are being screwed up
somehow. It is easily noticeable with dmesg, the correct one's are in paren.:
vga-pci0: Matrox model 0521 graphics accelerator irq 17(real 11)
at device 0.0 on pci1 ^^ ^^
47 matches
Mail list logo
