detecting internal modem + Booting from DOS
David Maxwell
> Hello from Gregg C Levine usually with Jedi Knight Computers
> It so happens, David, that I already figured that one out. But thank you for
> your advice. All it took was a little common sense, something I have running
> a little low on, this weekend. And asking the Force for assistance. Now the
> fun part will be figuring out how to access the Internet through its builtin
> modem, which uses a port not being noticed by NetBSD 1.4.
First, from your other question - booting from DOS, see the dosboot(8)
manpage. You can compile it from /usr/src/sys/arch/i386/stand/dosboot
The kernel is happy to have root on any one of a variety of filesystems.
Can you post the dmesg lines related to your modem? Is it getting a com
port assigned, or not? What brand/model is it?
--
David Maxwell, da...@vex.net|da...@maxwell.net --> Although some of you out
there might find a microwave oven controlled by a Unix system an attractive
idea, controlling a microwave oven is easily accomplished with the smallest
of microcontrollers. - Russ Hersch - (Microcontroller primer and FAQ)
Kevin P. Neal
> show up on the booting legend. What exactly are dmesg lines? Are they the
> sameones that the kernel prints out during a boot cycle? If they are, then
> no I can't, after all this is the same problem I had with sending a log of
> my first, and second attempts to bring up an X windows session. He isn't as
> yet connected in this operating system lifetime to the Internet. This guy
> is.
Use the command /sbin/dmesg to see the contents of the kernel message
buffer. At boot this contains the messages the kernel printed out
when it was detecting hardware and stuff.
As an aside, note that the message buffer is fixed in size, so when the
kernel prints out enough stuff (at run time) eventually the boot messages
go away. I think they are saved in /var/run/dmesg.boot on new enough
systems (1.4.something?).
As for getting the output of dmesg from one machine to another without
networking, you can save the output of dmesg to a file on a floppy.
The boot floppies do not have to stay in the floppy drive once you
are booted, so you can put another floppy in the drive and save to it.
# mount /dev/fd0a /mnt
# dmesg >/mnt/dmesg.txt
# unmount /mnt
--
Kevin P. Neal http://www.pobox.com/~kpn/
"35. Yekcim Esuom budgeted $100 for renting a truck. How far can he..."
A Survey of Mathematics with Applications, 5th ed, Angel+Porter, p 293
Richard Pennington
I can't seem to get cdrecord to work.
I installed the cdrecord binary package on my 1.4.2 system:
cdrecord-1.8 This program allows you to create CD's on a CD-Recorder
My dmesg output is:
adv0 at pci0 dev 12 function 0: AdvanSys ABP-9xxU SCSI adapter
adv0: interrupting at irq 11
scsibus0 at adv0: 8 targets, 8 luns per target
sd0 at scsibus0 targ 0 lun 0: <iomega, jaz 1GB, J.83> SCSI2 0/direct removable
sd0: drive offline
cd1 at scsibus0 targ 1 lun 0: <HP, CD-Writer+ 9200, 1.0c> SCSI4 5/cdrom removable
From cdrecord -scanbus i get:
Cdrecord 1.8 (i386-unknown-netbsd1.4.2) Copyright (C) 1995-2000 Jörg Schilling
cdrecord: No such file or directory. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
From cdrecord -dummy -speed=4 dev=0,1,0 code4.00.1.13.iso i get:
Cdrecord 1.8 (i386-unknown-netbsd1.4.2) Copyright (C) 1995-2000 Jörg Schilling
scsidev: '0,1,0'
scsibus: 0 target: 1 lun: 0
cdrecord: No such file or directory. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
I noticed a link in /dev scgx->/dev/cd0d. This seemed wrong since my writer is
cd1. I changed the symlink to cd1d with no apparent affect.
Does anyone have a clue as to what I'm doing wrong?
-Rich
--
Richard Pennington Introl Corporation, Milwaukee, WI USA
Email: ri...@introl.com Phone: +1 414-273-6100 Fax: +1 414-273-6106
US and Canada: 1 800-327-7171
Cross development tools for the 68HC05, 68HC08, 6809, 68HC11, 68HC12, 68HC16,
and 68XXX: http://www.introl.com ftp://ftp.introl.com
Jared D. McNeill
Jared
On Mon, 3 Jul 2000, Richard Pennington wrote:
> Date: Mon, 3 Jul 2000 12:38:30 -0500
> From: Richard Pennington <ri...@introl.com>
> To: port...@netbsd.org
> Subject: Trying to use cdrecord.
David Maxwell
> it isn't getting a port assigned to it, at least I think not, it doesn't
> show up on the booting legend. What exactly are dmesg lines? Are they the
The dmesg command will replay the output. You can copy it by hand, OR
mount -t msdos /dev/fd0a /mnt
cp /var/run/dmesg.boot /mnt
umount /mnt
Now you have a DOS floppy you can plug into a net-connected machine for
pasting purposes.
--
David Maxwell, da...@vex.net|da...@maxwell.net --> Mastery of UNIX, like
mastery of language, offers real freedom. The price of freedom is always dear,
but there's no substitute. Personally, I'd rather pay for my freedom than live
in a bitmapped, pop-up-happy dungeon like NT. - Thomas Scoville
Olaf Seibert
> I noticed a link in /dev scgx->/dev/cd0d.
On my Alpha, I also got such a link. Which was wrong because it should
have been to cd0c. Only the i386 port has the partition-d madness.
-Olaf.
--
___ Olaf 'Rhialto' Seibert - rhialto@polder -- Ah only did well at school
\X/ land.nl -- tae git intae an O level class tae git away fae Begbie.
Hi! I am a .signature virus. Copy me into your .signature to help me spead.
Andrew Gillham
> > I noticed a link in /dev scgx->/dev/cd0d.
>
> On my Alpha, I also got such a link. Which was wrong because it should
> have been to cd0c. Only the i386 port has the partition-d madness.
Can your Alpha share a single disk with NetBSD, Linux, VMS and Tru64?
Or eCos, VxWorks, etc?
-Andrew
Olaf Seibert
> Can your Alpha share a single disk with NetBSD, Linux, VMS and Tru64?
> Or eCos, VxWorks, etc?
I don't know, I never tried. (I could theoretically only try Linux
anyway, since I have none of the others)
As far as I am aware, the partition-d hack is rather dependent on the
fdisk-style partitioning anyway. It works only if there is only one "the
netbsd part of the disk". The Amiga port, for instance, does not have a
special d partition and (at least when I used it for a while) NetBSD's
partitions are each partitions in the native Amiga partitioning scheme.
(I am not really suggesting that NetBSD/i386 also do this, because fdisk
partitioning is rather inferior to Amiga's RigidDiskBlock partitioning
scheme).
> -Andrew
Alex Barclay
> > On Mon 03 Jul 2000 at 12:38:30 -0500, Richard Pennington wrote:
> > > I noticed a link in /dev scgx->/dev/cd0d.
> >
> > On my Alpha, I also got such a link. Which was wrong because it should
> > have been to cd0c. Only the i386 port has the partition-d madness.
>
> Can your Alpha share a single disk with NetBSD, Linux, VMS and Tru64?
> Or eCos, VxWorks, etc?
On i386 NetBSD I find it easier to use
cdrecord dev=/dev/cd1d:@ -v speed=4 image.raw
I got the scg stuff working on Solaris 2.7 with the scd driver but I found
the device stuff easier on NetBSD
A.