| |
| |
| |
|
Page: 1 2 3 4
Comments:
<0> :)
<1> hay _RADIOhead ?
<0> aXp: sup man
<0> ?
<0> aXp: xgl really rock dude
<0> init 0
<0> :) later
<2> can someone help me figure out this error? http://xmb.ath.cx/kern_err
<3> hey guys,, isnt there anywhere some good documentation on all the ioctls ?
<4> not as far as I know, they're fairly specific to each device or device cl***. Perhaps start collecting white papers?
<3> hmm
<3> maybe i should try to write something when i learn ilittle more
<3> im especially interested in the mii and the ethtool ioctl's
<3> btw infi you wont happen to have a link to a fast guide how to add proc entries?
<1> {xmb}, try to omit the make-kpkg version!
<4> cohonen: http://lwn.net/Kernel/LDD3/
<4> it's not really fast, but it covers it fairly early on with the scull program in chapter 2 iirc.
<2> axp, what do you mean
<2> 'make vmlinux' returns the same
<2> hi usn
<1> just a make! we are in the time of 2.6! look into version.h and don't give any self made version strings (make menuconfig --> there is a point where you can set a own version string!
<2> make returns the same
<1> it has to work just compiled mine a few hours ago!
<5> found netconsole. but do not get any packages from it :-(
<2> this is .17 pre + pax
<2> .17 pre alone returns the same err
<1> tbf, metconsole? read the docs in the kernel no "package" required except netcat
<1> paste your verison.h
<3> ****
<3> infi: did you have that link
<3> my irssi scrolled your potential answer away :-(
<3> nevermind
<3> i see it
<1> cohonen, by default irssi logs verything look into .irssi/
<3> aXp: :-D great ,, hehe ill remeber that for another time
<3> infi: ahh nice ,, i wasnt sure that LDD 3 was free
<5> aXp: hmm, don't know why netcat was silent, but now it works :-D
<6> aXp: no need if you have a pgup & pgdown key
<4> it's just annotated in chapter 2 or 3 iirc, the example programs are downloadable in a tarball from that site, though.
<4> however, before mucking around in kernelspace, it's Highly Recommended(tm) that you read through at least that particular chapter before writing code :)
<3> its in 3 :-D
<4> if you go and unload a module, but forget to unregister the /proc entry handler, Bad Things(r) will happen.
<3> sure
<4> what're you doing, anyway?
<3> well right now im just considdering to add minor fixes to the forcedeth driver
<3> not really coding a new driver
<3> just remembered that for some testing output proc might be better than printk 's
<3> infi: but the code they show is specific for adding a proc entry under devices it seems
<4> ok, chapter 4, from page 83 on, they have a huge long section about /proc.
<4> been a couple of months since I cracked the book.
<3> ahh oki
<3> :-D
<3> maybe i should just start bruteforce reading it
<4> well, not bruteforce, take your time :b
<3> theres lots of cute little fixes needed in the net drivers
<4> anyway, keep in mind that while there is a PITA workaround, the /proc filesystem is normally used for < 1 page (4096 byte) nodes.
<3> mii-tools and ethtools only works with like 2 thirds of the nics i tried
<3> PITE?
<3> -E+A
<4> it talks about how to implement more than that, but it's funky and not exactly what /proc was designed for.
<4> Pain in the Arse.
<3> well if im gonna output stuff in proc itll be ints small stuff
<3> so oki ,, i have to beware of the amount of information i output there
<3> the oreilly books are not bad,, not bad at all
<4> mostly. lately, they've come out with some whoppers, though. I think their editorial staff is on vacation.
<3> hehe
<3> well the linux kernel internals networking internals and device drivers ,, are indispensable's ressources for newbie kernel lurkers like me
<4> indeed.
<4> LKI is great.
<3> so ,, i dont mind a typo here and there and some bad gramma, the community is in dire need of documentation
<3> i had borrowed it but didnt have time to read much in it
<3> but itll come
<4> kernelnewbies.org has some open projects about that. their page is a bit unmaintained, though, and the last few times I've been over on oftc, they don't seem too active.
<3> yea i know
<3> same here
<4> the LKI book, and lwn.net tends to have some good and current news generally, though.
<3> i should just start reading like a historian on steorids and help them a little afterwards
<3> the autodocumentation should be added to all of the kernel as well
<3> im sad to admit that it seems the BSD guys have an much more deciplined (better)development process than most places in the GNU/Linux community
<4> agreed.
<4> ever tried to find out what primitive datatype size_t actually is?
<4> the headers are a fscking mess.
<4> the bazaar approach only works so far.
<7> guys got a problem with my pcmcia card...as i plug in the session freezes
<7> is this a kernel issue?
<4> what card?
<4> and when you say "session", what do you mean?
<8> doktoreas, I face the same problem when i insert my WaveLan card
<9> hello can anybody help me troublesort this kernel Oops http://pastebin.com/730896
<8> If i remove it then it starts working
<9> what problem exactly?
<7> if i boot the system with the pcmcia card inside it freezes
<7> this happen with also live distro like ubunut, knoppix, slax
<9> and is the driver compiled into the kernel or as a module?
<7> kernel
<9> so compile it as a module
<9> problem solved
<7> you think?
<8> Shadowcat, I dont think compiling as module will solve the problem
<9> bluehole: he can try
<9> meanwhile
<9> I can't make heads or tails out of this stack trace
<8> coz i am using Fedora core 4 which uses modules for my Card still it behaves in eratic way
<9> ok, so crappy linux support
<9> nothing we can do
<6> Shadowcat: yes you need too return too your beloved commercial software
<9> gb: very funny
<9> now does anybody have a constructive answer?
<9> this machine has been running linux for over two years
<6> Shadowcat: maybe when you have some solid indication of what the issue is because you've done some of the legwork
<9> then tell me what I should do instead
<6> that machine only has an uptime of two years ey?
<9> no, it's a laptop
<6> hahahaha
<9> but it's been running Linux since Debian Sarge was in beta 1
<9> and these kernel errors just started popping up
<6> sure they did, obviously you did nothing too the system too cause them
<9> no I didn't
<9> I was running 2.6.16.1 before
<6> stock kernel or compiled by you?
<9> but then my reiserfs started getting journal replays out of the blue
<9> so I reinstalled the root fs and put 2.6.16.16 on there
<9> and I started getting those errors
<9> first few reboots were trouble free too
<9> only started this morning, last night everything was fine
<6> glad I never went back too reiser
<9> and it's a compiled kernel
<9> gb: well I've pretty much eliminated reiser as a cause
<6> you are aware 2.6 is not considered stable?
<9> yes I'm aware ofi t
<9> that doesn't mean that every major distro isn't running it
<6> Shadowcat: I suggest you try a stock kernel & see how that goes for a while
<9> as in a few reboots?
<9> oh well what the hell
<9> I'm not getting anything else done this afternoon anyway
<6> without knowing the exact hardware spec, config of the kernel & specific machine usage I would only be making wild guesses
<9> Acer Travelmate 660
<9> I've been using software suspend2 on this laptop
<9> that's the reason I built a custom kernel to begin with
<0> oh no gb is here
<0> hideing :)
<6> with a know config of a functional kernel you will at least have an entire channel too ask about issues that rise with it
<6> known rather
<9> gb: I can post the config on pastebin if you want it
<9> I mean I ran the same config on 2.6.16.1 with no problems at all
<9> until that reiser thing
<6> if you're using the same config, thats an issue in itself
<9> errr?
Return to
#kernel
or
Go to some related
logs:
rshadow runescape
#perl
gaim subgroup
#php
#physics
#ldap
streetfighter netsmart
3c905b module gentoo
extract_url
#linux
|
|