FedoraForum.org - Fedora Support Forums and Community
Page 1 of 2 1 2 LastLast
Results 1 to 15 of 16
  1. #1
    Join Date
    Sep 2017
    Location
    Other Planet
    Posts
    9

    Unhappy Fedora 26, FakeRAID, unrecognised m.2 SSD

    I’m trying to install fedora workstation on 2xm.2 in raid0 made with intel RST and i’m running into issues.

    First one is that after creating installation usb and loading system it halts.
    Another option (bit better) was to create bootable usb from fedora image, boot UEFI, and it loads the system, but after trying to “install to hdd” setup doesn’t show ssd at all.

    I tried to switch off the raid too and had no luck to find ssd.

    somewhere found suggestion to use mdadm --assembly --scan but this one
    gave nothing too as it didn’t find anything.

    All in all i’m not very experienced in linux as i’m coming from osx, but would to switch to linux instead of using windows. Can anyone guide me and share some information what steps are necessary to make this raid0 configuration visible, to be able to write fedora to disk?

  2. #2
    Join Date
    Aug 2007
    Posts
    159

    Re: Fedora 26, FakeRAID, unrecognised m.2 SSD

    I’m trying to install fedora workstation on 2xm.2 in raid0 made with intel RST and i’m running into issues.
    All in all i’m not very experienced in linux as i’m coming from osx, but would to switch to linux instead of using windows.
    What you are attempting is a challenging install even for experienced Linux users. It isn't something a beginner should try for their first install.

    First a clarification is needed. Are these M.2 form factor PCIe SSDs, possibly with NMVe ? I noticed you don't capitalize anything even references to yourself ( i'm as opposed to I'm ). The proper name is capitalized M.2.

    Please provide the model numbers of these SSDs.

    If these are NMVe then that could be why the installer doesn't recognize them immediately.

    Also if these are NMVe is there a reason you need two of these in parallel ? Is the speed of one not fast enough ? One would be 3-4 times faster than a SATA SSD.

    If you have two then do a regular non-RAID Fedora install to one and use the second as a data drive.

    somewhere found suggestion to use mdadm --assembly --scan but this one
    gave nothing too as it didn’t find anything.
    This is the command to use if you have already created a mdadm RAID array and want to activate it. As you haven't created anything yet of course it won't find anything.

  3. #3
    Join Date
    Sep 2017
    Location
    Other Planet
    Posts
    9

    Re: Fedora 26, FakeRAID, unrecognised m.2 SSD

    Thank you for advice

    These are two Samsung 960 EVO, they are M.2 NVMe.
    And yes there is a reason why I'm I'm using them in RAID0 (strip) configuration, I'm working with lot's of video files and need to read and write them to the disk. In this configuration my read and write speed are nearly identical.

    Anyway, I think I will buy another one M.2 just for Fedora, As far as I read, there are lot's of people having same issues as me.

  4. #4
    Join Date
    Sep 2017
    Location
    Other Planet
    Posts
    9

    Re: Fedora 26, FakeRAID, unrecognised m.2 SSD

    I thought I will buy SATA SSD, for linux, but somehow after installing new SSD I can't even boot Live Fedora USB ;(

  5. #5
    Join Date
    Aug 2007
    Posts
    159

    Re: Fedora 26, FakeRAID, unrecognised m.2 SSD

    Have you read the Intel paper describing how Intel RST can be used with NVMe SSDs by Linux mdadm RAID ? It should be your starting point.

    https://www.intel.com/content/dam/su...or%20Linux.pdf

    I thought I will buy SATA SSD, for linux, but somehow after installing new SSD I can't even boot Live Fedora USB ;(
    What drive is set for first boot priority in your firmware ? If it is set to the SATA SSD and the SSD is unformatted that may be the problem. You need to set the boot priority to the live USB.
    Last edited by amiga; 20th October 2017 at 06:32 PM.

  6. #6
    Join Date
    Sep 2017
    Location
    Other Planet
    Posts
    9

    Re: Fedora 26, FakeRAID, unrecognised m.2 SSD

    It set to boot from USB.

    So, before installing SATA SSD, I was able to boot no problem, but issue was that there was no disk found later. So couldn't proceed install.

    After installing new SATA SSD, I'm unable to boot at all (load live-USB)
    and the message I get is:

    [1.457557] Error parsing PCC subspaces ftom PCCT
    [1.500924] APCI Error: [SDS0] Namespace lookup failure, AE_NOT_FOUND (20170119/psargs-363)
    [1.500929] APCI Error: [SDS0] Method parse/execution failed [\SHAD._STA] (Node ffff8e121e136730), AE_NOT_FOUND (20170119/psargs-543)
    [1.500941] APCI Error: [SDS0] Namespace lookup failure, AE_NOT_FOUND (20170119/psargs-363)
    [1.500944] APCI Error: [SDS0] Method parse/execution failed [\SHAD._STA] (Node ffff8e121e136730), AE_NOT_FOUND (20170119/psargs-543)
    [1.521462] APCI Error: [SDS0] Namespace lookup failure, AE_NOT_FOUND (20170119/psargs-363)
    [1.521544] APCI Error: [SDS0] Method parse/execution failed [\SHAD._STA] (Node ffff8e121e136730), AE_NOT_FOUND (20170119/psargs-543)
    [1.572384] APCI Error: [SDS0] Namespace lookup failure, AE_NOT_FOUND (20170119/psargs-363)
    [1.572388] APCI Error: [SDS0] Method parse/execution failed [\SHAD._STA] (Node ffff8e121e136730), AE_NOT_FOUND (20170119/psargs-543)

    and it stops.

  7. #7
    Join Date
    Aug 2007
    Posts
    159

    Re: Fedora 26, FakeRAID, unrecognised m.2 SSD

    Since you are having APCI errors you should disable APCI at the kernel level by adding apci=off as a kernel parameter of the live USB bootloader. If grub is used typing e usually allows you to edit the boot stanza.

    Did you download and read the Intel paper ? It is exactly what you need.

  8. #8
    Join Date
    Sep 2017
    Location
    Other Planet
    Posts
    9

    Re: Fedora 26, FakeRAID, unrecognised m.2 SSD

    thanks for your help! I was able to boot to the live-usb, but as i found there still no disks shows in installer or gpart, only sba which is USB-Flash. I think it means no linux to me. It's really sad that so simple setups are so complicated.

  9. #9
    Join Date
    Aug 2007
    Posts
    159

    Re: Fedora 26, FakeRAID, unrecognised m.2 SSD

    I was able to boot to the live-usb, but as i found there still no disks shows in installer or gpart, only sba which is USB-Flash. I
    Do you mean GParted and sda ?

    If the SSD is unformatted it may not show up in the installer. Is the new SSD viewable by UEFI firmware ?

    Please run the following and output the results.

    Code:
    $ ls -l /dev/sd*
    $ ls -l /dev/disk/by-id/*
    $ ls -l /dev/disk/by-path/*
    $ sudo fdisk -l

  10. #10
    Join Date
    Sep 2017
    Location
    Other Planet
    Posts
    9

    Re: Fedora 26, FakeRAID, unrecognised m.2 SSD

    Yes, Gparted doesn't show any of disks besides usb. Here is what I get in terminal:

    [liveuser@Unknown-30-9c-23-1c-b3-36-2 ~]$ ls -l /dev/sd*
    brw-rw----. 1 root disk 8, 0 Oct 22 2017 /dev/sda
    brw-rw----. 1 root disk 8, 1 Oct 22 2017 /dev/sda1
    brw-rw----. 1 root disk 8, 2 Oct 22 2017 /dev/sda2
    brw-rw----. 1 root disk 8, 3 Oct 22 2017 /dev/sda3
    [liveuser@Unknown-30-9c-23-1c-b3-36-2 ~]$ ls -l /dev/disk/by-id/*
    lrwxrwxrwx. 1 root root 10 Oct 22 2017 /dev/disk/by-id/dm-name-live-base -> ../../dm-1
    lrwxrwxrwx. 1 root root 10 Oct 22 2017 /dev/disk/by-id/dm-name-live-rw -> ../../dm-0
    lrwxrwxrwx. 1 root root 9 Oct 22 2017 /dev/disk/by-id/usb-PNY_USB_3.0_FD_070D5A7BAEE55573-0:0 -> ../../sda
    lrwxrwxrwx. 1 root root 10 Oct 22 2017 /dev/disk/by-id/usb-PNY_USB_3.0_FD_070D5A7BAEE55573-0:0-part1 -> ../../sda1
    lrwxrwxrwx. 1 root root 10 Oct 22 2017 /dev/disk/by-id/usb-PNY_USB_3.0_FD_070D5A7BAEE55573-0:0-part2 -> ../../sda2
    lrwxrwxrwx. 1 root root 10 Oct 22 2017 /dev/disk/by-id/usb-PNY_USB_3.0_FD_070D5A7BAEE55573-0:0-part3 -> ../../sda3
    [liveuser@Unknown-30-9c-23-1c-b3-36-2 ~]$ ls -l /dev/disk/by-path/*
    lrwxrwxrwx. 1 root root 9 Oct 22 2017 /dev/disk/by-path/pci-0000:00:14.0-usb-0:3:1.0-scsi-0:0:0:0 -> ../../sda
    lrwxrwxrwx. 1 root root 10 Oct 22 2017 /dev/disk/by-path/pci-0000:00:14.0-usb-0:3:1.0-scsi-0:0:0:0-part1 -> ../../sda1
    lrwxrwxrwx. 1 root root 10 Oct 22 2017 /dev/disk/by-path/pci-0000:00:14.0-usb-0:3:1.0-scsi-0:0:0:0-part2 -> ../../sda2
    lrwxrwxrwx. 1 root root 10 Oct 22 2017 /dev/disk/by-path/pci-0000:00:14.0-usb-0:3:1.0-scsi-0:0:0:0-part3 -> ../../sda3
    [liveuser@Unknown-30-9c-23-1c-b3-36-2 ~]$ sudo fdisk -l
    Disk /dev/sda: 28.9 GiB, 31004295168 bytes, 60555264 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x0975cb23

    Device Boot Start End Sectors Size Id Type
    /dev/sda1 * 0 3053567 3053568 1.5G 0 Empty
    /dev/sda2 104772 117775 13004 6.4M ef EFI (FAT-12/16/32)
    /dev/sda3 117776 145855 28080 13.7M 0 Empty


    Disk /dev/loop0: 1.4 GiB, 1482072064 bytes, 2894672 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop1: 6.5 GiB, 6981419008 bytes, 13635584 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop2: 512 MiB, 536870912 bytes, 1048576 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/mapper/live-rw: 6.5 GiB, 6981419008 bytes, 13635584 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/mapper/live-base: 6.5 GiB, 6981419008 bytes, 13635584 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    [liveuser@Unknown-30-9c-23-1c-b3-36-2 ~]$
    So I'm unsure why it's impossible to find my other SSD, as on windows OS they work just fine, and from my previous experiences with linux I was able to load
    drives and format them with Gparted and install linux on them with no problems. As I mentioned previously there is raid0 with 2xm.2 drives, but now there is a single SATA SSD on the system too, and I was hoping that OS will find it and will be able to use it but sadly, with no luck. Just to mention, had no luck with ubuntu, mint distros too, so maybe there is some problem with my PC or lack of knowledge.

    Thanks for your help once again.

  11. #11
    Join Date
    Aug 2007
    Posts
    159

    Re: Fedora 26, FakeRAID, unrecognised m.2 SSD

    I just noticed that you never mentioned anything about your hardware such as the chipset version of your motherboard. Is the computer brand new and latest generation ?

    Please post the output of lspci. This will list all of the controllers on your MB such as the SATA controllers.

    Also did you look at the kernel messages during boot to see if the SSD is detected. You can use dmesg or journalctl. The following is part of the ouput when my main SSD is detected.

    Code:
    Oct 22 20:35:10 server47.localdomain smartd[1077]: Device: /dev/sdb [SAT], opened
    Oct 22 20:35:10 server47.localdomain smartd[1077]: Device: /dev/sdb [SAT], Samsung SSD 850 EVO 250GB, S/N:S2R5NX0H524929J, WWN:5-002538-d40e18c38, FW:EMT02B6Q, 250 GB
    Last edited by amiga; 23rd October 2017 at 09:00 AM.

  12. #12
    Join Date
    Sep 2017
    Location
    Other Planet
    Posts
    9

    Re: Fedora 26, FakeRAID, unrecognised m.2 SSD

    this is what I get somthing like that: (I had to shorten this due to too much symbols)

    [liveuser@Unknown-30-9c-23-1c-b3-36 ~]$ lspci
    00:00.0 Host bridge: Intel Corporation Device 2020 (rev 04)
    00:04.0 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04)
    00:05.0 System peripheral: Intel Corporation Sky Lake-E MM/Vt-d Configuration Registers (rev 04)
    00:05.2 System peripheral: Intel Corporation Device 2025 (rev 04)
    00:05.4 PIC: Intel Corporation Device 2026 (rev 04)
    00:08.0 System peripheral: Intel Corporation Sky Lake-E Ubox Registers (rev 04)
    00:08.1 Performance counters: Intel Corporation Sky Lake-E Ubox Registers (rev 04)
    00:08.2 System peripheral: Intel Corporation Sky Lake-E Ubox Registers (rev 04)
    00:14.0 USB controller: Intel Corporation 200 Series PCH USB 3.0 xHCI Controller
    00:14.2 Signal processing controller: Intel Corporation 200 Series PCH Thermal Subsystem
    00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME HECI #1
    00:17.0 RAID bus controller: Intel Corporation SATA Controller [RAID mode]
    00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #1 (rev f0)
    00:1c.2 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #3 (rev f0)
    00:1c.5 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #6 (rev f0)
    00:1f.0 ISA bridge: Intel Corporation Device a2d2
    00:1f.2 Memory controller: Intel Corporation 200 Series PCH PMC
    00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio
    00:1f.4 SMBus: Intel Corporation 200 Series PCH SMBus Controller
    00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V
    01:00.0 USB controller: ASMedia Technology Inc. Device 2142
    02:00.0 USB controller: ASMedia Technology Inc. Device 2142
    03:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
    16:00.0 PCI bridge: Intel Corporation Sky Lake-E PCI Express Root Port A (rev 04)
    16:05.0 System peripheral: Intel Corporation Device 2034 (rev 04)
    16:05.2 System peripheral: Intel Corporation Sky Lake-E RAS Configuration Registers (rev 04)
    16:05.4 PIC: Intel Corporation Device 2036 (rev 04)
    16:08.0 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04)
    17:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1080] (rev a1)
    17:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1)
    64:00.0 PCI bridge: Intel Corporation Sky Lake-E PCI Express Root Port A (rev 04)
    64:05.0 System peripheral: Intel Corporation Device 2034 (rev 04)
    64:05.2 System peripheral: Intel Corporation Sky Lake-E RAS Configuration Registers (rev 04)
    64:05.4 PIC: Intel Corporation Device 2036 (rev 04)
    64:08.0 System peripheral: Intel Corporation Device 2066 (rev 04)
    65:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1080] (rev a1)
    65:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1)
    b2:05.0 System peripheral: Intel Corporation Device 2034 (rev 04)
    b2:05.2 System peripheral: Intel Corporation Sky Lake-E RAS Configuration Registers (rev 04)
    b2:05.4 PIC: Intel Corporation Device 2036 (rev 04)
    b2:12.0 Performance counters: Intel Corporation Sky Lake-E M3KTI Registers (rev 04)
    b2:12.1 Performance counters: Intel Corporation Sky Lake-E M3KTI Registers (rev 04)
    b2:12.2 System peripheral: Intel Corporation Sky Lake-E M3KTI Registers (rev 04)
    b2:15.0 System peripheral: Intel Corporation Sky Lake-E M2PCI Registers (rev 04)
    b2:17.0 System peripheral: Intel Corporation Sky Lake-E M2PCI Registers (rev 04)
    I think this is what I get according my disks:

    [ 4.507164] Linux agpgart interface v0.103
    [ 4.508742] ahci 0000:00:17.0: version 3.0
    [ 4.508820] ahci 0000:00:17.0: Found 2 remapped NVMe devices.
    [ 4.508821] ahci 0000:00:17.0: Switch your BIOS from RAID to AHCI mode to use them.
    [ 4.508825] ahci 0000:00:17.0: controller can't do SNTF, turning off CAP_SNTF
    [ 4.509035] ahci 0000:00:17.0: AHCI 0001.0301 32 slots 4 ports 6 Gbps 0xf impl RAID mode
    [ 4.509036] ahci 0000:00:17.0: flags: 64bit ncq led clo only pio slum part deso sadm sds apst
    [ 4.509040] ahci 0000:00:17.0: both AHCI_HFLAG_MULTI_MSI flag set and custom irq handler implemented
    [ 4.509459] scsi host0: ahci
    [ 4.509596] scsi host1: ahci
    [ 4.509727] scsi host2: ahci
    [ 4.509853] scsi host3: ahci
    [ 4.509870] ata1: SATA max UDMA/133 abar m524288@0x92e00000 port 0x92e00100 irq 31
    [ 4.509874] ata2: SATA max UDMA/133 abar m524288@0x92e00000 port 0x92e00180 irq 32
    [ 4.509875] ata3: SATA max UDMA/133 abar m524288@0x92e00000 port 0x92e00200 irq 33
    [ 4.509876] ata4: SATA max UDMA/133 abar m524288@0x92e00000 port 0x92e00280 irq 34
    [ 4.509985] libphy: Fixed MDIO Bus: probed
    and some red parts marked:

    [ 56.819582] EDAC skx: ECC is disabled on imc 0
    [ 56.878999] nouveau 0000:17:00.0: priv: HUB0: 00d054 00000007 (1b408216)
    [ 56.880809] nouveau 0000:17:00.0: DRM: Pointer to flat panel table invalid
    [ 57.203214] nouveau 0000:17:00.0: DRM: failed to create kernel channel, -22
    [ 57.442017] nouveau 0000:65:00.0: priv: HUB0: 00d054 00000007 (18408216)
    [ 57.443751] nouveau 0000:65:00.0: DRM: Pointer to flat panel table invalid
    [ 57.746253] nouveau 0000:65:00.0: DRM: failed to create kernel channel, -22
    I'm suing MSI X299 Chipset SLI Plus motherboard with Intel 7920X CPU.

  13. #13
    Join Date
    Aug 2007
    Posts
    159

    Re: Fedora 26, FakeRAID, unrecognised m.2 SSD

    I think I have found the problem. All of your SATA controlllers are part of a RAID bus controller instead of being normal SATA controllers as I have. Since this controller is in RAID mode Linux can't see any SATA drives.

    Code:
    00:17.0 RAID bus controller: Intel Corporation SATA Controller [RAID mode]
    
    [ 4.508742] ahci 0000:00:17.0: version 3.0
    [ 4.508820] ahci 0000:00:17.0: Found 2 remapped NVMe devices.
    [ 4.508821] ahci 0000:00:17.0: Switch your BIOS from RAID to AHCI mode to use them.
    [ 4.508825] ahci 0000:00:17.0: controller can't do SNTF, turning off CAP_SNTF
    [ 4.509035] ahci 0000:00:17.0: AHCI 0001.0301 32 slots 4 ports 6 Gbps 0xf impl RAID mode
    As I have underlined the 4 port 6 Gbps controller is in RAID mode. Linux can't see attached drives in this mode.

    In contrast my 2011 Z68 Gigabyte board has two separate normal SATA controllers.

    Code:
    $ lspci | grep -i sata
    00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05)
    08:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller (rev 11)
    You need to go into your firmware and switch this controller to AHCI mode so you can see the new SSD and possibly the two NVMe drives as well.

    I found this archived post from another forum that describes the problems you have been having.

    https://www.reddit.com/r/linuxquesti...r_linuxubuntu/

    I have a newer xps 15, with a similar ssd. My experience: if it's in RAID, gparted/Linux cannot see your hard drive at all. It works fine in ahci.
    Last edited by amiga; 24th October 2017 at 06:56 PM. Reason: added link to other post

  14. #14
    Join Date
    Sep 2017
    Location
    Other Planet
    Posts
    9

    Re: Fedora 26, FakeRAID, unrecognised m.2 SSD

    But my main concern is if I switch raid off to AHCI mode, I will loose all information in raid0. As I'm using this partition with windows I think it's to risky to try.

    Other thing, to setup raid i have to do it from BIOS so as I understand it's not software level raid but goes thru some of the intel chipset. Durring windows installation I had to load driver from usb stick to make volume visible to installer. For what I know for now, this dmraid or mdraid or mdadm should be able to make my disk visable to Fedora installer, but just I don't know how, as in all the guides says to enable mdraid=true and volume itself should be in /dev/md but somehow this doesnt work for me ;/

  15. #15
    Join Date
    Aug 2007
    Posts
    159

    Re: Fedora 26, FakeRAID, unrecognised m.2 SSD

    I found an older but longer paper that describes how to share an RST array between Windows and Linux with mdraid. It however doesn't mention anything about RAID and AHCI modes in the BIOS.

    https://www.intel.com/content/dam/ww...inux-paper.pdf

    On page 8 it mentions this:
    Various Linux installers (Anaconda* in RedHat*, YaST* in SLES) have a specialized
    module that assembles RAIDs volumes using mdadm.
    But my main concern is if I switch raid off to AHCI mode, I will lose all information in raid0. As I'm using this partition with windows I think it's to risky to try.
    If you don't write anything at all to the RAID array you won't lose any data. You could do a test where you switch to AHCI temporarily, boot the live USB, and see if the drives are visible. A live distribution won't touch any drives unless you tell it to. You could then switch back to RAID and boot into Windows.

    If Linux sees the drives in AHCI mode you could then decide how to proceed.

Page 1 of 2 1 2 LastLast

Similar Threads

  1. How I got Fedora 15 & Win 7 to dual boot on fakeRaid 0
    By d3m3tr1x in forum Guides & Solutions (Not For Questions)
    Replies: 0
    Last Post: 25th May 2011, 09:10 AM
  2. Fakeraid Raid 0 Fedora 14 Installation, dualboot with Win7
    By groszek in forum Installation, Upgrades and Live Media
    Replies: 2
    Last Post: 17th April 2011, 11:18 AM
  3. How to install Fedora 14 64bit on Fakeraid withh W7 ?
    By alblinux in forum Installation, Upgrades and Live Media
    Replies: 0
    Last Post: 3rd December 2010, 04:07 PM
  4. Fedora 10 - nvidia fakeraid
    By alini76 in forum Hardware & Laptops
    Replies: 2
    Last Post: 4th June 2009, 02:18 PM
  5. Unrecognised Realtek NIC
    By dodgydodgy in forum Servers & Networking
    Replies: 2
    Last Post: 19th January 2007, 09:20 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •