• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1] 2 3
Author Topic: I just got my Dreamplug  (Read 15991 times)
bwooster0
Newbie
*

Karma: 0
Posts: 44


View Profile
« on: February 10, 2011, 05:54:39 AM »

I just a Dreamplug. Here are some initial observations:

1) uanme -a shows:

Linux sheevaplug-debian 2.6.33.6 #1 PREEMPT Sun Dec 5 22:56:10 CST 2010 armv5tel GNU/Linux

so I think this is lenny

2) i did apt-get install usbutils and lsusb reports:


Bus 001 Device 003: ID 05e3:0726 Genesys Logic, Inc.
Bus 001 Device 004: ID 0d8c:013c C-Media Electronics, Inc.
Bus 001 Device 002: ID 1a40:0101 TERMINUS TECHNOLOGY INC. USB-2.0 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

3) ifconfig -s shows:


Iface   MTU Met   RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP TX-OVR Flg
eth0       1500 0      2292      0      0 0          1237      0      0      0 BMRU
lo        16436 0         4      0      0 0             4      0      0      0 LRU
uap0       1500 0        95      0      0 0           103      0      0      0 BMU


4) using my phones wireless network browser I noticed that the Dreamplug showed that it was hosting a wireless network named "Plug2-uAP-50a0"

I am wondering how I can back up the SD card in the device and then if I can update the system to debian squeeze.

Does anyone know how to do this? Thanks for any help
Logged

pancho
Newbie
*

Karma: 1
Posts: 20


View Profile
« Reply #1 on: February 10, 2011, 01:59:23 PM »

Hi.

Congrats!

To be sure about which Debian version is installed, simply do

$ cat /etc/debian_version

In order to backup the internal SD, I would remove it and read it in another computer (with GNU/Linux).

$ dd if=/dev/mmcblk0 of=dreamplug-rootfs.img bs=4M

should do the trick.  Note that the actual device name may vary.


Cheers,

pancho.
Logged

bwooster0
Newbie
*

Karma: 0
Posts: 44


View Profile
« Reply #2 on: February 12, 2011, 01:47:24 PM »

cat /etc/debian_version gives the following result:

5.0.3

There is no "/dev/mmcblk0" device. I am not sure how the internal disk is represented in /dev

There does not seem to be a port to hook up to a usb cable to get into the uBoot environment

I guess I should be able to update the internal card to a USB thumb drive or SD card
Logged

bwooster0
Newbie
*

Karma: 0
Posts: 44


View Profile
« Reply #3 on: February 12, 2011, 02:18:46 PM »

df -hT shows:

Filesystem    Type    Size  Used Avail Use% Mounted on
tmpfs        tmpfs    251M     0  251M   0% /lib/init/rw
udev         tmpfs     10M  712K  9.4M   7% /dev
tmpfs        tmpfs    251M  4.0K  251M   1% /dev/shm
rootfs      rootfs    906M  633M  227M  74% /
/dev/sda1     vfat     49M  2.6M   46M   6% /media/usb0
tmpfs        tmpfs    251M     0  251M   0% /var/cache/apt

/media/usb and /media/usb0 contain a file called "uImage"

it looks like we can back up /dev/sda1 to back up the internal hard drive

since there isn't a usb port to access the device via a serial terminal I am not sure how we could then access uBoot to tell the device to say boot from an SD card that might contain debian 6.0
Logged

bwooster0
Newbie
*

Karma: 0
Posts: 44


View Profile
« Reply #4 on: February 12, 2011, 03:31:16 PM »

I installed parted and here is what the "print" command shows:

Model: Generic STORAGE DEVICE (scsi)
Disk /dev/sda: 1016MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
 1      31.2kB  51.0MB  50.9MB  primary  fat16             
 2      51.0MB  1015MB  964MB   primary  ext3             

Unfortunately I forgot to order the JTAG unit to use with it! Doh!
I had heard that using ext2 is better because the journaling with ext3 was undesirable

Can anyone recommend a JTAG unit for this device other than the one form globalscale?

Thanks for any help
Logged

dmb
Newbie
*

Karma: 0
Posts: 12


View Profile
« Reply #5 on: February 12, 2011, 08:35:17 PM »

They started shipping the dream plugs, or are you just one of those special people that get it before the rest of us? Unfortunately, I am not aware of a way getting serial/jtag functionality without the jtag box.
Logged

Fletch
Jr. Member
**

Karma: 1
Posts: 61


View Profile
« Reply #6 on: February 13, 2011, 12:02:50 AM »

Interesting.  No Dreamplug images for any uboot, rootfs or kernel in the remository.  ESIA hasn't been updated for over 6 months.  Nothing on the plug wiki.  Makes you wonder how serious Marvell and GSI are about this new model.
Logged

jhf
Newbie
*

Karma: 0
Posts: 1


View Profile
« Reply #7 on: February 13, 2011, 02:39:05 PM »

I'm planning on ordering a Dreamplug soon, so I'm interested in learning as much as I can about the thing and how it's configured.

Bwooster0, do you think you could post the output of `dmesg`, `cat /proc/mounts` and `mount` (the last two might be identical, but if they're only similar, the differences could be illuminating).

Note that the /dev/sda1 device you mentioned corresponds only to the FAT16 partition with the kernel uImage on it.  I'm guessing the / ext3 partition is /dev/sda2 and if you want to back the whole system up you want to make an image of /dev/sda .  But I still need to read up on the the various ways Linux handles MTDs like the Dreamplug's internal SD.  The `dmesg` would really be helpful.

It's possible to create and use an Ext4 filesystem w/o a journal, if journaling is really frowned upon.  I need to find out if uBoot can handle ext4, or if it matters (since the kernel is on FAT16 anyway).

Debian being Debian, it should be possible to upgrade the system in place from Lenny to Squeeze just by changing the distribution in /etc/apt/sources.list and using apt-get -- but that's assuming the OS really is Lenny, and not some hacked-up hybrid like the Guruplug seems to ship with.  Anyway, I think you're really gonna need that JTAG box if you want to upgrade the system, even in place.

Again, I'm just starting to get into this, so please take my words with a grain of salt; recovering from a mistake without the JTAG box may not be possible.

Oh, and how's the cooling situation?  Are the overheating problems of the Guruplug fixed?

Thanks!
Logged

bwooster0
Newbie
*

Karma: 0
Posts: 44


View Profile
« Reply #8 on: February 17, 2011, 12:06:53 PM »

I have ordered a JTAG unit and will have it in a few days.

I plan to back up the internal storage to another SD card. Then I want to modify uboot to have the dreamplug boot from another external SD card.

I want to use the dreamplug as an access point to serve music to the Squeezebox devices in my house.

I don't want to start hacking on the box until I have a good backup / recovery strategy so that if I mess things up I can quickly get back to a good state.

I am concerned to hear that there don't seem repositories for images for the kernel and root filesystem.

I will run the unit overnight and let you know if it gets hot.

Oh yes, the unit did not come with any documentation or any cd that might contain backup images / software / docs.  8(
Logged

bwooster0
Newbie
*

Karma: 0
Posts: 44


View Profile
« Reply #9 on: February 18, 2011, 02:10:17 PM »

mount

tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
rootfs on / type rootfs (rw)
/dev/sda1 on /media/usb0 type vfat (rw,noexec,nodev,sync,noatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
tmpfs on /var/cache/apt type tmpfs (rw,noexec,nosuid)

cat /proc/mounts

rootfs / rootfs rw 0 0
/dev/root / ext3 rw,relatime,errors=continue,data=writeback 0 0
tmpfs /lib/init/rw tmpfs rw,nosuid,relatime,mode=755 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
usbfs /proc/bus/usb usbfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev tmpfs rw,relatime,size=10240k,mode=755 0 0
/dev/sda1 /media/usb0 vfat rw,sync,nodev,noexec,noatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/sda2 /media/usb1 ext3 rw,nodev,noexec,noatime,errors=continue,data=writeback 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620 0 0
tmpfs /var/cache/apt tmpfs rw,nosuid,noexec,relatime 0 0

dmesg

Linux version 2.6.33.6 (root@localhost.localdomain) (gcc version 4.2.0 20070413 (prerelease) (CodeSourcery 2007q1-10. Marvell 2008q3-13 20081204)) #1 PREEMPT Sun Dec 5 22:56:10 CST 2010
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Marvell GuruPlug Reference Board
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 131072
free_area_init_node: node 0, pgdat c052f690, node_mem_map c05de000
  Normal zone: 1024 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 130048 pages, LIFO batch:31
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyS0,115200 root=/dev/sda2 rootdelay=35
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 256MB 256MB = 512MB total
Memory: 513536KB available (4816K code, 862K data, 140K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:114
Console: colour dummy device 80x30
Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Kirkwood: MV88F6281-A1, TCLK=200000000.
Feroceon L2: Cache support initialised.
initial MPP regs: 01112222 11113311 33331111 33333333 00003333 00000222 00000000
  final MPP regs: 01112222 11113311 33331111 33333333 00003333 00000222 00000000
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: 00
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
    (2457000 KHz - 2482000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
    (2474000 KHz - 2494000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
    (5170000 KHz - 5250000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
    (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource orion_clocksource
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 32
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
JFS: nTxBlock = 4014, nTxLock = 32112
msgmni has been set to 1003
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
No NAND device found.
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address f0:ad:4e:00:50:a0
net eth1: port 0 with MAC address f0:ad:4e:00:50:a1
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
mice: PS/2 mouse device common for all mice
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
i2c /dev entries driver
cpuidle: using governor ladder
cpuidle: using governor menu
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
Registered led device: guruplug:red:health
Registered led device: guruplug:green:health
Registered led device: guruplug:red:wmode
Registered led device: guruplug:green:wmode
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
mmc0: new high speed SDIO card at address 0001
mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
Gating clock of unused units
before: 0x00dfc3fd
 after: 0x00cf41d9
rtc-mv rtc-mv: setting system clock to 2010-02-26 13:56:06 UTC (1267192566)
Waiting 35sec before mounting root device...
usb 1-1: new high speed USB device using orion-ehci and address 2
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 1-1.1: new high speed USB device using orion-ehci and address 3
scsi0 : usb-storage 1-1.1:1.0
usb 1-1.4: new full speed USB device using orion-ehci and address 4
input: C-Media Electronics Inc.       USB PnP Sound Device           as /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/1-1.4:1.2/input/input0
generic-usb 0003:0D8C:013C.0001: input: USB HID v1.00 Device [C-Media Electronics Inc.       USB PnP Sound Device          ] on usb-orion-ehci.0-1.4/input2
scsi 0:0:0:0: Direct-Access     Generic  STORAGE DEVICE   9909 PQ: 0 ANSI: 0
sd 0:0:0:0: Attached scsi generic sg0 type 0
scsi 0:0:0:1: Direct-Access     Generic  STORAGE DEVICE   9909 PQ: 0 ANSI: 0
sd 0:0:0:0: [sda] 1984000 512-byte logical blocks: (1.01 GB/968 MiB)
sd 0:0:0:1: Attached scsi generic sg1 type 0
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:1: [sdb] Attached SCSI removable disk
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1 sda2
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Attached SCSI removable disk
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda2): using internal journal
ext3_orphan_cleanup: deleting unreferenced inode 1457
ext3_orphan_cleanup: deleting unreferenced inode 1456
ext3_orphan_cleanup: deleting unreferenced inode 1455
ext3_orphan_cleanup: deleting unreferenced inode 116
ext3_orphan_cleanup: deleting unreferenced inode 115
EXT3-fs (sda2): 5 orphan inodes deleted
EXT3-fs (sda2): recovery complete
EXT3-fs (sda2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 8:2.
Freeing init memory: 140K
sata_mv sata_mv.0: version 1.28
sata_mv sata_mv.0: slots 32 ports 1
scsi1 : sata_mv
ata1: SATA max UDMA/133 irq 21
ata1: SATA link down (SStatus 0 SControl F300)
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
libertas_sdio: Libertas SDIO driver
Bluetooth: HCI socket layer initialized
libertas_sdio: Copyright Pierre Ossman
libertas_sdio mmc0:0001:1: firmware: requesting sd8688_helper.bin
libertas: can't load helper firmware
libertas: failed to load helper firmware
libertas_sdio: probe of mmc0:0001:1 failed with error -2
Bluetooth: vendor=0x2df, device=0x9105, class=255, fn=2
btmrvl_sdio mmc0:0001:2: firmware: requesting sd8688_helper.bin
btmrvl_sdio_download_helper: request_firmware(helper) failed, error code = -2
btmrvl_sdio_download_fw: Failed to download helper!
btmrvl_sdio_probe: Downloading firmware failed!
uap_probe: vendor=0x02DF device=0x9104 class=0 function=1
uap_sdio mmc0:0001:1: firmware: requesting mrvl/helper_sd.bin
usbcore: registered new interface driver snd-usb-audio
uap_sdio mmc0:0001:1: firmware: requesting mrvl/sd8688_ap.bin
UAP FW is active
NET: Registered protocol family 10
ADDRCONF(NETDEV_UP): eth0: link is not ready
eth0: link up, 1000 Mb/s, full duplex, flow control disabled
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
ADDRCONF(NETDEV_UP): uap0: link is not ready
ip_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (8030 buckets, 32120 max)
CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
Bluetooth: L2CAP ver 2.14
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: vendor=0x2df, device=0x9105, class=255, fn=2
Bridge firewalling registered
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
eth0: no IPv6 routers present
Logged

bwooster0
Newbie
*

Karma: 0
Posts: 44


View Profile
« Reply #10 on: February 19, 2011, 05:45:11 PM »

I've had my dreamplug on for more than 24 hours and it is just a little warm. No overheating issues so far.

Of course it wasn't actually doing anything. I was just ssh-ing into it now and then to confirm that it was running.

When I can run it as a squeeze server I will let you know about any heat issues.
Logged

bwooster0
Newbie
*

Karma: 0
Posts: 44


View Profile
« Reply #11 on: February 21, 2011, 05:02:52 PM »

I got my JTAG unit running from Mac OS X. This took a bit of googling and some minor hacking to get working. I found an app called "goSerial" that works well with the FTDI USB device in the Dreamplug.

I got into u-boot and tried a few things.

the version command shows:

U-Boot 2010.06-02334-g8f495d9-dirty (Dec 21 2010 - 15:27:37)
Marvell-GuruPlug

I do not know what version of u-boot this is.

printenv results in

bootcmd=date;setenv ethact egiga0; ${x_bootcmd_ethernet}; setenv ethact egiga1; ${x_bootcmd_ethernet}; ${x_bootcmd_usb}; ${x_bootcmd_kernel}; setenv bootargs ${x_bootargs} ${x_bootargs_root}; bootm 0x6400000;
bootdelay=3
baudrate=115200
x_bootcmd_ethernet=ping 192.168.2.1
x_bootcmd_usb=usb start
x_bootcmd_kernel=fatload usb 0 0x6400000 uImage
x_bootargs=console=ttyS0,115200
x_bootargs_root=root=/dev/sda2 rootdelay=35
burn_spi=sf probe 0; sf erase 0 d0000; sf write 1000000 0 d0000
ethact=egiga0
ethaddr=F0:AD:4E:00:50:A0
eth1addr=F0:AD:4E:00:50:A1
stdin=serial
stdout=serial
stderr=serial

Environment size: 594/4092 bytes

Now I have to figure out how to clone the internal drive to an SD card and have it boot from that card. Note that the bootdelay is 3 second! You don't have much time to hit that key to get into U-Boot!
Logged

bwooster0
Newbie
*

Karma: 0
Posts: 44


View Profile
« Reply #12 on: February 23, 2011, 08:53:51 PM »

I was able to backup the internal SD card to a USB drive. Then by changing the u-boot parameters I was able to boot the device from the USB drive. I really want to be able to boot the drive from an inserted SD card. The current U-Boot does not allow this so now I have to figure out how to upgrade U-Boot to a newer version.

*SIGH* Does anyone know how to do this? I know there is  quite a thread on this forum about U-Boot but I haven't found a definitive solution.
Logged

newitjames
Newbie
*

Karma: 2
Posts: 26



View Profile WWW
« Reply #13 on: February 24, 2011, 02:15:30 AM »

Hi bwooster0,

I noticed the same thing with the Dreamplug I tested. It does not allow the Kernel to be loaded from the SD card but it was quite easy to copy and rename the kernel from the SD onto the 1st partition of the microSD and leave the Rootfs on the SD card.

MicroSd boot
x_bootcmd_kernel=fatload usb 0 0x6400000 uImage
x_bootargs_root=root=/dev/sda2 rootdelay=35

SD card boot
x_bootcmd_kernel=fatload usb 0 0x6400000 uImageSD
x_bootargs_root=root=/dev/sdb2 rootdelay=35

newitjames.
Logged

bwooster0
Newbie
*

Karma: 0
Posts: 44


View Profile
« Reply #14 on: February 24, 2011, 12:00:16 PM »

Thanks! I'll try it.

I was thinking of trying out fedora on the dreamplug. I think it would require using the fedora kernel tho and I am not sure that fedora would have the drivers for the dreamplugs devices (sound, esata, spdif...)
Logged

Pages: [1] 2 3
Print
Jump to: