/srv/irclogs.ubuntu.com/2008/04/28/#ubuntu-kernel.txt

osmosiscould be this.. https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/11353200:02
ubotuLaunchpad bug 113532 in linux-source-2.6.20 "kernel 2.6.20 disk write performance much slower than 2.6.17" [Undecided,Confirmed] 00:02
osmosisyah, looks like that bug has stuck around.00:07
osmosisWhen I use dd to create a 1G, my system comes to a hault. Should disk IO really send my load average up to 50?02:09
=== gnomefre1k is now known as gnomefreak
=== thegodfather is now known as fabbione
krautmoin08:25
ackrcvdHi, I need to recompile the b43 driver in a default installation of 8.04... Do I need to recompile the entire kernel or just the b43 module?12:33
ackrcvdNo one knows?12:54
alex_joniI would try recompiling the module only13:03
ackrcvdHow would I go about doing that?13:12
ackrcvdI assume I only need linux-headers for this?13:12
ackrcvdHow do I get the sources for the module... /lib/modules/2.6.24-16-generic/kernel/drivers/net/wireless/b43/b43.ko is the module I'm trying to recompile13:13
alex_joniackrcvd: why do you need to recompile it?13:14
ackrcvdApplying patches suggeted to work with aircrack-ng suite13:15
alex_joniackrcvd: you need to get the source from somewhere.. so probably apt-get source linux-image-2.6.24-16-generic 13:16
alex_jonibut it won't be a trivial thing to do13:16
ackrcvdSo I would be required to rebuild the entire kernel?13:17
alex_joniprobably13:17
alex_jonibut you'll only use the module13:17
ackrcvdWhat I wanted to know was, If I had to follow the instructions on https://help.ubuntu.com/community/Kernel/Compile OR I could just recompile the b43 module13:17
alex_joniif you can get the exact same source, and can compile only the module, then that would probably be fine13:18
alex_joni(but I have no idea how you could/should do that)13:18
ackrcvdalex_joni: Cool... Thanks13:19
aboganialex_joni: How proceed your work about Ubuntu rtai kernel flavour?13:34
alex_joniabogani: pretty good :)13:36
alex_joniabogani: managed to build packages, put them in a repo, and built a live cd13:36
aboganialex_joni: Do you have plan to push your work in Ubuntu?13:37
alex_joniabogani: hmm.. didn't think about it13:39
alex_joniabogani: would it be usefull?13:41
alex_joni(gotta run to lunch for 30min, will be back though)13:41
aboganiOh Yes.13:41
aboganialex_joni: Anyway i hope to add Comedi into lum for Intrepid Ibex. I suppose that is a news for you. :-)13:41
aboganiGood lunch!13:41
abogani:-)13:41
alex_joniabogani: cool, let me know if I can help13:41
aboganiOk13:41
alex_joniabogani: so far we tried to stick with LTS's13:42
=== asac_ is now known as asac
alex_joniabogani: back14:16
=== ogasawara__ is now known as ogasawara
=== gnomefre1k is now known as gnomefreak
=== gnomefre1k is now known as gnomefreak
=== gnomefre1k is now known as gnomefreak
r1ddl3rHello, i'm trying to make a developing tool for programming the 8051 series of microcontrollers, since i dont have deep knowledge on Linux is there any1 willing to answer some questions?? (Or i'm on the wrong channel again?? )19:52
r1ddl3rlol dont swarm me with answers ppl, rofl19:55
r1ddl3roke imma let ya to yer jobs...19:55
mkrufkyrtg: bug # 220857 marked as no-fix will make Ubuntu no longer the distro of choice for v4l / dvb developers20:19
mkrufkyand the bot doesnt notice... again... bug 22085720:20
ubotuLaunchpad bug 220857 in linux-ubuntu-modules-2.6.24 "linuxtv.org mercurial repository wont build against hardy kernel due to "disagrees about version of symbol videobuf_*" [Low,Won't fix] https://launchpad.net/bugs/22085720:20
mkrufkythis is because ubuntu has copies of cx88 and saa7134 in the ubuntu/media tree, causing conflicts20:20
rtgmkrufky: the media modules are built against the ALSA headers in LUM, not against the kernel.20:21
mkrufkywhy cant you place them in drivers/media ??20:22
mkrufkythat would avoid this issue20:22
rtgmkrufky: they are direct copies of the kernel sources from drivers/media. They have to be built outside the kernel environment in order to get the correct ALSA headers. 20:23
mkrufkyok, but users will continue to attempt to get driver support for new devices using linuxtv.org sources, and after they install the sources and modprobe the new modules, the wrong versions are picked up20:24
mkrufkyusers dont know that thety have to delete the ubuntu versions first20:25
mkrufkyand we cant script that into the v4l/dvb build system, because we build on all distros -- we're not ubuntu-specific20:25
rtgmkrufky: how about developing DKMS packages that use the kernel Makefile ? We have patches in that makefile that enforce the header file inclusion order.20:26
mkrufkyim not familiar with DKMS packages20:27
rtgmkrufky: mdomsch from Dell developed it (or is the current maintainer)20:27
mdomschgood day20:27
mkrufkythe linuxtv.org repositories are where v4l/dvb devel goes on for upstream kernels, and we put forth a ton of effort such that the tree is backwards compatable with older kernels, so that users can get driver support for new hardware on distro kernels20:28
mkrufkyrtg: it doesnt do me any good to develop a DKMS package if i have to update it every day, rtg20:28
rtgmkrufky: we have somewhat the same problems, e.g., how to backport ALSA without borking external ALSA dependent drivers.20:28
mdomschmkrufky, http://linux.dell.com/dkms/dkms.html  if you're interested20:29
mkrufkypeople that are building their new v4l / dvb modules can build those modules against the LUM headers, if they like20:30
mkrufkythen they can use the new drivers and it will work with new alsa20:30
mkrufkythats no big deal20:30
mkrufkythe problem is, they dont even have this option with the current situation20:30
rtgmkrufky: I'm not sure what you're trying to tell me, but follow up with smb (who is online and did the work). I gotta take off.20:31
mkrufkyDKMS looks nice, but linuxtv.org has its own backwards-compat solution, this is not needed for us20:32
mkrufkysmb?20:32
smbme20:32
mkrufkyok, ttyl, rtg20:32
mkrufkyoh, hi, smb20:33
tseliotmkrufky: why did you say that you would have to update a DKMS package every day?20:33
mkrufkyas i was saying.  bug 220857 marked as no-fix will make Ubuntu no longer the distro of choice for v4l / dvb developers20:33
ubotuLaunchpad bug 220857 in linux-ubuntu-modules-2.6.24 "linuxtv.org mercurial repository wont build against hardy kernel due to "disagrees about version of symbol videobuf_*" [Low,Won't fix] https://launchpad.net/bugs/22085720:33
smbmkrufky: Hi. I looked into that when we had problems with the cx88 and saa71.. driver. 20:33
mkrufkytseliot: i represent the v4l / dvb kernel developers20:34
mkrufkytseliot: with digital television cards, distro kernels NEVER have support for the cards being sold today20:34
smbmkrufky: I followed just loosely. let me have a skip through the baglog20:34
mkrufkytseliot: so users must upgrade to the new drivers in the repositories hosted on linuxtv.org20:34
mkrufkyok, smb20:34
mdomschmkrufky, DKMS exists exactly because each project had its own backport solution; each different; many broken.20:36
mdomschDKMS is the underpinning of the work of the Linux Foundation Driver Backport Working Group20:36
mkrufkymdomsch: i, as a developer, need to run my developer sources on ubuntu20:36
mkrufkyi must not run a package20:37
mdomschand is required for all kernel modules Dell ships that aren't already on the distro media20:37
mkrufkyi need to run the sources WITH the bugs20:37
mkrufkyso that i can fix those bugs20:37
mdomschsure...20:37
mdomschDKMS can produce packages (debs, rpms, etc) but that's not it's core usefulness20:37
tseliotmkrufky: once you've set up the packaging scripts for DKMS you can create a script which replaces all the files with their updated versions and builds a new package (a shell script would be enough)20:38
mkrufkyyou are approaching this problem from a "how do we support the users" POV20:38
mkrufkybut i am raising a different issue20:38
mkrufkyi am raising, "how do we support the developers" POV20:38
smbmkrufky: The problem we faced was the need of a more recent ALSA driver to support newer cards. So ALSA was moved into lum to be independent. Unfortunately this raises problems for drivers that are to be compiled agains alsa headers.20:38
mdomschyes20:38
mkrufkyusers, yes -- would be nice if somebody would make a DKMS package for v4l/dvb modules, regularly20:38
mkrufkybut that doesnt help me20:38
mdomschdkms lets you have lots of versions of the source of a module20:39
mdomsche.g. /usr/src/somemodule-version120:39
mdomsch-version220:39
mdomsch-version320:39
mdomschand track what's installed20:39
mdomschI use it for development all the time20:39
mkrufkywill somebody volunteer to maintain these such packages for ubuntu users that require the latest v4l-dvb modules?20:41
smbmkrufky: What the v4l-dvb modules would need is, optionally look into lum headers first. I know this would then be ubuntu specific but once in place would need no specific maintenance20:44
mkrufkyplease see the launchpad bug report -- LUM headers are missing things in the linux-headers and the source tree wont build against LUM, alone20:44
mkrufkyto make a long story short -- i work for a company that makes these tv products, and am slowly converting my co-workers into linux users / linux developers.  in the past, i can give them an ubuntu cd, tell them to pull from my linuxtv tree and build it.  now, its not that simple any more, and it's easier for me to give them a fedora cd20:49
smbmkrufky: Yes the "right" headers are the linux-headers-lum-* ones. These have to be installed and the include path must use them before the kernel headers20:49
mkrufkyisnt there a way to look in ubuntu/media/foo *after* not finding said module in the standard kernel first?20:50
smbmkrufky: It is not only the problem of the modules. Since ALSA is in the kernel but not always the most current. It cannot be simply overridden by replacing the modules. As you experienced all external modules will try to use the kernel headers. Which do not necessarily match20:53
mkrufkyi see it as important that the "default" kernel have all modules working correctly20:53
mkrufkybut once i build my own v4l / dvb modules from source, i deserve for alsa to be broken20:54
mkrufkyand that is my fault, not ubuntu's20:54
mkrufkythe fact is, i dont even have that opportunity, now20:54
mkrufky(without first removing those from ubuntu/media/foo)20:54
mkrufkyand users wont know how to do it ...20:54
mkrufkynow, if a user goes to build his own v4l/dvb modules, that user probably doesnt need alsa to work20:55
mkrufkyif that user needs alsa to work, then that user has to simply wait for the next ubuntu kernel20:55
smbmkrufky: I see your point. But we also saw with the cx88 driver (as an example). That this requires alsa to work and produces quite awful problems when compiled against the kernel. So it might only partially help if those modules would sit somewhere else20:57
mkrufkyit only requires alsa if the user needs DMA audio in analog mode20:57
mkrufkyone can simply not use cx88-alsa20:58
mkrufky(it is blacklisted on my system)20:58
mkrufkycx88-alsa is a separate module, for exactly this reason20:58
mkrufkysame goes for saa7134-alsa20:58
smbmkrufky: This might be true, but I had several users that required this and had unusable systems because of problems there. I agree the current situation is not good. The problem is to find a solution that is good for all.21:01
mkrufky^^ the default installation should be a solution that is good for all21:02
mkrufkyand we dont disagree, there21:02
mkrufkyhowever......21:02
mkrufkyto fix this properly, you should do the following:21:03
mkrufkyhave cx88-alsa and saa7134-alsa disabled in the kernel build21:03
smbmkrufky: should be21:03
mkrufkyin the LUM build, you build cx88-alsa and saa7134-alsa against the LUM alsa headers, using the cx88 and saa7134 headers from the kernel21:03
mkrufkybut build the base cx88 and saa7134 modules WITH the kernel21:03
smbmkrufky: Ok. I see the point.21:04
mkrufkyi dont see why cx88xx cx8800 cx8802 and cx88-dvb are not built in-kernel21:05
smbmkrufky: So the video modules could be simply replaced when compiling externally21:05
mkrufkysame applies to saa7134 and saa7134-dvb21:05
mkrufkyyes, that is correct21:05
mkrufkythey depend, of course, on the v4l and dvb core dependencies21:05
mkrufkysuch as videobuf-foo , dvb-core, and any tuner / demod i2c client / dvb_frontend modules, etc21:06
smbmkrufky: The question is there: does this include anything sound related?21:06
mkrufkythe sound modules in question are cx88-alsa and saa7134-alsa21:07
mkrufkythose can be built outside21:07
mkrufkythe cx88 & saa713x drivers themselves do not depend on any sound stuff21:07
smbmkrufky: No, sorry. I meant the v4l dependencies. And I think this might have been a reson to move the whole drivers. It might have been not that clear.21:08
mkrufkyah21:08
mkrufkyi try to make myself accessible to you guys -- you should please always feel free to email me with those types of questions21:09
mkrufkyand i am not always as difficult as i am being today :-P21:09
smbmkrufky: Ok, I/we surely come back to that offer. ;-)21:09
mkrufkyanyway, v4l has absolutely zero dependency on alsa21:09
mkrufkyok, cool :-)21:10
mkrufkydvb also -- zero dependency on alsa21:10
pwnguini got a question about building upstream kernel git21:11
TankEnMatewhat is the major differences between a -server and a -generic kernel?21:11
pwnguinWarn for stack frames larger than (needs gcc 4.4) (FRAME_WARN) [1024] (NEW) ?21:11
pwnguini appear to have gcc 4.2 -- do i need to set that to 0?21:12
smbmkrufky: Ok, I take that point and see what can be done. But at least I think I understood the problem and see whether this can be changed21:12
TankEnMate*shrug* read the source luke! :)21:12
mkrufkysmb: ok, cool...  21:13
pwnguinTankEnMate: last i knew there wasnt much of a difference; you could try making a diff of the two ^_^21:13
mkrufkysmb: thank you -- i appreciate looking into this...  and so will the other v4l/dvb developers, and all my co workers ;-)21:13
TankEnMatepwnguin: tried that.. problem i am having doesn't seem to be related to an config changes that I could see..21:15
smbmkrufky: I hope we can get a solution that is good for everyone (well maybe most ;-)) which is what we all want in the end.21:15
mkrufkyyes, exactly21:15
TankEnMatepwnguin: only thing I can think is that the source code must be different...21:15
TankEnMateanyone here ever come across a kernel complaining about a initrd image is bad, when you know for certain that it is ok?21:16
smbpwnguin: I am guessing a bit there but it might be a compile option. Maybe something gcc4.2 just ignores. Or the makefiles just make sure it isn't used when using an oldr compiler. anyhow, if it compiles, I guess it should be ok21:18
FooEnMateugh..21:26
FooEnMateanyone had a problem with a kernel complaining that an initrd image was corrupt when you know for certain that it is ok?21:27

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!