> hi,
>
> Just found problem with boot loader. Attached "FAQ" will describe problem :)
This is not a problem.
> Q: What I want?
> A: Boot in verbose mode
>
> Q: What I do ?
> A: On boot prompt type "-v"
>
> Q: So ?
> A: Nothing (system is booting in normal mode)
That's correct. '-v' at the
> Since I dont think my other mail made it through...(since I didnt see it, or
> any replys)
>
> Has anyone gotten an Iomega Ditto Max drive to work on 4.0? I have both
> types, Floppy/ditto dash card and Parallel port, and would like to use it to
> back up my drive every week or so.
It's not s
>
> Sorry if I ask a FAQ,
Don't be sorry, don't do it. Search the mailing list archives.
> But where is ft0 support gone?
Into the bitbucket.
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he
I tried to install from the ports XFree 3.3.5 in my 4.0-CURRENT box.
It compile well, but when it's the time of the install I receive this error :
rm -f FSConnServ.o
cc -c -O2 -ansi -pedantic -Dasm=__asm -I../../include/fonts -I../..
-I../../ex
ports/include -DCSRG_BASED -DFUNCPROTO=15
-D
hi,
On Fri, Oct 15, 1999 at 12:57:26AM -0700, Mike Smith wrote:
> That's correct. '-v' at the boot: prompt does nothing.
But '/kernel' is default kernel name, so "-v" will be option to default
kernel name (at least FreeBSD 1.1.5.1/2.* does that :-) ).
> > Q: What I do then ?
> > A: On boot p
On Fri, Oct 15, 1999 at 11:45:56AM +0400, Alexey Zelkin wrote:
> hi,
>
> On Fri, Oct 15, 1999 at 12:57:26AM -0700, Mike Smith wrote:
>
> > That's correct. '-v' at the boot: prompt does nothing.
>
> But '/kernel' is default kernel name, so "-v" will be option to default
> kernel name (at least
I'm using freebsd 3.1 release at one of my PCs. Today i tried to upgrade
it to current. I read mail-archives and knew, that i had to compile kernel
first. So i made new config and configured and build kernel. While booting
loader prints the next error message and boot fails:
/kernel text=0x202b9
Hi
I am getting this breakage when I try to compile XFree86 on a really
current system:
cc -c -O2 -ansi -pedantic -Dasm=__asm -I../../include/fonts -I../..
-I../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO
-DMALLOC_0_RETURNS_NULL -DTCPCONN -DUNIXCONN -DHAS_STICKY_DIR_BIT
At 15/10/99, Mark Murray wrote:
>Hi
>
>I am getting this breakage when I try to compile XFree86 on a really
>current system:
>
>cc -c -O2 -ansi -pedantic -Dasm=__asm -I../../include/fonts -I../..
>-I../../exports/include -DCSRG_BASED -DFUNCPROTO=15
>-DNARROWPROTO -DMALLOC_0_RETURNS_NULL -D
Hi folks,
A sequence of silly mistakes and circumstances have conspired against me
to make it impossible for me to run XFree86. I understand that the
XFree86 build is broken in the face of recent signal-related changes.
I want to know how long I can expect to wait for XFree86 to build on
CURREN
> What hould i do to upgrade to current?
Rebuild and reinstall all your modules. Keep the ols ones "just in case".
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Sheldon Hearn wrote:
> I want to know how long I can expect to wait for XFree86 to build on
> CURRENT again. I'm not pushing, I just want to know whether I'm in for a
> wait of less than a week (in which case I'll do without XFree86) or
> whether I can expect to wait longer (in which case I'll bi
On Fri 15 Oct 1999 Jesus Rodriguez wrote:
>>Installation process has worked ok, but when i try to run
>>/usr/local/Office51/bin/soffice or /usr/local/bin/soffice always get a
screen
>>that says:
>>
>>Staroffice is already installed on:
>>/usr/local/Office51
>>
>>And i can select between Modify, U
Today Mike Smith wrote:
> >
> > Sorry if I ask a FAQ,
>
> Don't be sorry, don't do it. Search the mailing list archives.
It might help if HARDWARE.TXT (both -current and -stable) didn't
list floppy tapes. It refers to the driver as "stale" rather
than gone.
-
Mark Murray wrote:
>
> Hi
>
> I am getting this breakage when I try to compile XFree86 on a really
> current system:
>
> cc -c -O2 -ansi -pedantic -Dasm=__asm -I../../include/fonts -I../..
>-I../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO
>-DMALLOC_0_RETURNS_NULL -DTCPC
Yech, malformed patch. This one applies. :-)
Thanks, Marcel.
Ciao,
Sheldon.
Index: signal.h
===
RCS file: /home/ncvs/src/sys/sys/signal.h,v
retrieving revision 1.21
diff -u -d -r1.21 signal.h
--- signal.h1999/10/12 13:58:15
Around Yesterday, "David Scheidt" wrote :
DS> I had a panic tuesday, due to trying to load a broken module. I got the
DS> same panic: Timeout table full message. Interestingly, savecore seems to
I've been getting these really odd panics as well (which I reported
but no-one seemed interested)
On Fri, 15 Oct 1999, Khetan Gajjar wrote:
> I've been getting these really odd panics as well (which I reported
> but no-one seemed interested), with that error.
I had only the panics caused by loading an out of date KLD.
> I'm using the "experimental" ATA code though; are you using IDE
> dis
> On a related topic, we should fix the Alpha to emit the weak alias
> like the i386 does.
We should do what ever is reasonably possible to keep these two archs
operating the same. IMHO, people will expect their FreeBSD platform
knowledge to hold on the Alpha.
--
-- David([EMAIL PROTECTED]
I managed to fix this problem temporarily for myself, but was hoping
the tree would fix itself soon enough.
At the top of FSConServ.c add the line
#define _P1003_1B_VISIBLE
I believe (I deleeted the X source tree), and it'll build fine.
Excerpts from FreeBSD-Current: 15-Oct-99 XFree buil
> hi,
>
> On Fri, Oct 15, 1999 at 12:57:26AM -0700, Mike Smith wrote:
>
> > That's correct. '-v' at the boot: prompt does nothing.
>
> But '/kernel' is default kernel name, so "-v" will be option to default
> kernel name (at least FreeBSD 1.1.5.1/2.* does that :-) ).
However, FreeBSD 3.x and
the driver could come back if someone who HAD such a device were to adopt
it..
On Fri, 15 Oct 1999, jack wrote:
> Today Mike Smith wrote:
>
> > >
> > > Sorry if I ask a FAQ,
> >
> > Don't be sorry, don't do it. Search the mailing list archives.
>
> It might help if HARDWARE.TXT (both -curr
I've changed the attachment topography for pccard/pcic devices. Now
pcic attaches to the isa bus to act as a bridge to the pccard device.
For historical reasons, I've left the pccard device name as "card" but
this may change to pccard in the future, but there are too many legacy
drivers to do th
>
> Hi folks,
>
> A sequence of silly mistakes and circumstances have conspired against me
> to make it impossible for me to run XFree86. I understand that the
> XFree86 build is broken in the face of recent signal-related changes.
>
> I want to know how long I can expect to wait for XFree86 to
I seem to have a problem compiling a kernel on my laptop with the ed0
driver that I use for my D-link 660 pcmcia card.
Running current, cvsup this morning. Make world finished with no problems
but my attempt at kernel compilation yielded:
> if_ed_isa.o: In function `ed_isa_attach':
> if_ed_isa.
As Daniel Eischen wrote ...
Sheer curiosity and most likely a somewhat dim question:
what the h* is a weak versus a strong symbol?
Thanks,
Wilko
> John Birrell wrote:
> > Weak symbols don't work too well _between_ libraries. If libc is linked
> > before libpthread, any unresolved refer
Argh. I know whats wrong but I don't have a good idea on how to cleanly
fix it.
Comment out:
sys/dev/ed/if_ed_isa.c ...
in sys/i386/conf/files.i386 and reconfig/make etc.
Warner? You mind taking a peek at sys/dev/ed/if_ed_pccard.c and telling
me how to fix it so we can get rid of the sys/i3
So the system builds nice again - thanks.
I haven't tried the XFree86 fix yet.
However there is a problem with the pcm driver:
pcm0: irq 11 at device 15.0 on pci0
pcm0: unable to map register space
device_probe_and_attach: pcm0 attach returned 6
Any idea?
I used
device pcm0 a
[And this is one more reason why the default procedure was
"world before kernel" -- I have nothing against changing the
procedure, as long as people unbreak the new procedure...
]
"Ilmar S. Habibulin" wrote:
>
> I'm using freebsd 3.1 release at one of my PCs. Today i tried to upgrade
> it to cu
hi,
On Fri, Oct 15, 1999 at 03:09:44AM -0700, Bill Swingle wrote:
> > > > Q: What I do then ?
> > > > A: On boot prompt type "kernel -v"
> > > >
> > > > Q: So ?
> > > > A: All works fine (system is booting in verbose mode)
> > >
> > > '-v' is an argument to the kernel. Specify it as such. 8)
< said:
> the driver could come back if someone who HAD such a device were to adopt
> it..
Probably not. The hardware is just so transcendently evil that it's
unlikely it could be made to work reliably for more than one or two
people at a time.
At some point we need to stop supporting antique
On Thu, Oct 14, 1999 at 09:19:33AM -0500, David Scheidt wrote:
> On Thu, 14 Oct 1999, Alex Le Heux wrote:
>
> > After configuring the system for making a crashdump, I get "panic: Timeout
> > table full" halfway through the dump.
>
[snip]
>
> Sounds like your modules are out of date? That bit m
On Fri, 15 Oct 1999, Alex Le Heux wrote:
> On Thu, Oct 14, 1999 at 09:19:33AM -0500, David Scheidt wrote:
> > On Thu, 14 Oct 1999, Alex Le Heux wrote:
> >
> > > After configuring the system for making a crashdump, I get "panic: Timeout
> > > table full" halfway through the dump.
> >
> [snip]
>
On Fri, 15 Oct 1999, Alfred Perlstein wrote:
>
> What is your memory size? what is your swap device size?
256MB. 512MB.
David Scheidt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Fri, 15 Oct 1999, Khetan Gajjar wrote:
>
> Looks like we have our problem; it's the ATA driver. I don't recall
> seeing this error when using the wd driver.
Yup. When I force a panic from DDB, I get
panic: timeout table full
and a message about "Dump already in progress, bailing". I hav
On Fri, Oct 15, 1999 at 08:09:57PM +0200, Wilko Bulte wrote:
> Sheer curiosity and most likely a somewhat dim question:
>
> what the h* is a weak versus a strong symbol?
A weak symbol is like an alias for another (strong) symbol. The linker
will link to strong symbols first, then, for any unreso
On 15-Oct-99 at 15:05, John Birrell ([EMAIL PROTECTED]) wrote:
> On Fri, Oct 15, 1999 at 08:09:57PM +0200, Wilko Bulte wrote:
> > Sheer curiosity and most likely a somewhat dim question:
> >
> > what the h* is a weak versus a strong symbol?
>
> A weak symbol is like an alias for another (strong)
Hi,
I've got a Rockwell PCI Modem thats full hardware, and I was wondering
if anybody has written a driver for this kind yet.
I saw somebody posted something about they were going to write a driver for
such a hardware class.
Thanks
Bill
[EMAIL PROTECTED]
To Unsubscribe: send mail to [
hey If someone did adopt it then it wouldn't be a problem..
if no-on edoes then it can remain 'unsupported'
On Fri, 15 Oct 1999, Garrett Wollman wrote:
> <
>said:
>
> > the driver could come back if someone who HAD such a device were to adopt
> > it..
>
> Probably not. The hardware is just
On 15 October 1999 at 10:20, Julian Elischer <[EMAIL PROTECTED]> wrote:
> the driver could come back if someone who HAD such a device were to adopt
> it..
I have one (colorado thing). I _will not_ adopt it :-) but I'd
happily send it to a committer that wanted to support it. I haven't
used it i
Clean compile. I haven't rebooted yet, but it should be fine.
Thank you,
ed
"Matthew N. Dodd" wrote:
> Argh. I know whats wrong but I don't have a good idea on how to cleanly
> fix it.
>
> Comment out:
>
> sys/dev/ed/if_ed_isa.c ...
>
> in sys/i386/conf/files.i386 and reconfig/make etc.
>
>
Today Julian Elischer wrote:
> hey If someone did adopt it then it wouldn't be a problem..
> if no-on edoes then it can remain 'unsupported'
unsupported != tucked away in the attic, out of reach of
many/most users.
--
Jack
For all those who mailed this list about the temperature monitor apps
saying that the device wasn't configured, I have a preliminary version of
an app that should work for you. I just finished writing it about 10
minutes ago, and it only shows temperatures, and only shows them in
degrees C right n
Alexey Zelkin wrote:
>
> > It's pretty consistant with other OS's boot prompt.
> Ok, I see that I'll not get answer to my question except "do it otherwise".
Actually, you got an answer, though you might have missed it.
Boot2 does not have "/kernel" as default, but "/boot/loader". Thus,
even if
44 matches
Mail list logo
