I installed Jessie with the RC1. URL...A2) The network install images for testing (jessie) can be found at URL...However, unless you want to test the installer for testing the better choice is to use the stable installer to install a minimal stable system and then upgrade to testing by changing your /etc/apt/sources.list file.
View 8 Replies
I am having this problem on my old 64-bit Debian box (stable's Jessie) box, but nothing seems to fix it from what I saw online like in [URL] ... and other forums. Maybe I missed something?
Code: Select all$ sudo apt-get update
Ign http://dl.google.com stable InRelease
Hit http://dl.google.com stable Release.gpg
Ign http://ftp.us.debian.org jessie InRelease
Hit http://security.debian.org jessie/updates InRelease
[Code] ....
I have installed debian 8.8.1 stable and run updates. When I run the cat release command it shows stretch/sid. I made no changes to the apt/sources list.
What do i have to do so it only updates with the stable release I am planning to use it as a server and only want stable fixes.
After doing Debian's apt-get dist-upgrade from Wheezy/oldstable to Jessie/stable, I decided to try Kernel v4.2.0 instead of v3.16.0-4-amd64 to be even more updated. However, X doesn't work. /var/log/Xorg.0.log showed:
Code: Select allX.Org X Server 1.16.4
Release Date: 2014-12-20
[ 453.305] X Protocol Version 11, Revision 0
[ 453.305] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[code]...
I am just trying to setup my debian 8.2 stable in my Intel(R) Atom(TM) CPU N2600 @ 1.60GHz. The installation goes smooth without any issues. For this system , we are planning to use DUAL display with HDMI & LVDS.
We see that that only HDMI is working and LVDS screen is blank. However, we notice that XRANDR is is showing LVDS as connected
XORG.log:http://pastebin.com/LX9HhRui
KernlogINfo:http://pastebin.com/U2E09iZk
lspci:http://pastebin.com/eBC8wLVu
xrandr:http://pastebin.com/bS5NmAnQ
dmidecode:http://pastebin.com/2qSsHE1s
I update Jessie "stable" 8.2 to 8.4 and now I get 5 minute interval kernel messages:
Apr 18 06:39:52 OraHost kernel: [131985.494726] sdc: unknown partition table
Apr 18 06:45:03 OraHost kernel: [132295.755942] sdc: unknown partition table
Apr 18 06:50:03 OraHost kernel: [132595.946564] sdc: unknown partition table
Apr 18 06:55:13 OraHost kernel: [132906.139327] sdc: unknown partition table
Apr 18 07:00:23 OraHost kernel: [133216.340555] sdc: unknown partition table
I believe this has something to do with an mdadm update which was included in the release. When I configured the array, I didn't partition the disk devices, so maybe that has something to do with it. I am thinking of rebuilding the array and partitioning prior to build, but a quick fix would be referable.
And also something appears to have happened to the raid device since the update.
Prior to update, the array was /dev/md0 - now it is /dev/md/0 which is a symbolic link back to /dev/md0.
mdadm --detail --scan now reports /dev/md/0 where previously it reported /dev/md0
I created a new RAID1 array on a fresh system and immediately after the create, these messages appear at 5 minute intervals.
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 my laptop from Debian Wheezy to Jessie the other day, and just as before my wifi auto-connects to my router, and I can "ping http://www.google.com" just fine, but only for like a minute. Then the Internet access dies, but I'm still connected fine to my router, and I can ping its IP address. If I connect to the router through cable / eth0 everything works just fine, and I have full Internet access.
I assume there is something wonky with how ip address is assigned after the upgrade, how can I fix this, or trouble shoot further?
(I run Gnome desktop, with network manager).
I have an asus eee 1015px, which was running dualboot windows and wheezy with no problems (except the browsers seeming to take up a lot of CPU). Today having backed up everything, I wanted to upgrade to jessie. URL...
Everything seemed to be progressing fine, no strange messages, it took 1 hour for
Code: Select allapt-get upgrade
but maybe that's normal. However, then when I did
Code: Select allapt-get dist-upgrade
It froze at 17.30 with a weird screen. The sort of thing you never want to see on an install, a sad face and blocks instead of text.
pic: URL...
Then it moved on and gave a readout, which seemed pretty ominous
pic: URl...
It then moved and gave a readout, hanging again:
pic3: URl...
Now it seems to be in loop, moving on every 15 minutes or so but always ending up with the same screenful of text shown in the foto below, which ends with the last line reading like this:
Code: Select all[17798.587776] ieee80211 phy0: brcms_ops_bss_info_changed: arp filtering: enabled true, count 1 (implement)
or later
Code: Select all[20209.229273] ieee80211 phy0: brcms_ops_bss_info_changed: arp filtering: enabled true, count 1 (implement)
This pic shows the full screen: URL....
This is baffling for me I'm not very experienced with debian.
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.
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.
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.
On install my wifi was working, but when I rebooted it stopped working.Since then I've tried numerous things to attempt recovery of wifi. No luck so far.
View 14 Replies View RelatedDoes upgrade from wheezy to jessie modify print drivers....
View 1 Replies View RelatedI am trying to install Debian wheezy 7.6 stable, i made a bootable pen drive with netinst but when it arrives the select and install software part i got a error that i cant know what error is because it does not show its name. Just appear a red screen saying that a part in installation fails: Select and install software. I guess that this error is when it is installing tasksel.
View 2 Replies View RelatedI currently have squeeze installed and was wondering how I upgrade to stable 6.0.1, 6.0.2 etc.Would I be correct in doing apt-get update then apt-get upgrade?
View 1 Replies View RelatedI've just install debian squeeze version, or the testing one, but I am not really happy with it. Is not listening me all the time. If I install the debian stable I don't have internet connection. Is it possible to update the kernel somehow using the testing version?
View 12 Replies View RelatedI have been building a debian jessie system reasonably successfully but have come unstuck with libpam-mount. On a previous Ubuntu saucy system I simply installed it, created the appropriate pam_mount.conf.xml file and mounts would happen when users logged on and dismount on logoff. With jessie I can see that there is a libpam-mount package in main but when I try apt-get install it fails. If this package has been obsoleted (as one of the messages indicates might be the issue) what is the jessie way of handling this?
Here is my sources.list
Code: Select alldeb http://mirror.aarnet.edu.au/debian/ jessie main non-free contrib
deb-src http://mirror.aarnet.edu.au/debian/ jessie main non-free contrib
[code]....
Somehow got it partly to work. I have a new installation and I am using the 4.1 kernel now. I can switch on the Radeon chip which is great, but still have some trouble when trying to turn it completely off.
I have an Acer Aspire 4820TG Laptop with:
Core: i7-640M
integrated graphics: Intel
discrete graphics: Radeon Mobility 5650HD
I have installed Debian Jessie. After installing the non-free firmware for my ATI chip (following [URL] .....) so I could use vgaswitcheroo, the system broke.
The problem looks as follows: When I start the system the graphical login screen gets stuck and the console tells me first:
Code: Select allradeon 0000:01:00.0: Userspace still has active objects!
then a lot of numbers, then
Code: Select allradeon 0000:01:00.0: ring 5 stalled for more than 10000 msec
[drm:uvd_v1_0_ib_test] *ERROR* radeon: fence wait failed (-35).
[drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on ring 5 (-35).
and this repeats once (or twice?) until several new messages arrive.
Those pause at
Code: Select allFixing recursive faul but reboot is needed !
Then again lots of more error messages until the everything freezes, with the last message
Code: Select all---[ end trace 13dfd971ff8e0aed]---
(Might contain typos. I don't know how to get the whole messages since the system dies a minute after booting and I only have a few seconds after the error messages start)
Even when I prevented the xserver from starting at boot I still got the same problems.
I would very much like to be able to switch between my chips, because I can only use external monitors when the ATI chip is active, but I would also like to be able to use the battery saving internal chip option.
I also tried to install the proprietary driver (though I would prefer if I didn't have to do that), but I couldn't get the xserver to work while it was installed.
lscpi output:
Code: Select all00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 18)
00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 18)
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18)
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
[Code] ....
Musescore 2.0 is available but only for Sid, I have just installed Jessie since I wanted the stable version. I was wondering if it was possible to install that packaged only from the sid distribution on jessie. How should I proceed?
View 9 Replies View RelatedI have noticed that when installing Jessie, the graphical installer downloads updates to packages while installing if connected via Ethernet to the Internet. Remaining disconnected solves this problem. Is there any way to avoid this and install without downloading files other than apt lists?
View 3 Replies View RelatedI recently have started playing with various distros (Mostly just Zorin and Debian) and have been trying to find a GUI I can actually comfortably use without wanting to punch my screen. This lead me to cinnamon which looks like something I could actually use.
I performed a fresh installation of Debian Jessie without the desktop environment and print server (System Utilities or whatever that option is called was left checked) and after the system installed and booted I proceeded to login as the root and install cinnamon. Unfortunately afterwards my system would be nothing but a black screen with a box saying that cinnamon had crashed and was running in fallback mode.
However if I let a fresh installation install the default GUI of xfce and then perform the cinnamon installation, cinnamon will install and run. My question is why doesn't a clean install with cinnamon work but installing cinnamon after another gui does? I don't get any apparent error messages beyond cinnamon crashing and I'm still fairly new to Linux.
I have a Dell laptop (inspiron 1150) which was dual booting Windows XP and Ubuntu 9.04. I have successfully installed Debian Jessie Standard over the Ubuntu. I pre-partitioned using gparted-live to make a separate single partition for the Debian install. Guided partitioning was then carried out by the installer producing separate /, /home, and swap partitions. After installation, the grub menu shows an entry for Debian and Windows XP. I can boot Debian, but not Windows XP. The symptoms are the same as reported in other forums: A terminal is displayed, vanishes and the system reboots defaulting to the Debian boot.
The grub.cfg file for the Jessie system has an other-os entry:
Code: Select allmenuentry "Microsoft Windows XP Home Edition (on /dev/sda2)" {
set root=(hostdisk//dev/sda, msdos2)
search --no-floppy --fs-uuid --set=root cc0ce0ab0ce091ae
drivemap -s (hd0) ${root}
chainloader +1
}
The original Windows entry for the Ubuntu install was:
Code: Select allmenuentry "Microsoft Windows XP Home Edition (on /dev/sda2)" {
insmod ntfs
set root=(hd0,2)
search --no-floppy --fs-uuid --set cc0ce0ab0ce091ae
drivemap -s (hd0) ${root}
chainloader +1
}
The partitions produced by partman look OK (during the pre-partitioning I did not touch sda1, sda2, or sda3):
Code: Select all~ # fdisk -l
Disk /dev/sda: 37.3 GiB, 40007761920 bytes, 78140160 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
[Code] .....
Partition table entries are not in disk order.
The os-prober found XP:
Code: Select all~ # os-prober
/dev/sda2:Microsoft Windows XP Home Edition:Windows:chain
So it seems that everything is in place, but there are perhaps important differences in the grub.cfg files. Are the two "set root" commands equivalent for example?
I am having a problem with my new Toshiba Satellite Laptop... I had installed debian for some time but last week suddenly stopped working.
- the computer stopped working at all... nor bios access.
- I did a new bootable installation in USB drive and downloaded the latest debian iso from official website and created the bootable device via dd as usual.
- I installed the new debian but after I removed the usb drive in order to boot into my new system. I was taken to a screen saying "Start PXE over IPv6 -- Start PXE over IPv4 ..." I followed several links looking for a fix, and all of them lead me to disable network boot option in BIOS setup...
- I disabled but after that it appears a new message "No Bootable device -- Press restart system" and nothing happens from there.
- I have found info in Internet regarding this issue, but all I find is "windows related"
- Someone recommended me this: "The BIOS can no longer recognize the hard drive as a bootable device. This could be for a number of reasons. Your best bet, if it is still under warranty, is going to be to bring it back to where you purchased it"
- But instead, what I did was to create a new bootable device, this time containing XUBUNTU and installed it to the machine, I had the good news that the installation proceed without any problem, so I could figured out that my machine it is still alive...
- Back to my issue and hoping that something unexpected happened that fixed the machine, I got back and did a new Debian bootable device, also hoping that the latest was corrupted or something, but after reboot to my new system... the problem persisted again.
- I chose to have 1 partition in full disk.
Now I don't know what else to do... I don't like ubuntu, I have used debian for some years and I want to keep using it and I would not like to be forced to move to ubuntu or xubuntu for this.
I installed jessie amd64 lxde to a thumb drive to use with a laptop. Vanilla install using the amd64 lxde live cd. Upon booting the usb system, I am presented with a black screen with blinking cursor. No grub screen, no ability to type any commands and no ability to switch to another terminal. I tried booting into the live cd and I could get into the intro splash screen. Booting to the live system from there would also hang at a black screen.
However, using the kernel parameter "nomodeset" from the splash screen did allow the live system to boot to the desktop. I booted the live system, mounted the usb system and chrooted into it. I edited /etc/default/grub to include "nomodeset" in the GRUB_CMDLINE_LINUX_DEFAULT and GRUB_CMDLINE_LINUX variables and then ran update-grub.
Upon reboot to the usb system the problem still occurred. The video card in question is a amd firepro 5800m which has an lspci line of mobile radeon 5000 series. This card was supported in wheezy and apparently works with the live system.
I have the Ubuntu 10.04 beta, though It isn't the most stable,how can I upgrade, without having to burn a cd, from the Ubuntu 10.04 beta, to the Ubuntu 10.04 stable release?
View 9 Replies View RelatedI'm trying to upgrade my Win8/Wheezy 64-bit machine to Jessie 8.1 by installing from the amd64-bit netinstall iso image on a USB flash drive. I had done the previous, Wheezy, install on a disk partition that was whole-partition LUKS/LVM drive, with separate logical partitions for swap, root, and home.
Before doing the upgrade, I booted to the BIOS to ensure that my UEFI system had the correct, CSM and Legacy modes enabled in it, so that installer would boot using the non-efi BIOS mode.
Step one of the upgrade was to boot the netinstall and enter the rescue mode so that I could manually do the cryptsetup/LVM business. When I returned to the installer, I mounted the now-recognized logical partitions normally, choosing to format only the swap and / partitions.
During the entire process, I had to go into rescue mode one more time to manually mount the unencrypted /boot partition, along with my /home partition. I copied a backup of my old /etc/crypttab from the latter, and after returning to the installer, finished the install. That finish included installing grub on my hard drive's main boot partition.
Everything seemed to finish with no problems. However, when I try to boot the debian bootloader, I get tossed to grub rescue with the message that '/grub/x86_64-efi/normal.mod' doesn't exist. At this point I returned to the installer, mounted the /boot partition, and saw that there grub-install didn't create that an x86_64-efi directory at all. Instead, it had created an i386 directory. The exact name escapes me at the moment.
I *think* that my install was clean other than the last bit that was related to installing the bootloader. How to reinstall the bootloader in such a way as to make all of this work.
I installed a Debian server a few time ago, with the Squeeze version.
Now I want to upgrade it to Jessie, but all related documentation only talk about the procedures to upgrade from Wheezy to Jessie.
What should I do? Upgrade first Squeeze to Wheezy and after that to Jessie, or I can upgrade from Squeeze to Jessie?
I have installed Ubuntu 10.10. When the stable version is released, will I be able to upgrade to the stable version from the update manager, or will i have to install the stable version separate?What about 10.04 to 10.10 upgrade?
View 2 Replies View RelatedI 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?
