DebianThis forum is for the discussion of Debian Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I've compiled the 2.6.22 kernel using the instructions from this sticky to get the Debian boot logo. The kernel boots OK but part way through the boot process the text suddenly shifts to the right of the screen so that it disappears off the end and reappears on left hand side leaving a wide gap up the middle of the screen. Anyone know what causes this? I'm using a SIS integrated graphics chip.
BTW, this happens regardless of what resolution I set at vga=x on the kernel line in /grub/menu.lst
Also, I have googled but can't find an answer to the following question:
What does "ywrap,mtrr" do in the cheatcode "video=vesafb:ywrap,mtrr vga=788"?
Wow, I had forgotten about this post...It has been a while since I have been on LQ.
Here is what ywrap does (it is supposed to speed up scrolling as I understand it):
vesafb does not enable scrollback buffering as a default. You will need to pass to the kernel the option to enable it. Use video=vesa:ypan or video=vesa:ywrap to activate it. Both does the same thing, but in different ways. ywrap is a lot faster than ypan but may not work on slightly broken VESA 2.0 graphic cards. ypan is slower than ywrap but a lot more compatible. This option is only present in kernel 2.1.116 and above. Earlier kernels did not have the ability to allow scrollback buffering in vesafb.
The mtrr explanation is:
If your processor (on Intel platforms) supports MTRRs, enable this. It speeds up memory copies between the processor and the graphic card, but not strictly necessary. You can of course, do this after you have the console device working.
For the main part of your question about the text shifting to the right, I am not sure what causes that. I run Ubuntu now on all my computers and I have observed a similar thing when booting up in text mode without usplash. At the very end of th boot process, the last few lines are shifted over to the right. Each line appears shifted more than the next, so that it appears to be scrolling to the right. I just never investigated it to try and find out a cause.
I am trying to compile a custom 2.6.24 kernel for Debian Sid "The Debian Way" using:
make-kpkg --initrd --append-to-version=-xx kernel_image
This results in the following error:
dpkg-deb: control directory has bad permissions 2755 (must be >=0755 and <=0775)
I would appreciate it if anyone could tell me how to fix the problem.
The error message is referring to a permissions problem. I've not seen this particular error myself, but it should be fixed by changing permissions. I assume the "control directory" referred to in the error message is the directory in which you are compiling the kernel image. Try changing the permissions of that directory using chmod. Something like
chmod 755 <name>
Where <name> is the name of the directory. It should change permissions to 0755 as suggested by the error message. Hopefully that works.
I did a:
chmod 775 ./linux-source-2.6.24
however I still get the same error. I am not sure what the "control directory" part refers to.
Try doing this to the directory that dpkg builds the kernel image in. Normally that is /usr/src You might also try /usr/src/linux I'm not sure why permissions of the directory should be a problem. As I said, I have never seen that particular error before. Are you following the "guide" I wrote at the start of this thread? In that case, the kernel source should be unpacked in /usr/src/linux-source-2.6.24 and should be symbolically linked to /usr/src/linux
I have installed the knoppix 5.1.1 in my system using poor man install method. Now i want to upgrade the kernel. I have followed the below steps,
1. Check for the packages ,kernel-package,ncurses-dev fake root wget bzip2.
2. Downloaded the linux source for 22.214.171.124 and copied into /usr/src
3.Unpacked the file and get into that linux 126.96.36.199 dir.
4.typed make menuconfig. In that i havent selected anything.Checked for the SATA support.
6.fakeroot make-kpkg --revision=custom.1.0 kernel_image. this command tooks more than 1.5 hours to create an linux.188.8.131.52.deb file in /usr/src
7.get into /usr/src and typed dpkg -i <linux custom image file.deb>
When i did i got the error in lilo.conf as
Fatal:Trying to map files from unnamed devce 0x0010 (NFS/RAID mirror down ?)
I dont know how to proceed. I am new to the knoppix.Mean while i got the error as No space left on device when i installing the linux custom image file and i deleted the linux.184.108.40.206.tar.bz2 file. For past two days i am trying to resolve this. can aynone help me.
Well I had framebuffer support and the Debian boot logo working as stated above but now, without consciously changing anything, it has all disappeared and reverted to the default boot text. The only thing I have done is "aptitude upgrade".
As I am using a custom kernel, I wouldn't expect an upgrade to change the kernel boot parameters. Could this be a GRUB thing?
Edit: Sorry, I'm being dense.
I've just checked my /boot/grub/menu.lst and the "video=vesafb:ywrap,mtrr vga=788" cheatcode is missing.
Clearly the upgrade has overwritten this.
Anyone know how to stop this happening each time GRUB upgrades?
2nd edit: I found this on a Ubuntu site:
Add the parameter changes to the end of the line "#kopt...". These parameters will then be automatically added to any new kernel entries and should also survive an upgrade of grub.
The kernel boots OK but part way through the boot process the text suddenly shifts to the right of the screen so that it disappears off the end and reappears on left hand side leaving a wide gap up the middle of the screen. Anyone know what causes this? I'm using a SIS integrated graphics chip.
For information, I've solved the above problem by using the following boot parameter: "video=vesafb:ypan,vga=791"
I think ywrap may have been the problem, but also vga=791 seems to look better than vga=788
I have a nVidia GeForce FX 5200 video card with Debian Sid and upgraded from a 2.6.26 kernel to a 220.127.116.11. I ran into the following problem:
NVIDIA-Linux-x86-173.14.12-pkg1.run failed with:
"-> Kernel source path: '/lib/modules/18.104.22.168/source'
-> Kernel output path: '/lib/modules/22.214.171.124/build'
ERROR: If you are using a Linux 2.4 kernel, please make sure
you either have configured kernel sources matching your
kernel or the correct set of kernel headers installed
on your system."
This driver worked before with no issues on my previous kernel.
Interestingly this driver was not listed under the official NVIDIA drivers page for linux.
Does anyone know what changed in the newer kernels? It just seems strange that the NVIDIA driver could not find the kernel source / headers which was in the usual place and the path indicated was correct.