| |
| |
| |
|
Comments:
<0> Hello. I am having a strange problem with linux 2.6.17-r3 and nvidiadb. The system boots and sets the framebuffer device to some unrecognizable geometry: /sys/cl***/graphics/fb0/virtual_size is "1280,26163". It also starts with 'double true'. This happens when the only mode in /etc/fb.modes has a geometry of "1280 800 1280 800 8" and this option "double false".
<0> So what I'm saying: should I p*** some extra parameter to the kernel at boot time?
<1> hello, how can i disable DMA for compact flash disks ? :|
<1> i'm using kernel 2.6
<1> on boot it gives DriveReady SeekComplete ... error ... and it continues booting... why do i get that seekcomplete error stuff ?
<1> hello?
<1> hello, how can i disable DMA for compact flash disks in my kernel? i'm using linux 2.6 ? :|
<2> Kournikoza: do a fsck, if the messages still appear, go buy new hardware.
<2> Hm maybe, "nodma" at boottime
<0> I will rephrase: What has changed since linux 2.6.16-r5 in the framebuffer configuration? Because it worked fine p***ing "vesafb:ywrap,mtrr,1024x768-32@70" to the kernel, and after upgrading to 2.6.17-r3, the framebuffer device wasn't activated anymore. That's why I went with the nvidiafb, but it's giving me that problem I just mentioned.
<3> If I use syslinux for a floppy, then do I have to compile MS-DOS support into kernel to boot it sucessfully ? I get a "VFS..." kernel panic
<1> help, i'm trying to boot from a flash disk on which linux has been installed... however there is a problem when booting the system it gives DriveReady SeekComplete .. error.. it's all about DMA.. could it be that my compactflash doenst support DMA? are there compact flash cards with dma and with i won't get any errors on boot? also what i need to know is, when i mount the compact flash it hangs about 10 minutes when its mounted to a d
<4> redondos: try p***ing vga=731
<5> I've read about x-test kernels... are they are form of beta testing? I see some 'rumble' joystick support is available in them, does that mean it will eventually end up in a release?
<6> hi
<6> does linux 2.4.18 kernel support dvd writers? i wanna buy a dvd writer for playing dvds on my laptop (dell latitude c600 - ~5 years old, p3/740) and doing system backups, it only has usb1 port
<7> usb1 port is too slow to support dvd playback
<6> heh
<6> i will try get firewire
<7> or you could just switch the drive in the laptop into a dvd-rom model
<7> and use a normal cd-rw writer over usb. although it will be painful, usb1 is very slow
<6> czr: good idea
<8> yo _RADIOhead
<9> Yo neil_m dude
<9> how are you man
<8> am good
<8> what's up with you
<8> just copying all my music onto my new hdd
<8> :D
<9> :)
<9> upgradepkg
<9> latest dropline gnome make sh* on my slackwaer
<9> quity
<9> later
<8> cool
<1> hello. i'm using an IDE compact flash.. but on boot it gives me a driveready seekcomplete error.. and continues with booting, sometimes it hangs because dma timeout, how can i disable dma in the kernel for ide compact flash disks? i also have a fixed sata disk in the box which needs dma.. anyone can help me? i'm using kernel 2.6
<10> hi!
<10> what is the version of the alsa driver included in the last stable kernel?
<10> is it 1.0.11 or earlier?
<11> even though it is deprecated
<10> :-)
<11> but it works so what do I care :)
<10> I have probelms in identifying the version of the drivers in the kernel, not only for alsa but for the other drivers as well. Is there a standard way for doing so?
<10> well, I upgraded to alsa 1.0.11 only because I needed
<11> define standard :)
<11> & which stable kernel were you referring too?
<10> 2.6
<10> well, even not-standard would do :-D
<11> instead of saying stable, try a specific version, because I doubt any of us can guess or utilise crystall balls too determine what you consider as stable
<10> any possible way would do really
<11> hehehehe
<10> I mean last stable 2.6
<10> as on the front page of www.kernel.org
<11> yeah which series of 2.6?
<11> dont try n make ppl guess
<11> or you will get nil ***istance
<11> just generic advice in the realmn of common sense, but it doesn't seem too be very common
<10> 2.6.16. Are they very different? I am using 2.6.12 at the moment, but if I could understand which versions are the drivers I then would decide whether is the case to upgrade.
<11> yes the version feature vary enotmously :)
<10> but I thought that 2.6.13 superseded 2.6.12 and so on.
<10> So that there is only one last stable of the 2.6 kernel. Am I wrong?
<11> try looking in the Documentation directory too see what it says about versions, etc expected
<10> do i have to download and uncopress then?
<11> no if you look at the topic you'll see there are several 2.6 streams going concurrently
<10> oh blimey! I did not realise! Why?
<11> because each stream concentrates on different things
<11> eventually they combine in a 2/6/x release, but not always
<11> arrgh
<11> they especially dont combine if the result in trashed filesystems or similar :)
<10> ah
<10> so the 2.6.12 is still under development
<11> not sure, I think that was the last release that was considered stable
<10> so, what is the difference between the last 2.6.12 stable and the first 2.6.13? they do not overlap? the latter does not supersed the former?
<11> generally once you hit a new third digit works gets transferred to the next version, but not always
<11> some ppl still work on 2.0 kernels
<11> just depends on your needs really
<11> & some major releases grow in size for some kernel code cutters so they stick with older versions
<11> you know too large for them
<11> especially if they are developing code for embedded systems or other very restricting hardware in terms of ram and/or cpu power
<10> mmmm, so let's say I want to know the driver version in my present kernel
<10> what do I do?
<11> check the documentation, use a decent search engine :)
<11> sumtimes the changelog has such information if it changes from one version too the next
<10> yes, I have been reading ALL of the changelogs, till I had them coming out of my head!
<10> there has to be an easier way, I hope :-D
<11> learn too use a decent search engine which greps all those things for you :P
<11> & use the correct search criteria
<11> can make all the difference
<10> I am reading the documentation which came with the kernel, nothing about versions
<11> I find grep -v too be very handy
<11> for trimming crap
<11> if you dont know exactly what you want but you know what you dont want :)
<11> some search engines allow -ebay too kill matches on crap completely unrelated too your search
<11> but I think you should match on 2.6. & not a specific version if you want info re versioning of libs, etc
<11> then when you get the hang of it further restrict your search criteria for alsa or whatever
<11> there are lots of search engines out there & many are crap even dogpile which uses multiple engines
<10> at the same time, I do not think I am the only person with this problem, there has to be a quicker solution!
<11> that is possibly going too be the quickest way for you too retrieve the desired info
<11> eeos: do you have any idea of the number of people cutting code on any one version of the kernel?
<10> gb: roughly
<10> gb: don't you think they need to know?
<11> there are many lkml's but in general most people would rather be cutting code then answering questions they've already documented the answers too in their changelogs & code
<11> the kernel is evolving rapidly & the answer today might be different tomorrow or even in an hours time :)
<11> eeos: much kernel work is done by trial & error
<11> so even if code was designed for version b.c of a certain lib, ppl are still trying b-1.c or b.c+6 in an attempt too alleviate issues
<11> when compiling the makefile should search & inform you if you have the wrong version of a lib in a warning or critical error
<10> right, it sounds a bit hopeless for me at the moment. I will try reading changelogs again.
<10> have to go! thanks for helping me through.
<11> eeos: if you dont know what you are looking for reading changelogs will probably be pointless
<10> gb: well, I know what I am looking for. Introduction of 1.0.11 alsa driver in the kernel.
<10> gb: 2.6, any sub version
<10> gb: got to go. thanks again! bye.
<12> hi!
<12> so, i've compiled this nice new fangled kernel
<12> and it appears i cannot connect to the internet : (
<8> hah
<12> however, i can connect to another box and irc out from there.
<12> i suppose i should test the old kernel and make sure it still has internet.
<12> i say internet i mean the routing table is there, the pings work. but i can't connect to an ip not on subnet.
<12> (no ping to non-subnet)
<12> hmm to try other nic first too
<12> i may be back.
<12> how rare. other nic also has none of the internet.
<12> rebooticus into other kernel.
<12> ok, my bad. i broke something horribly and don't know how : (
<12> though if anyone has suggestions, that would be nice
<13> i'm a NEWBIE running debian gnu/linux sarge 2.6.8-3 on a laptop P133 80MB RAM and everything work OK except the wireless cards. whenever i insert a card in the pcmcia slots i get : cs: pcmcia_socket0: unable to apply power
<13> http://www.kernel.org/pub/linux/utils/kernel/pcmcia/powerbugs.html has NO newbie friendly fix for sarge!
<14> any one give me the link for kernel recompilation
Return to
#kernel
or
Go to some related
logs:
gnomebaker what is burnfree
xine no dvb dvb-t usb
#linux
mysql_fix_privilege_tables.sql Error 1046
top absolute css ie doesn't work
#linux
#web
disable appletalk debian
ubuntu CONFIG_AGP
gentoo permissions portage group
|
|