/srv/irclogs.ubuntu.com/2009/09/22/#ubuntu-kernel.txt

=== TheMuso` is now known as TheMuso
=== doko_ is now known as doko
valkyrhi12:53
valkyrCorrect me if Im wrong .. but 32bit Linux systems are also limited to under 4gb of ram right?  To increase limit one has to either upgrade to a 64bit version or update the kernel with a PAE aware kernel.  Would you all agree?12:53
domasright12:54
valkyrthanks12:54
domas(PAE kernel doesn't allow you to address all memory in application though )12:54
valkyrin which case what do i do?12:56
valkyrthere's no other choice here but to use PAE or just upgrade right12:56
domasyou use 64 bits12:57
domas;-)12:57
valkyrheh alright12:58
domaswindows have AWE, which allows applications to address larger areas, but I have no idea how it works ;-)12:58
valkyrthanks :))12:58
valkyrwell we won't have no use for windows here12:58
domasthere's specific API 12:58
valkyrdomas: going back to what you said12:58
valkyrin a single process is what oyu mean right?12:58
domasyes12:58
valkyrok12:59
domas(I'm working with multiple software pieces that loves memory ;-)12:59
valkyrs0 same  limitation per process as you have system-wide with a non-PAE kernel?12:59
domasactually, with non-PAE kernel you can allocate ~100MB more of memory ;-)13:00
domasor maybe not13:00
domas32-bit linux gives you about 2.7G per app13:00
domasand maximum contiguous allocation can be less (close to 2G)13:00
valkyrthey say that PAE slows the system down somewhat, but I've never heard any XP user complain about it. 13:00
domasif PAE would slow the system down, ubuntu-server kernels (all with PAE) would not be that usable, right?13:00
domasmaybe using memory via AWE is slower than directly, I don't know ;-)13:01
valkyrok you're not a kernel dev?13:01
valkyr:P13:01
domasI do some development for myself sometimes ;-) 13:01
valkyrXP switched to a PAE kernel with SP2. They still limit the memory in order to not confuse drivers. 13:01
valkyrso I don't know how big the difference in performance can be in practice.13:01
domasI doubt there is any13:02
valkyrok13:03
domas1%13:04
domas;-)13:04
valkyr1%?13:04
valkyryu checked?13:04
* domas points at http://people.redhat.com/nmurray/RHEL-2.1-VM-whitepaper.pdf13:05
domas"The performance impact is highly workload dependent, but on a fairly typical ker- 13:05
domasnel compile, the PAE penalty works out to be around a 1% performance hit on Red 13:05
domasHat?s test boxes. Testing withhits ranging from 0% to 10%"13:05
domasdamn pdf copypaste13:05
domasmangled the text ;-)13:05
valkyrah13:05
valkyrcould get a second opinion on this from one of the devs too 13:05
valkyrthanks for the link13:05
domasI prefer x86_64 ;-)13:07
valkyrso using memory via AWE is slower?13:09
valkyrdomas so with non-PAE you can allocate more than 1--mb13:18
valkyr100mb13:18
valkyrcant see it in the link though13:18
domasnoooo13:19
domaswith PAE kernel you can allocate ~2.7G13:19
domaswith non-PAE it is closer to 2.8G13:19
domas;-)13:19
valkyr/<domas> actually, with non-PAE kernel you can allocate ~100MB more of memory ;-)13:19
domas'more'13:19
valkyrohh13:19
valkyrso with a non-PAE kernel you dont have that many limitations to a PAE kernel?13:20
domaswell, it is just small difference13:20
valkyrbut per process, they're both limited equally13:21
valkyrnon-pae and PAE right?13:21
domasnono, I'm talking exactly about per-process13:21
domasPAE kernel can allocate much more overall13:21
valkyri dont gain anything more from using a non-PAE here do i 13:21
domasnope13:21
valkyrok13:22
valkyrthx domas14:15
Kanohi, i just looked at your linux-firmware package, a few files could be added15:31
Kanoyou have got only 2 of 3 possible firmware files for ar9170, the correct one for AVM Wlan N sticks is missing15:32
Kanohttp://www.kernel.org/pub/linux/kernel/people/mcgrof/firmware/ar9170/LICENSE15:33
Kanohttp://www.kernel.org/pub/linux/kernel/people/mcgrof/firmware/ar9170/ar9170.fw15:33
Kanoalso for your other non-free package15:33
Kanothere you could add xc3028-v27.fw as dvb firmware15:34
Kanoand dont say there is no bug...15:36
Kanohttps://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/27865615:36
ubot3Malone bug 278656 in linux-firmware "Missing firmware for em28xx DVB-T digital tuner" [Wishlist,Triaged] 15:36
Kanohttp://linuxwireless.org/en/users/Drivers/ar917015:39
Kanothe one stage part15:39
tormodKano: please add your information to the report if is relevant15:41
Kanothe 2nd bug is definitely clear ot not15:41
Kanowill add the url to the files to another bug15:41
Kanohttps://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/38640315:44
ubot3Malone bug 386403 in linux-firmware "ar9170 wireless firmware needed in Karmic" [Undecided,Fix released] 15:44
=== hggdh|afk is now known as hggdh
setuidHow do I ensure that the same initramfs/initrd that is used to successfully boot a 2.6.28-5 kernel on Jaunty, is used to generate a working 2.6.28-15 version? 18:47
setuidbecause 2.6.28-15 is unbootable18:48
setuidWhat is it that governs what modules/etc. are included in an initramfs? 19:32
setuidBecause I can't seem to generate one for 2.6.28-15-generic that models the same modules/support that is included in the default 2.6.28-5 that I'm using right now. 19:32
jk-hey setuid19:32
setuidhola19:32
jk-setuid: /etc/initramfs-tools/modules ?19:33
setuidOk, so when I run: update-initramfs.distrib -c -k 2.6.28-15-generic19:34
setuidIt should generate a working one... but doesn't19:35
setuidI get a hard-lock, when it tries to mount the root volume, using a UUID (the same construct that works with 2.6.28-5) 19:35
setuidSo any ideas? 19:46
=== mdomsch is now known as mdomsch_linuxcon
tormodwhy are there no daily builds in the mainline kernel-ppa?22:15

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