Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
no GUI after dist-upgrade from stable to testing [solved]
Re: upgrade to wheezy
Hello, I only know how to use apt-get, but I will try running aptitude. I'm currently trying to figure out how to mail myself the output of apt-get dist-upgrade so I can post it here.
Does the quick and painless reinstall erase all config files?
Does the quick and painless reinstall erase all config files?
- dilberts_left_nut
- Administrator
- Posts: 5346
- Joined: 2009-10-05 07:54
- Location: enzed
- Has thanked: 13 times
- Been thanked: 66 times
Re: upgrade to wheezy
Yes.
You can, however, back them up if you wish.
As for the outputs, can you not just save them to your windows partition the read/upload them from there?
(you would need to have ntfs-3g installed already though ...)
.. or to a usb stick?
You can, however, back them up if you wish.
As for the outputs, can you not just save them to your windows partition the read/upload them from there?
(you would need to have ntfs-3g installed already though ...)
.. or to a usb stick?
AdrianTM wrote:There's no hacker in my grandma...
- dilberts_left_nut
- Administrator
- Posts: 5346
- Joined: 2009-10-05 07:54
- Location: enzed
- Has thanked: 13 times
- Been thanked: 66 times
Re: upgrade to wheezy
If it doesn't automount under /media/something then make a dir, say /mnt/usb and do
sdX being the designation of your usb, as reported by dmesg or such.
Code: Select all
mount /dev/sdX1 /mnt/usb
AdrianTM wrote:There's no hacker in my grandma...
Re: upgrade to wheezy
I did finally get the output of apt-get dist-upgrade posted here:
http://sprunge.us/gAhR
Any suggestions based on these error messages? I get the same results when using the -f flag.
http://sprunge.us/gAhR
Any suggestions based on these error messages? I get the same results when using the -f flag.
Re: upgrade to wheezy
I didn't read the older posts but did you runlinux001 wrote:I did finally get the output of apt-get dist-upgrade posted here:
http://sprunge.us/gAhR
Any suggestions based on these error messages? I get the same results when using the -f flag.
apt-get -f install
?
or else run
aptitude full-upgrade
instead of apt-get and it should offer you some solutions
(note that those errors during upgrading may be due to you having some package(s) on hold, make sure everything is 'normal')
Re: upgrade to wheezy
apt-get -f install gave the same errors as apt-get dist-upgrade and apt-get -f dist-upgrade
aptitude full-upgrade seems to offer a solution. It produced hundreds of lines of output and asked me if I would like to proceed. Before I proceed, could you please verify that my sources.list file looks ok?
http://sprunge.us/JaGK
According to this guide, testing does not receive security updates. I interpret this to mean that the following line should be omitted:
deb http://security.debian.org/ <version>/updates main contrib non-free
Also, the squeeze-updates / wheezy-updates line ("volatile") must be omitted? Thank you.
aptitude full-upgrade seems to offer a solution. It produced hundreds of lines of output and asked me if I would like to proceed. Before I proceed, could you please verify that my sources.list file looks ok?
http://sprunge.us/JaGK
According to this guide, testing does not receive security updates. I interpret this to mean that the following line should be omitted:
deb http://security.debian.org/ <version>/updates main contrib non-free
Also, the squeeze-updates / wheezy-updates line ("volatile") must be omitted? Thank you.
- dilberts_left_nut
- Administrator
- Posts: 5346
- Joined: 2009-10-05 07:54
- Location: enzed
- Has thanked: 13 times
- Been thanked: 66 times
Re: upgrade to wheezy
Unsure of the details for security or volatile wheezy repo's, but just use the one you have until you are sorted, one problem at a time.
It looks very much like you have not done 'aptitude update' to update your package lists, or fetching them has failed.
It looks very much like you have not done 'aptitude update' to update your package lists, or fetching them has failed.
AdrianTM wrote:There's no hacker in my grandma...
Re: upgrade to wheezy
I completed aptitude full-upgrade. How do I undo the single user lock to try if the GUI works? Thanks.
- dilberts_left_nut
- Administrator
- Posts: 5346
- Joined: 2009-10-05 07:54
- Location: enzed
- Has thanked: 13 times
- Been thanked: 66 times
Re: upgrade to wheezy
So updating the package list solved the problem?linux001 wrote:I completed aptitude full-upgrade. How do I undo the single user lock to try if the GUI works? Thanks.
Code: Select all
update-rc.d gdm3 enable
AdrianTM wrote:There's no hacker in my grandma...
Re: upgrade to wheezy
I'm not sure yet, there were lots of error messages during the upgrade, but I will see if the GUI works.
Thanks for the command. I was debating between the following two:
update-rc.d gdm3 defaults
update-rc.d gdm3 enable
Thanks for the command. I was debating between the following two:
update-rc.d gdm3 defaults
update-rc.d gdm3 enable
- dilberts_left_nut
- Administrator
- Posts: 5346
- Joined: 2009-10-05 07:54
- Location: enzed
- Has thanked: 13 times
- Been thanked: 66 times
Re: upgrade to wheezy
Actually I've never used those commands much so I would do what the manual says rather than relying on my memory ...
AdrianTM wrote:There's no hacker in my grandma...
Re: upgrade to wheezy
Thanks. After issuing those commands, I was told that dependency based boot sequencing was in effect. But after rebooting the computer, nothing happened. Is there something else I could try?
Re: upgrade to wheezy
Did you search this forum for similar situations (no keyboard response)?
I think other people had this kind of problems.
The only time I think I had something similar (I use sid since the installation) was when udev had a bug and we had to delete /run, but that was quite a while ago and udev has been upgraded a lot since then.
If it's something related with the video driver, you could try appending nomodeset to GRUB's boot line but then it's better if you say (if you didn't already) something about the hardware.
I think other people had this kind of problems.
The only time I think I had something similar (I use sid since the installation) was when udev had a bug and we had to delete /run, but that was quite a while ago and udev has been upgraded a lot since then.
If it's something related with the video driver, you could try appending nomodeset to GRUB's boot line but then it's better if you say (if you didn't already) something about the hardware.
Re: upgrade to wheezy
Thanks secipolla. Here is a copy of my hardware (lspci). I will look around the forums for similar issues.linux001 wrote:Here, by the way, is a copy of my lspci dump:
Code: Select all
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b4) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b4) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b4) 00:1c.7 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 8 (rev b4) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 04) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06) 03:00.0 System peripheral: Ricoh Co Ltd Device e823 (rev 04) 08:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000
Re: upgrade to wheezy
Hello. I enabled boot logging by bootlogd and this is the content of /var/log/boot
Everything seems to be ok. There are some other messages that didn't get logged. I will copy these down manually by pausing the output. I will also try manually starting GNOME by issuing sudo /etc/init.d/gdm start. Please let me know if there are any other suggestions on how to get out of the console.
Code: Select all
Tue Jan 31 17:37:25 2012: Setting parameters of disc: (none).
Tue Jan 31 17:37:25 2012: Setting preliminary keymap...done.
Tue Jan 31 17:37:25 2012: Activating swap...done.
Tue Jan 31 17:37:25 2012: Checking root file system...fsck from util-linux 2.20.1
Tue Jan 31 17:37:25 2012: /dev/sda5: clean, 324118/3055616 files, 4060080/12206848 blocks
Tue Jan 31 17:37:25 2012: done.
Tue Jan 31 17:37:25 2012: Loading kernel modules...done.
Tue Jan 31 17:37:25 2012: Activating lvm and md swap...done.
Tue Jan 31 17:37:25 2012: Checking file systems...fsck from util-linux 2.20.1
Tue Jan 31 17:37:25 2012: done.
Tue Jan 31 17:37:25 2012: Mounting local filesystems...done.
Tue Jan 31 17:37:25 2012: Activating swapfile swap...done.
Tue Jan 31 17:37:25 2012: Cleaning up temporary files....
Tue Jan 31 17:37:25 2012: Setting kernel variables ...done.
Tue Jan 31 17:37:25 2012: Cleaning up ifupdown....
Tue Jan 31 17:37:25 2012: Setting up networking....
Tue Jan 31 17:37:25 2012: Configuring network interfaces...done.
Tue Jan 31 17:37:25 2012: Starting portmap daemon....
Tue Jan 31 17:37:25 2012: Cleaning up temporary files....
Tue Jan 31 17:37:25 2012: Setting up ALSA...done.
Tue Jan 31 17:37:25 2012: Setting console screen modes.
Tue Jan 31 17:37:25 2012: ^[[9;30]^[[14;30]Skipping font and keymap setup (handled by console-setup).
Tue Jan 31 17:37:25 2012: Setting up console font and keymap...done.
Tue Jan 31 17:37:25 2012: Setting sensors limits.
Tue Jan 31 17:37:25 2012: INIT: Entering runlevel: 2
Tue Jan 31 17:37:25 2012: Using makefile-style concurrent boot in runlevel 2.
Tue Jan 31 17:37:25 2012: Starting portmap daemon...Already running..
Tue Jan 31 17:37:25 2012: Enabling additional executable binary formats: binfmt-support.
Tue Jan 31 17:37:25 2012: Starting enhanced syslogd: rsyslogd.
Tue Jan 31 17:37:25 2012: Enabling power management...done.
Tue Jan 31 17:37:25 2012: PulseAudio configured for per-user sessions ... ^[[33m(warning).^[[39;49m
Tue Jan 31 17:37:25 2012: Starting deferred execution scheduler: atd.
Tue Jan 31 17:37:25 2012: Starting anac(h)ronistic cron: anacron.
Tue Jan 31 17:37:25 2012: Starting periodic command scheduler: cron.
Tue Jan 31 17:37:25 2012: Starting system message bus: dbus.
Tue Jan 31 17:37:25 2012: Loading cpufreq kernel modules...done (acpi-cpufreq).
Tue Jan 31 17:37:25 2012: CPUFreq Utilities: Setting ondemand CPUFreq governor...CPU0...CPU1...CPU2...CPU3...done.
Tue Jan 31 17:37:25 2012: Starting network connection manager: NetworkManager.
Tue Jan 31 17:37:25 2012: Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
Tue Jan 31 17:37:25 2012: Starting bluetooth: bluetoothd.
Tue Jan 31 17:37:25 2012: saned disabled; edit /etc/default/saned
Tue Jan 31 17:37:26 2012: Starting MTA: exim4.
Tue Jan 31 17:37:26 2012: Starting ACPI services....
Tue Jan 31 17:37:26 2012: Starting Common Unix Printing System: cupsd.
Tue Jan 31 17:37:26 2012: Starting acpi_fakekey daemon...done.
Re: upgrade to wheezy
Here are the unlogged boot messages:
Code: Select all
modprobe: module unix not found in modules.dep
INIT: version 2.88 booting
Using makefile-style concurrent boot in runlevel S.
Starting the hotplug events dispatcher: udevd.
Synthesizing the initial hotplug events...done.
Waiting for /dev to be fully populated... [ 4.085842] [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH
Re: upgrade to wheezy
Results of the following commands:
Nothing happened when the last two commands were executed.
Code: Select all
# /etc/init.d/gdm start
No such file or directory
# /etc/init.d/gdm3 start
# /etc/init.d/gdm3 restart
Re: no GUI after dist-upgrade from stable to testing/wheezy
I wonder if your upgrade removed a pile of stuff such as GDM. Try startx.
If I'm right - and there's no reason why I should be - you could treat this as a minimal install and start installing packages or meta-packages one at a time to see what builds up. Start with the kernel linux-image-3.1.0-1. Boot and make sure it works. Then xorg. Test it. Then your desktop or window manager. Again, test it. Assuming that your sources are good I would expect Apt to sort out the pieces.
If I'm right - and there's no reason why I should be - you could treat this as a minimal install and start installing packages or meta-packages one at a time to see what builds up. Start with the kernel linux-image-3.1.0-1. Boot and make sure it works. Then xorg. Test it. Then your desktop or window manager. Again, test it. Assuming that your sources are good I would expect Apt to sort out the pieces.
Re: no GUI after dist-upgrade from stable to testing/wheezy
Thanks Bulkley -- startx worked! How to I instruct the GUI to start by default?
Earlier, I issued the command update-rc.d gdm3 disable in order to enter single user mode, so this may be the reason the GUI is not starting by default. I have tried reversing this command with update-rc.d gdm3 enable and update-rc.d gdm3 defaults, and these commands indicate to me that dependent boot sequencing is in effect, but I still have nothing but a console on reboot.
Earlier, I issued the command update-rc.d gdm3 disable in order to enter single user mode, so this may be the reason the GUI is not starting by default. I have tried reversing this command with update-rc.d gdm3 enable and update-rc.d gdm3 defaults, and these commands indicate to me that dependent boot sequencing is in effect, but I still have nothing but a console on reboot.