I added two bits of information to the wiki that I found important, most importantly was the bit about the Kernel build option for IA32 support, which is necessary to run 32-bit binaries under 64-bit OS. All things appear to be working great, except for the problem of "MBR: Unknown" which I'll have to deal with later since I didn't feel like doing it at 1:30am...

I'm attempting to install unRAID Server version 5.0-beta14 AiO on slackware 13.1. The original slackware install goes well and everything works but after compiling the kernel (3.1.1) according to the instructions in the wiki I have all sorts of issues.

 

• My network card no longer works
  
• My mouse and keyboard work at the terminal but once in KDE nether work.
  
• The boot sequence looks different (no penguins) and I get a display error (although things do proceed)
  
• Various other errors that don't appear on the clean install
  

 

Can anyone give me a some pointers on what is causing all this? Is it normal when trying to upgrade an older version of slackware to a newer kernel or am I compiling it incorrectly? Is there a way to merge the unraid changes into a working config file?

 

Thanks for the help.

How did you configure the kernel?

It sounds like you didn't do it properly but I'm not so sure. It could be system configuration.

 

1) What do you mean by your network card doesn't work?

Does slackware see the network card but you don't have internet?  Or does your network card not show up at all?

 

2) How did you configure your initial X server? (aka how did you generate the Xorg.conf file)

 

3) If I remember correctly, you get this error if you choose a video mode setting during the setup that was not compiled in to the kernel.

I configured the kernel with according to the directions here http://lime-technology.com/wiki/index.php?title=Installing_unRAID_5.0_on_a_full_Slackware_Distro and used xconfig to pick other items I thought I might need.

 

1) Is looks like the card is found but times out for some reason. I'll take a closer look at the error when I get home.

2)I didn't configure x server at all other than picking the default options on the initial install.

 

Having never compiled a kernel before I'm wondering if I pick the correct options will everything work as before or will I need to reconfigure things (like xorg.conf) to work on the new kernel?

I've made a bit of progress. Following the guide after unziping the kernel file and creating the symlink I skipped the "Copy the unRAID kernel config and MD source mods" section and compiled a working 3.1.1 kernel with:

 

cd /usr/src/linux

make clean

zcat /proc/config.gz > .config  (I think this creates a .config file from the running kernel)

make oldconfig  (I pressed enter to accept most of the defaults)

make xconfig (for changes)

make all

make install

 

At that point I had a working 3.1.1 kernel (there was a problem with my network card but everthing else was working). Reboot to new kernel.

 

 

cd /usr/src/linux

make clean

zcat /proc/config.gz > .config

 

Then I used the GUI diff program in slackware to copy most of the changes from the .config in /usr/src/linux to the config in /uraid/usr/src/linux/.config. For the most part if an item was not set in the unraid kernel I copied it over. If there were two different settings I left the unraid one.

Then I started again at "Copy the unRAID kernel config and MD source mods"

 

After reboot everything was still working. Followed the rest of the guide. After "Copy unRAID scripts and executables" and "Copy additional libraries" the boot hangs on starting gpm but I can still telnet in. The rest of the setup goes fine although I do get some PHP errors on the server monitor when accessing the unraid web gui.

 

Does this process look reasonable?

Any ideas about the gpm hang?

I don't have my shares working yet. When I try to access in windows explorer the server is there but when I try to open it says "the network address is invalid".

 

 

rc.local is what's causing the boot to hang. GPM took the fall and got uninstalled.  Any tips on how I would fix it? I tried commenting out everything but the go script but got the same result. I may be able to live with it. If I need to I can telnet in and startx to get KDE.