| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 56840 | 2005-04-16 10:36:00 | Kernel Compile Supermount Querie | Phil B (648) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 345763 | 2005-04-16 10:36:00 | Running Mandrake 10.1 with stock 2.6.8 kernel. Downloaded & compiled the latest kernel, can't remember the number as i'm in xp at the mo. With the new kernel running the system can't see the other hard drive (sda1) through the ite raid card. It works ok with the stock kernel. When the system boots it says Supermount is not available for drive sda1. I've looked through the kernel options but can't find anything. Any ideas ? Phil |
Phil B (648) | ||
| 345764 | 2005-04-16 10:48:00 | Have a look at the previous kernel config file which should hopefully be in /boot. If you examine the section for SATA you should see what was configured on the working kernel. I've just looked at my kernel config (I don't have SATA), and it has this section: # CONFIG_BLK_DEV_IDE_SATA is not set # CONFIG_BLK_DEV_HD_IDE is not set CONFIG_BLK_DEV_IDEDISK=y Not sure if you need to select anything else. You will need to redo the kernel again with the support this time. |
Jen (38) | ||
| 345765 | 2005-04-16 11:21:00 | Not sure if you need to select anything else. You will need to redo the kernel again with the support this time.Yes, you will need more than that, and infact I don't think what I posted above will help (told you I don't use SATA, and there is also the SATA controller to configure in :rolleyes: ) Your best bet might to be to use the working config and use make oldconfig so that your working kernel settings are transferred to the new kernel and you only get asked about any new features in the lastest kernel. |
Jen (38) | ||
| 345766 | 2005-04-17 03:45:00 | As always, look at dmesg and the tail of /var/log/messages. The tone of that message suggests to me that it might be something wrong in a configuration file for supermount. apropos supermount might suggest things to look at. It's almost certainly not anything to do with the kernel options. Though I could be wrong. ;) Is SATA support a module or compiled into the kernel? A module might need to be explicitly loaded. I don't know. SATA isn't obsolete yet, so I haven't got any. |
Graham L (2) | ||
| 345767 | 2005-04-17 09:49:00 | I've just seen in mnt that it is listed as win c & win d (it' partitioned) But it doesn't show any of the files, just blank Any Ideas on that ? |
Phil B (648) | ||
| 345768 | 2005-04-19 02:42:00 | Sorry, this sort of dropped off the screen . The distribution kernel has modules for "everything" . This is why the boot is two stages: the ramdisk kernel is a minimum system which is just smart enough to load any modules needed for loading the main system . When you compile your own, you have to explicitly enable the things you need . (Just doing make oldconfig might not be enough . . . you don't have some of the sources . . . though SATA ought to be OK, because it's a disk system . I've had trouble with some "3rd party" driver sources not being included in the kernel rpm) . What you see in /mnt/ are the "mount points" for disks . Unless a disk is actually mounted, there is usually nothing there . (You can write and read files in such a mount point, and they will be accessible only when nothing is mounted on it . That could be a way of having "secret files" . They would be stored on the disk which has the "/" root . ) |
Graham L (2) | ||
| 1 | |||||