Re: vty3 and 4.0 snap 080799

[Brian Somers]

> 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 gets the "beep".
> > HTH in solving my problem
> > 
> > fwiw dept.- I have been using FreeBSD since 2.21-R

Errum, if this is a re-install, I may see what the problem is.  I 
changed sysinstall to run ``ppp install'' as sysinstall now writes an 
``install'' label into ppp.conf.  Might it be the case that a 
reinstall doesn't add the ``install'' label ?

-- 
Brian <[EMAIL PROTECTED]><[EMAIL PROTECTED]>
     <[EMAIL PROTECTED]>
Don't _EVER_ lose your sense of humour !  <[EMAIL PROTECTED]>




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: it's time...

[Matt Crawford]

> 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 seems I now have an extremely small window of
time to press a key to get to the boot prompt.  What do I need to
insert to get this window back up to several seconds?  My loader.rc
file looks like this:

\ Loader.rc
\
\ Includes additional commands
include /boot/loader.4th

\ Reads and processes loader.rc
\ start

\ Unless set otherwise, autoboot is automatic at this point

load kernel
load -t splash_image_data daemon_640.bmp
load vesa
load splash_bmp
boot


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: yet more TP 600E fun...

[Tom Bartol]

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 Aug 1999, David E. Cross wrote:

> 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?
> 
> --
> David Cross   | email: [EMAIL PROTECTED] 
> Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd 
> Rensselaer Polytechnic Institute, | Ph: 518.276.2860
> Department of Computer Science| Fax: 518.276.4033
> I speak only for myself.  | WinNT:Linux::Linux:FreeBSD
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: it's time...

[Sheldon Hearn]

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 the message

Problems with 4.0 keyboard input!

[Ron Klinkien]

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% 772K
load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K



Login through the network with telnet is no problem

I also want to know what this means:

WARNING: "bktr" is usurping "bktr"'s cdevsw[]

It's my Brooktree video capture/tuner card


This is my dmesg and config:

--- dmesg ---
Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #23: Fri Aug 13 22:15:49 CEST 1999
[EMAIL PROTECTED]:/usr/src/sys/compile/MOON
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 334092770 Hz
CPU: Pentium II/Xeon/Celeron (334.09-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x651  Stepping = 1

Features=0x183f9ff
real memory  = 134205440 (131060K bytes)
avail memory = 127098880 (124120K bytes)
Preloaded elf kernel "kernel" at 0xc02e2000.
VESA: v2.0, 4096k memory, flags:0x1, mode table:0xc028c1e2 (122)
VESA: Matrox Graphics Inc.
Pentium Pro MTRR support enabled
Probing for PnP devices:
npx0:  on motherboard
npx0: INT 16 interface
pcib0:  on motherboard
pci0:  on pcib0
WARNING: "bktr" is usurping "bktr"'s cdevsw[]
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
vga-pci0:  irq 10 at device 0.0 on
pci1
isab0:  at device 4.0 on pci0
chip1:  at device 4.1 on pci0
chip2:  at device 4.2 on pci0
chip3:  at device 4.3 on pci0
bktr0:  irq 14 at device 10.0 on pci0
iicbb0:  on bti2c0
iicbus0:  on iicbb0 master-only
smbus0:  on bti2c0
Miro TV, Temic PAL tuner.
xl0: <3Com 3c905-TX Fast Etherlink XL> irq 15 at device 11.0 on pci0
xl0: Ethernet address: 00:60:08:3e:74:63
xl0: autoneg complete, link status good (half-duplex, 10Mbps)
ncr0:  irq 10 at device 12.0 on pci0
isa0:  on motherboard
fdc0:  at port 0x3f0-0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0:  at port 0x60-0x6f on isa0
atkbd0:  irq 1 on atkbdc0
psm0:  irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
vga0:  at port 0x3b0-0x3df iomem 0xa-0xb on isa0
sc0:  on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
lpt0:  on ppbus 0
lpt0: Interrupt-driven port
isic0 at port 0xf80 iomem 0xd-0xd0fff irq 5 flags 0x2 on isa0
isic0: Teles S0/16, Creatix ISDN S0-16 or Niccy 1016
isic0: ISAC 2085 Version V2.3 (B3) (IOM-1) (Addr=0xc00d0100)
isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0xc00d0180, AddrB=0xc00d01c0)
Checking for GUS Plug-n-Play ...
No Plug-n-Play devices were found
gus0 at port 0x220 irq 11 drq 1 flags 0x3 on isa0
snd0:  snd0: 
i4b: ISDN call control device attached
i4bisppp: 1 ISDN SyncPPP device(s) attached
i4bctl: ISDN system control port attached
i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header compression)
i4btel: 2 ISDN telephony interface device(s) attached
i4brbch: 4 raw B channel access device(s) attached
i4btrc: 4 ISDN trace device(s) attached
changing root device to da0s1a
da0 at ncr0 bus 0 target 0 lun 0
da0:  Fixed Direct Access SCSI-2 device
da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing
Enabled
da0: 4094MB (8385121 512 byte sectors: 255H 63S/T 521C)
cd0 at ncr0 bus 0 target 6 lun 0
cd0:  Removable CD-ROM SCSI-2 device
cd0: 10.000MB/s transfers (10.000MHz, offset 15)
cd0: Attempt to query device size failed: NOT READY, Medium not present



--- CONFIG 
#
# MOON -- Kernel configuration for my FreeBSD server.
#
#   $Id: MOON,v 1.000.0.00 1999/08/09 17:12:26 ronk Exp $

machine "i386"
cpu "I686_CPU"
ident   MOON
maxusers64

options INET#InterNETworking
options FFS #Berkeley Fast Filesystem
options FFS_ROOT#FFS usable as root device [keep this!]
options MSDOSFS #MSDOS Filesystem
options CD9660  #ISO 9660 Filesystem
options PROCFS  #Process filesystem
options COMPAT_43   #Compatible with BSD 4.3 [KEEP THIS!]
options SCSI_DELAY=1000 #Be pessimistic about Joe SCSI device
options UCONSOLE#Allow users to grab the console
options USERCONFIG  #boot -c editor
options VISUAL_USERCONFIG   #visual boot -c editor

# System bus
controller  isa0
controller  pnp0
controller  pci0

# Floppy controller
controller  fdc0at isa? port "IO_FD1" irq 6 drq 2
disk 

Re: Problems with 4.0 keyboard input!

[Brian McGroarty]

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 FreeBSD boots, it never
happens. If I tap enter to abort the countdown, the keyboard
scrambles perhaps one time in five.

Resetting seems to be the only remedy. This persists with two
different keyboard models and on unplugging and reinserting the
keyboard.


Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights
reserved.
FreeBSD 4.0-CURRENT #10: Fri Aug 13 07:02:32 CDT 1999
[EMAIL PROTECTED]:/usr/src/sys/compile/DOCENT
Timecounter "i8254"  frequency 1193182 Hz
CPU: Celeron (686-class CPU)
  Origin = "GenuineIntel"  Id = 0x665  Stepping = 5
 
Features=0x183fbff
real memory  = 536870912 (524288K bytes)
avail memory = 518422528 (506272K bytes)
Programming 24 pins in IOAPIC #0
FreeBSD/SMP: Multiprocessor motherboard
 cpu0 (BSP): apic id:  0, version: 0x00040011, at 0xfee0
 cpu1 (AP):  apic id:  1, version: 0x00040011, at 0xfee0
 io0 (APIC): apic id:  2, version: 0x00170011, at 0xfec0
Preloaded elf kernel "kernel" at 0xc028f000.
Preloaded userconfig_script "/boot/kernel.conf" at 0xc028f09c.
Pentium Pro MTRR support enabled
Probing for PnP devices:
npx0:  on motherboard
npx0: INT 16 interface
pcib0:  on
motherboard
pci0:  on pcib0
WARNING: "bktr" is usurping "bktr"'s cdevsw[]
pcib1:  at device
1.0 on pci0
pci1:  on pcib1
vga-pci0:  irq 16 at
device 0.0 on pci1
isab0:  at device 7.0 on pci0
ata-pci0:  at device 7.1 on pci0
ata-pci0: Busmastering DMA supported
ata0 at 0x01f0 irq 14 on ata-pci0
ata1 at 0x0170 irq 15 on ata-pci0
chip1:  at device 7.2 on pci0
chip2:  at device 7.3
on pci0
bktr0:  irq 16 at device 16.0 on pci0
iicbb0:  on bti2c0
iicbus0:  on iicbb0 master-only
smbus0:  on bti2c0
Hauppauge Model 62471 A   
Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner, dbx stereo.
pci0: unknown card DD^0878 (vendor=0x109e, dev=0x0878) at 16.1
irq 16
pcm0:  irq 18 at device 18.0 on pci0
pcm0: using I/O space register mapping at 0xef00
fxp0:  irq 19 at device
19.0 on pci0
fxp0: Ethernet address 00:90:27:18:a6:fa
xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 16 at device 20.0 on
pci0
xl0: Ethernet address: 00:50:04:01:77:7b
xl0: autoneg complete, link status good (half-duplex, 100Mbps)
isa0:  on motherboard
fdc0:  at port 0x3f0-0x3f7 irq 6 drq 2 on
isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0:  at port 0x60-0x6f on isa0
atkbd0:  irq 1 on atkbdc0
psm0:  irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
vga0:  at port 0x3b0-0x3df iomem
0xa-0xb on isa0
sc0:  on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: routing 8254 via pin 2
IP packet filtering initialized, divert enabled, rule-based
forwarding disabled, logging disabled
SMP: AP CPU #1 Launched!
ata0: master: setting up UDMA2 mode on PIIX4 chip OK
ad0:  ATA-4 disk at ata0 as master
ad0: 13783MB (28229040 sectors), 28005 cyls, 16 heads, 63 S/T,
512 B/S
ad0: piomode=4, dmamode=2, udmamode=2
ad0: 16 secs/int, 31 depth queue, DMA mode
ata0: slave: setting up UDMA2 mode on PIIX4 chip OK
ad1:  ATA-4 disk at ata0 as slave 
ad1: 21557MB (44150400 sectors), 43800 cyls, 16 heads, 63 S/T,
512 B/S
ad1: piomode=4, dmamode=2, udmamode=2
ad1: 16 secs/int, 31 depth queue, DMA mode
ata1: master: setting up UDMA2 mode on PIIX4 chip OK
ad2:  ATA-4 disk at ata1 as master
ad2: 13783MB (28229040 sectors), 28005 cyls, 16 heads, 63 S/T,
512 B/S
ad2: piomode=4, dmamode=2, udmamode=2
ad2: 16 secs/int, 31 depth queue, DMA mode
atapi: piomode=4, dmamode=2, udmamode=-1
ata1: slave: setting up WDMA2 mode on PIIX3/4 chip OK
atapi: DMA transfer mode set
acd0:  CDROM drive at ata1 as slave 
acd0: drive speed 344 - 1034KB/sec, 384KB cache, DMA
acd0: supported read types: CD-R, CD-RW, CD-DA, packet track
acd0: supported write types: CD-R, CD-RW, test write
acd0: Audio: play, 128 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: no/blank disc inside, unlocked, lock protected




machine i386
cpu I686_CPU
ident   DOCENT
maxusers32

#makeoptionsDEBUG=-g#Build kernel with
gdb(1) debug symbols

options INET
options FFS
options FFS_ROOT
options CD9660
options PROCFS
options COMPAT_43
options KTRACE
options SYSVSHM #SYSV-style shared
memory
options SYSVMSG #SYSV-style message
queues
options SYSVSEM #SYSV-style semaphores

# To make an SMP kernel, the next two are needed
options SMP
options APIC_IO

controller  isa0
controller  pnp0# PnP support for ISA
cont

Re: vty3 and 4.0 snap 080799

[Michael A. Endsley]

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 "ppp" worked great on ALT-F3! I now have a
base installation and kernel source for compiling.
I won't do a full install of 3.2 because I want to follow current.
If I can provide any other information about what is not working on 4.0,
let me know. I will do whatever to get this working :)
Mike



At 03:45 PM 08/13/1999 +0100, Brian Somers wrote:
>> 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 gets the "beep".
>> > HTH in solving my problem
>> > 
>> > fwiw dept.- I have been using FreeBSD since 2.21-R
>
>Errum, if this is a re-install, I may see what the problem is.  I 
>changed sysinstall to run ``ppp install'' as sysinstall now writes an 
>``install'' label into ppp.conf.  Might it be the case that a 
>reinstall doesn't add the ``install'' label ?
>
>-- 
>Brian <[EMAIL PROTECTED]><[EMAIL PROTECTED]>
>     <[EMAIL PROTECTED]>
>Don't _EVER_ lose your sense of humour !  <[EMAIL PROTECTED]>
>
>
>
>
>To Unsubscribe: send mail to [EMAIL PROTECTED]
>with "unsubscribe freebsd-current" in the body of the message
>


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

SUPFLAGS in /etc/make.conf

[Ben Rosengart]

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 update" anyway.

Comments?

--
 Ben

UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ATA - Trouble mounting secondary master

[Mike Smith]

> 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 needed computrons to use the
> "ad" device name. However I have some patches to boot2 that allows
> to boot off an ad root device, provided you dont use the loader, and
> put the rigth boot string in boot.config.

This should now be totally redundant as long as your /etc/fstab entry 
is correct.

-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  [EMAIL PROTECTED]
\\-- Joseph Merrick   \\  [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: VESA module doesn't work with ATI Mach64 RagePro

[Mike Smith]

> 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 2.0/3.0 specification :-( I hate ATI :-(
> 
> Is there any good AGP graphics card with full BIOS support in hardware?

I'm having a lot of success with the Voodoo 3...
-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  [EMAIL PROTECTED]
\\-- Joseph Merrick   \\  [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: recent apm changes

[Mike Smith]

> 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 didn't, in fact, continue running; 
rather they paused and then resumed when you came out of suspend.

The "slept" message indicates that the system spent that amount of time 
inside the BIOS in suspend mode; there is no way for programs to be run 
during that time.

-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  [EMAIL PROTECTED]
\\-- Joseph Merrick   \\  [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: yet more TP 600E fun...

[Mike Smith]

> 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?

Known weirdness in the TP's BIOS not handled properly by the 
bootloader.  I don't have immediate plans to do anything about this; 
you could try hacking the loader to accept the 0x8b value and see if 
that actually works.  Or you could pester IBM to DTRT.

-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  [EMAIL PROTECTED]
\\-- Joseph Merrick   \\  [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Problems with 4.0 keyboard input!

[Warner Losh]

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 [ttyin] 0.01u 0.03s 0% 772K
: load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K
: load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K

I get that too from time to time.  I think that the boot blocks are
putting the keyboard into an odd state since I sometimes can't break
into the boot sequence to boot an alternate kernel.  So far it has
been confined to my Sony VAIO.  Never could come up with a good test
case for it, however

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Problems with 4.0 keyboard input!

[Kazutaka YOKOTA]

[...]
>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 hit the keyboard at the "wrong" moment during keyboard
initialization, the keyboard driver may get confused.

In your case, you type something before the kernel is loaded and that
seems to be causing the trouble.

Such key input should be discarded by the keyboard driver before it
tries to initialize the keyboard.  There may be a nasty timing problem
here...

As a temporary workaround, please apply the following patch to
/sys/dev/atkbd.c and see how it works.

Kazu

>Resetting seems to be the only remedy. This persists with two
>different keyboard models and on unplugging and reinserting the
>keyboard.

Index: atkbd.c
===
RCS file: /src/CVS/src/sys/dev/kbd/atkbd.c,v
retrieving revision 1.12
diff -u -r1.12 atkbd.c
--- atkbd.c 1999/07/18 06:16:25 1.12
+++ atkbd.c 1999/08/14 03:10:40
@@ -1153,7 +1178,7 @@
}
 
/* save the current controller command byte */
-   empty_both_buffers(kbdc, 10);
+   empty_both_buffers(kbdc, 200);
c = get_controller_command_byte(kbdc);
if (c == -1) {
/* CONTROLLER ERROR */


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: yet more TP 600E fun...

[Tom Bartol]

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 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?
> 
> Known weirdness in the TP's BIOS not handled properly by the 
> bootloader.  I don't have immediate plans to do anything about this; 
> you could try hacking the loader to accept the 0x8b value and see if 
> that actually works.  Or you could pester IBM to DTRT.
> 
> -- 
> \\  The mind's the standard   \\  Mike Smith
> \\  of the man.   \\  [EMAIL PROTECTED]
> \\-- Joseph Merrick   \\  [EMAIL PROTECTED]
> 
> 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Problems with 4.0 keyboard input!

[Mike Smith]

> 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 [ttyin] 0.01u 0.03s 0% 772K
> : load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K
> : load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K
> 
> I get that too from time to time.  I think that the boot blocks are
> putting the keyboard into an odd state since I sometimes can't break
> into the boot sequence to boot an alternate kernel.  So far it has
> been confined to my Sony VAIO.  Never could come up with a good test
> case for it, however

It's not the boot blocks doing anything explicit; they just use the BIOS.
-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  [EMAIL PROTECTED]
\\-- Joseph Merrick   \\  [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Problems with 4.0 keyboard input!

[Warner Losh]

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 going on, I'm just reporting what
I've seen

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: yet more TP 600E fun...

[Mike Smith]

> 
> 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; floppies 
from 0 upwards, fixed-disk devices from 0x80 upwards.   The loader 
searches upwards from 0 and from 0x80 until it fails to find a unit and 
stops there. It doesn't search all of the unit numbers because 
many BIOS implementations seem to wrap, eg. you may find that unit 0x90 
is the same as unit 0x80.  You can't be sure about where the wrap point 
will be, either.

Normally, when you're booting an El Torito image, the virtual floppy is
substituted for drive 0 (ie. you can't get at the real first floppy
drive). I can see why IBM would move it elsewhere, but 0x8b is just
about the most stupid place they could have put it.

This is the code (in /sys/boot/i386/libi386/biosdisk.c) that probes for 
BIOS disk units.  You try replacing the 'break' with 'continue' and see 
if it finds a device at 0x8b.  If it does, let me know and I'll send 
you some more complete patches that will always probe the claimed boot 
device.

static int
bd_init(void) 
{
int base, unit;

/* sequence 0, 0x80 */
for (base = 0; base <= 0x80; base += 0x80) {
for (unit = base; (nbdinfo < MAXBDDEV); unit++) {
bdinfo[nbdinfo].bd_unit = unit;
bdinfo[nbdinfo].bd_flags = (unit < 0x80) ? BD_FLOPPY : 0;

/* XXX add EDD probes */
if (!bd_int13probe(&bdinfo[nbdinfo]))
break;

/* XXX we need "disk aliases" to make this simpler */
printf("BIOS drive %c: is disk%d\n", 
   (unit < 0x80) ? ('A' + unit) : ('C' + unit - 0x80), nbdinfo);
nbdinfo++;
}
}
return(0);
}


> Tom
> 
> 
> On Fri, 13 Aug 1999, Mike Smith wrote:
> 
> > > 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?
> > 
> > Known weirdness in the TP's BIOS not handled properly by the 
> > bootloader.  I don't have immediate plans to do anything about this; 
> > you could try hacking the loader to accept the 0x8b value and see if 
> > that actually works.  Or you could pester IBM to DTRT.
> > 
> > -- 
> > \\  The mind's the standard   \\  Mike Smith
> > \\  of the man.   \\  [EMAIL PROTECTED]
> > \\-- Joseph Merrick   \\  [EMAIL PROTECTED]
> > 
> > 
> > 
> > 
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-current" in the body of the message
> > 
> 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 

-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  [EMAIL PROTECTED]
\\-- Joseph Merrick   \\  [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Problems with 4.0 keyboard input!

[Mike Smith]

> 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 going on, I'm just reporting what
> I've seen

*mumble*  We're seeing a few cases where BIOS code in the boot path 
isn't working too well (or at all) when run in vm86 mode. 8(

-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  [EMAIL PROTECTED]
\\-- Joseph Merrick   \\  [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

apm problems.

[Kelvin Farmer]

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 hook for unit 1
Execute APM hook "default suspend"

However, disk activity continues and the monitor isn't blanked.
then, if  a key is pressed:

Recieved APM Event: PMEV_STANDBYRESUME
Execute APM hook "default resume"
resume from suspended mode (Slept 00:28:34)
Execute APM Hook "pcm resume handler"
Called APM sound resume hook for unit 1

If apm -z is given, then the computer does go to sleep, monitor blanks,
no disk activity.

However, if apm -z is used while the computer is doing something (eg:
compiling a kernel)
then the computer goes to sleep, and everything stops, but will not wake
up properly.
no new process can be started ie: any command typed in starts but does
not appear to do anything, and can't be stopped (control -c)
if top is runing before apm -z is done then after resuming,top shows and
continues to update:

process state
top RUN
makeSELECT
ld  getblk
apmdbiord
syncer  drainv
etc.
alt-ctl-delete also does not work.

if more info is needed, just let me know what to do. Thanks =).
(I also don't need the apm features of the motherboard that much, so if
its likely to take a lot of work making apm work right just for this
motherboard it probably isn't worth the effort)

DMESG:

apm0:  on motherboard
apm: APM BIOS version 0102
apm: Code16 0xc00f, Data 0xc400
apm: Code entry 0xef50, Idling CPU disabled, Management enabled
apm: CS_limit=0x, DS_limit=0x
apm: Engaged control enabled
apm: found APM BIOS v1.2, connected at v1.2
apm: Slow Idling CPU disabled
Add hook "default suspend"
Add hook "default resume"

[I didn't originally have the 'idling CPU disabled' set in the bios, but
then the cpu would be put into a slow state while actually busy,
resulting in make world taking many more hours than usual...]

apm:
APM version: 1.2
APM Managment: Enabled
AC Line status: on-line
Battery status: unknown
Remaining battery life: unknown
Remaining battery time: unknown
Number of batteries: 0
Resume timer: Wed Dec 31 18:59:59 1969
Resume on ring indicator: enabled
APM Capacities:
global standby state
global suspend state
resume timer from suspend 


--
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message