struct sock change in kernel 2.6

[lijin liu]

Hello everyone!

I am trying to implement a simple tcp server in the kernel. I read the
ktcpvs's source code, but it works under kernel 2.4.

The  struct sock changed in kernel 2.6, I have two questions about the struct:

1. Is sk_wq field in 2.6 equals to sk_sleep field in 2.4?
2. How can I access the tcp accept queue in kernel 2.6? (In kernel
2.4, we could use tp_pinfo.af_tcp.accept_queue, but it was removed in
2.6)


PS: Should sk_receive_queue in the struct sock be used as
tp_pinfo.af_tcp.accept_queue?

Thanks a lot!

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

RE: custom kernel install - query

[Srinivas G.]

> r...@ubuntu:/boot# ls
> abi-2.6.32-24-generic memtest86+.bin
> config-2.6.32-24-generic  System.map-2.6.32-24-generic
> config-2.6.35.9   System.map-2.6.35.9
> grub  vmcoreinfo-2.6.32-24-generic
> initrd.img-2.6.32-24-generic  vmlinuz-2.6.32-24-generic
> initrd-img-2.6.35.9-custom    vmlinuz-2.6.35.9
> initrd-img-kernel-2.6.35.9
> r...@ubuntu:/boot# update-grub
> Generating grub.cfg ...
> Found linux image: /boot/vmlinuz-2.6.35.9
> Found linux image: /boot/vmlinuz-2.6.32-24-generic
> Found initrd image: /boot/initrd.img-2.6.32-24-generic
> Found Microsoft Windows XP Professional on /dev/sda2
> done
> r...@ubuntu:/boot# 

Hi Sengottuvelan,

Can you rename the initrd file to initrd-img-2.6.35.9 from 
initrd-img-2.6.35.9-custom. For other files, like System.map and config, they 
do not have the -custom extension. So, just remove the -custom from your initrd 
and run the update-grub command again.   

Thanks and Regards,
Srinivas G


___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Need help EHCI host driver on Linux 2.6.29

[Syed Khader]

On Tue, Dec 21, 2010 at 5:18 PM, CL Lee  wrote:
> Dear Experts,
>
> I am developing a EHCI host driver for Linux kernel 2.6.29 on a proprietary 
> SoC. But for weeks now, I am troubleshooting a time out error from khubd.
>
Which SoC? what arch? What is the error message you see?
> I believe it's related to the client device not being able to update the qtd 
> struct which has been set at some Dma addresses, say 0x87xx. Is this 
> possible?
>
are you referring to qtd_dma in qdt_struct?
> The main issue is the register address for chip lies in 0x5a80 range, so 
> is the on-chip memory. If I set the qtd structs to on chip memory(internal 
> sram), kernel paging error will occur.
>
If this register address range are actual hw addresses, then yes you
will see kernel paging error, unless you have ioremapped them.

-syed

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: custom kernel install - query

[Sengottuvelan S]

Hi Srinivas,

Even doing update-grub command , I was not able to see new menu-entry
in /boot/grub/grub.cfg . Somehow , "update-grub"  not catching "*
initrd-img-2.6.35.9-custom"*  in the boot

Any help on this highly appreciated

r...@ubuntu:/boot# ls
abi-2.6.32-24-generic memtest86+.bin
config-2.6.32-24-generic  System.map-2.6.32-24-generic
config-2.6.35.9   System.map-2.6.35.9
grub  vmcoreinfo-2.6.32-24-generic
initrd.img-2.6.32-24-generic  vmlinuz-2.6.32-24-generic
*initrd-img-2.6.35.9-custom*vmlinuz-2.6.35.9
initrd-img-kernel-2.6.35.9
r...@ubuntu:/boot# update-grub
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.35.9
Found linux image: /boot/vmlinuz-2.6.32-24-generic
*Found initrd image: /boot/initrd.img-2.6.32-24-generic
*Found Microsoft Windows XP Professional on /dev/sda2
done
r...@ubuntu:/boot#



On Mon, Dec 20, 2010 at 8:33 PM, Srinivas G. <
sriniv...@esntechnologies.co.in> wrote:

> > > On Ubuntu 10.10, you need to update /etc/default/grub and then use
> > > 'sudo update-grub' to update your configuration.
> > >
> >
> > I see, thanks for the info on grub2 guys! If the files were copied to
> > /boot it sounds like the original poster just needs to update grub. I
> > still don't understand how the files got copied tho, I always have to
> > dpkg them myself (not done at the make-kpkg stage) and grub is taken
> > care of then.
>
> On Ubuntu systems, just follow the following steps for building the new
> kernel images.
>
> Note: I build the kernel image as a ROOT, here. So, I did not use the
> SUDO.
>
> 1) Download the required kernel version TAR ball from the www.kernel.org
> and extract it in the /usr/src directory.
> 2) Change into the newly created directory.
> 3) Build the kernel with the following set of commands from
> /usr/src/linux directory. Here the linux is a link to the newly created
> directory.
> 4) Then run the following commands.
> # make mrproper
> # make clean
> # make menuconfig  - Just exit from the GUI menu by pressing YES.
> # make prepare
> # make menuconfig- Do the modifications, whatever you want.
> # make clean
> # make bzImage   (capital L letter in bzImage)
> # make modules
> # make modules_install
> # make install
>
> Then, build the initrd file with the following command from anywhere,
> however you need to copy the build initrd file explicitly to the /boot
> directory.
> # mkinitramfs -o initrd-img-kernel-version kernel-version
>
> Finally, update the grub with the following command from /boot directory
> and restart the system. By default it boots into the newly build kernel
> image.
> # update-grub
>
> For more information on Grub follow the link
> https://help.ubuntu.com/community/Grub2
>
> Thanks and Regards,
> Srinivas G
>
>


-- 
Regards,
S. Sengottuvelan.
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Need help EHCI host driver on Linux 2.6.29

[Greg KH]

On Wed, Dec 22, 2010 at 07:18:35AM +0800, CL Lee wrote:
> Dear Experts,
> 
> I am developing a EHCI host driver for Linux kernel 2.6.29 on a
> proprietary SoC. But for weeks now, I am troubleshooting a time out
> error from khubd.

Ick, you do realize how old 2.6.29 is, right?  It's many years old, and
way out of date and unsupported.  If you are stuck with it, you are on
your own, sorry.

> I believe it's related to the client device not being able to update
> the qtd struct which has been set at some Dma addresses, say
> 0x87xx. Is this possible?
> 
> The main issue is the register address for chip lies in 0x5a80
> range, so is the on-chip memory. If I set the qtd structs to on chip
> memory(internal sram), kernel paging error will occur. 
> 
> So I am at a loss of what I can. Please kindly advise.

Care to try your driver out on .36 or .37-rc6? and post your code?
Without that, there's not much we can do, sorry.

good luck,

greg k-h

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Problem with booting newly compiled kernel

[Mandeep Sandhu]

>>> I believe the UUID is created per partition/file system and are
>>> created when creating the file system for a partition.  If anyone even
>>> had their drive changed from /dev/hda to /dev/sda due to linux
>>> changing how they labeled ide drives they will know why people use
>>> UUID instead of the device name .  Also, it is not guaranteed that
>>> they drives will always come up in the same order between kernel
>>> releases(This is my personal opinion).
>>>
>>
>> I think you are correct, it is assigned when a file system is created.
>> It is a tunable parameter which can be chnaged using tune2fs -U
>> command.
>> A new UUID can be generated using command uuidgen.
>
> Would that mean that there has to be a table stored somewhere which
> provides this kind of mapping? In that case, as this table is required
> at the boot time, even before the bootable harddisk is detected which
> could have stored such a table persitently, is this table written
> somewhere in the initramfs?

I think UDEV manages persistent naming of devices for you. The
mappings that you talk of are managed as udev rules. Reading more on
udev might give you a better idea. I don't know the exact details so
I'll point you to link I've planning to read for some time! :)
http://reactivated.net/writing_udev_rules.html

CMIIW.

Regards,
-mandeep


>
>>
>>> --
>>> John
>>>
>>
>
> -
> Shreyansh
>
> ___
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Accessing PCI Memory Mapped Registers in Linux Kernel

[Syed Khader]

> As we've talked, it looks the code would be ok, but I guess architecture
> doesn't handle the 16 bit address correctly. Our team will find a way to get
> through this by modifying the PCI module.
Which is the platform/arch you are seeing this problem as opposed to
intel(Where the code works?).
Remember on Intel, I/O space is separate from main memory. On other
platforms(say on ARM) its memory mapped.
I suspect the dev->base_addr may not be the same on both platforms.
Have you checked it?

-syed

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Problem with booting newly compiled kernel

[Shreyansh Jain]

Hi,

On Wed, Dec 22, 2010 at 2:58 AM, Prasad Joshi  wrote:
> On Tue, Dec 21, 2010 at 8:43 PM, John Mahoney  wrote:
 b. Also, who generates these UUID - is it a disk property (like, ROM
 signature or stuff?), or this is some udev magic?

>>>
>>> IMHO, this is fixed for every device during manufacturing.
>>>
>>
>> I believe the UUID is created per partition/file system and are
>> created when creating the file system for a partition.  If anyone even
>> had their drive changed from /dev/hda to /dev/sda due to linux
>> changing how they labeled ide drives they will know why people use
>> UUID instead of the device name .  Also, it is not guaranteed that
>> they drives will always come up in the same order between kernel
>> releases(This is my personal opinion).
>>
>
> I think you are correct, it is assigned when a file system is created.
> It is a tunable parameter which can be chnaged using tune2fs -U
> command.
> A new UUID can be generated using command uuidgen.

Would that mean that there has to be a table stored somewhere which
provides this kind of mapping? In that case, as this table is required
at the boot time, even before the bootable harddisk is detected which
could have stored such a table persitently, is this table written
somewhere in the initramfs?

>
>> --
>> John
>>
>

-
Shreyansh

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: KVM - virtualization support

[Ponmuthu Subramaniam Nandan]

Looking at the datasheet for Intel(R) Core(TM)2 Duo CPU   E7200,
http://ark.intel.com/Product.aspx?id=35348

VTx is disabled in the core itself, so not sure whether you will have any
bios options to enable that.

But as John rightly pointed out, you should be able to run virtual machine
(Virtualbox, qemu..), but with performance penalty.

Regards,
Subbu
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Need help EHCI host driver on Linux 2.6.29

[CL Lee]

Dear Experts,

I am developing a EHCI host driver for Linux kernel 2.6.29 on a proprietary 
SoC. But for weeks now, I am troubleshooting a time out error from khubd.

I believe it's related to the client device not being able to update the qtd 
struct which has been set at some Dma addresses, say 0x87xx. Is this 
possible?

The main issue is the register address for chip lies in 0x5a80 range, so is 
the on-chip memory. If I set the qtd structs to on chip memory(internal sram), 
kernel paging error will occur. 

So I am at a loss of what I can. Please kindly advise.

Best regards,
CL
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: KVM - virtualization support

[Sengottuvelan S]

Hi All,

I have below architecture. I assume it does not support KVM. Please point
me somone what is exactly needed to support KVM support in my machine?

# egrep -c ' lm ' /proc/cpuinfo
2
# uname -m
x86_64
# uname -a
Linux ubuntu 2.6.32-24-generic #39-Ubuntu SMP Wed Jul 28 05:14:15 UTC 2010
x86_64 GNU/Linux
and

# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model  : 23
model name : Intel(R) Core(TM)2 Duo CPU E7200  @ 2.53GHz
stepping : 6
cpu MHz  : 1600.000
cache size : 3072 KB
physical id : 0
siblings : 2
core id  : 0
cpu cores : 2
apicid  : 0
initial apicid : 0
fpu  : yes
fpu_exception : yes
cpuid level : 10
wp  : yes
flags  : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
constant
_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl est
tm2
 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm
bogomips : 5054.10
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model  : 23
model name : Intel(R) Core(TM)2 Duo CPU E7200  @ 2.53GHz
stepping : 6
cpu MHz  : 1600.000
cache size : 3072 KB
physical id : 0
siblings : 2
core id  : 1
cpu cores : 2
apicid  : 1
initial apicid : 1
fpu  : yes
fpu_exception : yes
cpuid level : 10
wp  : yes
flags  : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
constant
_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl est
tm2
 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm
bogomips : 5054.00
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:


On Tue, Dec 21, 2010 at 5:57 AM, matthias  wrote:

> Hi,
>
> 2010/12/21 Sengottuvelan S :
> > Hi All,
> >
> > I am trying to see whether my kernel has KVM support or not. When i
> execute
> > #egrep -c '(vmx|svm)' /proc/cpuinfo  , output shows '0'' which means my
> > custom kernel does not have capability of KVM.
> >
> > How do i enable or support KVM in my new kernel. Is it possible or not?
>
> /proc/cpuinfo gives you information about your CPU and not about the
> modules your kernel support.
> If you don't have the right hardware, afaik you have to use a
> different hypervisor.
>
>
> Regards,
> Matthias
> --
> motzblog.wordpress.com
>
> ___
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>



-- 
Regards,
S. Sengottuvelan.
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Accessing PCI Memory Mapped Registers in Linux Kernel

[Daniel (Youngwhan) Song]

Hi Mulyadi,

On Tue, Dec 21, 2010 at 9:59 AM, Mulyadi Santosa
wrote:

> Hi Daniel.
>
> On Tue, Dec 21, 2010 at 16:04, YOUNGWHAN SONG  wrote:
> > test_foo = (struct foo*)regsva;
>
> I was thinking differently, could it be that casting...as shown
> above...introduce this behaviour? what if you just point to the
> address...directly without any "container" such as struct foo?
>
>
>
> printk(KERN_DBG "value TEST1: 0x%lx\n", readl(test_foo->TEST1));
> > printk(KERN_DBG "value 0: 0x%x\n", readw(&test_foo->a1[0]);
> > printk(KERN_DBG "value 1: 0x%x\n", readw(&test_foo->a1[1]);
>
> in the above statement, it means "take the address of a1[0 and read
> some bytes from that address", right?
>
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer and consultant
>
> blog: the-hydra.blogspot.com
> training: mulyaditraining.blogspot.com
>

As we've talked, it looks the code would be ok, but I guess architecture
doesn't handle the 16 bit address correctly. Our team will find a way to get
through this by modifying the PCI module.

Thanks, Mulaydi for this post.

Have a great day.

Daniel
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Problem with booting newly compiled kernel

[Prasad Joshi]

On Tue, Dec 21, 2010 at 8:43 PM, John Mahoney  wrote:
>>> b. Also, who generates these UUID - is it a disk property (like, ROM
>>> signature or stuff?), or this is some udev magic?
>>>
>>
>> IMHO, this is fixed for every device during manufacturing.
>>
>
> I believe the UUID is created per partition/file system and are
> created when creating the file system for a partition.  If anyone even
> had their drive changed from /dev/hda to /dev/sda due to linux
> changing how they labeled ide drives they will know why people use
> UUID instead of the device name .  Also, it is not guaranteed that
> they drives will always come up in the same order between kernel
> releases(This is my personal opinion).
>

I think you are correct, it is assigned when a file system is created.
It is a tunable parameter which can be chnaged using tune2fs -U
command.
A new UUID can be generated using command uuidgen.

> --
> John
>

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Problem with booting newly compiled kernel

[John Mahoney]

>> b. Also, who generates these UUID - is it a disk property (like, ROM
>> signature or stuff?), or this is some udev magic?
>>
>
> IMHO, this is fixed for every device during manufacturing.
>

I believe the UUID is created per partition/file system and are
created when creating the file system for a partition.  If anyone even
had their drive changed from /dev/hda to /dev/sda due to linux
changing how they labeled ide drives they will know why people use
UUID instead of the device name .  Also, it is not guaranteed that
they drives will always come up in the same order between kernel
releases(This is my personal opinion).

--
John

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Problem with booting newly compiled kernel

[Prasad Joshi]

On Tue, Dec 21, 2010 at 6:16 PM, Shreyansh Jain  wrote:
> Hi List,
>
> On Tue, Dec 21, 2010 at 7:22 PM, Prasad Joshi  
> wrote:
>> On Tue, Dec 21, 2010 at 1:37 AM, Alexandre Courbot  wrote:
        linux   /vmlinuz-2.6.37-rc6+
 root=UUID=01432597-18e7-4609-9f85-3fad1d762ddc ro iommu=1
>>>
>>> Try replacing root=UUID=01432597-18e7-4609-9f85-3fad1d762ddc by the
>>> simpler root=/dev/sdaX. I had similar problems some time ago - for
>>> some reason, my kernel did not like UUIDs.
>>
>> bravo Alexandre :)
>> It solved the problem. I am really thankful to you.
>>
>
> Sorry to hijack your thread, but I thought this is the most opportune
> time to ask my query.
>
> @Prasad Nice to know that this suggestion solved the issue. I too have
> found this issue very irritating but could never understand by UUID
> were not recognized (where as my distro kernel recognizes them very
> well).

The default kernel with Ubuntu 10.10 too recognized the UUID.

>
> a. Does any have any idea which component causes this issue. As to,
> what am I missing while compiling a new kernel that it doesn't
> recognize the UUID of a dev disk?

The function responsible for mounting the root file system is
prepare_namespace()

void __init prepare_namespace(void)
{

if (saved_root_name[0]) {
root_device_name = saved_root_name;
if (!strncmp(root_device_name, "mtd", 3) ||
!strncmp(root_device_name, "ubi", 3)) {
mount_block_root(root_device_name, root_mountflags);
goto out;
}
ROOT_DEV = name_to_dev_t(root_device_name);
if (strncmp(root_device_name, "/dev/", 5) == 0)
root_device_name += 5;
}

...
mount_root();
}

The function name_to_dev_t is responsible for finding out the correct
major and minor numbers for the root device. The function also works
on UUID. IMHO, the function is responsible for doing it is
devt_from_partuuid, though I did not look into the details.

>
> b. Also, who generates these UUID - is it a disk property (like, ROM
> signature or stuff?), or this is some udev magic?
>

IMHO, this is fixed for every device during manufacturing.

> Thanks to anyone who can provide any hint about this.
>
> -
> Shreyansh
>

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: KVM - virtualization support

[matthias]

Hi,

2010/12/21 Sengottuvelan S :
> Hi All,
>
> I am trying to see whether my kernel has KVM support or not. When i execute
> #egrep -c '(vmx|svm)' /proc/cpuinfo  , output shows '0'' which means my
> custom kernel does not have capability of KVM.
>
> How do i enable or support KVM in my new kernel. Is it possible or not?

/proc/cpuinfo gives you information about your CPU and not about the
modules your kernel support.
If you don't have the right hardware, afaik you have to use a
different hypervisor.


Regards,
Matthias
-- 
motzblog.wordpress.com

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Sound not coming after compiling new kernel 2.6.36

[Shreyansh Jain]

Hi Rishi,

On Tue, Dec 21, 2010 at 11:04 AM, Rajat Sharma  wrote:
> likely sound driver for Intel 82801G is not selected in your kernel config
> file. .config generated after you did make menuconfig.
>
> On Tue, Dec 21, 2010 at 10:11 AM, Rishi Agrawal 
> wrote:
>>
>> Hi All,
>>
>> I compiled the kernel 2.6.36 and now the sound is missing. I have pasted
>> the outputs of lsmod and lspci. I have fedora 12 installed on the system.
>>
>> Have I done something wrong in the menuconfig stage.
>>
>> Sound is coming properly with the old Fedora Kernel.
>>
>> I tried tweaking the alsamixer but it did not work.
>>
>>
>> [ri...@rishi-desktop ~]$ uname -a
>> Linux rishi-desktop 2.6.36 #1 SMP Sat Dec 18 21:24:34 IST 2010 i686 i686
>> i386 GNU/Linux
>>
>>
>>
>> [ri...@rishi-desktop ~]$ lspci | grep -i audio
>> 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High
>> Definition Audio Controller (rev 02)
>>
>> [ri...@rishi-desktop ~]$ lsmod | grep snd
>> snd_hda_codec_analog    53691  1
>> snd_hda_intel  20031  1
>> snd_hda_codec  73253  2 snd_hda_codec_analog,snd_hda_intel
>> snd_hwdep   4856  1 snd_hda_codec
>> snd_seq    42695  0
>> snd_seq_device  4937  1 snd_seq
>> snd_pcm    62570  2 snd_hda_intel,snd_hda_codec
>> snd_timer  15387  2 snd_seq,snd_pcm
>> snd    46823  11
>> snd_hda_codec_analog,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer,thinkpad_acpi
>> snd_page_alloc  6077  2 snd_hda_intel,snd_pcm
>> soundcore   4831  1 snd

Can you try re-compiling the kernel with SOUND_OSS_CORE (I don't
remember which option activates this flag)? Though I did not face this
issue in my current kernel config (2.6.36.1), but I remember that one
of my old box had a similar issue. It got resolved after I had enabled
some parameters for OSS (ironically, which seems to be deprecated in
current kernel !)

sh...@tiger-l:~/work/kernels/linux-2.6.36.1$ lsmod | grep snd
snd_hda_codec_intelhdmi10004  1
snd_hda_codec_realtek   222503  1
snd_hda_intel  21757  2
snd_hda_codec  88655  3
snd_hda_codec_intelhdmi,snd_hda_codec_realtek,snd_hda_intel
snd_hwdep   5424  1 snd_hda_codec
snd_pcm_oss34603  0
snd_mixer_oss  13718  1 snd_pcm_oss
snd_pcm71854  3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_dummy   1350  0
snd_seq_oss26310  0
snd_seq_midi4588  0
snd_rawmidi18980  1 snd_seq_midi
snd_seq_midi_event  6047  2 snd_seq_oss,snd_seq_midi
snd_seq46769  6
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer  18561  2 snd_pcm,snd_seq
snd_seq_device  5744  5
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd54427  16
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore   6492  1 snd
snd_page_alloc  7216  2 snd_hda_intel,snd_pcm

May be this can help.

[My crude suggestion, or I should say, hit-and-trial method !!]

-
Shreyansh

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Problem with booting newly compiled kernel

[Shreyansh Jain]

Hi List,

On Tue, Dec 21, 2010 at 7:22 PM, Prasad Joshi  wrote:
> On Tue, Dec 21, 2010 at 1:37 AM, Alexandre Courbot  wrote:
>>>        linux   /vmlinuz-2.6.37-rc6+
>>> root=UUID=01432597-18e7-4609-9f85-3fad1d762ddc ro iommu=1
>>
>> Try replacing root=UUID=01432597-18e7-4609-9f85-3fad1d762ddc by the
>> simpler root=/dev/sdaX. I had similar problems some time ago - for
>> some reason, my kernel did not like UUIDs.
>
> bravo Alexandre :)
> It solved the problem. I am really thankful to you.
>

Sorry to hijack your thread, but I thought this is the most opportune
time to ask my query.

@Prasad Nice to know that this suggestion solved the issue. I too have
found this issue very irritating but could never understand by UUID
were not recognized (where as my distro kernel recognizes them very
well).

a. Does any have any idea which component causes this issue. As to,
what am I missing while compiling a new kernel that it doesn't
recognize the UUID of a dev disk?

b. Also, who generates these UUID - is it a disk property (like, ROM
signature or stuff?), or this is some udev magic?

Thanks to anyone who can provide any hint about this.

-
Shreyansh

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: KVM - virtualization support

[Mohammed Gamal]

On Tue, Dec 21, 2010 at 8:49 AM, Sengottuvelan S
 wrote:
> Hi All,
>
> I am trying to see whether my kernel has KVM support or not. When i execute
> #egrep -c '(vmx|svm)' /proc/cpuinfo  , output shows '0'' which means my
> custom kernel does not have capability of KVM.
>
> How do i enable or support KVM in my new kernel. Is it possible or not?
>
> Please someone throw light on this.
>

This most likely means your processor doesn't support
hardware-assisted virtualization altogether.
What's your exact processor model?

> --
> Regards,
> S. Sengottuvelan.
>
> ___
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: KVM - virtualization support

[John Mahoney]

On Tue, Dec 21, 2010 at 1:49 AM, Sengottuvelan S
 wrote:
> Hi All,
>
> I am trying to see whether my kernel has KVM support or not. When i execute
> #egrep -c '(vmx|svm)' /proc/cpuinfo  , output shows '0'' which means my
> custom kernel does not have capability of KVM.
>

I think you are misunderstanding the flags in /proc/cpuinfo.  I
believe they represent which features the processor supports, not what
features the kernel supports.  Like Rajat said you may need to enable
the feature in your BIOS, but otherwise you may want to check the
datasheet for the processor.

feel free to paste the output of:

cat /proc/cpuinfo

If you do not have this feature you will have to use something such as
VirtualBox, of course there will be a performance penalty.

--
John

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Accessing PCI Memory Mapped Registers in Linux Kernel

[Mulyadi Santosa]

Hi Daniel.

On Tue, Dec 21, 2010 at 16:04, YOUNGWHAN SONG  wrote:
> test_foo = (struct foo*)regsva;

I was thinking differently, could it be that casting...as shown
above...introduce this behaviour? what if you just point to the
address...directly without any "container" such as struct foo?

> printk(KERN_DBG "value TEST1: 0x%lx\n", readl(test_foo->TEST1));
> printk(KERN_DBG "value 0: 0x%x\n", readw(&test_foo->a1[0]);
> printk(KERN_DBG "value 1: 0x%x\n", readw(&test_foo->a1[1]);

in the above statement, it means "take the address of a1[0 and read
some bytes from that address", right?

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: KVM - virtualization support

[hiren panchasara]

> How do i enable or support KVM in my new kernel. Is it possible or not?
>

I am not an expert here but this might be helpful?

http://www.linux-kvm.org/page/FAQ#What_do_I_need_to_use_KVM.3F

Thanks,
Hiren
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Suggestion for the LISTDOMAIN

[Michelle Konzack]

Hello * and owners of ,

since I am  ISP  I  am  runing  into  troubles  with  spam  coming  from
listservers or faked Froms: I suggest you to

   CHANGE the LISTDOMAIN from

   kernelnewbies.org
   to
   lists.kernelnewbies.org

which makes spamfiltering much easier.

Thanks, Greetings and nice Day/Evening
Michelle Konzack

-- 
# Debian GNU/Linux Consultant ##
   Development of Intranet and Embedded Systems with Debian GNU/Linux

itsyst...@tdnet France EURL   itsyst...@tdnet UG (limited liability)
Owner Michelle KonzackOwner Michelle Konzack

Apt. 917 (homeoffice)
50, rue de Soultz Kinzigstraße 17
67100 Strasbourg/France   77694 Kehl/Germany
Tel: +33-6-61925193 mobil Tel: +49-177-9351947 mobil
Tel: +33-9-52705884 fix

  
 

Jabber linux4miche...@jabber.ccc.de

Linux-User #280138 with the Linux Counter, http://counter.li.org/


signature.pgp
Description: Digital signature
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: KVM - virtualization support

[Rajat Sharma]

sadly... yes!

On Tue, Dec 21, 2010 at 4:08 PM, Prasad Joshi wrote:

> On Tue, Dec 21, 2010 at 6:49 AM, Sengottuvelan S
>  wrote:
> > Hi All,
> >
> > I am trying to see whether my kernel has KVM support or not. When i
> execute
> > #egrep -c '(vmx|svm)' /proc/cpuinfo  , output shows '0'' which means my
> > custom kernel does not have capability of KVM.
> >
>
> It means the hardware does not have virtualization support.
>
> > How do i enable or support KVM in my new kernel. Is it possible or not?
> >
> > Please someone throw light on this.
> >
> > --
> > Regards,
> > S. Sengottuvelan.
> >
> > ___
> > Kernelnewbies mailing list
> > Kernelnewbies@kernelnewbies.org
> > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> >
> >
>
> ___
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Problem with booting newly compiled kernel

[Prasad Joshi]

On Tue, Dec 21, 2010 at 1:37 AM, Alexandre Courbot  wrote:
>>        linux   /vmlinuz-2.6.37-rc6+
>> root=UUID=01432597-18e7-4609-9f85-3fad1d762ddc ro iommu=1
>
> Try replacing root=UUID=01432597-18e7-4609-9f85-3fad1d762ddc by the
> simpler root=/dev/sdaX. I had similar problems some time ago - for
> some reason, my kernel did not like UUIDs.

bravo Alexandre :)
It solved the problem. I am really thankful to you.

>
> Alex.
>

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: KVM - virtualization support

[Prasad Joshi]

On Tue, Dec 21, 2010 at 6:49 AM, Sengottuvelan S
 wrote:
> Hi All,
>
> I am trying to see whether my kernel has KVM support or not. When i execute
> #egrep -c '(vmx|svm)' /proc/cpuinfo  , output shows '0'' which means my
> custom kernel does not have capability of KVM.
>

It means the hardware does not have virtualization support.

> How do i enable or support KVM in my new kernel. Is it possible or not?
>
> Please someone throw light on this.
>
> --
> Regards,
> S. Sengottuvelan.
>
> ___
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: KVM - virtualization support

[Mohammed Gamal]

On Tue, Dec 21, 2010 at 11:22 AM, Rajat Sharma  wrote:
> you can turn it on in BIOS, if your CPU supports virtualization. Look for VT
> extention or Virtualization under CPU section of your BIOS.
>
> Rajat
>
If the CPU doesn't have vmx or svm flags to begin with, then it most
likely does not support hardware virtualization.

> On Tue, Dec 21, 2010 at 12:19 PM, Sengottuvelan S
>  wrote:
>>
>> Hi All,
>>
>> I am trying to see whether my kernel has KVM support or not. When i
>> execute
>> #egrep -c '(vmx|svm)' /proc/cpuinfo  , output shows '0'' which means my
>> custom kernel does not have capability of KVM.
>>
>> How do i enable or support KVM in my new kernel. Is it possible or not?
>>
>> Please someone throw light on this.
>>
>> --
>> Regards,
>> S. Sengottuvelan.
>>
>> ___
>> Kernelnewbies mailing list
>> Kernelnewbies@kernelnewbies.org
>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>
>
>
> ___
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: KVM - virtualization support

[Rajat Sharma]

you can turn it on in BIOS, if your CPU supports virtualization. Look for VT
extention or Virtualization under CPU section of your BIOS.

Rajat

On Tue, Dec 21, 2010 at 12:19 PM, Sengottuvelan S  wrote:

> Hi All,
>
> I am trying to see whether my kernel has KVM support or not. When i execute
>
> #egrep -c '(vmx|svm)' /proc/cpuinfo  , output shows '0'' which means my
> custom kernel does not have capability of KVM.
>
> How do i enable or support KVM in my new kernel. Is it possible or not?
>
> Please someone throw light on this.
>
> --
> Regards,
> S. Sengottuvelan.
>
> ___
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies