> It sounds like ppp is simply exiting immediately. I'll turn debugging
> on and give it a shot myself; perhaps somebody broke something.
>
> - Jordan
>
> > I should have also stated that I tried all the other "F" keys also.
> > The only vty that is available/active is vty1 for debugging. Every
> Surely if you don't want to see the boot messages for cosmetic
> reasons a splash screen is the most cosmeticly pleasing solution.
Speaking of splash screens (a bit far from the thread's original
topic), I've got my laptop set up to show the daemon-and-sunset
picture on boot, but it see
I see the same problem when trying to boot FreeBSD-3.0-RELEASE (or there
abouts) and later cdroms on my TP770.
I can boot FreeBSD-2.2.8 and earlier FreeBSD-3.0-SNAP cdroms just fine. I
think it has something to do with the new boot loader that went in just
before 3.0-RELEASE.
Tom
On Fri, 13 A
On Fri, 13 Aug 1999 09:48:47 EST, "Matt Crawford" wrote:
> load kernel
> load -t splash_image_data daemon_640.bmp
> load vesa
> load splash_bmp
> boot
Why boot and not autoboot?
Ciao,
Sheldon.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of t
Hello,
After building a few succesfull 4.0 releases (last cvsupped on 13 aug 99),
the keyboard is acting very strange, i cannot login,
i get only strange characters, and when I hit CTRL I get:
load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K
load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 7
I get the bktr device usurping its own cdevsw[] as well - I was
told it was "most likely" benign, so I've been waiting for
others' comments.
I also get the keyboard problem periodically, and I've been
trying to isolate just what I do to cause it. Generally, if I
reboot and don't hit a key before
Brian (and others).
You are correct about the installation. I had a 3.0-R slice, and somehow
corrupted it. I decided I would go to 4.0 and follow current. That is when
the problem started. However:
very early this morning, I got 3.2 (19990812) floppies and did a ftp
installation with those. The "p
I submit that putting "-z" in here is silly, because the sample cvsup
config files turn on compression, and suggest commenting it out if you
have a fast link. It seems counterintuitive that one can comment out
the compression in the standard supfiles and then have it enabled by
default with "make
> It seems Geoff Rehmet wrote:
> > Hmm,
> >
> > My root device still lands up on "wd0" - even though my fstab has
> > the root filesystem on ad0s1a. I haven't looked at getting it to
> > use the ad dev entries for the root file system. (I'm assuming that
> > is still WIP.)
>
> Our boot blocks/
> Yes, thanks. Information reported by 0x4F01 function about any video
> mode has set MODE_NON_VGA attribute indeed. And now I have found DOS TSR
> program for VESA support...
Bleagh. Have you tried ignoring that attribute in our code and seeing
what happens when you select one?
> I hate VESA
> Then after 5 seconds the screen blanks, the power light starts
> flashing (indicating suspend mode), but when I hit a key, the console
> says (slept 00:00:02) only, and programs in fact continued running
> (thus it didn't go or remain in suspend mode at all).
I think you'll find that programs d
> I attempt to boot a CD off of the TP600E and I get the following errors:
>
> "Can't work out which disk we are booting from."
> "Guessed BIOS device 0x8b not found by probes, defaulting to disk0:"
>
> Then whenever it attmpts to access "disk0:" it goes to the floppy drive.
>
> Suggestions?
K
In message <01bee5f0$c467c7c0$0264a8c0@.demon.nl> "Ron Klinkien" writes:
: After building a few succesfull 4.0 releases (last cvsupped on 13 aug 99),
: the keyboard is acting very strange, i cannot login,
: i get only strange characters, and when I hit CTRL I get:
:
: load: 0.04 cmd: login242
[...]
>I also get the keyboard problem periodically, and I've been
>trying to isolate just what I do to cause it. Generally, if I
>reboot and don't hit a key before FreeBSD boots, it never
>happens. If I tap enter to abort the countdown, the keyboard
>scrambles perhaps one time in five.
If you hi
I'd be more than happy to do the pestering if some one could write down
a detailed description of exactly how the TP's BIOS is non-compliant.
I don't know enough about the boot process and BIOS to write such a
description.
Tom
On Fri, 13 Aug 1999, Mike Smith wrote:
> > I attempt to boot a CD
> In message <01bee5f0$c467c7c0$0264a8c0@.demon.nl> "Ron Klinkien" writes:
> : After building a few succesfull 4.0 releases (last cvsupped on 13 aug 99),
> : the keyboard is acting very strange, i cannot login,
> : i get only strange characters, and when I hit CTRL I get:
> :
> : load: 0.04 c
In message <[EMAIL PROTECTED]> Mike Smith writes:
: It's not the boot blocks doing anything explicit; they just use the BIOS.
I have noticed that boot[12] doesn't seem to have this problem.
However, after /boot/loader has been loaded, I see this problem from
time to time. I don't know what is go
>
> I'd be more than happy to do the pestering if some one could write down
> a detailed description of exactly how the TP's BIOS is non-compliant.
> I don't know enough about the boot process and BIOS to write such a
> description.
It's expected that the BIOS numbers disk units sequentially; fl
> In message <[EMAIL PROTECTED]> Mike Smith writes:
> : It's not the boot blocks doing anything explicit; they just use the BIOS.
>
> I have noticed that boot[12] doesn't seem to have this problem.
> However, after /boot/loader has been loaded, I see this problem from
> time to time. I don't kno
Hi,
Apm does not seem to be behaving correctly on my computer (running
yesterday's CURRENT)
eg: with a make world running, the following happens after about 15 mins
of not touching the keyboard.
Received APM Event: PMEV_STANDBYREQ
Execute APM hook "pcm suspend handler"
Called APM sound suspend
20 matches
Mail list logo
