/srv/irclogs.ubuntu.com/2007/05/29/#ubuntu-kernel.txt

defendguinst3: is fstab still used or is there a better way to make sure that a partition is always mounted at a certain place?12:20
=== zul_ [n=chuck@CPE0006258ec6c1-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-kernel
=== zul [n=chuck@CPE0006258ec6c1-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-kernel
TheMusoc12:37
TheMusough12:37
=== cjwatson_ [n=cjwatson@82-69-40-219.dsl.in-addr.zen.co.uk] has joined #ubuntu-kernel
=== jml [n=jml@121.44.221.16] has joined #ubuntu-kernel
=== kkubasik [n=kkubasik@pool-71-178-228-226.washdc.fios.verizon.net] has joined #ubuntu-kernel
=== blenderhead001 [n=blenderh@adsl-068-209-133-121.sip.jax.bellsouth.net] has joined #ubuntu-kernel
=== jml [n=jml@121.44.221.16] has joined #ubuntu-kernel
st3defendguin, well, i don't see any reason for not using fstab01:31
defendguinfor some reason i kept thinking there were more high level ways i could manage that procedure01:32
defendguini thought it could be handled by the gnome partition editor but i was mistaken01:33
st3don't choose high level when low level is human readable and just works :)01:40
defendguinst3: well i could add a new user manually but it is better not to because if i do he won't appear in the user picker in gdm and i can't manage his rights with any high level tool01:41
=== lfittl [n=lfittl@213.129.230.12] has joined #ubuntu-kernel
st3well, that's a gdm fault02:02
defendguinyeah02:02
st3i usually don't use X, so no idea :)02:03
defendguinyou would think gdm and the gdm config tool would know better02:03
defendguinmust stink to browse the web without x02:03
defendguinand your missing out on all the wobbly windows02:04
st3i didn't say i never use X, i usually don't02:07
st3well, my graphics card isn't as powerful as needed for displaying wobbly windows :)02:07
=== holycow [n=hello@mail.wjsgroup.com] has joined #ubuntu-kernel
holycowhey guys02:48
holycowi'm looking at buying this device and puttinhg ubuntu on it:02:48
holycowhttp://www.dynamism.com/u8240/main.shtml02:48
holycowit has a Intel Pentium A110 800MHz02:49
holycowcan anyone comment on kernel support for the cpu in any regard?02:49
holycowi'm willing to be a guinea pig if any kernel devs need that as a testing platform02:49
holycowthe chipset is right tho so it should be allright02:50
mjg59Should be nothing special about the kernel at all02:54
holycowjust reading more on that cpu as i've never heard about it, just looks like lower clocked pentium m cpus02:54
holycowso indeed02:54
holycowmjg59, thanks for the heads up, i'll do a writeup when i get the device on the installation process03:00
defendguinhey mjg59   this person found a work around for this bug but what needs to be done to fix this for gutsy?   https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/8682003:06
=== johanbr [n=j@blk-224-156-151.eastlink.ca] has joined #ubuntu-kernel
=== AvengerMoJo [n=alex@61.14.130.201] has joined #ubuntu-kernel
mjg59defendguin: Should already be fixed in gutsy, I believe03:57
defendguinwould it work to test that with a liveCD?04:01
mjg59Once they exist, yeah04:02
defendguinfair enough.  Thanks04:02
=== infinity2 [n=adconrad@cerberus.0c3.net] has joined #ubuntu-kernel
=== AvengerMoJ1 [n=alex@61.14.130.209] has joined #ubuntu-kernel
=== bleinmono [n=toffel@ppp91-76-72-62.pppoe.mtu-net.ru] has joined #ubuntu-kernel
=== pwnguin [n=jld5445@camaro.cis.ksu.edu] has joined #ubuntu-kernel
pwnguinstrange question: what's the "right" way to bring a newer kernel into a feisty install?06:04
crimsun#ubuntu question.  I'll address it there.06:05
pwnguini already asked it twice in there, but okay06:05
=== pwnguin [n=jld5445@camaro.cis.ksu.edu] has left #ubuntu-kernel []
=== m0rg0th [n=m0rg0th@220.225.228.97] has joined #ubuntu-kernel
=== infinity [n=adconrad@cerberus.0c3.net] has joined #ubuntu-kernel
=== m0rg0th_ [n=m0rg0th@220.225.228.97] has joined #ubuntu-kernel
=== n2diy [n=darryl@ppp-42d429ae.wlks.losch.net] has joined #ubuntu-kernel
=== abogani [n=alessio@adsl203-157-083.mclink.it] has joined #ubuntu-kernel
=== Lure [n=lure@ubuntu/member/lure] has joined #ubuntu-kernel
=== abogani [n=alessio@adsl203-157-083.mclink.it] has joined #ubuntu-kernel
=== infinity2 [n=adconrad@cerberus.0c3.net] has joined #ubuntu-kernel
=== koresko [n=koresko@128.171.100.1] has joined #ubuntu-kernel
koreskoI'm looking for a kernel that can see 1 GB of RAM on x86.  Generic sees about 750M.08:58
koreskoIs it necessary to recompile the kernel? Hopefully not - 1 GB is the memory size of about half the laptops I saw when shopping for this one a few days ago.08:59
Mithrandir-generic sees 1.5GB for me on i38608:59
crimsunwhat Mithrandir said.08:59
Mithrandirat least the kernel from 7.0409:00
MithrandirI am fairly sure at least 6.10 and 6.06 did the same.09:00
crimsunI just verified on 2.6.20-16-generic and 2.6.22-5-generic09:00
koreskoHm, I wonder if I have a bad BIOS setting or something.  Should I try mem=1024M on the commandline?09:01
koreskoThis is with the very latest Feisty kernel, running on a Turion64 laptop (Acer Aspire 5100).09:01
Mithrandirsounds weird.  Check that the machine sees all the memory in the bios?09:02
koreskoHm, good point.  I will have to reboot but will do that.09:02
koreskoHang on, rebooting... should be back in 5 minutes.09:04
=== koresko [n=koresko@128.171.100.1] has joined #ubuntu-kernel
koreskoAh, OK, I made a bonehead mistake!09:11
koreskoThe problem was that the BIOS had allocated 256 MB to the onboard video card.  I reduced it to 64 MB, and now the kernel sees 969 MB.09:12
koreskoI was confused because when I upgraded my desktop box from 0.5 to 1.0 GB I needed to rebuild the kernel with the high memory option enabled, else it only saw about 750 MB of memory. 09:12
koreskoThat was under Gentoo.09:13
Mithrandirmakes sense, then09:13
koreskoI was afraid I was going to have to maintain my own kernel... the reason I'm running Ubuntu instead of Gentoo on this machine is mostly to do with the fact that it doesn't need as much effort to maintain it.09:14
koreskoAnyway, thanks for confirming that it was *supposed* to work - else I'd probably have built my own kernel and still been stuck.09:16
koreskoBut now I realize that I don't get any benefit from having 3.5 GB of swap, since the virtual is limited to 4 GB, right?09:17
=== unhappy [n=justinas@85.206.151.78] has joined #ubuntu-kernel
=== abogani [n=alessio@adsl203-157-083.mclink.it] has joined #ubuntu-kernel
=== anibal [n=anibal@debian/developer/anibal] has joined #ubuntu-kernel
=== cbx33 [i=c2df514b@ubuntu/member/cbx33] has joined #ubuntu-kernel
cbx33hi guys....09:37
cbx33I'm getting this error09:37
cbx33runaway loop modprobe binfmt-464c09:37
cbx33but not all the time09:37
cbx33just occasionally09:37
cbx33i saw on some threads it could be because I'm running 32 bit on 64 arch?09:38
cbx33but this machine has happily ran through dapper and edgy and normally feisty09:38
cbx33I sometimes get an error about pnpbios failing09:38
cbx33and that's usually the start of the problems09:39
cbx33anyone got any ideaS?09:39
=== cassidy [n=cassidy@host-85-27-113-187.brutele.be] has joined #ubuntu-kernel
=== Keybuk [n=scott@quest.netsplit.com] has joined #ubuntu-kernel
cbx33hmmm09:52
=== ivoks [n=ivoks@32-246.dsl.iskon.hr] has joined #ubuntu-kernel
cbx33could have been a dodgy ram chip09:52
st3koresko, no, it's not limited to 4G11:03
koreskost3: Really? Even on x86?  11:03
st3my kernel configuration:11:04
st3CONFIG_HIGHMEM4G=y11:04
st3# CONFIG_HIGHMEM64G is not set11:04
st3Mem:   1018228k total,   776696k used,   241532k free,        0k buffers11:04
st3Swap:  4882724k total,   273164k used,  4609560k free,   280560k cached11:04
koreskoHm, interesting point.  But 32 bits can only address 4G, right?11:05
koreskoOr are you running a 64-bit kernel?11:05
st3i'm running a 32 bit kernel on an old 32 bit processor11:05
crimsunPentium Pros and newer support PAE.11:05
st3right11:06
koreskoI see.11:06
koreskoCan you actually use more than 4G of virtual?11:06
st3(no need for PAE to have large swap, though)11:06
st3sure11:06
koreskoI don't understand how it is addressed... Oh, maybe there is a 4G limit per process and the kernel swaps things around to make that work.11:07
st3no, that's entirely kernel managed of course11:07
koreskoOK, but then what is the point of 64 bits?11:08
mjg59You can't have more than 4GB of virtual on x86, no11:08
koreskomjg59: Hm, so how is is that st3's machine is showing nearly 5G?11:09
koreskoI am completely confused now.11:09
st3bahaha, do you want me to allocate them all?11:10
koreskost3: I was wondering what would happen if you tried that.11:11
st3wait11:11
mjg59PAE lets you have more than 4GB of physical space11:11
mjg59But per-process, you're still limited to 4GB11:12
mjg59(Well, 3 really)11:12
koreskoAh, I thought it might be something like that.11:12
koreskoWell, the biggest program I run routinely uses about 900M, so I'm covered!11:13
st3ok, i'm almost done...11:19
koreskoI'm going to bed.  Pretty late here.11:20
st3i'm allocating 4294967297 bytes (note the final 7)11:20
koreskoThanks for your help!11:20
koreskoHm, why that specific number of bytes?11:20
st3it's 2^32+111:21
koreskoAh, I see!11:21
koreskoSo... any smoke?11:21
st3no11:22
st3it works ok11:22
koreskoAnd you did this in one process?11:22
st3no, two ones11:22
koreskoAh, OK.11:22
st3(a process is limited to 2^30*3-1 or something like that)11:22
koreskoThat makes sense.11:23
koreskoSome of the address space (1G) is reserved for the kernel, right?11:23
koreskoThere used to be a config option to control where the split went.  I think the default was 2G/2G kernel/user.11:23
st3iirc, the default was 1G/3G11:24
mjg59Yes, 1:311:24
mjg59Some of the address space is used to refer to the physical address space11:24
koreskoHm, I vaguely remember that being the optional setting.11:24
mjg59Moving it lets you use more RAM without needing HIGHMEM11:24
koreskoOK, I think I see.11:26
koreskoBedtime!  Thanks again for the info.  It's hard to find this even via Google (I tried).  The kernel docs themselves are a bit terse.11:32
=== gicmo [n=gicmo@p5491E104.dip.t-dialin.net] has joined #ubuntu-kernel
tepsipakkihum, I merged ndiswrapper before checking out the version in kernel..11:56
=== koresko [n=koresko@cpe-67-49-146-130.hawaii.res.rr.com] has joined #ubuntu-kernel
=== MidMark [n=marco@host-78-12-66-76.cust-adsl.tiscali.it] has joined #ubuntu-kernel
=== elmarco|away is now known as elmarco
=== AvengerMoJo [n=alex@61.14.130.201] has joined #ubuntu-kernel
lifelesswhat would cause a drive to flip-flop between sda and hda on boots ? (not every time, but its not consistent)01:20
=== EtienneG [n=etienne@ubuntu/member/EtienneG] has joined #ubuntu-kernel
shawarmaDidn't there used to be a restricted-modules package that corresponds to the server images?01:39
=== BenC [n=bcollins@debian/developer/bcollins] has joined #ubuntu-kernel
=== Cheka [n=Cheka@ina044000021.lancs.ac.uk] has joined #ubuntu-kernel
=== abogani [n=alessio@adsl203-157-083.mclink.it] has joined #ubuntu-kernel
Chekahey folks... if i wanted to profile the linux networking stack how would i go about it ?02:00
BenCCheka: netperf?02:17
Chekanetperf will tell me the throughput, but i'm more interested in the length of packet processing at each stage02:18
Chekai.e. hardware interrupt, ip processing, tcp processing etc02:18
BenCthat's more like normal kernel perf stuff02:22
BenCoprofile I think is what you want02:22
BenCI also don't know if you can get the granularity you're expecting, in regards to ip vs. tcp processing time02:22
Chekai've used another profiler and it shows the amount of time spent in the kernel, but as you said not to the granularity that i want :(02:23
=== ivoks [n=ivoks@backup.grad.hr] has joined #ubuntu-kernel
=== zul [n=chuck@CPE0006258ec6c1-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-kernel
zulBenC: is there still a meeting today?02:43
BenCzul: yep02:43
zulokies02:44
zulwhats on the agenda?02:44
zuler never mind02:45
=== Mithrandir [n=tfheen@vawad-xen1.err.no] has joined #ubuntu-kernel
Mithrandirhm, the 3ware 9550SX-12MI should be well supported, shouldn't it?02:57
Mithrandirand is a decent controller?02:57
thomMithrandir: yeah, works pretty well for us03:00
thomjust make sure you get BBUs! :-)03:00
Mithrandirbattery backups, yeah.03:01
Mithrandir do you have any experience with the Areca ARC-1130?03:01
=== Mithrandir isn't very familiar with raid controllers costing ~500
thom(the 9550 disables write cache utterly and irrevocably with no BBU)03:01
thomwe had a couple of arecas and they were dreadful03:01
Mithrandirok, good to know.03:02
thombut that was on oldish RHEL03:02
Mithrandirthe 3wares are cheaper, so it's not a hard choice to make.03:02
Mithrandirby about the price of the battery03:02
thomheh03:03
kylemMithrandir, all 3ware controllers are pretty good.03:16
kylemif you can live with their custom ODF.03:16
MithrandirI'm pondering using them as a JBOD and use the swraid layer03:17
maswanMithrandir: we had rather bad experiences with areca too, 3wares are stable for us.03:31
kylemMithrandir, are you sure they don't use their own ODF with JBOD too?03:31
Mithrandirkylem: no, but I'd think it less likely03:31
kylemhmm.03:31
Mithrandirmaswan: ok, thanks.  That settles it.03:31
kylemMithrandir, i don't trust areca... their driver people are... perhaps we should talk in private. ;-)03:32
=== Mithrandir chuckles.
Mithrandirthat bad?03:32
kylemno comment.03:33
maswanI _think_ I've moved between !3ware and 3ware for md raid5 devices03:33
maswanyeah, started out a raidset on sata_sil, then changed to 3ware for stability03:33
kylemyeah, 3ware are top notch in the prosumer. raid controller business.03:34
Mithrandirok, coolie03:34
=== AvengerMoJo [n=alex@219.142.230.9] has joined #ubuntu-kernel
=== johanbr [n=j@JBrannlund.MathStat.Dal.Ca] has joined #ubuntu-kernel
st3Cheka, iperf?03:58
Chekadoes that give me detailed statics of the network code or just the network throughput?03:59
st3"Iperf is a tool to measure maximum TCP bandwidth, allowing the tuning of various parameters and UDP characteristics. Iperf reports bandwidth, delay jitter, datagram loss."04:02
Chekayeh, that's what i thought, i'm more interested in how long the the packet is in each layer, say the ip processing (i.e. the ip_output.c functions or whatever)04:04
=== AlinuxOS [n=vsichi@host122-198-dynamic.8-87-r.retail.telecomitalia.it] has joined #ubuntu-kernel
=== ubuntu_laptop [n=ubuntu_l@ubuntu/member/gnomefreak] has joined #ubuntu-kernel
=== m0rg0th [n=m0rg0th@219.64.120.181] has joined #ubuntu-kernel
zulwhoops...I brought down the network at work04:23
=== mdomsch [n=Matt_Dom@cpe-70-113-73-138.austin.res.rr.com] has joined #ubuntu-kernel
=== lfittl [n=lfittl@213.129.230.12] has joined #ubuntu-kernel
=== BenC_ [n=bcollins@collinsap1.phunnypharm.org] has joined #ubuntu-kernel
=== ubuntu_laptop [n=ubuntu_l@ubuntu/member/gnomefreak] has joined #ubuntu-kernel
=== sacater [n=sacater@105.245.131.213.static.inetbone.net] has joined #ubuntu-kernel
=== sacater [n=sacater@213.131.245.105] has joined #ubuntu-kernel
=== BenC [n=bcollins@debian/developer/bcollins] has joined #ubuntu-kernel
=== sacater [n=sacater@colchester-lug/member/sacater] has joined #ubuntu-kernel
=== pmjdebruijn [n=pmjdebru@home.pcode.nl] has joined #ubuntu-kernel
=== Lure [n=lure@89-212-19-55.dynamic.dsl.t-2.net] has joined #ubuntu-kernel
=== koresko [n=koresko@cpe-67-49-146-130.hawaii.res.rr.com] has joined #ubuntu-kernel
=== bleinmono [n=toffel@ppp91-76-182-33.pppoe.mtu-net.ru] has joined #ubuntu-kernel
=== iwj [n=ian@xenophobe.extern.relativity.greenend.org.uk] has joined #ubuntu-kernel
=== Amaranth [n=travis@ubuntu/member/Amaranth] has joined #ubuntu-kernel
=== n2diy [n=darryl@66.212.43.63] has joined #ubuntu-kernel
=== elmarco is now known as elmarco|away
fdovingdid anything special change from 2.6.20 to 2.6.22 that would make my trackpoint die? (latitude d620)08:16
=== sacater [n=sacater@colchester-lug/member/sacater] has joined #ubuntu-kernel
=== mdomsch [n=Matt_Dom@cpe-70-113-73-138.austin.res.rr.com] has joined #ubuntu-kernel
=== doko [n=doko@dslb-088-073-101-115.pools.arcor-ip.net] has joined #ubuntu-kernel
=== iwj [n=ian@xenophobe.extern.relativity.greenend.org.uk] has joined #ubuntu-kernel
=== amitk_ [n=amit@a81-197-135-210.elisa-laajakaista.fi] has joined #ubuntu-kernel
=== ivoks [n=ivoks@backup.grad.hr] has joined #ubuntu-kernel
=== AlinuxOS [n=vsichi@host122-198-dynamic.8-87-r.retail.telecomitalia.it] has joined #ubuntu-kernel
=== infinity3 [n=adconrad@cerberus.0c3.net] has joined #ubuntu-kernel
=== Keybuk [n=scott@wing-commander.netsplit.com] has joined #ubuntu-kernel
=== m0rg0th_ [n=m0rg0th@219.64.120.181] has joined #ubuntu-kernel
=== he1ix [n=ehrenfeu@fachschaft.informatik.uni-freiburg.de] has joined #ubuntu-kernel
=== gicmo [n=gicmo@p5491F2CD.dip.t-dialin.net] has joined #ubuntu-kernel
=== unhappy [n=justinas@85.206.151.213] has joined #ubuntu-kernel
=== Studiosus [n=vic@88.201.134.142] has joined #ubuntu-kernel
=== ivoks [n=ivoks@20-252.dsl.iskon.hr] has joined #ubuntu-kernel
keturnfdoving: maybe it's the season for trackpoint death?  the thing on my inspirion 4000 died, but booting older software doesn't bring it back, so I'm assuming it was hardware gremlins.10:57
fdovingketurn: well, this machine is pretty new. and it works with the feisty kernels :)11:01
=== duke_ [n=duke@66-227-189-141.dhcp.trcy.mi.charter.com] has joined #ubuntu-kernel
=== victory747 [n=vic@87.113.23.123.plusnet.pte-ag1.dyn.plus.net] has joined #ubuntu-kernel
victory747Hi, I just upgraded feisty to 2.6.20-16.  Previously (2.6.20-15 and earlier) my IDE hard drive always showed up as /dev/sda.  Now, suddenly with this new kernel it shows up as /dev/hda.  Is this a known problem?12:08

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