2.6 Cursor problem (was init acting the maggot):-(
Recently, Somebody Somewhere wrote these words On Wed, Jun 29, 2005 at 06:43:49PM +0100, Declan Moriarty wrote: Should I choose a 2.6 kernel, the loadkeys script doesn't start, and I get this curious messing with no cursor. This is infuriating I rebuilt the 2.4 and 2.6 kernels on LFS-5.0 here. Only a 1% change, mainly in usb because the modules were barfing over hotplug. Spamd is now starting under the 2.4 kernel and all seems well there. Loadkeys is running again under the 2.6 kernel. Neither have framebuffer enabled for the console. The console cursor problem remains. Further, If I change from a console into X and back out, the cursor vanishes :-((. At any stage, running 'setfont same font' restores the cursor action. No dri enabled either, btw. I think the init issue was the poor (idiotic) naming convention of kernels and maps in the common /boot partition. I now have vmlinuz-version and System.map-version which was definitely not what I had before. -- With best Regards, Declan Moriarty. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Init acting the maggot?
On Thu, 30 Jun 2005, Declan Moriarty wrote: Which kind of tells me I didn't compile in a framebuffer at all. [EMAIL PROTECTED] /usr/src/linux-2.6.12.1]# grep FRAMEBUFFER .config # CONFIG_FRAMEBUFFER_CONSOLE is not set but the radeon module loaded a module called fb. Same thing? Not quite, you've enabled framebuffers (so, it's possible for an application to draw graphics on them, I guess) but NOT the framebuffer console which is what the system would use. I think you were originally uing a different vga 'mode' which gave you a text screen of a different size [ framebuffers are normally associated with an initial display of one penguin per CPU ]. Framebuffers will often allow several different resolutions (e.g. 1024x768, 800x600, 640x480) depending on what the graphics card and monitor can agree to do. But, I can't recommend playing about with framebuffer modelines in 2.6 (didn't work for me when I tried it once) and anyway if you don't want a framebuffer there's no reason to bloat your kernel by including one. But, since you seem to have a radeon framebuffer module it sounds as if you selected CONFIG_FB for framebuffers - maybe that is interfering with the VGA= parameter (in early 2.6 kernels, multiple framebuffer modules apparently didn't co-exist happily, maybe vgacon and framebuffer is similar). Of course, I could be wrong about what you were using in 2.4. If this was my box, I'd keep the semi-working 2.6 kernel just in case, and try a new version with a slightly different config (and a local version or EXTRAVERSION, e.g. -rfb or whatever) : since the radeon framebuffer loads, build it in and do not select any other framebuffers, also enable support for console on framebuffer (it's tucked away in menuconfig), then in your boot arguments play with video=radeonfb # should get you 80x30, plus a penguin video=radeonfb:[EMAIL PROTECTED] # 100x37 text video=radeonfb:[EMAIL PROTECTED] # 128x48 text - you should be able to put all of these in lilo.conf or grub's menu at the same time, so if one is unreadable you can still ctrl-alt-del to reboot cleanly (if enabled - otherwise log in and reboot blind) without having to bring up a different kernel each time to change the bootargs. If the last two do nothing, the refresh rate of 70 is probably outside what your card can achieve. If the display is unreadably smeared, try a different refresh rate. And of course if it's too small, don't use that resolution in future. I don't know if these changes will side-step the cursor problem or not. Ken -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Init acting the maggot?
On Thu, Jun 30, 2005 at 04:00:13PM +0100, Declan Moriarty wrote: modprobe radeon got me a module which found the right type of card in the agp bus. That looked good. Good. modprobe fbcon gave me: FATAL: Module fbcon not found. It's 'Framebuffer Console support' in 'make menuconfig'. Which kind of tells me I didn't compile in a framebuffer at all. [EMAIL PROTECTED] /usr/src/linux-2.6.12.1]# grep FRAMEBUFFER .config # CONFIG_FRAMEBUFFER_CONSOLE is not set but the radeon module loaded a module called fb. Same thing? I think not. fbcon is only for using the text consoles as a framebuffer thing. When X11 runs on the fbdev driver like this: Section Device Identifier Framebuffer Driver fbdev Option fbdev /dev/fb0 EndSection Section Screen Identifier Screen0 Device Framebuffer then 'startx' switches the display to using the 'nvidiafb' module, but when you switch back to text console with ctrl-alt-F1 it's gone blind until you modprobe fbcon. As I remember it, the vga card has some 'text modes' where it has its own fonts, and it has 'graphic modes' where it has only pixels, so the driver has to paint the text characters. And I think X11 on nvidiafb switches it to graphic mode, but doesn't switch it back, so from that point you need the fbcon driver or you won't have a text console anymore. What you are saying is than the new module-init tools are crap. I agree. Also some dweeb changed the names of all these modules. I think we are in the middle of a process. The old way was: A program talks to a device file, the kernel wakes up and loads the corresponding module. The new way is: Something, a boot script, loads a module, udev sees it and creates the corresponding device file. Maybe some drivers are already living in the future, so they don't know the old way anymore, and some other drivers don't know of the future yet, and we are caught in the middle, as we alway are. I think you take lines pretty much like the XFConfig mode lines that don't blow your monitor up. Get the stahndard vesa ones and you are fairly safe. Yes, I read about that. As I alway do: I'll learn it when I have to. Regards Joern -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Spam filtering on the mailing lists
Hi everyone! I finally got around to updating the SpamAssasin rulesets for the mailing lists today (thanks to Jim Gifford for giving me explicit instructions!). I'd be interested to know if you: 1) Notice a significant decrease in the levels of spam on the lists 2) Continue to receive spam 3) Have any legitimate email that is being blocked. I'd prefer it if you could send that info directly to me rather than clutter up the lists with it, please. Best regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
