I upgraded one of my Squeeze installations to Wheezy, but after selecting it in grub, nothing is displayed on screen: no CLI and no GUI. I tried Ctrl + Alt + F[1-7] and I got nothing. My laptop is Acer Aspire 7715Z. I am attributing this to module as there seems to be disk activity, but without a screen, I cannot be certain.
View 14 Replies
is it possible to simulate upgrading a Squeeze installation to a Wheezy or Jessie installation, on a OVH server ?I would like simulate upgrading server, and if not problems, upgrading in real time.I don't do that manipulation, and I don't do mistakes on a production server.
View 2 Replies View RelatedI upgraded from deb7 to deb8, but am no longer able to boot. After passing the grub boot menu, the following messages are displayed:
Code:
Select allLoading, please wait...
[ 6.065713] systemd-fsck[148]: /dev/sda1: clean, 428644/1310720 files, 410616
9/52442880 blocks
[ 7.480551] Error: Driver 'pcspkr' is already registered, aborting...
[ 8.692700] systemd-fsck[341]: /dev/sda5: clean, 145485/6176768 files, 17407409/24695552 blocks
[ 18.066215] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated). Use CAP_NET_ADMIN and alias netdev- instead
_
The screen then clears and an underscore is displayed as the sole character at the top left position of the screen. The system hangs at this point. During installation, I rejected two changed files: /etc/init.d/bootlogd and /etc/libreoffice/sofficerc. For both, I opted to keep the installed version (the default choice of the installer) rather than replacing with the new version. The first might be related to the problem, although it seems to be responsible only for logging the boot process, and I would not expect this to compromise booting.
In case this information is useful, sda1 is mounted at /, sda2 is swap space, sda3 is extended, and sda5 is a logical partition mounted at /home.
I am able to boot into rescue mode, but other than that the system is not usable. Unfortunately, no useful error messages are given to aid in diagnosing the problem.
I've changed my /etc/apt/sources.lst file to use "jessie" repositories instead of "wheezy". I then ran synaptic and updated everything (there were loads of packages, something like 2000 to update).
After this I rebooted. The grub menu shows as usual with the background image I'd set and the operating systems as usual (including Windows 7) however there is no longer a 5 second countdown and when I select *any* menu option, it asks for a username and password.
I don't know what username and password it's asking for as I never used to have one set!!! I did have a username and password set up so that if you wanted to edit a grub menu option so I tried that but to no avail.
I'm using MBR/BIOS not EFI.
Recently I upgraded my machine from wheezy to jessie.
Everything went smooth until the point that I restarted the node.
During startup I'm getting the following message which is flooding the screen:
Code: Select allsystemd-journald[296]: Failed to forward syslog message: Connection refused
After waiting a long time (the message above still continues to flood the screen), I'm being prompted with the following:
Code: Select allGive root password for maintenance (or type Control-D to continue):
If I press Ctrl+D the boot process continues and finally boots normally.
What I can do to avoid pressing Ctrl+D during the boot process?
I'm assuming that it must be a startup service which is failing but I'm unable to trace which exactly is that.
I'm attaching the full log [URL] ....
I have done on previous releases, but this time it hangs on me. It's "only" a Virtualbox, so I can reproduce it.
The wheezy already runs systemd, and is fully updated to to latest packages. Does not run any graphical.
Edits the source.list and does
$ apt-get update
$ apt-get upgrade # Did on one upgrade
$ apt-get dist-upgrade
It starts to upgrade (complains about missing version in libpgp-error), libc is installed, but at some point the systemd is running at high CPU and a dpkg seems to be stalled.
Should I disable systemd on wheezy before? This might not have been tested so much.
Does upgrade from wheezy to jessie modify print drivers....
View 1 Replies View RelatedI hit some trouble upgrading from FC 10 to FC 12 using the netinst CD. I had previously successfully upgraded the system from FC5 to FC10 with the same method - that time everything went well. At first the upgrade went well - the installation program found my FC installation and detected the partitions right. The problem appeared when about 90% of the rpm's were installed. Anaconda was complaining about a fatal error with a package and quit.
After rebooting and restarting the installation program it does not recognize my partitions anymore and suggests I'd format them for a fresh installation. As all my data is there I'd rather not do that. I then rebooted again and chose "Repair" from the installation menu. I got to the console and noticed that all partitions mounted cleanly and all the data seems to be there. Trying to reboot from the hard disk almost works. The system gets up, goes through grub, gets the kernel running and mounts the disks but fails to launch Xorg.
I get to a terminal login from here by pressing Ctrl+Alt+F2. When I type the user name and press enter the terminal seems to crash - does not ask for the password but simply returns to the user name query. An error message flashes just after pressing enter but too quickly for me to read. When I boot from CD again and go to the terminal via the "Repair" option the previous events can be seen from /var/log/messages. Xorg tries to start and stops trying after a certain amount of failures. After that it says this:
Code:
init: prefdm main process (2123) terminated with status 1
init: prefdm main process ended, respawning
init: prefdm respawning too fast,stopped
[code]....
My best guess is that this happens because the upgrade was aborted before it completed and hence some necessary rpm's were left out. I figured I could possibly fix this by updating the packages with yum from the terminal if I got to log in. What should I do now? Could I for example try and manually copy some missing files to the disk as I can access it via the repair option?
what the odds are of successfully installing from 9.10 to 10.04 without something nasty happening?
View 7 Replies View RelatedI got "stuck" with stable up to now and want to upgrade to Wheezy. But, although I've done this before, I'm having a dependency problem I wanted to ask about before breaking my system somehow. This is the /etc/apt/sources.list, ready for Wheezy:
[URL]
So, I regularly use aptitude as my package manager. After updating the database with aptitude update, trying aptitude full-upgrade gives me a huge of conflicts.
[code]....
But, if I use apt-get dist-upgrade, I get no conflicts. if I dist-upgrade with apt-get, will that affect my daily usage of aptitude (which I prefer)? I know APT is a single database and apt-get and aptitude are just different interfaces, but I guess differences might rise when marking packages as automatically or manually installed.
I upgraded my Wheezy 7.8 to make sure all packages were installed Before taking the next step to upgrade to Jessie.I upgraded to Jessie and it seemed to run OK....but after reboot I had no network Connection..I checked ifconfig and the wrong network card mac address is being assigned to the wrong card....?I have a clonezilla server on my server, so this was my network interfaces before and after upgrade
Code: Select all# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
[code]...
I even checked nano /etc/resolv.conf and sure enough my gateway was the same for my Internet eth0.When I ran ifconfig I could see that the eth0 mac address was set as eth1..I tried to reset my drbl for clonezilla but that only sees the vmware Connection and not my actural cards.. have taken alook at /etc/udev/rules.d/70-persistent-net.rules and the assignment is right but not ifconfig?
With "quiet" removed from the grub linux line, I'm getting the following error messages when the boot hangs up early in the boot process (19.768231 seconds into boot).:
input: HDA NVidia HDMI/DP,pcm=3 as devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input6
input: HDA NVidia HDMI/DP,pcm=7 as devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input7
input: HDA NVidia HDMI/DP,pcm=8 as devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input8
So, is this a NVidia issue or a sound card issue?
Sound is not working perfectly since installation. I fixed it by command: 'alsactl init' every time sound doesn't come out. However, since last week, sound was not working. I suspect it was caused by the 'apt-get upgrade' I did.
Code: Select allroot@debian:~# alsactl init
alsactl: init:1743: No soundcards found...
lspci (only audio)
Code: Select allroot@debian:~# lspci -v
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] SiS7012 AC'97 Sound Controller (rev a0)
Subsystem: Micro-Star International Co., Ltd. Device b002
[Code] ....
It seems I am missing a module/ kernel driver for the sound card
Note: I have testing in sources list but have stable with higher priority. So I should still be in Wheezy
i have an installation of wheezy 7.8 i think. i was facing difficulties in read of matroska video. therefore have decided to installer gstreamer1.0 wich should be resolve my problem. i have added the backports repository in apt sources list. after an apt-get update i launch apt-get install gstreamer1.0 . i have noticed it have starting downloading more file than it needs i concluded that it was a upgrade or something like because the kernel was also updated. after the the packet downloading it has started the installation with some errors related to LOCALE LCC. it has stopped and restarted some services wich is normal. i have closed all others apps and restarted. Here start the hell. after the restart i have passed the kde login screen and after BLACK SCREEN with mouse working.
Alt+F2 don't open the krunner
What i have tried? i have rename the /home/jefcolbi/.cache and back it again, rename /home/jefcolbi/.kde and back it again. next i have tried to check the Xorg config file. i created a new one with X -configure, modified it to feet my system configuration this does not resolve the problem but add another the keyboard is not working in graphical mode.
My system configuration:
Toshiba laptop Satellite Pro L300
Dual core
3gb Ram
graphic card:Mobile Intel(R) GMA 4500MHD
sound card: Intel HD Audio
debian whezzy 7.8 with KDE
Note: everything was working fine before trying to install gstreamer1.O from backports repository
I have upgraded my debian server on april when Jessie came up, but I *forgot* to reboot at this time. As a new kernel* was released this week as a security update, and since my server installed it (via unattended-upgrade on security packages), I rebooted it last night. It never came back online.
I have access to a rescue boot (Ubuntu 12.04 LTS), and tried to analyse the failure (by mounting /sys /dev /proc and /boot and chrooting), but without luck so far.
As it's a dedicated server, I don't have access to the console. What I know :
No log in var/log since the failed reboot. I don't know how to have/find others logs.Previous kernel was 3.2.0-4-amd64, new is 3.16.0-4-amd64, What I tried without luck) :
Change the booting kernel, via update-grub. Tried 3.2, 3.2 with sysvinit and 3.16 rescue mode I think. I should have done it right, but without console it's hard to tell.apt-get update/apt-get upgrade/apt-get dist-upgradeadding nomodeset to kernel load in grubWhat I haven't tried :
update-initramfs, I don't really know why it would block the boot
*linux-image-3.16.0-4-amd64:amd64 3.16.7-ckt11-1+deb8u2
I'm on Wheezy with version 304.117 of the proprietary nvidia driver installed and working, but an application I have needs a newer version of the driver. I'm trying to install the 319.82 version in backports by following the instructions given here, but when I issue the command to install nvidia-kernel-dkms, I get the following:
Code: Select all> sudo aptitude -t wheezy-backports -r install nvidia-kernel-dkms
The following NEW packages will be installed:
libgl1-nvidia-glx-i386:i386{a} nvidia-driver{a}
The following packages will be REMOVED:
libgl1-nvidia-alternatives{u} libglx-nvidia-alternatives{u}
libxvmcnvidia1{u} nvidia-glx{u}
The following packages will be upgraded:
glx-alternative-nvidia glx-diversions libgl1-nvidia-glx
libgl1-nvidia-glx:i386 libnvidia-ml1 nvidia-alternative
nvidia-installer-cleanup nvidia-kernel-dkms nvidia-settings
nvidia-smi nvidia-vdpau-driver xserver-xorg-video-nvidia
The following partially installed packages will be configured:
mint-flashplugin-11:i386
12 packages upgraded, 2 newly installed, 4 to remove and 151 not upgraded.
Need to get 32.3 MB of archives. After unpacking 9,440 kB will be freed.
The following packages have unmet dependencies:
glx-alternative-mesa : Depends: glx-diversions (= 0.2.2) but 0.5.1~bpo70+1 is to be installed.
Internal error: found 2 (choice -> promotion) mappings for a single choice.
Internal error: found 2 (choice -> promotion) mappings for a single choice.
The following actions will resolve these dependencies:
Remove the following packages:
1) glx-alternative-mesa
2) glx-alternative-nvidia
3) libgl1-nvidia-glx
4) libgl1-nvidia-glx:i386
5) nvidia-alternative
6) nvidia-kernel-dkms
[Code] ....
Accept this solution? [Y/n/q/?] q
The mint-flashplugin problem is a separate issue which I've had for a while. I assume that it can be ignored for the purposes of this post.
If I'm reading the aptitude output above correctly, it's telling me that the only way to "resolve" the conflict is by uninstalling all nvidia support, leaving me with no driver at all. Is that right?
System is hanging during boot after a successful fresh install via netinstall disk. Never makes it to any GUI or prompt. However, it does still respond to CTRL-ALT-DEL (not completely frozen).Default debian installation with one exception - KDE checkbox was checked for installation. Everything else was default, with "use full disk with GRUB" option chosen.The boot process appears to hang during the service starts. It appears that the start job for "Create Static De..." is not actually ever completing. I don't know how to troubleshoot that any further than I have.
This is running on hardware, it is not a virtual machine. 480GB SSD, i7, 16GB of RAM, AMD R9 390 (I dunno if this is the problem, but it seems a likely culprit).There are no other disks attached. I have verified successful memtest completions (0 failures) and hard disk is intact and working fine (I have swapped for another disk, and the same thing happens as well).
My skill level with Linux is relatively low. I have proficiency using it and programming for it, but not much in the way of troubleshooting/ installation/ drivers.
Here is an album of "screenshots" (phone photos) of the boot sequence in debug: URL....I tried booting straight to console by removing "quiet" from boot options and changing to "text", but it does not alter the outcome in any discernible way.
I installed Debian Jessie (netinst, daily snapshot) on my Acer Aspire V5-123 laptop in the UEFI mode with the secure boot turned off. everything (network, hardware, partitioning, ...) went smoothly to the last step, but after removing the boot media (USB stick) and rebooting, the firmware could not find the boot device ! The only thing I can think of, is that the EFI boot is not set up properly by Debian installer, but I don't know how to fix it.
View 11 Replies View RelatedI installed Debian Squeeze-testing weekly build today, with CD1 alone. It took 1 Hour 38 minutes to install and configure on my Pentium 4 2.7 Ghz , 1GB ram HP machine. I have some trouble with the installation. Sometimes the desktop just freezes while moving Icons, or opening Xterm. I cannot use Ctrl-Alt-Backspace, OR Ctrl-Alt-Delete keys. I have to physically reboot. Why doesn't Ctrl-Alt-Backspace work on GNOME? Is there a IRC chat for Debian Help and what applications does one use on GNOME for IRC chat?
View 5 Replies View RelatedI have 2 Slackware installs at home, both tracking -current. When 13.37 is officially released I'm considering changing one of those to remain as "stable" for general family consumption. My question is...when the next release comes, how painless and/or successful is the upgrade process. Yes I know of the detailed upgrade instructions by Pat V, and I know I'd have no difficulty executing them.
View 5 Replies View RelatedJust re-installed Wheezy to ssd-drive and noticed that everything works much faster than before. For the older install I made some changes to /etc/fstab (I think) which I found from the web. I don't remember exactly what changes.
Question is: what's the situatation with Wheezys beta4-release and ssd-drive? Do I have to edit something at the moment, or does the installer notice ssd-drive and make everything needed?
I searched the forum about installing the liquorix kernel but I cannot understand why the file /etc/apt/sources.list is not mentioned to invoke the liquorix repository.
Instead, I found: Alternative Performance Kernel for Debian wrote:For anyone interested, just add the following to a sources file (/etc/apt/sources.list.d/liquorix.list): deb [url] or for you scripters, echo "deb [url]
I already have a Notebook with windows (for some reason it needs 3 partitions..) and wheezy. When I installed wheezy I create 2 logical partition inside a primary one: one logical for /home and the other one for filesystem. Now I would like to overwrite wheezy and get get jessie, but without touching windows and home.
I already try to upgrading and it went wrong, so I prefer overwrite, what I have to do during "manual installation" phase?
I'm wondering I've read in some places that if people would like to move from a stable branch of Debian to the testing you can usually just replace the lines in sources.list with the testing release and update and then dist-upgrade. Is this true...and if so is it safe?
View 1 Replies View RelatedI added the following line to my sources.list
Code: Select alldeb [URL] ..... wheezy main non-free
and then after:
Code: Select allapt-get update
I run:
Code: Select allapt-get install nautilus-dropbox
but I got stuck (console freeze) and I had to reboot hoping to sort out somehow...
After reboot I try to apt-get again but I got the following message (my traslation)
Code: Select allE: dpkg was interrupted.
It's necessary to do "sudo dpkg --configure -a" for correcting the problem
So I went in the console again for that command and I get
Code: Select allConfigurazione di nautilus-dropbox (1.4.0-3)...
Dropbox is the easiest way to share and store your files online. [URL] ....
but nothing fruitful seems to happen; and now how to proceed?
I am installing Whezzy and the installer failed to install grub on the MBR of /dev/sda
My disks are
- /dev/sda : the flash drive with the debian ISO
- /dev/sbd : a small SSD for the / partition (sdb1)
- /dev/sdc + /dev/sdd : a software RAID-1 array with LVM for /home, ...
Grub fails to install on /dev/sda which makes sense since this is the flash drive containing the Debian ISO so no MBR.
I already tried to run grub-update manually on /dev/sdb (with chroot /target grub-install --no-floppy --force "/dev/sdb" ).
It works but the system is not directly bootable. I had access to a second PC to read the grub documentation so was able to boot and to fix my system but this is annoying.
Is it normal to see my flash drive as /dev/sda? Could it be that my flash drive is incorrectly detected as a HD?
Is there a way to force the installer to install grub on /dev/sdb?
I have a server in which I'm trying to install Debian into. There's no BIOS, only EFI boot. The vendor locked it down so there's no way to see it or get into it.
The Wheezy 7.8 netinst CD has EFI boot parameters and works on everything I throw it in, except this one server. Booting it up, the code doesn't see the EFI and boots into normal mode, negating every chance to install it (dozens upon dozens of failed installs).
During boot, I press the [TAB] at the Debian Linux installer menu and get the load parameters (/install.amd/vmlinuz vga=788 etc). What parameter can I add to this line to get it to run in UEFI mode so we can install it?
I have a laptop primarily used for a client work. It is running Debian Wheezy, and wish to keep it intact in case I need to do more work for client.
I would like to install Ubuntu 14.04 alongside Debian, and use Ubuntu as a bit of a play/experiment area, etc... HD has lots of space (600GB free), and as far as I can tell Grub is installed in MBR.
I did some searches, and from what I can tell, it sounds like I can just install Ubuntu from ISO file, specify how much space to use (say 400GB), and that's it. This sounds almost too easy. Once I install and restart machine, will there be selection for what Distro to boot.
Without knowing the consequences I added the Sid repository to Wheezy (installed version) in order to install some software. Only much later I discovered that this generated me some mess which does not allow now to install additional software due to library conflicts.
I tried to install some packages needed to build the PhantomJS but here is what I got:
Code: Select allReading package lists...
Building dependency tree...
Reading state information...
build-essential is already the newest version.
g++ is already the newest version.
g++ set to manually installed.
[Code] ....
Is there a way to clean up the mess that Sid introduced and revert back to the Wheezy versions?
I have an old backup, so it would take me much more time to reinstall/reconfigure certain software, so I am looking to alternatives.
Is there a way to check all the packages and find all the potential conflicts and then a way to restore the original Wheezy content?
I try to update the packages before upgrade to wheezy,looks like when I run apt-get update,it shows error as per below:
W: GPG error: http://fosiki.com stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 379393E0AAEE96F6
rat:~# apt-key adv --keyserver keyserver.fosiki.com --recv-keys 379393E0AAEE96F6
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --
[code]....
