Debian Installation :: Overwrite Wheezy With Jessie

Jun 20, 2015

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?

View 11 Replies


ADVERTISEMENT

Debian Installation :: Upgrade From Squeeze To Wheezy Or Jessie

Jul 28, 2015

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 Related

Debian Installation :: Failed Wheezy To Jessie Upgrade (cannot Boot)

Aug 13, 2014

I 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.

View 12 Replies View Related

Debian Installation :: Segmentation Fault When Upgrading From Wheezy To Jessie

May 11, 2015

A few days ago I bought a Raspberry PI B with Debian Wheezy (7.0 - I think) on it. Before installing a media centre on it I wanted to do some basic configuration/upgrade and decided to upgrade to Debian Jessie. I followed the instructions provided on [URL] .....

Before moving to Jessie I have upgraded the original Wheezy; after the upgrade the version was 7.8. Everything went well till I executed "apt-get dist-upgrade". Errors where generated. As suggested I tried the "apt-get -f install"; but it did not go smoothly either. However, so far, I am accessing the desktop and everything seems fine (although I did not do anything fancy yet). The version recorded is 8.0. Thus, should I worry about the error messages generated?

Please find the log file here: [URL] ......

Note that I put the log file on Google Drive because each time I clicked on "add file" in the "Upload Attachment" tab when editing this message I got:

Internal Server Error:
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, forum-admin@forums.debian.net and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.

View 7 Replies View Related

Debian Installation :: Broken Grub After Wheezy To Jessie Upgrade

Jun 2, 2015

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.

View 3 Replies View Related

Debian Installation :: Dist-upgrade From Wheezy (using Systemd) To Jessie Hangs

Nov 19, 2014

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.

View 10 Replies View Related

Debian Installation :: Upgrade From Wheezy To Jessie Modify Print Drivers?

Feb 9, 2016

Does upgrade from wheezy to jessie modify print drivers....

View 1 Replies View Related

Debian :: Spring On Wheezy But Not Jessie

May 19, 2015

I've had a weird issue recently with Java/Spring. Basically, it would work on all machines but my trusty Debian box. Macs for devs, Ubuntu for production and some devs have it too. This annoyed me, because of course Debian is the greatest and it must work there too! Also, Java is based on the whole write once run anywhere concept, I have never really had a problem with code behaving differently on different Java installs of the same version, even on completely different OSs it seems to behave itself very well. URL....

I moved up to Jessie and the problem goes away. I can only conclude that some library that is called by Java got upgraded, somehow influences the order in which Spring resolves its dependencies. Probably the fact that other devs build on Ubuntu and have got it working there, and the upgrade to Jessie brings my libs more in line with what Ubuntu will be running has done the trick.

View 0 Replies View Related

Debian :: No Internet After Upgrade From Wheezy To Jessie

May 27, 2015

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?

View 14 Replies View Related

Debian :: Wheezy To Jessie Upgrade Will Not Boot

May 28, 2015

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?

View 1 Replies View Related

Debian Multimedia :: Upgraded To Jessie From Wheezy - No Sound

Jan 22, 2015

I upgraded to Jessie today and found that I have no sound.

Code: Select all# uname -a
Linux ath 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) x86_64 GNU/Linux

There is no sound card on the motherboard. Sound worked previously through HDMI from a Nvidia GTX570

Code: Select all# lspci|grep Audio
09:00.1 Audio device: NVIDIA Corporation GF110 High Definition Audio Controller (rev a1)

Code: Select all# aplay -l
aplay: device_list:268: no soundcards found...

[code]....

View 8 Replies View Related

Debian :: Dedi Server Don't Reboot After Wheezy / Jessie Upgrade

Jul 26, 2015

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

View 6 Replies View Related

Debian :: Upgraded From Wheezy To Jessie / Now Only GNOME Classic Works

Apr 27, 2015

I did an in-place upgrade to Jessie today and I can only get the GNOME Classic desktop, which I have to select when I log in. I had started to get used to the default desktop in Wheezy, so I'd like it back if possible. When I select gnome system default, I get my desktop, but no menus or anything I can click on at all. All I can do is ctrl-alt-delete and reboot or shutdown. I run it on a Lenovo Ideapad U410.

View 8 Replies View Related

Debian Configuration :: Udev Static Device Change From Wheezy To Jessie

Sep 9, 2015

I am using a 3rd party kernel driver that does not support udev properly. When I was using wheezy I placed the required device files in /lib/udev/devices.

The udev in jessie does not appear to support this. Is there any way to have udev create these device files or will I have to create then using a script at boot-up?

View 1 Replies View Related

Debian Multimedia :: Upgraded To Jessie From Wheezy - Sound Plays On Everything But Browsers

Dec 25, 2014

I just installed wheezy and upgraded to jessie. I had previously gotten sound working in wheezy by installing the flashplugin-nonfree and flashplugin-nonfree-extrasound packages, after configuring my headset in system settings. However, now I can't get sound to play in firefox. I've installed flashplugin-nonfree, flashplugin-nonfree-extrasound, and pulseaudio, still without luck. The volume is turned all the way up in alsamixer, sound tests play fine, and I can play music in VLC without any problems. This leads me to believe it's not a problem with drivers, but with some package I'm missing that will allow firefox to play sound. Sound wasn't working in the default video player either, before I installed the flash plugin. Is there something I'm missing?

Also, sound doesn't play on Konqueror either (KDE browser), which seems to indicate it's a problem with flash and not with firefox itself. After removing the flash plugin and installing pepperflashplugin-nonfree to ensure the pepper plugin was used instead of flash, sound still would not play in chromium, so I reinstalled the flash plugin and still don't have sound in any browser.

View 1 Replies View Related

Debian Hardware :: Android Phone No Longer Mounting Since Wheezy -> Jessie

Aug 7, 2015

Used to be, when I connected my phone and turned on USB Storage, it would automount, and I'd get a popup window asking me what I wanted to do (open and view files, or import photos with gthumb). I would just choose open and view files, move photos, music, etc. back and forth...

I would see the device listed in pcmanfm or thunar. Now, nothing happens. I do not get the popup, nor see the device in any file manager, etc. When I do fdisk -l, I do not see the phone listed, but when I do lsusb, I do see it.

Code: Select allBus 008 Device 067: ID 0482:0734 Kyocera Corp.
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

It's a Kyocera Hydro Elite, an android device, set for USB Mass Storage upon connection. The phone knows when it's been connected and gives me the option to turn on the mass storage, which used to trigger the popup on the computer, but the computer no longer responds.

I have thunar-volman and mtp-tools installed.

I don't seem to have any relevant entry in /etc/fstab. Not sure if I did before upgrading to jessie from wheezy or not... I don't believe so...don't think an upgrade would wipe anything from there.

Why I'm not getting access to the phone now? Or how I can mount it without knowing it's location from fdisk? I do not use gnome, but rather plain openbox.

View 12 Replies View Related

Debian Hardware :: Lenovo ThinkPad SL410 - Upgraded Wheezy To Jessie And Lost USBs

May 8, 2015

I run Debian with Gnome on a beat up workhorse ThinkPad. I upgraded to Jessie last week with just one issue. Before the upgrade, I could plug in a USB drive (I use a couple of WD MyPassports most often) and they would mount, read, and write without a hitch.

Since the upgrade, when I plug in a USB drive, the file manager (3.14.1) sees the drive, but when I click on the drive to access/mount it, I receive a dialog box reading: Oops! Something went wrong. Unhandled error message: Error when getting information for file '/media/user/MyPassport1': Input/output error.

If I hit the little “eject” button in the file manager, then mount the drive as root from a command prompt [e.g., mount -t ntfs-3g /dev/sdb1 /media/external] I can run a directory of the drive, but ls -l /media/external fails. From the command prompt I am unable to perform reads or writes to the drive.

Rebooting into recovery mode (i.e., without Gnome), I get the same behavior with CLI messages reporting I/O errors with the drive. I can run a directory, but ls -l, reads, and writes fail.

This behavior is the same on all three USB ports. It is not limited to these MyPassport devices.

The drives work flawlessly on another headless machine upgraded to Jessie the same day. And on another still running Wheezy.

If I boot the ThinkPad from a live CD (Mint 14, I believe) the USB drives mount, read, and write fine.

My BIOS is up to date, 1.52.

lspci -v says this about USB ports:

Code: Select all00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) (prog-if 00 [UHCI])
   Subsystem: Lenovo Device 20f0
   Flags: bus master, medium devsel, latency 0, IRQ 23
   I/O ports at 1880 [size=32]
   Capabilities: [50] PCI Advanced Features
   Kernel driver in use: uhci_hcd

[Code] .....

View 4 Replies View Related

Debian Installation :: Wheezy To SSD Drive?

Jan 6, 2013

Just 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?

View 7 Replies View Related

Debian :: Installation Of The Liquorix Kernel In Wheezy

Jun 15, 2011

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]

View 2 Replies View Related

Debian Installation :: Moving From Squeeze To Wheezy?

Apr 2, 2011

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 Related

Debian Installation :: Upgrade To Wheezy Successful But No CLI And No GUI?

Jun 9, 2011

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 View Related

Debian :: Nautilus-dropbox Installation On Wheezy

Nov 9, 2014

I 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?

View 11 Replies View Related

Debian Installation :: Wheezy - Installer Failed On Grub

Nov 23, 2014

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?

View 2 Replies View Related

Debian Installation :: Wheezy 7.8 UEFI Boot Commands

Feb 6, 2015

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?

View 10 Replies View Related

Debian Installation :: Install Ubuntu 14.04 Alongside Wheezy

Apr 23, 2015

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.

View 6 Replies View Related

Debian Installation :: Mixed Wheezy With Sid Now Have Broken Packages

May 6, 2015

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?

View 1 Replies View Related

Debian Installation :: GPG Error When Update From Squeeze To Wheezy

Jan 7, 2016

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]....

View 9 Replies View Related

Debian Installation :: Wheezy Sources Not Working After Install?

Apr 7, 2011

I have just installed Wheezy after repartitioning and had to set up my sources list myself as (most of it) was not done for me. I have just added the main official repository,security updates and the multimedia repository. To be honest I'm not sure if any of them are working when I do an update in aptitude, I think the multimedia one might be. The CD ROM isn't even working despite the fact I have done apt-cdrom add.I am getting the following when run aptitude update:

Ign cdrom://[Debian GNU/Linux testing _Wheezy_ - Official Snapshot i386 CD Binary-1 20110328-05:16] wheezy InRelease
Ign cdrom://[Debian GNU/Linux testing _Wheezy_ - Official Snapshot i386 CD Binary-1

[code]....

View 6 Replies View Related

Debian Installation :: Wheezy Installer Not Recognizing USB Keyboard

Jul 6, 2011

I am using Wheezy netinstall on a USB stick. The machine has an Intel DH57JG motherboard, USB keyboard, and no optical drive. The installer loads to the initial screen OK, but the keyboard is not active. This problem has been reported for several years and was supposed to be fixed by kernel 2.6.32, yet here it is. What can I do?

One suggestion has been to disable/enable USB legacy support in the BIOS. It is enabled by default. If I disable it, the installer doesn't load. This keyboard works fine on other Linux machines and on the BIOS in this machine. I read there was a problem with Cherry keyboards and the Squeeze installer. This keyboard is not a Cherry but does have Cherry keyswitches.

View 1 Replies View Related

Debian Installation :: Cannot Boot Wheezy Live Usb-hdd / Solve It?

Jul 19, 2011

I've created my own wheezy live usb-hdd using:# lb config -a i386 --mode debian --distribution wheezy --linux-flavours 686 -b usb-hdd --bootloader syslinux --memtest none -p xfce
P: Considering defaults defined in /etc/live/build.conf
P: Creating config tree
# lb build
The binary.img was created.
Now if I try to boot from this image using qemu, I get a message "No bootable device"
If I check this main partition using gparted, the flag is "lba" instead of "boot".
Even doesn't work if try to change to "boot".
How to solve this problem?

View 13 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved