Vallo Kallaste writes:
> > - History buffer (back-scroll buffer) management functions are moved
> > to a new file, schistory.c.
>
> My question is slightly off-topic, but.. is it now possible (or in the
> future) to choose which key combination to use for back-scroll buffer
> handling? I persona
>i'm wondering why when the system dumpdev is set to a device that
>doesn't have a read dump routine (nodump()) why it lies about the
>dump being successful.
Just another bug.
>Index: kern_shutdown.c
>===
>RCS file: /home/ncvs/src/s
>I think I know why a lot of people _aren't_ seeing this panic: it
>doesn't show up if you #undef DEVT_FASCIST in kern/kern_conf.c .
#undef DEVT_FASICIST weakens tthe error detection.
>I found this by accident because I can't get a crash dump using the wd
>driver. I get
>
>dumping to dev (0, 131
On May 05, 1999 at 05:00:16PM -0700, Carlos C. Tapang wrote:
> >
> >In a nutshell, there is a table of interrupt vectors which is set
> >by the BIOS at boot time, which are used by the loader (and by the
> >FreeBSD kernel, if VM86 is turned on).
> >
> Thanks, Jonathan. Are any of the following TRUE
*sigh* No suprise here. As 90% of these things are this was yet
another Dumb User Error. I had a base address conflict that kept
the card from being probed.
Thanks for everyone's help. As always FreeBSD is working just
great!
-Steve
To Unsubscrib
Did all of that and a 'set boot_verbose'. Lots more data but
I'm still not even seeing a probe for ethernet cards on the
isa bus. I have 'ed1' and 'ep1' enabled in the kernel:
device ed1 at isa? port 0x340 irq 10 iomem 0xd8000
device ep1 at isa? port 0x340 irq 10
And it is certainly not being de
On Tue, 18 May 1999, Thomas T. Veldhouse wrote:
> I have a Yamaha-SA3 card built into my motherboard. I uses the pcm drivers
> for sound. My system is current as of two days ago.
>
> I just installed KDE-1.1.1 (curious about performance) and I was testing out
> the one and only sound that seems
On Mon, 17 May 1999, John W. DeBoskey wrote:
>For those of you who know more than I When a -current
> kernel boots up, it dies when trying to mount /tmp as an mfs.
>
> Fatal Trap 12: page fault while in kernel mode
Fixed it earlier this week or last week in v1.63 (14 May) of
/sys/ufs/mfs
>
>In a nutshell, there is a table of interrupt vectors which is set
>by the BIOS at boot time, which are used by the loader (and by the
>FreeBSD kernel, if VM86 is turned on).
>
Thanks, Jonathan. Are any of the following TRUE?
1. FreeBSD is affected by these vectors only if VM86 is turned ON.
2. I
i'm wondering why when the system dumpdev is set to a device that
doesn't have a read dump routine (nodump()) why it lies about the
dump being successful.
Index: kern_shutdown.c
===
RCS file: /home/ncvs/src/sys/kern/kern_shutdown.c
> > device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000
>
> You should probably show the list what device lines you are using for
> current, since config barfs on the above line under current:
>
> config: line 52: `net' interrupt label obsolete
Fair enough:
device ed1 at isa? port 0x280 irq 1
In case that there are any further problems with SANE
I am kind-off line due to my ISP (www.dspeed.net) disappearing
from the Net :( Time to look for a different ISP provider
Amancio
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the
> i cannot build sane -1.00 ports (ports/graphics/sane-1.00) for a long time
> under FreeBSD. i've tried to contact with maintainer of this
> port (g...@hotlava.com), but he doesn't respont. could anyone fix it?
Amancio Hasty has sent me a fix for this, but I
have not had time to test and commit
It seems Mike Smith wrote:
> >
> > No, it does not work at all with that maximum set. I'm using the disk to
> > hold
> > an FFS filesystem, and mounting it, BTW. See, in the old driver, it limited
> > the transfer, but it ALSO queued the rest of the transfer. AFD doesn't, and
> > I can tell this
>
> No, it does not work at all with that maximum set. I'm using the disk to hold
> an FFS filesystem, and mounting it, BTW. See, in the old driver, it limited
> the transfer, but it ALSO queued the rest of the transfer. AFD doesn't, and
> I can tell this because I get random parts of kernel memor
On Sun, 16 May 1999, Narvi wrote:
>
> On Sat, 15 May 1999, Alfred Perlstein wrote:
>
> > On Sat, 15 May 1999, Narvi wrote:
> >
> > >
> > > On Fri, 14 May 1999, Garance A Drosehn wrote:
> > >
> > > > At 3:51 PM +0700 5/12/99, Ustimenko Semen wrote:
> > > > > Are we going to get this license?
I have confirmed that the problem occurs if I just do:
xsetpointer Joystick
sleep 1
xsetpointer pointer
So M.A.M.E. is unrelated to the problem as Bruce Evans would suggest.
So the problem appears to be with XFree86 not closing the joystick
device after I've used it as a pointer with 'xset
Last night switched from 3.1 to 4.0. Smooth transition. The only
error I've seen is one of my ethernet cards is no longer detected.
In the previous kernel (3.1-STABLE) I had the following config
line:
device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000
When the system booted it would detect
On Tue, 18 May 1999 08:53:49 +0200, Sheldon Hearn wrote:
> I remade world and kernel (config -g -r) with yesterday's HEAD and still
> get a panic mounting MFS. My kernel config includes MFS but not
> MFS_ROOT.
>
> Shout if you want a trace. I haven't provided one here, since I'll need
> to copy
I have a Yamaha-SA3 card built into my motherboard. I uses the pcm drivers
for sound. My system is current as of two days ago.
I just installed KDE-1.1.1 (curious about performance) and I was testing out
the one and only sound that seems to come with it. It seems that the sound
device is buffer
Yep! The patch seems to have fixed the problem! :-)
Thanks Luoqi!!
Bob
On Mon, May 17, 1999 at 11:42:21PM -0400, Luoqi Chen wrote:
> > I have been making world each time after cvsupping so I would expect the
> > mfs kld module to be getting rebuilt and it appears to be up-to-date:
> >
> > -r
>> If its just that you are unsatisfied with only max 32K transfers, thats
>> another matter, and stuff for later changes.
>
>No, it does not work at all with that maximum set. I'm using the disk to hold
>an FFS filesystem, and mounting it, BTW. See, in the old driver, it limited
>the transfer, but
> ??? ISA only configs wont compile.
> ??? Fixed.
Unfortunately it still doesn't work on my Toshiba 445CDX notebook (it
seems that driver isn't probed at all - no ata messages visible on boot
time). I can't attach dmesg output because system can't mount root f/s
and my floppy forgotten at home
>I know I cut off the transfer length, but I also return the missing
>size in b_resid, so the kernel _should_ come back with the rest of
>the transfer in a new request or at least fail on the unsatisfied
>request, and on my system it does seem to work...
>If this doesn't work in all cases, some oth
Hi,
For those of you who know more than I When a -current
kernel boots up, it dies when trying to mount /tmp as an mfs.
Fatal Trap 12: page fault while in kernel mode
fault virtual address = 0x9d2c0b38
fault code = supervisor read, page not present
instruction pointer =
i cannot build sane -1.00 ports (ports/graphics/sane-1.00) for a long time
under FreeBSD. i've tried to contact with maintainer of this
port (g...@hotlava.com), but he doesn't respont. could anyone fix it?
--
sincerely,
ilya naumov (at work)
To Unsubscribe: send mail to majord...@freebsd.org
It seems Brian Feldman wrote:
>> It seems Brian Feldman wrote:
>> > Yes, I finally got it working! The explanation is in the patch, which I
>> > should
>> > not need to explain again :)
>>
>> Hmm, Does it not work as is ?? It works on my LS120 drive, and a couble
>> of others. Besides your hack
On Tue, 18 May 1999, Soren Schmidt wrote:
> It seems Brian Feldman wrote:
> > Yes, I finally got it working! The explanation is in the patch, which I
> > should
> > not need to explain again :)
>
> Hmm, Does it not work as is ?? It works on my LS120 drive, and a couble
> of others. Besides your
David O'Brien wrote:
>
> > > Below follow dmesg output and kernel configuration.
> >
> > > device pcm0 at isa? port ? irq 10 drq 1 flags 0x0
> >
> > I have this:
> >
> > device pcm0 at nexus? port ? irq 10 drq 1 flags 0x0
> >^^
>
> I would like to update ``sys/i386/isa/snd
On Thu, 6 May 1999, Tomer Weller wrote:
> whenever i try to compile KDE software (ports also) i get this error, though
> packages install fine.
> i installed KDE from packages, i suspect that's the problem.
I didn't see a response to this as I was going through my inbox, so apologies
if this ha
30 matches
Mail list logo
