I installed 2.6.38 from backports. It boots OK, and among the start-up messages it says it has started kdm, but then it offers only a console login prompt, no GUI. I assumed (perhaps optimistically?) that newer kernels would be backward-compatible, and that any dependencies on other software would be enforced by the package mechanisms. Running amd64, Squeeze, KDE.
View 6 RepliesJust added Squeeze multimedia repositories in source list,but get this after reload :
W: GPG error: ftp://ftp.debian-multimedia.org squeeze Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 07DC563D1F41B907
However,update for Audacity & Mplayer showed in Update Manager,and I successfully updated.
I have been using my system for couple of weeks, and normally update software when the icon is displayed on top bar (gnome). Last couple of days there were updates for X, and I am not sure whether that is the cause of my problem. Once bootup, I get the login screen. When enter the password the login screen keep coming back. there is no error about any password issue, or anything. It keeps prompt me to enter the password.
I could login back the following way.
1. ctrl + alt + F1 , and login with the same username/pwd as for X
2.change to root
3.pkill gdm3
4.exit from root to user privilege
5. startx
The system starts X correctly and no login screen is displayed. I could use the system as usual.
The only thing I did custom to my system was upgrading to the latest kernel (2.6.38) using the source. This was to get support for my hardware, but that was about a month ago. I do not see anything in /var/log (X, demesg etc).
I am running Debian squeeze. A while ago I upgraded my kernel to 2.6.38 from backports. Just now I thought it would be good to upgrade to 2.6.39 from backports. Upgrade went fine, but after rebooting I get a kernel panics rightaway.
"No filesystem could mount root, tried:"
"Kernel panics = not syncing: VFA: Unable to mount root fs on unkown-block(0,0)."
This is the first time one of Linux installations halts/panics on booting, so I don't know what to do now. I tried booting the recovery entry from the grub boot menu, but same result.
I looked into my shell 'profile' on my running lenny and copied the PS1 definition over to my [virtual] new squeeze machine, but astoundingly, the prompt does not change!
The prompt always remains to be like this:${debian_chroot:+($debian_chroot)}u@h:w$
This does definitively not stem from 'profile' and I cannot find, where it is defined and how I can override this. If I do it interactively, in a terminal [terminal running in Gnome], it works like expected. In that script, even if I use 'unset PS1',followed by PS1= ... / export PS1, it does not change,Someone with the knowledge and/or a good idea would be great!
After an update on squeeze about a week or two ago, my console font turned green. I'm not exactly sure of the timing, because I switch between lenny and squeeze, and some time passed between the update and the reboot in squeeze.
During the update, I was asked if I wanted to keep my altered /etc/grub.d/00_header or take the package maintainer's version. I took the PM's version, knowing I'd lose my edit (set gfxpayload=1024x768x16). When I add that line to the new 00_header, run update-grub and reboot, the console font is the size I want, but it's a dull green. Reminds me of my first computer. How do I get it back to white and keep the 1024x768 resolution?
Currently booting with grub-legacy and chainloading grub2. If I boot entirely with grub-legacy, and pass vga=791, the console font will be white. It doesn't matter which kernel I use. Currently, I'm running 2.6.32-3-686. Same behavior exists if I use 2.6.30-2-686. If I use 1024x768x8 I get a dull gray instead of dull green.
My Squeeze installation has the horrific 80x25 line display, and I cannot stand it. I know it can do better, because the grub screen is very tiny. I ran dpkg-reconfigure console-setup, but the offerings there aren't much better. I don't know what happened to the good ol' days of grub when all you had to do was pass vga=791 to the kernel to get a decent console size... but it seems they are gone.
I don't really understand this new v2 grub... I don't know why it was necessary to change how it was configured, when it seemed to work so exquisitely. how I would accomplish the functional equivalent of passing vga=791 (1024x768@75hz) to the kernel in grub
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.)
On a Debian 5.0.8 I have a problem with OpenSSH server (sshd): when connecting to it from another host there is always a 10 seconds delay before sshd gives login prompt to the client. After the connection is established the communication goes on without any interruption. This long delay started to happen a few months ago and sshd_config was not changed at that time.
Here is a short description of the conversation between the putty client (on MS Windows) and sshd:
- putty client starts connection to sshd
- 10 s delay
- sshd returns "login as:"
- user types username in putty window
- sshd returns "password:"
- user types password in putty window
- sshd returns MotD and shell prompt
Here is a short description of the conversation between the OpenSSH client (on a Debian 6) and sshd:
- client does "ssh user@host.foo.bar"
- 10 s delay
- sshd returns "Password:"
- user types password
- sshd returns MotD and shell prompt
I tried connecting from:
- local host - NO DELAY
- a host on the same subnet - delay exists
- a host on another subnet - delay exists
I've found the following suggestions but to no avail (of course I restarted sshd after changing its configuration):
- on server put "UseDNS no" at the end of /etc/ssh/sshd_config
- in /etc/hosts on the server define mappings between IP addresses and host names for the ssh clients
- on client use "GSSAPIAuthentication no" in /etc/ssh/ssh_config
Here are some logs and configurations:
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.
I installed the 32 bit version of Debian Jessie (8.0) on an Asus X205TA. The Asus X205TA laptop is quirky like a lot of Intel Baytrail Atom laptops/tablets in that it has 32 bit EFI but a 64 bit capable CPU, and installing Linux on them is an exercise in frustration. Jessie is probably the first distro to support 32bit EFI out of the box, and the install went surprisingly smoothly. As expected the sound and built in WIFI does not work, but everything else seems to work well.
I spent half a day compiling the 4.03 kernel but it crashes on boot, and I ended uninstalling it in frustration.
Is there any backport of the 4.0 (or 4.1 which is currently a release candidate) for Jessie? Debian also seems to have pulled the kernel image off of their "experimental" repository.
[URL] ....
In trying to get something else working, I installed a newer version of the kernel from backports (I'm on 2.6.26 lenny and the backport kernel is 2.6.32). That failed, so I want to remove the backport kernel completely.
I tried:
Code:
and got:
Code:
Accept this solution? [Y/n/q/?]
I don't really understand how these metapackages work and I don't want to accidentally remove my currently-working kernel.
What's the correct way to remove all packages related to the backports kernel and leave the existing lenny ones alone?
downgrade my squeeze installation to kernel 2.6.32-29 (I think I have -30 now).
- what is the proper way to downgrade to that version of the kernel (I got my current kernel version when I installed squeeze few days ago and the official repo does not seem to have the -29 version anymore)?
- how to prevent that future automatic updates "upgrade" me again to the non-working version?
Laptop Amilo L1300, installed Debian Squeeze from netinstall from scratch a month ago. Installed Xfce as a DE afterwards.
This laptop usually has problem with: ACPI, Wifi and tons of other stuff usually Kernel related and is really picky about kernel version!
Now - with Lenny it worked without problems, but it had gnome and ext3 so I took a gamble and did a fresh install of Squeeze with Xfce with Ext4 filesystem and overall performance of the computer was faster and more responsive.
For wireless I have to use[url]
It all worked 100% until a week ago (roughly).
I do not use synaptic nor update manager, so I updated the system via terminal (as root of course) "apt-get update" and "apt-get upgrade". And I noticed it will upgrade kernel. I went through the upgrade process, as I thought it's all a 2.6.32-5-686 kernel version and it will not brake anything since it IS a stable branch of Debian and it will not install new kernel. Of course it did not install 2.6.34 or anything like that...
After the update I began experiencing problems, first with mouse pointer, it became invisible and goes back visible and resume from suspend, also wireless randomly disconnects and sometimes won't reconnect to wifi network, as I found out it's all kernel related problems (googled it up). I do not know how to go back to previous kernel version, since in Grub2 menu it only points to one and only kernel version, as I reckon it's the same version but with bugfixes? Or should I say buy UNfixes. I tried using a liquorix kernel 2.6.32 but as he works, has problem with ACPI as I presume since it freezes the system on random occasions.
Please, what EXACT version of kernel was in Squeeze like 3 weeks ago? And how can install that particular version of kernel, since it was the only one that worked besides the one from Lenny.
"uname -r" says: 2.6.32-5-686
That's what it always said.
Is it possible I had, dunno 2.6.32.28 and it was updated to, dunno, 2.6.32.29 or some later one?
I managed to google up this:[url]
And how can I go back to 2.6.32.28 kernel for instance?
Should I use some of the snapshots from [url]?
I have squeeze with Gnome and 2.6.32-5-686 kernel. Due to problems with graphics card (kernel bugs), I'd like to update the kernel. The problem is, 2.6.32-5-686 seems to be at the moment last kernel for squeeze.Is it any way to update just a kernel and stay with squeeze or I must upgrade squeeze to the testing (wheezy)?
View 7 Replies View RelatedBefore I ask I know what I'm asking is not recommended.
On Lenny It was possible to change the boot login to permit logins as root
I can't find how to do that since I installed Squeeze.
On my raspberry pi 3 with debian jessie I'd like to install a new version of ejabberd (xmpp/jabber server). For some platforms, the latest version 16.02 is available under jessie-backports, but for armhf, it is not: in the table at the bottom of <https://packages.debian.org/jessie-backports/ejabberd>, next to armhf is the version 16.01 listed in red, instead of 16.02 in green as for amd64 etc. What do these colours mean, and why the difference in versions? Will 16.02 become available for armhf as well in the (near) future, or is this an indication of a more serious problem?
Jessie's older version 14.07 does not offer the features I need, and 16.01 does not run at all; hence my hopes are pinned on 16.02.
I just wanted to know if i download Debian Squeeze linux-source-2.6.32 from packages.debian.org and try and compile it in debian lenny using lenny's packages will the build succeed ?
View 6 Replies View RelatedI'm attempting to install ndiswrapper-dkms package. The installation fails due to the following error:Module build for the currently running kernel was skipped since the kernel source for this kernel does not seem to be installed. dpkg reports that the source is installed
[code]....
I've been searching google for the past couple of days but haven't found anything specific. Any ideas to get me going in the right direction?
uname -a reports
Linux debtop 2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686 GNU/Linux
I've got a fresh install of Squeeze on a 32bit host and I have been unable to boot into XEN/dom0.The Xen Kernel is "linux-image-2.6.32-5-xen-686" (pvops) and Hypervisor is xen-hypervisor-4.0-i386.The system default installed with grub2.It boots quite happily in normal mode, using the above Kernel, but just reboots itself if I try run it as Xen/dom0. (reboots within a second of pressing <enter> ... there is no messages displayed on the screen that I have noticed)The relevant menu (generated by /etc/grub.d/20_linux_xen) entry for running Xen is as below;
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN 4.0-i386' --class debian --class gnu-linux --class gnu --class os --class xen {
insmod part_msdos
[code]....
I'm using Squeeze amd64, installed latest kernel 2.6.38 from backport yesterday. Just now try to check for any update but failed, these messages show.
View 2 Replies View RelatedAfter upgrading to Ubuntu 9.10 I no longer get a login prompt when switching to console mode e.g. (CTRL+ALT)-F1. Instead i just get blinking cursor in the top left corner. Key strokes are printed the screen but otherwise nothing happens. I can switch back and forth between X and the console normally.
Where are the consoles configured, and is there a corresponding log somewhere i can check? Has anyone had similars problem?
My system is an old Amilo Pro laptop with a VIA 800 compatible chip-set.
I installed Ubuntu 10.10 on my 32gb flash drive. Just one large partition for the OS and about a gig for swap. Worked fine. Booted to USB on two computers and a laptop at home. Fine. Figured I'd try it on a work pc for the sake of testing a random computer. Well I stick the drive in, boot up, select usb from the boot menu and bam Ubuntu starts loading. I look away, it's cool ubuntu's loading. Well I turn back and it's a black screen. It's "<username>@whatever login:" or something close.
I use the username and password I created during installation and what I used to login to the computer like fifty million times while booted into Ubuntu. Well, invalid login. The first time I installed this OS on this drive I updated it through the update manager and rebooted. Next thing I know I type in my username and password, hit enter, and bam black screen, some stuff, then im asked to login again. Now after this next iteration I am faced with yet another faulty login screen. What is up with this OS?
Are the 1.3 Wine packages availible at [url] compatible with the Squeeze kernel? What about future updates to the packages there?
View 3 Replies View RelatedUbuntu has stopped booting correctly. Now it shows the Ubuntu logo and then, instead of GDM, it shows a console login prompt. How do I go about troubleshooting this?'m in Windows XP (which I like a lot better than Ubuntu, because it actually works) but all my files and work are on my Linux partition.
View 9 Replies View RelatedHi,I'm using a Dell Lattitude D620 laptop. I just installed the latest kernel 2.6.38 in my Squeeze amd64 :
Output of uname -r
2.6.38-bpo.2-amd64
Now I'm running on new kernel,everything seems fine except my wifi ( now I'm connected through ethernet ). Before I do the process with the guide in http://wiki.debian.org/wl to activate my wifi,I'd like to ask for some advice here,is this latest kernel support my wifi card? If yes,how to activate it?
Output of lspci :
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
[code]....
Sometimes a kernel image seems to have the same version as the backported kernel image, for example:
linux-image-2.6.32-bpo.5-amd64
linux-image-2.6.32-5-amd64
What are the differences between the two?
Debian Lenny worked just great. That was my first experience of Debian. The installer recognised all my hardware and the system was soon up and running brilliantly with a few tweaks. Confident of Debian's reliability, I decided to move to Debian 6 and did a fresh install, with downloads of the new operating system rather than a distribution upgrade. The installation routines have not worked for the same computer system. I don't know if its hardware not being recognised by Debian 6 that were recognised without a problem by Debian 5??
At first, the boot-up flipped at "Waiting for /dev to be fully populated," there was a kernal panic then Debian disappeared. No signal was sent to the monitor and I had to switch off the computer manually
I was able to look into the Debian 6 OS from Arch Linux, installed on different partitions of the same hard-drive. I am able to overwrite the Debian files as root from Arch.
My i686 machine has PATA IDE drives.
Why are 2) dbus and the 3) avahi-demon failing? I need to get them started first so that I can get an internet connection and try and correct the problem with X and the wrong Nvidia driver. Is there some configuration I can do either from Arch, where I am now, or the bash prompt on Debian? Thanks in advance.
After reinstalling Squeeze's base system, the console font is too small to read comfortably. I tried to pass the kernel parameter vga=0x303 without success. After init starts the font reverts to a very small font that I cannot read comfortably on my 17 inch TFT LCD monitor.
View 7 Replies View RelatedInstalled Squeeze from a CD image (lxde) but the desktop environment did not appear, only a text login. Downloaded lxde using aptitude, but haven't a clue as to how to activate it from the console, or anything else other than aptitude, for that matter. Openbox is part of lxde, and with my Lenny I could bring it up from the command line with the command <openbox>; not now. Can't get on to the internet, so am writing this with Damn Small Linux on a CD.
View 2 Replies View Related