LinHES Forums http://forum.linhes.org/ |
|
R5.5 No sata_mv module http://forum.linhes.org/viewtopic.php?f=2&t=18607 |
Page 1 of 1 |
Author: | mihanson [ Sun Jul 20, 2008 11:32 pm ] |
Post subject: | R5.5 No sata_mv module |
I'm having trouble with my Supermicro AOC-SAT2-MV8 8 port SATA PCI-X card with R5.5. It seems that the module I need, sata_mv, is not compiled in the kernel or as a module. Line 1324 (if memory serves) of the /boot/config<TAB> says it is not included as module or in kernel. Anyone who may have a card based on Marvell Hercules-2 chipset beware. This particular card uses the Marvell 88SX6081. Code: # lspci -vv 0a:01.0 SCSI storage controller: Marvell Technology Group Ltd. MV88SX6081 8-port SATA II PCI-X Controller (rev 09) Subsystem: Marvell Technology Group Ltd. Unknown device 11ab Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 7 Region 0: Memory at ed400000 (64-bit, non-prefetchable) [size=1M] Region 2: I/O ports at 4000 [size=256] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [60] PCI-X non-bridge device Command: DPERE- ERO- RBC=512 OST=4 Status: Dev=0a:01.0 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=512 DMOST=4 DMCRS=8 RSCEM- 266MHz- 533MHz- Code: # lspci -mn
0a:01.0 "0100" "11ab" "6081" -r09 "11ab" "11ab" |
Author: | yaplej [ Sat Jul 26, 2008 11:09 pm ] |
Post subject: | |
I am having the same problem. http://knoppmyth.net/phpBB2/viewtopic.php?t=18499 |
Author: | mihanson [ Sun Jul 27, 2008 10:50 am ] |
Post subject: | |
I spoke to Cecil (cesman) about it and it was not included because it was marked "highly experimental" in the kernel. So, in order to use a card that needs sata_mv, here's what you need to do (all as root): DO THIS AT YOUR OWN RISK! BACKUP/CLONE YOUR SYSTEM FIRST! Get the kernel source from knoppmyth.net Code: dpkg -i linux-source-2.6.23-chw-4_2.6.23-chw-4-10.00.Custom_all.deb cd /usr/src && tar jxf linux-source-2.6.23-chw-4.tar.bz2 cd linux-source-2.6.23-chw-4 cp /boot/config-2.6.23-chw4 .config make menuconfig Arrow down to Device Drivers > SATA (prod) and Parallel ATA (experimental) Drivers In there somewhere is the Marvell driver marked highly experimental. Highlight it and press 'y' It should have a * in the box now. Exit out and when promted to save the configuration, say yes. Code: make -j2 Note the number following the -j should be the number of processers in the box x2. So if you have a quad-core, enter -j8, dual-core -j4 and so on. After it finishes (it could take a while) Code: make install
make modules_install lilo -v reboot Note that there were at least a couple ethernet device drivers (may be others for other devices, but I'm not sure) that were compiled from outside the kernel source tree. I believe they were the e1000 (for intel NICs) and a Realtek driver (not sure of the name). If you need these drivers, be sure to copy the .ko files to a safe place before running make install and then place them back in the proper directories after you run make install.[/b] |
Author: | graysky [ Thu Oct 02, 2008 1:19 pm ] |
Post subject: | |
@mihanson - I followed your steps but it resulted in a kernel panic upon reboot. Please have a look at my thread here if you can help ![]() |
Author: | mihanson [ Thu Oct 02, 2008 2:43 pm ] |
Post subject: | |
graysky wrote: @mihanson - I followed your steps but it resulted in a kernel panic upon reboot. Please have a look at my thread here if you can help
![]() graysky: not sure what it could be. My instuctions "worked for me" on the sata_mv module. Maybe your changes don't play nice with some other things in the kernel? |
Author: | graysky [ Thu Oct 02, 2008 2:54 pm ] |
Post subject: | |
thanks for the reply.. I dunno since this is my first experience working with recompiling the kernels ![]() |
Author: | mihanson [ Thu Oct 02, 2008 9:00 pm ] |
Post subject: | |
Code: # lilo -v But I thought you covered that here: Quote: Code: # make -j2 # make install (answered yes to re-running lilo) # reboot |
Author: | graysky [ Fri Oct 03, 2008 12:50 pm ] |
Post subject: | |
Right, but since it wasn't mentioned in your steps, I just wanted to make sure. I just did a fresh install of R5.5, and didn't change any options, just copied over the .config and rebuilt the kernel which worked without a kernel panic. To me, that proves that the problem must be with something I'm compiling into it... I'm going to go though and just do all kernel modules now and see if it'll boot. There was one area (CONFIG_NF_CONNTRACK_MARK=y) that didn't offer an option for a module, either enabled or disabled. I plan to omit that altogether and see. Thanks again for the reply. EDIT: nope, kernel panic results from just adding module support ![]() What is the correct method to save my out-of-the-box kernel as a third option in lilo's boot menu so that I can boot into it without having to do a new install from scratch? |
Author: | mihanson [ Fri Oct 03, 2008 2:41 pm ] |
Post subject: | |
graysky wrote: Right, but since it wasn't mentioned in your steps, I just wanted to make sure. Yeah, I forgot that step in my instructions, but I went back and edited to add that step. Quote: What is the correct method to save my out-of-the-box kernel as a third option in lilo's boot menu so that I can boot into it without having to do a new install from scratch?
I'm not versed enough in kernel compiles, but I'd think you'd need to give your new kernel a unique name and not use cesman's "default" naming convention. |
Author: | graysky [ Fri Oct 03, 2008 2:50 pm ] |
Post subject: | |
mihanson wrote: graysky wrote: Right, but since it wasn't mentioned in your steps, I just wanted to make sure. Yeah, I forgot that step in my instructions, but I went back and edited to add that step. Quote: What is the correct method to save my out-of-the-box kernel as a third option in lilo's boot menu so that I can boot into it without having to do a new install from scratch? I'm not versed enough in kernel compiles, but I'd think you'd need to give your new kernel a unique name and not use cesman's "default" naming convention. Yeah, I had a look at /etc/lilo.conf and more or less just copied the default section. I copied the kernel and .gz to working and working.gz and edited my conf accordingly... I should now have three options. We'll see. |
Author: | graysky [ Sat Oct 04, 2008 5:50 pm ] |
Post subject: | |
Figured it out... I was missing the #make modules_install step. Anyway, I wrote up an unofficial HOWTO: Install Moblock on R5.5 in case anyone cares to do so. |
Author: | yaplej [ Sun Nov 30, 2008 2:48 am ] |
Post subject: | Thank you! |
mihanson, Just wanted to stop by and say thanks. Those steps worked perfectly. I installed R5.5 to my IDE boot disk, and then before running any of the setup scripts <CTRL><ALT><F1> to the console, and installed the custom kernel. When I rebooted it starts back up asking for the root password to run the setup scripts. Now to LVM or to storage group... oh off topic. Thanks again mabye R6 will have native support for Marvell ![]() |
Page 1 of 1 | All times are UTC - 6 hours |
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |