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.)
Geoff.
-Original Message-
From: Soren Schmidt [mailto:[EMAIL
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/loader dont have the
On Wed, Aug 11, 1999 at 04:24:55AM +1000, Andy Farkas wrote:
Perhaps this should be a PR...
Seeing as how we are recently being amused by fortune(6) quotes, I thought
I'd mention an acronymn that hasn't been used recently: POLA
Can anyone explain why every time I upgrade world, my hard
That can't be true, at least not for the IBM DeskStars I own, I've
NEVER EVER seen them do that, one proof should be:
same here
wdc0: unit 0 (wd0): IBM-DTTA-350840, DMA, 32-bit, multi-block-16
wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S
wdc0: unit 1 (wd1):
I've just tried and coming in via wd and ad produce the same
problem.
Note my previous comment - the access light is a steady on for
this particular drive. It's left that way when devices are
probed during startup.
My configuration FWIW -
(Note that the devclass_alloc_unit messages are new as
: Correct, but the nature of the kernel probe/attach messages is to convey
: information in a readable, consistent, useful manner.
Agreed. However, what's magical about 80 columns?
What's magical is that almost every text console is limited to 80
columns (think serial console), as well as
On Wed, 11 Aug 1999, Warner Losh wrote:
Then we disagree. There are several scripts floating around that use
them for purposes where there isn't a kernel interface... It would be
ideal if there were interfaces for all this info, but there isn't
always.
Fine. Due to flux in the bus-system
On Wed, 11 Aug 1999, Nate Williams wrote:
The most common case for a console is an 80 column wide console (this is
the default for the virtual terminals, most printers, most text
terminals, etc..)
Changing it is silly, and non-standard.
The line wrapping stuff I brought back for the EISA
Soren Schmidt wrote:
[SNIP]
Have you tried putting disks on the UDMA66 channel ?? I think it
should work in upto WDMA mode now with the ata driver...
I have first to install 4.0 and from my wd2 (I've got a little help from
RNordier, I should make do)
Then, I'll get a UDMA-66 drive (any
It seems Thierry Herbelot wrote:
Soren Schmidt wrote:
[SNIP]
Have you tried putting disks on the UDMA66 channel ?? I think it
should work in upto WDMA mode now with the ata driver...
I have first to install 4.0 and from my wd2 (I've got a little help from
RNordier, I should make
In message [EMAIL PROTECTED] Nate Williams writes:
: And you plan on booting FreeBSD on your PDA?
Yes. I'm already booting NetBSD/hpcmips on it But that's another
thread all by itself...
: stty columns is only effective *AFTER* you have a shell and the box has
: booted.
Yes I know that,
Hi,
Oh, do you have suspend button on your box? Cool.
On my poor experience, suspeding by hot-keys easier to
success than by zzz(8).
On this point I can report the oppposite experience, on my
machine (a no name special) the trackpad tends to lock up if touched
between power
: stty columns is only effective *AFTER* you have a shell and the box has
: booted.
Yes I know that, but you seem to be arguing that all terminals have 80
columns... This is not the case, although many of them do.
Most of them do. It is the 'least common denominator' that FreeBSD runs
Nate Williams scribbled this message on Aug 11:
: The line wrapping stuff I brought back for the EISA bus stuff in -current
: makes it easy to define the wrap point. If some small number of people
: want the ability to wrap at 132 or 40 or whatever, I don't think its
: unreasonable to
Hi,
I have a program which does something like userland-nfs (nfs v2 client).
It is able to crash the machine. After compiling a debug kernel the
only output I get after the crashdump is:
---snip---
(100) root@ttyp3 # gdb -kernel -se /sys/compile/WORK/kernel.debug -c
/var/crash/vmcore.1
IdlePTD
At 02:45 PM 08/11/1999 +0200, Dag-Erling Smorgrav wrote:
"Michael A. Endsley" [EMAIL PROTECTED] writes:
I just downloaded the latest snap (080799) and tried installing it.
When getting to the media section and configuring ppp for a ftp install,
I try going to vty3 (alt-f3). However, that vty
Use alt-F4 for the shell during install.
vty0 - alt-F1 [Install]
vty1 - alt-F2 [Debug]
vty2 - alt-f3 [Inactive]
vty3 - alt-F4 [Shell]
PrtScr will cycle through all available vty's.
HTH. HAND :)
Larry Lile
[EMAIL PROTECTED]
On Wed, 11 Aug 1999 [EMAIL PROTECTED] wrote:
At 02:45 PM
On Wed, 11 Aug 1999, Larry Lile wrote:
Use alt-F4 for the shell during install.
vty0 - alt-F1 [Install]
vty1 - alt-F2 [Debug]
vty2 - alt-f3 [Inactive]
How about we emit a message:
"This screen intentionally left blank." :)
vty3 - alt-F4 [Shell]
PrtScr will cycle through all
On Wed, 11 Aug 1999, Warner Losh wrote:
It also would allow one to kick the VGA display into 132 columns in
the boot loader and have more of a chance to get more of the boot
process on the screen. syscons already supports parts of this...
I was just reading through the thread again, and I
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 other
F-key gets the "beep".
HTH in solving my problem
fwiw dept.- I have been using FreeBSD since 2.21-R
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
The shell is not started until after the install starts, ie when
the ftp connects (the dists start getting untarred.)
Larry Lile
On Wed, 11 Aug 1999 [EMAIL PROTECTED] wrote:
I should have also stated that I tried all the other "F" keys also.
The only vty that is available/active is vty1
Well, something is wrong with what I am trying to say :)
After entering the phone number to my ISP, the message screen pops up
saying "...type ALT-F3..." to go to that vty. A person is supposed to go to
that vty and then either type "dial" or "term".
It is at this time that the vty (alt-f3) is
Soren Schmidt [EMAIL PROTECTED] writes:
It seems Geoff Rehmet wrote:
Brian McGroarty writes :
In using the ATA driver, I'm unable to automatically mount a
partition on a master drive on the secondary controller. fsck
complains that device rwd2s1e isn't configured and exists.
I started a fresh installation with todays floppies. During the
installation, I monitored vty1.
What I found out is that ifconfig doesn't recognize/config either my modem
or cuaa0(ppp0).
After clicking "YES" at the "Do you want to try DHCP configuration of the
interface" screen, I switched to
Kevin Street [EMAIL PROTECTED] writes:
Soren Schmidt [EMAIL PROTECTED] writes:
Hmm, damn, after the problem went away for Geoff I thought it to be
solved since I've never heard of it anywhere else, and I cant reproduce
it here no matter what I try.
Does it help eany if you only has the
Hi, Nate.
I'm sorry if my poor english troubled you.
We should have no problems responding in this amount of time in FreeBSD,
since we don't (didn't used to?) have any code that should cause
significant delay in responding.
My understanding on system suspend code in FreeBSD is that once APM
Hi,
does current current support isa cards that use shared interupts on the
card (eg. multi sio cards) again?
Frank
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
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 other
F-key
After taking a break from this discussion, I do think that I like the
idea of wrapping boot messages in a sane way at column n (= 80 by
default) so long as one knows where messages from one device end and
the next one begin.
I'd also oppose things like
foo0: .. irq
foo0: 9
as opposed to
Ok... needless to say, I am having problems...
1: any access to the serial port (/dev/cuaa0) locks the machine.
2: I cannot get the ethernet card to work.
2a: It is sort-a recognized by the system, It senses the insert and remove,
but it cannot get the CIS. I remember reading somewhere
On Wed, 11 Aug 1999, Warner Losh wrote:
No! At some point they should use a facility similar to solaris/sysv
where they don't display, but do make it into the dmesg buffer...
Warner
What in the world would be the point of doing this? What would be so great
about not seeing the system
On Wed, 11 Aug 1999, Warner Losh wrote:
After taking a break from this discussion, I do think that I like the
idea of wrapping boot messages in a sane way at column n (= 80 by
default) so long as one knows where messages from one device end and
the next one begin.
I'd also oppose things
On Wed, 11 Aug 1999, Brian F. Feldman wrote:
What in the world would be the point of doing this? What would be so
great about not seeing the system boot up?
The same reason that when you type 'cp foo /tmp/' it doesn't say '1 file
copied, 3425 bytes.' or other nonesense. If nothings wrong then
[[ cc trimmed. ]]
In message [EMAIL PROTECTED] "Matthew N.
Dodd" writes:
: check out eisa_reg_print() and eisa_print_child() in
: sys/i386/eisa/eisaconf.c
:
: Sanity in output is a good thing.
Agreed. I like what I see there. Maybe it is time to hoist something
like that into bus_subr.c
Hello. I have a reproducable problem which gdb says is ending up at
0x2818d862 in isatty() from /usr/lib/libc.so.3. A full back trace is
below. If this is a problem in FreeBSD, I'm very glad to do any
experiments that might be helpful. If it's a problem somewhere else,
any pointers on what I
On Wed, 11 Aug 1999, Warner Losh wrote:
In message [EMAIL PROTECTED] "Matthew N.
Dodd" writes:
: check out eisa_reg_print() and eisa_print_child() in
: sys/i386/eisa/eisaconf.c
:
: Sanity in output is a good thing.
Agreed. I like what I see there. Maybe it is time to hoist something
I just rebooted on an August 11 kernel. My system
still is happy with the disks. Hmm.
I can't remember exactly where my tracing went, before I
left off before, but the message you are seeing comes from
/sys/i386/isa/diskslice_machdep.c, line 200 (version 1.35).
What you will probably find, is
37 matches
Mail list logo
