Debian Configuration :: Tampered With Kernel And After Restoring It Cannot Print
Jul 19, 2011
I tampered with Kernel and after restoring it cannot print , when I tried to re instal printer get the following message: CUPS sharing "Unable to get printer status(client-error-forbidden)!"
I have Debian 6 (squeeze), I have also seen this under Ubuntu (can not remember how I fixed it). (has worked in ubuntu 10.10)I can hibernate, but when I switch on the system cold boots (it does not restore previous session).Note suspend works fine. Have looked in /var/log/pm-suspend.log Shows for each block of suspend suspend a block of resume suspend, but hibernate hibernate is not followed by resume hibernate ( I assume that is what is expected.)
My computer initially had one hard drive, with Debian Lenny 5.0.4 installed. I haven't done any special configuration, so upon boot, I was presented with the GRUB kernel select menu, then gdm, etc. I think I used the Debian installer's 'use entire drive with LVM' configuration.
I then added a second hard drive, with the intention of installing Windows XP on it. After I installed XP on this second drive, I found out that it had overwritten the MBR on the first drive. (It was my intention do use the BIOS' F8-key boot menu to choose between the two drives, each with their own distinct boot loader. The two drives and OS's would be completely independent.)
Using my Debian installer CD, I think I have GRUB installed on the first drive again. I've found a number of tutorials which say I can use 'set' and 'linux' to boot the system, but the linux command always returns a file not found error.
I think my LVM filesystem is still intact, as the Debian installer's fdisk reports it, it can also chroot to it and my installation appears to be intact. 'ls' within GRUB shows (derek-swap_1) (derek-root) (hd0) (hd0,1) (hd0,2) (hd1) (hd1,1) (fd0) . 'derek' was the hostname I used.
I would like to simply restore the system to the way it was before: with the standard GRUB that comes with Debian 5.0.4, which then boots into the debian with my LVM filesystem. Is there a way to do this from the Debian installer CD? (I was hoping there would be a 'dummy install' command which would install GRUB and configure it properly, but leave all my existing partitions and filesystems intact.)
I have recently installed Debian alongside Vista on the same boot menu using the GRUB booting device. Only problem is, I couldn't boot Vista at all any more, so I removed my Debian installation from that drive. But the GRUB boot record persists, I don't have the Recovery disk to restore my old system, so I have to find a way to manually remove the GRUB track and put the old record in its place. I assume there was a copy made of it by the installation program, now my only problem is to find that file and copy the content back in place (at the address at the very beginning of the drive) all that by using Linux code, since that is all I have left. Being new to this game, I have no idea how to begin writing the right command for a job like this
debian unstable system i have a problem with thinkfinger. By default i should only swipe my finger and i don`t have to press enter after that. The problem is that now i have to press enter. For example in GDM if i enter my username i should swipe my finger and it should let me log in. Now after i swipe my finger nothing happenes unless i press enter.The problem may be related to the update of xorg. The same problem has been reported here: Is there anyone here who uses thinkfinger who could possibly have an idea why is this happening?I am using thinkfinger 3.0 on debian unstable with kernel 2.6.32-amd64, xorg 1.7.4, SGS Thomson Microelectronics Fingerprint Reader and GNOME. Other than the having to press enter i have no problems with thinkfinger. I am have patched thnikfinger with two patches:This patch solves the problem with thinkfinger taking too long to intialize:
I have the printer Canon i-SENSYS LBP6020. I followed the instructions from the site URL....There are no errors, but when I try to print, nothing comes out of the printer.My system is: Debian GNU/Linux 8 (jessie)Here is some debugging information:
Error log while printing from a CANON LBP6020: URL.... Troubleshooting information while printing from CANON LBP6020: URL....
I'm trying to find good instructions to help me set up a print server with a usb printer on a Lenny box with no GUI. The printer is a Brother HL-2170W. Can anyone point me in the right direction?
I have no idea what's going on. I've had this machine running for over a year, and it's been great. A month or so ago, I realized that jobs weren't going to the printer. When i VNC'd in, I noticed that print jobs would show up in the queue as "Processing" briefly, then disappear.
lsusb: Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[Code]....
I've even reinstalled the OS (not just for this reason) to no avail. Printer is dete cted without issue, I just can't use it.
I run Debian Squeeze but I have the system installed step by step from minimal installation. So I'm not sure if I have forgotten basic packages important for printing. I open system-config-printer to add a new network printer. In the list of the Network Printers after some seconds it appears the HP Color LaserJet 2600n. I chose it and hit Forward. A new window opens that says that system is searching for Drivers and finally I'm ready for printing.
I am trying to set up a print server here on a Squeeze system using the stock debian CUPS package. It seems that since Apple has bought this package, it has caused me nothing but grief. I have set up two different USB printers with raw print queues, and every time I send a print job to either of them, the job disappears into thin air, with no error output. In fact, when I look at the queue, it says the job was completed successfully. I look at the logs, and there is no output indicating any issues. Just for kicks, I reconfigured one of the printers to use a linux driver, and it printed just fine (a little slow, but fine). I set it back to raw, and the jobs disappear again into oblivion.
I have done this many times in the past, and never had any issues -- I even had this very same printer set up that way about a year ago, and it worked great. The only noteworthy thing that seems to have changed is that there are no longer any files called "mime.types" and "mime.convs". It seems they have been replaced by "raw.types" and "raw.convs". The contents of these two files are as follows:
I recently installed debian squeeze 32bit on a second partition of my amd athlon 64 X2 dual core machine.Currently it is using linux-image-2.6.32-trunk-686 kernel.But linux-image-2.6.32-trunk-amd64 is available.on the repository.Is it a 64bit kernel or 32bit kernel optimized for amd64 architecture?
I am using DEBIAN 6.0 and I wannna update my kernel from 2.6.32 to 2.6.38. Every time, I do it but after the installation & rebooting into the new kernel it gives me error "UNABLE TO BOOT INTO THE KERNEL".
I have a problem with my custom kernel when I want to create the Nvidia kernel module.After this finished I installed the image and headers and created the Nvidia kernel module. Everything worked fine.However, if I remove the linux-source from my home directory then I can't create the kernel module.Even though I have the headers for the kernel installed.
I have a set of vm's with stable, testing, and sid to keep track of how things are going. When I did an apt-get dist-upgrade with squeeze last week, things seemed to OK (350 package updates) until the end. It didn't seem to like and / or was confused by a kernel dependency.
I am not too concerned yet. Because these are in vm's, I do a snapshot before any significant change. I can futz around with impunity because I have that backup.
I re-booted, and tried the apt-get dist-upgrade again with same results. I think I also tried apt-get -f install.
So I reverted to the snapshot, and will simply try again in the future. I recall that with lenny as testing, the font-desktop was really screwed up for about a period of 6 weeks.
However, just in case someone else runs into this:
1) a re-boot worked, but the failure of apt-get made me nervous enough to revert.
2) waiting for corrections has seemed to work in the past (with a single exception with a 4-disk SCSI software RAID10 update that failed to re-boot lenny successfully after what seemed to be a minor update -- that was on a real system, not a vm. I haven't gotten back to look at that.)
I have a debian system installed on my pc . I have just saved a text file on my desktop . Please let me know how can i print the file through comand prompt ? I need to learn the printing the file thru comamnd line .
I've recently performed a clean upgrade from 11.0 to 11.3 (wipe / partition to ext4, retain /home disk, swap partition etc.) and everything is fine, installed as Gnome distro with KDE3 from repos.Anyway, I've noticed that SuSE will say "doing fast boot" and suspend any console spew until after the kernel has finished with hardware detection and the like. I'd like to be able to see exactly what's happening with the kernel at boot, as I'm quite paranoid and in the event of system failure etc. it would be difficult to view the logs post-boot. Also, my IDE optical drives have a habit of sometimes only being partially detected due to the power line being somewhat intermittent, and I've seen the kernel attempt to re-stablish a link on 11.0, whereas I'd never be able to see that in 11.3 unless I see the console spew, so it would look like the system hanging on "doing fast boot".
Note: I do not want to disable splash=silent, unless spalsh has another option which will give me the desired functionality. I want to have a silent boot, with the option of going verbose with Esc; it's one of the things that I love about SuSE.Oh, and Grub was a nightmare as usual with disk ordering differing at run-time from config file and the total freeze at "loading stage2", so I had to manually fix that. Why does the installer seemingly ignore or revert the specific options I set for GRUB? I understand that the default options for GRUB are ok for single disk users, but my disk ordering is not overly exotic. I stress that this was not user error, as I've had the same issue from going from 10.2 to 10.3 to 11.0, even though they were clean grub installs (rewrites). /rant.
I tampered with installation process while I was reinstalling ubuntu, now I have this command on my screen and I'm stuck. GRUB RESCUE>_ What do I need to type, to continue installation.
On Lenny, due to some compatibility issues: kernels before 2.6.26 don't recognize part of my vaio laptop's hardware, while the last drivers of my videocard (version: 260, card: nvidia gt 230m) suffer some incompatibility problem (this is one of the most problematic computers I ever had), so I have to use version 256, which doesn't work with kernels after (perhaps) 2.6.32. So, I suppose I have to check each kernel between that two versions and hope that one of them will be ok. I searched quite deeply over the net but didn't find anything related to debian, except for generic kernels [URL], but as someone told me that it's better if I only install stuff from the stable repository or backports. What can I do? Is there any backports archive or something like that? Otherwise, what should I do?
I recently bought an AMD R7 360 videocard and I'd like to use the free Radeon driver.
Problem is, PCI-ID 0x665f is not present in Jessie's 3.16 kernel sources. The hardware however is supported, it's just not recognized. So I'll have to get the Debain sources and patch include/drm/drm_pciids.h
From the 4.1rc1 kernel I know what to patch and where.
Debian page that explains how to use the Debian build system for recompiling the current kernel from Debian packages?
Upgraded Wheezy to Jessie, by changing my apt sources to point at stable instead of wheezy. Ran upgrade, and dist-upgrade, all fine etc.
Then tried to update the kernel by installing linux-image-amd64 package .. seemed to work fine, but after a reboot my kernel version still says 3.10.23
What have I missed?
Code: Select allroot@hostname:~# apt-cache search linux-image linux-headers-3.16.0-4-amd64 - Header files for Linux 3.16.0-4-amd64 linux-image-3.16.0-4-amd64 - Linux 3.16 for 64-bit PCs linux-image-3.16.0-4-amd64-dbg - Debugging symbols for Linux 3.16.0-4-amd64 linux-image-amd64 - Linux for 64-bit PCs (meta-package)
I have a MyBookLive where i installed a Debian 2.6 kernel. The system is running fine so far. Because of an error message when apt-get upgrade (udev) i tried to upgrade to 3.16. Here's what i did:
- apt-get install linux-image-xx - apt-get install linux-source-xx - extract the source - copied the old .config from running 2.6 kernel over to the 3.16 directory - make oldconfig - make uImage - make modules - make modules_install - copied uImage to /boot
No error messages because its a headless device - its just not booting up.
I was wondering if anyone can assist me. I am looking to build a server with Debian as the host. When I installed Debian (Squeeze) the default kernel was "2.6.32-3-trunk-amd64". When I tried to install 'Virtualbox' application, I got a failure because I didn't have the 'kernel-headers' installed on my machine. I noticed there are no specific header package the 'trunk' kernel I was using. I have a few questions so I guess I should begin:
Is it safe to remove the 'trunk' kernel and boot my system on just the regular 2.6.32-3-amd64 kernel? Is this OK or not recommended? Please explain whatever is the correct answer. This is my 1st time using a 'Trunk' kernel so I don't know the in's and out's of it.
If I am using Debian 'Testing' for virtualization via 'Vbox', is there a specific kernel I "should" be using?
I have maked a new kernel (version is 2.6.24.7) in debian system which kernel is 2.6.26, and then when i start the new kernel which is 2.6.24.7, it tells me that:
My girlfriend got a 'new' (second hand) laptop, a HP Compaq 6715s. When I tried to install Debian on it, the install went immensely slow - glacial, even. It was a very minimal install but it tooks hours to get to nowhere.
I found out online that this was because of a problem between the current kernel and the hard drive (or HD bus, something hardware-y to do with the disk) which meant file operations were extremely slow. I thought "easy, patiently install Debian and then install newer kernel". Except that after six hours, the install wasn't even halfway.
So I install Arch Linux with the 2.6.35 kernel: no problems with the drive speed at all. After a lot of researching (I only played around with Arch once, more than a year ago) I got the system into a usable state. But now wlan0 has suddenly disappeared, together with some other problems - and a usable laptop wasn't exactly what I had in mind, it was supposed to be awesome (or at least good). Which, with Debian, it would be
So... is it possible to make a Debian installation use a later version of a kernel? I'd want to install Debian with the 2.6.35 kernel, not install Debian and then afterwards update the kernel (because I don't have 24 hours to install an OS, if it'll ever even install).
I've found some stuff online but it might well have been written in the Cyrillic alphabet. All I understand, I think, is that in theory it's possible.
I installed Debian Squeeze from a net install to a raid 1 array. I have been having a lot of troubles related to being able to write to one or more of the mounted drives - even touch gives me errors.
The most interesting line from dmesg is:
Here is the full output from dmesg:
I found a thread that indicated that this bug was fixed in the next kernel version: 2.6.32-6. I am willing to upgrade the kernel to get rid of my problems. Is a squeeze kernel at 2.6.32-6 or higher available? If so, where? I have not compiled my own kernel, and am not very interested in getting into that.
Trying to compile the 2.6.36.2 kernel. Its not the first kernel I've compiled, but I've run into a problem I've not come accross before.
While compiling I get this error.
[Code]....
Looks like the headers sys/eventfd.h and linux/virtio_rng.h haven't been selected in my .config file. I just copied my old config from the last kernel I built. This was a while ago (2.6.30), but I thought I'd give it a go anyway.
what config option they are under or what I can do to get rid of this error?
This is Wheezy x86_64. I tried two different ways to install kernel 2.6.38 on my machine and both have failed. First thing I did was to follow this guide [URL]... el-26.html) and try to compile the latest stable from kernel.org. I don't know why, but it turns into kernel panic when I try to run it. Second thing I did was to install the liquorix 2.6.38, and that also fails, seeming to boot but hanging a second short from the login. I don't know what I'm doing wrong. Is there a special way to install kernels in Debian? This is the first time I tried compiling a kernel, so it's quite likely that the problem is sitting 6 inches from the computer screen. Also, how would I remove those kernels since they're obviously not working? I know I could remove them from the grub menu but I'm not sure how to completely delete them.
I'm running testing, so yesterday I upgraded to the new kernel (2.6.38). Unluckly I can't get to the desktop, because the system just hangs (screen goes black then nothing happens). I have found that my problem is the radeon (open-source) driver. When the it tries to get to the desktop it enters an infinite loop, so the system hangs. The bug is better described here: [URL]. However, I don't know how to fix it. I would prefer not to go to the fglrx (proprietary) driver because of tearing issues.