Falcon Posted July 26, 2011 Share Posted July 26, 2011 I have replaced my parity disk from 2TB to 3TB and I have used the Preclear_disk script version 1.12beta to clear the disk with -A as 64k alignment. I can't help with your issue, but it should read 4k alignment (or sector 64) 3TB disks use their own alignment and an entirely different partitioning style. They use a GPT partition. The GPT partiton puts into place a "protective" partition table in the MBR to make legacy utilities think the disk is entirely allocated. Many older utilities will just report the partition starting on sector 1. The GPT partition is 4k aligned, so do not worry... and the -A had absolutely no effect on the preclear because the drive was over 2.2TB in size, but it did no harm either. The "-A" option was ignored because of the size of the drive. It is normal for fdisk to see the protective MBR partition and show it as starting on sector 1. It just has no way to know of the actual GPT partition. Joe L. Thanks a lot Now I can relax. Quote Link to comment
savestheday Posted July 26, 2011 Share Posted July 26, 2011 Did I miss something on cache drive permissions? I'm not sure what's going on but my .Plex directory on my cache drive randomly gives a permission denied error. Originally I thought it was because I swapped out cache drives about a week ago...that's when it initially happened. But since then, I've had random issues with it happening again. An entire reinstall of Plex is the only way to fix it. What's weird is I don't have these problems with sab, couch potato, or sick beard. Those were installed by unmenu. Not sure if unmenu sets some permissions up differently. BTW, I'm launching Plex through ./start.sh while ssh'd in under root. If I chmod +x start.sh it'll start but everything else that it launches fails because of permissions. Also, the same exact permissions issue is happening with my install of twonky. What is also weird about my cache drive is it stores all of my say downloads. I downloaded a movie the other night and was unable to delete it via AFP. It's not an AFP issue as I was able to delete other movies. This movie was in my Movies share but had not yet been moved off of the cache drive. Unfortunately, it kept its permissions when the mover ran and I was unable to delete it. I've run the new permissions in the Utils folder. Right now I'm in permissions hell. Permissions in Linux (chmod, chown) have always been a dark art for me. Any help would be appreciated. Quote Link to comment
Nezil Posted July 27, 2011 Share Posted July 27, 2011 Savestheday... You always seem to ask questions that are close to home for me; I hope I'm able to help you. chmod and chown are not really that complicated; if you do an ls -l on a directory, you'll see all the files with their associated permissions. For reference, I've included the ls -l of my Plex directory: root@unRAID:/apps/Plex# ls -l total 32170 drwxr-xr-x 5 root root 136 2011-07-17 12:09 Library/ -rwxr-xr-x 1 neil 1000 2186244 2011-07-14 19:49 Plex\ Media\ Scanner* -rwxr-xr-x 1 neil 1000 3752708 2011-07-14 19:49 Plex\ Media\ Server* drwxr-xr-x 5 neil 1000 648 2011-07-14 19:37 Resources/ -rwxr-xr-x 1 neil 1000 124367 2011-07-14 19:37 libass.so.4* -rwxr-xr-x 1 neil 1000 73205 2011-07-14 19:37 libavahi-client.so.3* -rwxr-xr-x 1 neil 1000 55429 2011-07-14 19:37 libavahi-common.so.3* -rwxr-xr-x 1 neil 1000 6080560 2011-07-14 19:37 libavcodec.so.52* -rwxr-xr-x 1 neil 1000 1040592 2011-07-14 19:37 libavformat.so.52* -rwxr-xr-x 1 neil 1000 116112 2011-07-14 19:37 libavutil.so.50* -rwxr-xr-x 1 neil 1000 141573 2011-07-14 19:37 libboost_filesystem.so.1.46.1* -rwxr-xr-x 1 neil 1000 263374 2011-07-14 19:37 libboost_iostreams.so.1.46.1* -rwxr-xr-x 1 neil 1000 433534 2011-07-14 19:37 libboost_program_options.so.1.46.1* -rwxr-xr-x 1 neil 1000 1079412 2011-07-14 19:37 libboost_regex.so.1.46.1* -rwxr-xr-x 1 neil 1000 98211 2011-07-14 19:37 libboost_signals.so.1.46.1* -rwxr-xr-x 1 neil 1000 16293 2011-07-14 19:37 libboost_system.so.1.46.1* -rwxr-xr-x 1 neil 1000 121430 2011-07-14 19:37 libboost_thread.so.1.46.1* -rwxr-xr-x 1 neil 1000 2413759 2011-07-14 19:37 libcurl.so.4* -rwxr-xr-x 1 neil 1000 341159 2011-07-14 19:37 libdbus-1.so.3* -rwxr-xr-x 1 neil 1000 23415 2011-07-14 19:37 libepeg.so.0* -rwxr-xr-x 1 neil 1000 209907 2011-07-14 19:37 libexpat.so.1* -rwxr-xr-x 1 neil 1000 99643 2011-07-14 19:37 libexslt.so.0* -rwxr-xr-x 1 neil 1000 89664 2011-07-14 19:37 libfaac.so.0* -rwxr-xr-x 1 neil 1000 245739 2011-07-14 19:37 libfontconfig.so.1* -rwxr-xr-x 1 neil 1000 3655228 2011-07-14 19:37 libfreeimage.so.3* -rwxr-xr-x 1 neil 1000 637624 2011-07-14 19:37 libfreetype.so.6* -rwxr-xr-x 1 neil 1000 92741 2011-07-14 19:37 libfribidi.so.0* -rwxr-xr-x 1 neil 1000 973644 2011-07-14 19:37 libiconv.so.2* -rwxr-xr-x 1 neil 1000 297847 2011-07-14 19:37 libjpeg.so.8* -rwxr-xr-x 1 neil 1000 33936 2011-07-14 19:37 libminiupnpc.so.5* -rwxr-xr-x 1 neil 1000 327522 2011-07-14 19:37 libmp3lame.so.0* -rwxr-xr-x 1 neil 1000 9188 2011-07-14 19:37 libnatpmp.so.1* -rwxr-xr-x 1 neil 1000 4425772 2011-07-14 19:37 libpython2.7.so.1.0* -rwxr-xr-x 1 neil 1000 299141 2011-07-14 19:37 libsoci_core-gcc-3_0-3.0.0.so* -rwxr-xr-x 1 neil 1000 108624 2011-07-14 19:37 libsoci_sqlite3-gcc-3_0-3.0.0.so* -rwxr-xr-x 1 neil 1000 693759 2011-07-14 19:37 libsqlite3.so.0* -rwxr-xr-x 1 neil 1000 252632 2011-07-14 19:37 libswscale.so.0* -rwxr-xr-x 1 neil 1000 1645425 2011-07-14 19:37 libxml2.so.2* -rwxr-xr-x 1 neil 1000 278879 2011-07-14 19:37 libxslt.so.1* -rwxr-xr-x 1 neil 1000 101724 2011-07-14 19:37 libz.so.1* -rwxr-xr-x 1 neil 1000 287 2011-07-15 09:22 start.sh* In this case, you can see the format is made up of: [permissions codes] [owner's username] [group name or id] [file size] [date and time] [filename] To focus on permission codes, as the rest is pretty self explanatory, this are broken up into: [type of file (d for directory, l for link, - for file)] [user permissions] [group permissions] [others permissions] And example from above is: -rwxr-xr-x 1 neil 1000 2186244 2011-07-14 19:49 Plex\ Media\ Scanner* This indicates that the owner is neil, the group id is 1000, and that 'neil' has Read, Write and Execute permissions, group 1000 has Read and Execute permissions, and everyone else has Read and Execute permissions as well. It's important to remember that the 'root' user has Write permissions as well, even though he isn't the owner or in the group. To change ownership, you use the command chown [user]:[group (optional)] filename To change permissions, you use the chmod [settings] filename The settings for chmod can be in the form of numbers to represent the permissions, or for simplicity, can be using letters. I won't bother to explain the number method here, there are plenty of resources available for that on the internet; the letter approach is far simpler: u = user, g = group, o = others + = set permission, - = remove permission r = read, w = write, x = execute Using these combinations, you can change permissions to anything you want. For example: chmod +x,+r [filename] will make the file readable and executable to user, group and others. chmod o-w [filename] will make the file not writable to others. chmod u+x,g-x,o-x [filename] will make the file readable and executable to user, but not executable by group and others. I'll create a new post about the Plex issues. Quote Link to comment
Yorgo Posted July 27, 2011 Share Posted July 27, 2011 Has anyone with a Realtek NIC had success with 5.0-beta10? I seem to be having an issue with my Realtek NIC, 8111DL on an ASRock M3A785GXH/128M mobo, and beta10. With beta9, no issue playing back any backed-up BD and DVD content streamed to my TViX M6500a media players (2) however with beta10, many files (including 2 specific test files, 1 BD in BDMV folder, 1 DVD) stutter heavily. Interestingly, there are a number BD files that play back with no stuttering via beta10. I went from beta7 to beta10 (discovered the problem), went to beta9 (no problem), tried beta10 again (to absolutely determine it is the culprit and not some other issue in the system, determined it is), and now back to beta9 again with no stuttering problems. Let me know what other information you need. Thanks, Y Quote Link to comment
Nezil Posted July 27, 2011 Share Posted July 27, 2011 Savestheday, your Plex issues... The best way for me to help you is to explain what I've done to install Plex; something I should have done long ago actually. As I've stated before, I'm running an additional 2.5" HDD connected by USB and mounted inside my case to house all of my apps, rather than a cache drive (which I don't use at all), some things may differ because of this, but I don't think anything major. The first thing I did was to unpack the latest Plex tarball, and rename the folder. You've already done this. My understanding from other posts, is that for transcoding, the alsa-lib-1.0.23-i486-1.tgz package is required. I'm not sure if this will be the case in future, but for now this needs to be added to your install. The easiest way to achieve this is by putting it in the /boot/extra folder of your flash drive. Plex was originally written for the Mac operating system, and when it first runs, it creates a Library folder structure in the user's home folder. In unRAID, you'll probably be using the root user to run Plex, so the folder structure will be created in the /root directory. This directory is on the RAM disk, and will be lost on every boot, loosing your Plex library database and all settings; not good. To fix this problem, you'll need to make a Library Folder on your cache drive, and then create symlinks in the /root location to this location. You can do this by adding the following lines to your go script: ln -s /Library /mnt/cache/.Plex/Library ln -s /root/Library /mnt/cache/.Plex/Library Plex includes all the required dependancies, which does make things simple. You need to tell the unRAID OS where this folder is by appending a line to the ld.so.conf file and then reload the new configuration. As before, in your go script add: echo "/mnt/cache/.Plex" >> /etc/ld.so.conf ldconfig By default, Plex stores the 'HTTP Live Streaming' chunks in the /tmp folder, which can get pretty big. It doesn't matter that this folder will disappear on reboots, but it does matter that it will grow in size taking up RAM, which you don't want. Luckily Plex honours the TMPDIR environment variable, and that's the easiest way to move the location of these temporary files. There have been some other suggestions for this issue, such as bind mounts, but this can cause issues with starting and stopping the array, so a better solution is to add the TMPDIR variable to /etc/profile. To do that, you need to add this line to your go script: echo "export TMPDIR=/mnt/cache/tmp" >> /etc/profile Finally, to actually start Plex, you could telnet in and do it, but a better way is to have a script that automatically does this when you start the array, and automatically stops it when you stop the array. As part of the as yet unfinished add-ons system, unRAID calls a file located at /usr/local/sbin/emhttp_event before or after certain unRAID events, and you can hook onto this to start and stop applications. I should give credit to Joe L for pointing this out. I've butchered Joe's original proposed script until this add on system is finalised, the script I use is shown below, and located at /boot/custom/emhttp_event/event . To get this script to be called, you must add a line to your go script as follows: echo '/boot/custom/emhttp_event/event $1' >> /usr/local/sbin/emhttp_event # A script to start up and shutdown services running when the array starts and stops case $1 in svcs_started) if ! ps -ef | grep .Plex/Plex\ Media\ Server | grep -v grep; then /mnt/cache/.Plex/start.sh >> /Library/Logs/.Plex\ Media\ Server.log 2>&1 & logger -t Plex\ Media\ Server Started fi;; svcs_restarted) if ! ps -ef | grep .Plex/Plex\ Media\ Server | grep -v grep; then /mnt/cache/.Plex/start.sh >> /Library/Logs/.Plex\ Media\ Server.log 2>&1 & logger -t Plex\ Media\ Server Started fi;; stopping_svcs) if ps -ef | grep .Plex/Plex\ Media\ Server | grep -v grep; then kill `ps -ef | grep Plex | grep -v grep | awk '{print $2}'` logger -t Plex\ Media\ Server Stopped fi;; *) logger -t Event\ Script Incorrect\ Argument;; esac Notes: - I actually have more things in my script because I'm also running Squeezebox Server, though these are not shown here. - I've made some changes to the script so that it will work for your cache drive, rather than an additional drive like I have. - In later versions of Plex (not yet released ones) the 'stopping_svcs' section for Plex can be changed to: kill -s INT `ps -ef | grep .Plex/Plex\ Media\ Server | grep -v grep | awk '{print $2}'` because the Media Server will automatically close down all associated python scripts when it's issued the INT signal. The currently released version doesn't do this yet. - Permissions are not important if you've followed these instructions, as the Media Server is run as root, and can access all the required files anyway. I hope this helps! Quote Link to comment
Wimpie Posted July 27, 2011 Share Posted July 27, 2011 I don't know if this is beta10 related but... I build a new unraid box (same hardware as Johnm's Goliath build, just another CPU). Just one 3Tb drive is attached, and not yet added to the array (it's a completely new build). The boot syslog is ok, just some references to a non existent super.dat file. A 3Tb drive is precleared with the 3Tb beta version of preclear on another PC. After boot I log in from another PC, so I can add the precleared as disk 1 (no other disk added, array is not protected with a parity drive). I have a syslog tail, the drive does not get added to the array. Some strange things in the tail syslog: - still some problems with the super.dat file. - 05:24:35 Norco_Tower kernel: unraid: allocating 13240K for 1280 stripes (2 disks) -> 2 drives? only one (+ flash offcourse) - hardware errors (timeout's). Do I have hardware errors, or is this a bug? I don't think it's hardware, I tried this on a MB port, and on a SASLP-MV8 port. syslog_boot.txt syslog_tail.txt Quote Link to comment
EddieA Posted July 27, 2011 Share Posted July 27, 2011 Nezil. Maybe you should also add this to the existing Plex thread, as it's not really a beta issue, plus it keeps all the relevant information together. But I'm not sure how this part works: By default, Plex stores the 'HTTP Live Streaming' chunks in the /tmp folder, which can get pretty big. It doesn't matter that this folder will disappear on reboots, but it does matter that it will grow in size taking up RAM, which you don't want. Luckily Plex honours the TMPDIR environment variable, and that's the easiest way to move the location of these temporary files. There have been some other suggestions for this issue, such as bind mounts, but this can cause issues with starting and stopping the array, so a better solution is to add the TMPDIR variable to /etc/profile. To do that, you need to add this line to your go script: echo "export TMPDIR=/mnt/cache/tmp" >> /etc/profile All you have done is add the TMPDIR to /etc/profile, which means that any new logins will inherit that setting. The current root session will not have it, and so starting Plex will continue to use /tmp. Cheers. Quote Link to comment
Nezil Posted July 27, 2011 Share Posted July 27, 2011 Hmm... that's a good point Eddie. In my case, I've modified the /etc/profile setting in the bzroot image (along with many other modifications) rather than add it to the go script. The profile script in my case then applies to all sessions; I'd not thought of that problem if using the go script. In the go script case, you'd be better to add two lines then: echo "export TMPDIR=/mnt/cache/tmp" >> /etc/profile export TMPDIR=/mnt/cache/tmp as that will cover the current session and future ones. Is that right? Quote Link to comment
PeterB Posted July 27, 2011 Share Posted July 27, 2011 It seems to me that mover isn't being invoked automatically - every time unRAID is booted. I have to go into settings, and 'Apply' the mover schedule before it will be run. Is anyone else experiencing this? Quote Link to comment
meoge Posted July 27, 2011 Share Posted July 27, 2011 I did notice that mover didn't start automatically after I upgraded to beta 10, but I've not put anything else on there since I hit 'Apply'. I don't reboot my server enough to know if this has to be done after a reboot. I do remember having this happen on previous beta's and it seemed to be fine once I hit 'Apply' once. Quote Link to comment
Soul Posted July 27, 2011 Share Posted July 27, 2011 Can't wait to try this out, thanks Tom! BTW if I turn off SMB, should I still get TOWER-SMB in my sidebar? I'd have thought it would go away if I'm not running SMB..... Quote Link to comment
Soul Posted July 27, 2011 Share Posted July 27, 2011 Hmmm tried the upgrade and my PCI NIC isn't detected. Tried another NIC and still no joy. Back to Beta9 with the new NIC and still nothing. I assume it's therefore not unRAIDs issue so going to try an ubuntu live usb stick to see what happens... Quote Link to comment
Interstellar Posted July 27, 2011 Share Posted July 27, 2011 I think netatalk is released. http://sourceforge.net/projects/netatalk/files/netatalk/2.2/ Latest entry is 9 hours ago with no beta tag? Also updated my server, testing is in progress... Quote Link to comment
savestheday Posted July 27, 2011 Share Posted July 27, 2011 It seems to me that mover isn't being invoked automatically - every time unRAID is booted. I have to go into settings, and 'Apply' the mover schedule before it will be run. Is anyone else experiencing this? Yup noticed that the past few days. Btw Nezil thanks for all your permissions help! Quote Link to comment
ftp222 Posted July 28, 2011 Share Posted July 28, 2011 I just upgraded my test system to 5.0b10 from 4.7. I followed the instructions in the release notes for the upgrade. None of the drives showed MBR error or any messages pertaining to an MBR problem; however when I started the array, disks 1 & 2 show as unformatted. All disks worked fine in 4.7 for the past month. When I upgraded to 4.7 from 4.6 I did have HPA on these 2 drives. I removed it with a tool suggested by this forum and it allowed an upgrade to 4.7 without any problems. I have to believe this is somehow pertinent to what I am seeing with this upgrade to 5.0. My system log is attached. It looks like there is a problem with the superblock on md1 & md2? What steps do the experts suggest? Jul 27 22:15:44 Backup logger: mount: wrong fs type, bad option, bad superblock on /dev/md2, Jul 27 22:15:44 Backup logger: missing codepage or helper program, or other error Jul 27 22:15:44 Backup logger: In some cases useful info is found in syslog - try Jul 27 22:15:44 Backup logger: dmesg | tail or so Jul 27 22:15:44 Backup logger: Jul 27 22:15:44 Backup emhttp: _shcmd: shcmd (115): exit status: 32 Jul 27 22:15:44 Backup emhttp: disk2 mount error: 32 Jul 27 22:15:44 Backup emhttp: shcmd (124): rmdir /mnt/disk2 Jul 27 22:15:44 Backup kernel: REISERFS (device md3): Using r5 hash to sort names Jul 27 22:15:44 Backup kernel: REISERFS (device md4): Using r5 hash to sort names Jul 27 22:15:44 Backup kernel: REISERFS (device md7): Using r5 hash to sort names Jul 27 22:15:44 Backup logger: mount: wrong fs type, bad option, bad superblock on /dev/md1, Jul 27 22:15:44 Backup logger: missing codepage or helper program, or other error Jul 27 22:15:44 Backup logger: In some cases useful info is found in syslog - try Jul 27 22:15:44 Backup logger: dmesg | tail or so Jul 27 22:15:44 Backup logger: Jul 27 22:15:44 Backup emhttp: _shcmd: shcmd (120): exit status: 32 Jul 27 22:15:44 Backup emhttp: disk1 mount error: 32 Jul 27 22:15:44 Backup emhttp: shcmd (125): rmdir /mnt/disk1 Jul 27 22:15:44 Backup kernel: REISERFS (device md8): Using r5 hash to sort names Jul 27 22:15:44 Backup kernel: REISERFS (device md6): Using r5 hash to sort names Jul 27 22:15:44 Backup kernel: REISERFS (device md5): Using r5 hash to sort names Edit - I assumed I would see MBR unknown on the main page somewhere, I did not know I had to click on the disk number to see the info. Upon clicking the disk number, I do see: Partition 1 size: 488386552 KB (K=1024) Partition format: MBR: 4K-aligned File sytem type: unknown syslog07272011.txt Quote Link to comment
Joe L. Posted July 28, 2011 Share Posted July 28, 2011 DO NOT FORMAT THOSE DRIVES. instead, stop the array and use the mkmbr utility on them. They appear unformatted because their partition starts on sector 63. mkmbr /dev/sdX should do it. (change /dev/sdX = for each of the two drives). It will fix the MBRs of the two disks. Then re-start the array. Quote Link to comment
bubbaQ Posted July 28, 2011 Share Posted July 28, 2011 Just upgraded a 12-drive 4.4.2 system to 5b10, on a full 13.1 Slackware distro, with 2.6.39.3 kernel. I updated the wiki article http://lime-technology.com/wiki/index.php?title=Installing_unRAID_5.0_on_a_full_Slackware_Distro#Extract_initramfs_files_from_bzroot accordingly. All drives were found and array was ready to mount, despite changing controllers to AOC-SASLP-MV8. I was happy with the existing r8169 so I re-enabled that in the kernel. Took several hours to finish the new permissions script, and Apache was hosed until I changed the Apache config to use the user "nobody." While the permissions script was running, I could not open another browser window into emhttp. Speeds are good.... about 45mb/sec over LAN. One small nit... the file explorer available with the folder icon on the main emhttp display, is showing a bogus date for "last modified" Quote Link to comment
ftp222 Posted July 29, 2011 Share Posted July 29, 2011 DO NOT FORMAT THOSE DRIVES. instead, stop the array and use the mkmbr utility on them. They appear unformatted because their partition starts on sector 63. mkmbr /dev/sdX should do it. (change /dev/sdX = for each of the two drives). It will fix the MBRs of the two disks. Then re-start the array. Thank you Joe L. That seems to have gotten everything in order. Running new permissions script now. Quote Link to comment
capler Posted July 29, 2011 Share Posted July 29, 2011 Can someone please help me re-enable the linux r8169 driver into this beta10 release? I tried copying the .ko across from beta9 but modprobe in beta10 doesn't accept it (I'm guessing because the kernel is now 2.6.39.3). I tried downloading r8169 driver source code from Realtek site, but I can't build ('make clean modules') the driver because of an error (the 'build' folder is allegedly not found, even though when I 'ls' that folder it does, in fact exist). Quote Link to comment
prostuff1 Posted July 29, 2011 Share Posted July 29, 2011 Can someone please help me re-enable the linux r8169 driver into this beta10 release? I tried copying the .ko across from beta9 but modprobe in beta10 doesn't accept it (I'm guessing because the kernel is now 2.6.39.3). I tried downloading r8169 driver source code from Realtek site, but I can't build ('make clean modules') the driver because of an error (the 'build' folder is allegedly not found, even though when I 'ls' that folder it does, in fact exist). I assume you want to do this because you are having problems with beta10 and the Realtek driver now included. Quote Link to comment
mrmachine Posted July 29, 2011 Share Posted July 29, 2011 Can someone please help me re-enable the linux r8169 driver into this beta10 release? I tried copying the .ko across from beta9 but modprobe in beta10 doesn't accept it (I'm guessing because the kernel is now 2.6.39.3). I tried downloading r8169 driver source code from Realtek site, but I can't build ('make clean modules') the driver because of an error (the 'build' folder is allegedly not found, even though when I 'ls' that folder it does, in fact exist). Is it a symlink that points to a folder that does not exist? Quote Link to comment
capler Posted July 29, 2011 Share Posted July 29, 2011 Can someone please help me re-enable the linux r8169 driver into this beta10 release? I tried copying the .ko across from beta9 but modprobe in beta10 doesn't accept it (I'm guessing because the kernel is now 2.6.39.3). I tried downloading r8169 driver source code from Realtek site, but I can't build ('make clean modules') the driver because of an error (the 'build' folder is allegedly not found, even though when I 'ls' that folder it does, in fact exist). I assume you want to do this because you are having problems with beta10 and the Realtek driver now included. yes exactly: http://lime-technology.com/forum/index.php?topic=14158.msg134153#msg134153 Quote Link to comment
capler Posted July 29, 2011 Share Posted July 29, 2011 Can someone please help me re-enable the linux r8169 driver into this beta10 release? I tried copying the .ko across from beta9 but modprobe in beta10 doesn't accept it (I'm guessing because the kernel is now 2.6.39.3). I tried downloading r8169 driver source code from Realtek site, but I can't build ('make clean modules') the driver because of an error (the 'build' folder is allegedly not found, even though when I 'ls' that folder it does, in fact exist). Is it a symlink that points to a folder that does not exist? /lib/modules/2.6.39.3-unRAID/build is a symlink that points to a folder which does exist: /usr/src/linux-2.6.39.3 but that folder only contains: .config COPYING System.map drivers/ but according to my research there's supposed to be a Makefile there too in order to get make to build. Quote Link to comment
mrmachine Posted July 29, 2011 Share Posted July 29, 2011 Can someone please help me re-enable the linux r8169 driver into this beta10 release? I tried copying the .ko across from beta9 but modprobe in beta10 doesn't accept it (I'm guessing because the kernel is now 2.6.39.3). I tried downloading r8169 driver source code from Realtek site, but I can't build ('make clean modules') the driver because of an error (the 'build' folder is allegedly not found, even though when I 'ls' that folder it does, in fact exist). Is it a symlink that points to a folder that does not exist? /lib/modules/2.6.39.3-unRAID/build is a symlink that points to a folder which does exist: /usr/src/linux-2.6.39.3 but that folder only contains: .config COPYING System.map drivers/ but according to my research there's supposed to be a Makefile there too in order to get make to build. unRAID only includes the config, custom drivers and System.map. You will need to download the kernel source, copy unRAID's .config, make oldconfig, make menuconfig, etc. I have recently done this myself to add DVB drivers so I can run Tvheadend. I worked out how to do it all by taking bits and pieces from a few pages on the Wiki. Mainly how to compile kernel headers and install Virtual Box in combination with how to recompile the kernel. The Wiki pages are not totally clear though, as they make it sound as though you need to install a full Slackware distro to build the kernel, apart from one sentence that says it can be done from unRAID installed on a flash drive. I've attached my work-in-progress scripts that I use to build a new kernel and modules, extract bzroot, install drivers and kernel modules and userland apps/packages, and recompress bzroot. Just dump these in /boot/kernel/, then cd /boot/kernel and ./1-kernel.sh, ./2-userland.sh, and ./3-compress.sh. Make sure you modify 2-userland.sh to suit your needs (adding extra kernel drivers/modules and packages). It's currently customised for my needs. The first script will download the sources and packages you need to recompile the kernel. Follow the examples in the second script to download and install any additional stuff you want. The third script will re-compress the bzroot and install the new kernel and system at /boot/bzroot_custom and /boot/bzimage_custom. You'll need to modify syslinux.cfg to add an option to boot the custom kernel and system. Archive.zip Quote Link to comment
limetech Posted July 29, 2011 Author Share Posted July 29, 2011 Can someone please help me re-enable the linux r8169 driver into this beta10 release? I tried copying the .ko across from beta9 but modprobe in beta10 doesn't accept it (I'm guessing because the kernel is now 2.6.39.3). I tried downloading r8169 driver source code from Realtek site, but I can't build ('make clean modules') the driver because of an error (the 'build' folder is allegedly not found, even though when I 'ls' that folder it does, in fact exist). I assume you want to do this because you are having problems with beta10 and the Realtek driver now included. yes exactly: http://lime-technology.com/forum/index.php?topic=14158.msg134153#msg134153 I'm going to get rid of r8168 and restore r8169 in -beta10a. So much for Realtek being able to support their own NIC's Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.