install to sd card

Questions about the installation of FreeBSD
monz
Posts: 6
Joined: Tue Jul 02, 2013 4:06 pm

install to sd card

Post by monz »

I would like to install GhostBSD 3.1 (LXDE version) to an mmc SDCH card. I have searched online but found no information about this. In fact, I cannot even find information about how to mount an mmc card in GhostBSD.

I have installed a few Linux systems onto sd cards and they work fine. Please help. Thanks.
User avatar
ericbsd
Developer
Posts: 2052
Joined: Mon Nov 19, 2012 7:54 pm

Re: install to sd card

Post by ericbsd »

you want to install GhostBSD .imf on sd card or install GhostBSD on a sd card?
monz
Posts: 6
Joined: Tue Jul 02, 2013 4:06 pm

Re: install to sd card

Post by monz »

I don't know what is GhostBSD .imf

I wanted to just install the regular GhostBSD system onto the card, as if the sd card
was a hard-drive. That's how I did it with the Linux systems.

I would also need to put a boot-loader onto the mbr of the sd card.
For this, I would prefer GRUB, because the card I have is 32 GB, and
I would like to partition it before installing GhostBSD, so that I can
put some other operating systems on it as well. So information on that
would be helpful too ... I'm still not too familiar with GhostBSD's naming
of devices and partitions (I know they are called slices).

(PS - Since I wrote the original question to this forum, I installed GhostBSD onto
a real hard-drive for the first time, and so far I really like it.)
User avatar
ericbsd
Developer
Posts: 2052
Joined: Mon Nov 19, 2012 7:54 pm

Re: install to sd card

Post by ericbsd »

I never use sd card yet, but it should show up as sd* or da*.
* = number
monz
Posts: 6
Joined: Tue Jul 02, 2013 4:06 pm

Re: install to sd card

Post by monz »

On my GhostBSD machine I have the SDHC card inserted into the slot, but the only devices which have slice numbers are ad0 and ada0, and ad0 is a link to ada0 ... and ada0 is the hard-drive which already has GhostBSD installed onto it.

There is no /dev/da* or /dev/sd* .. this is one of the reasons why I said already that I don't know how to even mount the SD card. I'm guess that there must be a module which needs to be loaded, and if so, then how can I load it without rebooting the system?
User avatar
ericbsd
Developer
Posts: 2052
Joined: Mon Nov 19, 2012 7:54 pm

Re: install to sd card

Post by ericbsd »

What kind of card reader is it?

Code: Select all

pciconv -lv 
will show it.
you can

Code: Select all

kldload mmc
and

Code: Select all

kldload sdhci
and see if the card reader shows up.
monz
Posts: 6
Joined: Tue Jul 02, 2013 4:06 pm

Re: install to sd card

Post by monz »

Thanks! .. I did kldload mmc and kldload sdhci and did not get any error messages. But when I ls /dev/ it still shows all the same devices which I had before. Here is that output:

Code: Select all

# ls -l /dev/
total 3
crw-r--r--  1 root  wheel       0,  36 Jul  2 22:55 acpi
lrwxr-xr-x  1 root  wheel            4 Jul  2 22:55 ad0 -> ada0
lrwxr-xr-x  1 root  wheel            6 Jul  2 22:55 ad0s1 -> ada0s1
lrwxr-xr-x  1 root  wheel            7 Jul  2 22:55 ad0s1a -> ada0s1a
lrwxr-xr-x  1 root  wheel            7 Jul  2 22:55 ad0s1b -> ada0s1b
crw-r-----  1 root  operator    0,  94 Jul  2 19:38 ada0
crw-r-----  1 root  operator    0,  96 Jul  2 19:38 ada0s1
crw-r-----  1 root  operator    0,  98 Jul  2 19:38 ada0s1a
crw-r-----  1 root  operator    0, 100 Jul  2 19:38 ada0s1b
crw-------  1 root  wheel       0,  37 Jul  2 22:55 agpgart
crw-------  1 root  wheel       0,  42 Jul  2 22:55 atkbd0
crw-------  1 root  kmem        0,  19 Jul  2 22:55 audit
crw-------  1 root  wheel       0,  11 Jul  2 19:39 bpf
lrwxr-xr-x  1 root  wheel            3 Jul  2 22:55 bpf0 -> bpf
crw-rw-rw-  1 root  wheel       0,  45 Jul  2 22:55 bpsm0
dr-xr-xr-x  2 root  wheel          512 Jul  2 22:55 cam
crw-rw-rw-  1 root  wheel       0,  88 Jul  2 22:55 cardbus1.0.cis
lrwxr-xr-x  1 root  wheel           14 Jul  2 22:55 cardbus1.cis -> cardbus1.0.cis
crw-rw-rw-  1 root  wheel       0,  93 Jul  2 19:38 cd0
crw-------  1 root  wheel       0,   3 Jul  6 04:15 console
crw-------  1 root  wheel       0,  71 Jul  2 22:55 consolectl
crw-rw-rw-  1 root  wheel       0,  10 Jul  2 22:55 ctty
crw-rw----  1 uucp  dialer      0,  49 Jul  2 22:55 cuau0
crw-rw----  1 uucp  dialer      0,  50 Jul  2 22:55 cuau0.init
crw-rw----  1 uucp  dialer      0,  51 Jul  2 22:55 cuau0.lock
crw-------  1 root  wheel       0,  33 Jul  2 22:55 dcons
crw-------  1 root  wheel       0,   6 Jul  2 22:55 devctl
cr--------  1 root  wheel       0,  90 Jul  2 22:55 devstat
crw-------  1 root  wheel       0,  34 Jul  2 22:55 dgdb
dr-xr-xr-x  2 root  wheel          512 Jul  2 19:39 dri
crw-rw-rw-  1 root  wheel       0, 121 Jul  5 14:28 dsp0.0
dr-xr-xr-x  2 root  wheel          512 Jul  2 22:55 fd
crw-------  1 root  wheel       0,  13 Jul  2 22:55 fido
crw-r-----  1 root  operator    0,   4 Jul  2 22:55 geom.ctl
crw-------  1 root  wheel       0,  20 Jul  2 19:38 io
lrwxr-xr-x  1 root  wheel            6 Jul  2 22:55 kbd0 -> atkbd0
lrwxr-xr-x  1 root  wheel            7 Jul  2 22:55 kbd1 -> kbdmux0
crw-------  1 root  wheel       0,  14 Jul  2 22:55 kbdmux0
crw-------  1 root  wheel       0,   7 Jul  2 22:55 klog
crw-r-----  1 root  kmem        0,  18 Jul  2 22:55 kmem
dr-xr-xr-x  2 root  wheel          512 Jul  2 22:55 label
lrwxr-xr-x  1 root  wheel           12 Jul  2 19:39 log -> /var/run/log
crw-rw----  1 root  cups        0,  52 Jul  2 22:55 lpt0
crw-rw----  1 root  cups        0,  53 Jul  2 22:55 lpt0.ctl
crw-------  1 root  wheel       0,  75 Jul  2 22:55 mdctl
crw-r-----  1 root  kmem        0,  17 Jul  2 19:38 mem
crw-rw-rw-  1 root  wheel       0,   8 Jul  2 22:55 midistat
crw-rw-rw-  1 root  wheel       0,  41 Jul  2 19:38 mixer0
crw-------  1 root  kmem        0,  16 Jul  2 22:55 nfslock
crw-rw-rw-  1 root  wheel       0,  21 Jul  7 02:22 null
crw-------  1 root  operator    0,  91 Jul  2 22:55 pass0
crw-------  1 root  operator    0,  92 Jul  2 22:55 pass1
crw-rw-rw-  1 root  wheel       0,  38 Jul  2 22:55 pccard0.cis
crw-rw-rw-  1 root  wheel       0,  39 Jul  2 22:55 pccard1.cis
crw-rw-rw-  1 root  wheel       0,  40 Jul  2 22:55 pccard2.cis
crw-r--r--  1 root  wheel       0,  23 Jul  2 19:38 pci
crw-------  1 root  wheel       0,  54 Jul  2 22:55 ppi0
crw-rw-rw-  1 root  wheel       0,  44 Jul  2 19:39 psm0
crw-rw-rw-  1 root  wheel       0,  30 Jul  2 22:55 ptmx
dr-xr-xr-x  2 root  wheel          512 Jul  3 00:08 pts
crw-rw-rw-  1 root  wheel       0,  31 Jul  2 19:38 random
cr--r--r--  1 root  wheel       0,   5 Jul  2 19:38 sndstat
lrwxr-xr-x  1 root  wheel            4 Jul  2 22:55 stderr -> fd/2
lrwxr-xr-x  1 root  wheel            4 Jul  2 22:55 stdin -> fd/0
lrwxr-xr-x  1 root  wheel            4 Jul  2 22:55 stdout -> fd/1
crw-------  1 root  wheel       0,   9 Jul  2 22:55 sysmouse
crw-------  1 root  wheel       0,  46 Jul  2 22:55 ttyu0
crw-------  1 root  wheel       0,  47 Jul  2 22:55 ttyu0.init
crw-------  1 root  wheel       0,  48 Jul  2 22:55 ttyu0.lock
crw-------  1 root  wheel       0,  55 Jul  2 19:39 ttyv0
crw-------  1 root  wheel       0,  56 Jul  2 19:39 ttyv1
crw-------  1 root  wheel       0,  57 Jul  2 19:39 ttyv2
crw-------  1 root  wheel       0,  58 Jul  2 19:39 ttyv3
crw-------  1 root  wheel       0,  59 Jul  2 19:39 ttyv4
crw-------  1 root  wheel       0,  60 Jul  2 19:39 ttyv5
crw-------  1 root  wheel       0,  61 Jul  2 19:39 ttyv6
crw-------  1 root  wheel       0,  62 Jul  2 19:39 ttyv7
crw-------  1 root  wheel       0,  63 Jul  2 19:38 ttyv8
crw-------  1 root  wheel       0,  64 Jul  2 19:38 ttyv9
crw-------  1 root  wheel       0,  65 Jul  2 19:38 ttyva
crw-------  1 root  wheel       0,  66 Jul  2 19:38 ttyvb
crw-------  1 root  wheel       0,  67 Jul  2 19:38 ttyvc
crw-------  1 root  wheel       0,  68 Jul  2 19:38 ttyvd
crw-------  1 root  wheel       0,  69 Jul  2 19:38 ttyve
crw-------  1 root  wheel       0,  70 Jul  2 19:38 ttyvf
lrw-rw----  1 root  cups             9 Jul  2 22:55 ugen0.1 -> usb/0.1.0
lrw-rw----  1 root  cups             9 Jul  2 22:55 ugen1.1 -> usb/1.1.0
lrw-rw----  1 root  cups             9 Jul  2 22:55 ugen2.1 -> usb/2.1.0
lrw-rw----  1 root  cups             9 Jul  2 22:55 ugen3.1 -> usb/3.1.0
lrwxr-xr-x  1 root  wheel            6 Jul  2 22:55 urandom -> random
drwxrwx---  2 root  cups           512 Jul  2 22:55 usb
crwxrwx---  1 root  cups        0,  73 Jul  2 22:55 usbctl
crw-rw----  1 root  wheel       0,  74 Jul  2 22:55 xpt0
crw-rw-rw-  1 root  wheel       0,  22 Jul  2 22:55 zero

You made a typo: it should be pciconf -lv. Here is the complete output from that command on my system (the Atheros is a cardbus wifi card, the Intel wifi shows up here and must be an internal wifi, but I have never been able to get it working with GhostBSD, PC-BSD, or Linux).

Code: Select all

# pciconf -lv
hostb0@pci0:0:0:0:	class=0x060000 card=0x0890103c chip=0x33408086 rev=0x03 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '82855PM Processor to I/O Controller'
    class      = bridge
    subclass   = HOST-PCI
pcib1@pci0:0:1:0:	class=0x060400 card=0x00000000 chip=0x33418086 rev=0x03 hdr=0x01
    vendor     = 'Intel Corporation'
    device     = '82855PM Processor to AGP Controller'
    class      = bridge
    subclass   = PCI-PCI
uhci0@pci0:0:29:0:	class=0x0c0300 card=0x0890103c chip=0x24c28086 rev=0x03 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller'
    class      = serial bus
    subclass   = USB
uhci1@pci0:0:29:1:	class=0x0c0300 card=0x0890103c chip=0x24c48086 rev=0x03 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller'
    class      = serial bus
    subclass   = USB
uhci2@pci0:0:29:2:	class=0x0c0300 card=0x0890103c chip=0x24c78086 rev=0x03 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller'
    class      = serial bus
    subclass   = USB
ehci0@pci0:0:29:7:	class=0x0c0320 card=0x0890103c chip=0x24cd8086 rev=0x03 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller'
    class      = serial bus
    subclass   = USB
pcib2@pci0:0:30:0:	class=0x060400 card=0x00000000 chip=0x24488086 rev=0x83 hdr=0x01
    vendor     = 'Intel Corporation'
    device     = '82801 Mobile PCI Bridge'
    class      = bridge
    subclass   = PCI-PCI
isab0@pci0:0:31:0:	class=0x060100 card=0x00000000 chip=0x24cc8086 rev=0x03 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '82801DBM (ICH4-M) LPC Interface Bridge'
    class      = bridge
    subclass   = PCI-ISA
atapci0@pci0:0:31:1:	class=0x01018a card=0x0890103c chip=0x24ca8086 rev=0x03 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '82801DBM (ICH4-M) IDE Controller'
    class      = mass storage
    subclass   = ATA
pcm0@pci0:0:31:5:	class=0x040100 card=0x0890103c chip=0x24c58086 rev=0x03 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller'
    class      = multimedia
    subclass   = audio
none0@pci0:0:31:6:	class=0x070300 card=0x0890103c chip=0x24c68086 rev=0x03 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller'
    class      = simple comms
    subclass   = generic modem
vgapci0@pci0:1:0:0:	class=0x030000 card=0x0890103c chip=0x4e501002 rev=0x00 hdr=0x00
    vendor     = 'ATI Technologies Inc'
    device     = 'RV350 [Mobility Radeon 9600 M10]'
    class      = display
    subclass   = VGA
ipw0@pci0:2:4:0:	class=0x028000 card=0x25278086 chip=0x10438086 rev=0x04 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = 'PRO/Wireless LAN 2100 3B Mini PCI Adapter'
    class      = network
cbb0@pci0:2:6:0:	class=0x060700 card=0x0890103c chip=0x72231217 rev=0x00 hdr=0x02
    vendor     = 'O2 Micro, Inc.'
    device     = 'OZ711M3/MC3 4-in-1 MemoryCardBus Controller'
    class      = bridge
    subclass   = PCI-CardBus
cbb1@pci0:2:6:1:	class=0x060700 card=0x0890103c chip=0x72231217 rev=0x00 hdr=0x02
    vendor     = 'O2 Micro, Inc.'
    device     = 'OZ711M3/MC3 4-in-1 MemoryCardBus Controller'
    class      = bridge
    subclass   = PCI-CardBus
none1@pci0:2:6:2:	class=0x088000 card=0x0890103c chip=0x71101217 rev=0x00 hdr=0x00
    vendor     = 'O2 Micro, Inc.'
    device     = 'OZ711Mx 4-in-1 MemoryCardBus Accelerator'
    class      = base peripheral
cbb2@pci0:2:6:3:	class=0x060700 card=0x0890103c chip=0x72231217 rev=0x00 hdr=0x02
    vendor     = 'O2 Micro, Inc.'
    device     = 'OZ711M3/MC3 4-in-1 MemoryCardBus Controller'
    class      = bridge
    subclass   = PCI-CardBus
bge0@pci0:2:14:0:	class=0x020000 card=0x0890103c chip=0x165e14e4 rev=0x03 hdr=0x00
    vendor     = 'Broadcom Corporation'
    device     = 'NetXtreme BCM5705M_2 Gigabit Ethernet'
    class      = network
    subclass   = ethernet
ath0@pci0:4:0:0:	class=0x020000 card=0x32021186 chip=0x0013168c rev=0x01 hdr=0x00
    vendor     = 'Atheros Communications Inc.'
    device     = 'Atheros AR5001X+ Wireless Network Adapter'
    class      = network
    subclass   = ethernet
User avatar
ericbsd
Developer
Posts: 2052
Joined: Mon Nov 19, 2012 7:54 pm

Re: install to sd card

Post by ericbsd »

can you try

Code: Select all

kldload mmcsd
too
User avatar
ericbsd
Developer
Posts: 2052
Joined: Mon Nov 19, 2012 7:54 pm

Re: install to sd card

Post by ericbsd »

The best way to know if you card reader is supported is Ctrl+Alt+F1 in the same time it will bring you to tty0 put your sd card in. You will see on which dev/*. To go back to the desktop Ctrl+Alt+F9.

You can also look /var/log/dmesg.*
monz
Posts: 6
Joined: Tue Jul 02, 2013 4:06 pm

Re: install to sd card

Post by monz »

I tried loading all three modules, each one separately, and also all three on top of each other. Now kldstat shows me that they are loaded, but there is still no new information, neither in pciconf nor in dmesg.

Any other ideas?

Maybe I should mention that this is an old computer: an HP Compaq nc6000 laptop, and a very new sd card: a 32 gb Sony SF-32UY with the U-1 and C-10 symbols printed on it. Perhaps the problem lies there?
Post Reply