Re: DragonFly cannot detect existing FreeBSD partitions during install and cannot detect SanDisk USB flash drive during install
On Mon, Jul 28, 2008 at 9:26 AM, Matthew Dillon [EMAIL PROTECTED] wrote: :... : cd md ad acd mfs : : Here, I typed ? where it doesn't show any da device : : :Could it be that you have to load the module at boot from loader.conf? :I know I had to fiddle with this when I set up my system to boot from a :vinum mirror volume. Look in /boot/defaults/loader.conf for options and :make your own adapted loader.conf in /boot. : :-- : : Mvh - Stefan - Yah, it should work if specified in loader.conf. Alternatively one can compile up a custom kernel that builds it in. -Matt Matthew Dillon [EMAIL PROTECTED] Hi Matt and Stefan, By the way, is there any difference when you install DragonFly on a notebook PC and a desktop PC? Because when I try to boot my USB SanDisk on an AMD-64 Athlon machine, it just detects the mount partition of the USB and successfully boots without any problem. Below is the dmesg and df messages output. # dmesg Copyright (c) 2003-2008 The DragonFly Project. Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. DragonFly 2.0.0-RELEASE #1: Sat Jul 19 14:34:49 PDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Calibrating clock(s) ... TSC clock: 207290 Hz, i8254 clock: 1193143 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: AMD Athlon(tm) 64 Processor 3200+ (2000.09-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x20ff2 Stepping = 2 Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2 Features2=0x1SSE3 AMD Features=0xe050NX,AMIE,LM,DSP,3DNow! Data TLB: 32 entries, fully associative Instruction TLB: 32 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 internal cache: 512 kbytes, 64 bytes/line, 1 lines/tag, 16-way associative real memory = 1006305280 (982720K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x007d2000 - 0x3bf9, 998039552 bytes (243662 pages) avail memory = 963477504 (940896K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f bios32: Entry = 0xf0010 (c00f0010) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x31 pnpbios: Found PnP BIOS data at 0xc00f7cf0 pnpbios: Entry = f:8b8a Rev = 1.0 Other BIOS signatures found: Preloaded elf kernel /kernel at 0xc07a5000. Preloaded elf module /modules/ehci.ko at 0xc07a5260. Preloaded elf module /modules/acpi.ko at 0xc07a5308. crypto: crypto core wlan: 802.11 Link Layer Pentium Pro MTRR support enabled md0: Malloc disk Math emulator present pci_open(1):mode 1 addr port (0x0cf8) is 0x80008f64 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=80] is there (id=02041106) pcibios: BIOS version 3.00 Using $PIR table, 11 entries at 0xc00f7bb0 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded01A 0x01 3 4 5 6 7 10 11 12 14 15 embedded01B 0x02 3 4 5 6 7 10 11 12 14 15 embedded10A 0x01 3 4 5 6 7 10 11 12 14 15 embedded0 17C 0x03 3 4 5 6 7 10 11 12 14 15 embedded0 15A 0x02 3 4 5 6 7 10 11 12 14 15 embedded0 15B 0x02 3 4 5 6 7 10 11 12 14 15 embedded0 15C 0x02 3 4 5 6 7 10 11 12 14 15 embedded0 15D 0x02 3 4 5 6 7 10 11 12 14 15 slot 16 30A 0x01 3 4 5 6 7 10 11 12 14 15 slot 16 30B 0x02 3 4 5 6 7 10 11 12 14 15 slot 16 30C 0x03 3 4 5 6 7 10 11 12 14 15 slot 16 30D 0x05 3 4 5 6 7 10 11 12 14 15 embedded20A 0x05 3 4 5 6 7 10 11 12 14 15 embedded20B 0x05 3 4 5 6 7 10 11 12 14 15 embedded20C 0x05 3 4 5 6 7 10 11 12 14 15 embedded20D 0x05 3 4 5 6 7 10 11 12 14 15 slot 16 40A 0x01 3 4 5 6 7 10 11 12 14 15 slot 16 40B 0x02 3 4 5 6 7 10 11 12 14 15 slot 16 40C 0x03 3 4 5 6 7 10 11 12 14 15 slot 16 40D 0x05 3 4 5 6 7 10 11 12 14 15 slot 1 0 11A 0x01 3 4 5 6 7 10 11 12 14 15 slot 1 0 11B 0x02 3 4 5 6 7 10 11 12 14 15 slot 1 0 11C 0x03 3 4 5 6 7 10 11 12 14 15 slot 1 0 11D 0x05 3 4 5 6 7 10 11 12 14 15 slot 2 0 12A 0x02 3 4 5 6 7 10 11 12 14 15 slot 2 0 12B 0x03 3 4 5 6 7 10 11 12 14 15 slot 2 0 12C 0x05 3 4 5 6 7 10 11 12 14 15 slot 2 0 12D 0x01 3 4 5 6 7 10 11 12 14 15 embedded0 16A 0x01 3 4 5 6 7 10 11 12 14 15 embedded0 16B 0x02 3 4
Re: DragonFly cannot detect existing FreeBSD partitions during install and cannot detect SanDisk USB flash drive during install
:Hi Matt and Stefan, : :By the way, is there any difference when you install DragonFly on a :notebook PC and a desktop PC? Because when I try to boot my USB :SanDisk on an AMD-64 Athlon machine, it just detects the mount :partition of the USB and successfully boots without any problem. Below :is the dmesg and df messages output. Being able to boot off of alternative media really comes down to whether the BIOS support it or not. I can boot off a USB stick on my test cubes though I've noticed that the BIOS does not always properly reset the USB ports, causing it to not probe them sometimes on reboot. -Matt
Re: DragonFly cannot detect existing FreeBSD partitions during install and cannot detect SanDisk USB flash drive during install
Matthew Dillon wrote: :Hi Matt and Stefan, : :By the way, is there any difference when you install DragonFly on a :notebook PC and a desktop PC? Because when I try to boot my USB :SanDisk on an AMD-64 Athlon machine, it just detects the mount :partition of the USB and successfully boots without any problem. Below :is the dmesg and df messages output. Being able to boot off of alternative media really comes down to whether the BIOS support it or not. I can boot off a USB stick on my test cubes though I've noticed that the BIOS does not always properly reset the USB ports, causing it to not probe them sometimes on reboot. Yes, I've seen that, and also with my USB mouse occasionally, but it happens rarely so I don't know how to reproduce it.
Re: DragonFly cannot detect existing FreeBSD partitions during install and cannot detect SanDisk USB flash drive during install
On Sat, Jul 26, 2008 at 1:32 PM, Matthew Dillon [EMAIL PROTECTED] wrote: :Hi, : :I have a notebook PC with existing FreeBSD disk partitions of 6.2 and :5.5 releases and then to install DragonFly 2.0 for multiple OS :booting. Before I begin installing DragonFly, I already created a :slice for it using FreeBSD-6.2 installer and I assume the same slice :type of 165 that DragonFly is using but somehow it failed to detect :existing FreeBSD partitions. So, what I did next is to try installing :DragonFly on my 1GB SanDisk USB flash drive but somehow it failed to :detect the device during installation. Although I know this USB :drive's driver is supported by DragonFly as I've have tried plugging :it on another PC with DragonFly. : :da0 at umass-sim0 bus 0 target 0 lun 0 :da0: SanDisk U3 Cruzer Micro 3.21 Removable Direct Access SCSI-2 device :da0: Serial Number \^_ :da0: 1.000MB/s transfers :da0: 973MB (1994385 512 byte sectors: 64H 32S/T 973C) : :Thanks, :Archimedes If the installer isn't seeing the usb device it could be that booting from the live CD or equivalent isn't loading all the necessary modules. You'd have to play with it manually from a root prompt. Try kldload'ing the ehci driver maybe. Maybe we could figure out what is going on from the dmesg output on the laptop after booting the DFly live-cd? -Matt Matthew Dillon [EMAIL PROTECTED] Hi Matt, Yes, you are right. After kldload'ing the ehci driver manually, it automatically detects my SanDisk USB flash drive. I proceeded to installation and got successful with it. However when booting after installation, it stops somewhere while mounting the device. Below is the error encountered. Mounting root from ufs:/dev/da0s1a no disk named 'da0s1a' setrootbyname failed ffs_mountroot: can't find rootvp root mount failed: 6 Manual root filesystem specification: fstype:device Specify root (e.g. ufs:da0s1a) ? List valid disk boot devices panic Just panic abort Abort manual input mountroot mountroot ? Possibly valid device for 'ufs' root: cd md ad acd mfs Here, I typed ? where it doesn't show any da device mountroot panic or abort panic :panic from console Trace beginning at frame 0xc07bdcb8 panic (c07bdcdc,a,c07bdce5,62,c07bdd6c) at panic+0x8c panic (c0539aee,c07bdce0,696e6170,c16a0063,80283) at panic+0x8c vfs_mountroot_ask (c05d6ef8,cb286c20,c07bdd98,c02a54c8,0) at vfs_mountroot_ask+0x1cb vfs_mountroot(0,,7bac00,7c8000,7c8000) at vfs_mountroot + 0xa9 mi_starup (7ba000,d,c0613ab8,c07bdc64,c07bdc54) at mi_startup+0x92 begin () at begin+0x42 Debugger (panic) Stopped at Debugger+0x34 : movb$0,in_Debugger.3949 db Panic is displayed when I invoked abort or panic. Is this a bug? Thanks, Archimedes
Re: DragonFly cannot detect existing FreeBSD partitions during install and cannot detect SanDisk USB flash drive during install
Archimedes Gaviola wrote: Hi Matt, Yes, you are right. After kldload'ing the ehci driver manually, it automatically detects my SanDisk USB flash drive. I proceeded to installation and got successful with it. However when booting after installation, it stops somewhere while mounting the device. Below is the error encountered. Mounting root from ufs:/dev/da0s1a no disk named 'da0s1a' setrootbyname failed ffs_mountroot: can't find rootvp root mount failed: 6 Manual root filesystem specification: fstype:device Specify root (e.g. ufs:da0s1a) ? List valid disk boot devices panic Just panic abort Abort manual input mountroot mountroot ? Possibly valid device for 'ufs' root: cd md ad acd mfs Here, I typed ? where it doesn't show any da device Could it be that you have to load the module at boot from loader.conf? I know I had to fiddle with this when I set up my system to boot from a vinum mirror volume. Look in /boot/defaults/loader.conf for options and make your own adapted loader.conf in /boot. -- Mvh - Stefan -
Re: DragonFly cannot detect existing FreeBSD partitions during install and cannot detect SanDisk USB flash drive during install
:... : cd md ad acd mfs : : Here, I typed ? where it doesn't show any da device : : :Could it be that you have to load the module at boot from loader.conf? :I know I had to fiddle with this when I set up my system to boot from a :vinum mirror volume. Look in /boot/defaults/loader.conf for options and :make your own adapted loader.conf in /boot. : :-- : : Mvh - Stefan - Yah, it should work if specified in loader.conf. Alternatively one can compile up a custom kernel that builds it in. -Matt Matthew Dillon [EMAIL PROTECTED]
Re: DragonFly cannot detect existing FreeBSD partitions during install and cannot detect SanDisk USB flash drive during install
:Hi, : :I have a notebook PC with existing FreeBSD disk partitions of 6.2 and :5.5 releases and then to install DragonFly 2.0 for multiple OS :booting. Before I begin installing DragonFly, I already created a :slice for it using FreeBSD-6.2 installer and I assume the same slice :type of 165 that DragonFly is using but somehow it failed to detect :existing FreeBSD partitions. So, what I did next is to try installing :DragonFly on my 1GB SanDisk USB flash drive but somehow it failed to :detect the device during installation. Although I know this USB :drive's driver is supported by DragonFly as I've have tried plugging :it on another PC with DragonFly. : :da0 at umass-sim0 bus 0 target 0 lun 0 :da0: SanDisk U3 Cruzer Micro 3.21 Removable Direct Access SCSI-2 device :da0: Serial Number \^_ :da0: 1.000MB/s transfers :da0: 973MB (1994385 512 byte sectors: 64H 32S/T 973C) : :Thanks, :Archimedes If the installer isn't seeing the usb device it could be that booting from the live CD or equivalent isn't loading all the necessary modules. You'd have to play with it manually from a root prompt. Try kldload'ing the ehci driver maybe. Maybe we could figure out what is going on from the dmesg output on the laptop after booting the DFly live-cd? -Matt Matthew Dillon [EMAIL PROTECTED]
