Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Full Slackware Build - Having driver troubles

Featured Replies

Hi Guys,

 

Can't get my server to boot with my modified kernel (14.1 x64).

 

My dmesg output is attached.

 

I keep getting the file system can't be found message 'cannot open root device'.

 

What am I missing driver wise!? I've ticked most of the boxes in make menuconfig.

 

Thanks!

  • Author

Hi Guys,

 

I've attached my config file and the dmesg, lsmod and lspci if someone could work out what I'm doing wrong!

 

Many Thanks!!

config.txt

dmesg.txt

lsmod.txt

lspci.txt

Hi Guys,

 

I've attached my config file and the dmesg, lsmod and lspci if someone could work out what I'm doing wrong!

 

Many Thanks!!

 

Your kernel does not include the driver for your root filesystem, or a driver for your SATA bus, or other stuff that is only built as modules, your kernel will panic if it boots and can not access the necessary disks, partitions and/or files.

 

You have two options.

 

Option A

 

Run the following command:

 

/usr/share/mkinitrd/mkinitrd_command_generator.sh

 

It will suggest what command you need to run to make a initrd or “Initial Ram Disk” (basically what bzroot is in unRAID).

 

Once you have done that you need to update your bootloader.

 

if you are running grub...

 

grub-mkconfig -o /boot/grub/grub.cfg

 

If you are running lilo add / update an entry:

nano /etc/lilo.conf

 

It should look something like this (customize for your system)

 

image = /boot/vmlinuz-custom-2.6.37.6
  root = /dev/sda1
  initrd = /boot/initrd-custom-2.6.37.6.gz
  label = newkernel
  read-only # Non-UMSDOS filesystems should be mounted read-only for checking

 

Update Lilo

 

lilo

 

Option B

 

Attach a copy of the following command:

 

lspci -k

 

Then I can tell you which drivers you need to compile into the kernel to boot up.

 

  • Author

Here is my lspci -k output:

 

root@Slack64:~# lspci -k
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09)
Subsystem: ASUSTeK Computer Inc. Device 844d
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:06.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
Subsystem: ASUSTeK Computer Inc. P8P67 Deluxe Motherboard
Kernel driver in use: mei_me
Kernel modules: mei_me
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
Subsystem: ASUSTeK Computer Inc. P8P67 Deluxe Motherboard
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.6 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 7 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.7 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 8 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
Subsystem: ASUSTeK Computer Inc. P8P67 Deluxe Motherboard
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5)
00:1f.0 ISA bridge: Intel Corporation C206 Chipset Family LPC Controller (rev 05)
Subsystem: ASUSTeK Computer Inc. Device 844d
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05)
Subsystem: ASUSTeK Computer Inc. P8P67 Deluxe Motherboard
Kernel driver in use: ahci
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
Subsystem: ASUSTeK Computer Inc. P8P67 Deluxe Motherboard
Kernel modules: i2c_i801
01:00.0 VGA compatible controller: AMD/ATI [Advanced Micro Devices, Inc.] Tahiti PRO [Radeon HD 7950]
Subsystem: Hightech Information System Ltd. Device 201c
Kernel driver in use: fglrx_pci
Kernel modules: radeon, fglrx
01:00.1 Audio device: AMD/ATI [Advanced Micro Devices, Inc.] Tahiti XT HDMI Audio [Radeon HD 7970 Series]
Subsystem: Hightech Information System Ltd. Device aaa0
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
04:00.0 RAID bus controller: Silicon Image, Inc. SiI 3132 Serial ATA Raid II Controller (rev 01)
Subsystem: Silicon Image, Inc. Device 7132
Kernel driver in use: sata_sil24
05:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
Subsystem: ASUSTeK Computer Inc. Device 8369
Kernel driver in use: e1000e
Kernel modules: e1000e
06:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
Subsystem: ASUSTeK Computer Inc. Device 8369
Kernel driver in use: e1000e
Kernel modules: e1000e
07:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
Subsystem: ASUSTeK Computer Inc. Device 8488
Kernel driver in use: xhci_hcd
Kernel modules: xhci_hcd
root@Slack64:~# 

 

Thanks!!

Here is my lspci -k output:

 

00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05)
Subsystem: ASUSTeK Computer Inc. P8P67 Deluxe Motherboard
Kernel driver in use: ahci
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
Subsystem: ASUSTeK Computer Inc. P8P67 Deluxe Motherboard
Kernel modules: i2c_i801
04:00.0 RAID bus controller: Silicon Image, Inc. SiI 3132 Serial ATA Raid II Controller (rev 01)
Subsystem: Silicon Image, Inc. Device 7132
Kernel driver in use: sata_sil24
05:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
Subsystem: ASUSTeK Computer Inc. Device 8369
Kernel driver in use: e1000e
Kernel modules: e1000e
06:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
Subsystem: ASUSTeK Computer Inc. Device 8369
Kernel driver in use: e1000e
Kernel modules: e1000e

 

I would add all the above drivers into your kernel. Slackware needs to have at least the disk drivers and file system drivers to access the disk drive where it can load the rest as modules.

 

When you go into make menuconfig:

 

/

 

You can now search for what you want and see what other dependencies are needed to enable the driver.

 

In your case, I would search for the following and enable them all: ahci, i2c_i801, sata_sil24, e1000e.

 

You want to make sure they are a * and not a M.

 

Also make sure the file system you used to install Slackware is enabled as well. In my case both my boot and root partitions where EXT4.

 

When you enabled the drivers and the filesystem:

 

make -j4 <--- Replace 4 with the number of cores you have. This will speed up the compile.

make -j4 modules  <--- Replace 4 with the number of cores you have. This will speed up the compile.

make modules_install

 

 

  • Author

Thanks. Ill try that and report back.

 

That should be added to the sticky as that is very nifty!

  • Author

OK didn't work.

 

I just get stuck at "Press enter to activate this console" which apparently is due to the switch "BINFMT_SCRIPT" not being a *. So I've now rebuild the kernel with that enabled.

 

But... I installed Grub last night and it won't link to the vmlinuz file.

 

This is my grub file:

 

root@Slack64:/boot# cat grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
set default="0"

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=dejavusansmono
else
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2  3f0d1d96-35bd-4511-8598-a3fcd1ccf460
else
  search --no-floppy --fs-uuid --set=root 3f0d1d96-35bd-4511-8598-a3fcd1ccf460
fi
    font="/usr/share/grub/dejavusansmono.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_output gfxterm
set timeout=15
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Slackware-14.1 GNU/Linux' --class slackware-14.1 --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-3f0d1d96-35bd-4511-8598-a3fcd1ccf460' {
load_video
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2  3f0d1d96-35bd-4511-8598-a3fcd1ccf460
else
  search --no-floppy --fs-uuid --set=root 3f0d1d96-35bd-4511-8598-a3fcd1ccf460
fi
echo	'Loading Linux 3.10.17 ...'
linux	/boot/vmlinuz-huge-3.10.17 root=UUID=3f0d1d96-35bd-4511-8598-a3fcd1ccf460 ro  
echo	'Loading initial ramdisk ...'
initrd	/boot/initrd.gz
}
submenu 'Advanced options for Slackware-14.1 GNU/Linux' $menuentry_id_option 'gnulinux-advanced-3f0d1d96-35bd-4511-8598-a3fcd1ccf460' {
menuentry 'Slackware-14.1 GNU/Linux, with Linux 3.10.17' --class slackware-14.1 --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.10.17-advanced-3f0d1d96-35bd-4511-8598-a3fcd1ccf460' {
	load_video
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2  3f0d1d96-35bd-4511-8598-a3fcd1ccf460
	else
	  search --no-floppy --fs-uuid --set=root 3f0d1d96-35bd-4511-8598-a3fcd1ccf460
	fi
	echo	'Loading Linux 3.10.17 ...'
	linux	/boot/vmlinuz-huge-3.10.17 root=UUID=3f0d1d96-35bd-4511-8598-a3fcd1ccf460 ro  
	echo	'Loading initial ramdisk ...'
	initrd	/boot/initrd.gz
}
menuentry 'Slackware-14.1 GNU/Linux, with Linux 3.10.17 (recovery mode)' --class slackware-14.1 --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.10.17-recovery-3f0d1d96-35bd-4511-8598-a3fcd1ccf460' {
	load_video
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2  3f0d1d96-35bd-4511-8598-a3fcd1ccf460
	else
	  search --no-floppy --fs-uuid --set=root 3f0d1d96-35bd-4511-8598-a3fcd1ccf460
	fi
	echo	'Loading Linux 3.10.17 ...'
	linux	/boot/vmlinuz-huge-3.10.17 root=UUID=3f0d1d96-35bd-4511-8598-a3fcd1ccf460 ro single 
	echo	'Loading initial ramdisk ...'
	initrd	/boot/initrd.gz
}
menuentry 'Slackware-14.1 GNU/Linux, with Linux 3.10.17' --class slackware-14.1 --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.10.17-advanced-3f0d1d96-35bd-4511-8598-a3fcd1ccf460' {
	load_video
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2  3f0d1d96-35bd-4511-8598-a3fcd1ccf460
	else
	  search --no-floppy --fs-uuid --set=root 3f0d1d96-35bd-4511-8598-a3fcd1ccf460
	fi
	echo	'Loading Linux 3.10.17 ...'
	linux	/boot/vmlinuz-generic-3.10.17 root=UUID=3f0d1d96-35bd-4511-8598-a3fcd1ccf460 ro  
	echo	'Loading initial ramdisk ...'
	initrd	/boot/initrd.gz
}
menuentry 'Slackware-14.1 GNU/Linux, with Linux 3.10.17 (recovery mode)' --class slackware-14.1 --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.10.17-recovery-3f0d1d96-35bd-4511-8598-a3fcd1ccf460' {
	load_video
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2  3f0d1d96-35bd-4511-8598-a3fcd1ccf460
	else
	  search --no-floppy --fs-uuid --set=root 3f0d1d96-35bd-4511-8598-a3fcd1ccf460
	fi
	echo	'Loading Linux 3.10.17 ...'
	linux	/boot/vmlinuz-generic-3.10.17 root=UUID=3f0d1d96-35bd-4511-8598-a3fcd1ccf460 ro single 
	echo	'Loading initial ramdisk ...'
	initrd	/boot/initrd.gz
}
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

 

 

and this is what is in my boot folder:

 

root@Slack64:/boot# ls -al
total 30988
drwxr-xr-x  4 root root    4096 Dec 11 17:46 ./
drwxr-xr-x 23 root root    4096 Dec 11 17:08 ../
lrwxrwxrwx  1 root root      37 Dec  7 15:59 README.initrd -> /usr/doc/mkinitrd-1.4.8/README.initrd
-rw-r--r--  1 root root 1876690 Dec 11 17:46 System.map
-rw-r--r--  1 root root 2213519 Oct 23 22:29 System.map-generic-3.10.17
-rw-r--r--  1 root root 3391172 Oct 23 22:34 System.map-huge-3.10.17
-rw-r--r--  1 root root 1876500 Dec 11 17:36 System.old
-rw-r--r--  1 root root     512 Dec  7 16:06 boot.0800
-rw-r--r--  1 root root     512 Dec  8 16:29 boot.0820
-rw-r--r--  1 root root     168 Dec  7 16:06 boot_message.txt
lrwxrwxrwx  1 root root      19 Dec  7 16:05 config -> config-huge-3.10.17
-rw-r--r--  1 root root  137802 Oct 23 22:29 config-generic-3.10.17
-rw-r--r--  1 root root  137802 Oct 23 22:34 config-huge-3.10.17
-rwxr-xr-x  1 root root  217646 Jan 10  2011 elilo-ia32.efi*
-rwxr-xr-x  1 root root  250510 Jan 10  2011 elilo-x86_64.efi*
drwxr-xr-x  5 root root    4096 Dec 11 17:36 grub/
drwxr-xr-x 14 root root    4096 Dec 11 17:35 initrd-tree/
-rw-r--r--  1 root root 5587626 Dec 11 17:35 initrd.gz
-rw-------  1 root root  165376 Dec 11 17:08 map
-rw-r--r--  1 root root 2959072 Dec 11 17:46 vmlinuz
-rw-r--r--  1 root root 3455584 Oct 23 22:29 vmlinuz-generic-3.10.17
-rw-r--r--  1 root root 6441264 Oct 23 22:34 vmlinuz-huge-3.10.17
-rw-r--r--  1 root root 2958800 Dec 11 17:36 vmlinuz.old

 

Why isn't grub picking up the third kernel!?

 

OK, modified the gun file even though it says don't to point at my kernel. It works and I can get x to start.

 

But for some reason I can't get the mouse to work, so I've restarted the .config building from scratch to see what is what. I might need to rebuild the X config...

I can get this working for you. Just need to get some additional information.

 

Are you compiling unRAID into the 3.10.17 kernel?

 

Is the vmlinuz you are showing there the one you want boot?

 

If so, where did you get it?

 

Show me the following:

 

ls /boot - la

 

and...

 

ls /usr/src

 

and...

 

cat /etc/default/grub

 

ATTACH a copy of your .config file from where you compiled your new kernel.

 

/usr/src/XXXXXX/.config

 

  • Author

Hi,

 

I've partially cracked it - I've got it to boot and get to to KDE desktop!

 

However, the ATI drivers refuse to start and I think it is down to the fact lsmod shows only three items not 20+

config.txt

Hi,

 

I've partially cracked it - I've got it to boot and get to to KDE desktop!

 

However now I can't get the ATi Drivers to start, so I'm now trying a 32 bit kernel and building it to see if I can get that to push it into life.

 

lsmod when booted into this new kernel comes up with two items, not the 20+ when I boot normal  :o

 

Any thoughts on this secondary problem? I'll attach the docs when I reboot this 32 bit kernel.

 

I see you added most things into the kernel aside from those modules.

 

If you did a 64-Bit install and switching it over to 32-Bit... You are in for quite an adventure.

 

Which drivers were you planning on using? The proprietary AMD drivers or the open source ones (Radeon)?

 

The reason I ask, the open source drivers are better. If you try to install AMD Drivers it requires you running an older version of xorg-server (perhaps not on Slackware but most other Distros you do) unless you are installing the beta ones (which if you install AMD Drivers I recommend).

 

If you kernel doesn't already, go enable the Radeon drivers or if they are a module. Add them to your Linux line in grub to load.

 

radeon.dpm=1 radeon.audio=1 clocksource=hpet hpet=enable

 

The hpet stuff is for 24fps playback if you are doing XBMC with the Radeon drivers.

 

If you want the low down on on all things AMD (not Radeon drivers)... Read the last 10 pages or so in the following thread. You will be an AMD pro by the end of it.

 

https://bbs.archlinux.org/viewtopic.php?id=57084&p=239

  • Author

I'm using the Offical ATI drivers as cgminer requires it for mining (the whole point of this exercise unfortunately).

 

Thoughts on this? A fraction of the modules are being loaded and this is the reason why the ATI drivers will not load (module dependencies).

 

Normal Kernel:

root@Slack64:~# cat lsmod-Slack64.txt 
Module                  Size  Used by
ipv6                  292446  20 
joydev                  9751  0 
lp                      9851  0 
ppdev                   5862  0 
parport_pc             19332  0 
parport                30389  3 lp,ppdev,parport_pc
fuse                   73848  3 
eeepc_wmi               4608  0 
asus_wmi               16202  1 eeepc_wmi
sparse_keymap           3074  1 asus_wmi
rfkill                 15522  2 asus_wmi
fglrx                7362082  138 
intel_powerclamp        8391  0 
coretemp                5870  0 
evdev                  10032  6 
kvm_intel             126236  0 
kvm                   363491  1 kvm_intel
crc32_pclmul            2883  0 
crc32c_intel           14113  0 
ghash_clmulni_intel     4333  0 
microcode              13140  0 
mperf                   1163  0 
snd_hda_codec_hdmi     29622  1 
video                  11451  1 asus_wmi
snd_hda_intel          34861  2 
psmouse                81058  0 
snd_hda_codec         143196  2 snd_hda_codec_hdmi,snd_hda_intel
i2c_i801               13860  0 
snd_hwdep               6388  1 snd_hda_codec
e1000e                194662  0 
serio_raw               4585  0 
i2c_core               20936  1 i2c_i801
snd_pcm                76009  3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_page_alloc          7098  2 snd_pcm,snd_hda_intel
snd_timer              18614  1 snd_pcm
amd_iommu_v2            7116  1 fglrx
snd                    58630  10 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel
agpgart                27267  1 fglrx
ptp                     8148  1 e1000e
soundcore               5354  1 snd
lpc_ich                12841  0 
pps_core                6777  1 ptp
thermal                 8644  0 
processor              27543  0 
fan                     2617  0 
ehci_pci                3688  0 
thermal_sys            22993  5 fan,video,intel_powerclamp,thermal,processor
mei_me                  7728  0 
ehci_hcd               39275  1 ehci_pci
wmi                     8243  1 asus_wmi
mei                    42963  1 mei_me
freq_table              2628  1 thermal_sys
hwmon                   1337  3 coretemp,thermal_sys,asus_wmi
button                  4696  1 fglrx
loop                   18479  0 
xhci_hcd               88528  0 
hid_generic             1145  0 
usbhid                 37080  0 
hid                    87523  2 hid_generic,usbhid

 

 

UnRAID Kernel:

root@Slack64:~# cat lsmodunraid.txt 
Module                  Size  Used by
ipv6                  227280  20 
joydev                  8239  0 
mperf                   1027  0 

 

Attached is the .config file.

 

Any ideas?

 

 

 

 

In answer to your earlier questions: Yes 3.10.17 kernel.

 

root@Slack64:/usr/src/linux# ls /boot -la
total 33032
drwxr-xr-x  4 root root    4096 Dec 11 20:41 ./
drwxr-xr-x 23 root root    4096 Dec 11 19:08 ../
lrwxrwxrwx  1 root root      37 Dec  7 15:59 README.initrd -> /usr/doc/mkinitrd-1.4.8/README.initrd
-rw-r--r--  1 root root 2215850 Dec 11 20:41 System.map
-rw-r--r--  1 root root 2213519 Oct 23 22:29 System.map-generic-3.10.17
-rw-r--r--  1 root root 3391172 Oct 23 22:34 System.map-huge-3.10.17
-rw-r--r--  1 root root 2310487 Dec 11 20:35 System.old
-rw-r--r--  1 root root     512 Dec  7 16:06 boot.0800
-rw-r--r--  1 root root     512 Dec  8 16:29 boot.0820
-rw-r--r--  1 root root     168 Dec  7 16:06 boot_message.txt
lrwxrwxrwx  1 root root      19 Dec  7 16:05 config -> config-huge-3.10.17
-rw-r--r--  1 root root  137802 Oct 23 22:29 config-generic-3.10.17
-rw-r--r--  1 root root  137802 Oct 23 22:34 config-huge-3.10.17
-rwxr-xr-x  1 root root  217646 Jan 10  2011 elilo-ia32.efi*
-rwxr-xr-x  1 root root  250510 Jan 10  2011 elilo-x86_64.efi*
drwxr-xr-x  5 root root    4096 Dec 11 19:00 grub/
drwxr-xr-x 14 root root    4096 Dec 11 17:35 initrd-tree/
-rw-r--r--  1 root root 5587626 Dec 11 17:35 initrd.gz
-rw-------  1 root root  165376 Dec 11 17:08 map
-rw-r--r--  1 root root 3493968 Dec 11 20:41 vmlinuz
-rw-r--r--  1 root root 3455584 Oct 23 22:29 vmlinuz-generic-3.10.17
-rw-r--r--  1 root root 6441264 Oct 23 22:34 vmlinuz-huge-3.10.17
-rw-r--r--  1 root root 3746080 Dec 11 20:35 vmlinuz.old

 

root@Slack64:/usr/src/linux# ls /usr/src
ati/  linux@  linux-3.10.17-unraid/  linux-3.10.17.tar.bz2

 

root@Slack64:/usr/src/linux# cat /etc/default/grub
# If you change this file, run grub-mkconfig -o /boot/grub/grub.cfg
# afterwards to update /boot/grub/grub.cfg.

GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=false
GRUB_TIMEOUT=15
GRUB_DISTRIBUTOR=$( sed 's/Slackware /Slackware-/' /etc/slackware-version )
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX=""

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480
#GRUB_GFXMODE=1024x768x32

# Font used on the graphical terminal:
#GRUB_FONT=/usr/share/grub/dejavusansmono.pf2

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entrys
#GRUB_DISABLE_LINUX_RECOVERY="true"

 

And the .config file is attached.

 

I'll send you over a few crypto coins if you crack this!!! (If you collect such things!)

config.txt

You followed this guide right?

 

http://docs.slackware.com/howtos:hardware:proprietary_graphics_drivers

 

Show me where it is asking for modules. Is it during the AMD install or when you are trying to load the desktop?

 

Did you blacklist the Radeon Drivers?

 

Also, do you have a /etc/X11/xorg.conf? If so, post that.

 

  • Author

You followed this guide right?

 

http://docs.slackware.com/howtos:hardware:proprietary_graphics_drivers

 

Show me where it is asking for modules. Is it during the AMD install or when you are trying to load the desktop?

 

Did you blacklist the Radeon Drivers?

 

Also, do you have a /etc/X11/xorg.conf? If so, post that.

 

Yes I followed that guide - installing the drivers again results in errors, booting up using the normal kernel and it is fine.

 

If you look at the full lsmod list, you can see that fglrx uses a few other modules. Eg amd_iommu_v2.

 

I might crack on tomorrow and see if UnRAID works and then try and solve this issue later.

 

  • Author

I've cracked it, I've now go UnRAID running.

 

However, one final problem.

 

I get this error when starting emhttp:

 

/lib/udev/usb_id: No such file or directory

 

And also it doesn't pick up my pro key which is in /boot/config

 

Ideas?

Starting with udev version 174, usb_id (and others) are builtin to udev. You either have to fix the udev rules or drop down to a prior version of udev.

 

udevadm --version

 

Will tell you what version of udev you are running.

  • Author

udevadm --version

182

 

 

So what is my best option? Dropping down a version doesn't seem the best way IMO?

If sticking with Slackware, I'd just drop down or don't copy of the udev rules from unRAID (I didn't test this).

 

You could download udev from git and checkout tag 173.

 

Compile it and install it over udev 182.

 

udev git

 

I'd use clonezilla to clone your PC first in case it doesn't work.

 

You know what you are doing, perhaps switch unRAID to a different Linux Distro and make your life easy. I'm put Slackware next to Gentoo and Linux From Scratch when you talk about difficulty.

 

ls /lib/udev

 

That is where you want to see usb_id show up.

  • Author

I'll try compiling a earlier version of udev.

 

As for knowing what I'm doing, I'm just trying things to see what sticks!!

 

How hard would it be to do it in another distro? One that is slightly better supported/common?

I'll try compiling a earlier version of udev.

 

I think that is what I ended up doing to get it working. I just download udev 173 and slammed it in there.

 

As for knowing what I'm doing, I'm just trying things to see what sticks!!

 

How hard would it be to do it in another distro? One that is slightly better supported/common?

 

It's not much different than what you have done so far. Compile a Linux Kernel with unRAID in it, copy over emhttp, install the various software that emhttp needs, start the various services like Samba, NFS, etc. in your Linux Distro. Bam! You have unRAID in something other than Slackware.

 

Slackware is for very experienced Linux Pros. Even I get stumped, frustrated run into trouble in Slackware and I have using Linux for a decade. Gentoo which is fundamentally more difficult than Slackware. However, I think it's 100 times easier because of the thriving Gentoo community, website, forums, wikis, etc. As you have probably found out by now, Good Luck finding a damn thing about doing X, Y and Z on Slackware on the internet. 

  • Author

Quite!

 

Christmas project then, compile unraid on Gentoo!

Quite!

 

Christmas project then, compile unraid on Gentoo!

 

I'm starting to worry about you. Do you need a hug?

 

Otherwise you must enjoy challenges / puzzles.

  • Author

Well quite. Learning process...

 

Been chatting with a friend and we might pick Fedora or Debian.

 

Had some troubles compiling 173 so I downloaded 165 and it works!

 

Pulled the disks overnight but ill plug it all in and do a parity check tonight. But it did detect all the disks A-ok.

 

Thanks for the help.

  • Author

OK,

 

Everything *seems* to work.

 

The only problem I've come across so far is that I'm limited to 80MB/sec. Even though previously I'd hit 120+.

 

Any thoughts?

 

I'm thinking drivers *shrug*

  • Author

Got it - Sil card can't handle full speed from two disks.

 

Upgrade that and I'm sorted!!

 

It's working!!!!!

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.