I just compiled my own kernel based in the default kernel “3.1.0-1.2-desktop” the problem that I’m getting is that the system doesn’t recognize my hard drive
trying manual resume from /dev/disk/by-id/...-part5
resume device /dev/disk/by-id/...-part5 not found (ignoring)
trying manual resume from /dev/disk/by-id/...-part5
resume device /dev/disk/by-id/...-part5 not found (ignoring)
waiting for device /dev/sda2 to appear: ................. could no find /dev/sda2
want me to fall back to /dev/disk/by-id/...-part2? (Y/n)
waiting for device /dev/disk/by-id/...-part2 to appear............. not found -- exiting to /bin/sh
-sh: cannot set terminal process group (-1): inappropriate ioctl for device
-sh: no job control in this shell
$
i made sure that the driver of the Hard Driver was inside the kernel this is a pick of the .config file (using cat /usr/src/linux/.config | grep CONFIG_ATA)
# CONFIG_ATALK is not set
# CONFIG_ATA_OVER_ETH is not set
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_VERBOSE_ERROR=y
CONFIG_ATA_ACPI=y
CONFIG_ATA_SFF=y
CONFIG_ATA_BMDMA=y
CONFIG_ATA_PIIX=y #<--------- this is the driver that I need
CONFIG_ATA_GENERIC=m
Did you leave yourself a working kernel to boot from? So, not sure what is wrong, but I have a nice script that can compile any kernel version AND it is linked to another script that can be used to download any kernel version, back to 2.6.11 of 2005 fame. Here is the link:
You are given an opportunity to configure how your kernel works by default. Take that option and search on the terms you mention above to see if you can make the required changes.
Thanks! jdmcdaniel3 the script is great! but didn’t fix my problem
I have the default kernel working properly (this is the one that I’m using right now) I wan to compile my own kernel to make sure that everything is in order and as i like it
In sakc, you are given an opportunity to make kernel configuration changes using menuconfig and you can even search on things like “CONFIG_ATA_PIIX=y”. Before the compile starts, sakc takes on the default kernel configuration. So again, what exactly is the problem you have when you compile a kernel using sakc? Did you notice there is another linked script called sgtb, which can get for you any released kernel version, clear back to 2005 releases that can be compiled with sakc?
On 12/03/2011 04:06 PM, jdmcdaniel3 wrote:
>
> juanp_1982;2413961 Wrote:
>> Thanks! jdmcdaniel3 the script is great! but didn’t fix my problem
>>
>> I have the default kernel working properly (this is the one that I’m
>> using right now) I wan to compile my own kernel to make sure that
>> everything is in order and as i like it
>
> In sakc, you are given an opportunity to make kernel configuration
> changes using menuconfig and you can even search on things like
> “CONFIG_ATA_PIIX=y”. Before the compile starts, sakc takes on the
> default kernel configuration. So again, what exactly is the problem you
> have when you compile a kernel using sakc? Did you notice there is
> another linked script called sgtb, which can get for you any released
> kernel version, clear back to 2005 releases that can be compiled with
> sakc?
@juanp: How did you generate .config, the kernel configuration file?
@jdmcdaniel3: I didn’t get any error, I compile a new kernel (3.1.4 that I downloaded from The Linux Kernel Archives), I didn’t notice sgtb. in either way (with sakc or the traditional way) I have always made sure to set CONFIG_ATA_PIIX=y
@lwfinger: first I copied the /boot/config-2.6.37.6-0.9-desktop into /usr/src/linux-2.6.37.6-0.9 then I ran make localmodconfig and then I ran make xconfig to remove most of the stuff that I don’t have in my PC
I think that when I working with menuconfig and sakc or xconfig and the traditional way I unset something that cause this problem
I would like to say while modifying the kernel defaults to reduce kernel size or to remove unneeded modules might speed it up, you really need to know what you are doing. Now it can be argued that you will never learn without trying, but the results might be to make it time to reload openSUSE and to start over again. Most often, the rewards for such kernel modifications is no noticeable change what so ever. I would like to say that doing such kernel changes while in a VM is a good way to do little damage while learning the ropes. But in the end, I just stick with the defaults set by the developers with very few exceptions. The most recent change I used was to set the default governor speed for my Intel CPU. But in general, I would be careful modifying the kernel defaults from that you find.
I have been compiling my own kernel for the pass 4 years, I know that the performance improvement it too little but I’m stubborn I like to know what is running what is not. The other thing is that I know that this kernel is not working because of something very small as a simple check mark or a simple selection for a module so I would like to fix since I’m almost done with it
PS: I have my default kernel working just ok, so I’m able to use my PC
On 12/04/2011 05:16 PM, juanp 1982 wrote:
>
> Hi jdmcdaniel3
>
> I have been compiling my own kernel for the pass 4 years, I know that
> the performance improvement it too little but I’m stubborn I like to
> know what is running what is not. The other thing is that I know that
> this kernel is not working because of something very small as a simple
> check mark or a simple selection for a module so I would like to fix
> since I’m almost done with it
> PS: I have my default kernel working just ok, so I’m able to use my PC
Obviously, you eliminated something that is needed to boot the system. The most
likely possibility is the disk driver. You should look at the lsmod output from
your current kernel, locate the disk driver, and make certain that it is
configured in the new system.
On 12/05/2011 12:06 PM, juanp 1982 wrote:
>
> that’s the thing, I thought that before posting here, so the driver for
> my hard drive is OK, but I don’t know what else could be
Post the output of lsmod here, and your .config on the openSUSE pastebin.
On 12/05/2011 01:36 PM, back space wrote:
>
> I see your disk label is sda, doesn’t that indicate Serial-ATA or SCSI?
>
> I had something similar a while back when messing round with Gentoo,
> and had to enable SCSI and SATA support to have the computer recognise
> the drive.
It used to be true that sda meant SATA or SCSI, but now any drive handled by
libata is also called sda.
On 12/05/2011 03:26 PM, juanp 1982 wrote:
>
> lwfinger;2414690 Wrote:
>> On 12/05/2011 01:56 PM, juanp 1982 wrote:
>>>
>>> @lwfinger: this is my ‘.config’
>>> (http://dl.dropbox.com/u/38105514/Config.txt) file and this is my
>>> ‘lsmod’ (http://dl.dropbox.com/u/38105514/lsmod) file
>>
>> I did not see any problems yet. It seems that ata_generic is the only
>> one needed
>> for the disk, and that is generated in your kernel.
>>
>> Please post the output from ‘sudo make install’.
>
>
> this is ‘make install’ (http://dl.dropbox.com/u/38105514/Install.txt)
> output
Well, ata_generic is in the module list to be part of initrd. I have no idea why
your kernel will not boot.
