DragonFly BSD
DragonFly kernel List (threaded) for 2004-08
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: cvsup, installer and booting


From: "Martin P. Hellwig" <mhellwig@xxxxxxxxx>
Date: Tue, 03 Aug 2004 19:56:04 +0200

George Georgalis wrote:
Hi - Yesterday decided to try DragonFly. I have a lot of Linux
background and had a crash course, on the job training of FreeBSD a
while back... so I have a clue, but device names, packaging, and some
tools are different from what I'm use to.

My first attempt installed and booted fine; but I had a problem
with cvsup. I ended up using "*default release=cvs" in both
dragonfly-cvs-supfile and FreeBSD-ports-supfile, but that gives me "*,v"
files. Is there a way to use them locally or should I use "*default
release=cvs tag=." to get actual Makefiles?

It is the CVS pository and has too be checked out to do anything usefull (the cvs -R -d %PATH% checkout %WHATEVER% way).
Read the README file in the root of your install CD-ROM, it is explained there what to do.



Another question about DragonFly cvsup. Is it okay to use the same "base=/usr" in both dragonfly-cvs-supfile and FreeBSD-ports-supfile, or should I use "base=/usr/local/FreeBSD" for those ports, why will sharing /usr not be a problem? I presume I need separate prefix directories? (below prefix was changed because of disk space)

#FreeBSD-ports-supfile
*default base=/usr
*default prefix=/usr/fcvs
#*default release=cvs
*default release=cvs tag=.

#dragonfly-cvs-supfile
*default base=/usr
*default prefix=/usr/dcvs
#*default release=cvs
*default release=cvs tag=.


/usr will do fine in both cases for the base and the prefix, these are btw the checked out update files and wil create dirs the first time you use it, for the FreeBSD ports files it will be /usr/ports and for the DragonFly source it will be /usr/src





I had more serious problems on my second machine. The installer uses UDMA33. Linux has problems setting the speed automatically (it uses UDMA66), but I can speed it up manually (commands below). The bios supports ATA 133 and there is a (1 channel) 80 pin ribbon. Can I fix this from the DragonFly installer?

Sorry I don't know that maybe somebody else.




The show stopper is it doesn't boot. The bootloader says something like
this:
f1 DOS
f2 BSD
f5 xxx

I don't remember exactly what xxx is but it does successfully launch
the bootloader on what bios sees as the first disk on an auxiliary ata
controller, xxx (it's an sata).

I've used the installer defaults, and installed DragonFly on
/dev/ad0s2{a,d,e,f,g} for / /var /tmp /usr /home
plus a swap in there somewhere.

When I went back to the installer to repair the install, it saw them
(the slice?) but it couldn't mount the bsd partitions. Second attempt to
install did the same thing. What's going on here? Output of some linux
commands are below.

Yeah had the same, I reinstalled it and checked out both options in the bootloader questions and it worked for me.



I had a good feeling about DragonFly from the first time I heard of it, and now it's being mentioned in very respectable circles. The undertaking is impressive and I commend the developers who are behind it!

// George



@715 root@sta:~/ # hdparm /dev/hda


/dev/hda:
 multcount    =  0 (off)
 IO_support   =  1 (32-bit)
 unmaskirq    =  1 (on)
 using_dma    =  0 (off)
 keepsettings =  0 (off)
 readonly     =  0 (off)
 readahead    = 256 (on)
 geometry     = 16383/255/63, sectors = 120103200, start = 0
@729 root@sta:~/ # hdparm -c 1 -d1 -p 4 -X udma5 -m 16 -z /dev/hda

/dev/hda:
 attempting to set PIO mode to 4
 setting 32-bit IO_support flag to 1
 setting multcount to 16
 setting using_dma to 1 (on)
 setting xfermode to 69 (UltraDMA mode5)
 multcount    = 16 (on)
 IO_support   =  1 (32-bit)
 using_dma    =  1 (on)
@729 root@sta:~/ # hdparm /dev/hda

/dev/hda:
multcount = 16 (on)
IO_support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
geometry = 16383/255/63, sectors = 120103200, start = 0
@732 root@sta:~/ # hdparm -I /dev/hda | egrep '(DMA|PIO)' | grep -v QUEUED
DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4 udma5 PIO: pio0 pio1 pio2 pio3 pio4 @739 root@sta:~/ # lspci
00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 3123
00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP]
00:0d.0 FireWire (IEEE 1394): VIA Technologies, Inc. OHCI Compliant IEEE 1394 Host Controller (rev 80)
00:10.0 USB Controller: VIA Technologies, Inc. UHCI USB (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. UHCI USB (rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc.: Unknown device 3104 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc.: Unknown device 3177
00:11.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. AC97 Audio Controller (rev 50)
00:12.0 Ethernet controller: VIA Technologies, Inc. Ethernet Controller (rev 74)
00:14.0 RAID bus controller: CMD Technology Inc: Unknown device 3112 (rev 02)
01:00.0 VGA compatible controller: VIA Technologies, Inc.: Unknown device 3122 (rev 03)
@739 root@sta:~/ # fdisk -l /dev/hda


Disk /dev/hda: 255 heads, 63 sectors, 7476 cylinders
Units = cylinders of 16065 * 512 bytes

Device Boot Start End Blocks Id System
/dev/hda1 1 1785 14337981 c Win95 FAT32 (LBA)
/dev/hda2 * 1786 7476 45712957+ a5 FreeBSD
@740 root@sta:~/ # cat /proc/cpuinfo processor : 0
vendor_id : CentaurHauls
cpu family : 6
model : 9
model name : VIA Nehemiah
stepping : 5
cpu MHz : 999.937
cache size : 64 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu de pse tsc msr mtrr pge cmov mmx fxsr sse rng rng_en
bogomips : 1974.27




-- mph



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]