Re: PCMCIA drivers

> The current pccard code is evil and must die. Be that as it may, it is a huge improvement today over what it was a month ago. Thanks!! 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 b

Re: Sh still is not working for MAKEDEV

Amancio Hasty wrote: > Well, he can run "ktrace -di ./MAKEDEV " then > kdump >foo.dump > > Or compile sh with debug symbols and trace down the failure. Thanks to all for prompt replies. It seems like a bug in egcs which broke sh when "-march=pentium" option is used while -O? level doesn't really

Re: Sh still is not working for MAKEDEV

Well, he can run "ktrace -di ./MAKEDEV " then kdump >foo.dump Or compile sh with debug symbols and trace down the failure. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Sh still is not working for MAKEDEV

On Mon, Aug 02, 1999, Maxim Sobolev wrote: > Hi folks, > > Does anybody investigating what wrong with the sh in the -current? As I > reported earlier it still fails to correctly process MAKEDEV script. Are you sure you are not running bash instead of sh? -- |Chris Costello <[EMAIL PROTECTED

Re: Panic plus advice needed

On Sunday, 1 August 1999 at 23:33:07 +0200, Andrzej Bialecki wrote: > On Sat, 31 Jul 1999, Jeroen Ruigrok/Asmodai wrote: > >> >> No, just options DDB. >> This bt was obtained after doing gdb -k kernel.0 vmcore.0 >> I still have the DDB trace on paper which I can type in if needed/wanted. >> >>> W

Re: Sh still is not working for MAKEDEV

On Mon, 02 Aug 1999 22:34:19 +0300, Maxim Sobolev wrote: > Does anybody investigating what wrong with the sh in the -current? As I > reported earlier it still fails to correctly process MAKEDEV script. Perhaps someone should have come out and said this last time: I can't reproduce the problem.

FYI for those with 3Com 3c905C cards

I've gotten a couple of reports from people claiming to have trouble with the 3c905C, usually along the lines of "the autonegotiation works and I can bring the card up, but I can't receive or send any packets." (For those who don't know, the 3c905C differes from the 3c905B in that it has a new 3C

Re: junior-hacker task: "prepdisk"

In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes: : My real beef here is not with the boot failure but with the fact that our : command line tools stink when I bring in a new blank disk... Yes. Several times I've hit this problem, but have never been PO'd enough to fix it... Warner To

Re: PCMCIA drivers

In message Adam Wight writes: : First, the current zp driver cannot be configured if the pccard services : are being used, since it uses its own pccard code. Very Bad. : : Then, the PCMCIA model that we use now makes it impossible to use both : functions of a

Sh still is not working for MAKEDEV

Hi folks, Does anybody investigating what wrong with the sh in the -current? As I reported earlier it still fails to correctly process MAKEDEV script. Sincerely, Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: APM related panic

> # sorry to break the thread, I'm a digest reader... Not a problem at all. > > > apm0: on motherboard > > > apm: APM BIOS version 0102 > > > apm: Code16 0xc00f, Data 0xc00fdfa0 > > > apm: Code entry 0x8010, Idling CPU enabled, Management enabled > > > apm: CS_limit=0x0, DS_limit=0x0 >

Re: Assembler capable of supporting 3dnow!

On 2 Aug 1999, Assar Westerlund wrote: > Doug Rabson <[EMAIL PROTECTED]> writes: > > There are no public betas that I can find. The only updates to binutils > > publically available seem to be the Linux patchsets :-(. > > Try (or the CVS > tre

Re: APM related panic

> Hi! > > Thanks, seems your patch did the trick (panic gone). Following is dmesd: Thanks for the confirmation; I've made an even more pessimistic patch that should cover your situation. Please let me know if your next CTM works correctly. Thanks for the quick bug report too! > apm_probe: A

Re: APM related panic

Hi! Thanks, seems your patch did the trick (panic gone). Following is dmesd: apm_probe: APM bios gave zero len code16, pegged to 64K apm_probe: APM bios gave zero len data, tentative 64K apm0: on motherboard apm: APM BIOS version 0102 apm: Code16 0xc00f, Data 0xc00fdfa0 apm: Code entry 0x00

Re: Recent -CURRENT doesn't show process times on some hardware

> On Sunday, 1 August 1999 at 22:17:51 -0700, Mike Smith wrote: > >> What makes this all the more puzzling is that it happens only on one > >> machine. Hint: it's a laptop (Dell Latitude CPi). panic is a normal > >> Pentium machine of no particular lineage. Does this ring a bell with > >> anyb

Re: junior-hacker task: "prepdisk"

>> very dangerously dedicated:= dangerously dedicated with the DOSpartition >> table and/or boot signature zeroed or otherwise clobbered. >> undangerously dedicated:= dangerously dedicated with the DOSpartition table >> fixed to cover the whole disk (including the MBR). This is very easy

Re: junior-hacker task: "prepdisk"

On Tue, 3 Aug 1999, Bruce Evans wrote: > >>> My semantics may be wrong on these two: what I'm talking about is > >>> what is in handbook chapter 8 "Using command line utilities " gives > >>> you a disk which doesn't boot. > >> > >>Ok; of those two examples, the first should give you a truly dedic

Re: junior-hacker task: "prepdisk"

On Mon, 2 Aug 1999, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Mike Smith writes: > >> In message <[EMAIL PROTECTED]>, Bruce Evans writes: > >> > >> >All of the above only work for the easy case where the whole disk is > >> >being labelled. In general, the disk size must be redu

Re: junior-hacker task: "prepdisk"

>>> My semantics may be wrong on these two: what I'm talking about is >>> what is in handbook chapter 8 "Using command line utilities " gives >>> you a disk which doesn't boot. >> >>Ok; of those two examples, the first should give you a truly dedicated >>disk. (You can only generate a "dangerous

Re: APM related panic

# sorry to break the thread, I'm a digest reader... Hi, > > apm0: on motherboard > > apm: APM BIOS version 0102 > > apm: Code16 0xc00f, Data 0xc00fdfa0 > > apm: Code entry 0x8010, Idling CPU enabled, Management enabled > > apm: CS_limit=0x0, DS_limit=0x0 > > These limits look pretty su

Re: Assembler capable of supporting 3dnow!

Doug Rabson <[EMAIL PROTECTED]> writes: > There are no public betas that I can find. The only updates to binutils > publically available seem to be the Linux patchsets :-(. Try (or the CVS tree at :pserver:[EMAIL PROTECTED]:/cvs/binutils. That

Re: junior-hacker task: "prepdisk"

In message <[EMAIL PROTECTED]>, Robert Nordier writes: >> >What fails? Can you be more specific? How recent are your boot1/boot2 >> >blocks? I would be inclined to dd at least 8k over the front of the >> >disk myself, but I don't think that's relevant in your case. >> >> Disk error #1 while

Re: junior-hacker task: "prepdisk"

> >What fails? Can you be more specific? How recent are your boot1/boot2 > >blocks? I would be inclined to dd at least 8k over the front of the > >disk myself, but I don't think that's relevant in your case. > > Disk error #1 while trying to load boot/loader. I think the bios > in this case

Re: Assembler capable of supporting 3dnow!

On Sun, 1 Aug 1999, Brian F. Feldman wrote: > On Sun, 1 Aug 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > > I'm messing around with the latest mesa and have discovered (suprise)that our > > assembler doesn't support 3dnow instructions. Are there any plans to update to > >

Re: Recent -CURRENT doesn't show process times on some hardware

On Sunday, 1 August 1999 at 22:17:51 -0700, Mike Smith wrote: >> What makes this all the more puzzling is that it happens only on one >> machine. Hint: it's a laptop (Dell Latitude CPi). panic is a normal >> Pentium machine of no particular lineage. Does this ring a bell with >> anybody? > > D

Re: mountpoint locking with fbsd-nfs

On Sun, 1 Aug 1999, Kevin Day wrote: > > > > :Yeah, I know about -alldirs... The problem was that we had customers who > > :wanted us to export their home directories, and unless I gave them their own > > :filesystem, I couldn't restrict it in the manner i wanted. :) > > : > > :Just checking to