[LAU] pretty much frustrated about those rt-kernels!

[schoappied]

schoappied wrote:
> Emanuel Rumpf wrote:
>   
>> 2008/7/7 schoappied <schoappied at gmail.com>:
>>   
>>     
>>> I did:
>>> # mkinitramfs -o initrd.img-2.6.25.8-rt7 2.6.25.8-rt7
>>>
>>> But the errors still remains
>>>     
>>>       
>> hm .. maybe it was the change to fstab then, that
>> had an effect on it.
>>
>> I discovered some problems with lines like this in /etc/fstab :
>> UUID=13495293458246835258345  /  reiserfs ............etc.
>>
>> things went better, when replaced with:
>> /dev/disk/by-uuid/13495293458246835258345  /  reiserfs ............etc.
>>
>> (directory names instead of "UUID=" (probably more compatible - who knows..))
>> _______________________________________________
>> Linux-audio-user mailing list
>> Linux-audio-user at lists.linuxaudio.org
>> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
>>
>>   
>>     
> I'm glad I can use the 64studio kernel now and have wireless internet 
> working.
>
>
> When looking at my fstab file, its looking fine to my, but I question if 
> the mount option for /hda3 is fine.... <none>
>
> # /etc/fstab: static file system information.
> #
> # <file system> <mount point>   <type>  <options>       <dump>  <pass>
> proc            /proc           proc    defaults        0       0
> /dev/hda1       /               ext3    errors=remount-ro 0       1
> /dev/hda2       /home           ext3    defaults        0       2
> /dev/hda3       none            swap    sw              0       0
> /dev/hdc        /media/cdrom0   udf,iso9660 user,noauto     0       0
> /dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0
>
>
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user at lists.linuxaudio.org
> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
>
>   
But how can it be that the normal kernel just works fine with this fstab?

I think the problem is more likely related to the .config file or 
initrd.img-2.6.25.8-rt7 stuff or can it be that there's something wrong 
in the settings/ .config for ATA drives... ??? But I must say, I'm not 
very experienced in this kind of problem solving...

And why doesn't the system complain about the /hda1??