[ratzofftoya]

OK, it seems like I'm having a couple distinct issues. Any help would be really appreciated--I'm a 100% novice when it comes to Linux. Probably the first of many. Here's an attempt to capture each one. Running the latest XBMCBuntu build on an i5 Haswell NUC. The only other thing I've done is update to RC1 and install some add-ons.

1.)Can't get into BIOS. I am using a K400 with the dongle plugged into the USB ports. This issue started to occur only AFTER XBMCBuntu was installed. Before that, I could access the BIOS just fine. Now it seems like the keyboard just doesn't work until after the OS boots up. Any ideas?

2.)Can't see second SSD. I currently have two SSDs in the machine. In my first attempt at installing XBMCBuntu, there was some sort of a fatal error caused by the inability to install some kind of "grub." After I restarted, I would just see the BIOS prompt (unresponsive) and an endless black screen. I decided to just open up the case and unplug the SSD that was home to the partial installation, and the system then booted up from the USB drive as normal. I installed XBMCBuntu on the other SSD (the one that was still plugged in) without issue. Then I plugged the first SSD back in. Now, it seems from the File Manager that Ubuntu only sees one of the SSDs. I'd check in BIOS but...see above.

3.)NUC restarts on shutdown. I can't get the darn thing to turn off. This might be a BIOS issue--haven't updated that yet--but see above.

4.)How do I see network drives? I was certainly able to see NFS shares from my NAS within XBMC, but is there any way I can look at my NAS within the Ubuntu file manager, as I can in Windows?

Welp, I think that's it for now. Linux is hard.

[froman]

1) use a regular usb keyboard, not a bluetooth
2) open a terminal on the linux and type this. (without the first "$")
$sudo fdisk -l
(this will list all your block devices, hdds, pendrives, etc.)

$sudo dmesg|grep -i sd
show the logs about the sd* devices (block devices), maybe you can see here what happen with your second disk.

probably your disk is ok, it's just not mounted (you have to mount the devices in some dir to access the data.)

you can check if it's mounted with
$sudo mount
or
$df -h

3) how are you shutting down the system?

4) I do not use much the graphical interface, but you can try this.
in order to mount the nsf share you have to know the IP address and the share name.
example: IP 192.168.100.20 share: porn (internet is for porn right? )
go back to the console and type this
$sudo mount -t nfs 192.168.100.20:/porn /mnt
then you can see the content of the /mnt dir.


and linux it's not hard, it just different, and not friendly


sorry about my english.

[ratzofftoya]

3) how are you shutting down the system?

Turns out this was a BIOS issue, actually.

Thanks!

[Paulpoco]

OK, it seems like I'm having a couple distinct issues. Any help would be really appreciated--I'm a 100% novice when it comes to Linux. Probably the first of many. Here's an attempt to capture each one. Running the latest XBMCBuntu build on an i5 Haswell NUC. The only other thing I've done is update to RC1 and install some add-ons.

2.)Can't see second SSD. I currently have two SSDs in the machine. In my first attempt at installing XBMCBuntu, there was some sort of a fatal error caused by the inability to install some kind of "grub." After I restarted, I would just see the BIOS prompt (unresponsive) and an endless black screen. I decided to just open up the case and unplug the SSD that was home to the partial installation, and the system then booted up from the USB drive as normal. I installed XBMCBuntu on the other SSD (the one that was still plugged in) without issue. Then I plugged the first SSD back in. Now, it seems from the File Manager that Ubuntu only sees one of the SSDs. I'd check in BIOS but...see above.

Welp, I think that's it for now. Linux is hard.

You have to update your /etc/fstab file so it mounts other drives at boot.

Next we will get the /dev and UUID names. Results below are just an example of my drives.

xbmc@xbmc:~$ sudo blkid
/dev/sda1: UUID="4be2e917-0f24-4a15-920c-4a1a65a89d5c" TYPE="ext4"
/dev/sda2: UUID="ded90d8c-222d-4e84-902d-f0a4ac3bbb61" TYPE="swap"
/dev/sda3: UUID="828b3517-cbf8-415e-acf7-bd65f20c1588" TYPE="ext4"
/dev/sdb2: UUID="8ae4cad3-9a5d-49fd-89eb-649d348e9ce2" TYPE="ext4"

Whatever you want to call your other drive, good to use the /dev/sdxx name. In my case I made two directories sda3 and sdb2.

xbmc@xbmc:~$ cd /media
xbmc@xbmc:~$ sudo mkdir sdb1

Next edit the /etc/fstab file.

xbmc@xbmc:~$ sudo nano /etc/fstab

Make yours look similar to what I have listed below. Do not change the entries already listed. Change the UUID and /media/sdxx to match yours. In my /etc/fstab I added the last 4 lines at the bottom.

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=4be2e917-0f24-4a15-920c-4a1a65a89d5c / ext4 errors=remount-ro 0 1
# swap was on /dev/sda2 during installation
UUID=ded90d8c-222d-4e84-902d-f0a4ac3bbb61 none swap sw 0 0
# /dev/sda3
UUID=828b3517-cbf8-415e-acf7-bd65f20c1588 /media/sda3 ext4 auto,user,rw,exec 0 0
# /dev/sdb2
UUID=8ae4cad3-9a5d-49fd-89eb-649d348e9ce2 /media/sdb2 ext4 auto,user,rw,exec 0 0